Bug#641919: linux-image-3.0.0-1-amd64: VIA-Rhine II resetting: network connectivity lost
El Lunes, 19 de Septiembre de 2011, Ben Hutchings escribió:
> On Sat, 2011-09-17 at 15:59 +0100, Antonio Marcos López Alonso wrote:
> > Package: linux-2.6
> > Version: 3.0.0-3
> > Severity: normal
> > Tags: upstream
> >
> > This is the same behavior as bug #549606. Network connection is lost
> > somehow and dmesg outputs lots of:
> >
> > via-rhine 0000:00:12.0: eth0: Transmit timed out, status 0003, PHY status
> > 786d, resetting...
> > via-rhine 0000:00:12.0: eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
> >
> > Resetting the machine fixes the issue.
> >
> > This behavior has been happening now and then since the previous bug was
> > closed.
>
> [...]
>
> I think bug #549606 was closed in error, as the supposed fix is related
> to behaviour after a transmit timeout and not the cause of timeouts.
> Before it was closed, you found that the kernel parameter 'noapic' was a
> workaround for the problem on your system, which means it probably isn't
> a bug in the driver). I notice that you are currently *not* using that
> parameter.
Hi Ben:
I effectively used noapic to apparently workaround the problem but in the long
run I found it just minimized the problem somehow (occurrences were less).
>
> I asked you to report this bug at <http://bugzilla.kernel.org>,
> including the fact that 'noapic' works around it. The product should be
> 'Platform Specific/Hardware' and the component 'i386'.
>
> You won't be able to do that at the moment because that server is done,
> but please try to do that in a week or so. Then let us know the
> bug number so we can keep track of it.
OK, I'll do it so and let you know.
Antonio
Reply to: