--- En date deÂ: Lun 24.1.11, Ozan ÃaÄlayan <ozan@xxxxxxxxxxxxx> a ÃcritÂ: > De: Ozan ÃaÄlayan <ozan@xxxxxxxxxxxxx> > Objet: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) > Ã: "Lionel Debroux" <lionel_debroux@xxxxxxxx> > Cc: linux-acpi@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, platform-driver-x86@xxxxxxxxxxxxxxx, rjw@xxxxxxx, colin.king@xxxxxxxxxxxxx > Date: Lundi 24 janvier 2011, 10h21 > Pazartesi 24 Ocak 2011 gÃnà (saat > 11:04:35) Lionel Debroux ÅunlarÄ yazmÄÅtÄ: > > > > --- En date de : Dim 23.1.11, Ozan ÃaÄlayan <ozan@xxxxxxxxxxxxx> > > a Ãcrit : > > > > > De: Ozan ÃaÄlayan <ozan@xxxxxxxxxxxxx> > > > Objet: Re: Common boot/shutdown issues with the > latest 2.6.37 (Mostly Asus laptops) > > > Ã: linux-acpi@xxxxxxxxxxxxxxx, > linux-kernel@xxxxxxxxxxxxxxx, > platform-driver-x86@xxxxxxxxxxxxxxx, > rjw@xxxxxxx, colin.king@xxxxxxxxxxxxx > > > Date: Dimanche 23 janvier 2011, 21h24 > > > On 23.01.2011 16:28, Ozan ÃaÄlayan > > > wrote: > > > > Hi, > > > > > > > > I'm getting a lot of bug reports about > hanging > > > boot/shutdowns on these > > > > days. > > > > > > > > Most of the affected hardware are ASUS > laptops. The > > > problem is that I > > > > don't have access to any of those > problematic laptops > > > and the users are > > > > not able at all to debug/bisect what is > going on. > > > However, I have > > > > collected dmesgs of good/bad boots, > acpidump, etc. > > > > > > > > Here are the current status: > > > > > > > > "Asus F50SV does not boot unless lapic is > passed" > > > > https://bugzilla.kernel.org/show_bug.cgi?id=26502 > > > > > > > > "Regression between 2.6.35-020635-rc1 and > > > 2.6.35-020635 breaks acpi > > > > support on Asus X71 laptop" > > > > https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/689796 > > > > > > > > "Asus N61JQ hangs at shutdown unless lapic > is passed" > > > > (Not reported upstream yet, I've only > downstream bug > > > report which is > > > > Turkish) > > > > http://bugs.pardus.org.tr/show_bug.cgi?id=15969 > > > > > > > > "Asus X61S does not boot unless acpi=off is > given" > > > > (Not reported upstream yet, I've only > downstream bug > > > report which is > > > > Turkish) > > > > http://bugs.pardus.org.tr/show_bug.cgi?id=16322 > > > > (I've told the reporter to try with nolapic, > it will > > > probably fix the > > > > issue but until confirmed acpi=off is the > only > > > solution. 2.6.36 was fine) > > > > > > > > I'll post more bugs in here as I've found > them. > > > > > > (CC'ing: Colin King from Canonical) > > > > > > Another one for Asus N90Sc which was booting fine > with > > > 10.04 > > > but fails to boot with 10.10: > > >ÂÂÂhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/653626 > > > > > > Seen that the issue mostly happens on Asus boxes, > it's > > > possible > > > that their firmwares are buggy but they were > > > booting/shutting down > > > correctly until a recent change in kernel. > > My ASUS F3Jv-AS022P (Core 2 Duo T7200, 2 GB RAM, BIOS > version > > 207) has trouble (read: it reboots within one second > of the > > vmlinuz being loaded) with recent kernels as well. > > > > While I haven't performed a full bisection yet (which > is why > > I didn't try reporting the problem until I saw this > thread), > > I have narrowed down the problem by compiling several > tagged > > versions: > > * 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. > Maybe rebooting immediately while booting > is a sign of another problem, I don't know. > > --- > Ozan ÃaÄlayan > TUBITAK/UEKAE - Pardus Linux > http://www.pardus.org.tr/eng Lionel. -- To unsubscribe from this list: send the line "unsubscribe platform-driver-x86" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
