Bug 1062463 - Marvell 88SE91xx SATA 3 (6 Gbps) controller not detected [NEEDINFO]
Summary: Marvell 88SE91xx SATA 3 (6 Gbps) controller not detected
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-07 00:38 UTC by Marlos de Mendonça Corrêa
Modified: 2014-12-10 15:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-12-10 15:01:21 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 735251 0 unspecified CLOSED Marvell 88SE91xx SATA 3 (6 Gbps) controller not detected 2021-02-22 00:41:40 UTC

Internal Links: 735251

Description Marlos de Mendonça Corrêa 2014-02-07 00:38:46 UTC
Description of problem:
I can`t install Fedora 20 on my Asus Rampage III Black Edition because the SATA 3 HDs arent detected.

Version-Release number of selected component (if applicable):
Fedora 20 - Kernel 3.11.10-301 and newer


Reproductibility: Install or Run (Live) Fedora 20 on Asus Rampage III Black Edition (wich has Marvell 88SE91xx SATA 3) and try to detect HDs (2x WDC SATA 3 Velociraptor as RAID 0) on SATA 3 port

  
Actual results: Controller is exhibited with lspci, but none of their HDs are detected. Logs don`t show nothing regardind the SATA 6 HDs


Expected results:
That HDs are properly detected.


Additional info:
If I do /bin/echo 1b4b 91a2 > /sys/bus/pci/drivers/ahci/new_id my SATA Controller is recognized correctly, but anaconda doesn't show the HDs.

This bugs has been reported since Fedora 15.

See https://bugzilla.redhat.com/show_bug.cgi?id=735251

Comment 1 Justin M. Forbes 2014-02-24 13:59:14 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.13.4-200.fc20.  Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 2 Marlos de Mendonça Corrêa 2014-02-27 01:40:08 UTC
The bug remains valid as all information (workarounds, Reproductibility, etc...) reported. I've tested today, after upgraded to kernel 3.13.4-200.fc20.

Comment 3 Justin M. Forbes 2014-05-21 19:39:41 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.14.4-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you experience different issues, please open a new bug report for those.

Comment 4 Marlos de Mendonça Corrêa 2014-05-21 22:48:15 UTC
The bug remains the same! Nothing changed!

Comment 5 Justin M. Forbes 2014-11-13 16:01:56 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 6 Justin M. Forbes 2014-12-10 15:01:21 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


Note You need to log in before you can comment on or make changes to this bug.