On Fri, 2012-09-14 at 18:48 +0100, Julian Gilbey wrote: > Package: src:linux > Version: 3.2.23-1 > Severity: normal > > I've had four oopses today when trying to connect to an ethernet. [...] If the log doesn't actually say 'Oops', it's not an oops. In fact this is a WARNING. Anyway, the important message is: 'NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out' which basically means the hardware transmit path got stuck. When this happens the driver is called to reset the hardware, but this seems to have been unsuccessful as the driver log messages are repeated. As you say this is is not easily reproducible, I'm not sure how to make progress on it. Thinking about what might have made a difference: have you made any changes to the physical network connection recently (different cable or plugged into something different)? Was the room colder/hotter than normal when you started the computer? Ben. -- Ben Hutchings Logic doesn't apply to the real world. - Marvin Minsky
Attachment:
signature.asc
Description: This is a digitally signed message part