Ubuntu
linux package

11ab:6145 problem with 88SE6145 SATA II controller

Bug #1094288 reported by Menno on 2012-12-28

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Expired	High	Unassigned

Bug Description

Added expansion/daughterboard to motherboard. Daugtherboard is recognised propperly - seems to be funtioning normally.
$ lspci -v
(...)
02:00.0 RAID bus controller: Marvell Technology Group Ltd. 88SE6145 SATA II PCI-E controller (rev a1) (prog-if 8f)
        Subsystem: Marvell Technology Group Ltd. 88SE6145 SATA II PCI-E controller
        Flags: bus master, fast devsel, latency 0, IRQ 16
        I/O ports at df00 [size=8]
        I/O ports at de00 [size=4]
        I/O ports at dd00 [size=8]
        I/O ports at dc00 [size=4]
        I/O ports at db00 [size=16]
        Memory at fddff000 (32-bit, non-prefetchable) [size=1K]
        [virtual] Expansion ROM at fde00000 [disabled] [size=256K]
        Capabilities: <access denied>
        Kernel driver in use: pata_marvell
        Kernel modules: pata_marvell, ahci

Tis daughterboard contains 4 SATA ports. Upon connecting a new/extra sata disk to SATA3 or 4 (and rebooting), nothing happens - disk is not recognised. Connecting the new/extra disk to STAT1 or 2 system fails to boot propperly. The grub menu is displayed but upon selecting the proper entry, the system comes to a halt in an empty terminal window.

Potential WORKAROUND: Adding a "ahci.marvell_enable=1" to the kernel command line
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-44-generic 2.6.32-44.98
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-44.98-generic 2.6.32.59+drm33.24
Uname: Linux 2.6.32-44-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: i386
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
CurrentDmesg:
[ 23.558266] type=1505 audit(1356672649.137:19): operation="profile_replace" pid=991 name="/usr/sbin/mysqld"
[ 26.612066] eth2: no IPv6 routers present
Date: Fri Dec 28 16:31:03 2012
HibernationDevice: RESUME=UUID=72be8fbd-0f3a-41fd-83d6-bf2bd3ef40b6
IwConfig:
lo no wireless extensions.

eth2 no wireless extensions.

eth0 no wireless extensions.
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-44-generic root=UUID=b5cc8552-da84-4854-8612-99517e9059d1 ro quiet splash
ProcEnviron:
PATH=(custom, no user)
LANG=nl_NL.UTF-8
SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.14
RfKill:

SourcePackage: linux
dmi.bios.date: 06/26/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: CN700-8237
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/26/2009:svn:pn:pvr:rvn:rnCN700-8237:rvr:cvn:ct3:cvr:

See original description

Tags:

Revision history for this message

Menno (q-menno) wrote on 2012-12-28:

