Bug 48755

Summary: 5.0-p2 kernel panic probably filesystem related
Product: Base System Reporter: Matthias Buelow <mkb>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 5.0-RELEASE   
Hardware: Any   
OS: Any   

Description Matthias Buelow 2003-02-27 19:00:23 UTC
Got a panic right now on 5.0-p2/i386, probably related to filesystem
stuff:

# gdb -k /boot/kernel/kernel ./vmcore.0 
GNU gdb 5.2.1 (FreeBSD)
Copyright 2002 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 "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-undermydesk-freebsd"...(no debugging symbols found)...
panic: bwrite: buffer is not busy???
panic messages:
---
panic: pmap_enter: attempted pmap_enter on 4MB page

syncing disks, buffers remaining... panic: bwrite: buffer is not busy???
Uptime: 17h3m21s
Dumping 511 MB
ata0: resetting devices ..
done
 16 32[CTRL-C to abort]  48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448[CTRL-C to abort]  464 480 496
---
#0  0xc01de84b in doadump ()
(kgdb) bt
#0  0xc01de84b in doadump ()
#1  0xc01decd6 in boot ()
#2  0xc01def23 in panic ()
#3  0xc021d692 in bwrite ()
#4  0xc021ec4e in vfs_bio_awrite ()
#5  0xc02ca63a in ffs_fsync ()
#6  0xc02c987e in ffs_sync ()
#7  0xc023070b in sync ()
#8  0xc01de94c in boot ()
#9  0xc01def23 in panic ()
#10 0xc031afed in pmap_enter ()
#11 0xc02dc8d4 in vm_fault ()
#12 0xc031e45f in trap_pfault ()
#13 0xc031df52 in trap ()
#14 0xc030f048 in calltrap ()
---Can't read userspace from dump, or kernel process---

I'll keep the crashdump for a while, in case someone wants
to extract some more info.
Comment 1 Kris Kennaway freebsd_committer freebsd_triage 2003-10-11 09:37:18 UTC
State Changed
From-To: open->feedback

Does this problem persist in 5.1-CURRENT?  If so, please obtain 
full debugging information as described here: 

http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
Comment 2 Kris Kennaway freebsd_committer freebsd_triage 2003-11-01 03:03:12 UTC
State Changed
From-To: feedback->closed

Feedback timeout