From: Fredrik Rinnestam <fredrik@obra.se>
To: linux-ide@vger.kernel.org
Subject: Re: SIL3512 lockup problem using driver verion 0.9 and Linux 2.6.14
Date: Sat, 3 Feb 2007 21:14:49 +0100 [thread overview]
Message-ID: <20070203201449.GA1222@useful.obra.se> (raw)
In-Reply-To: <457E040D.2020707@gmail.com>
> > ata1: command 0x35 timeout, stat 0xd1 host_stat 0x1
> > ata1: status=0xd1 { Busy }
> > sd 0:0:0:0: SCSI error: return code = 0x8000002
> > sda: Current: sense key=0xb
> > ASC=0x47 ASCQ=0x0
> > end_request: I/O error, dev sda, sector 17033103
> > ata1: Abnormal status 0xD1 on port 0xC001E087
> > ata1: Alternate status 0xD1 on port 0xC001E08A
> > ata1: Error 0xd1
> > ata1: Abnormal status 0xD1 on port 0xC001E087
> > ata1: Alternate status 0xD1 on port 0xC001E08A
> > ata1: Error 0xd1
> > ata1: Abnormal status 0xD1 on port 0xC001E087
> > ata1: Alternate status 0xD1 on port 0xC001E08A
>
> This is message from old error handling and doesn't really contain much
> useful info. Even if you have to use previous kernel in production
> system, providing error messages from 2.6.19 will help chasing down the
> cause.
>
> --
> tejun
I get very similar error-messages with my SiI 3512 controller. I just
noticed this while connecting a second drive and moving data from sdb to
sda. Copying stuff from the internal ide-controller (nvidia) to sda does
not produce any errors. I've also tried diffrent cables without any
luck. Kernel is 2.6.19.2
This is what dmesg pukes out:
EXT3 FS on sdb1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0
ata1.00: (BMDMA stat 0x60)
ata1.00: tag 0 cmd 0x35 Emask 0x1 stat 0x51 err 0x4 (device error)
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0
ata1.00: (BMDMA stat 0x60)
ata1.00: tag 0 cmd 0x35 Emask 0x1 stat 0x51 err 0x4 (device error)
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
ata1.00: (BMDMA stat 0x61)
ata1.00: tag 0 cmd 0x35 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd1)
ata1: port failed to respond (30 secs, Status 0xd1)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
ata1.00: (BMDMA stat 0x61)
ata1.00: tag 0 cmd 0x35 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd1)
ata1: port failed to respond (30 secs, Status 0xd1)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
ata1.00: (BMDMA stat 0x61)
ata1.00: tag 0 cmd 0x35 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd1)
ata1: port failed to respond (30 secs, Status 0xd1)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/100
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ata1.00: limiting speed to UDMA/66
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
ata1.00: (BMDMA stat 0x61)
ata1.00: tag 0 cmd 0x35 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd1)
ata1: port failed to respond (30 secs, Status 0xd1)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/66
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x0
ata1.00: (BMDMA stat 0x60)
ata1.00: tag 0 cmd 0x35 Emask 0x1 stat 0x51 err 0x4 (device error)
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ata1.00: limiting speed to UDMA/44
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
ata1.00: (BMDMA stat 0x61)
ata1.00: tag 0 cmd 0x35 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd1)
ata1: port failed to respond (30 secs, Status 0xd1)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/44
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
ata1.00: limiting speed to UDMA/33
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x2400000 action 0x2 frozen
ata1.00: (BMDMA stat 0x61)
ata1.00: tag 0 cmd 0x35 Emask 0x4 stat 0x40 err 0x0 (timeout)
ata1: port is slow to respond, please be patient (Status 0xd1)
ata1: port failed to respond (30 secs, Status 0xd1)
ata1: soft resetting port
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
ata1.00: configured for UDMA/33
ata1: EH complete
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
01:09.0 Mass storage controller: Silicon Image, Inc. SiI 3512
[SATALink/SATARaid] Serial ATA Controller (rev 01)
Subsystem: Silicon Image, Inc. SiI 3512 SATALink Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at c800 [size=8]
Region 1: I/O ports at cc00 [size=4]
Region 2: I/O ports at d000 [size=8]
Region 3: I/O ports at d400 [size=4]
Region 4: I/O ports at d800 [size=16]
Region 5: Memory at e3041000 (32-bit, non-prefetchable)
[size=512]
[virtual] Expansion ROM at 50000000 [disabled] [size=512K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
--
Fredrik Rinnestam
next prev parent reply other threads:[~2007-02-03 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 16:08 SIL3512 lockup problem using driver verion 0.9 and Linux 2.6.14 Steve Graham
2006-12-12 1:21 ` Tejun Heo
2006-12-30 18:53 ` Steve Graham
2007-02-03 20:14 ` Fredrik Rinnestam [this message]
2007-02-03 23:17 ` Fredrik Rinnestam
2007-02-06 7:34 ` Tejun Heo
2007-02-06 17:55 ` Fredrik Rinnestam
2007-02-12 1:03 ` Tejun Heo
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=20070203201449.GA1222@useful.obra.se \
--to=fredrik@obra.se \
--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).