AlsaDevices.txt Edit (403 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (42.5 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec97.0.ac97.0.0.txt Edit (870 bytes, text/plain; charset="utf-8")
Card0.Codecs.codec97.0.ac97.0.0.regs.txt Edit (767 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (1.3 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (12.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (522 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (568 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (574 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.2 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (93.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (194.5 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (2.0 MiB, text/plain; charset="utf-8")

Revision history for this message

Brad Figg (brad-figg) wrote on 2012-12-28: Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status:	New → Confirmed

Revision history for this message

penalvch (penalvch) wrote on 2012-12-28:

Menno, thank you for reporting this and helping make Ubuntu better. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelBoot ?

summary:	- problem with 88SE6145 SATA II controller + 11ab:6145 problem with 88SE6145 SATA II controller
Changed in linux (Ubuntu):
importance:	Undecided → High
status:	Confirmed → Incomplete
tags:	added: needs-debugging-kernel-boot-log

penalvch (penalvch) on 2012-12-28

description:

updated

Revision history for this message

Menno (q-menno) wrote on 2013-01-05:

Hi!

I ran some tests with the "quiet" and "splash" options removed. It is now clear that the boot process does NOT come to a halt (so this is not a kernel/boot problem after all - sorry for that), but waits for an extended period on device "ATA6", resetting is and waiting again etc. etc. Finally after some 5 minutes it gives up and boot continues normally. I assume that ATA6 is the first SATA port of the daugtherboard with the Marvell 88SE6145 controller. Can anyone give me directions how to check this assumption and how to proceed from this point?

Regards, Menno

Revision history for this message

penalvch (penalvch) wrote on 2013-01-06:

Menno, could you please provide a log that demonstrates this problem (ex. dmesg)?

tags:

added: potential-workaround

Revision history for this message

Menno (q-menno) wrote on 2013-01-06:

Hi!

For starters: the problem moved from ata6 to ata2. No idea why

copied from dmesg:

[ 2.517709] ata2: PATA max UDMA/133 cmd 0xdd00 ctl 0xdc00 bmdma 0xdb08 irq 16
...
[ 7.872213] ata2.00: qc timeout (cmd 0xec)
[ 7.872234] ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 12.912038] ata2: link is slow to respond, please be patient (ready=0)
[ 17.896037] ata2: device not ready (errno=-16), forcing hardreset
[ 23.092036] ata2: link is slow to respond, please be patient (ready=0)
[ 27.908037] ata2: SRST failed (errno=-16)
[ 33.104036] ata2: link is slow to respond, please be patient (ready=0)
[ 37.920038] ata2: SRST failed (errno=-16)
[ 43.116037] ata2: link is slow to respond, please be patient (ready=0)
[ 72.964037] ata2: SRST failed (errno=-16)
[ 77.992037] ata2: SRST failed (errno=-16)
[ 77.992043] ata2: reset failed, giving up
[ 83.032037] ata2: link is slow to respond, please be patient (ready=0)
[ 88.016038] ata2: device not ready (errno=-16), forcing hardreset
[ 88.016054] ata2: soft resetting link
[ 93.212037] ata2: link is slow to respond, please be patient (ready=0)
[ 98.028036] ata2: SRST failed (errno=-16)
[ 98.028050] ata2: soft resetting link
[ 103.224036] ata2: link is slow to respond, please be patient (ready=0)
[ 108.040037] ata2: SRST failed (errno=-16)
[ 108.040052] ata2: soft resetting link
[ 113.236036] ata2: link is slow to respond, please be patient (ready=0)
[ 143.084039] ata2: SRST failed (errno=-16)
[ 143.084055] ata2: soft resetting link
[ 148.112037] ata2: SRST failed (errno=-16)
[ 148.112043] ata2: reset failed, giving up
[ 148.112053] ata2: EH complete

Regards, Menno

Revision history for this message

penalvch (penalvch) wrote on 2013-01-13:

Menno, thank you for providing the log. If you add the following kernel parameter when booting up, does it WORKAROUND the issue:
ahci.marvell_enable=1

tags:

removed: needs-debugging-kernel-boot-log

Revision history for this message

Menno (q-menno) wrote on 2013-01-18:

Christopher, adding "ahci.marvell_enable=1" did not work at first. Than I got serious doubts is maybe the disk itself could be faulty. So i put it in a WinXP box and formatted it as one FAT32 partition. Put is back, and NOW it is recognized with the marvell_enable workaround. I still have to see if this is stable, I will come back on that point is some days.

This however, presents a new thing, normally after complete boot, I can logon from my WinXP box within 30 seconds. Now, with the disk recognized, this takes about 5 minutes. So maybe somewhere there still is a timeout in the disk system preventing samba to start. DMESG as yet, does not present a clue. I will look into that later.

penalvch (penalvch) on 2013-01-19

Changed in linux (Ubuntu):
status:	Incomplete → Confirmed

Revision history for this message

Menno (q-menno) wrote on 2013-01-19:

Hi!
I promised to get back on the stability issue: well it is NOT stable. One boot it works, the next is doesn't - behavior is unpredictable

I supply two logs:
1) the successful boot:

[ 2.274525] ata3: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 16
...
[ 2.274525] ata3: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 16
...
[ 8.236061] ata3.00: qc timeout (cmd 0xec)
[ 8.236196] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 8.556068] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 8.557570] ata3.00: ATA-8: V4-CT032V4SSD2, S5FAMM22, max UDMA/100
[ 8.557644] ata3.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 8.558420] ata3.00: configured for UDMA/100
...
[ 22.816084] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 22.816174] ata3.00: failed command: IDENTIFY DEVICE
[ 22.816257] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[ 22.816262] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 22.816408] ata3.00: status: { DRDY }
[ 22.816479] ata3: hard resetting link
[ 23.136067] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 23.138273] ata3.00: configured for UDMA/100
[ 23.138378] ata3: EH complete
...
[ 40.816319] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 40.837751] ata3.00: failed command: IDENTIFY DEVICE
[ 40.848725] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[ 40.848730] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 40.880902] ata3.00: status: { DRDY }
[ 40.891862] ata3: hard resetting link
[ 41.352330] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 41.354441] ata3.00: configured for UDMA/100
[ 41.354496] ata3: EH complete

And 2) the unsuccessful boot:

[ 2.239979] ata3: SATA max UDMA/133 abar m1024@0xfddff000 port 0xfddff100 irq 16
...
[ 2.796072] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
...
[ 7.796063] ata3.00: qc timeout (cmd 0xec)
[ 7.796086] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 8.116069] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 15.153557] sdc1
[ 15.155748] sd 7:0:0:0: [sdc] Assuming drive cache: write through
...
[ 18.116060] ata3.00: qc timeout (cmd 0xec)
[ 18.116082] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 18.116095] ata3: limiting SATA link speed to 1.5 Gbps
[ 18.436068] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 48.436045] ata3.00: qc timeout (cmd 0xec)
[ 48.436063] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[ 48.756064] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

