From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 14310] [bisected] 2.6.31 regression sis5513 PIO Mode 0 hang
Date: Fri, 6 Nov 2009 12:51:51 GMT [thread overview]
Message-ID: <200911061251.nA6Cppke032145@demeter.kernel.org> (raw)
In-Reply-To: <bug-14310-11633@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=14310
--- Comment #8 from David S. Miller <davem@davemloft.net> 2009-11-06 12:51:46 ---
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Date: Thu, 5 Nov 2009 16:54:27 +0100
> The problem is that the change in the debug patch affects all host drivers
> and at this moment is not safe enough neither for -stable nor for -rc.
>
> Somebody needs to go and review all host drivers and their usage of ->media
> field for tuning logic present in ->set_pio_mode implementations first.
The drivers which do this are:
drivers/ide/alim15x3.c
drivers/ide/it8172.c
drivers/ide/it8213.c
drivers/ide/pdc202xx_old.c
drivers/ide/piix.c
drivers/ide/qd65xx.c
drivers/ide/sis5513.c
drivers/ide/slc90e66.c
While the majority of them seem to use it to decide whether to enable
prefetching or not, alim15x3.c uses the ->media value to decide
whether to turn on the ATA or the ATAPI FIFO.
I don't think it's safe to call ->set_pio_mode() until we actually
know the media type.
I suppose we could guard the prefetch/FIFO changes in these drivers
with a test like:
if (!(hwif->port_flags & IDE_PFLAG_PROBING))
or something like that.
But in this stage of the game, it's just too risky and reverting
the early PIO0 commit is the best way to go.
I'll do that now.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2009-11-06 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-03 2:52 [Bug 14310] New: [bisected] 2.6.31 regression sis5513 PIO Mode 0 hang bugzilla-daemon
2009-10-10 1:07 ` [Bug 14310] " bugzilla-daemon
2009-10-10 21:17 ` bugzilla-daemon
2009-10-23 18:32 ` bugzilla-daemon
2009-10-24 13:38 ` bugzilla-daemon
2009-10-24 13:39 ` bugzilla-daemon
2009-10-27 8:35 ` bugzilla-daemon
2009-11-05 15:54 ` Bartlomiej Zolnierkiewicz
2009-11-06 12:52 ` David Miller
2009-11-05 15:56 ` bugzilla-daemon
2009-11-06 12:51 ` bugzilla-daemon [this message]
2009-11-06 13:05 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2009-10-24 2:19 David Fries
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=200911061251.nA6Cppke032145@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@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.