Bug 10444
Summary: | Early EC init causes boot failures on multiple brands and models | ||
---|---|---|---|
Product: | ACPI | Reporter: | TJ (linux) |
Component: | Config-Other | Assignee: | ykzhao (yakui.zhao) |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | high | CC: | bekirserifoglu |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.25-rc8 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Attachments: | VGN-FE41Z R0200J3 |
Description
TJ
2008-04-11 21:32:49 UTC
I neglected to mention that in many of the cases being reported to Ubuntu, the system only fails to boot due to this if it is on AC power. If it is allowed to boot past the ACPI initialisation phase AC power can then be resumed without an issue. More research into this needs to be done on a wider range of model/DSDT combinations with and without power. My tentative theory is that when on AC power at boot a Notify(BAT0, 0x81) event is triggered (Battery status change) to indicate charging whereas booting with no AC power connected this event presumably won't occur. Hi, TJ Will you please attach the output of acpidump? Thanks. Will you please try the latest kernel (2.6.25-rc9) and see whether the problem still exists? Please attach the output of dmesg. Thanks. Created attachment 15776 [details]
VGN-FE41Z R0200J3
This is from my PC where I was able to reproduce the issue. Remember that we're getting reports covering a several different models at Ubuntu. I'm guessing we can expect more once 8.04 Hardy is released from beta at the end of this month.
In the related Ubuntu bug report I suggested forcing the EC into interrupt mode with "ec_intr=1" https://bugs.edge.launchpad.net/linux/+bug/191137/comments/40 One user has reported back with success with "quiet ec_intr=1" with Hardy 2.6.24. I've just built 2.6.rc9 and will be testing it shortly. 2.6.25-rc9 *with CONFIG_DEBUG=y* boots successfully. I now have to try another build without the DEBUG statements since they appear to be at the root of this issue. Also, I mentioned recommending the "ec_intr=1" parameter but on searching the kernel source (2.6.24 - 2.6.25-rc9) can't find mention of it despite it being documented in Greg Koah Hartman's 'Linux Kernel in a Nutshell', chapter 9, 'Kernel Boot Command-Line Parameter Reference'. If it's been removed the experience reported by the user must have been a fluke. 2.6.25-rc9 boots successfully with no CONFIG_DEBUG_KERNEL set. Any idea where to look in the source for commits that would cause this in 2.6.24? Ideally I'd like to cherry-pick the commit(s) that will prevent this error. Will you please try the git-bisect to identify which commit causes the problem in 2.6.24? Thanks. Will you please try the latest kernel and see whether the problem still exists? Thanks. Since there is no response for more than one month, it will be rejected. If the problem still exists, please reopen it. Thanks. I had the problem with the kernel 2.6.24. Then I compiled the kernel 2.6.25.4 myself.and the problem seems to be gone. |