Lost ata interrupt, usb hid (mouse keyboard) freezes

Bug #576496 reported by d0pp on 2010-05-06
70
This bug affects 14 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

****** NOACPI fix this issue ******

Mouse and keyboard freezes randomly. ata<x>.00 looses input. Is still able to control the computer from via SSH. Tried to unload the module usbhid but it won't unload.

In /var/log/messages this happens
May 4 21:13:54 desktop-linux kernel: [ 258.040020] ata3: lost interrupt (Status 0x51)
May 4 21:13:59 desktop-linux kernel: [ 263.040026] ata3.00: qc timeout (cmd 0xa0)
May 4 21:13:59 desktop-linux kernel: [ 263.040038] sr 2:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
May 4 21:13:59 desktop-linux kernel: [ 263.040072] ata3: soft resetting link
May 4 21:13:59 desktop-linux kernel: [ 263.260235] ata3.00: configured for UDMA/33
May 4 21:14:04 desktop-linux kernel: [ 268.260021] ata3.00: qc timeout (cmd 0xa0)
May 4 21:14:04 desktop-linux kernel: [ 268.260028] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
May 4 21:14:04 desktop-linux kernel: [ 268.260049] ata3: soft resetting link
May 4 21:14:05 desktop-linux kernel: [ 268.480233] ata3.00: configured for UDMA/33
May 4 21:14:10 desktop-linux kernel: [ 273.480022] ata3.00: qc timeout (cmd 0xa0)
May 4 21:14:10 desktop-linux kernel: [ 273.480028] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
May 4 21:14:10 desktop-linux kernel: [ 273.480032] ata3.00: limiting speed to UDMA/33IO3
May 4 21:14:10 desktop-linux kernel: [ 273.480051] ata3: soft resetting link
May 4 21:14:10 desktop-linux kernel: [ 273.700235] ata3.00: configured for UDMA/33
May 4 21:14:15 desktop-linux kernel: [ 278.700023] ata3.00: qc timeout (cmd 0xa0)
May 4 21:14:15 desktop-linux kernel: [ 278.700028] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
May 4 21:14:15 desktop-linux kernel: [ 278.700031] ata3.00: disabled
May 4 21:14:15 desktop-linux kernel: [ 278.700058] ata3: soft resetting link
May 4 21:14:15 desktop-linux kernel: [ 278.860062] ata3: EH complete

Have had the problems since I installed ubuntu 10.04-beta2 x64 up to the freshest update.

The problem is discussed here:
http://ubuntuforums.org/showthread.php?p=9236636&posted=1#post9236636

Israel Lacerra (israeldl) wrote :

I have the same problem. But my keyboard and mouse are ps/2. On Ubuntu 9.10 they worked.

ata5: lost interrupt (Status 0x51)
[ 980.000034] ata5.00: qc timeout (cmd 0xa0)
[ 980.000046] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 980.000052] sr 5:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
[ 980.000066] ata5.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 980.000068] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[ 980.000072] ata5.00: status: { DRDY ERR }
[ 980.000097] ata5: soft resetting link
[ 980.164344] ata5: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:600:0x13)
[ 980.180257] ata5.00: configured for UDMA/66
[ 985.180030] ata5.00: qc timeout (cmd 0xa0)
[ 985.180037] ata5.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 985.180062] ata5: soft resetting link
[ 985.348338] ata5: nv_mode_filter: 0x1f39f&0x1f39f->0x1f39f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:600:0x13)
[ 985.360260] ata5.00: configured for UDMA/66
[ 990.364027] ata5.00: qc timeout (cmd 0xa0)
[ 990.364034] ata5.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 990.364040] ata5.00: limiting speed to UDMA/66IO3
[ 990.364064] ata5: soft resetting link
[ 990.524333] ata5: nv_mode_filter: 0x1f38f&0x1f39f->0x1f38f, BIOS=0x1f000 (0xc5000000) ACPI=0x1f01f (30:600:0x13)
[ 990.544266] ata5.00: configured for UDMA/66
[ 995.540030] ata5.00: qc timeout (cmd 0xa0)
[ 995.540037] ata5.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 995.540041] ata5.00: disabled
[ 995.540075] ata5: soft resetting link
[ 995.696079] ata5: EH complete

Israel Lacerra (israeldl) wrote :

Problem resolved with latest updates of Lucid

Israel Lacerra (israeldl) wrote :

>Problem resolved with latest updates of Lucid
Actually, the problem persists

d0pp (d0pp) wrote :

