From: Jeff Garzik <jeff@garzik.org>
To: prx <root@cinatas.ath.cx>
Cc: linux-kernel@vger.kernel.org,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [2.6.17-rc6-mm1] Oops during sata_promise init
Date: Sat, 10 Jun 2006 13:03:16 -0400 [thread overview]
Message-ID: <448AFB54.3080006@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0606101715440.3135@cinatas.ath.cx>
prx wrote:
> Hi,
>
> sorry for my late answer.
>
> The hardware which Oopses due to the third (PATA) channel is:
> 02:0b.0 Mass storage controller: Promise Technology, Inc.
> PDC20575 (SATAII150 TX2plus) (rev 02)
>
> I know it's the PATA chan which fails because i commented the
> part discovering the third channel out, giving me a working
> system :)
OK, thanks.
So it sounds like either #upstream broke #promise-sata-pata, or simply a
bug got introduced into the only-used-in-mm-trees version of sata_promise.c.
I will look into it, but since Promise PATA-on-SATA support is still
highly experimental, I can't promise an immediate response. This isn't
something that is in 2.6.17-rc, or even something going into 2.6.18.
Jeff
parent reply other threads:[~2006-06-10 17:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.61.0606101715440.3135@cinatas.ath.cx>]
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=448AFB54.3080006@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@cinatas.ath.cx \
/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).