13.10: Kernel panic - not syncing (on system start)

Medion P8610 Fabian Wehning 2 participants 3 messages Dec 19, 2013 – Dec 20, 2013 ACPI

Share & tools

Fabian Wehning

author

2013-12-19 21:53 UTC #0 lore raw

[1.] One line summary of the problem:
[Medion P8610] 13.10: Kernel panic - not syncing (on system start)

[2.] Full description of the problem/report:
While booting linux crashes with the message "Kernel panic - not
syncing: Attempt to kill init! exitcode=0x00000009". In a bisect (done by Joseph Salisbury [[email protected]]) it was tested and this bug seems to be introduced either by

commit 76a6225bf0b64572251a8c27d33e84afac6af713
Author: Bob Moore <[email protected]>
Date: Fri Mar 8 09:23:16 2013 +0000

ACPICA: Split object conversion functions to a new file

commit d5a36100f62fa6db5541344e08b361b34e9114c5
Author: Bob Moore <[email protected]>
Date: Fri Mar 8 09:23:03 2013 +0000

ACPICA: Add mechanism for early object repairs on a per-name basis

[3.] Keywords (i.e., modules, networking, kernel):
kernel, Ubuntu, ACPICA

[4.] Kernel version (from /proc/version):
--> unable to boot therefore impossible to get

[5.] No Oops.. message

[6.] Beyond skill level

[7.] Environment
--> unable to boot therefore impossible to execute the command

[7.1.] Software:
--> unable to boot therefore impossible to get

[7.2.] Processor information (from /proc/cpuinfo):
--> unable to boot therefore impossible to get anything useful

[7.3.] Module information (from /proc/modules):
--> unable to boot therefore impossible to get anything useful

[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem) --> unable to boot therefore impossible to get anything useful

[7.5.] PCI information ('lspci -vvv' as root)
--> unable to boot therefore impossible to get anything useful

[7.6.] SCSI information (from /proc/scsi/scsi)
--> unable to boot therefore impossible to get anything useful

[7.7.] Other information that might be relevant to the problem (please look in /proc and include all information that you think to be relevant):
--> unable to boot therefore impossible to get anything useful

[X.] Other notes, patches, fixes, workarounds:
https://bugs.launchpad.net/bugs/1242938

Zheng, Lv

2013-12-20 08:05 UTC #1 lore raw

Hi, Fabian

Could you offer an acpidump output of this machine.
You can dump this using a booted system.
And can you try to obtain the entire panic log through serial consoles?
The last lines in the photo indicated that the kernel panic was caused by pci_assign_unassigned_resources. We need to know the device ID and the control method name to reproduce the panic using acpidump.

Thanks and best regards
-Lv

Quoted 71 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Fabian Wehning
Sent: Friday, December 20, 2013 5:53 AM
To: [email protected]
Subject: [Medion P8610] 13.10: Kernel panic - not syncing (on system start)
[1.] One line summary of the problem:
[Medion P8610] 13.10: Kernel panic - not syncing (on system start)
[2.] Full description of the problem/report:
While booting linux crashes with the message "Kernel panic - not
syncing: Attempt to kill init! exitcode=0x00000009". In a bisect (done by Joseph Salisbury [[email protected]]) it was tested and this bug seems to be introduced either by
commit 76a6225bf0b64572251a8c27d33e84afac6af713
Author: Bob Moore <[email protected]>
Date: Fri Mar 8 09:23:16 2013 +0000
ACPICA: Split object conversion functions to a new file
or
commit d5a36100f62fa6db5541344e08b361b34e9114c5
Author: Bob Moore <[email protected]>
Date: Fri Mar 8 09:23:03 2013 +0000
ACPICA: Add mechanism for early object repairs on a per-name basis
[3.] Keywords (i.e., modules, networking, kernel):
kernel, Ubuntu, ACPICA
[4.] Kernel version (from /proc/version):
--> unable to boot therefore impossible to get
[5.] No Oops.. message
[6.] Beyond skill level
[7.] Environment
--> unable to boot therefore impossible to execute the command
[7.1.] Software:
--> unable to boot therefore impossible to get
[7.2.] Processor information (from /proc/cpuinfo):
--> unable to boot therefore impossible to get anything useful
[7.3.] Module information (from /proc/modules):
--> unable to boot therefore impossible to get anything useful
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem) --> unable to boot therefore impossible to get anything useful
[7.5.] PCI information ('lspci -vvv' as root)
--> unable to boot therefore impossible to get anything useful
[7.6.] SCSI information (from /proc/scsi/scsi)
--> unable to boot therefore impossible to get anything useful
[7.7.] Other information that might be relevant to the problem (please look in /proc and include all information that you think to be relevant):
--> unable to boot therefore impossible to get anything useful
[X.] Other notes, patches, fixes, workarounds:
https://bugs.launchpad.net/bugs/1242938
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Zheng, Lv

2013-12-20 08:09 UTC #2 lore raw

In reply to Fabian Wehning

Forgot to mention that you need to open an bug at:
bugzilla.kernel.org
with product set to ACPI and component set to ACPICA-core.

Thanks and best regards
-Lv

Quoted 68 lines

From: [email protected] [mailto:[email protected]] On Behalf Of Fabian Wehning
Sent: Friday, December 20, 2013 5:53 AM
[1.] One line summary of the problem:
[Medion P8610] 13.10: Kernel panic - not syncing (on system start)
[2.] Full description of the problem/report:
While booting linux crashes with the message "Kernel panic - not
syncing: Attempt to kill init! exitcode=0x00000009". In a bisect (done by Joseph Salisbury [[email protected]]) it was tested and this bug seems to be introduced either by
commit 76a6225bf0b64572251a8c27d33e84afac6af713
Author: Bob Moore <[email protected]>
Date: Fri Mar 8 09:23:16 2013 +0000
ACPICA: Split object conversion functions to a new file
or
commit d5a36100f62fa6db5541344e08b361b34e9114c5
Author: Bob Moore <[email protected]>
Date: Fri Mar 8 09:23:03 2013 +0000
ACPICA: Add mechanism for early object repairs on a per-name basis
[3.] Keywords (i.e., modules, networking, kernel):
kernel, Ubuntu, ACPICA
[4.] Kernel version (from /proc/version):
--> unable to boot therefore impossible to get
[5.] No Oops.. message
[6.] Beyond skill level
[7.] Environment
--> unable to boot therefore impossible to execute the command
[7.1.] Software:
--> unable to boot therefore impossible to get
[7.2.] Processor information (from /proc/cpuinfo):
--> unable to boot therefore impossible to get anything useful
[7.3.] Module information (from /proc/modules):
--> unable to boot therefore impossible to get anything useful
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem) --> unable to boot therefore impossible to get anything useful
[7.5.] PCI information ('lspci -vvv' as root)
--> unable to boot therefore impossible to get anything useful
[7.6.] SCSI information (from /proc/scsi/scsi)
--> unable to boot therefore impossible to get anything useful
[7.7.] Other information that might be relevant to the problem (please look in /proc and include all information that you think to be relevant):
--> unable to boot therefore impossible to get anything useful
[X.] Other notes, patches, fixes, workarounds:
https://bugs.launchpad.net/bugs/1242938
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html