2.6.20-16 kernell corrupts SB450 kmix

Bug #140937 reported by Pavel Mendl
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned
linux-source-2.6.20 (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: kernel-image-2.6.20-16-generic-di

100% reproducible bug, verified to be caused by 2.6.20-16 kernel while 2.6.20-15 works OK:

Environment: Installing fresh Kubuntu 7.04 Feisty Fawn from the official site downloaded live CD for a friend on the Aspire 3104NWLMi laptop.

Related hardware: lspci | grep Audio ==> 00:14.2 Audio device: ATI Technologies Inc SB450 HDA Audio (rev 01)

Brief description: While under 2.6.20-15-generic kernel was KMix functional normally (under reservations see below), after Full update it started to show the one completely unrelated to the given hardware (either by text description, or by that e.g. did not have any inputs (mics) panel at all). Trying to localize problem I made another fresh Kubuntu installation, where just after establishing network connection I intended to separately update on package-by-package basis. Luckily (even if not fully accidentally ;-) ) I started with kernel update (to 2.6.20-16-generic) and bingo, the problem reappeared. To confirm localization I have immediately rebooted on previous kernel 2.6.20-15-generic, with no other changes and the correct KMix panel reappeared.

Related to (suspected-to-be :-) ) bugs:
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/137734 (as the similar problem - corrupt sound support - and same kernel version)

https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/81975
https://bugs.launchpad.net/ubuntu/+source/gnome-alsamixer/+bug/95479 (as I used to get same error message ("function snd_mixer_load failed: Invalid argument") from alsamixer under 2.6.20-16-generic)

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/46939 (as related to the following more general mixer related problems - see below)

More general problems with KMix/amixer/alsamixer functionalities for SB450 are described (including my addendum) here: http://ubuntuforums.org/showthread.php?t=506515 (I do not want to cross post, so just linking here)

More details:
As I had to pass the laptop back to the friend, I just listed what I have seen in other bugreports, to have at least some clues possibly

2.6.20-16 lsmod | grep snd_ ==>
snd_hda_intel 21912 4
snd_hda_codec 205056 1 snd_hda_intel
snd_pcm_oss 44544 0
snd_mixer_oss 17408 2 snd_pcm_oss
snd_pcm 79876 4 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 23684 3 snd_pcm,snd_seq
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 54020 14 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
snd_page_alloc 10888 2 snd_hda_intel,snd_pcm

2.6.20-15 lsmod | grep snd_ ==>
snd_hda_intel 21912 1
snd_hda_codec 205440 1 snd_hda_intel
snd_pcm_oss 44544 0
snd_mixer_oss 17408 1 snd_pcm_oss
snd_pcm 79876 3 snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd_seq_dummy 4740 0
snd_seq_oss 32896 0
snd_seq_midi 9600 0
snd_rawmidi 25472 1 snd_seq_midi
snd_seq_midi_event 8448 2 snd_seq_oss,snd_seq_midi
snd_seq 52592 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 23684 2 snd_pcm,snd_seq
snd_seq_device 9100 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 54020 12 snd_hda_intel,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
snd_page_alloc 10888 2 snd_hda_intel,snd_pcm

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

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.

Revision history for this message
Michele Mangili (mangilimic) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
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.