Hello,

Harald Dunkel wrote:
> Hi Tejun,
> 
> Setting the timeout to 15 did not help, either :-(. All your patches
> are still in, of course.

Hmm... I'm out of ideas.  I'll try it when I get back home.

> May 10 22:15:55 pluto kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr
> 0x0 action 0x2 frozen
> May 10 22:15:55 pluto kernel: ata2.00: cmd
> a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0xad data 2052 in
> May 10 22:15:55 pluto kernel:          res
> 40/00:02:00:08:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
> May 10 22:15:55 pluto kernel: ata2: soft resetting port
> May 10 22:15:55 pluto kernel: CLASSIFY TF 00/01:01:01:14:eb/a0 <6>ata2:
> SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> May 10 22:15:55 pluto kernel: ata2.00: XXX: IDENTIFY
> May 10 22:15:55 pluto kernel: 00: 3b38 13ed f880 edbe  8013 bef8 13ed f880
[--snip--]
> May 10 22:15:55 pluto kernel: ata2.00: failed to IDENTIFY (device
> reports illegal type, err_mask=0x0)
> May 10 22:15:55 pluto kernel: ata2.00: revalidation failed (errno=-22)
> May 10 22:15:55 pluto kernel: ata2.00: limiting speed to UDMA/33:PIO3
> May 10 22:15:55 pluto kernel: ata2: failed to recover some devices,
> retrying in 5 secs
> May 10 22:16:00 pluto kernel: ata2: hard resetting port
> May 10 22:16:01 pluto kernel: CLASSIFY TF 00/01:01:01:14:eb/a0 <6>ata2:
> SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> May 10 22:16:01 pluto kernel: ata2.00: XXX: IDENTIFY
> May 10 22:16:01 pluto kernel: 00: 85c0 0000 0000 0000  0000 0000 0000 0000
[--snip--]
> May 10 22:16:01 pluto kernel: ata2.00: configured for UDMA/33
> May 10 22:16:01 pluto kernel: ata2: EH complete

Well, at least one thing worked.  I'll push the patch upstream soon.

Thanks.

-- 
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to