ICH7 rev 1 SATA controller not supported

Bug #131696 reported by Gaetan Semet
6
Affects Status Importance Assigned to Milestone
Linux
Fix Released
Medium
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
linux-source-2.6.22 (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Bug description:

I've just bought a Gigabyte 945GM-S2 motherboard for Intel Core 2 processor. The SATA chipset in it, Intel 82801 (ICH7 rev 1), doesn't seem to be working with any version of Ubuntu Install CD I've tested. I've tried so far Festy, Edgy and Dapper, and they all have problems with the harddrive : Feisty and Edgy doesn't find a HD at all, and dapper does find the right SATA drive (with the right partition), but fails writing on it.

Here is the dmesg extract on Feisty related to SATA error:

[ 0.000000] Linux version 2.6.20-15-generic (root@palmer) (gcc version 4.1.2 (Ubuntu 4.1.2-0ubuntu4)) #2 SMP Sun Apr 15 07:36:31 UTC 2007 (Ubuntu 2.6.20-15.27-generic)
...
[ 2.893469] SCSI subsystem initialized
[ 2.897624] libata version 2.20 loaded.
[ 2.900296] ata_piix 0000:00:1f.1: version 2.10ac1
[ 2.900312] ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
[ 2.900329] PCI: Setting latency timer of device 0000:00:1f.1 to 64
[ 2.900363] ata1: PATA max UDMA/133 cmd 0x000101f0 ctl 0x000103f6 bmdma 0x0001f000 irq 14
[ 2.906294] ata2: PATA max UDMA/133 cmd 0x00010170 ctl 0x00010376 bmdma 0x0001f008 irq 15
[ 2.906313] scsi0 : ata_piix
[ 2.908392] USB Universal Host Controller Interface driver v3.0
[ 3.230801] ata1.00: ATAPI, max UDMA/66
[ 3.395653] ata1.00: configured for UDMA/66
[ 3.396005] scsi1 : ata_piix
[ 3.563402] ATA: abnormal status 0x7F on port 0x00010177
[ 3.570325] scsi 0:0:0:0: CD-ROM PIONEER DVD-RW DVR-108 1.18 PQ: 0 ANSI: 5
[ 3.570585] ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ]
[ 3.570606] ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
[ 3.570618] PCI: Setting latency timer of device 0000:00:1f.2 to 64
[ 3.570641] ata3: SATA max UDMA/133 cmd 0x0001d000 ctl 0x0001d402 bmdma 0x0001e000 irq 19
[ 3.570662] ata4: SATA max UDMA/133 cmd 0x0001d800 ctl 0x0001dc02 bmdma 0x0001e008 irq 19
[ 3.570672] scsi2 : ata_piix
[ 3.740247] ATA: abnormal status 0xD0 on port 0x0001d007
[ 3.740256] scsi3 : ata_piix
[ 3.904942] ATA: abnormal status 0x7F on port 0x0001d807

I've also tested Parted Magic boot CD and it doesn't work either. Does ICH7 rev 1 chipset not fully supported by last kernels?

This bug may be related to the following bugs already filled about ICH7 support but the behaviour is a bit different : I've never found a way of getting something writen on my SATA drive, so no install can be performed:

- https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/56727
- https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/53754
- https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/92757

Many thanks in advance for your support or any advice, next are some usefull system info:

lspci :

00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
00:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port (rev 02)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 01)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 01)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 01)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 01)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 01)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01)
00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller IDE (rev 01)
00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01)
01:00.0 VGA compatible controller: nVidia Corporation Unknown device 0421 (rev a1)
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)

lspci -vvx for ATA :

00:1f.2 IDE interface: Intel Corporation 82801GB/GR/GH (ICH7 Family) Serial ATA Storage Controller IDE (rev 01) (prog-if 8f [Master SecP SecO PriP PriO])
    Subsystem: Giga-byte Technology Unknown device b002
    Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
    Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
    Latency: 0
    Interrupt: pin B routed to IRQ 19
    Region 0: I/O ports at d000 [size=8]
    Region 1: I/O ports at d400 [size=4]
    Region 2: I/O ports at d800 [size=8]
    Region 3: I/O ports at dc00 [size=4]
    Region 4: I/O ports at e000 [size=16]
    Capabilities: <access denied>
00: 86 80 c0 27 05 00 b0 02 01 8f 01 01 00 00 00 00
10: 01 d0 00 00 01 d4 00 00 01 d8 00 00 01 dc 00 00
20: 01 e0 00 00 00 00 00 00 00 00 00 00 58 14 02 b0
30: 00 00 00 00 70 00 00 00 00 00 00 00 0b 02 00 00

