Comment 0 for bug 1176577

Right after upgrading kernel from 3.5 to 3.8 (Ubuntu 13.04), the syslog got flooded by a large number of such messages:

(cut)
May 5 15:33:15 compaq-aldo kernel: [ 205.064042] mei 0000:00:03.0: unexpected reset: dev_state = RESETING
May 5 15:33:21 compaq-aldo kernel: [ 211.076029] mei 0000:00:03.0: unexpected reset: dev_state = RESETING
May 5 15:33:27 compaq-aldo kernel: [ 217.088035] mei 0000:00:03.0: unexpected reset: dev_state = RESETING
May 5 15:33:33 compaq-aldo kernel: [ 223.100039] mei 0000:00:03.0: unexpected reset: dev_state = RESETING
May 5 15:33:39 compaq-aldo kernel: [ 229.112045] mei 0000:00:03.0: unexpected reset: dev_state = RESETING
(cut)

This was associated by non reliable ethernet functionality, i.e. transfer of large files from my Ubuntu box to a local NAS connected via ethernet got hanging with no other apparent errors or diagnostics: nautilus copy just stopped transferring data, leaving the copy window there with the progress bar stopped.

I tried to reboot, but this behaviour is perfectly reproducible.

This is one of the first syslog lines got from that kernel:

May 5 15:30:15 compaq-aldo kernel: [ 0.000000] Linux version 3.8.0-19-generic (buildd@roseapple) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #30-Ubuntu SMP Wed May 1 16:36:13 UTC 2013 (Ubuntu 3.8.0-19.30-generic 3.8.8)

I attach the whole syslog from boot of that kernel.

On the same box, launching a previsous kernel (3.5) works flawlessly. For the time being, I removed 3.8 kernel from my box, now running 3.5.

Kind regards
Aldo