On Tuesday 27 March 2001 21:23, Alan Cox wrote:
> > Then, my question will be, why is the kernel loosing the irq for eth1
> > and gets unusable?
>
> In the APIC case on many intel boards it appears to be a hardware bug.
> THere is a workaround for the apic problems in -ac
Any ideas on the origina
> Then, my question will be, why is the kernel loosing the irq for eth1
> and gets unusable?
In the APIC case on many intel boards it appears to be a hardware bug. THere
is a workaround for the apic problems in -ac
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
[EMAIL PROTECTED] writes:
> > > NETDEV WATCHDOG: eth0: transmit timed out
> > > eth0: Transmit timed out: status f048 0c00 at 0/28 command 001a000
> >
> > Same here on 2.4.1 smp with two dirt-cheap ne2pci-clones. System
> > unusuable (as stated by clem ealier today) and need for
> > reb
Jens Gecius wrote:
>
> John Madden <[EMAIL PROTECTED]> writes:
>
> > I'm receiving the following errors while botting a previously-fine 2.2
> > machine (Dell 2450, 2 eepro 100's):
> >
> > NETDEV WATCHDOG: eth0: transmit timed out
> > eth0: Transmit timed out: status f048 0c00 at 0/28 co
John Madden <[EMAIL PROTECTED]> writes:
> I'm receiving the following errors while botting a previously-fine 2.2
> machine (Dell 2450, 2 eepro 100's):
>
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out: status f048 0c00 at 0/28 command 001a000
Same here on 2.4.1 s
I'm receiving the following errors while botting a previously-fine 2.2
machine (Dell 2450, 2 eepro 100's):
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out: status f048 0c00 at 0/28 command 001a000
(repeating with different status codes..)
Any thoughts?
John
-
To unsubsc
6 matches
Mail list logo