lsmod
Module Size Used by
binfmt_misc 12680 1
rfcomm 40856 0
l2cap 25728 5 rfcomm
bluetooth 55908 4 rfcomm,l2cap
ppdev 10116 0
lp 12452 0
acpi_cpufreq 10056 1
cpufreq_userspace 5408 0
cpufreq_stats 7360 0
cpufreq_powersave 2688 0
cpufreq_ondemand 9228 2
freq_table 5792 3 acpi_cpufreq,cpufreq_stats,cpufreq_ondemand
cpufreq_conservative 8200 0
tc1100_wmi 8068 0
sony_acpi 6284 0
pcc_acpi 13184 0
dev_acpi 12292 0
video 16388 0
sbs 15652 0
i2c_ec 5888 1 sbs
dock 10268 0
container 5248 0
button 8720 0
battery 10756 0
asus_acpi 17308 0
backlight 7040 1 asus_acpi
ac 6020 0
ipv6 268704 10
fuse 46612 1
snd_hda_intel 21912 1
snd_hda_codec 205440 1 snd_hda_intel
snd_pcm_oss 44544 0
snd_mixer_oss 17408 1 snd_pcm_oss
snd_pcm 79876 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
af_packet 23816 2
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 23684 2 snd_pcm,snd_seq
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
xpad 9988 0
snd 54020 12 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 8672 1 snd
i2c_core 22784 1 i2c_ec
parport_pc 36388 1
parport 36936 3 ppdev,lp,parport_pc
usblp 14848 0
intel_agp 25116 1
iTCO_wdt 11812 0
psmouse 38920 0
pcspkr 4224 0
agpgart 35400 1 intel_agp
iTCO_vendor_support 4868 1 iTCO_wdt
serio_raw 7940 0
snd_page_alloc 10888 2 snd_hda_intel,snd_pcm
shpchp 34324 0
pci_hotplug 32576 1 shpchp
evdev 11008 5
tsdev 8768 0
sd_mod 23428 0
usb_storage 72256 0
usbhid 26592 0
hid 27392 1 usbhid
libusual 17936 1 usb_storage
squashfs 49028 1
loop 17800 2
unionfs 74020 1
nls_cp437 6784 1
isofs 36284 1
sg 36252 0
sr_mod 17060 1
cdrom 37664 1 sr_mod
ehci_hcd 34188 0
r8169 32392 0
uhci_hcd 25360 0
ata_piix 15492 1
ata_generic 9092 0
libata 125720 2 ata_piix,ata_generic
scsi_mod 142348 5 sd_mod,usb_storage,sg,sr_mod,libata
generic 5124 0 [permanent]
usbcore 134280 8 xpad,usblp,usb_storage,usbhid,libusual,ehci_hcd,uhci_hcd
thermal 14856 0
processor 31048 2 acpi_cpufreq,thermal
fan 5636 0
fbcon 42656 0
tileblit 3584 1 fbcon
font 9216 1 fbcon
bitblit 6912 1 fbcon
softcursor 3200 1 bitblit
vesafb 9220 0
capability 5896 0
commoncap 8192 1 capability

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

Added complete dmesg

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

For info, the complete dmesg for gutsy Alpha 3. The "ATA: abnormal status" doesn't appear, but the drive is not recognised (but it is well physically connected, grub can browse the partitions).

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thank you for your bug report.

