eth2: Station identity 001f:0001:0008:000a
eth2: Looks like a Lucent/Agere firmware version 8.10
eth2: Ad-hoc demo mode supported
eth2: IEEE standard IBSS ad-hoc mode supported
eth2: WEP supported, 104-bit key
eth2: MAC address 00:02:2D:5C:18:9F
eth2: Station name "HERMES I"
eth2: ready
eth2: index 0x01: Vcc 3.3, irq 9, io 0x0100-0x013f
eth2: New link status: Connected (0001)
spurious 8259A interrupt: IRQ7.
eth2: New link status: Connected (0001)
If I set this network card down and try to bring it back up, all net
device access stalls in D state. No dmesg, no panics, nadda.
David
On Tue, Sep 16, 2003 at 11:06:23AM -0400, David Ford wrote:
> eth2: Station identity 001f:0001:0008:000a
> eth2: Looks like a Lucent/Agere firmware version 8.10
> eth2: Ad-hoc demo mode supported
> eth2: IEEE standard IBSS ad-hoc mode supported
> eth2: WEP supported, 104-bit key
> eth2: MAC address 00:02:2D:5C:18:9F
> eth2: Station name "HERMES I"
> eth2: ready
> eth2: index 0x01: Vcc 3.3, irq 9, io 0x0100-0x013f
> eth2: New link status: Connected (0001)
> spurious 8259A interrupt: IRQ7.
> eth2: New link status: Connected (0001)
>
> If I set this network card down and try to bring it back up, all net
> device access stalls in D state. No dmesg, no panics, nadda.
I've seen a similar problem with tg3 in virgin -test5 and with hostap in
-test4-mm5. I believe I read it was due to something failing to
release the rtnl semaphore?
--
Matt Mackall : http://www.selenic.com : of or relating to the moon