Re: PROBLEM: Network hang: "eth0: Tx timed out (f0080), is buffer full?" (Plain)

[Jon Mason]

It seems to me that the driver does not re-enable interrupts or the
transmit and receive engines after it resets the adapter because of
the PCI bus error.

So, I would like to provide you with a patch which will log the state
of these registers after the adapter reset and during the transmit
timeout events to dmesg.  If you do not have the kernel source
available, I can try and compile the module for you (it will just take
a bit longer, as I will have to find the SuSE 9.2 source).

Thanks,
Jon


On Fri, 17 Dec 2004 18:15:13 +0100, Richard Ems
<richard.ems@xxxxxxxxxxxxxxxxxxxx> wrote:
> Jon Mason wrote:
> > It seems to me the cause of the tx timeouts is the "HostError", which
> > is a PCI bus error.  This most likely caused the adapter to hang and
> > then the transmits started timing out.
> >
> > As far as I can tell, the dl2k driver code is common between 2.4 and
> > 2.6.  So, some other change in the kernel is causing the driver to
> > behave differently and expose this problem.
> >
> > I am not the maintainer, but I can try to assist you. However, it will
> > require running debug drivers (as I am not able to find any
> > documentation on this adapter).  If you are not willing or able to do
> > this, then I would suggest going back to the 2.4 kernel.
> 
> Ok, yes, I'm willing to try your debug drivers. We'll see if I'm also
> able ;-)
> 
> What shall I do?
> 
> Thanks ,Richard
> 
> --
> Richard Ems
> 
> MTG Marinetechnik GmbH
> Wandsbeker Königstr. 62
> 22041 Hamburg
> Telefon: +49 40 65803 312
> TeleFax: +49 40 65803 392
> mail: richard.ems@xxxxxxxxxxxxxxxxxxxx
> 
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/