[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout

2014-12-28 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386790

[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout

2014-10-29 Thread joneall
Tested with upstream kernel vmlinuz-3.18.0-031800rc2-generic. The problem of an off-line CPU remains: $ lscpu Architecture: x86_64 CPU op-mode(s):32-bit, 64-bit Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0 Off-line CPU(s) list: 1

[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout

2014-10-29 Thread Christopher M. Penalver
joneall, please answer the following questions: + Could you please provide the specific model of your D-Link hub? + Is this limited to either a specific number of devices or a specific device plugged in simultaneously? + Did this problem not occur in a release prior to Trusty? ** Tags added:

[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout

2014-10-29 Thread joneall
The hub is a D-Link model DUB-H7 with 6 ports of which 2 powered. I get the problem with the my mouse, an external USB disk and an HP Officejet 2620 printer plugged into the D-Link. My Samsung Syncmaster T240 screen hub, the D-link and a Logitch K120 keyboard are plugged directly into the

[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout

2014-10-29 Thread joneall
In order to answer your last question, I just booted a Debian system $ uname -a Linux jon-debian 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2 x86_64 GNU/Linux and it also has the kernel panic: $ dmesg | grep -i smp [0.00] Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc

[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout

2014-10-29 Thread Christopher M. Penalver
joneall: With fewer devices plugged in, I did not have the problem, but I cannot be quantitative about this withour more testing. So, any combination of two devices plugged into the hub does not demonstrate this problem, correct? In order to answer your last question, I just booted a Debian

[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout

2014-10-29 Thread joneall
Sorry, I don't know enough about kernels. I would have thought a Debian kernel at a certain level was the same as an Ubuntu one. I will make some more test (like with older kernels) tomorrow. Thanks again for your interest. -- You received this bug notification because you are a member of

[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout

2014-10-28 Thread Joseph Salisbury
** Tags added: kernel-da-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1386790 Title: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout To manage notifications about this bug go to: