sata_mv

sata_mv

[Steven Gill]

Hi List,

I am having some issues getting my Marvell 6145 working on my Asus P5E 
ws pro motherboard working.  I am using a 3rd party patch to get the 
pata port working, but have not had success with my e-sata ports (on the 
board the 6145 drives 2 sata and 2 e-sata ports.  There are another 6 
sata ports driven by the onboard intel ich9).  When checking dmesg 
output, I see this:

ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:02:00.0 to 64
Marvell (S)ATA Controller is found, using IRQ 16.
Interrupt Error: 0x40000000 orgIntStatus: 0x40000001 completeSlot=0x1.

I am willing to help debug any issues, test patches, etc, but most 
importantly wanted to report the issue.  I know this is labelled as 
"highly experimental", but again, wanted to offer assistance in testing.

Regards,

Steve

Re: sata_mv (NOT!)

[Mark Lord]

Steven Gill wrote:
> Hi List,
> 
> I am having some issues getting my Marvell 6145 working on my Asus P5E 
> ws pro motherboard working.  I am using a 3rd party patch to get the 
> pata port working, but have not had success with my e-sata ports (on the 
> board the 6145 drives 2 sata and 2 e-sata ports.  There are another 6 
> sata ports driven by the onboard intel ich9).  When checking dmesg 
> output, I see this:
> 
> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:02:00.0 to 64
> Marvell (S)ATA Controller is found, using IRQ 16.
> Interrupt Error: 0x40000000 orgIntStatus: 0x40000001 completeSlot=0x1.
> 
> I am willing to help debug any issues, test patches, etc, but most 
> importantly wanted to report the issue.  I know this is labelled as 
> "highly experimental", but again, wanted to offer assistance in testing.
..

Wrong driver.  sata_mv does *NOT* drive the 6145 chip.
Rather, that particular chip emulates AHCI, and uses the ahci driver.

-ml

Re: sata_mv (NOT!)

[Steven Gill]

Sorry for the mistake there.  I realized I was using a non-mainline 
driver to get PATA to work, but decided to move to a SATA DVD burner.  
When inserting a disk into the drive (when hooked to the Marvell 6145), 
I get the following:

ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392 in
         cdb 4a 01 00 00 10 00 00 00  08 00 00 00 00 00 00 00
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata10.00: status: { DRDY }
ata10: hard resetting link
ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata10.00: configured for UDMA/100
ata10: EH complete
ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata10.00: cmd a0/00:00:00:02:00/00:00:00:00:00/a0 tag 0 pio 16388 in
         cdb 51 00 00 00 00 00 00 00  02 00 00 00 00 00 00 00
         res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
ata10.00: status: { DRDY }
ata10: hard resetting link
ata10: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

I am currently running 2.26.2

I was able to sucessfully burn a CD when connecting this drive to the 
ICH9 controller sata port, but could not burn a dual layer dvd (There 
was a similar reset message)

