http://bugzilla.suse.com/show_bug.cgi?id=1146782 http://bugzilla.suse.com/show_bug.cgi?id=1146782#c1 Michal Kubeček changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mkubecek@suse.com Summary|Go To Meeting kills |Go To Meeting kills |ethernet network connection |ethernet network connection |intermittendly |intermittendly (r8152 | |4-1.2:1.0 eth2: Tx status | |-71) --- Comment #1 from Michal Kubeček --- This is probably the important part: Aug 22 09:13:04 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:04 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:04 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:04 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:04 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:05 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:05 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:05 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:05 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 Aug 22 09:13:05 d41.suse.de kernel: r8152 4-1.2:1.0 eth2: Tx status -71 These errors go on after this. There is also a lot of NetworkManager timeout messages but those seem to appear even befor the real problem starts so they may not be relevant. -71 would be -EPROTO but I don't know if it's the right way to interpret urb->status (which is where write_bulk_callback() takes the error code from). -- You are receiving this mail because: You are on the CC list for the bug.