Home Questions Tags Users Unanswered. Penalver penalvch wrote on It will allow additional upstream developers to examine the issue. You can see the hardware error messages with dmesg command. The issue I face is that the card behaves erratically, dropping a drive from the array Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Add device id for Marvell 88se91a2 bytes, patch
|Date Added:||1 July 2016|
|File Size:||44.82 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Knowing what distro you selected may offer better guesses. The only cure worked so far is to disable the NCQ. Email me about changes to this bug report.
To be filled by O. Note You need to log in before you can comment on or make changes to this bug. MvW 2nv2u wrote on Registration is quick, simple and absolutely free.
Linux 下安装识别 Marvell 88SE91xx 硬盘
However, as a maybe: Under Linux copies or writes failed – be it to the drive itself or to the NTFS partition from Windows, under Windows the drive benchmarked fine.
Visit the following links: Comment 4 Justin M.
Can you post the dmesg from the install attempt? Just running dd with defaults: I don’t know why it didn’t before.
Once you’ve tested the upstream kernel, please comment on which kernel version specifically you tested. Tech support suggested testing it outside of the array – zero filling the drive results in a failure at different times, anything from 1. Find More Posts by jefro.
Version-Release number of selected component if applicable: Zero filling linix partition instead of the drive seems a bit more stable but still fails – after 6. For more on this, please read the official Ubuntu documentation: If this bug is fixed in the mainline kernel, please add the following tags: If you need to reset your password, click here.
Linux 下安装识别 Marvell 88SE91xx 硬盘 |
This bug affects 4 people. Where do I find that script? The problem is reproducible! Even though I lnux have the exact same hardware, the result I encounter is the same.
Bug # “Marvell Sata controller and AMD-Vi problems” : Bugs : linux package : Ubuntu
Very stable without NCQ. This command takes effect immediately however it’s not persistent on rebooting so you’ll eventually have to change the boot parameters.
Find More Posts by ardvark It is my understanding that the card should just work – as the controller is supported by Linux 8s8e91xx should hence just work, unfortunately it does not. Linux Kernel Bug Tracker Thanks for the post – I’ll play around with your suggestions and see if I have any success – would be great if that is the solution.
I’m not an expert but hopefully someone knowledgeable may be able to help. As pointed here http: It sounds like the preferred solution is PCI quirk, and some of the infrastructure is in place, but it hasn’t been implemented yet. Symptoms consist of a much longer boot process, and failure to identify any devices attached to the Marvell controllers.