Bug 16318 - macbook pro 5,1 does not boot with acpi
Summary: macbook pro 5,1 does not boot with acpi
Alias: None
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_other
Depends on:
Blocks: 15310
  Show dependency tree
Reported: 2010-06-30 13:38 UTC by syamajala
Modified: 2010-07-23 12:20 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.34
Regression: Yes
Bisected commit-id:


Description syamajala 2010-06-30 13:38:03 UTC
The macbook pro 5,1 model no longer boots with acpi enabled. I can only get my system to boot with acpi=off. I tried kernel 2.6.33 and everything seems to work. When using 2.6.34 my system hangs at waiting for udev uevents to be processed. I'm trying to figure out how I can get more info. I will also try 2.6.35-rc3.
Comment 1 Zhang Rui 2010-07-01 05:43:51 UTC
I'm not aware of any 2.6.34 regressions like this.
can you use git-bisect to find out which commit introduces this bug?

cc Rafael, as this should be on 2.6.34 regressions list.
Comment 2 syamajala 2010-07-10 15:38:07 UTC
I can try, I have no experience with git though.
Comment 3 Len Brown 2010-07-13 01:59:06 UTC
lots of git bisect howto's, like this one:

also, the man page itself:


One guess would be drivers/acpi/ec.c
so you might do something simple like limit the bisect to that file,
or to drivers/acpi/
Comment 4 syamajala 2010-07-23 12:20:47 UTC
I'm not sure if I built my kernels correctly using git bisect.

I used my distributions kernel config file when I was building my kernels, but I stripped the config down a little, because it was building a lot of stuff I didn't need as modules. After going through all the git bisect steps and having each kernel work, I realized the problem must be in one of the things I didn't build as a module. So, this either might not be an upstream problem, or it might not be an acpi problem, because I was able to get my system to boot with acpi enabled with every single git bisect kernel.

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