linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Luiz Fernando N. Capitulino" <lcapitulino@mandriva.com.br>
To: Quel Qun <kelk1@comcast.net>
Cc: Tejun Heo <htejun@gmail.com>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jeff Garzik <jeff@garzik.org>,
	linux-ide@vger.kernel.org, stable@kernel.org
Subject: Re: [PATCH] libata: implement BROKEN_HPA horkage and apply it to HDS724040KLSA80
Date: Wed, 8 Aug 2007 13:54:40 -0300	[thread overview]
Message-ID: <20070808135440.034ff452@localhost> (raw)
In-Reply-To: <080820071650.11586.46B9F45F0005906600002D422200761438CE05040A05@comcast.net>

Em Wed, 08 Aug 2007 16:50:39 +0000
kelk1@comcast.net (Quel Qun) escreveu:

|  -------------- Original message ----------------------
| From: Tejun Heo <htejun@gmail.com>
| > Luiz Fernando N. Capitulino wrote:
| > > Em Wed, 08 Aug 2007 11:21:08 +0900
| > > Tejun Heo <htejun@gmail.com> escreveu:
| > > 
| > > | Alan Cox wrote:
| > > | >>> I'd rather know what is going on here. A drive can legitimately
| > > | >>> support LBA48 and HPA and refuse READ_NATIVE_MAX_EXT.
| > > | >> READ_NATIVE_MAX_EXT is mandatory if HPA && LBA48, no
| > > | > 
| > > | > Ok the report in that thread is different. The offending Maxtor simply
| > > | > aborts the read_native_max_ext
| > > | 
| > > | I'll resend sans ata_id_has_hpa() change.  Does that sound okay?  I
| > > | don't really think we can do anything other than blacklisting it.
| > > 
| > >  Does that make your patch invalid or is it still ok?
| > 
| > You controller being ICH ahci, I don't think the chance of the
| > controller messing things up is pretty slim but, just in case, do you
| > have another SATA controller to cross check?  If not, can you put the
| > controller into IDE mode so that ata_piix can drive it and test whether
| > the problem persists?
| >
| Hi, 
| Unfortunately, I do not have any machine with a different controller. Whichever 
| I pick in the BIOS between ATA and AHCI, it seems that the drive is always 
| handled by the ahci module, and the boot process goes the exact same way.
| Is there a way to force the IDE mode?

 I can try it here, but maybe not today.

-- 
Luiz Fernando N. Capitulino

  reply	other threads:[~2007-08-08 16:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-08 16:50 [PATCH] libata: implement BROKEN_HPA horkage and apply it to HDS724040KLSA80 Quel Qun
2007-08-08 16:54 ` Luiz Fernando N. Capitulino [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-08-07  5:42 Tejun Heo
2007-08-07 14:51 ` Luiz Fernando N. Capitulino
2007-08-07 15:00   ` Tejun Heo
2007-08-07 15:04     ` Luiz Fernando N. Capitulino
2007-08-07 15:25 ` Alan Cox
2007-08-07 15:36   ` Tejun Heo
2007-08-07 15:47     ` Jeff Garzik
2007-08-07 16:57       ` Alan Cox
2007-08-07 16:52         ` Jeff Garzik
2007-08-07 16:53     ` Alan Cox
2007-08-07 16:53       ` Tejun Heo
2007-08-07 16:58     ` Alan Cox
2007-08-08  2:21       ` Tejun Heo
2007-08-08  9:35         ` Alan Cox
2007-08-08 13:23         ` Luiz Fernando N. Capitulino
2007-08-08 13:40           ` Tejun Heo
2007-08-07 18:46     ` Chuck Ebbert
2007-08-07 19:41       ` Alan Cox
2007-08-07 22:12     ` Alan Cox

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=20070808135440.034ff452@localhost \
    --to=lcapitulino@mandriva.com.br \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kelk1@comcast.net \
    --cc=linux-ide@vger.kernel.org \
    --cc=stable@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 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).