Re: Kernel panic on amd64Netbsd 4.0

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Sep 26, 2008 at 04:10:30AM -0700, Paul Goyette wrote:
> On Fri, 26 Sep 2008, Stephen Borrill wrote:
> 
> >>There are no general issues with bounce buffers, AFAIK. But there
> >>may be issues with individual drivers not doing the bus_dma(9)
> >>thing properly.
> >
> >Are there any known guilty drivers to be either avoided or fixed?
> 
> I don't know which devices/drivers are prone to this, but my system is 
> rather an "ordonary" one, with nothing exotic as far as I know.  Here's 
> my dmesg:
> 
> Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
>     2006, 2007, 2008
>     The NetBSD Foundation, Inc.  All rights reserved.
> Copyright (c) 1982, 1986, 1989, 1991, 1993
>     The Regents of the University of California.  All rights reserved.
> 
> NetBSD 4.99.72 (SPEEDY (ASUS M2N-E) 2008-09-20 21:18:14) #0: Sat Sep 20 
> 14:36:00 PDT 2008
>       
> paul%speedy.whooppee.com@localhost:/build/obj/amd64/sys/arch/amd64/compile/SPEEDY
> total memory = 3070 MB
> avail memory = 2967 MB
> timecounter: Timecounters tick every 10.000 msec
> timecounter: Timecounter "i8254" frequency 1193182 Hz quality 100
> SMBIOS rev. 2.4 @ 0xf0000 (72 entries)
> System manufacturer System Product Name (System Version)
> mainbus0 (root)
> cpu0 at mainbus0 apid 0: AMD 686-class, 2310MHz, id 0x100f22

I've only Intel systems with more than 4GB RAM.

> cpu0: erratum 298 present
> cpu0: erratum 298 present
> cpu0: erratum 309 present
> cpu0: WARNING: errata present, BIOS upgrade may be
> cpu0: WARNING: necessary to ensure reliable operation

Could this be one reason ?

> ohci0 at pci0 dev 2 function 0: vendor 0x10de product 0x036c (rev. 0xa1)
> APCF: Picked IRQ 20 with weight 0
> ohci0: interrupting at ioapic0 pin 20
> ohci0: OHCI version 1.0, legacy support
> usb0 at ohci0: USB revision 1.0
> ehci0 at pci0 dev 2 function 1: vendor 0x10de product 0x036d (rev. 0xa2)
> APCL: Picked IRQ 21 with weight 0
> ehci0: interrupting at ioapic0 pin 21
> ehci0: EHCI version 1.0
> ehci0: companion controller, 10 ports each: ohci0
> usb1 at ehci0: USB revision 2.0

At first glance ohci and ehci are safe.

> viaide0 at pci0 dev 4 function 0
> viaide0: NVIDIA MCP55 IDE Controller (rev. 0xa1)
> viaide0: bus-master DMA support present
> viaide0: primary channel configured to compatibility mode
> viaide0: primary channel interrupting at ioapic0 pin 14

viaide is basically a pciide; I guess it's safe

> ppb0 at pci0 dev 6 function 0: vendor 0x10de product 0x0370 (rev. 0xa2)
> pci1 at ppb0 bus 1
> pci1: i/o space, memory space enabled
> azalia0 at pci0 dev 6 function 1: Generic High Definition Audio Controller
> AAZA: Picked IRQ 21 with weight 1
> azalia0: interrupting at ioapic0 pin 21
> azalia0: host: 0x10de/0x0371 (rev. 162), HDA rev. 1.0

Never used this on a >4GB system (who needs audio on such a system ? :)


> nfe0 at pci0 dev 8 function 0: vendor 0x10de product 0x0373 (rev. 0xa3)
> APCH: Picked IRQ 22 with weight 1
> nfe0: interrupting at ioapic0 pin 22
> nfe0: Ethernet address 00:1e:8c:3e:2b:95

This one could be a suspect too.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--