Messages in this thread | | | From | Henny Wilbrink <> | Date | Sun, 11 May 2008 11:35:03 +0200 | Subject | Re: 2.6.26-rc1 fails to boot |
| |
Carlos R. Mafra wrote: > On Sat 10.May'08 at 22:21:28 +0200, Henny Wilbrink wrote: > Content-Description: message body text > > Hello, > > > > Kernel 2.6.26-rc1 completely fails to boot on my laptop. The last line > > appearing on the console is: > > > > ACPI: Processor [CPU1] (supports 8 throttling states) > > Does booting with hpet=disable help?
No, 2.6.26-rc1 with hpet=disable now stops at
ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
However, with idle=mwait as suggested by Venkatesh Pallipadi it did boot in 2 out of 2 attempts.
> > > Kernel 2.6.25 fails to boot in an estimated 1 in 2 attempts. The last > > line on the console if this one fails is: > > > > ACPI: LNXTHERM:01 is registered as thermal_zone0 > > > > I did a git bisection with "fails to boot in the first three attempts" > > as the definition of "bad" between 2.6.26-rc1 and 2.6.25-rc3 which I > > believed to be free of this problem. The many reboots in the > > bisection process however showed me that 2.6.25-rc3 also has an > > estimated 1 in 10 chance of failing. Anyway, the bisection ended > > with: > > > > 8a3227268877b81096d7b7a841aaf51099ad2068 is first bad commit > > > > The bisection log and dmesg are attached. > > I have this boot problem since before 2.6.25-rc1 but it is > very difficult to do a bisection. Sometimes the probability > of hanging was 1:30 and what I thought was a good kernel in > fact was bad. > > In fact the commit you got is a "merge commit" which does not > change the source code so it is clearly bogus. > > Mark Lord points out that this bug comes and goes with slight > modifications in the .config, and in fact very recently > the probability of hanging changed dramatically for me. > > I have already booted the kernel afa26be86b65 (six commits > after 2.6.26-rc1) more than 30 times and it did not hang. > > You can also take a look at some discussion here: > http://bugzilla.kernel.org/show_bug.cgi?id=10117 >
Yes this definitely looks like the same problem.
> And good luck with this!
Thanks,
Henny
| |