From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Jonathan Bagg <jbagg@lenbrook.com>, linux-ide@vger.kernel.org
Subject: Re: imx6 sata cdrom driver issue
Date: Fri, 24 Apr 2015 09:58:01 +0200 [thread overview]
Message-ID: <15678294.L2fz4hMtva@wuerfel> (raw)
In-Reply-To: <5539101D.1020909@lenbrook.com>
On Thursday 23 April 2015 11:30:37 Jonathan Bagg wrote:
> Spam Status: CRM114
> On arm imx6, running mainline 3.19, mounting a SATA CDROM fails aprox
> 1/20 times with this error....
>
> root@freescale /tmp$ mount /dev/sr0 test/
> UDF-fs: warning (device sr0): udf_fill_super: No partition found (2)
> mount: mounting /dev/sr0 on test/ failed: Invalid argument
>
> I've tried several disks and dvd drivers. They all experience this
> issue. The same disks mount 100% of the time on an x86 machine. Once
> mounted, I can read data without issue. Also tried a HDD on the same
> SATA link, no issue.
>
> Sometimes the kernel will dump out the attached backtrace on the mount
> command.
>
I think you have a combination of two bugs:
a) something that mount() does leads to the 'sd' device being unregistered
b) something goes wrong in the cleanup of that device, which leads to
the messages you see.
What is particularly strange here is the error about unregistering the
/disk/ rather than the cdrom.
Do you have two SATA ports on one controller, with the other one being
conneced to a disk drive?
My best guess is that something in the error handling of
drivers/ata/ahci_imx.c causes a reset of the entire bus and that
triggers the other bugs. Can you instrument that error handling to
see what's going on?
Arnd
next prev parent reply other threads:[~2015-04-24 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 15:30 imx6 sata cdrom driver issue Jonathan Bagg
2015-04-24 7:58 ` Arnd Bergmann [this message]
2015-05-04 16:15 ` Jonathan Bagg
[not found] ` <55439CA1.4030601@lenbrook.com>
2015-05-04 18:37 ` Arnd Bergmann
2015-05-04 21:03 ` Jonathan Bagg
2015-05-05 10:48 ` Arnd Bergmann
2015-05-08 19:45 ` Jonathan Bagg
2015-05-19 19:13 ` Jonathan Bagg
2015-05-19 19:18 ` Kevin Groeneveld
2015-05-28 19:16 ` Fabio Estevam
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=15678294.L2fz4hMtva@wuerfel \
--to=arnd@arndb.de \
--cc=jbagg@lenbrook.com \
--cc=linux-arm-kernel@lists.infradead.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 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).