From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Steven Gill <smgill75@verizon.net>, linux-ide@vger.kernel.org
Subject: Re: sata_mv (NOT!)
Date: Tue, 26 Aug 2008 10:14:43 -0400 [thread overview]
Message-ID: <48B40FD3.5040009@rtr.ca> (raw)
In-Reply-To: <48B4092E.3050907@rtr.ca>
Mark Lord wrote:
> Jeff Garzik wrote:
>> Mark Lord wrote:
>>>
>>> Yeah, it looks to me as if libata still has DVD burner issues.
>>> I used my SATA DVDRW drive to burn a Suse DVD the other day,
>>> and the same drive refused to read the burnt disc without first
>>> rebooting.
>>>
>>> linux-2.6.25.6
>>>
>>> Disc was fine, though. Single-layer.
>>
>> Do you get error messages as well? Of what kind?
> ..
>
> There have been so many broken things in so many parts of the kernel of
> late,
> that I'm just way too far behind in diagnosing/fixing them. Or
> reporting them,
> since many developers have stated they would rather not see a bug report
> without a bisect.
>
> But here's all that was in the logs for this particular bug.
> These messages appeared when trying to read the freshly burned DVD,
> both before and after eject/reinsert. A reboot cured it:
>
> [ 8209.473181] attempt to access beyond end of device
> [ 8209.473189] sr0: rw=0, want=68, limit=4
> [ 8209.487646] attempt to access beyond end of device
> [ 8209.487655] sr0: rw=0, want=5480256, limit=4
..
> [ 8209.514467] attempt to access beyond end of device
> [ 8209.514467] sr0: rw=0, want=68, limit=4
> [ 8209.514467] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
..
To hazard a guess at the problem here, I'd say that perhaps the media change
went undetected, and so sr_media_change() never got called.
I'm no longer even sure what would trigger that call.
Cheers
prev parent reply other threads:[~2008-08-26 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 22:47 sata_mv Steven Gill
2008-08-13 16:12 ` sata_mv (NOT!) Mark Lord
2008-08-20 5:20 ` Steven Gill
2008-08-21 22:05 ` Mark Lord
2008-08-22 5:17 ` Jeff Garzik
2008-08-26 13:46 ` Mark Lord
2008-08-26 14:14 ` Mark Lord [this message]
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=48B40FD3.5040009@rtr.ca \
--to=liml@rtr.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=smgill75@verizon.net \
/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).