kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #86803
[Bug 1386790] [NEW] Kernel panic CPU1 did not get callout
Public bug reported:
When booting with a D-Link USB hub connected, the boot process "finds"
only one core of my dual-core CPU:
$ dmesg | grep -i smp
[ 0.000000] Linux version 3.13.0-37-generic (buildd@kapok) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 (Ubuntu 3.13.0-37.64-generic 3.13.11.7)
[ 0.000000] found SMP MP-table at [mem 0x000f53c0-0x000f53cf] mapped at [ffff8800000f53c0]
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.020375] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
[ 0.123368] smpboot: CPU0: Intel Pentium(R) Dual-Core CPU E6700 @ 3.20GHz (fam: 06, model: 17, stepping: 0a)
[ 0.124000] x86: Booting SMP configuration:
[ 10.160714] smpboot: CPU1: Not responding
[ 10.160748] smpboot: Total of 1 processors activated (6399.99 BogoMIPS)
[ 0.124000] Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout!
With the USB hub unplugged, the boot always "finds" the CPU:
$ dmesg | grep -i smp
[ 0.000000] Linux version 3.13.0-37-generic (buildd@kapok) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 (Ubuntu 3.13.0-37.64-generic 3.13.11.7)
[ 0.000000] found SMP MP-table at [mem 0x000f53c0-0x000f53cf] mapped at [ffff8800000f53c0]
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.010389] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
[ 0.061061] smpboot: CPU0: Intel Pentium(R) Dual-Core CPU E6700 @ 3.20GHz (fam: 06, model: 17, stepping: 0a)
[ 0.064000] x86: Booting SMP configuration:
[ 0.074763] smpboot: Total of 2 processors activated (12799.47 BogoMIPS)
Why does a CPu not respond quickly enough because of a hub? Or is it
Linux which is too hasty? Or something else? In any case, it is
bothersome not to be able to use the USB hub.
I am using Ubuntu 14.04.1 LTS with KDE, aka Kubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-37-generic 3.13.0-37.64
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: jon 2453 F.... pulseaudio
jon 2809 F.... pulseaudio
/dev/snd/controlC0: jon 2453 F.... pulseaudio
jon 2809 F.... pulseaudio
CurrentDesktop: KDE
Date: Tue Oct 28 17:34:10 2014
HibernationDevice: RESUME=UUID=a10df41c-1508-4381-bb09-0b6992378272
InstallationDate: Installed on 2014-10-25 (3 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=7efb481c-5492-4093-9000-a5be0fc30152 ro
RelatedPackageVersions:
linux-restricted-modules-3.13.0-37-generic N/A
linux-backports-modules-3.13.0-37-generic N/A
linux-firmware 1.127.7
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FI
dmi.board.name: G31M-ES2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFI:bd08/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G31M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1386790
Title:
Kernel panic CPU1 did not get callout
Status in “linux” package in Ubuntu:
New
Bug description:
When booting with a D-Link USB hub connected, the boot process "finds"
only one core of my dual-core CPU:
$ dmesg | grep -i smp
[ 0.000000] Linux version 3.13.0-37-generic (buildd@kapok) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 (Ubuntu 3.13.0-37.64-generic 3.13.11.7)
[ 0.000000] found SMP MP-table at [mem 0x000f53c0-0x000f53cf] mapped at [ffff8800000f53c0]
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.020375] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
[ 0.123368] smpboot: CPU0: Intel Pentium(R) Dual-Core CPU E6700 @ 3.20GHz (fam: 06, model: 17, stepping: 0a)
[ 0.124000] x86: Booting SMP configuration:
[ 10.160714] smpboot: CPU1: Not responding
[ 10.160748] smpboot: Total of 1 processors activated (6399.99 BogoMIPS)
[ 0.124000] Kernel panic - not syncing: smp_callin: CPU1 started up but did not get a callout!
With the USB hub unplugged, the boot always "finds" the CPU:
$ dmesg | grep -i smp
[ 0.000000] Linux version 3.13.0-37-generic (buildd@kapok) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014 (Ubuntu 3.13.0-37.64-generic 3.13.11.7)
[ 0.000000] found SMP MP-table at [mem 0x000f53c0-0x000f53cf] mapped at [ffff8800000f53c0]
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] smpboot: Allowing 4 CPUs, 2 hotplug CPUs
[ 0.010389] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
[ 0.061061] smpboot: CPU0: Intel Pentium(R) Dual-Core CPU E6700 @ 3.20GHz (fam: 06, model: 17, stepping: 0a)
[ 0.064000] x86: Booting SMP configuration:
[ 0.074763] smpboot: Total of 2 processors activated (12799.47 BogoMIPS)
Why does a CPu not respond quickly enough because of a hub? Or is it
Linux which is too hasty? Or something else? In any case, it is
bothersome not to be able to use the USB hub.
I am using Ubuntu 14.04.1 LTS with KDE, aka Kubuntu.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-37-generic 3.13.0-37.64
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: jon 2453 F.... pulseaudio
jon 2809 F.... pulseaudio
/dev/snd/controlC0: jon 2453 F.... pulseaudio
jon 2809 F.... pulseaudio
CurrentDesktop: KDE
Date: Tue Oct 28 17:34:10 2014
HibernationDevice: RESUME=UUID=a10df41c-1508-4381-bb09-0b6992378272
InstallationDate: Installed on 2014-10-25 (3 days ago)
InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=7efb481c-5492-4093-9000-a5be0fc30152 ro
RelatedPackageVersions:
linux-restricted-modules-3.13.0-37-generic N/A
linux-backports-modules-3.13.0-37-generic N/A
linux-firmware 1.127.7
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/09/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FI
dmi.board.name: G31M-ES2L
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFI:bd08/09/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: G31M-ES2L
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386790/+subscriptions
Follow ups
-
[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout
From: Launchpad Bug Tracker, 2014-12-29
-
[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout
From: joneall, 2014-10-29
-
[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout
From: Christopher M. Penalver, 2014-10-29
-
[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout
From: joneall, 2014-10-29
-
[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout
From: joneall, 2014-10-29
-
[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout
From: Christopher M. Penalver, 2014-10-29
-
[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout
From: joneall, 2014-10-29
-
[Bug 1386790] Re: [Gigabyte G31M-ES2L] Kernel panic CPU1 did not get callout
From: Joseph Salisbury, 2014-10-28
-
[Bug 1386790] Re: Kernel panic CPU1 did not get callout
From: Christopher M. Penalver, 2014-10-28
-
[Bug 1386790] Status changed to Confirmed
From: Brad Figg, 2014-10-28
-
[Bug 1386790] [NEW] Kernel panic CPU1 did not get callout
From: joneall, 2014-10-28
References