Hard freeze when reading from SATA disk on promise 20376 sata (MSI k7N2ILSR)

Bug #126704 reported by Jonathan Austin
6
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

This is a problem that has bugged me for as long as I've had this MB, Disk combo and until today when I bought an external SATA disk i couldn't trace it very far.

So. I get hard lockups when reading from the Maxtor Maxline disk on the Promise 20376 onboard SATA RAID controller. I am NOT using any kind of RAID Array and have many different partitions on the disk.

Same disk over USB in external SATA enclosure does NOT cause the lockups

The lockups are what I consider 'hard' lockups -no signal from numlock and I have to use ctrl+alt+sysreq to shut down - they DO work.

I'm sure there are lots of potentially useful commands I could jive the output of - but here are two I thought immediately useful:

$ lsmod | grep prom
sata_promise 12292 0
libata 125208 3 sata_nv,ata_generic,sata_promise
$ uname -r
2.6.20-16-386

I'll attatch lspci output

Revision history for this message
Jonathan Austin (mailforwho) wrote :

NOTE: the disk I _usually_ have on the SATA controller (that I usually can't use without getting a crash) is in an external USB caddy now.

I _just_ noticed that doing long file copy operations from this USB disk it is spewing this message:

usb 2-5: reset high speed USB device using ehci_hcd and address 3

into dmesg about every 2 minutes. I mention it because it might say something about the disk and not the sata controller...? - sorry if I'm barking well up the wrong tree! For sure it isn't crashing now, so something about having the disk connected with SATA is very bad compared to USB! File transfers are slow now...

I've got time to play around with different configs and tools if someone can point me in the right direction and say what data I should collect.

Revision history for this message
David Freitas (jddcef) wrote :

Hi,

Asus P5K-VM, Ubuntu 7.04, SATA HDD, PATA DVDRW, Core2 Duo E6750.

PROBLEM: Installs fine from bootable CD. Freezes (at splash) when starting up though. Just after loading SATA modules.

I don't think this is specific to Core2duo, but Story 17 on https://wiki.ubuntu.com/Core_2_Duo_Support gave me the solution.

>>>>>>> FIX: Grub creates the incorrect entry for root, It was "root=/dev/hda1", but it must be "root=/dev/sda1"! <<<<<<<<<
That fixes the problem on my board!

In the grub menu, you can press "e" to edit the entry, then change to "root=/dev/sda1", then press "b" to boot it. This is a temporary change. When in Ubuntu, do a "sudo gedit /boot/grub/menu.lst" and change it permanently at the bottom of that file somewhere.

Also check your BIOS is the latest version, asus.com said my E6750 was supported with a certain new version which I updated to.

Running "uname -a" once in Ubuntu, gives: "Linux def-desktop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux "

Revision history for this message
David Freitas (jddcef) wrote :

myFIX: Grub creates the incorrect entry for root, It was "root=/dev/hda1", but it must be "root=/dev/sda1"

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
David Freitas (jddcef) wrote :

8.10 works better now, thanks.

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

Thanks David. Per your last comment I'm marking this Fix Released for Intrepid.

Who, since you are the original bug reporter, if this is not resolved for you feel free to change the status back to New.

Changed in linux:
status: Incomplete → Fix Released
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.