Bug 58811 - 3.10-rc2 fails to boot on P4 notebook (stuck right after ACPI: Added _OSI(Processor Aggregator Device)
Summary: 3.10-rc2 fails to boot on P4 notebook (stuck right after ACPI: Added _OSI(Pro...
Status: CLOSED WILL_FIX_LATER
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Lan Tianyu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-25 11:58 UTC by Clemens Eisserer
Modified: 2013-06-03 13:04 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.10-rc2
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
screenshot of boot-log (61.85 KB, image/jpeg)
2013-05-25 11:59 UTC, Clemens Eisserer
Details
lspci output of the affacted machine (1.24 KB, text/plain)
2013-05-25 11:59 UTC, Clemens Eisserer
Details
dmesg output when booting linux-3.9.3 on the affacted machine (46.39 KB, text/plain)
2013-05-25 11:59 UTC, Clemens Eisserer
Details

Description Clemens Eisserer 2013-05-25 11:58:43 UTC
When trying to boot Fedora's 3.10-rc2 build on my old P4 based laptop (sis chipset) it gets stuck right after the following line:

ACPI: Added _OSI(Processor Aggregator Device)

When booting Linux-3.9.3, the line which appears after this is:

ACPI: EC: Look up EC in DSDT

Please see the screenshot, lspci output as well as a dmesg output of kernel-3.9.3 attached.
Comment 1 Clemens Eisserer 2013-05-25 11:59:05 UTC
Created attachment 102541 [details]
screenshot of boot-log
Comment 2 Clemens Eisserer 2013-05-25 11:59:25 UTC
Created attachment 102551 [details]
lspci output of the affacted machine
Comment 3 Clemens Eisserer 2013-05-25 11:59:49 UTC
Created attachment 102561 [details]
dmesg output when booting linux-3.9.3 on the affacted machine
Comment 4 Lan Tianyu 2013-05-27 01:15:00 UTC
Please provide the output of acpidump and do bisect to find which commit cause this regression.
Comment 5 Lan Tianyu 2013-05-27 01:19:39 UTC
BTW, please try latest upstream kernel(v3.10-rc2) to confirm whether the issue exists in upstream kernel.
Comment 6 Clemens Eisserer 2013-05-27 19:13:20 UTC
Unfortunately I don't have the time to bisect this issue.
However I'll provide an acpidump soon.
Comment 7 Lan Tianyu 2013-05-28 03:10:29 UTC
Currently, there is no way to judge how the issue happens and the log in comment #1 is too limit. So bisect is the best to find the cause.
Comment 8 Lan Tianyu 2013-05-30 06:56:02 UTC
How about with "acpi=off" kernel parameter?
Comment 9 Lan Tianyu 2013-06-03 13:04:53 UTC
There is no more clue because it just gets stuck during bootup and bisect is the best way to debug now. From comment #6, you have no time to do bisect no. So mark this bug close as WILL_FIX_LATER. If you have time to do bisect, please feel free to reopen this bug. Sorry.

Note You need to log in before you can comment on or make changes to this bug.