[alsa-devel] Issues with HP DV4 laptop sound after Ubuntu Jaunty 9.04 upgrade
Hello again.
I was able to get my internal speakers working for my HP Pavilion Dv4 laptop by following the advice I found in the alsa-devel archives. That advice seems to have worked for quit a few people who found it by a post I made to the Ubuntu Forums.
But now, after I have upgraded my Ubuntu from version 8.10 (when sound worked) to version 9.04, sound no longer works correctly. I have some detailed information about the sequencing and the specific error. Attached is an alsa-info.txt output.
Here's what I'm seeing (extracts from dmesg/kernel logs):
Apr 29 15:13:17 Harlindon kernel: [ 19.937190] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Apr 29 15:13:17 Harlindon kernel: [ 19.937270] HDA Intel 0000:00:14.2: setting latency timer to 64
Apr 30 09:37:09 Harlindon kernel: [ 19.941675] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Apr 30 09:37:09 Harlindon kernel: [ 19.941750] HDA Intel 0000:00:14.2: setting latency timer to 64
May 1 16:06:01 Harlindon kernel: [ 19.852324] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 1 16:06:01 Harlindon kernel: [ 19.852398] HDA Intel 0000:00:14.2: setting latency timer to 64
May 1 16:13:43 Harlindon kernel: [ 20.950985] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 1 16:13:43 Harlindon kernel: [ 20.951060] HDA Intel 0000:00:14.2: setting latency timer to 64
Commit Log for Fri May 1 16:41:58 2009 [Upgrade to Ubuntu Jaunty 9.04]
May 1 17:11:05 Harlindon kernel: [ 20.318416] hda-intel: unable to grab IRQ 0, disabling device May 1 17:11:05 Harlindon kernel: [ 20.318517] HDA Intel: probe of 0000:00:14.2 failed with error -16
May 1 17:14:18 Harlindon kernel: [ 22.977762] hda-intel: unable to grab IRQ 0, disabling device May 1 17:14:18 Harlindon kernel: [ 22.977828] HDA Intel: probe of 0000:00:14.2 failed with error -16
May 1 17:18:49 Harlindon kernel: [ 21.105013] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 1 17:18:49 Harlindon kernel: [ 21.105087] HDA Intel 0000:00:14.2: setting latency timer to 64
May 1 21:15:14 Harlindon kernel: [ 19.776991] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 1 21:15:14 Harlindon kernel: [ 19.777893] HDA Intel 0000:00:14.2: setting latency timer to 64
May 2 09:22:01 Harlindon kernel: [ 20.540543] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 2 09:22:01 Harlindon kernel: [ 20.540619] HDA Intel 0000:00:14.2: setting latency timer to 64
May 2 09:26:04 Harlindon kernel: [ 19.819578] hda-intel: unable to grab IRQ 0, disabling device May 2 09:26:04 Harlindon kernel: [ 19.819677] HDA Intel: probe of 0000:00:14.2 failed with error -16
May 2 10:37:28 Harlindon kernel: [ 20.175934] hda-intel: unable to grab IRQ 0, disabling device May 2 10:37:28 Harlindon kernel: [ 20.175999] HDA Intel: probe of 0000:00:14.2 failed with error -16
May 2 13:26:27 Harlindon kernel: [ 20.610591] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 2 13:26:27 Harlindon kernel: [ 20.610666] HDA Intel 0000:00:14.2: setting latency timer to 64
May 2 16:57:23 Harlindon kernel: [ 19.885497] hda-intel: unable to grab IRQ 0, disabling device May 2 16:57:23 Harlindon kernel: [ 19.885575] HDA Intel: probe of 0000:00:14.2 failed with error -16
May 2 18:20:18 Harlindon kernel: [ 22.605977] hda-intel: unable to grab IRQ 0, disabling device May 2 18:20:18 Harlindon kernel: [ 22.606042] HDA Intel: probe of 0000:00:14.2 failed with error -16
What is damned peculiar is that is has sometimes worked (as you can see above). I can find no pattern however. I HAVE downloaded an compiled the latest alsa-driver-snapshot. That last reboot has the same unable to grab irq error.
Any suggestions are greatly appreciated.
At Sat, 02 May 2009 23:57:42 -0500, Guy Stalnaker wrote:
Hello again.
I was able to get my internal speakers working for my HP Pavilion Dv4 laptop by following the advice I found in the alsa-devel archives. That advice seems to have worked for quit a few people who found it by a post I made to the Ubuntu Forums.
But now, after I have upgraded my Ubuntu from version 8.10 (when sound worked) to version 9.04, sound no longer works correctly. I have some detailed information about the sequencing and the specific error. Attached is an alsa-info.txt output.
Here's what I'm seeing (extracts from dmesg/kernel logs):
Apr 29 15:13:17 Harlindon kernel: [ 19.937190] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Apr 29 15:13:17 Harlindon kernel: [ 19.937270] HDA Intel 0000:00:14.2: setting latency timer to 64
Apr 30 09:37:09 Harlindon kernel: [ 19.941675] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Apr 30 09:37:09 Harlindon kernel: [ 19.941750] HDA Intel 0000:00:14.2: setting latency timer to 64
May 1 16:06:01 Harlindon kernel: [ 19.852324] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 1 16:06:01 Harlindon kernel: [ 19.852398] HDA Intel 0000:00:14.2: setting latency timer to 64
May 1 16:13:43 Harlindon kernel: [ 20.950985] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 1 16:13:43 Harlindon kernel: [ 20.951060] HDA Intel 0000:00:14.2: setting latency timer to 64
Commit Log for Fri May 1 16:41:58 2009 [Upgrade to Ubuntu Jaunty 9.04]
May 1 17:11:05 Harlindon kernel: [ 20.318416] hda-intel: unable to grab IRQ 0, disabling device
This is pretty unusual. Most likely either a BIOS or an ACPI problem, has little to do with the sound driver itself.
Takashi
Hello again, Takashi,
Can you think of why a new distribution might be the cause, or a change that a new distribution makes, that would result in such behavior? The new distribution includes a new kernel and a new version of xorg (I think), so everything on top of the hardware is new. What's damned peculiar is that the HTML output interface is always recognized successfully. It's only the Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) on pci 00:14.2 that seems to have this issue.
To add oddity to the issue, I brought the laptop to work this morning and on boot the Audio device was successfully recognized and aplay -l shows it a card 0!!
I wonder ... do you think that it's possible that a keyboard, mouse, printer, or some other USB device plugged into the laptop at boot could affect something like this? That's really the only difference between work and home.
Thanks for taking the time to read that long post to the list!!
Guy
Takashi Iwai wrote:
At Sat, 02 May 2009 23:57:42 -0500, Guy Stalnaker wrote:
Hello again.
I was able to get my internal speakers working for my HP Pavilion Dv4 laptop by following the advice I found in the alsa-devel archives. That advice seems to have worked for quit a few people who found it by a post I made to the Ubuntu Forums.
But now, after I have upgraded my Ubuntu from version 8.10 (when sound worked) to version 9.04, sound no longer works correctly. I have some detailed information about the sequencing and the specific error. Attached is an alsa-info.txt output.
Here's what I'm seeing (extracts from dmesg/kernel logs):
Apr 29 15:13:17 Harlindon kernel: [ 19.937190] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Apr 29 15:13:17 Harlindon kernel: [ 19.937270] HDA Intel 0000:00:14.2: setting latency timer to 64
Apr 30 09:37:09 Harlindon kernel: [ 19.941675] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Apr 30 09:37:09 Harlindon kernel: [ 19.941750] HDA Intel 0000:00:14.2: setting latency timer to 64
May 1 16:06:01 Harlindon kernel: [ 19.852324] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 1 16:06:01 Harlindon kernel: [ 19.852398] HDA Intel 0000:00:14.2: setting latency timer to 64
May 1 16:13:43 Harlindon kernel: [ 20.950985] HDA Intel 0000:00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 1 16:13:43 Harlindon kernel: [ 20.951060] HDA Intel 0000:00:14.2: setting latency timer to 64
Commit Log for Fri May 1 16:41:58 2009 [Upgrade to Ubuntu Jaunty 9.04]
May 1 17:11:05 Harlindon kernel: [ 20.318416] hda-intel: unable to grab IRQ 0, disabling device
This is pretty unusual. Most likely either a BIOS or an ACPI problem, has little to do with the sound driver itself.
Takashi
At Mon, 04 May 2009 10:26:27 -0500, Guy Stalnaker wrote:
Hello again, Takashi,
Can you think of why a new distribution might be the cause, or a change that a new distribution makes, that would result in such behavior? The new distribution includes a new kernel and a new version of xorg (I think), so everything on top of the hardware is new. What's damned peculiar is that the HTML output interface is always recognized successfully. It's only the Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) on pci 00:14.2 that seems to have this issue.
To add oddity to the issue, I brought the laptop to work this morning and on boot the Audio device was successfully recognized and aplay -l shows it a card 0!!
I wonder ... do you think that it's possible that a keyboard, mouse, printer, or some other USB device plugged into the laptop at boot could affect something like this? That's really the only difference between work and home.
I guess it's an issue with ACPI or core PCI layer. Or suspend, if this happens only after suspend/resume and not after a fresh boot.
In any way, I recommend you to report this on kernel bugzilla.
Takashi
Takashi,
I will take my queries there. Thanks for your help!!
Guy
Takashi Iwai wrote:
At Mon, 04 May 2009 10:26:27 -0500, Guy Stalnaker wrote:
Hello again, Takashi,
Can you think of why a new distribution might be the cause, or a change that a new distribution makes, that would result in such behavior? The new distribution includes a new kernel and a new version of xorg (I think), so everything on top of the hardware is new. What's damned peculiar is that the HTML output interface is always recognized successfully. It's only the Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) on pci 00:14.2 that seems to have this issue.
To add oddity to the issue, I brought the laptop to work this morning and on boot the Audio device was successfully recognized and aplay -l shows it a card 0!!
I wonder ... do you think that it's possible that a keyboard, mouse, printer, or some other USB device plugged into the laptop at boot could affect something like this? That's really the only difference between work and home.
I guess it's an issue with ACPI or core PCI layer. Or suspend, if this happens only after suspend/resume and not after a fresh boot.
In any way, I recommend you to report this on kernel bugzilla.
Takashi
participants (2)
-
Guy Stalnaker -
Takashi Iwai