From: Tejun Heo <htejun@gmail.com>
To: Harri <harald.dunkel@t-online.de>
Cc: linux-ide@vger.kernel.org
Subject: Re: 2.6.24-rc1, sata_sil: access to SH-S183A broken again?
Date: Mon, 29 Oct 2007 11:54:31 +0900 [thread overview]
Message-ID: <47254B67.2050301@gmail.com> (raw)
In-Reply-To: <4724845D.4020903@t-online.de>
Harri wrote:
> Hi Tejun,
>
> Is it possible that the DMA workaround for sata_sil and the
> Samsung SH-S183A DVD writer was lost for 2.6.24-rc1? I found
No, I don't think we ever had workaround for sata_sil + SH-S183A
combination. Do you have any specific patch/commit in mind?
> this in syslog:
[--snip--]
> Oct 28 11:29:26 pluto kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr
> 0x0 action 0x2 frozen
> Oct 28 11:29:26 pluto kernel: ata4.00: cmd
> a0/01:00:00:10:00/00:00:00:00:00/a0 tag 0 cdb 0xa4 data 16 in
> Oct 28 11:29:26 pluto kernel: res
> 40/00:02:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> Oct 28 11:29:26 pluto kernel: ata4.00: status: { DRDY }
> Oct 28 11:29:27 pluto kernel: ata4: soft resetting link
> Oct 28 11:29:32 pluto kernel: ata4: port is slow to respond, please be
> patient (Status 0xf8)
> Oct 28 11:29:37 pluto kernel: ata4: SRST failed (errno=-16)
> Oct 28 11:29:37 pluto kernel: ata4: hard resetting link
> Oct 28 11:29:37 pluto kernel: ata4: SATA link up 1.5 Gbps (SStatus 113
> SControl 310)
> Oct 28 11:29:38 pluto kernel: ata4.00: configured for UDMA/33
> Oct 28 11:29:38 pluto kernel: ata4: EH complete
> Oct 28 11:29:38 pluto kernel: sr0: disc change detected.
>
> Its difficult to reproduce, though.
The failing command is REPORT_KEY. What were you doing when you saw
this error?
Not being reproducible indicates that it's unlikely to be a DMA issue
and more likely a temporary glitch in media recognition.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-10-29 2:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 12:45 2.6.24-rc1, sata_sil: access to SH-S183A broken again? Harri
2007-10-29 2:54 ` Tejun Heo [this message]
2007-10-29 9:22 ` Harri
2007-10-29 9:41 ` Tejun Heo
2007-10-30 7:52 ` Harald Dunkel
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=47254B67.2050301@gmail.com \
--to=htejun@gmail.com \
--cc=harald.dunkel@t-online.de \
--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 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.