ata errors leading to system hang: "soft resetting link" repeated many times before hang

Bug #672052 reported by daf
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Upon upgrade to Ubuntu 10.10 (and after that, re-installing clean with 10.10, the issue appeared to be gone but has come back), I see a lot of this in /var/log/messages*:
Nov 6 12:31:34 nea kernel: [ 6606.394579] ata1: soft resetting link
Nov 6 12:31:35 nea kernel: [ 6606.728749] ata1.00: configured for UDMA/100
Nov 6 12:31:35 nea kernel: [ 6606.771552] ata1.01: configured for UDMA/66
Nov 6 12:31:35 nea kernel: [ 6606.771580] ata1: EH complete
Nov 6 12:31:49 nea kernel: [ 6620.614128] ata1: soft resetting link
Nov 6 12:31:49 nea kernel: [ 6620.971835] ata1.00: configured for UDMA/100
Nov 6 12:31:49 nea kernel: [ 6621.010734] ata1.01: configured for UDMA/66
Nov 6 12:31:49 nea kernel: [ 6621.010769] ata1: EH complete
Nov 6 12:31:52 nea kernel: [ 6623.621721] ata1: soft resetting link
Nov 6 12:31:52 nea kernel: [ 6624.070317] ata1.00: configured for UDMA/100
Nov 6 12:31:52 nea kernel: [ 6624.110679] ata1.01: configured for UDMA/66
Nov 6 12:31:52 nea kernel: [ 6624.110714] ata1: EH complete
Nov 6 12:32:35 nea kernel: [ 6667.065505] ata1: soft resetting link
Nov 6 12:32:36 nea kernel: [ 6667.691700] ata1.00: configured for UDMA/100
Nov 6 12:32:36 nea kernel: [ 6667.731588] ata1.01: configured for UDMA/66
Nov 6 12:32:36 nea kernel: [ 6667.731626] ata1: EH complete

This is repeated quite often and eventually the machine hangs dead (even sysrq keys don't work).

It seems that the issue is antagonised by my external 2TB drive which was connected on eSata. Powering off and reconnecting the drive via USB (at least 2x slower when working with files!), the problem goes away. The messages can be triggered by copying to the device. The drive is not a problem though -- palimpsest reports the drive is OK and, as I've reported above, connecting on USB makes the problem go away (and the problem wasn't present in prior revisions of the kernel).

This wasn't a problem before 10.10; 9.10 worked fine with this through several iterations of the kernel. It seems that a kernel update around 10.10 has caused the problem to rear its head. Please advise if I can furnish any more info. I'm considering trying a vanilla, latest kernel from kernel.org compiled for my system to see if the problem is there too -- please advise if doing so would be helpful as I'll do so sooner rather than later.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.35
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: daf 2312 F.... pulseaudio
 /dev/snd/pcmC0D0p: daf 2312 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf9ff4000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,14627551,00100001'
   Controls : 33
   Simple ctrls : 19
Date: Sun Nov 7 09:08:01 2010
HibernationDevice: RESUME=UUID=87d4d6ac-7706-44d2-a2b7-76802575b3df
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7551
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=12a288e8-1c77-4d55-96cc-30ae97b7368f ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/zsh
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 1: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UserAsoundrc:
 # ALSA library configuration file

 # Include settings that are under the control of asoundconf(1).
 # (To disable these settings, comment out this line.)
 </home/daf/.asoundrc.asoundconf>
WifiSyslog:

dmi.bios.date: 11/23/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V3.6
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: KA780G-M (MS-7551)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.6:bd11/23/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7551:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnKA780G-M(MS-7551):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0:
dmi.product.name: MS-7551
dmi.product.version: 1.0
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD

Revision history for this message
daf (davydm) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

daf, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, could you please capture the oops following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Capturing_OOPs ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
daf (davydm) wrote :

I haven't seen the bug since I reported the workaround -- simply because I haven't tried to reproduce it, having maintained the workaround on my home machine.

I'll try to get a test done asap -- though the test may prove rather insignificant since I've switched to Linux Mint 12 after:
a) the lack of response on this and other critical bugs that I filed against Ubuntu packages (no offence intended: I tend to get apathetic about being a good user and reporting bugs and trying to be helpful when every bug I submit is only examined 1 or 2 releases later. Again, no offence: I'm not starting a fight here, I'm not trying to flame (though I'm sure it seems that way). I just start to give up).
b) Unity. Yes, that famous flogging horse. Not at all that Unity was created or even set as the default -- even on upgrade! -- more that the implementation of Unity broke everything else I liked, mainly through patches on GTK which broke heaps of the apps I wanted to use and every other desktop environment that I tried at the time. GNOME 3 is no better, and I'm now, sadly, using KDE which, slow and unresponsive as it gets, at least does (mostly) what I want it to do.

Anyway, this isn't really the right place for this and my apathy sets in again. I'll report back on the current state of this bug in Linux Mint 12, which will probably still be relevant to Ubuntu because of the upstream package chain.

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

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.