From: Len Brown <lenb@kernel.org>
To: Danny ter Haar <dth@dth.net>
Cc: Gabriel C <nix.or.die@googlemail.com>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not:
Date: Mon, 30 Jul 2007 13:30:54 -0400 [thread overview]
Message-ID: <200707301330.54640.lenb@kernel.org> (raw)
In-Reply-To: <20070730025412.GA22888@dth.net>
On Sunday 29 July 2007 22:54, Danny ter Haar wrote:
> Quoting Gabriel C (nix.or.die@googlemail.com):
> > Now while we think is ACPI this should be easy for you to bisect.
> > This commit http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=39804b20f62532fa05c2a8c3e2d1ae551fd0327b
> > merged ACPI so this one should be your first bad one.
> > Maybe Len has some idea and you don't need to bisect :)
>
> Thanks to personal coaching of Gabriel i bisected the last few days.
>
> It looked like this was the cullprit:
>
> 22aadf8a07067644e101267ed5003043f2ad05bf is first bad commit
Please attach the output from acpidump to
http://bugzilla.kernel.org/show_bug.cgi?id=7880
We'll likely be able to tell from it if that patch
has any real effect on your system, or if you test
result was from some unrelated event.
Also, please test with CONFIG_X86_ACPI_CPUFREQ=n
to remove the acpi-cpufreq driver (and thus this patch)
from your kernel. If it still fails, then we know
that this driver (and this patch) are not related
to the failure.
> 2.6.23-rc1-git[1-6] all lockup solid after either direct or
> within a couple of minutes (less than 2) after reboot.
>
> They all run fine with "acpi=off" as boot argument.
Hmmm, okay, the "big hammer" works. Please see
if any of these smaller hammers work:
pnpacpi=off
acpi=noirq
notsc
thanks,
-Len
next prev parent reply other threads:[~2007-07-30 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070727193832.GA20289@dth.net>
[not found] ` <200707290142.53689.bzolnier@gmail.com>
[not found] ` <20070729012324.GA29723@dth.net>
[not found] ` <46ABFFE4.3060703@googlemail.com>
[not found] ` <20070729033030.GA24636@dth.net>
2007-07-29 3:54 ` ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not Gabriel C
2007-07-30 2:54 ` Update: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not: Danny ter Haar
2007-07-30 17:30 ` Len Brown [this message]
2007-07-31 1:10 ` Danny ter Haar
2007-07-31 4:00 ` Danny ter Haar
2007-07-31 14:30 ` Danny ter Haar
2007-08-01 0:44 ` Danny ter Haar
2007-08-01 20:03 ` Update: ACPI problems: 2.6.22-git17 working, 2.6.23-rc1* is not: (was ide not working) Danny ter Haar
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=200707301330.54640.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=bzolnier@gmail.com \
--cc=dth@dth.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
/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;
as well as URLs for NNTP newsgroup(s).