From: Robert Hancock <hancockr@shaw.ca>
To: Alexander <aledin@mail.ru>
Cc: linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>
Subject: Re: PROBLEM REMAINS: [sata_nv ADMA breaks ATAPI] Crash on accessing DVD-RAM
Date: Thu, 10 Jan 2008 23:46:47 -0600 [thread overview]
Message-ID: <478702C7.80401@shaw.ca> (raw)
In-Reply-To: <fa.krOVfyFmB2aqGjJIoHCLmQxecWc@ifi.uio.no>
Alexander wrote:
> Hello!
>
> The problem described at https://bugzilla.redhat.com/show_bug.cgi?id=351451 and
> at http://ubuntuforums.org/showthread.php?t=655772 and supposedly fixed by the
> patch http://kerneltrap.org/mailarchive/linux-kernel/2007/11/25/445094 is still
> there. I have compiled 2.6.24-rc7 kernel and booted my PC with it just to find
> out that my SATA DVD-RW is
There's this patch which was intended to fix it:
http://lkml.org/lkml/2007/11/22/148
which hasn't been merged yet. I see now that there was some further
discussion from someone saying that didn't fix the problem for them,
which I wasn't CCed on.. It looks like in their case, libata is
receiving SGs with DMA addresses above 4GB even though the block layer
bounce limit is set to 32-bit. That's the mechanism that sata_nv depends
on to ensure that it gets proper addresses when accessing ATAPI devices
where it is limited to 32-bit DMA.. Could that be breaking or
insufficient somehow?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2008-01-11 5:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.krOVfyFmB2aqGjJIoHCLmQxecWc@ifi.uio.no>
2008-01-11 5:46 ` Robert Hancock [this message]
2008-01-12 8:25 ` PROBLEM REMAINS: [sata_nv ADMA breaks ATAPI] Crash on accessing DVD-RAM Alexander
2008-01-12 19:25 ` Robert Hancock
2008-01-12 20:35 ` James Bottomley
2008-01-12 23:04 ` Robert Hancock
2008-01-12 23:27 ` James Bottomley
2008-01-13 1:38 ` Robert Hancock
2008-01-13 3:12 ` James Bottomley
2008-01-13 13:33 ` Alan Cox
2008-01-13 15:38 ` James Bottomley
2008-01-13 16:29 ` Alan Cox
2008-01-13 16:51 ` James Bottomley
2008-01-15 1:41 ` Robert Hancock
2008-01-15 2:23 ` James Bottomley
2008-02-01 0:09 ` Robert Hancock
2008-02-01 9:59 ` Alexander
2008-02-04 8:29 ` Alexander
2008-01-10 13:44 Alexander
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=478702C7.80401@shaw.ca \
--to=hancockr@shaw.ca \
--cc=aledin@mail.ru \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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.