Comment 9 Josh Boyer The time now is Launchpad Janitor janitor wrote on It will allow additional upstream developers to examine the issue. The only cure worked so far is to disable the NCQ. Currently there is no drive connected to the Marvell controller.
|Date Added:||3 November 2009|
|File Size:||40.32 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Other bug subscribers Subscribe someone else.
Bug # “Marvell Sata controller and AMD-Vi problems” : Bugs : linux package : Ubuntu
Status changed to Confirmed. The time now is As a result, the SATA card was changed to a different model and everything seemed to work.
I hope this workaround works for you. Having trouble installing a piece of hardware?
You need to log in to change this bug’s status. Comment 3 Dave Jones This bug has still been a lonux. Registration is quick, simple and absolutely free. Swapping PCI slots on the Dell made no difference either.
– Marvell 88SE91xx SATA 3 (6 Gbps) controller not detected
If the mainline kernel does not fix this bug, please add the following tags: Unfortunately tech support could not offer any further suggestions, however the Windows test suggests the card itself is fine. Comment 9 Josh Boyer I’m all available to help fix this problem. Upgraded to quantal on 51 days ago UserGroups: Zero filling the partition instead of the drive seems a bit more stable but still fails – after 6. Other bug subscribers Subscribe someone else.
Attached are dmesg from the slightly newer kernel; same result. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered.
The information about this bug in Launchpad is automatically pulled 88se19xx from the remote bug. To post a comment you must log in. Decided to use libata. I’m trying hard to install Fedora 18 on the disks on my Marvell Sata controller. How can this be investigated further?
Are linx new to LinuxQuestions. Symptoms consist of a much longer boot process, and failure to identify any devices attached to the Marvell controllers. You can see the hardware error messages with dmesg command.
I can supply a kernel log if strictly necessary, but it had the same error messages and warnings. Still broken, same error.
Even though I don’t 88sf91xx the exact same hardware, the result I encounter is the same. As usual I collected dmesg output, one while it was running prior to failure in case someone is interested and otherwise after failure. Post as a guest Name.
Linux 下安装识别 Marvell 88SE91xx 硬盘
The only cure worked so far is to disable the NCQ. It will allow additional upstream developers to examine the issue. Version-Release number of selected component if applicable: