From: Gabriel C <nix.or.die@googlemail.com>
To: Danny ter Haar <dth@dth.net>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-kernel@vger.kernel.org, len.brown@intel.com,
linux-acpi@vger.kernel.org
Subject: Re: ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not
Date: Sun, 29 Jul 2007 05:54:22 +0200 [thread overview]
Message-ID: <46AC0F6E.2000008@googlemail.com> (raw)
In-Reply-To: <20070729033030.GA24636@dth.net>
Danny ter Haar wrote:
[ added linux-acpi and Len to CC ]
> Quoting Gabriel C (nix.or.die@googlemail.com):
>> Maybe try to :
>> disable BSG ( maybe some leftover bug )
>> boot acpi=off ( that got merged kind late )
>
> My first git disected kernel wouldn't boot, but with
> acpi=off it would indeed boot!
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 :)
>
> As did the 2.6.23-rc1-git5 kernel...
>
> I will bisect further to find out exactly what patch is
> playing up in my particular setup.
>
> thanks for the tip! ;-)
You are welcome :)
>
> Danny
>
Gabriel
next prev parent reply other threads:[~2007-07-29 3:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 19:38 ide problems: 2.6.22-git17 working, 2.6.23-rc1* is not dth
2007-07-28 23:42 ` Bartlomiej Zolnierkiewicz
2007-07-29 0:30 ` Danny ter Haar
2007-07-29 1:23 ` Danny ter Haar
2007-07-29 2:48 ` Gabriel C
2007-07-29 3:30 ` Danny ter Haar
2007-07-29 3:54 ` Gabriel C [this message]
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
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=46AC0F6E.2000008@googlemail.com \
--to=nix.or.die@googlemail.com \
--cc=bzolnier@gmail.com \
--cc=dth@dth.net \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.