From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jonas Lundgren <jonas@local.se>, Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: Scary Intel SATA problem: "frozen"
Date: Tue, 28 Nov 2006 18:22:45 -0500 [thread overview]
Message-ID: <456CC4C5.6090003@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0611281444330.4244@woody.osdl.org>
Linus Torvalds wrote:
> So maybe these _are_ related somehow, and my problem showed up because I
> actually had concurrent access to my DVD drive (some KDE media daemon
> checking to see if I inserted a music CD or something?). Jeff, Tejun, is
> there any reason to believe that the two channels on a PIIX ata controller
> are somehow "tied together" and it could be problematic for concurrent
> accesses?
I was sorta wondering in that direction too. If its in legacy mode
(PATA and SATA smushed together), that's a possibility. But native or
AHCI modes, the channels are pretty independent (which is the nature of
SATA).
Historical note: ata_piix is IMO more complicated than ahci, because
the silicon is emulating the PATA interface using an internal (probably
huge) state machine, converting PATA behavior to sending/receiving SATA
packets. There are classes of problems that just don't exist on ahci,
simply because we can directly talk to the sata phy, rather than having
to guess what the emulation state machine is doing.
Jeff
next prev parent reply other threads:[~2006-11-28 23:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 22:24 Scary Intel SATA problem: "frozen" Jonas Lundgren
2006-11-28 22:59 ` Linus Torvalds
2006-11-28 23:22 ` Jeff Garzik [this message]
2006-11-28 23:43 ` Linus Torvalds
2006-11-29 0:38 ` Jeff Garzik
2006-11-29 0:51 ` Linus Torvalds
2006-11-29 2:51 ` Mark Lord
2006-11-29 0:57 ` Tejun Heo
2006-11-29 7:14 ` Jonas Lundgren
2006-11-29 7:29 ` Tejun Heo
2006-11-29 14:11 ` Mark Lord
2006-11-29 16:19 ` Linus Torvalds
2006-12-06 17:58 ` Jonas Lundgren
2006-12-06 18:45 ` Andrew Lyon
2006-12-07 1:25 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 15:04 [git patches] libata fixes Jeff Garzik
2006-11-28 17:31 ` Scary Intel SATA problem: "frozen" Linus Torvalds
2006-11-28 17:37 ` Mark Lord
2006-11-28 17:55 ` Sergei Shtylyov
2006-11-28 20:12 ` Eric D. Mudama
2006-11-28 20:36 ` Sergei Shtylyov
2006-11-29 1:12 ` Tejun Heo
2006-11-28 18:05 ` Alan
2006-11-28 18:33 ` Linus Torvalds
2006-11-28 21:03 ` Jeff Garzik
2006-11-28 21:45 ` Linus Torvalds
2006-11-28 22:18 ` 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=456CC4C5.6090003@garzik.org \
--to=jeff@garzik.org \
--cc=htejun@gmail.com \
--cc=jonas@local.se \
--cc=linux-ide@vger.kernel.org \
--cc=torvalds@osdl.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.