Re: 2.4.14-3 via-rhine lockup

Urban Widmark
2001-11-02T21:05:42Z

On Thu, 1 Nov 2001, Hans-Joachim Baader wrote:

> Hi,
>
> I sent the following message a few days ago but I didn't see it on LKML.
> Did it reach you? Anyway here it is again.

Yes, I got it haven't done anything about it yet (I blame the snow ...)

> I couldn't get the output into a file but if necessary I'll try again.

My idea was to compare before and after ...

> Oct 28 18:51:22 mandel kernel: eth0: exiting interrupt, status=0x0000.
> Oct 28 18:51:24 mandel kernel: eth0: Interrupt, status 0001.
> Oct 28 18:51:24 mandel kernel: In via_rhine_rx(), entry 11 status 00409700.
> Oct 28 18:51:24 mandel kernel: via_rhine_rx() status is 00409700.
> Oct 28 18:51:24 mandel kernel: eth0: exiting interrupt, status=0x0000.
> Oct 28 18:51:24 mandel kernel: eth0: Transmit frame #2859186 queued in slot 1.
> Oct 28 18:51:24 mandel kernel: eth0: Interrupt, status 0002.
> Oct 28 18:51:24 mandel kernel: eth0: exiting interrupt, status=0x0000.
>
>
> > After it stops working, do you still get log messages from it?
> > Including via_rhine_rx()?
>
> Yes, the above output is from the non-working state.

But everything looks fine. As I read that the card is still receiving data
and generating interrupts. After "Transmit frame" you get an interrupt
with status=2 (IntrTxDone) and you get rx interrupts as well.

One thing that is odd is that the rx status is always the same and a
broadcast, when sending something do you get anything other than
"via_rhine_rx() status is 00409700" ?

/Urban