On Tue, Jun 10, 2003 at 02:08:54PM +0200, Markus Wennrich wrote: > > > > > fxp0: device timeout > > > > I get these as well. Is it on irq9 by any chance, along with acpi0 ? > > > > > > No. It's on irc 11 device 8 (as dmesg states). All irqs in bios are > > > set to 11 (factory default). ACPI is disabled. > > > > Ok, well that's a useful data point (for me anyway) since it means > > there's a problem with fxp losing interrupts that's not related to some > > other ACPI problems I've experienced, suggesting that it's therefore a > > fxp driver problem. > > I have the same problem here with a freshly cvsupped 5.1-CURRENT. > The machine has two fxp-NICs and I get device timeouts with both of > them (with acpi enabled or disabled, both the same, no change). See > attached dmesg. Well, I got a little further: Until yesterday, my fxp's both hat "irq 10", shared with the uhci-usb-controller. Everything worked fine. Since the cvsup, fxp0 uses "irq 3" (shared with sio0) and fxp1 "irq 10" (shared with uhci0), which didn't work. If I remove "sio" from my kernel-config, fxp0 works fine. But if I use the fxp1-device (dhclient or ifconfig) the machine freezes immediatly. Then I tried to also remove the usb-support, so the fxp1 has irq 10 soley for itself ... doesn't work. The machine still freezes. (I tried to pinpoint both irq's to irq 3 via device.hints (hint.fxp.1.irq=3) ... didn't worked.) Well ... at least I can use fxp0 if it has its irq soley for itself. But the machine still freezes, if I try to use fxp1. Any ideas what else I could try? I volunteer for debugging ;-) Bye, Markus -- Unix IS user friendly ... it's just selective about who its friends are.Received on Tue Jun 10 2003 - 23:34:20 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:11 UTC