On Wed, 2003-09-24 at 11:19, Sean Estabrooks wrote:
> You can try reloading the module with the watchdog parameter to see if it
> removes the problem for you:
>
> modprobe 3x59x watchdog=1
>
> Obviously you have to unload the module before you can reload it. The
> watchdog option may or m
On Wed, 24 Sep 2003 10:45:55 -0400
David Hart <[EMAIL PROTECTED]> wrote:
> Sep 24 09:19:30 main kernel: eth0: transmit timed out, tx_status 00
> status e681.
> Sep 24 09:19:30 main kernel: diagnostics: net 0cc2 media a800 dma
> 003a.
> Sep 24 09:19:30 main kernel: eth0: Interrupt posted but
On Wed, 2003-09-24 at 09:53, Sean Estabrooks wrote:
> There should have been two additional error lines above the one you
> started with. The first one saying "transmit timed out". They would
> give important information but my guess would be tthat you have
> some bus-mastering device in the m
On Wed, 24 Sep 2003 08:42:20 -0400
David Hart <[EMAIL PROTECTED]> wrote:
> We're getting quite a few of these on one client. This works perfectly
> in Windows. Card is a 3Com 3CXFE575BT. It seems to be identified
> properly.
>
> Sep 24 07:41:58 main kernel: eth0: Interrupt posted but not delivere
We're getting quite a few of these on one client. This works perfectly
in Windows. Card is a 3Com 3CXFE575BT. It seems to be identified
properly.
Sep 24 07:41:58 main kernel: eth0: Interrupt posted but not delivered --
IRQ blocked by another device?
Sep 24 07:41:58 main kernel: Flags; bus-master