Aug 19 22:05:18 [kernel] warning: `growisofs' uses deprecated v2 
capabilities in a way that may be insecure.
Aug 19 22:06:21 [kernel] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 
action 0x6 frozen
Aug 19 22:06:21 [kernel] ata5.00: cmd 
a0/01:00:00:00:80/00:00:00:00:00/a0 tag 0 dma 32768 out
Aug 19 22:06:21 [kernel]          cdb 2a 00 00 00 00 00 00 00  10 00 00 
00 00 00 00 00
Aug 19 22:06:21 [kernel]          res 
40/00:03:00:0c:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Aug 19 22:06:21 [kernel] ata5.00: status: { DRDY }
Aug 19 22:06:21 [kernel] ata5: hard resetting link
Aug 19 22:06:21 [kernel] ata5: SATA link up 1.5 Gbps (SStatus 113 
SControl 300)

Steve

Mark Lord wrote:
> Steven Gill wrote:
>> Hi List,
>>
>> I am having some issues getting my Marvell 6145 working on my Asus 
>> P5E ws pro motherboard working.  I am using a 3rd party patch to get 
>> the pata port working, but have not had success with my e-sata ports 
>> (on the board the 6145 drives 2 sata and 2 e-sata ports.  There are 
>> another 6 sata ports driven by the onboard intel ich9).  When 
>> checking dmesg output, I see this:
>>
>> ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
>> PCI: Setting latency timer of device 0000:02:00.0 to 64
>> Marvell (S)ATA Controller is found, using IRQ 16.
>> Interrupt Error: 0x40000000 orgIntStatus: 0x40000001 completeSlot=0x1.
>>
>> I am willing to help debug any issues, test patches, etc, but most 
>> importantly wanted to report the issue.  I know this is labelled as 
>> "highly experimental", but again, wanted to offer assistance in testing.
> ..
>
> Wrong driver.  sata_mv does *NOT* drive the 6145 chip.
> Rather, that particular chip emulates AHCI, and uses the ahci driver.
>
> -ml
>

Re: sata_mv (NOT!)

[Mark Lord]

Steven Gill wrote:
..
> I am currently running 2.26.2
> 
> I was able to sucessfully burn a CD when connecting this drive to the 
> ICH9 controller sata port, but could not burn a dual layer dvd (There 
> was a similar reset message)
..

Yeah, it looks to me as if libata still has DVD burner issues.
I used my SATA DVDRW drive to burn a Suse DVD the other day,
and the same drive refused to read the burnt disc without first rebooting.

linux-2.6.25.6

Disc was fine, though.  Single-layer.

Cheers

Re: sata_mv (NOT!)

[Jeff Garzik]

Mark Lord wrote:
> Steven Gill wrote:
> ..
>> I am currently running 2.26.2
>>
>> I was able to sucessfully burn a CD when connecting this drive to the 
>> ICH9 controller sata port, but could not burn a dual layer dvd (There 
>> was a similar reset message)
> ..
> 
> Yeah, it looks to me as if libata still has DVD burner issues.
> I used my SATA DVDRW drive to burn a Suse DVD the other day,
> and the same drive refused to read the burnt disc without first rebooting.
> 
> linux-2.6.25.6
> 
> Disc was fine, though.  Single-layer.

Do you get error messages as well?  Of what kind?

	Jeff

Re: sata_mv (NOT!)

[Mark Lord]

Jeff Garzik wrote:
> Mark Lord wrote:
>>
>> Yeah, it looks to me as if libata still has DVD burner issues.
>> I used my SATA DVDRW drive to burn a Suse DVD the other day,
>> and the same drive refused to read the burnt disc without first 
>> rebooting.
>>
>> linux-2.6.25.6
>>
>> Disc was fine, though.  Single-layer.
> 
> Do you get error messages as well?  Of what kind?
..

There have been so many broken things in so many parts of the kernel of late,
that I'm just way too far behind in diagnosing/fixing them.   Or reporting them,
since many developers have stated they would rather not see a bug report
without a bisect.

But here's all that was in the logs for this particular bug.
These messages appeared when trying to read the freshly burned DVD,
both before and after eject/reinsert.  A reboot cured it:

[ 8209.473181] attempt to access beyond end of device
[ 8209.473189] sr0: rw=0, want=68, limit=4
[ 8209.487646] attempt to access beyond end of device
[ 8209.487655] sr0: rw=0, want=5480256, limit=4
[ 8209.487664] attempt to access beyond end of device
[ 8209.487668] sr0: rw=0, want=5479232, limit=4
[ 8209.487681] attempt to access beyond end of device
[ 8209.487685] sr0: rw=0, want=5479008, limit=4
[ 8209.487694] attempt to access beyond end of device
[ 8209.487700] sr0: rw=0, want=5480248, limit=4
[ 8209.487714] attempt to access beyond end of device
[ 8209.487719] sr0: rw=0, want=5479224, limit=4
[ 8209.487728] attempt to access beyond end of device
[ 8209.487733] sr0: rw=0, want=5479000, limit=4
[ 8209.487742] attempt to access beyond end of device
[ 8209.487747] sr0: rw=0, want=5479656, limit=4
[ 8209.487757] attempt to access beyond end of device
[ 8209.487762] sr0: rw=0, want=5478632, limit=4
[ 8209.487771] attempt to access beyond end of device
[ 8209.487776] sr0: rw=0, want=5478408, limit=4
[ 8209.487784] attempt to access beyond end of device
[ 8209.487789] sr0: rw=0, want=5479648, limit=4
[ 8209.487797] attempt to access beyond end of device
[ 8209.487802] sr0: rw=0, want=5478624, limit=4
[ 8209.487811] attempt to access beyond end of device
[ 8209.487816] sr0: rw=0, want=5478400, limit=4
[ 8209.487829] attempt to access beyond end of device
[ 8209.487833] sr0: rw=0, want=4496644, limit=4
[ 8209.487843] attempt to access beyond end of device
[ 8209.487848] sr0: rw=0, want=4495620, limit=4
[ 8209.487857] attempt to access beyond end of device
[ 8209.487862] sr0: rw=0, want=4495396, limit=4
[ 8209.487870] attempt to access beyond end of device
[ 8209.487875] sr0: rw=0, want=4496636, limit=4
[ 8209.487883] attempt to access beyond end of device
[ 8209.487888] sr0: rw=0, want=4495612, limit=4
[ 8209.487896] attempt to access beyond end of device
[ 8209.487901] sr0: rw=0, want=4495388, limit=4
[ 8209.487910] attempt to access beyond end of device
[ 8209.487915] sr0: rw=0, want=4496044, limit=4
[ 8209.487924] attempt to access beyond end of device
[ 8209.487929] sr0: rw=0, want=4495020, limit=4
[ 8209.487938] attempt to access beyond end of device
[ 8209.487942] sr0: rw=0, want=4494796, limit=4
[ 8209.487951] attempt to access beyond end of device
[ 8209.487955] sr0: rw=0, want=4496036, limit=4
[ 8209.487964] attempt to access beyond end of device
[ 8209.487969] sr0: rw=0, want=4495012, limit=4
[ 8209.487978] attempt to access beyond end of device
[ 8209.487982] sr0: rw=0, want=4494788, limit=4
[ 8209.487990] attempt to access beyond end of device
[ 8209.487995] sr0: rw=0, want=1252, limit=4
[ 8209.488004] attempt to access beyond end of device
[ 8209.488008] sr0: rw=0, want=1028, limit=4
[ 8209.488014] UDF-fs: No partition found (1)
[ 8209.514467] attempt to access beyond end of device
[ 8209.514467] sr0: rw=0, want=68, limit=4
[ 8209.514467] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16

Re: sata_mv (NOT!)

[Mark Lord]

Mark Lord wrote:
> Jeff Garzik wrote:
>> Mark Lord wrote:
>>>
>>> Yeah, it looks to me as if libata still has DVD burner issues.
>>> I used my SATA DVDRW drive to burn a Suse DVD the other day,
>>> and the same drive refused to read the burnt disc without first 
>>> rebooting.
>>>
>>> linux-2.6.25.6
>>>
>>> Disc was fine, though.  Single-layer.
>>
>> Do you get error messages as well?  Of what kind?
> ..
> 
> There have been so many broken things in so many parts of the kernel of 
> late,
> that I'm just way too far behind in diagnosing/fixing them.   Or 
> reporting them,
> since many developers have stated they would rather not see a bug report
> without a bisect.
> 
> But here's all that was in the logs for this particular bug.
> These messages appeared when trying to read the freshly burned DVD,
> both before and after eject/reinsert.  A reboot cured it:
> 
> [ 8209.473181] attempt to access beyond end of device
> [ 8209.473189] sr0: rw=0, want=68, limit=4
> [ 8209.487646] attempt to access beyond end of device
> [ 8209.487655] sr0: rw=0, want=5480256, limit=4
..
> [ 8209.514467] attempt to access beyond end of device
> [ 8209.514467] sr0: rw=0, want=68, limit=4
> [ 8209.514467] isofs_fill_super: bread failed, dev=sr0, iso_blknum=16, block=16
..

To hazard a guess at the problem here, I'd say that perhaps the media change
went undetected, and so sr_media_change() never got called.

I'm no longer even sure what would trigger that call.

Cheers