[Bugme-new] [Bug 8933] New: ata_piix blocks ahci from accessing the harddisk

bugme-daemon at bugzilla.kernel.org bugme-daemon at bugzilla.kernel.org
Fri Aug 24 10:58:59 PDT 2007


http://bugzilla.kernel.org/show_bug.cgi?id=8933

           Summary: ata_piix blocks ahci from accessing the harddisk
           Product: Drivers
           Version: 2.5
     KernelVersion: 2.6.23-0.129.rc3.git4
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
        AssignedTo: drivers_other at kernel-bugs.osdl.org
        ReportedBy: romal at gmx.de


Most recent kernel where this bug did not occur: 2.6.17
Distribution: Fedora 6 Core test 3
Hardware Environment: Toshiba Tecra S3
Software Environment: Fedora & Ubunu
Problem Description:

If I boot Fedora 7 or Ubuntu 7 install dvd with kernel parameter noprobe, the
problem can be fixed.

When manually selecting the drivers, the driver ahci has to be loaded first,
that brings up the harddisk. Second the driver ata_piix has to be loaded, to
get
access to the optical drive.

Installed system does not boot.

Steps to reproduce:

lspci
00:00.0 0600: 8086:2590 (rev 03)
00:01.0 0604: 8086:2591 (rev 03)
00:1b.0 0403: 8086:2668 (rev 03)
00:1c.0 0604: 8086:2660 (rev 03)
00:1c.1 0604: 8086:2662 (rev 03)
00:1d.0 0c03: 8086:2658 (rev 03)
00:1d.1 0c03: 8086:2659 (rev 03)
00:1d.2 0c03: 8086:265a (rev 03)
00:1d.3 0c03: 8086:265b (rev 03)
00:1d.7 0c03: 8086:265c (rev 03)
00:1e.0 0604: 8086:2448 (rev d3)
00:1f.0 0601: 8086:2641 (rev 03)
00:1f.1 0101: 8086:266f (rev 03)
00:1f.2 0106: 8086:2653 (rev 03)
01:00.0 0300: 10de:0148 (rev a2)
02:00.0 0200: 11ab:4362 (rev 15)
05:05.0 0280: 8086:4220 (rev 05)
05:0b.0 0607: 104c:8031
05:0b.2 0c00: 104c:8032
05:0b.4 0805: 104c:8034


Thus bug is present in Ubuntu and Fedora, so I don`t think this is a
distribution-specific bug.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


More information about the Bugme-new mailing list