similar to: FFS related panic in 4.8-STABLE

[ Asked on -questions on Friday; re-asking now on -stable without cross-post] I recently upgraded a 4.11-REL machine to 6.0-REL and have run into some snags. While the installation from CD went fine, after configuring and enabling my ed0 NIC, bad things start to happen. FWIW, this machine is an ancient (hardware circa 1991, BIOS circa 1994) dual-Pentium 133 MHz machine, with EISA/PCI and

Here's a patch against 4.8-RELEASE kernel that allows disk writes on softupdates-enabled filesystems to be delayed for (theoretically) arbitrarily long periods of time. The motivation for such updating policy is surprisingly not purely suicidal - it can allow disks on laptops to spin down immediately after I/O operations and stay idle for longer periods of time, thus saving considerable amount

Hello, This file server was upgraded from 6.2-RELEASE-p$something to 6.3-RELEASE-p3 (current RELENG_6_3 sources via csup) on August, 11 and rebooted to the new kernel on August, 12. The school is closed due to holidays. The only load is mail delivery to Maildirs via NFS from another server (just 50 mailboxes or so, none of them very busy) and nightly backups. I went there on August, 13 to perform

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

Not sure what all to do, but doing a 'gdb -k kernel.debug /dev/mem', a backtrack on one of the processes shows ... server has been up 12 days now, and running a June 8th kernel ... #0 0x20f4f0 in ?? () (kgdb) proc 67258 (kgdb) bt #0 mi_switch () at machine/globals.h:119 #1 0x8014a1f9 in tsleep (ident=0x8a3d2200, priority=8, wmesg=0x80263d4a "inode", timo=0) at

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)

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

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

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, I need some help to understand a backtrace. The situation is as follows: A diskless system acting as a kind of bandwithshaping firewall with both ipfw2 and ipfilter active at the same time. Ipfilter is used for port adress translation. The system panics about once every 6 hours. The network load is very low, only one Windows XP machine is connected but not actively used. I added a disk

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

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,

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

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,

I started sharing out zfs filesystems via NFS last week using sharenfs=on. That seems to work fine until I reboot. Turned out the NFS server wasn''t enabled - I had to enable nfs/server, nfs/lockmgr and nfs/status manually. This is a stock SXCR b49 (ZFS root) install - don''t think I''d changed anything much. Shouldn''t a ZFS share be permanently enabling NFS?

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 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

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

I get the above panic after nfs clients attach to this nfs server and being read/write ops on it after an unclean shutdown. I've fsck'ed the fs, and it marks it as clean, but I get this every time. It's an NFS share of a GEOM stripe (about 2TB). mode = 0100600, inum = 58456203, fs = /mnt panic: ffs_valloc: dup alloc I do have dumps from two crashes so far. This is