Linux ATA/IDE development
 help / color / mirror / Atom feed
From: "Brian Rademacher" <rad@radfiles.net>
To: fedora-test-list@redhat.com
Cc: linux-ide@vger.kernel.org
Subject: $100 reward! - Marvell 88SX6081 disk problem during high load...
Date: Thu, 12 May 2005 00:05:10 -0600	[thread overview]
Message-ID: <005e01c556b8$8e1db550$0301a8c0@Rad> (raw)

Yes, I'm desperate, and $100 will be immediately sent your way (paypal, or 
whatever form you want) upon resolution of the problem by you...I've been 
trying for months to get a Marvell 88SX6081 on an ABIT SU-2S motherboard to 
work under Fedora...Thought I would post some of the relevent dmesg output 
to see if anyone has any ideas...Long story short, under a high load (in 
this case, just trying to format the drives), they go offline and never come 
back...This happens under FC4T3 and FC3 I'm using two Maxtor Diamondmax 10 
300 gig SATA-II drives (6B300S0)...

I tested both drives for errors on a different system and they are fine...I 
have also tried various versions of drive firmware from Maxtor with no 
luck...If I keep the load low, things work fine...I have been able to format 
in the past by increasing the inode size, thus causing less load during the 
format, although it crashed later on with the same errors during an updatedb 
operation...

I have a feeling that this is driver related, which is a bad thing, as ABIT 
no longer supports my SU-2S motherboard and Marvell doesn't support end 
users...I have tried A LOT of things in relation to this problem, but feel 
free to suggest them again anyway...

As far as the reward goes, it will go to the first person that comes up with 
the solution (which must be practical for me, and not something like "write 
your own libata driver") as judged by the email receipt time...(anyone want 
to rewrite a driver?  I have the GPL source)...


Here is the driver init:
ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 26 (level, low) -> IRQ 201
scsi0 : Marvell SCSI to SATA adapter
scsi1 : Marvell SCSI to SATA adapter
scsi2 : Marvell SCSI to SATA adapter
scsi3 : Marvell SCSI to SATA adapter
scsi4 : Marvell SCSI to SATA adapter
scsi5 : Marvell SCSI to SATA adapter
scsi6 : Marvell SCSI to SATA adapter
scsi7 : Marvell SCSI to SATA adapter
  Vendor: Maxtor    Model: 6B300S0           Rev: BANC
  Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sda: drive cache: write back
 sda: sda1 sda2 sda3
Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
  Vendor: Maxtor    Model: 6B300S0           Rev: BANC
  Type:   Direct-Access                      ANSI SCSI revision: 03
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdb: drive cache: write back
SCSI device sdb: 586114704 512-byte hdwr sectors (300091 MB)
SCSI device sdb: drive cache: write back
 sdb: sdb1 sdb2 sdb3
Attached scsi disk sdb at scsi1, channel 0, id 0, lun 0


Then this happens mid-way through the format:
cfq: depth 4 reached, tagging now on
cfq: depth 4 reached, tagging now on
scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 
0 lun 0
scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 
0 lun 0
scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 
0 lun 0
scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 
0 lun 0
scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 
0 lun 0
scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 
0 lun 0
(lots of these device offlined message)


Followed by:
SCSI error : <0 0 0 0> return code = 0x8
end_request: I/O error, dev sda, sector 407850128
Buffer I/O error on device md0, logical block 101384192
lost page write due to I/O error on md0
scsi0 (0:0): rejecting I/O to offline device
Buffer I/O error on device md0, logical block 101384193
lost page write due to I/O error on md0
scsi0 (0:0): rejecting I/O to offline device
Buffer I/O error on device md0, logical block 102400000
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 102400001
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 102400002
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 102400003
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 102400004
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 102400005
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 102400006
lost page write due to I/O error on md0
Buffer I/O error on device md0, logical block 102400007
lost page write due to I/O error on md0
scsi0 (0:0): rejecting I/O to offline device
scsi0 (0:0): rejecting I/O to offline device
scsi0 (0:0): rejecting I/O to offline device
scsi0 (0:0): rejecting I/O to offline device
scsi0 (0:0): rejecting I/O to offline device
scsi0 (0:0): rejecting I/O to offline device
(lots of these messages)


And then:
SCSI error : <0 0 0 0> return code = 0x8
end_request: I/O error, dev sda, sector 407981200
scsi0 (0:0): rejecting I/O to offline device
SCSI error : <0 0 0 0> return code = 0x8
end_request: I/O error, dev sda, sector 408112272
scsi0 (0:0): rejecting I/O to offline device
(lots of these with various sectors listed)


And last:
Synchronizing SCSI cache for disk sda:
FAILED
  status = 0, message = 00, host = 1, driver = 00 

-- 
fedora-test-list mailing list
fedora-test-list@redhat.com
To unsubscribe: 
http://www.redhat.com/mailman/listinfo/fedora-test-list

                 reply	other threads:[~2005-05-12  6:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='005e01c556b8$8e1db550$0301a8c0@Rad' \
    --to=rad@radfiles.net \
    --cc=fedora-test-list@redhat.com \
    --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