Thanks for your help determining the cause of this bug. There is enough
information for a developer to start work on the bug, therefore, I am
marking it confirmed. Based on your new information this is most likely
an IRQ issue. Please see the following:
https://help.ubuntu.com/community/Debuggin
Ok, the picture is getting a bit clearer... I did some further
investigation. The explanation for the "strange" part (traffic only when
moving mouse) is probably the shared interrupt 5 between the USB device
2 and the ethernet device eth0 (b44):
cat /proc/interrupts
CPU0
** Attachment added: "lspci-vvnn.log"
http://launchpadlibrarian.net/18954161/lspci-vvnn.log
--
Network traffic only when moving mouse
https://bugs.launchpad.net/bugs/287600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/18954158/dmesg.log
--
Network traffic only when moving mouse
https://bugs.launchpad.net/bugs/287600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Attachment added: "version.log"
http://launchpadlibrarian.net/18954151/version.log
--
Network traffic only when moving mouse
https://bugs.launchpad.net/bugs/287600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/18954142/uname-a.log
--
Network traffic only when moving mouse
https://bugs.launchpad.net/bugs/287600
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
This does seem like a very strange bug in the resume system. In order to get a
complete bug report we will need the following information:
uname -a > uname-a.log
cat /proc/version_signature > version.log
dmesg > dmesg.log
sudo lspci -vvnn > lspci-vvnn.log
Also, please see this guide for trouble
I forgot to say, that this problem appears right after resuming. So not
after working an hour or two, but right after startup. So it really
seems to be a hibernation/resume issue.
Thinking about it, I can't remember having seen it with the wifi
adapter. Also I noticed the ethernet device sometimes
