similar to: Kernel panic on FreeBSD 4.8-STABLE

Every few days now I get a panic like the one shown in the attached backtrace. I've made sure my filesystem is clean with fsck and even turned off write caching on my IDE drive. Maybe someone here can figure out what is wrong. Let me know if you need more information. Michael -------------- next part -------------- root@taco /usr/src/sys/compile/ZOE> gdb -k -c /opt/savecore/vmcore.0

While I was tying down a supernet to the discard interface, the box crashed on me. Its a STABLE box from June 4th. I was in zebra at the time and thought I would route a /24 to ds0 instead of to the IP on ds0 (which I had done for a number of other aggregate routes). The only other "strange" thing about the box is that ds0 is loaded via kld. I will see if I can reproduce it on a

Hi stable, nice you see you again. I was one of those guys who was seeing constand panics on 24 hour boundaries but couldn't provide a backtrace due to the ar device not taking a dump. I installed a dedicated drive just to take the dump, and then didn't have a panic for a couple weeks. Now, I am back with, and I have traces to share. The first two, from 2003-09-27 and 2003-09-28

Just trying to understand if anything might be going on with this crash dump or just faulty hardware ? dmesg at the end ---Mike # gdb -k /kernel.debug vmcore.0 GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type

All: I cvsup'ed earlier this evening and am still able to reproduce this panic at will. Command line, panic backtrace, dmesg, ldd output, and mplayer version follow. If more information is needed, just let me know. % mplayer foo.mov [a quicktime file] [plays for awhile, and then panics] # gdb -k -s /usr/obj/usr/src/sys/LICHEN/kernel.debug -e /var/crash/kernel.2 -c /var/crash/vmcore.2

Hi, all-- I've got a 1997 Dell XPS D300 which has been rock-solid over the years, which I'd just upgraded via a PowerLeap iP3/T-1400C. The system seemed stable for several days, so I cvsup'ed and updated this machine from 4.7p10 to 4.8-STABLE, only to get a panic a few hours later. Can anyone make an educated guess as to whether the panic below is related to this upgrade, or

Hello. I'm having a 4.7Rp9 server which is since months quite unstable, so I've compiled a debug kernel and got a crash dump. I'm a programmer and I know a little how to use gdb, I'm not so expert about FreeBSD kernel insides however, so I can't get much from it. Any kind of help is appreciated. This is the crash message: IdlePTD at phsyical address 0x0032f000 initial pcb

Some more crashes of 4.8-RELEASE. Lets see what do I have today: # ls -l /var/crash total 1576676 -rw-r--r-- 1 root wheel 2 Jul 30 13:31 bounds -rw-r--r-- 1 root wheel 2193252 Jun 25 17:30 kernel.0 -rw-r--r-- 1 root wheel 2193252 Jul 4 00:08 kernel.1 -rw-r--r-- 1 root wheel 2193252 Jul 15 19:28 kernel.2 -rw-r--r-- 1 root wheel 2193252 Jul 16 17:50 kernel.3

Getting the following panic on a new Dell Poweredge 1650. This machine is going to be a VPN server and has a large number of pptp links configured. The machine is stable if mpd is not running. (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc0229a0f in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc0229e4d in panic (fmt=0xc042876c "%s") at

After about a day and a half or so of uptime, I'm getting the aforementioned panic on the server ... better then having it hang solid, but right now I'm not sure if this is replacing it, or just one being triggered earlier then the other ... First scan through Google, I came across some posts talking about NMBCLUSTERS ... since its at the same settings as my other server (the default)

My wife got the following from a system running (effectively) 4.8-RELEASE (I built/installed world just before the kernel version was updated from 4.8-RC to 4.8-RELEASE). I gather she made a few attempts to get mozilla to start and then the system panic'd. According to the crashdump, p->p_leader is NULL but according to the code, this can never happen. This is a UP Athlon XP-1800 with

Today my system coredumped (4.8-STABLE from Saturday), I believe it's somehow X11 related: X11 crashed first (signal 11). I was running it as root (I know I shouldn't). I didn't think about it and restarted X11. While it was starting, I had a look at the console, there was a bright white message: issignal. This shows up at X11 startup. Then the system coredumped. Below is more

Hello list, I have been fighting this problem for a few days now. I have changed memory and opened the case and monitored for heat. I have been getting the same panic about every 12 to 24 hours. I can let the system sit idle, or run it under a heavy load (cpu and disk), but the panics dont seem to be related to system load. It looks to me like a dangling pointer in softdep_update_inodeblock,

Hi Ian and others, umount(8) -f does crash here on several just updated 4.8STABLE boxes for nfs volumes. Server is an IRIX server. All clients are FreeBSD. Here is a backtrace: #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc021f1c0 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc021f60d in panic (fmt=0xc03bd664 "from debugger") at

Hello, Using the technique suggested here ( https://stat.ethz.ch/pipermail/r-devel/2007-September/047028.html), we can update a matrix in place (see example 1 below), with huge time and memory savings. Is it possible to tweak example 2 to update in place also? The only difference is that the matrix is held within a new environment. Thanks, Simon # example 1 - fast and doesn't

[ Normally I'd have replied to the original email but I couldn't figure out a way to subscribe to a list, and then reply to an email already posted to the list.] I have this very problem (with a different card): http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049618.html It looks like drm_open_helper() gets a NULL dev parameter and a panic occurs when it attempts to set

After some dialog with Terry Lambert on -hackers, I've been advised to post this here. I have a 4.7-RELEASE-p10 box that is suffering regular kernel panics. The machine is a Dell 2650 running primarily as a file/print server to a number of computer labs of about 400 machines (although it also functions as a rembo image server and squid proxy). It mainly stores applications, which

Hello folks, I have a panic at shutdown related to FUSE. #0 doadump (textdump=<value optimized out>) at pcpu.h:234 234 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt full #0 doadump (textdump=<value optimized out>) at pcpu.h:234 No locals. #1 0xffffffff8090d9a6 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:449 _ep = (struct

Hi, I've encountered a strange problem while using FreeBSD 6.0 for our local mirror (mirror.math.uni-bielefeld.de) and thus is providing access via ftp, http, rsync and cvsup (all local and remote). The system crashes periodically with a kernel panic (panic: sbdrop). The uptimes between two crashes are going from a few hours to a few weeks. The system is a i386, Intel Pentium 4 based with

It's about that situation when power returns during the shutdown sequence, and the UPS ignores the "Kill power now!" command. In Debian, there is an old workaround for this: the POWEROFF_WAIT option. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=358696 . However, it does not work in Debian Stable (Jessie, NUT 2.7.2-4), apparently because systemd thinks it's smart