similar to: FREEBSD 7.1-STABLE crashes when trying to mount USB device of solaris UFS filesystem

Hi there, from time to time my PC panics when I insert an empty DVD or CD-R. The kernel locks up instantly after the DVD writer's tray is closed. It seems burning the first DVD isn't critical but inserting the second one seems susceptible. I use k3b as software, which polls the hardware while the tray is open, maybe it's something with hald. Don't know, just use this. I

Hello, I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on the same day. I had a panic that looks to me very similiar to the one described here (hence the subject): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html What caught my curiosity is the message: Unread portion of the kernel message buffer: acd0: WARNING - TEST_UNIT_READY read

Hello, My server is experiencing occasional kernel panics when under moderate load. I'm attaching a crash dump and the dmesg output. I'm not sure how to read the kernel backtrace but it looks like the Intel NIC (em0) caused the problem. Occasionally, I used to get a "em0: watchdog timeout -- resetting" error message, but I never had a kernel panic. The problem started last

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,

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

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)

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:17.procfs Security Advisory The FreeBSD Project Topic: Kernel memory disclosure in procfs and linprocfs Category: core Module: sys Announced:

I didn't get much (read: any) feedback from the freebsd-emulation list on this, so i'm passing it on myself. My original post can be found at: http://lists.freebsd.org/pipermail/freebsd-emulation/2003-August/000136.html A few days ago, i found myself in need of mounting a vmware image on my old 4.7-STABLE system. To do this, i needed linprocfs functioning properly, but this module

CentOS Errata and Enhancement Advisory 2012:0563 Upstream details at : https://rhn.redhat.com/errata/RHEA-2012-0563.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3339ea32376a891578471c3c02ae549c47231da1b45cbe9aa74770c7358e1713 kmod-snd_hda-1.0.21.6.3.0-1.el6_2.i686.rpm x86_64:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:17.procfs Security Advisory The FreeBSD Project Topic: kernel memory disclosure via procfs Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-03:17.procfs Security Advisory The FreeBSD Project Topic: kernel memory disclosure via procfs Category: core Module: sys Announced:

Hi! I've updated the patch I've tested on 6.3 for 6.4 (only offsets differ), if anyone can test it I can file a PR so it hopefully :) can be committed: http://people.freebsd.org/~nox/linprocfs-6.4.patch (same patch for 6.3: http://people.freebsd.org/~nox/linprocfs-6.3.patch ) The original posting with the patch for RELENG_7 that I used is here:

Hi List! Don't see much discussion about MAC here, time to change that! :-) Currently trying to set up a service jail, according to instructions in the handbook[1]. The problem I'm facing is that nullfs does not seem to support multilabeled filesystems, or am i missing something? ls -lZ /usr/js/testjail/var/run/test -rw-r--r-- 1 root wheel biba/equal 0 Feb 6 17:15

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

Hi, I am going to merge latest batch of the nullfs improvements into stable/9. This will bring up significant performance enchancements due to use of the shared locks for lookups if the lower layer supports it, much better caching on the nullfs layer, and proper handling of the text segments on the nullfs. Also, it should improve the error recovery and some corner cases with locking.