From: "Richard Schütz" <r.schtz@t-online.de>
To: "Ozan Çağlayan" <ozan@pardus.org.tr>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, rjw@sisk.pl
Subject: Re: Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops)
Date: Sun, 23 Jan 2011 16:00:53 +0100 [thread overview]
Message-ID: <4D3C42A5.6060909@t-online.de> (raw)
In-Reply-To: <4D3C3B1E.1080500@pardus.org.tr>
> 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
next prev parent reply other threads:[~2011-01-23 15:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 14:28 Common boot/shutdown issues with the latest 2.6.37 (Mostly Asus laptops) Ozan Çağlayan
2011-01-23 15:00 ` Richard Schütz [this message]
2011-01-23 15:11 ` Gene Heskett
2011-01-23 16:49 ` Ozan Çağlayan
2011-01-23 16:56 ` Ozan Çağlayan
2011-01-23 20:24 ` Ozan Çağlayan
2011-01-24 9:00 ` Ozan Çağlayan
2011-01-24 9:04 ` Lionel Debroux
2011-01-24 9:21 ` Ozan Çağlayan
2011-01-24 9:47 ` Lionel Debroux
2011-01-24 20:14 ` Lionel Debroux
2011-01-25 2:56 ` Len Brown
2011-01-26 7:41 ` Lionel Debroux
2011-01-27 7:59 ` Lionel Debroux
2011-01-25 6:22 ` Ozan Çağlayan
2011-01-25 19:38 ` Rafael J. Wysocki
2011-01-25 19:45 ` Ozan Çağlayan
2011-01-25 19:54 ` Rafael J. Wysocki
2011-01-25 20:00 ` Ozan Çağlayan
2011-01-29 17:49 ` Ozan Çağlayan
2011-01-30 20:30 ` Ozan Çağlayan
2011-01-30 22:48 ` Rafael J. Wysocki
2011-01-31 8:53 ` Ozan Çağlayan
2011-01-31 9:50 ` Rafael J. Wysocki
2011-01-31 10:03 ` Ozan Çağlayan
2011-01-31 10:14 ` Rafael J. Wysocki
2011-01-31 10:20 ` Richard Schütz
2011-01-31 10:23 ` Rafael J. Wysocki
2011-01-31 10:29 ` Richard Schütz
2011-01-31 18:24 ` Rafael J. Wysocki
2011-01-31 18:29 ` Ozan Çağlayan
2011-01-31 18:33 ` Rafael J. Wysocki
2011-01-31 18:38 ` Ozan Çağlayan
2011-01-31 19:12 ` Rafael J. Wysocki
2011-01-31 20:35 ` Ozan Çağlayan
2011-01-31 20:42 ` Rafael J. Wysocki
2011-01-31 20:42 ` Ozan Çağlayan
2011-01-31 21:04 ` Ozan Çağlayan
2011-01-31 22:52 ` Rafael J. Wysocki
2011-02-03 21:10 ` Ozan Çağlayan
2011-02-03 22:04 ` Rafael J. Wysocki
2011-02-03 22:13 ` Ozan Çağlayan
2011-02-03 22:51 ` Rafael J. Wysocki
2011-02-04 6:44 ` Ozan Çağlayan
2011-02-04 20:36 ` Rafael J. Wysocki
2011-02-05 13:21 ` Ozan Çağlayan
2011-02-05 18:16 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D3C42A5.6060909@t-online.de \
--to=r.schtz@t-online.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ozan@pardus.org.tr \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox