Hi Nathan!
On Mit, 25 Aug 2004, Nathan Bryant wrote:
Oops, never mind that. That's just because you hadn't ifup'd the device
I did.
Before you ran cat /proc/interrupts after resume? Are you sure? eth0 didn't appear anywhere in there...
yet. But I still suspect a driver issue; your IRQ routing looks like it should be OK, but somebody is sending repeated interrupts. You could test with "acpi=noirq", but I don't think that will help.
It worked!!!! Yes, no problems. Booting with acpi=noirq and loading the b44 module let it find irq 5 and it is working. I am writing this email from after a resume, even X worked out of the box.
Back to the drawing board. :( That means there's still something wrong with pci_link.c
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
