From: Maarten Vanraes <maarten@ba.be>
To: linux-kernel@vger.kernel.org
Subject: megaraid_sata vs megasr
Date: Mon, 26 May 2008 10:05:30 +0200 [thread overview]
Message-ID: <200805261005.31015.maarten@ba.be> (raw)
Hello, (can you CC me? i'm not on the list)
I have a LSI MegaRAID SAS 8204ELP card, and since it wasn't recognized by any
driver, i tried using the megasr driver supplied by LSI (it also supplies
open_source code with it), i had to modify the code a bit to get it to boot
with kernel-2.6.21 . but there's a very high iowait on it. i'm wondering if
the megaraid_sas driver is meant to be the driver for the same hardware as
megasr? would it help if i just added another PCI ID to the module and try
that one?
Sincerely,
Maarten Vanraes
[] # lspci -s 08:00.0 -vvvn
08:00.0 0100: 1000:0059 (rev 08)
Subsystem: 1000:3002
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR+ <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 18
Region 0: I/O ports at 3000 [size=256]
Region 1: Memory at d8410000 (64-bit, non-prefetchable) [size=16K]
Region 3: Memory at d8400000 (64-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at d8000000 [disabled] [size=2M]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [68] Express (v1) Endpoint, MSI 00
DevCap: MaxPayload 4096 bytes, PhantFunc 0, Latency L0s <64ns,
L1 <1us
ExtTag+ AttnBtn- AttnInd- PwrInd- RBE- FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal-
Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr-
TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x8, ASPM L0s L1, Latency
L0 <64ns, L1 <1us
ClockPM- Suprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain-
CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk-
DLActive- BWMgmt- ABWMgmt-
Capabilities: [98] Message Signalled Interrupts: Mask- 64bit+
Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000
Capabilities: [b0] MSI-X: Enable- Mask- TabSize=1
Vector table: BAR=1 offset=00002000
PBA: BAR=1 offset=00003000
Capabilities: [100] Advanced Error Reporting <?>
Kernel driver in use: megasr
--
Maarten Vanraes
BA NV: IT & Security
next reply other threads:[~2008-05-26 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 8:05 Maarten Vanraes [this message]
2008-05-26 17:11 ` megaraid_sata vs megasr Jeff Garzik
2008-05-27 9:55 ` Maarten Vanraes
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=200805261005.31015.maarten@ba.be \
--to=maarten@ba.be \
--cc=linux-kernel@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