Hi Antonio, Anotonio Marcos López Alonso wrote: >> On Sat, 2011-09-17 at 15:59 +0100, Antonio Marcos López Alonso wrote:
>>> 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. [...] > 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). [...] > El Lunes, 19 de Septiembre de 2011, Ben Hutchings escribió: >> 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. Did you end up passing this upstream? I'd also be interested to hear if more recent kernels behave differently (though I expect they don't). Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120125214257.GA2340@burratino