Yesterday i installed the standard 32 bit version of Ubuntu 10.04, and haven't had any crashes yet. It's probably more of a workaround than a fix and since I'm having 4GB of ram maybe not 100% ideal. At least the kernel in the 32bit version supports PAE so this appears to be the best solution for me at the moment.

Carl Wright (cawright) wrote :

i am getting the same errors in my logs when my machine freezes.

ay 13 17:24:58 user-desktop kernel: [ 462.390064] NVRM: Xid (0001:00): 8, Channel 00000004
May 13 17:26:13 user-desktop kernel: [ 537.040028] ata3: lost interrupt (Status 0x51)
May 13 17:26:18 user-desktop kernel: [ 542.042183] ata3.00: qc timeout (cmd 0xa0)
May 13 17:26:18 user-desktop kernel: [ 542.042192] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
May 13 17:26:18 user-desktop kernel: [ 542.042196] sr 2:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
May 13 17:26:18 user-desktop kernel: [ 542.042207] ata3.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
May 13 17:26:18 user-desktop kernel: [ 542.042208] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
May 13 17:26:18 user-desktop kernel: [ 542.042211] ata3.00: status: { DRDY ERR }
May 13 17:26:18 user-desktop kernel: [ 542.042230] ata3: soft resetting link
May 13 17:26:18 user-desktop kernel: [ 542.225353] ata3: nv_mode_filter: 0x1f39f&0x1f3ff->0x1f39f, BIOS=0x1f000 (0xc5000000) ACPI=0x0
May 13 17:26:18 user-desktop kernel: [ 542.270225] ata3.00: configured for UDMA/66
May 13 17:26:23 user-desktop kernel: [ 547.270034] ata3.00: qc timeout (cmd 0xa0)
May 13 17:26:23 user-desktop kernel: [ 547.270039] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
May 13 17:26:23 user-desktop kernel: [ 547.270059] ata3: soft resetting link
May 13 17:26:23 user-desktop kernel: [ 547.442523] ata3: nv_mode_filter: 0x1f39f&0x1f3ff->0x1f39f, BIOS=0x1f000 (0xc5000000) ACPI=0x0
May 13 17:26:23 user-desktop kernel: [ 547.482629] ata3.00: configured for UDMA/66
May 13 17:26:28 user-desktop kernel: [ 552.483800] ata3.00: qc timeout (cmd 0xa0)
May 13 17:26:28 user-desktop kernel: [ 552.483806] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
May 13 17:26:28 user-desktop kernel: [ 552.483810] ata3.00: limiting speed to UDMA/66:PIO3
May 13 17:26:28 user-desktop kernel: [ 552.483830] ata3: soft resetting link
May 13 17:26:28 user-desktop kernel: [ 552.660297] ata3: nv_mode_filter: 0x1f38f&0x1f3ff->0x1f38f, BIOS=0x1f000 (0xc5000000) ACPI=0x0
May 13 17:26:29 user-desktop kernel: [ 552.700232] ata3.00: configured for UDMA/66
May 13 17:26:34 user-desktop kernel: [ 557.703049] ata3.00: qc timeout (cmd 0xa0)
May 13 17:26:34 user-desktop kernel: [ 557.703055] ata3.00: TEST_UNIT_READY failed (err_mask=0x5)
May 13 17:26:34 user-desktop kernel: [ 557.703058] ata3.00: disabled
May 13 17:26:34 user-desktop kernel: [ 557.703085] ata3: soft resetting link
May 13 17:26:34 user-desktop kernel: [ 557.860076] ata3: EH complete
May 13 17:28:24 user-desktop kernel: [ 668.420096] NVRM: Xid (0001:00): 8, Channel 00000003
May 13 17:28:32 user-desktop kernel: [ 676.430093] NVRM: Xid (0001:00): 8, Channel 00000003
May 13 17:28:49 user-desktop kernel: [ 693.430094] NVRM: Xid (0001:00): 8, Channel 00000004

Carl Wright (cawright) wrote :

and by the way,I can confirm this issue still exists, my machine is fully updated.

d0pp (d0pp) wrote :

It's been some days now since I changed from the 64bit to the 32bit version and I haven't had any crashes since this.

Lisa Nelson (lisa50469) wrote :

I'm also fully updated, and have the same issue.

d0pp (d0pp) wrote :

I just had a new crash. This is the first freeze I have experienced since I installed the 32bit system 10 days ago. The errors are the same as before.

Nick Lawson (vektuz-gmail) wrote :

