linux-image-2.6.17-[34]-686 doesn't boot, libata error

Screenshot of first part of trace

Screenshot of the second part of trace

I attached screenshots of trace. Forgot to mention the exact version number of kernel image:

Package: linux-image-2.6.17-3-686
Installed-Size: 60644
Architecture: i386
Source: linux-source-2.6.17
Version: 2.6.17-3.4

Confirmed - I have an identical trace.

I can confirm this behaviour on a thinkpad x41 with
0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)

Additional to the null pointer exception the HDD LED is glowing all the time

Also 2.6.17-2 works, this only happens with 2.6.17-3

Forgot to mention: My system is a Dell XPS M1710 Laptop with

0000:00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA Storage Controllers cc=IDE (rev 01)

Confirm here too.
My laptop is a Dell inspiron 700m with EIDE storage.
As others say, 2.6.17-2 works fine.

Confirmed. Running an Acer Aspire 5272Wlmi, /w a sata drive. 2.6.17-2 works, but 2.6.17-3, and the kernel from git both fail with the exact same error.

Applies to linux-image-2.6.17-4-686 version 2.6.17-4.5 too.

Confirmed. linux-image-2.6.17-4-686 version 2.6.17-4.5 does not boot on Dell D610.

Confirmed. I have an identical trace to the second trace screenshot that was posted here.

Jie Zhang wrote:
> Confirmed. linux-image-2.6.17-4-686 version 2.6.17-4.5 does not boot on
> Dell D610.

It might be worth mentioning that D610 has an PATA drive, but it is used
through a SATA controller (i found this a bit odd). I don't know if the
HD is used like this on other computers affected.

- S

linux-image-2.6.17-4-686 version 2.6.17-4.6 doesn't work either (the new 4.6 not 4.5).

Responding to Sami Haahtinen, I can confirm this bug occurs on my system, which is a T43p with exact same storage device hackery - PATA hard drive access throuhg a SATA->PATA bridge, May this be the culprit that triggers the bug?

How can you tell that your system has SATA -> PATA bridge? I'd like to check mine.

Mikael Nilsson wrote:
> How can you tell that your system has SATA -> PATA bridge? I'd like to
> check mine.

Without taking apart your computer, you should be able to see by
checking the following things. Although I can't tell how reliable these
are since i don't have access to a PATA only HW at the moment.

* Your HD shows up as a SCSI device (sda)
* kernel reports ata1 as PATA device (dmesg will tell)

For me the line that kernel spits out is:
ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14

Another way is to see what IDE controller you have:
ressu@denial:~/ > lspci | grep IDE
0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA
Controller (rev 03)

Then check check the make and model of your HD to see if it's a SATA drive.

If someone has an easier way, please fill in. ;)

- S

On tor, 2006-07-06 at 13:57 +0000, Sami Haahtinen wrote:
> * Your HD shows up as a SCSI device (sda)

Check.

> * kernel reports ata1 as PATA device (dmesg will tell)
>
>
> For me the line that kernel spits out is:
> ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14

Check:

ata1: PATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14

> Another way is to see what IDE controller you have:
> ressu@denial:~/ > lspci | grep IDE
> 0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA
> Controller (rev 03)

Check:
IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) Serial ATA
Storage Controllers cc=IDE (rev 01)

>
> Then check check the make and model of your HD to see if it's a SATA
> drive.

Uhm, how do I tell? I'm getting confused - I thought I was using a SATA
drive. Now it seems it's an IDE drive being presented as a SATA drive.
Or did I misunderstand something?

/Mikael

--
Plus ça change, plus c'est la même chose

On tor, 2006-07-06 at 14:22 +0000, Mikael Nilsson wrote:

> Uhm, how do I tell? I'm getting confused - I thought I was using a SATA
> drive. Now it seems it's an IDE drive being presented as a SATA drive.
> Or did I misunderstand something?

The drive itself says "Serial ATA", so that's clear now.

My Dell D610:

Harddrive:
ata1: SATA max UDMA/133 cmd 0x1F0 ctl 0x3F6 bmdma 0xBFA0 irq 14
DVD drive:
ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xBFA8 irq 15

Looks like bug 51584

I'm marking this bug as duplicate of bug 51488, though this bug has more information. There are already duplicates marked for that bug. Lets make it the master bug ;)

It is fixed now.

The 18 month support period for Edgy Eft 6.10 has reached its end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. 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!