snd-hda-intel broken in generic_2.6.22-14.38_amd64

The upgrade of linux-ubuntu-modules-2.6.22-14-generic from .37 to .38 just makes my all gnome applications crash, the machine cannot restart properly. I have to push the power button to shut it down.

I can confirm the bug on 2.6.24, it causes the kernel to get confused, apps that attempt to read the process table crash. The only workaround at this point is to disable the intel-hda driver. My dmesg is exactly the same as the user who posted the report. Side note: I have a Radeon 2600XT in my system, which has audio output through the HDMI port which uses the intel-hda driver, I know support for this was recently introduced. Perhaps that is the issue?

Thank you for taking the time to report this bug and helping to make Ubuntu better. Per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Hello Leann Ogasawara,

I have seen this problem with my desktop using Ubuntu 8.04.

I have attached the files you requested. please see attachment.

Thanks.

I have a simliar problem with my VIA High Definition Audio driver after installing this version on my Everex Cloudbook. I re-installed the machine from scratch, and verified that this package is the package that breaks my sound (no gstreamer device, alsa-mixer cannot find default device, etc...). There are numerous threads on this happening in Hardy, glad to see I'm not the only Gutsy user with the issue.

My post above is about upgrading to .38 in line with this bug report. My comment was that my log files are with version .37 (sound working) and not .38 (sound broken) since I currently would like to have sound on my computer. Summary: .37 works for me, .38 doesn't, reverted to .37.

Hi Guys,

Wanted to give a quick update. With the current Intrepid Ibex 8.10 development cycle already under way we'll need to try to target getting this fixed with this upcoming release first. Would any of you experiencing this issue care to test the latest Intrepid Alpha release - http://www.ubuntu.com/testing . If the issue still exists, please attach your dmesg output which hopefully also captures the oops shown in the original description.

Also just a note that beginning with the Intrepid Ibex cycle, the linux-ubuntu-modules package was actually merged with the linux kernel source package. Therefore any future bugs that would have been reported against linux-ubuntu-modules should now just be reported against linux. I've gone ahead and moved this bug to also target the linux kernel source package. Thanks.

Also against 2.6.22 and 2.6.24 this will be closed until we can determine and appropriate patch to backport and if it that patch will qualify for a stable release update - http://wiki.ubuntu.com/StableReleaseUpdates . Thanks.

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.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug report is being closed because we received no response to the previous inquiry for information. Please reopen if this is still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If the issue remains in Jaunty, please test the latest upstream kernel build - https://wiki.ubuntu.com/KernelMainlineBuilds . To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.