On Tue, Jul 17, 2012 at 08:12:10AM +0100, Julian Gilbey wrote: > On Wed, Jul 11, 2012 at 11:16:39PM +0100, Julian Gilbey wrote: > > I've had numerous occasions in at least the last month (from kernel > > 3.2.19-1 or earlier - that's as far back as my logs go) when my > > machine has given a kernel error when trying to connect to a > > Windows-driven ethernet. (I hadn't realised that it was a kernel > > issue until very recently.) Below is a typical kernel log from boot > > until the "crash" occurred; my machine was connected to the ethernet > > during this process. It is sporadic - it sometimes works fine and > > othertimes not at all, and it sometimes works and then stops working. > > A followup on this bug. I've started noticing it on my home network > with no Windows machine involved - it can occur within minutes of > booting. The only machines present on the local network are two linux > boxes and a Netgear router.
I think this may be a hardware fault: I have now identified what appears to be the physical situation under which this bug manifests itself: it reliably occurs when I attempt to connect to an ethernet without my power supply connected (i.e., running from the battery), and never seems to occur when I am on main power. So that is why I think this is a hardware fault - I guess the bug should then be closed? Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