This problem affects me too. However, its different, it only affects USB devices on the same IRQ as the SATA_NV driver:

 23: 786792 0 IO-APIC-fasteoi ohci_hcd:usb2, sata_nv

In my case, that OHCI_HCD (usb hub) is actually an external hub built into my monitor. Once I moved my mouse and keyboard away from that hub, they were no longer affected by this issue. (However, I still get the issue, and the computer freezes up while its doing the soft reset).

It seems pretty random, and I scanned for bad blocks on the HDD (badblocks) and found none.

The other thing different is that for me it didn't completely freeze the mouse, but it did lower the sample rate to like 2hz, so the mouse moved very slowly (and typing was very delayed).

Nick Lawson (vektuz-gmail) wrote :

Oh. Some more information: Setting the computer to suspend (or hibernate) and then waking it up again, caused the devices to continue working normally (for a while)

Peter Steller (psteller) wrote :

I have the same problem with fully updated Lucid 64-bit and PS/2 keyboard/mouse.

Snahrck (hansenclever) wrote :

I have a similar problem. It occurs occasionally disabling me from writing to sata disk. Most times it occurs when I plug an USB device. I'm using an updated version of Lucid: 2.6.32-22-generic-pae #36-Ubuntu SMP Thu Jun 3 23:14:23 UTC 2010 i686 GNU/Linux

dmesg logs when it occurs:

[ 41.952008] eth2: no IPv6 routers present
[ 6755.000032] ata4: lost interrupt (Status 0x50)
[ 6786.000039] ata4: lost interrupt (Status 0x51)
[ 6791.000048] ata4.00: qc timeout (cmd 0xa0)
[ 6791.000063] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 6791.000070] sr 3:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
[ 6791.000086] ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 6791.000088] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[ 6791.000096] ata4.00: status: { DRDY ERR }
[ 6791.000124] ata4: soft resetting link
[ 6791.164366] ata4: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)
[ 6791.180285] ata4.00: configured for UDMA/33
[ 6796.180030] ata4.00: qc timeout (cmd 0xa0)
[ 6796.180038] ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 6796.180064] ata4: soft resetting link
[ 6796.345243] ata4: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)
[ 6796.360293] ata4.00: configured for UDMA/33
[ 6801.360034] ata4.00: qc timeout (cmd 0xa0)
[ 6801.360040] ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 6801.360044] ata4.00: limiting speed to UDMA/33:PIO3
[ 6801.360065] ata4: soft resetting link
[ 6801.524391] ata4: nv_mode_filter: 0x738f&0x739f->0x738f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)
[ 6801.540294] ata4.00: configured for UDMA/33
[ 6806.540028] ata4.00: qc timeout (cmd 0xa0)
[ 6806.540036] ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 6806.540040] ata4.00: disabled
[ 6806.540075] ata4: soft resetting link
[ 6806.696082] ata4: EH complete

Mariusz Domański (mario.7) wrote :

New kernel seems to fix this bug for me (got exact same 'lost interrupt' errors in logs):
http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/
After about 2 days of (not too intensive) testing everything seems to be working fine. New kernel also fixed some issues with DVD-ROM not working properly before.

Fabio Marzocca (thesaltydog) wrote :

Same problem as above and same syslog messages.
It occurs every time I plug in an esxternal HD drive or a mp3 reader in any USB port.
I suspect it is a sort of IRQ conflict, but I don't know where to troubleshoot.

Kim Tyler (ktyler) wrote :

I have the problem where cd/dvd drives go "dead" when being accessed, either for data or status. If access for data, the log shows many "VFS: busy inodes on changed media or resized disk sr0" and the cd/dvd drive is dead, while if for status, the drives (I have 2 cd/dvd drives) die silently. My problems always has something like "lost interrupt (Status 0x51)" at the start of the problems. It appears not to happen with lucid live CD, or with meerkat live CD (beta) or meerkat USB (beta).
My dist is lucid AMD 64 kernel fully updated. I also have nvidia video.

I will try new kernel from above and report, since I really need a fix for this.

Kim Tyler (ktyler) wrote :

