From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Brett Russ <russb@emc.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Pasi Pirhonen <upi@papat.org>,
Michael Madore <Michael.Madore@aslab.com>,
Bogdan Costescu <Bogdan.Costescu@iwr.uni-heidelberg.de>,
"Mr. Berkley Shands" <bshands@exegy.com>,
Jim Edwards <jim@networkdesigning.com>,
scott olson <scotto701@yahoo.com>
Subject: Re: [PATCH 2.6.14-rc2] libata: Marvell SATA support (DMA mode) (resend: v0.22)
Date: Fri, 30 Sep 2005 13:37:47 +0200 [thread overview]
Message-ID: <m3r7b6pz04.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <20050930053600.F3B821CDD0@lns1058.lss.emc.com> (Brett Russ's message of "Fri, 30 Sep 2005 01:36:00 -0400 (EDT)")
Brett Russ <russb@emc.com> writes:
> This is my libata compatible low level driver for the Marvell SATA
> family. Currently it runs in DMA mode on a 6081 chip.
I've tried the new version of the driver on our Supermicro 6024H-T
server with the Marvell 88SX6081 8-port SATA controller. There are
six disks in the server, if that makes any difference.
When booting up, the driver issued the following text:
sata_mv version 0.22
ACPI: PCI Interrupt 0000:02:03.0[A] -> GSI 56 (level, low) -> IRQ 20
sata_mv(0000:02:03.0) 32 slots 8 ports unknown mode IRQ via INTx
ata1: SATA max UDMA/133 cmd 0x0 ctl 0xF8922120 bmdma 0x0 irq 20
ata2: SATA max UDMA/133 cmd 0x0 ctl 0xF8924120 bmdma 0x0 irq 20
ata3: SATA max UDMA/133 cmd 0x0 ctl 0xF8926120 bmdma 0x0 irq 20
ata4: SATA max UDMA/133 cmd 0x0 ctl 0xF8928120 bmdma 0x0 irq 20
ata5: SATA max UDMA/133 cmd 0x0 ctl 0xF8932120 bmdma 0x0 irq 20
ata6: SATA max UDMA/133 cmd 0x0 ctl 0xF8934120 bmdma 0x0 irq 20
ata7: SATA max UDMA/133 cmd 0x0 ctl 0xF8936120 bmdma 0x0 irq 20
ata8: SATA max UDMA/133 cmd 0x0 ctl 0xF8938120 bmdma 0x0 irq 20
ATA: abnormal status 0x80 on port 0xF892211C
ATA: abnormal status 0x80 on port 0xF892211C
At that point the machine freezes hard -- the SysRq key doesn't work.
lspci -vxx output for the controller:
02:03.0 RAID bus controller: Marvell Technology Group Ltd. MV88SX6081 8-port SATA II PCI-X Controller (rev 03)
Subsystem: Super Micro Computer Inc: Unknown device 6080
Flags: bus master, fast Back2Back, 66Mhz, medium devsel, latency 64, IRQ 5
Memory at dd200000 (64-bit, non-prefetchable) [size=1M]
I/O ports at 2000 [size=256]
Capabilities: [40] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Capabilities: [60] #07 [0030]
00: ab 11 81 60 17 03 b0 02 03 00 04 01 08 40 00 00
10: 04 00 20 dd 00 00 00 00 01 20 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 d9 15 80 60
30: 00 00 00 00 40 00 00 00 00 00 00 00 05 01 00 00
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2005-09-30 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 5:36 Brett Russ
2005-09-30 11:37 ` Lars Magne Ingebrigtsen [this message]
2005-10-04 2:08 ` Jeff Garzik
2005-10-05 15:17 ` Evgeny Rodichev
2005-10-05 17:04 ` Jeff Garzik
2005-10-05 17:10 ` Brett Russ
2005-10-05 19:14 ` Bogdan Costescu
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=m3r7b6pz04.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=Bogdan.Costescu@iwr.uni-heidelberg.de \
--cc=Michael.Madore@aslab.com \
--cc=bshands@exegy.com \
--cc=jgarzik@pobox.com \
--cc=jim@networkdesigning.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=russb@emc.com \
--cc=scotto701@yahoo.com \
--cc=upi@papat.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
all inboxes | Powered by JetHome®