Subject: Re: ath hickups ?
To: None <current-users@NetBSD.org, email@example.com>
From: Allen Briggs <firstname.lastname@example.org>
Date: 06/14/2007 06:33:06
On Wed, Jun 13, 2007 at 10:31:41PM -0500, David Young wrote:
> Could you have exhausted mbufs? Is OACTIVE set?
Definitely not exhausted mbufs. Not sure about OACTIVE, but I doubt it.
The system had just booted and was basically idle--just running ntpd.
> Does ath0 share the PCI bus with any other device? Does it share an
> interrupt? Does pcictl(8) indicate any PCI bus errors on the ath0?
Ugh. It's on the same bus as vga0 and does share "irq 11" with a
few devices, but does not share an ioapic pin with anyone:
ath0 at pci6 dev 3 function 0
vga0 at pci6 dev 5 function 0: ATI Technologies Radeon 7000/VE QY (rev. 0x00)
aac0: interrupting at ioapic1 pin 0 (irq 11)
aac1: interrupting at ioapic2 pin 0 (irq 11)
uhci0: interrupting at ioapic0 pin 16 (irq 11)
ath0: interrupting at ioapic0 pin 20 (irq 11)
It's the irq that counts, right? (amd64) I don't know much about
how the modern PC interrupts are supposed to work.
I'll see if I can twiddle the interrupt mappings in the BIOS or something.
I don't see any errors in the pcictl dump.
> When the net stalls, is ath0 still interrupting at all? Does it
> interrupt non-stop?
> If you enable a bunch of net80211 and ath debugging, does any event
> correlate with the stalls?
I'll take a look.
Allen Briggs | http://www.ninthwonder.com/~briggs/ | email@example.com