From: "Berck E. Nash" <flyboy@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot
Date: Tue, 25 Sep 2007 12:14:11 -0600 [thread overview]
Message-ID: <46F94FF3.1000400@gmail.com> (raw)
In-Reply-To: <46F8665A.4000206@garzik.org>
Jeff Garzik wrote:
> The first step would be to clone the "upstream" branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
>
> and see if the problem is reproducible there. If yes, then you have
> narrowed down the problem to something my ATA devel tree has introduced
> into -mm.
Nope, you're off the hook. The libata tree works great, so it must be
something else in -mm conflicting.
next prev parent reply other threads:[~2007-09-25 18:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 18:02 2.6.23-rc7-mm1 AHCI ATA errors -- won't boot Berck E. Nash
2007-09-25 1:37 ` Jeff Garzik
2007-09-25 18:14 ` Berck E. Nash [this message]
2007-09-25 18:21 ` Jens Axboe
2007-09-25 18:28 ` Berck E. Nash
2007-09-25 18:32 ` Jens Axboe
2007-09-25 19:29 ` Berck E. Nash
2007-09-25 20:40 ` Jeff Garzik
2007-09-25 22:07 ` Berck E. Nash
2007-09-25 22:46 ` Berck E. Nash
2007-09-26 1:21 ` Jeff Garzik
2007-09-26 2:25 ` Berck E. Nash
2007-09-26 2:33 ` Jeff Garzik
2007-09-26 4:40 ` Jeff Garzik
2007-09-26 10:03 ` Bernd Schmidt
2007-09-26 14:22 ` Berck E. Nash
2007-09-27 1:05 ` Tejun Heo
2007-09-26 14:19 ` Berck E. Nash
2007-10-03 21:18 ` Jeff Garzik
[not found] <fa.7B5oGGPZtkIAG9trDHdybt+z9Qg@ifi.uio.no>
[not found] ` <fa.lh2GEsFivC+TeMBqgRXU+5p7ySM@ifi.uio.no>
[not found] ` <fa.tqIC/0YXN2BDEJQ7WBFuJ0EEUrI@ifi.uio.no>
[not found] ` <fa.Q/HeymU0u7VpG+dN5Lc1DraTos0@ifi.uio.no>
2007-09-25 22:39 ` Robert Hancock
2007-09-26 1:10 ` Jeff Garzik
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=46F94FF3.1000400@gmail.com \
--to=flyboy@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=jeff@garzik.org \
--cc=linux-ide@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.