* Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
@ 2009-07-22 2:10 KueiHuan Chen
2009-07-22 2:53 ` Mark Lord
0 siblings, 1 reply; 10+ messages in thread
From: KueiHuan Chen @ 2009-07-22 2:10 UTC (permalink / raw)
To: Mark Lord, Tejun Heo, saeed; +Cc: linux-ide
Dear Mark,
Sorry for the incorrect mail format, so i resent it again.
Here has a problem when we put the 7042 on the kirkwood
platform(6281). When system starting to build software raid 5,
sometimes it would meet the unable to stop eDMA problem in all
channels. And then whole system is being hang ... All the phy mode
value are also not correctly if we read it out at that time.
Could you please kindly have a look at the error messages and give
some advice for me to find out the root cause ? Thanks.
Thanks again.
-------------
ata4: Unable to stop eDMA
ata4.00: exception Emask 0x52 SAct 0x1f SErr 0xffffffff action 0xe frozen
ata4: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt
PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq
TrStaTrns UnrecFIS DevExch }
ata4.00: cmd 61/e0:00:c7:26:4f/01:00:01:00:00/40 tag 0 ncq 245760 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata4.00: status: { DRDY }
ata4.00: cmd 61/c8:08:cf:22:4f/03:00:01:00:00/40 tag 1 ncq 495616 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata4.00: status: { DRDY }
ata4.00: cmd 61/30:10:97:26:4f/00:00:01:00:00/40 tag 2 ncq 24576 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata4.00: status: { DRDY }
ata4.00: cmd 61/20:18:a7:28:4f/02:00:01:00:00/40 tag 3 ncq 278528 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata4.00: status: { DRDY }
ata4.00: cmd 61/00:20:c7:2a:4f/04:00:01:00:00/40 tag 4 ncq 524288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata4.00: status: { DRDY }
ata4: hard resetting link
ata1: Unable to stop eDMA
ata1.00: exception Emask 0x52 SAct 0x1fffff SErr 0xffffffff action 0xe frozen
ata1: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt
PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq
TrStaTrns UnrecFIS DevExch }
ata1.00: cmd 60/00:00:c7:2f:4f/01:00:01:00:00/40 tag 0 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:08:c7:30:4f/01:00:01:00:00/40 tag 1 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:10:c7:31:4f/01:00:01:00:00/40 tag 2 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:18:c7:32:4f/01:00:01:00:00/40 tag 3 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:20:c7:2e:4f/01:00:01:00:00/40 tag 4 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:28:c7:33:4f/01:00:01:00:00/40 tag 5 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:30:c7:34:4f/01:00:01:00:00/40 tag 6 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:38:c7:35:4f/01:00:01:00:00/40 tag 7 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:40:c7:36:4f/01:00:01:00:00/40 tag 8 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:48:c7:37:4f/01:00:01:00:00/40 tag 9 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:50:c7:38:4f/01:00:01:00:00/40 tag 10 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:58:c7:39:4f/01:00:01:00:00/40 tag 11 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:60:c7:3a:4f/01:00:01:00:00/40 tag 12 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:68:c7:3b:4f/01:00:01:00:00/40 tag 13 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:70:c7:3c:4f/01:00:01:00:00/40 tag 14 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:78:c7:3d:4f/01:00:01:00:00/40 tag 15 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:80:c7:3e:4f/01:00:01:00:00/40 tag 16 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:88:c7:3f:4f/01:00:01:00:00/40 tag 17 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:90:c7:40:4f/01:00:01:00:00/40 tag 18 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/00:98:c7:41:4f/01:00:01:00:00/40 tag 19 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1.00: cmd 60/08:a0:c7:42:4f/00:00:01:00:00/40 tag 20 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata1.00: status: { DRDY }
ata1: hard resetting link
ata2: Unable to stop eDMA
ata2.00: exception Emask 0x52 SAct 0x1fffff SErr 0xffffffff action 0xe frozen
ata2: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt
PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq
TrStaTrns UnrecFIS DevExch }
ata2.00: cmd 60/00:00:c7:2f:4f/01:00:01:00:00/40 tag 0 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:08:c7:30:4f/01:00:01:00:00/40 tag 1 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:10:c7:31:4f/01:00:01:00:00/40 tag 2 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:18:c7:32:4f/01:00:01:00:00/40 tag 3 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:20:c7:2e:4f/01:00:01:00:00/40 tag 4 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:28:c7:33:4f/01:00:01:00:00/40 tag 5 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:30:c7:34:4f/01:00:01:00:00/40 tag 6 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:38:c7:35:4f/01:00:01:00:00/40 tag 7 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:40:c7:36:4f/01:00:01:00:00/40 tag 8 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:48:c7:37:4f/01:00:01:00:00/40 tag 9 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:50:c7:38:4f/01:00:01:00:00/40 tag 10 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:58:c7:39:4f/01:00:01:00:00/40 tag 11 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:60:c7:3a:4f/01:00:01:00:00/40 tag 12 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:68:c7:3b:4f/01:00:01:00:00/40 tag 13 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:70:c7:3c:4f/01:00:01:00:00/40 tag 14 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:78:c7:3d:4f/01:00:01:00:00/40 tag 15 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:80:c7:3e:4f/01:00:01:00:00/40 tag 16 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:88:c7:3f:4f/01:00:01:00:00/40 tag 17 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:90:c7:40:4f/01:00:01:00:00/40 tag 18 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/00:98:c7:41:4f/01:00:01:00:00/40 tag 19 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2.00: cmd 60/08:a0:c7:42:4f/00:00:01:00:00/40 tag 20 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata2.00: status: { DRDY }
ata2: hard resetting link
ata3: Unable to stop eDMA
ata3.00: exception Emask 0x52 SAct 0x1fffff SErr 0xffffffff action 0xe frozen
ata3: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt
PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq
TrStaTrns UnrecFIS DevExch }
ata3.00: cmd 60/00:00:c7:2f:4f/01:00:01:00:00/40 tag 0 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:08:c7:30:4f/01:00:01:00:00/40 tag 1 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:10:c7:31:4f/01:00:01:00:00/40 tag 2 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:18:c7:32:4f/01:00:01:00:00/40 tag 3 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:20:c7:2e:4f/01:00:01:00:00/40 tag 4 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:28:c7:33:4f/01:00:01:00:00/40 tag 5 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:30:c7:34:4f/01:00:01:00:00/40 tag 6 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:38:c7:35:4f/01:00:01:00:00/40 tag 7 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:40:c7:36:4f/01:00:01:00:00/40 tag 8 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:48:c7:37:4f/01:00:01:00:00/40 tag 9 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:50:c7:38:4f/01:00:01:00:00/40 tag 10 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:58:c7:39:4f/01:00:01:00:00/40 tag 11 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:60:c7:3a:4f/01:00:01:00:00/40 tag 12 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:68:c7:3b:4f/01:00:01:00:00/40 tag 13 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:70:c7:3c:4f/01:00:01:00:00/40 tag 14 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:78:c7:3d:4f/01:00:01:00:00/40 tag 15 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:80:c7:3e:4f/01:00:01:00:00/40 tag 16 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:88:c7:3f:4f/01:00:01:00:00/40 tag 17 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:90:c7:40:4f/01:00:01:00:00/40 tag 18 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/00:98:c7:41:4f/01:00:01:00:00/40 tag 19 ncq 131072 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3.00: cmd 60/08:a0:c7:42:4f/00:00:01:00:00/40 tag 20 ncq 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
ata3.00: status: { DRDY }
ata3: hard resetting link
Best Regards,
KueiHuan-Chen
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-22 2:10 Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent) KueiHuan Chen
@ 2009-07-22 2:53 ` Mark Lord
2009-07-22 7:04 ` KueiHuan Chen
0 siblings, 1 reply; 10+ messages in thread
From: Mark Lord @ 2009-07-22 2:53 UTC (permalink / raw)
To: khchen; +Cc: Tejun Heo, saeed, linux-ide
KueiHuan Chen wrote:
> Dear Mark,
>
> Sorry for the incorrect mail format, so i resent it again.
>
> Here has a problem when we put the 7042 on the kirkwood
> platform(6281). When system starting to build software raid 5,
> sometimes it would meet the unable to stop eDMA problem in all
> channels. And then whole system is being hang ... All the phy mode
> value are also not correctly if we read it out at that time.
..
Are you using a discrete 7042 chip on a PCIe bus
along with a 6281 chip ??
Or are you simply using the built-in SATA controller inside the 6281 ?
In either event, Marvell did not deem to share *any* technical info
about the 6281 with me, so I really cannot help you.
Saeed Bishara from Marvell did everything to do with that chip.
> Could you please kindly have a look at the error messages and give
> some advice for me to find out the root cause ? Thanks.
>
> Thanks again.
> -------------
> ata4: Unable to stop eDMA
> ata4.00: exception Emask 0x52 SAct 0x1f SErr 0xffffffff action 0xe frozen
> ata4: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt
> PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq
> TrStaTrns UnrecFIS DevExch }
> ata4.00: cmd 61/e0:00:c7:26:4f/01:00:01:00:00/40 tag 0 ncq 245760 out
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x56 (ATA bus error)
..
I think the messages that happened before those above are the important ones,
and you did not show those messages here.
Cheers
--
Mark Lord
Real-Time Remedies Inc.
mlord@pobox.com
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-22 2:53 ` Mark Lord
@ 2009-07-22 7:04 ` KueiHuan Chen
2009-07-22 8:27 ` saeed bishara
0 siblings, 1 reply; 10+ messages in thread
From: KueiHuan Chen @ 2009-07-22 7:04 UTC (permalink / raw)
To: Mark Lord; +Cc: Tejun Heo, saeed, linux-ide
Dear Mark & Saeed,
2009/7/22 Mark Lord <mlord@pobox.com>:
>
> Are you using a discrete 7042 chip on a PCIe bus
> along with a 6281 chip ??
> Or are you simply using the built-in SATA controller inside the 6281 ?
>
We use a standalone 7042 chip on a PCIe bus with 6281 platform. And
we choose four channels from 7042 to build a software raid 5. We had
experimented that even though we disable the sata channels of 6281
soc, the problem is still remain.
> In either event, Marvell did not deem to share *any* technical info
> about the 6281 with me, so I really cannot help you.
>
> Saeed Bishara from Marvell did everything to do with that chip.
>
>
> ..
>
> I think the messages that happened before those above are the important
> ones,
> and you did not show those messages here.
There is no any messages before the "unable to disable eDMA". It
just freeze for a while and then output these messages. I had tried to
use the sata driver from Marvell BSP driver 4.2.2. The problem is the
same. The BSP are also cannot disable eDMA. Then we unmount this chip
from that board and remount it into the other platform(powerpc). It
works fine without any problem ... So we suspicion the problem may due
to 7042 work on 6281 platform.
If you have any ideas , please kindly tell us. We would try it !
Thanks!
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-22 7:04 ` KueiHuan Chen
@ 2009-07-22 8:27 ` saeed bishara
2009-07-22 11:56 ` KueiHuan Chen
0 siblings, 1 reply; 10+ messages in thread
From: saeed bishara @ 2009-07-22 8:27 UTC (permalink / raw)
To: khchen; +Cc: Mark Lord, Tejun Heo, saeed, linux-ide
Hi,
looks to me something wrong happened in PCIe link level, and any
register read ends up with 0xFFFFFFFF. can you please use devmem2 tool
and read any register (e.g. 0x22000) of the device?
also, can you test any other PCIe device?
does this issue happens when using the Marvell BSP 4.2.2?
saeed
On Wed, Jul 22, 2009 at 10:04 AM, KueiHuan Chen<kueihuan.chen@gmail.com> wrote:
> Dear Mark & Saeed,
>
> 2009/7/22 Mark Lord <mlord@pobox.com>:
>>
>> Are you using a discrete 7042 chip on a PCIe bus
>> along with a 6281 chip ??
>> Or are you simply using the built-in SATA controller inside the 6281 ?
>>
>
> We use a standalone 7042 chip on a PCIe bus with 6281 platform. And
> we choose four channels from 7042 to build a software raid 5. We had
> experimented that even though we disable the sata channels of 6281
> soc, the problem is still remain.
>
>> In either event, Marvell did not deem to share *any* technical info
>> about the 6281 with me, so I really cannot help you.
>>
>> Saeed Bishara from Marvell did everything to do with that chip.
>>
>>
>> ..
>>
>> I think the messages that happened before those above are the important
>> ones,
>> and you did not show those messages here.
>
> There is no any messages before the "unable to disable eDMA". It
> just freeze for a while and then output these messages. I had tried to
> use the sata driver from Marvell BSP driver 4.2.2. The problem is the
> same. The BSP are also cannot disable eDMA. Then we unmount this chip
> from that board and remount it into the other platform(powerpc). It
> works fine without any problem ... So we suspicion the problem may due
> to 7042 work on 6281 platform.
>
> If you have any ideas , please kindly tell us. We would try it !
>
> Thanks!
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-22 8:27 ` saeed bishara
@ 2009-07-22 11:56 ` KueiHuan Chen
2009-07-22 12:09 ` saeed bishara
0 siblings, 1 reply; 10+ messages in thread
From: KueiHuan Chen @ 2009-07-22 11:56 UTC (permalink / raw)
To: saeed bishara; +Cc: Mark Lord, Tejun Heo, saeed, linux-ide
Hi Saeed,
There is no any chance to read the PCIe register from user space.
Because when it happens, system is just like hang without any
response. The only chance is to modify it in the drivers. If you want
to see some special register, you can tell me, i would modify the
driver to print it out. Below is the last register information from
devmem2.
Sorry for we don't have other PCIe device to test. And this issue
would happens when using the Marvell BSP 4.2.2. The result is all the
same as sata_mv.c (Dead in deactivateEdma, keep looping with the
MV_SATA_UNRECOVERABLE_COMMUNICATION_ERROR event)
Thanks.
------------------
Value at address 0x22000 (0x40000000): 0x28126
Value at address 0x24000 (0x40000000): 0x41ED
Value at address 0x26000 (0x40000000): 0xE1A00000
Value at address 0x28000 (0x40000000): 0xE1A01008
------------------------
Value at address 0x22030 (0x40000030): 0x280D7
Value at address 0x24030 (0x40000030): 0x50803
Value at address 0x26030 (0x40000030): 0xEB09FE5F
Value at address 0x28030 (0x40000030): 0x12FFF10
... cannot deactivate Edma .. keep looping.
Best Regards,
KueiHuan-Chen
2009/7/22 saeed bishara <saeed.bishara@gmail.com>:
> Hi,
> looks to me something wrong happened in PCIe link level, and any
> register read ends up with 0xFFFFFFFF. can you please use devmem2 tool
> and read any register (e.g. 0x22000) of the device?
>
> also, can you test any other PCIe device?
>
> does this issue happens when using the Marvell BSP 4.2.2?
> saeed
>
> On Wed, Jul 22, 2009 at 10:04 AM, KueiHuan Chen<kueihuan.chen@gmail.com> wrote:
>> Dear Mark & Saeed,
>>
>> 2009/7/22 Mark Lord <mlord@pobox.com>:
>>>
>>> Are you using a discrete 7042 chip on a PCIe bus
>>> along with a 6281 chip ??
>>> Or are you simply using the built-in SATA controller inside the 6281 ?
>>>
>>
>> We use a standalone 7042 chip on a PCIe bus with 6281 platform. And
>> we choose four channels from 7042 to build a software raid 5. We had
>> experimented that even though we disable the sata channels of 6281
>> soc, the problem is still remain.
>>
>>> In either event, Marvell did not deem to share *any* technical info
>>> about the 6281 with me, so I really cannot help you.
>>>
>>> Saeed Bishara from Marvell did everything to do with that chip.
>>>
>>>
>>> ..
>>>
>>> I think the messages that happened before those above are the important
>>> ones,
>>> and you did not show those messages here.
>>
>> There is no any messages before the "unable to disable eDMA". It
>> just freeze for a while and then output these messages. I had tried to
>> use the sata driver from Marvell BSP driver 4.2.2. The problem is the
>> same. The BSP are also cannot disable eDMA. Then we unmount this chip
>> from that board and remount it into the other platform(powerpc). It
>> works fine without any problem ... So we suspicion the problem may due
>> to 7042 work on 6281 platform.
>>
>> If you have any ideas , please kindly tell us. We would try it !
>>
>> Thanks!
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-22 11:56 ` KueiHuan Chen
@ 2009-07-22 12:09 ` saeed bishara
2009-07-23 2:24 ` KueiHuan Chen
0 siblings, 1 reply; 10+ messages in thread
From: saeed bishara @ 2009-07-22 12:09 UTC (permalink / raw)
To: khchen; +Cc: Mark Lord, Tejun Heo, saeed, linux-ide
>
> Sorry for we don't have other PCIe device to test. And this issue
> would happens when using the Marvell BSP 4.2.2. The result is all the
> same as sata_mv.c (Dead in deactivateEdma, keep looping with the
> MV_SATA_UNRECOVERABLE_COMMUNICATION_ERROR event)
can you add stack_dump at this point?
>
> Thanks.
> ------------------
> Value at address 0x22000 (0x40000000): 0x28126
> Value at address 0x24000 (0x40000000): 0x41ED
> Value at address 0x26000 (0x40000000): 0xE1A00000
> Value at address 0x28000 (0x40000000): 0xE1A01008
> ------------------------
> Value at address 0x22030 (0x40000030): 0x280D7
> Value at address 0x24030 (0x40000030): 0x50803
> Value at address 0x26030 (0x40000030): 0xEB09FE5F
> Value at address 0x28030 (0x40000030): 0x12FFF10
I was looking for register at 0x22000 of the device, the physical
address should be the base address of the device (check /proc/iomem) +
0x22000.
>
> ... cannot deactivate Edma .. keep looping.
>
> Best Regards,
> KueiHuan-Chen
>
>
>
> 2009/7/22 saeed bishara <saeed.bishara@gmail.com>:
>> Hi,
>> looks to me something wrong happened in PCIe link level, and any
>> register read ends up with 0xFFFFFFFF. can you please use devmem2 tool
>> and read any register (e.g. 0x22000) of the device?
>>
>> also, can you test any other PCIe device?
>>
>> does this issue happens when using the Marvell BSP 4.2.2?
>> saeed
>>
>> On Wed, Jul 22, 2009 at 10:04 AM, KueiHuan Chen<kueihuan.chen@gmail.com> wrote:
>>> Dear Mark & Saeed,
>>>
>>> 2009/7/22 Mark Lord <mlord@pobox.com>:
>>>>
>>>> Are you using a discrete 7042 chip on a PCIe bus
>>>> along with a 6281 chip ??
>>>> Or are you simply using the built-in SATA controller inside the 6281 ?
>>>>
>>>
>>> We use a standalone 7042 chip on a PCIe bus with 6281 platform. And
>>> we choose four channels from 7042 to build a software raid 5. We had
>>> experimented that even though we disable the sata channels of 6281
>>> soc, the problem is still remain.
>>>
>>>> In either event, Marvell did not deem to share *any* technical info
>>>> about the 6281 with me, so I really cannot help you.
>>>>
>>>> Saeed Bishara from Marvell did everything to do with that chip.
>>>>
>>>>
>>>> ..
>>>>
>>>> I think the messages that happened before those above are the important
>>>> ones,
>>>> and you did not show those messages here.
>>>
>>> There is no any messages before the "unable to disable eDMA". It
>>> just freeze for a while and then output these messages. I had tried to
>>> use the sata driver from Marvell BSP driver 4.2.2. The problem is the
>>> same. The BSP are also cannot disable eDMA. Then we unmount this chip
>>> from that board and remount it into the other platform(powerpc). It
>>> works fine without any problem ... So we suspicion the problem may due
>>> to 7042 work on 6281 platform.
>>>
>>> If you have any ideas , please kindly tell us. We would try it !
>>>
>>> Thanks!
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-22 12:09 ` saeed bishara
@ 2009-07-23 2:24 ` KueiHuan Chen
2009-07-23 13:20 ` saeed bishara
0 siblings, 1 reply; 10+ messages in thread
From: KueiHuan Chen @ 2009-07-23 2:24 UTC (permalink / raw)
To: saeed bishara; +Cc: Mark Lord, Tejun Heo, saeed, linux-ide
Hi Saeed,
The result is same as what you guess, all register is ending with
FFFF. If there has any tip to work through this, please kindly let us
know.
Thanks.
---------------
#cat /proc/iomem
00000000-07ffffff : System RAM
00025000-0035ffff : Kernel text
00360000-003c4a0b : Kernel data
e8000000-efffffff : PEX Memory
e8000000-e80fffff : 0000:00:01.0
e8000000-e80fffff : mvSata
f1012000-f10120ff : serial8250.0
f1012000-f101201f : serial
f1012100-f101211f : serial
f10a0000-f10a3fff : mv88fx_snd
f8000000-f83fffff : physmap-flash.0
f8000000-f83fffff : physmap-flash.0
Strating to build software raid5 and execute devmem2.
Value at address 0xE8022000 (0x40000000): 0xC2213E
Value at address 0xE8024000 (0x40000000): 0xC2213E
Value at address 0xE8026000 (0x40000000): 0xC2213E
Value at address 0xE8028000 (0x40000000): 0xC2213E
------------------------
Value at address 0xE8022030 (0x40000030): 0xFE
Value at address 0xE8024030 (0x40000030): 0xE8
Value at address 0xE8026030 (0x40000030): 0xE2
Value at address 0xE8028030 (0x40000030): 0xC4
=======repeate
Value at address 0xE8022000 (0x40000000): 0xC2213E
Value at address 0xE8024000 (0x40000000): 0xC2213E
Value at address 0xE8026000 (0x40000000): 0xC2213E
Value at address 0xE8028000 (0x40000000): 0xC2213E
------------------------
Value at address 0xE8022030 (0x40000030): 0xF9
Value at address 0xE8024030 (0x40000030): 0xED
Value at address 0xE8026030 (0x40000030): 0xF7
Value at address 0xE8028030 (0x40000030): 0xD8
=======repeate
Value at address 0xE8022000 (0x40000000): 0xC2213E
Value at address 0xE8024000 (0x40000000): 0xC2213E
Value at address 0xE8026000 (0x40000000): 0xC2213E
Value at address 0xE8028000 (0x40000000): 0xC2213E
------------------------
Value at address 0xE8022030 (0x40000030): 0xE1
Value at address 0xE8024030 (0x40000030): 0xC17B
Value at address 0xE8026030 (0x40000030): 0xE5
Value at address 0xE8028030 (0x40000030): 0xCC
=======repeate
Value at address 0xE8022000 (0x40000000): 0xFFFFFFFF
Value at address 0xE8024000 (0x40000000): 0xFFFFFFFF
Value at address 0xE8026000 (0x40000000): 0xFFFFFFFF
Value at address 0xE8028000 (0x40000000): 0xFFFFFFFF
------------------------
Value at address 0xE8022030 (0x40000030): 0xFFFFFFFF
Value at address 0xE8024030 (0x40000030): 0xFFFFFFFF
Value at address 0xE8026030 (0x40000030): 0xFFFFFFFF
Value at address 0xE8028030 (0x40000030): 0xFFFFFFFF
=======repeate
Value at address 0xE8022000 (0x40000000): 0xFFFFFFFF
Value at address 0xE8024000 (0x40000000): 0xFFFFFFFF
Value at address 0xE8026000 (0x40000000): 0xFFFFFFFF
Value at address 0xE8028000 (0x40000000): 0xFFFFFFFF
------------------------
Value at address 0xE8022030 (0x40000030): 0xFFFFFFFF
Value at address 0xE8024030 (0x40000030): 0xFFFFFFFF
Value at address 0xE8026030 (0x40000030): 0xFFFFFFFF
Value at address 0xE8028030 (0x40000030): 0xFFFFFFFF
...
first time call trace
WARNING: at drivers/ata/mvSata_4_2_2/CoreDriver/mvSata.c:4811 deactivateEdma()
[<c002a99c>] (dump_stack+0x0/0x14) from [<c01f8dcc>] (deactivateEdma+0x7c/0xec)
[<c01f8d50>] (deactivateEdma+0x0/0xec) from [<c01f8e6c>]
(mvSataDisableChannelDma+0x30/0x40)
[<c01f8e3c>] (mvSataDisableChannelDma+0x0/0x40) from [<c01ec54c>]
(mv_ial_ht_abort+0x48/0xe0)
[<c01ec504>] (mv_ial_ht_abort+0x0/0xe0) from [<c01bd394>]
(__scsi_try_to_abort_cmd+0x2c/0x34)
r7:c775c000 r6:c77cb800 r5:c7fe8200 r4:c77c93c0
[<c01bd368>] (__scsi_try_to_abort_cmd+0x0/0x34) from [<c01be938>]
(scsi_error_handler+0x128/0x2f4)
[<c01be810>] (scsi_error_handler+0x0/0x2f4) from [<c0069fc4>]
(kthread+0x54/0x80)
r7:00000000 r6:00000000 r5:c01be810 r4:c77cb800
[<c0069f70>] (kthread+0x0/0x80) from [<c0059894>] (do_exit+0x0/0x6f8)
r5:00000000 r4:00000000
second time call trace
WARNING: at drivers/ata/mvSata_4_2_2/CoreDriver/mvSata.c:4811 deactivateEdma()
[<c002a99c>] (dump_stack+0x0/0x14) from [<c01f8dcc>] (deactivateEdma+0x7c/0xec)
[<c01f8d50>] (deactivateEdma+0x0/0xec) from [<c01f8e6c>]
(mvSataDisableChannelDma+0x30/0x40)
[<c01f8e3c>] (mvSataDisableChannelDma+0x0/0x40) from [<c01ef8a4>]
(mvRestartChannel+0xa4/0x108)
[<c01ef800>] (mvRestartChannel+0x0/0x108) from [<c01ec584>]
(mv_ial_ht_abort+0x80/0xe0)
[<c01ec504>] (mv_ial_ht_abort+0x0/0xe0) from [<c01bd394>]
(__scsi_try_to_abort_cmd+0x2c/0x34)
r7:c775c000 r6:c77cb800 r5:c7fe8200 r4:c77c93c0
[<c01bd368>] (__scsi_try_to_abort_cmd+0x0/0x34) from [<c01be938>]
(scsi_error_handler+0x128/0x2f4)
[<c01be810>] (scsi_error_handler+0x0/0x2f4) from [<c0069fc4>]
(kthread+0x54/0x80)
r7:00000000 r6:00000000 r5:c01be810 r4:c77cb800
[<c0069f70>] (kthread+0x0/0x80) from [<c0059894>] (do_exit+0x0/0x6f8)
r5:00000000 r4:00000000
0 3: deactivateEdma: Edma Failed (EDMA status = ffffffff)
... loop ..
Best Regards,
KueiHuan-Chen
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-23 2:24 ` KueiHuan Chen
@ 2009-07-23 13:20 ` saeed bishara
2009-07-23 13:23 ` saeed bishara
0 siblings, 1 reply; 10+ messages in thread
From: saeed bishara @ 2009-07-23 13:20 UTC (permalink / raw)
To: khchen; +Cc: Mark Lord, Tejun Heo, saeed, linux-ide
The stack tells that a command has been timed out. again, I think i
On Thu, Jul 23, 2009 at 5:24 AM, KueiHuan Chen<kueihuan.chen@gmail.com> wrote:
> Hi Saeed,
>
> The result is same as what you guess, all register is ending with
> FFFF. If there has any tip to work through this, please kindly let us
> know.
>
> Thanks.
> ---------------
> #cat /proc/iomem
> 00000000-07ffffff : System RAM
> 00025000-0035ffff : Kernel text
> 00360000-003c4a0b : Kernel data
> e8000000-efffffff : PEX Memory
> e8000000-e80fffff : 0000:00:01.0
> e8000000-e80fffff : mvSata
> f1012000-f10120ff : serial8250.0
> f1012000-f101201f : serial
> f1012100-f101211f : serial
> f10a0000-f10a3fff : mv88fx_snd
> f8000000-f83fffff : physmap-flash.0
> f8000000-f83fffff : physmap-flash.0
>
>
> Strating to build software raid5 and execute devmem2.
> Value at address 0xE8022000 (0x40000000): 0xC2213E
> Value at address 0xE8024000 (0x40000000): 0xC2213E
> Value at address 0xE8026000 (0x40000000): 0xC2213E
> Value at address 0xE8028000 (0x40000000): 0xC2213E
> ------------------------
> Value at address 0xE8022030 (0x40000030): 0xFE
> Value at address 0xE8024030 (0x40000030): 0xE8
> Value at address 0xE8026030 (0x40000030): 0xE2
> Value at address 0xE8028030 (0x40000030): 0xC4
> =======repeate
> Value at address 0xE8022000 (0x40000000): 0xC2213E
> Value at address 0xE8024000 (0x40000000): 0xC2213E
> Value at address 0xE8026000 (0x40000000): 0xC2213E
> Value at address 0xE8028000 (0x40000000): 0xC2213E
> ------------------------
> Value at address 0xE8022030 (0x40000030): 0xF9
> Value at address 0xE8024030 (0x40000030): 0xED
> Value at address 0xE8026030 (0x40000030): 0xF7
> Value at address 0xE8028030 (0x40000030): 0xD8
> =======repeate
> Value at address 0xE8022000 (0x40000000): 0xC2213E
> Value at address 0xE8024000 (0x40000000): 0xC2213E
> Value at address 0xE8026000 (0x40000000): 0xC2213E
> Value at address 0xE8028000 (0x40000000): 0xC2213E
> ------------------------
> Value at address 0xE8022030 (0x40000030): 0xE1
> Value at address 0xE8024030 (0x40000030): 0xC17B
> Value at address 0xE8026030 (0x40000030): 0xE5
> Value at address 0xE8028030 (0x40000030): 0xCC
> =======repeate
> Value at address 0xE8022000 (0x40000000): 0xFFFFFFFF
> Value at address 0xE8024000 (0x40000000): 0xFFFFFFFF
> Value at address 0xE8026000 (0x40000000): 0xFFFFFFFF
> Value at address 0xE8028000 (0x40000000): 0xFFFFFFFF
> ------------------------
> Value at address 0xE8022030 (0x40000030): 0xFFFFFFFF
> Value at address 0xE8024030 (0x40000030): 0xFFFFFFFF
> Value at address 0xE8026030 (0x40000030): 0xFFFFFFFF
> Value at address 0xE8028030 (0x40000030): 0xFFFFFFFF
> =======repeate
> Value at address 0xE8022000 (0x40000000): 0xFFFFFFFF
> Value at address 0xE8024000 (0x40000000): 0xFFFFFFFF
> Value at address 0xE8026000 (0x40000000): 0xFFFFFFFF
> Value at address 0xE8028000 (0x40000000): 0xFFFFFFFF
> ------------------------
> Value at address 0xE8022030 (0x40000030): 0xFFFFFFFF
> Value at address 0xE8024030 (0x40000030): 0xFFFFFFFF
> Value at address 0xE8026030 (0x40000030): 0xFFFFFFFF
> Value at address 0xE8028030 (0x40000030): 0xFFFFFFFF
> ...
>
> first time call trace
> WARNING: at drivers/ata/mvSata_4_2_2/CoreDriver/mvSata.c:4811 deactivateEdma()
> [<c002a99c>] (dump_stack+0x0/0x14) from [<c01f8dcc>] (deactivateEdma+0x7c/0xec)
> [<c01f8d50>] (deactivateEdma+0x0/0xec) from [<c01f8e6c>]
> (mvSataDisableChannelDma+0x30/0x40)
> [<c01f8e3c>] (mvSataDisableChannelDma+0x0/0x40) from [<c01ec54c>]
> (mv_ial_ht_abort+0x48/0xe0)
> [<c01ec504>] (mv_ial_ht_abort+0x0/0xe0) from [<c01bd394>]
> (__scsi_try_to_abort_cmd+0x2c/0x34)
> r7:c775c000 r6:c77cb800 r5:c7fe8200 r4:c77c93c0
> [<c01bd368>] (__scsi_try_to_abort_cmd+0x0/0x34) from [<c01be938>]
> (scsi_error_handler+0x128/0x2f4)
> [<c01be810>] (scsi_error_handler+0x0/0x2f4) from [<c0069fc4>]
> (kthread+0x54/0x80)
> r7:00000000 r6:00000000 r5:c01be810 r4:c77cb800
> [<c0069f70>] (kthread+0x0/0x80) from [<c0059894>] (do_exit+0x0/0x6f8)
> r5:00000000 r4:00000000
>
> second time call trace
> WARNING: at drivers/ata/mvSata_4_2_2/CoreDriver/mvSata.c:4811 deactivateEdma()
> [<c002a99c>] (dump_stack+0x0/0x14) from [<c01f8dcc>] (deactivateEdma+0x7c/0xec)
> [<c01f8d50>] (deactivateEdma+0x0/0xec) from [<c01f8e6c>]
> (mvSataDisableChannelDma+0x30/0x40)
> [<c01f8e3c>] (mvSataDisableChannelDma+0x0/0x40) from [<c01ef8a4>]
> (mvRestartChannel+0xa4/0x108)
> [<c01ef800>] (mvRestartChannel+0x0/0x108) from [<c01ec584>]
> (mv_ial_ht_abort+0x80/0xe0)
> [<c01ec504>] (mv_ial_ht_abort+0x0/0xe0) from [<c01bd394>]
> (__scsi_try_to_abort_cmd+0x2c/0x34)
> r7:c775c000 r6:c77cb800 r5:c7fe8200 r4:c77c93c0
> [<c01bd368>] (__scsi_try_to_abort_cmd+0x0/0x34) from [<c01be938>]
> (scsi_error_handler+0x128/0x2f4)
> [<c01be810>] (scsi_error_handler+0x0/0x2f4) from [<c0069fc4>]
> (kthread+0x54/0x80)
> r7:00000000 r6:00000000 r5:c01be810 r4:c77cb800
> [<c0069f70>] (kthread+0x0/0x80) from [<c0059894>] (do_exit+0x0/0x6f8)
> r5:00000000 r4:00000000
> 0 3: deactivateEdma: Edma Failed (EDMA status = ffffffff)
>
> ... loop ..
> Best Regards,
> KueiHuan-Chen
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-23 13:20 ` saeed bishara
@ 2009-07-23 13:23 ` saeed bishara
2009-07-23 14:42 ` KueiHuan Chen
0 siblings, 1 reply; 10+ messages in thread
From: saeed bishara @ 2009-07-23 13:23 UTC (permalink / raw)
To: khchen; +Cc: Mark Lord, Tejun Heo, saeed, linux-ide
sorry, my previous email was sent mistakenly before I completed it.
I think you have pcie link issue here, I think it's very likely a hw
issue in your board.
saeed
On Thu, Jul 23, 2009 at 4:20 PM, saeed bishara<saeed.bishara@gmail.com> wrote:
> The stack tells that a command has been timed out. again, I think i
>
> On Thu, Jul 23, 2009 at 5:24 AM, KueiHuan Chen<kueihuan.chen@gmail.com> wrote:
>> Hi Saeed,
>>
>> The result is same as what you guess, all register is ending with
>> FFFF. If there has any tip to work through this, please kindly let us
>> know.
>>
>> Thanks.
>> ---------------
>> #cat /proc/iomem
>> 00000000-07ffffff : System RAM
>> 00025000-0035ffff : Kernel text
>> 00360000-003c4a0b : Kernel data
>> e8000000-efffffff : PEX Memory
>> e8000000-e80fffff : 0000:00:01.0
>> e8000000-e80fffff : mvSata
>> f1012000-f10120ff : serial8250.0
>> f1012000-f101201f : serial
>> f1012100-f101211f : serial
>> f10a0000-f10a3fff : mv88fx_snd
>> f8000000-f83fffff : physmap-flash.0
>> f8000000-f83fffff : physmap-flash.0
>>
>>
>> Strating to build software raid5 and execute devmem2.
>> Value at address 0xE8022000 (0x40000000): 0xC2213E
>> Value at address 0xE8024000 (0x40000000): 0xC2213E
>> Value at address 0xE8026000 (0x40000000): 0xC2213E
>> Value at address 0xE8028000 (0x40000000): 0xC2213E
>> ------------------------
>> Value at address 0xE8022030 (0x40000030): 0xFE
>> Value at address 0xE8024030 (0x40000030): 0xE8
>> Value at address 0xE8026030 (0x40000030): 0xE2
>> Value at address 0xE8028030 (0x40000030): 0xC4
>> =======repeate
>> Value at address 0xE8022000 (0x40000000): 0xC2213E
>> Value at address 0xE8024000 (0x40000000): 0xC2213E
>> Value at address 0xE8026000 (0x40000000): 0xC2213E
>> Value at address 0xE8028000 (0x40000000): 0xC2213E
>> ------------------------
>> Value at address 0xE8022030 (0x40000030): 0xF9
>> Value at address 0xE8024030 (0x40000030): 0xED
>> Value at address 0xE8026030 (0x40000030): 0xF7
>> Value at address 0xE8028030 (0x40000030): 0xD8
>> =======repeate
>> Value at address 0xE8022000 (0x40000000): 0xC2213E
>> Value at address 0xE8024000 (0x40000000): 0xC2213E
>> Value at address 0xE8026000 (0x40000000): 0xC2213E
>> Value at address 0xE8028000 (0x40000000): 0xC2213E
>> ------------------------
>> Value at address 0xE8022030 (0x40000030): 0xE1
>> Value at address 0xE8024030 (0x40000030): 0xC17B
>> Value at address 0xE8026030 (0x40000030): 0xE5
>> Value at address 0xE8028030 (0x40000030): 0xCC
>> =======repeate
>> Value at address 0xE8022000 (0x40000000): 0xFFFFFFFF
>> Value at address 0xE8024000 (0x40000000): 0xFFFFFFFF
>> Value at address 0xE8026000 (0x40000000): 0xFFFFFFFF
>> Value at address 0xE8028000 (0x40000000): 0xFFFFFFFF
>> ------------------------
>> Value at address 0xE8022030 (0x40000030): 0xFFFFFFFF
>> Value at address 0xE8024030 (0x40000030): 0xFFFFFFFF
>> Value at address 0xE8026030 (0x40000030): 0xFFFFFFFF
>> Value at address 0xE8028030 (0x40000030): 0xFFFFFFFF
>> =======repeate
>> Value at address 0xE8022000 (0x40000000): 0xFFFFFFFF
>> Value at address 0xE8024000 (0x40000000): 0xFFFFFFFF
>> Value at address 0xE8026000 (0x40000000): 0xFFFFFFFF
>> Value at address 0xE8028000 (0x40000000): 0xFFFFFFFF
>> ------------------------
>> Value at address 0xE8022030 (0x40000030): 0xFFFFFFFF
>> Value at address 0xE8024030 (0x40000030): 0xFFFFFFFF
>> Value at address 0xE8026030 (0x40000030): 0xFFFFFFFF
>> Value at address 0xE8028030 (0x40000030): 0xFFFFFFFF
>> ...
>>
>> first time call trace
>> WARNING: at drivers/ata/mvSata_4_2_2/CoreDriver/mvSata.c:4811 deactivateEdma()
>> [<c002a99c>] (dump_stack+0x0/0x14) from [<c01f8dcc>] (deactivateEdma+0x7c/0xec)
>> [<c01f8d50>] (deactivateEdma+0x0/0xec) from [<c01f8e6c>]
>> (mvSataDisableChannelDma+0x30/0x40)
>> [<c01f8e3c>] (mvSataDisableChannelDma+0x0/0x40) from [<c01ec54c>]
>> (mv_ial_ht_abort+0x48/0xe0)
>> [<c01ec504>] (mv_ial_ht_abort+0x0/0xe0) from [<c01bd394>]
>> (__scsi_try_to_abort_cmd+0x2c/0x34)
>> r7:c775c000 r6:c77cb800 r5:c7fe8200 r4:c77c93c0
>> [<c01bd368>] (__scsi_try_to_abort_cmd+0x0/0x34) from [<c01be938>]
>> (scsi_error_handler+0x128/0x2f4)
>> [<c01be810>] (scsi_error_handler+0x0/0x2f4) from [<c0069fc4>]
>> (kthread+0x54/0x80)
>> r7:00000000 r6:00000000 r5:c01be810 r4:c77cb800
>> [<c0069f70>] (kthread+0x0/0x80) from [<c0059894>] (do_exit+0x0/0x6f8)
>> r5:00000000 r4:00000000
>>
>> second time call trace
>> WARNING: at drivers/ata/mvSata_4_2_2/CoreDriver/mvSata.c:4811 deactivateEdma()
>> [<c002a99c>] (dump_stack+0x0/0x14) from [<c01f8dcc>] (deactivateEdma+0x7c/0xec)
>> [<c01f8d50>] (deactivateEdma+0x0/0xec) from [<c01f8e6c>]
>> (mvSataDisableChannelDma+0x30/0x40)
>> [<c01f8e3c>] (mvSataDisableChannelDma+0x0/0x40) from [<c01ef8a4>]
>> (mvRestartChannel+0xa4/0x108)
>> [<c01ef800>] (mvRestartChannel+0x0/0x108) from [<c01ec584>]
>> (mv_ial_ht_abort+0x80/0xe0)
>> [<c01ec504>] (mv_ial_ht_abort+0x0/0xe0) from [<c01bd394>]
>> (__scsi_try_to_abort_cmd+0x2c/0x34)
>> r7:c775c000 r6:c77cb800 r5:c7fe8200 r4:c77c93c0
>> [<c01bd368>] (__scsi_try_to_abort_cmd+0x0/0x34) from [<c01be938>]
>> (scsi_error_handler+0x128/0x2f4)
>> [<c01be810>] (scsi_error_handler+0x0/0x2f4) from [<c0069fc4>]
>> (kthread+0x54/0x80)
>> r7:00000000 r6:00000000 r5:c01be810 r4:c77cb800
>> [<c0069f70>] (kthread+0x0/0x80) from [<c0059894>] (do_exit+0x0/0x6f8)
>> r5:00000000 r4:00000000
>> 0 3: deactivateEdma: Edma Failed (EDMA status = ffffffff)
>>
>> ... loop ..
>> Best Regards,
>> KueiHuan-Chen
>>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent)
2009-07-23 13:23 ` saeed bishara
@ 2009-07-23 14:42 ` KueiHuan Chen
0 siblings, 0 replies; 10+ messages in thread
From: KueiHuan Chen @ 2009-07-23 14:42 UTC (permalink / raw)
To: saeed bishara; +Cc: Mark Lord, Tejun Heo, saeed, linux-ide
Hi Saeed,
Thanks for the information. Is there any register that we can change
to cover this problem ?
Thanks again.
Best Regards,
KueiHuan-Chen
2009/7/23 saeed bishara <saeed.bishara@gmail.com>:
> sorry, my previous email was sent mistakenly before I completed it.
> I think you have pcie link issue here, I think it's very likely a hw
> issue in your board.
>
> saeed
>
> On Thu, Jul 23, 2009 at 4:20 PM, saeed bishara<saeed.bishara@gmail.com> wrote:
>> The stack tells that a command has been timed out. again, I think i
>>
>> On Thu, Jul 23, 2009 at 5:24 AM, KueiHuan Chen<kueihuan.chen@gmail.com> wrote:
>>> Hi Saeed,
>>>
>>> The result is same as what you guess, all register is ending with
>>> FFFF. If there has any tip to work through this, please kindly let us
>>> know.
>>>
>>> Thanks.
>>> ---------------
>>> #cat /proc/iomem
>>> 00000000-07ffffff : System RAM
>>> 00025000-0035ffff : Kernel text
>>> 00360000-003c4a0b : Kernel data
>>> e8000000-efffffff : PEX Memory
>>> e8000000-e80fffff : 0000:00:01.0
>>> e8000000-e80fffff : mvSata
>>> f1012000-f10120ff : serial8250.0
>>> f1012000-f101201f : serial
>>> f1012100-f101211f : serial
>>> f10a0000-f10a3fff : mv88fx_snd
>>> f8000000-f83fffff : physmap-flash.0
>>> f8000000-f83fffff : physmap-flash.0
>>>
>>>
>>> Strating to build software raid5 and execute devmem2.
>>> Value at address 0xE8022000 (0x40000000): 0xC2213E
>>> Value at address 0xE8024000 (0x40000000): 0xC2213E
>>> Value at address 0xE8026000 (0x40000000): 0xC2213E
>>> Value at address 0xE8028000 (0x40000000): 0xC2213E
>>> ------------------------
>>> Value at address 0xE8022030 (0x40000030): 0xFE
>>> Value at address 0xE8024030 (0x40000030): 0xE8
>>> Value at address 0xE8026030 (0x40000030): 0xE2
>>> Value at address 0xE8028030 (0x40000030): 0xC4
>>> =======repeate
>>> Value at address 0xE8022000 (0x40000000): 0xC2213E
>>> Value at address 0xE8024000 (0x40000000): 0xC2213E
>>> Value at address 0xE8026000 (0x40000000): 0xC2213E
>>> Value at address 0xE8028000 (0x40000000): 0xC2213E
>>> ------------------------
>>> Value at address 0xE8022030 (0x40000030): 0xF9
>>> Value at address 0xE8024030 (0x40000030): 0xED
>>> Value at address 0xE8026030 (0x40000030): 0xF7
>>> Value at address 0xE8028030 (0x40000030): 0xD8
>>> =======repeate
>>> Value at address 0xE8022000 (0x40000000): 0xC2213E
>>> Value at address 0xE8024000 (0x40000000): 0xC2213E
>>> Value at address 0xE8026000 (0x40000000): 0xC2213E
>>> Value at address 0xE8028000 (0x40000000): 0xC2213E
>>> ------------------------
>>> Value at address 0xE8022030 (0x40000030): 0xE1
>>> Value at address 0xE8024030 (0x40000030): 0xC17B
>>> Value at address 0xE8026030 (0x40000030): 0xE5
>>> Value at address 0xE8028030 (0x40000030): 0xCC
>>> =======repeate
>>> Value at address 0xE8022000 (0x40000000): 0xFFFFFFFF
>>> Value at address 0xE8024000 (0x40000000): 0xFFFFFFFF
>>> Value at address 0xE8026000 (0x40000000): 0xFFFFFFFF
>>> Value at address 0xE8028000 (0x40000000): 0xFFFFFFFF
>>> ------------------------
>>> Value at address 0xE8022030 (0x40000030): 0xFFFFFFFF
>>> Value at address 0xE8024030 (0x40000030): 0xFFFFFFFF
>>> Value at address 0xE8026030 (0x40000030): 0xFFFFFFFF
>>> Value at address 0xE8028030 (0x40000030): 0xFFFFFFFF
>>> =======repeate
>>> Value at address 0xE8022000 (0x40000000): 0xFFFFFFFF
>>> Value at address 0xE8024000 (0x40000000): 0xFFFFFFFF
>>> Value at address 0xE8026000 (0x40000000): 0xFFFFFFFF
>>> Value at address 0xE8028000 (0x40000000): 0xFFFFFFFF
>>> ------------------------
>>> Value at address 0xE8022030 (0x40000030): 0xFFFFFFFF
>>> Value at address 0xE8024030 (0x40000030): 0xFFFFFFFF
>>> Value at address 0xE8026030 (0x40000030): 0xFFFFFFFF
>>> Value at address 0xE8028030 (0x40000030): 0xFFFFFFFF
>>> ...
>>>
>>> first time call trace
>>> WARNING: at drivers/ata/mvSata_4_2_2/CoreDriver/mvSata.c:4811 deactivateEdma()
>>> [<c002a99c>] (dump_stack+0x0/0x14) from [<c01f8dcc>] (deactivateEdma+0x7c/0xec)
>>> [<c01f8d50>] (deactivateEdma+0x0/0xec) from [<c01f8e6c>]
>>> (mvSataDisableChannelDma+0x30/0x40)
>>> [<c01f8e3c>] (mvSataDisableChannelDma+0x0/0x40) from [<c01ec54c>]
>>> (mv_ial_ht_abort+0x48/0xe0)
>>> [<c01ec504>] (mv_ial_ht_abort+0x0/0xe0) from [<c01bd394>]
>>> (__scsi_try_to_abort_cmd+0x2c/0x34)
>>> r7:c775c000 r6:c77cb800 r5:c7fe8200 r4:c77c93c0
>>> [<c01bd368>] (__scsi_try_to_abort_cmd+0x0/0x34) from [<c01be938>]
>>> (scsi_error_handler+0x128/0x2f4)
>>> [<c01be810>] (scsi_error_handler+0x0/0x2f4) from [<c0069fc4>]
>>> (kthread+0x54/0x80)
>>> r7:00000000 r6:00000000 r5:c01be810 r4:c77cb800
>>> [<c0069f70>] (kthread+0x0/0x80) from [<c0059894>] (do_exit+0x0/0x6f8)
>>> r5:00000000 r4:00000000
>>>
>>> second time call trace
>>> WARNING: at drivers/ata/mvSata_4_2_2/CoreDriver/mvSata.c:4811 deactivateEdma()
>>> [<c002a99c>] (dump_stack+0x0/0x14) from [<c01f8dcc>] (deactivateEdma+0x7c/0xec)
>>> [<c01f8d50>] (deactivateEdma+0x0/0xec) from [<c01f8e6c>]
>>> (mvSataDisableChannelDma+0x30/0x40)
>>> [<c01f8e3c>] (mvSataDisableChannelDma+0x0/0x40) from [<c01ef8a4>]
>>> (mvRestartChannel+0xa4/0x108)
>>> [<c01ef800>] (mvRestartChannel+0x0/0x108) from [<c01ec584>]
>>> (mv_ial_ht_abort+0x80/0xe0)
>>> [<c01ec504>] (mv_ial_ht_abort+0x0/0xe0) from [<c01bd394>]
>>> (__scsi_try_to_abort_cmd+0x2c/0x34)
>>> r7:c775c000 r6:c77cb800 r5:c7fe8200 r4:c77c93c0
>>> [<c01bd368>] (__scsi_try_to_abort_cmd+0x0/0x34) from [<c01be938>]
>>> (scsi_error_handler+0x128/0x2f4)
>>> [<c01be810>] (scsi_error_handler+0x0/0x2f4) from [<c0069fc4>]
>>> (kthread+0x54/0x80)
>>> r7:00000000 r6:00000000 r5:c01be810 r4:c77cb800
>>> [<c0069f70>] (kthread+0x0/0x80) from [<c0059894>] (do_exit+0x0/0x6f8)
>>> r5:00000000 r4:00000000
>>> 0 3: deactivateEdma: Edma Failed (EDMA status = ffffffff)
>>>
>>> ... loop ..
>>> Best Regards,
>>> KueiHuan-Chen
>>>
>>
>
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2009-07-23 14:42 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-07-22 2:10 Marvell 7042 has some problem on Marvell 6281(kirkwood) platform (Resent) KueiHuan Chen
2009-07-22 2:53 ` Mark Lord
2009-07-22 7:04 ` KueiHuan Chen
2009-07-22 8:27 ` saeed bishara
2009-07-22 11:56 ` KueiHuan Chen
2009-07-22 12:09 ` saeed bishara
2009-07-23 2:24 ` KueiHuan Chen
2009-07-23 13:20 ` saeed bishara
2009-07-23 13:23 ` saeed bishara
2009-07-23 14:42 ` KueiHuan Chen
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).