Stibbons:
Can you indicate whether a Gutsy LiveCD ( http://cdimage.ubuntu.com/releases/gutsy/tribe-4/ ) shows the same problem (error messages in dmesg and can't see partitions)?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Punting from Ubuntu -> linux-source-2.6.20 and setting to Incomplete pending reply from Stibbons.

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

I'll attach a complete dmesg ASAP for Gutsy Gibbons Live CDs tribe 4.

Install of Dapper Drake worked fine (first install failed on grub setup, I tryed a second time and it worked completly).

Attach is the dmesg

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

(I believe I might be able to test a Dell 9200 so if a live CD shows the problem on Gutsy I should be able to confirm)

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

Here is the dmesg for Gutsy Tribe 4. There doesn't seem to have any problem in it (no "abnormal..." things), no error, but the connected hard drive is not found by the installer.

Some (http://forum.ubuntu-fr.org/viewtopic.php?id=139007, French !) advised me to change the SATA controller mode ("Enhanced" or "Auto"), but this doesn't change anything.

I'm now using Feisty with old kernel driver (2.6.15-23) and the system starts. If I use the current kernel version 2.6.20, the startup fails after scsi enumeration.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Stibbon:
Just for my benefit, are you doing anything like RAIDing disks together using fakeraid?

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

nothing. I have a SATA I disk with 6 partitions on it (2 primary 4 logical):
/dev/sda1 * 1 12 96358+ 83 Linux
/dev/sda2 135 24321 194282077+ 5 Extended
/dev/sda4 13 134 979965 82 Linux swap / Solaris
/dev/sda5 135 1958 14651248+ 83 Linux
/dev/sda6 1959 24321 179630766 83 Linux

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

Do you think it is possible to port the ata_piix module from kernel 2.6.15 with the 2.6.20 (if this comes from this module...)? I have quite a good experience in C dev but never jumped into the kernel itself, but if I can bring any help, I'll be pleased. :)

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Stibbons:
: ) I'm not employed by Ubuntu/Cannonical (but I can program) so this advice may be wrong. It sounds like a fix for your card needs to be made but a straight port of the .15 module to .20 is unlikely to work because the kernel interfaces have changed (and thus you will need to modify the .15 to call the right functions and any new functions will need to be inserted etc.). You can see a history of the very latest ata_piix module from upstream by looking at http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=drivers/ata/ata_piix.c;h=a78832ea81fa0f5cc9460cca362f498307820cb1;hb=HEAD . I would also expect the .20 driver to have support for newer cards and perhaps new features too.

The fastest way to get a fix is to narrow down what change broke your card. The traditional way of doing this is to take a working driver and a broken driver then do bisection until you find the change that broke things. This is time consuming but ultimately tends to have good results if you can narrow it down to one patch (these days it has become easier because the kernel source code is managed with the version control software git). Doing this is beyond the scope of this comment though.

The other thing you can do if you are willing to test vanilla upstream kernels is to see whether the latest vanilla kernel has the issue. If it does you can then say so in the upstream kernel bugzilla ( http://bugzilla.kernel.org/ ).

Revision history for this message
Amit Kucheria (amitk) wrote :

Have you already tried another distribution? Is this a problem present only in Ubuntu?

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

I've tryed Parted Magic, which is based on gentoo (kernel 2.6.22) I think... and it doesn't see my harddrive as well.
I've not tried other distribution. Which live CD do you advise?

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

I'm trying right now Mandriva Spring 2007 and this is the same thing, the SATA Controller doesn't find any harddrive.

Attached the dmesg (kernel : Linux localhost 2.6.17-13mdv #1 SMP Fri Mar 23 15:18:36 EDT 2007 x86_64 Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz GNU/Linux)

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

Hello everybody. Do you have some news about this bug?
I manage to compile the Kernel 2.6.15 and the nvidia driver together so my computer is usable, but I cannot upgrade to the latest version. Should I do something else to complete my report and have the bug status move to "confirmed"?

I've tried so far:
- Ubuntu Feisty/Edgy
- Mandriva x64 and x32
- Gentoo Live CD
- Parted Magic live CD

They all doesn't find any hard drive on my SATA controller. Just Dapper does work, and I'm using its kernel (2.6.15) on Feisty.
Thanks all

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Stibbons:
Given all the testing you've done so far I would strong recommend filing this issue on the http://bugzilla.kernel.org/ . If you can build your own kernels that's a good place to go to get this fixed...

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Punting from linux-source-2.6.20 -> linux-source-2.6.22 because this has been reproduced on Gutsy. Setting back to new as reporter replied to queries.

Changed in linux-source-2.6.20:
status: Incomplete → New
Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

Posted on kernel bug tracker : http://bugzilla.kernel.org/show_bug.cgi?id=8944
Thanks for your support.

Changed in linux:
status: Unknown → In Progress
Changed in linux:
status: In Progress → Invalid
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Stibbons:
Why did you close the upstream bug INVALID? I know bug posting can be frustrating but I think you're were going the right about getting your issue resolved...

Revision history for this message
Gaetan Semet (gaetan-xeberon) wrote :

I did not wanted to close the bug, I was quite surprised when I receive the following mail :
From : Bug Watch Updater <email address hidden>
To: gaetan
Object : [Bug 131696] Re: ICH7 rev 1 SATA controller not supported
   ** Changed in: linux
         Status: In Progress => Invalid

I think I miss entered my bug report on the kernel bugzilla. I've reopened it.

I'm currently quite happilly following the bug 8944 for resolution (I have a working station, with an old kernel indeed, but everything on it works, printer, compiz, etc, so it's not like if I couldn't use my lovely Pinguin). Thanks for your attention :)

PS: not everything, I'm missing the dual core support, but this can wait a bit...

Changed in linux:
status: Invalid → Confirmed
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Sitsofe, please don't set bugs back to New when the reporter provides information. It should be moved to Confirmed if the information seems appropriate/complete or left at incomplete if you have asked for more information. The developers will rarely look at bugs in new (at least while there is already a big pile in Confirmed). See: https://wiki.ubuntu.com/Bugs/WorkFlow

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Henrik:
First up - my apologies for not following protocol. The reason I set it back to New is because I don't have the power to assign a bug to someone (see https://wiki.ubuntu.com/KernelTeamBugPolicies ) nor would I know who to assign it to. In the past I used to set kernel bugs to Confirmed and then someone pointed me to the KernelTeamBugPolicies at which point I was forced to go back and change all the bugs I set to Confirmed (but couldn't assign) back to New.

Can you indicate what the correct thing to do is? I was aware of WorkFlow but thought it was superseded by individual team's policies (having sub-policies does make life more difficult though - you never know whose toes you are going to stand on next)...

Changed in linux:
status: Confirmed → In Progress
Changed in linux:
status: In Progress → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
Bryan Wu (cooloney) wrote :

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

-Bryan

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
Changed in linux:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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