From: "Tvrtko A. Ursulin" <tvrtko@ursulin.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: 2.6.26 DVD playing regression with libata
Date: Wed, 30 Jul 2008 07:57:29 +0100 [thread overview]
Message-ID: <200807300757.29520.tvrtko@ursulin.net> (raw)
In-Reply-To: <20080730002011.21947c32@lxorguk.ukuu.org.uk>
On Wednesday 30 July 2008 00:20:11 Alan Cox wrote:
> > Jul 29 21:10:03 media kernel: [353032.319013] sr 2:0:0:0: [sr0] unaligned
> > transfer Jul 29 21:10:03 media kernel: [353032.319013] sr 2:0:0:0: [sr0]
> > unaligned transfer
>
> This is coming from the scsi/block layer and definitely isn't good.
> Doesn't directly look like a libata bug but seems to be higher up the
> stack. What software is triggering this ?
I tried to reproduce it now but could not.
After a fresh boot into 2.6.26, I first tried mounting the DVD which was fine. Then I ran lsdvd which also worked and finally mplayer without any problems. In
contrast to that yesterday I ran my playdvd.pl (http://www.ursulin.net/2008/06/effectively-using-mplayer-within-mythtv/) script from within MythTV and it
exited immediately. It looked like either it triggered that failure without any delay or subsystem was already in that failure mode by simple DVD insertion.
When ran directly lsdvd would exit being unable to open /dev/dvd (/dev/scdo). Unfortunately I didn't debug it further at the time.
The only difference is that yesterday box had an uptime of couple of days while this morning it was completely fresh. Unless mounting the disc before
everything else somehow stabilised something. Hm let me do another reboot... no, still can't reproduce it.
One interesting thing, sometimes it detects drive capabilities like this:
[ 3.498951] sr0: scsi3-mmc drive: 62x/62x writer dvd-ram cd/rw xa/form2 cdda tray
And sometimes like this:
[ 3.514104] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
Later I think is correct according to drive datasheet.
I will keep 2.6.26 running and see if the problem comes back in following days.
Tvrtko
next prev parent reply other threads:[~2008-07-30 6:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 22:23 2.6.26 DVD playing regression with libata Tvrtko A. Ursulin
2008-07-29 23:20 ` Alan Cox
2008-07-30 6:57 ` Tvrtko A. Ursulin [this message]
2008-07-30 6:59 ` Justin Mattock
2008-07-30 7:08 ` Tvrtko A. Ursulin
2008-07-30 7:17 ` Justin Mattock
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=200807300757.29520.tvrtko@ursulin.net \
--to=tvrtko@ursulin.net \
--cc=alan@lxorguk.ukuu.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox