Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Andreas Mohr <andi@lisas.de>
To: Tejun Heo <tj@kernel.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	michal@physics.ubc.ca,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Andreas Mohr <andi@lisas.de>
Subject: Re: [PATCH #upstream-fixes] ata_piix: save, use saved and restore IOCFG
Date: Fri, 2 Jan 2009 09:29:33 +0100	[thread overview]
Message-ID: <20090102082933.GA7881@rhlx01.hs-esslingen.de> (raw)
In-Reply-To: <495D8450.6070505@kernel.org>

Hi,

On Fri, Jan 02, 2009 at 12:04:48PM +0900, Tejun Heo wrote:
> Certain ACPI implementations mess up IOCFG on _STM making libata
> detect cable type incorrectly after a suspend/resume cycle.  This
> patch makes ata_piix save IOCFG on attach, use the saved value for
> things which aren't dynamic and restore it on detach so that the next
> driver also gets the BIOS initialized value.
> 
> This patch contains the following changes.
> 
> * makes ich_pata_cable_detect() use saved_iocfg.
> 
> * make piix_iocfg_bit18_quirk() take @host and use saved_iocfg.
> 
> * hpriv allocation moved upwards to save iocfg before doing anything
>   else.
> 
> This fixes bz#11879.  Andreas Mohr reported and diagnosed the problem.

I'm mighty unhappy ;-)

First, I still think prime cause was a weak disk implementation of Word 93
and not BIOS ACPI handling itself (bug #12202 is a PATA SSD, too!).
(unless one thinks that BIOS should know about SSD variants of PATA
and actively do special-case them itself)
Second, you've been keeping silent about the duplicate processing
for too long (I didn't know about it at all until marked duplicate),
thus nobody else could derive any hard facts from the doubled information.
Third, it was not just me who reported it, Carl Michal did >= 10 reports
in his bug.
Fourth, "bz#11879" may seem a precise indication, but when writing this
within Bugzilla instead of a plain "bug #11879", you probably won't have it
hyperlinked, thus I'd always prefer the usual writing. </nitpick>


Patch seems fine to me, thanks a helluva lot for your hard work!
(probably will test, later)

> Signed-off-by: Tejun Heo <tj@kernel.org>

Acked-by: Andreas Mohr <andi@lisas.de>

  reply	other threads:[~2009-01-02  8:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-02  3:04 [PATCH #upstream-fixes] ata_piix: save, use saved and restore IOCFG Tejun Heo
2009-01-02  8:29 ` Andreas Mohr [this message]
2009-01-02  8:49   ` Tejun Heo
2009-01-02  8:58     ` Andreas Mohr

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=20090102082933.GA7881@rhlx01.hs-esslingen.de \
    --to=andi@lisas.de \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=michal@physics.ubc.ca \
    --cc=tj@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