linux-kernel - Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D3C42A5.6060909@t-online.de>
Date:	Sun, 23 Jan 2011 16:00:53 +0100
From:	Richard Schütz <r.schtz@...nline.de>
To:	Ozan Çağlayan <ozan@...dus.org.tr>
CC:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	platform-driver-x86@...r.kernel.org, rjw@...k.pl
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus
 laptops)

> 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.
>
> Thanks,
>

Looks like these are all Intel machines. Do they use intel_idle for the 
CPU powersaving features?
(cat /sys/devices/system/cpu/cpuidle/current_driver)

If yes - does booting with intel_idle.max_cstate=0 or 
intel_idle.max_cstate=3 boot parameter help?

It could be related to https://bugzilla.kernel.org/show_bug.cgi?id=21952 
somehow, which seems to be an 2.6.35 regression.

-- 
Regards,
Richard Schütz
--
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/