I tried kernel above (http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-lucid/) and IT HAS THE IDENTICAL PROBLEM. This seems to be a real showstopper for me. I need the lucid version of the kernel (so I don't keep having to compile the kernel and/or drivers), but lucid breaking webcam and now the cd/dvd drives, it is a complete disaster for me.

Snahrck (hansenclever) wrote :
Download full text (4.7 KiB)

I have the same problem (see below) and my computer is up to date. My mouse (USB) and keyboard (PS/2) won't freeze. The problem happens at random, but frequently is triggered by plugin in a usb flash drive. Sometimes when it happens if I have a terminal opened every command returns "Bus error". I can't even shutdown or restart the machine.

"nv_mode_filter" does it have something to do with nvidia chipset. Maybe it is a driver issue?

Do you have virtual box installed? Because I do and this guy had too and fixed a similar problem by uninstalling virtual box:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/231575/comments/51

dmesg:
[ 3504.000025] ata4: lost interrupt (Status 0x50)
[ 3535.000038] ata4: lost interrupt (Status 0x51)
[ 3540.000038] ata4.00: qc timeout (cmd 0xa0)
[ 3540.000050] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 3540.000055] sr 3:0:0:0: CDB: Test Unit Ready: 00 00 00 00 00 00
[ 3540.000070] ata4.00: cmd a0/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[ 3540.000071] res 51/20:03:00:00:00/00:00:00:00:00/a0 Emask 0x5 (timeout)
[ 3540.000075] ata4.00: status: { DRDY ERR }
[ 3540.000101] ata4: soft resetting link
[ 3540.164359] ata4: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)
[ 3540.180297] ata4.00: configured for UDMA/33
[ 3545.180029] ata4.00: qc timeout (cmd 0xa0)
[ 3545.180037] ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 3545.180063] ata4: soft resetting link
[ 3545.344365] ata4: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)
[ 3545.360297] ata4.00: configured for UDMA/33
[ 3550.360037] ata4.00: qc timeout (cmd 0xa0)
[ 3550.360045] ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 3550.360050] ata4.00: limiting speed to UDMA/33:PIO3
[ 3550.360075] ata4: soft resetting link
[ 3550.524380] ata4: nv_mode_filter: 0x738f&0x739f->0x738f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)
[ 3550.540290] ata4.00: configured for UDMA/33
[ 3555.540029] ata4.00: qc timeout (cmd 0xa0)
[ 3555.540036] ata4.00: TEST_UNIT_READY failed (err_mask=0x5)
[ 3555.540040] ata4.00: disabled
[ 3555.540074] ata4: soft resetting link
[ 3555.696079] ata4: EH complete

cat /var/log/debug:
Oct 13 10:22:19 siid00 kernel: [ 3540.164359] ata4: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)
Oct 13 10:22:24 siid00 kernel: [ 3545.344365] ata4: nv_mode_filter: 0x739f&0x739f->0x739f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)
Oct 13 10:22:29 siid00 kernel: [ 3550.524380] ata4: nv_mode_filter: 0x738f&0x739f->0x738f, BIOS=0x7000 (0xc000) ACPI=0x701f (60:600:0x13)

lspci:
lspci
00:00.0 Host bridge: nVidia Corporation Device 0071 (rev a3)
00:00.1 RAM memory: nVidia Corporation Device 007f (rev a1)
00:00.2 RAM memory: nVidia Corporation Device 0075 (rev a1)
00:00.3 RAM memory: nVidia Corporation Device 006f (rev a1)
00:00.4 RAM memory: nVidia Corporation Device 00b4 (rev a1)
00:01.0 RAM memory: nVidia Corporation Device 0076 (rev a1)
00:01.1 RAM memory: nVidia Corporation Device 0078 (rev a1)
00:01.2 RAM memory: nVidia Corporation Device 0079 (rev a1)
00:01.3 RAM memory: nVidia Corporation Device 007a (rev a1)...

Read more...

Kim Tyler (ktyler) wrote :

Hi there, there is also a bug report #544548.

A work around is to add "noacpi" into the kernel boot line in grub, either from the grub2 boot menu (enter with "e" from the boot menu) or by adding "noacpi" to the /etc/default/grub file, and then update-grub. If you alter the /boot/grub/grub.cfg file directly, it will be overwritten on the next update-grub, eg when you update the kernel.

In my case, the line in the file is :-

GRUB_CMDLINE_LINUX_DEFAULT="noacpi quiet splash"

(NOTE - there is also a noapic parameter, which probably isn't the one you want - I get confused each time)

Kim Tyler (ktyler) wrote :

see also http://www.mjmwired.net/kernel/Documentation/kernel-parameters.txt and look for ALL occurrences of noacpi and acpi (especially acpi=)

description: updated
affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Confirmed

d0pp, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? 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 the development 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 . Please do not test the kernel in the daily folder, but the one all the way at the bottom. 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. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

tags: added: lucid needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
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  Edit
Everyone can see this information.

Other bug subscribers