Subject: kern/31501: reproducible panics with 3.99.9/i386
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: None <dive@endersgame.net>
List: netbsd-bugs
Date: 10/07/2005 11:05:01
>Number:         31501
>Category:       kern
>Synopsis:       NetBSD 3.99.9 panics in a repeatable manner on i386
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 07 11:05:00 +0000 2005
>Originator:     dive@endersgame.net
>Release:        NetBSD 3.99.8
>Organization:
>Environment:
System: NetBSD jane.endersgame.net 3.99.8 NetBSD 3.99.8 (JANE) #64: Thu Sep 22 18:50:15 EDT 2005 dive@jane.endersgame.net:/sys/arch/i386/compile/JANE i386
Architecture: i386
Machine: i386
>Description:
Whenever trying to boot a 3.99.9 kernel (I'm currently running 3.99.8, and have
been meaning to upgrade, but obviously can't, as I can't get 3.99.9 to boot) I
get a kernel panic every time. As it panics early in the boot process, I am
unable to get a crash dump, but I have typed out a traceback:

fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
uvm_fault(0xc0313b20, 0, 0, 1) -> 0xe
kernel: page fault trap, code=0
Stopped in pid 0.1 (swapper) at netbsd:bufq_alloc+0x6b: cmpl    %ebx,0x8(%esi)
db> t
bufq_alloc(c15fa9c4,22,50,2,12) at netbsd:bufq_alloc+0x6b
fdattach(c157e200,c15fa800,c035cee0,0,c03047a0) at netbsd:fdattach+0x75
config_attach_loc(c157e200,c02fda50,0,c035cee0,c028fa00) at
netbsd:config_attach_loc+0x2cc
fdcfinishattach(c157e200,c01e15f0,0,c025fda80,358000) at
netbsd:fdcfinishattach+0x110
config_process_deferred(c0315144,0,c0314a0,bfeff000,c02fda80) at
netbsd:config_process_deferred+0x46
configure(0,1,0,0,0) at netbsd:configure+0x64
main(0,0,0,0,0) at netbsd:main+0xc9

At first I thought this might be something to do with the floppy driver, so I
removed that and tried again, same result, just at a different point in the
kernel. The hardware is fine, and the ram has been through memtest86 with no
problems.

More detail about the exact hardware configuration can be provided on request,
but I do not think this is a hardware issue.

Kernel config used:
# jane.endersgame.net kernel configuration [NetBSD (current) i386]
# AMD Athlon XP 2700+ (TBred) 2.16ghz, 256KB L2 cache, 1GB DDR333 SDRAM
# $egnet: JANE,v 1.104 2005/10/07 10:32:31 dive Exp $

machine		i386	x86

ident		"JANE"

maxusers	128

makeoptions	COPTS="-pipe -O2 -march=athlon-xp"
makeoptions	DEBUG="-g"

options		I686_CPU
options		EXEC_ELF32
options		EXEC_AOUT
options		EXEC_SCRIPT
options		DEBUG
options		DDB
options		MTRR
options		RTC_OFFSET=0
options		NTP
options		SYSVSHM
options		SYSVMSG
options		SYSVSEM
options		SHMMAXPGS=32768
options		COMPAT_30
options		COMPAT_20
options		COMPAT_LINUX
options		COMPAT_OSSAUDIO
options		USER_LDT
options		INET
options		WSEMUL_VT100
options		WS_KERNEL_FG=WSCOL_GREEN
options		WSDISPLAY_COMPAT_PCVT
options		WSDISPLAY_COMPAT_SYSCONS
options		WSDISPLAY_COMPAT_USL
options		WSDISPLAY_COMPAT_RAWKBD
options		XSERVER
options		INSECURE
options		PCIBIOS
options		PCIVERBOSE
options		NFSSERVER
options		UFS_DIRHASH

file-system	FFS
file-system	NFS
file-system	CD9660
file-system	NULLFS
file-system	PROCFS
file-system	MSDOSFS
file-system	PTYFS

config		netbsd root on wd0a type ffs dumps on wd0b

mainbus0	at root
cpu0		at mainbus0
pci0		at mainbus? bus ?
pci*		at pchb? bus ?
pci*		at ppb? bus ?
agp*		at pchb?
pchb*		at pci? dev ? function ?
pcib*		at pci? dev ? function ?
ppb*		at pci? dev ? function ?
isa0		at pcib?
npx0		at isa0 port 0xf0 irq 13
fdc0		at isa0 port 0x3f0 irq 6 drq 2
vga*		at pci? dev ? function ?
pckbc0		at isa0
pckbd0		at pckbc0
wsdisplay*	at vga? console ?
wskbd0		at pckbd0 console ? mux 1
pcppi0		at isa?
attimer0	at isa?
sysbeep0	at pcppi0
viaide0		at pci0 dev 15 function 0
viaide1		at pci0 dev 15 function 1
pdcide*		at pci? dev ? function ?
satalink*	at pci? dev ? function ?
atabus0		at viaide0 channel 0
atabus1		at viaide0 channel 1
atabus2		at viaide1 channel 0
atabus3		at viaide1 channel 1
atabus*		at ata?
atapibus*	at atapi?
wd0		at atabus0 drive 0 flags 0x0000
wd1		at atabus1 drive 0 flags 0x0000
wd2		at atabus2 drive 0 flags 0x0000
wd*		at atabus? drive ? flags 0x0000
cd*		at atapibus? drive ? flags 0x0000
fd0		at fdc? drive ?
uhci*		at pci? dev ? function ?
usb*		at uhci?
uhub*		at usb?
uhub*		at uhub? port ? configuration ? interface ?
uhidev*		at uhub? port ? configuration ? interface ?
ums*		at uhidev? reportid ?
uaudio*		at uhub?
wsmouse*	at ums? mux 0
skc*		at pci? dev ? function ?
sk*		at skc?
makphy*		at mii? phy ?
auvia*		at pci? dev ? function ?
audio*		at audiobus?
com0		at isa0 port 0x3f8 irq 4

pseudo-device	vnd		2
pseudo-device	bpfilter
pseudo-device	tun
pseudo-device	loop
pseudo-device	pty
pseudo-device	rnd
pseudo-device	wsmux
pseudo-device	wsfont
pseudo-device	clockctl


>How-To-Repeat:
Boot the above kernel config with latest -current source on this machine. I
don't know if others are affected by this bug or not.
>Fix:
Unknown.