similar to: Processes hung in 'inode' state ...

neptune# ps -M vmcore.1 -N kernel.debug -axl | grep inode | wc -l 961 and I have a vmcore to work on here !! :) (kgdb) proc 99643 (kgdb) bt #0 mi_switch () at machine/globals.h:119 #1 0x8014a1f9 in tsleep (ident=0x8a4ef600, priority=8, wmesg=0x80263d4a "inode", timo=0) at /usr/src/sys/kern/kern_synch.c:479 #2 0x80141507 in acquire (lkp=0x8a4ef600, extflags=16777280,

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

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

Hi everybody, today I met the following problems on my freebsd box. I had a USB stick of opensolaris bootable USB image and tried to mount it on my fbsd box. The first time, when I tried to mount the usb device, my system freezed and then rebooted giving me one core in my dumpdev. When I tried to redo the mounting, the kernel informed me that the filesystem needed to be fsck'd before

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

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

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