hda-intel: spurious response 0x0:0x0, last cmd=0x5f0700... then hard system crash

[james_fried]

Dell Vostro Desktop 430 MT (D064302) - runs perfectly 99.9% of the time, but hard crashes randomly every other day or so leaving about 100 lines of the following in kernel.log:

kernel: [ 2187.925261] hda-intel: spurious response 0x0:0x0, last cmd=0x5f0700

Only a hard power down can recover the system.

Any help much appreciated - this bug is making this machine (which is the main machine in my office) undependable.

J

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-24-generic 2.6.32-24.38
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-24.38-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 1: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 1: Headset [Logitech USB Headset], device 0: USB Audio [USB Audio]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: james 1370 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xfba00000 irq 16'
   Mixer name : 'Nvidia ID b'
   Components : 'HDA:10de000b,10de0101,00100100'
   Controls : 0
   Simple ctrls : 0
Card0.Amixer.values:

Card1.Amixer.info:
 Card hw:1 'Headset'/'Logitech Logitech USB Headset at usb-0000:00:1d.0-1.8, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0a0c'
   Controls : 6
   Simple ctrls : 2
Date: Thu Jul 29 15:11:27 2010
Frequency: Once a day.
HibernationDevice: RESUME=UUID=c79de6b6-4453-4d43-b065-631f852d1959
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
MachineType: Dell Inc. Vostro 430
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-24-generic root=UUID=cbde1b13-7e5f-435b-adef-75decdcfe19a ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34.1
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
dmi.bios.date: 03/15/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.0.3
dmi.board.name: 054KM3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.0.3:bd03/15/2010:svnDellInc.:pnVostro430:pvr00:rvnDellInc.:rn054KM3:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.name: Vostro 430
dmi.product.version: 00
dmi.sys.vendor: Dell Inc.

[kernel-janitor (kernel-janitor)]

Hi james_fried,

If you could also please 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.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[james_fried (me-jamescooke)]

Hi,

I understand the need to see if the bug occurs in the latest kernel. I've tried the upstream kernel and it runs on the machine, and in the short while that I ran the machine (1 hour or so) the crash didn't occur.

Since this is a production machine, I need to keep it running on the full nvidia driver, but it doesn't appear to be supported by the upstream kernel, so I've had to roll back to keep both screens and good resolution running.

Instead I'm now testing with a newer kernel from kernel.ubuntu.com (2.6.33) and it hasn't crashed so far today. I'll update on here if it appears to be a fix - but the crash is happening very sporadically.

J

[james_fried (me-jamescooke)]

Hi there,

I've been testing different Kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/ - so far everything up to and including 2.6.35.rc6.maverick has crashed in the same way. Attached are the error messages from the kern.log - some different things are going one depending on the kernel in use...

-- 2.6.35-020635rc6-generic (maverick) - the newest kernel I've tested so far, kern.log.start-to-crash.2.6.35-020635rc6-generic.txt shows the full kern.log from boot to crash. last cmd is now 0x4f0d00.

If there's a version that I can run of 2.6.36 that will support the nvidia drivers please let me know so I can test.

J

[james_fried (me-jamescooke)]

more info showing crash on 2.6.35-020635rc1-generic (lucid)... the wireless card gets deauthenticated?

[Inácio Alves (inacioufc)]

Hi,

I'm having the same problem. I have a Dell Vostro Desktop 230 slim with a core2Quad processor and i get the message "hda-intel: spurious response 0x0:0x0, last cmd=0x5f0700" too.

I need press <ALT>+<print Screen>+<B> to reboot the system.

[Inácio Alves (inacioufc)]

Hi, i search this expression "spurious response" in the source kernel and the only match was in sound/pci/hda/hda_intel.c file.
I have downloaded the 2.6.35.4 version from kernel.org and realize the compiling proccess.
At this moment i am up 1 hour and not get this message.

I will continue up to test. I think that this problem is related with intel sound module.

[Inácio Alves (inacioufc)]

Well,

My system was up to 3 hours, but crashs again.
In this moment i disable the 'audio device' in setup config to see if i get no crash.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]