On the second log: note the long delay after the logged event at 8.116069, this is EXACTLY as appears in the output of DMESG

Any suggestions?

Hi!
I promised to get back on the stability issue: well it is NOT stable. One boot it works, the next is doesn't - behavior is unpredictable

I supply two logs: 
1) the successful boot:

[    2.274525] ata3: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 16
...
[    2.274525] ata3: SATA max UDMA/133 irq_stat 0x02400000, PHY RDY changed irq 16
...
[    8.236061] ata3.00: qc timeout (cmd 0xec)
[    8.236196] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    8.556068] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    8.557570] ata3.00: ATA-8: V4-CT032V4SSD2, S5FAMM22, max UDMA/100
[    8.557644] ata3.00: 62533296 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    8.558420] ata3.00: configured for UDMA/100
...
[   22.816084] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   22.816174] ata3.00: failed command: IDENTIFY DEVICE
[   22.816257] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[   22.816262]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   22.816408] ata3.00: status: { DRDY }
[   22.816479] ata3: hard resetting link
[   23.136067] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   23.138273] ata3.00: configured for UDMA/100
[   23.138378] ata3: EH complete
...
[   40.816319] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[   40.837751] ata3.00: failed command: IDENTIFY DEVICE
[   40.848725] ata3.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
[   40.848730]          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[   40.880902] ata3.00: status: { DRDY }
[   40.891862] ata3: hard resetting link
[   41.352330] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   41.354441] ata3.00: configured for UDMA/100
[   41.354496] ata3: EH complete

And 2) the unsuccessful boot:

[    2.239979] ata3: SATA max UDMA/133 abar m1024@0xfddff000 port 0xfddff100 irq 16
...
[    2.796072] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
...
[    7.796063] ata3.00: qc timeout (cmd 0xec)
[    7.796086] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[    8.116069] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[   15.153557]  sdc1
[   15.155748] sd 7:0:0:0: [sdc] Assuming drive cache: write through
...
[   18.116060] ata3.00: qc timeout (cmd 0xec)
[   18.116082] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   18.116095] ata3: limiting SATA link speed to 1.5 Gbps
[   18.436068] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[   48.436045] ata3.00: qc timeout (cmd 0xec)
[   48.436063] ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
[   48.756064] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

On the second log: note the long delay after the logged event at 8.116069, this is EXACTLY as appears in the output of DMESG

Any suggestions?

penalvch (penalvch) on 2013-01-19

tags:

removed: potential-workaround

Revision history for this message

penalvch (penalvch) wrote on 2013-01-19:

#10

Menno, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.8-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

Changed in linux (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Menno (q-menno) wrote on 2013-02-16:

#11

Hi!
Since my server is a "production system", I am somewhat reluctant to update to a new version. I therefore tried to find a way to test the latest kernel without having tot upgrade the whole system. Up to now I did not find a "safe and easy" way to do so. Can you point me to instructions on how to test a new and possibly unstable kernel version, without having to upgrade my server? (OK, this might look like a bit of cold-water fear, but I am not really familiar with kernel testing/debugging issues)

Revision history for this message

penalvch (penalvch) wrote on 2013-02-17:

#12

Menno, thank you for your comments. Regarding them https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094288/comments/11 :
>"Hi! Since my server is a "production system", I am somewhat reluctant to update to a new version. I therefore tried to find a way to test the latest kernel without having tot upgrade the whole system. Up to now I did not find a "safe and easy" way to do so. Can you point me to instructions on how to test a new and possibly unstable kernel version, without having to upgrade my server? (OK, this might look like a bit of cold-water fear, but I am not really familiar with kernel testing/debugging issues)"

Do you know you do not have to upgrade the entire system just to perform the test requested of you in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1094288/comments/10 ?

Revision history for this message

Launchpad Janitor (janitor) wrote on 2013-04-19:

#13

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Menno (q-menno) wrote on 2013-07-18:

#14

Hi!

I finally came around to updating the kernel. Tested with the 12.04 LTS version / 3.2 kernel. Unfortunately mij RAID system won't boot on this 3.2 kernel. Had to fall back to the original 2.6 kernel. Problem. however, still remains. Any activity on this bug?

Regards, Menno

penalvch (penalvch) on 2013-07-19

tags:

added: needs-server-mfg+model

Revision history for this message

Menno (q-menno) wrote on 2013-07-19:

#15

Christopher, thanks for reacting to my post. I would really like to help in solving this pesky problem. Please inform me of all the info logs etc. you need.
From your tag I suspect you want some hardware info:

PC with motherboard: "Jetway J7F2 C7 1.2GHz J7F21G2ES P" & expansion card "JETWAY 4 x SATA AD-module". Currently running UBUNTU 12.04.2 LTS and kernel version 2.6.32-45-generic.

The system is booted with the "ahci.marvell_enable=1" option.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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

Ubuntulinux package

11ab:6145 problem with 88SE6145 SATA II controller

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package