[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4D3FD00D.2040303@yahoo.fr>
Date: Wed, 26 Jan 2011 08:41:01 +0100
From: Lionel Debroux <lionel_debroux@...oo.fr>
To: Len Brown <lenb@...nel.org>
CC: Ozan Çağlayan <ozan@...dus.org.tr>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
platform-driver-x86@...r.kernel.org, rjw@...k.pl,
colin.king@...onical.com
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus
laptops)
>>>>> * 2.6.35 series: .4 and .6 boot successfully, .8 and .10 fail;
>>>>> * 2.6.36 series: -rc2 boots successfully, .1 fails;
>>>>> * 2.6.37 series: -rc4 fails.
>>>>
>>>> So it's probably a commit to the mainline tree which was picked
>>>> by 2.6.35 maintainer to the stable tree (probably it was CC'ed)
>>>> cause this.
>>>>
>>>> Does passing nolapic or acpi=off cures the issue?
>>> IIRC, I tested at least one of these, without improvement.
>>> I'll test again tonight, when I can physically access the
>>> computer.
>> None of nolapic, acpi=off, nolapic acpi=off enables 2.6.35.8 to
>> boot on my ASUS F3Jv-AS022P.
>> The kernel line is
>> kernel /boot/vmlinuz root=/dev/sda9 nomce vga=791 nomodeset
>> I've attached the 2.6.35.6 config.
>
> looks like you've bisected as far as:
> 2.6.35.6 good
> 2.6.35.8 bad
>
> can you try 2.6.35.7 and continue on to find which specific patch
> in .stable broke your machine?
The bisection between 2.6.35.6 and 2.6.35.8 is in progress, two steps
left and no good kernel found yet (?!)
Due to not having physical access to the computer during work time, I
won't be able to finish until tonight.
Regards,
Lionel.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists