Sound not working after upgrading to 3.8.0-19

This change was made by a bot.

I'd like to perform a bisect to figure out what commit caused this regression.

Can you test the following kernels and report back?:

v3.8.6: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.6-raring/
v3.8.7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.7-raring/
v3.8.8: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8.8-raring/

You don't have to test every kernel, just up until the kernel that first has this bug.

One thing to note, you will need to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance!

Related : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1170710

Hi,
All 3.8.x are working perfectly except 3.8.0-19

What I noticed is:
When I update my system from 3.8.0-18 to 3.8.0-19 sound stopped working.
I rebooted to -18 and verified its working fine. again booted to -19 and no sound again!

Then while remaining in -19, i just reinstall the kernel and extras and sound works after reboot.

For the test, I removed -19 switched back to -18 and upgrade the system again and faced the problem.

Seems like reinstalling the kernel while booting from it fixed the issue.

I saw that blacklist file contained SoundCard, Alsa, and other sound related modules which are now okay after reinstall.

Marking Confirmed, question was answered.

I also confirm that all the mainline kernel from 3.8.6 to 3.8.8 worked fine.

It works by following:

- upgrade to 3.8.0-19 -> sound failed
- Boot from 3.8.0-19. verify by 'uname -r'
- reinstall apt-get purge reinstall linux-image-$(uname -r).
- reboot
- Solved!!!! (sound works)

I don't think so, that's only the random caracteristic of this problem. It does not happens on all boot for me, so sometimes it works, sometimes it doesn't, without being able to understand any differences between those cases...

@Syed Asad Ali Rizvi,

Can you confirm that sound now works for every boot? This may be due to a Ubuntu SAUCE patch since the bug does not exist in upstream v3.8.8

@Joseph,
Yes it works for every boot.

Booting on today LiveCD:
[ 22.042712] BUG: unable to handle kernel paging request at ffff880130537fe0
[ 22.042760] IP: [<ffffffffa069c820>] patch_generic_hdmi+0xe0/0x550 [snd_hda_codec_hdmi]
[ 22.042808] PGD 1c0e063 PUD bb583067 PMD 130c01063 PTE 8000000130537161
[ 22.042847] Oops: 0003 [#1] SMP
[ 22.042870] Modules linked in: snd_hda_codec_hdmi ath9k(+) ath9k_common snd_hda_codec_realtek ath9k_hw btusb snd_hda_intel(+) snd_hda_codec ath mac80211 snd_hwdep(F) snd_pcm(F) coretemp snd_page_alloc(F) cfg80211 snd_seq_midi(F) uvcvideo kvm_intel snd_seq_midi_event(F) videobuf2_vmalloc videobuf2_memops snd_rawmidi(F) videobuf2_core videodev psmouse(F) snd_seq(F) snd_seq_device(F) snd_timer(F) kvm snd(F) soundcore(F) asus_laptop serio_raw(F) sparse_keymap input_polldev mei parport_pc(F) bnep intel_ips lpc_ich ppdev(F) dm_multipath(F) mac_hid rfcomm scsi_dh(F) bluetooth microcode(F) lp(F) parport(F) squashfs(F) overlayfs(F) nls_iso8859_1(F) ext2(F) dm_raid45 xor(F) dm_mirror(F) dm_region_hash(F) dm_log(F) usb_storage(F) nouveau mxm_wmi wmi atl1c ttm i915 ahci(F) libahci(F) video(F) i2c_algo_bit drm_kms_helper drm
[ 22.043339] CPU 1
[ 22.043354] Pid: 1463, comm: modprobe Tainted: GF 3.8.0-19-generic #29-Ubuntu ASUSTeK Computer Inc. U43Jc/U43Jc
[ 22.043412] RIP: 0010:[<ffffffffa069c820>] [<ffffffffa069c820>] patch_generic_hdmi+0xe0/0x550 [snd_hda_codec_hdmi]
[ 22.043469] RSP: 0018:ffff88012b67bac0 EFLAGS: 00010283
[ 22.043498] RAX: 0000000000000008 RBX: 0000000000000002 RCX: 0000000000000002
[ 22.043535] RDX: ffff880130537fd8 RSI: ffff880130537fe0 RDI: ffff88012daf4c20
[ 22.043574] RBP: ffff88012b67baf8 R08: 0000000000000001 R09: 0000000000000006
[ 22.043611] R10: 0000000000000008 R11: 0000000000000014 R12: ffff88012daf4800
[ 22.043648] R13: 0000000000000000 R14: 0000000000000002 R15: ffff880130538000
[ 22.043686] FS: 00007fb3df56d740(0000) GS:ffff880137c40000(0000) knlGS:0000000000000000
[ 22.043729] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 22.043758] CR2: ffff880130537fe0 CR3: 0000000131668000 CR4: 00000000000007e0
[ 22.043796] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 22.043834] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 22.043871] Process modprobe (pid: 1463, threadinfo ffff88012b67a000, task ffff88012b672e80)
[ 22.043915] Stack:
[ 22.043927] 00000000ffffffff ffffffffa06a0002 ffffffffa069e880 0000000000000001
[ 22.043970] ffff88012daf4800 00000000ffffffff ffffffffa06a0000 ffff88012b67bb58
[ 22.044013] ffffffffa04ca186 2d6164682d646e73 64692d6365646f63 303832363830383a
[ 22.044055] Call Trace:
[ 22.044079] [<ffffffffa04ca186>] snd_hda_codec_configure+0x146/0x440 [snd_hda_codec]
[ 22.044126] [<ffffffffa04ee2f0>] azx_probe_continue+0x3a0/0x4f0 [snd_hda_intel]
[ 22.044168] [<ffffffffa04ec8b0>] ? azx_attach_pcm_stream+0x1e0/0x1e0 [snd_hda_intel]
[ 22.044211] [<ffffffffa04edcb0>] ? azx_halt+0x30/0x30 [snd_hda_intel]
[ 22.044251] [<ffffffffa04ec6d0>] ? azx_pcm_trigger+0x580/0x580 [snd_hda_intel]
[ 22.044293] [<ffffffffa04ed810>] ? azx_runtime_suspend+0x30/0x30 [snd_hda_intel]
[ 22.044335] [<ffffffffa04ea670...

So it sounds like this bug is resolved for you, @Syed Asad Ali Rizvi. However, you still experience the bug, @Bruno? @C de-Avillez, do you still see this bug with 3.8.0-19?

If you still see the bug, Bruno and Carlos, I'll bisect to find the SAUCE patch that introduced this. We will first need to know the last Ubuntu kernel that did not exhibit this bug. Can you also confirm the 3.8.0-18 kernel did not have the bug?

Until the last reboot (on April 20th) yes, it is there. I will reboot again in a few, but I have seen no updates that might have changed anything.

As I've said before, it looks to be totally random. I had it on my latest boot, but not on the two before. I did not tried just to reboot again and again to have statistics or see if it occurs really randomly, because I have more important things to fix first, but I might do so later.

Also, that random caracteristic makes bisect very hard... Because I will never know whether it is fixed or not just happening on that couple of boots, unless obviously it crash.

The oops in comment #12 is bug 1169984.

Interesting. I am also experiencing this same bug on Ubuntu 12.04 (3.2 kernel...) -- did we accidentally back-merge the bug?

{{{
multimedia@fermmy-media:~$ uname -a
Linux fermmy-media 3.2.0-51-generic-pae #77-Ubuntu SMP Wed Jul 24 20:40:32 UTC 2013 i686 i686 i386 GNU/Linux
multimedia@fermmy-media:~$ cat /etc/issue
Ubuntu 12.04.2 LTS \n \l
}}}

dmesg + backtrace: http://pastebin.com/uMAmEnxD