Marvell 88SE6121 not supported

Bug #335615 reported by Stephen Hemminger
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: linux-image

The Marvell 88SE6121 SAS disk controller on Asus P6-T motherboard is not supported in Jaunty.
It appears to be as simple as just enabling CONFIG_SCSI_MVSAS=m in kernel config!

Revision history for this message
ooze (zoe-gauthier) wrote :

As far as I know, the mvsas driver is for 88SE6440 devices. If you need to enable SATA support on a 88SE6121 device, you can learn more at http://wiki.debian.org/pata_marvell.

If you think this is still a bug, please include the following additional information:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

Changed in linux-meta:
status: New → Incomplete
Revision history for this message
Stephen Hemminger (shemminger) wrote :

Marvell devices on ASUS P6-T are:

07:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
08:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b2)
09:00.0 RAID bus controller: Marvell Technology Group Ltd. Device 6440 (rev 02)
0a:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)

The one the bug is about is:

09:00.0 RAID bus controller: Marvell Technology Group Ltd. Device 6440 (rev 02)
 Subsystem: ASUSTeK Computer Inc. Device 82e4
 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: 64 bytes
 Interrupt: pin A routed to IRQ 19
 Region 2: I/O ports at cc00 [size=128]
 Region 4: Memory at fbcff000 (64-bit, non-prefetchable) [size=4K]
 Expansion ROM at fbc80000 [disabled] [size=256K]
 Capabilities: [48] Power Management version 2
  Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0+,D1+,D2-,D3hot+,D3cold-)
  Status: D0 PME-Enable- DSel=0 DScale=1 PME-
 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
  Address: 0000000000000000 Data: 0000
 Capabilities: [e0] Express (v1) Legacy Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 unlimited
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 2048 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
  LnkCap: Port #0, Speed 2.5GT/s, Width x4, ASPM L0s, Latency L0 <256ns, L1 unlimited
   ClockPM- Suprise- LLActRep- BwNot-
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 Capabilities: [100] Advanced Error Reporting <?>
 Kernel driver in use: mvsas
 Kernel modules: mvsas

Just enabling CONFIG_SCSI_MVSAS gets the correct driver.
I even extracted driver from kernel source and built it standalone, and that worked as well.

ooze (zoe-gauthier)
Changed in linux-meta:
status: Incomplete → Confirmed
Revision history for this message
vincefn (vincent-favre-nicolin) wrote :

  Kernel 2.6.28-12 (which is now in jaunty's proposed-updates) adds support for mvsas:

uname -a
Linux gre019099 2.6.28-12-generic #43-Ubuntu SMP Fri May 1 19:31:32 UTC 2009 x86_64 GNU/Linux

 find /lib/modules/ -iname *mvsas*
/lib/modules/2.6.28-12-generic/kernel/drivers/scsi/mvsas.ko

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352336

    Vincent

Revision history for this message
taka k. (scar) wrote :

i followed the instructions on http://wiki.debian.org/pata_marvell and now my two disks are being detected as /dev/sdc and /dev/sdd. however, i have them setup in a RAID-1 using the Marvell option ROM , in the BIOS. so, shouldn't linux see it as one device? does that mean i am a victim of this bug?

i am using ubuntu 8.10 with linux 2.6.27-14-generic. i actually have the 88SE6121, so i am confused by Stephen Hemminger's comments regarding the 6440. i notice in lspci it says the controller is using the 'ahci' kernel module, shouldn't that be raid or something?

ooze (zoe-gauthier)
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.