You are not logged in.

#1 2012-08-31 00:49:57

Zmann
Member
Registered: 2010-04-27
Posts: 36

[SOLVED] issues with soundcard after last kernel update

Hi all,

after last kernel update 2 days ago I'm experiencing trouble with my soundcard. At boot time I get

...
[    2.347864] EDAC MC: Ver: 2.1.0
[    2.350971] BUG: unable to handle kernel paging request at 63616465
[    2.351070] IP: [<c02f211d>] strncpy+0x1d/0x40
[    2.351137] *pde = 00000000
[    2.351197] Oops: 0000 [#1] PREEMPT SMP
[    2.351311] Modules linked in: i82975x_edac(+) edac_core snd_pcm snd_page_alloc snd_hwdep floppy(+) tg3(+) snd_timer agpgart snd i2c_core soundcore acpi_cpufreq(+) libphy mperf wmi button processor parport_pc lp parport nfs nfs_acl lockd auth_rpcgss sunrpc fscache ext4 crc16 jbd2 mbcache raid1 md_mod sd_mod ahci libahci ata_piix libata uhci_hcd scsi_mod ehci_hcd usbcore usb_common
[    2.352508]
[    2.352543] Pid: 204, comm: systemd-udevd Not tainted 3.5.3-1-ARCH #1 Hewlett-Packard HP xw4400 Workstation/0A68h
[    2.352674] EIP: 0060:[<c02f211d>] EFLAGS: 00010206 CPU: 1
[    2.352714] EIP is at strncpy+0x1d/0x40
[    2.352752] EAX: f4452a40 EBX: f4452a40 ECX: 0000001e EDX: 63616465
[    2.352792] ESI: 63616465 EDI: f4452a40 EBP: f4563d6c ESP: f4563d60
[    2.352830]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[    2.352868] CR0: 80050033 CR2: 63616465 CR3: 347f0000 CR4: 000007d0
[    2.352906] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
[    2.352945] DR6: ffff0ff0 DR7: 00000400
[    2.352983] Process systemd-udevd (pid: 204, ti=f4562000 task=f44b3a70 task.ti=f4562000)
[    2.353029] Stack:
[    2.353063]  f4452a40 00000003 f4452140 f4563de0 f88f2580 00000004 f4452038 f88f6000
[    2.353309]  f4452000 f4d49000 00000000 00000000 f4452034 00000000 00000000 00040000
[    2.353335]  00040000 00000004 fed14000 f4d49060 00000246 00000292 f4d49060 00000003
[    2.353335] Call Trace:
[    2.353335]  [<f88f2580>] i82975x_init_one+0x22a/0x2d9 [i82975x_edac]
[    2.353335]  [<c03a2701>] ? __rpm_callback+0x41/0x80
[    2.353335]  [<c030c867>] pci_device_probe+0x87/0x110
[    2.353335]  [<c0291c27>] ? sysfs_create_link+0x17/0x20
[    2.353335]  [<c039a143>] driver_probe_device+0x63/0x1e0
[    2.353335]  [<c039a351>] __driver_attach+0x91/0xa0
[    2.353335]  [<c039a2c0>] ? driver_probe_device+0x1e0/0x1e0
[    2.353335]  [<c03988f2>] bus_for_each_dev+0x42/0x80
[    2.353335]  [<c0399d1e>] driver_attach+0x1e/0x20
[    2.353335]  [<c039a2c0>] ? driver_probe_device+0x1e0/0x1e0
[    2.353335]  [<c0399977>] bus_add_driver+0x187/0x270
[    2.353335]  [<c030c6e0>] ? pci_dev_put+0x20/0x20
[    2.353335]  [<c039a93a>] driver_register+0x6a/0x140
[    2.353335]  [<f88f4000>] ? 0xf88f3fff
[    2.353335]  [<c030caf2>] __pci_register_driver+0x42/0xb0
[    2.353335]  [<f88f4000>] ? 0xf88f3fff
[    2.353335]  [<f88f402b>] i82975x_init+0x2b/0x8c [i82975x_edac]
[    2.353335]  [<c01011f2>] do_one_initcall+0x112/0x160
[    2.353335]  [<c015c17a>] ? __blocking_notifier_call_chain+0x4a/0x80
[    2.353335]  [<c01936c5>] sys_init_module+0xe35/0x1ae0
[    2.353335]  [<c04cc21f>] sysenter_do_call+0x12/0x28
[    2.353335] Code: 8b 7d fc 89 ec 5d c3 8d b4 26 00 00 00 00 55 89 e5 83 ec 0c 89 5d f4 89 75 f8 89 7d fc 66 66 66 66 90 89 c3 89 d6 89 c7 49 78 08 <ac> aa 84 c0 75 f7 f3 aa 89 d8 8b 75 f8 8b 5d f4 8b 7d fc 89 ec
[    2.353335] EIP: [<c02f211d>] strncpy+0x1d/0x40 SS:ESP 0068:f4563d60
[    2.353335] CR2: 0000000063616465
[    2.358469] FDC 0 is a post-1991 82077
[    2.360474] intel_rng: Firmware space is locked read-only. If you can't or
[    2.360474] intel_rng: don't want to disable this in firmware setup, and if
[    2.360474] intel_rng: you are certain that your system has a functional
[    2.360474] intel_rng: RNG, try using the 'no_fwh_detect' option.
[    2.361639] ---[ end trace 759a4bd47c17a7a0 ]---
...

As a consequence alsa fails to initialize sound afterwards (from /var/log/boot):
...
Thu Aug 30 18:19:12 2012: :: Restoring ALSA Levels    [BUSY] /usr/sbin/alsactl: load_state:1686: No soundcards found...
Thu Aug 30 18:19:12 2012:    [FAIL]
...

Additionally I noticed, that the system cannot terminate some processes at shutdown, which is causing unmount problems. I tried booting into a Ubuntu Live system, where I didn't notice any issues (that is: sound worked).

Don't know, what to try next. Any suggestions? Is it safe (or advisable) to downgrade to older kernel version and check, if the problem disappears?

Cheers, Zmann

Last edited by Zmann (2012-09-07 12:18:44)

Offline

#2 2012-09-02 14:36:42

eNTi
Member
Registered: 2006-04-30
Posts: 108

Re: [SOLVED] issues with soundcard after last kernel update

seems to be a systemd problem... i can only wonder about the irony of systemd not working together with pulseaudio... well i got the same problem.

http://comments.gmane.org/gmane.linux.a … eral/45416

update: try to login via "startx -- vt01" (from #archlinux)

update 2: tried the "startx -- vt01" without any luck:

Sep 02 16:40:19 eNTi pulseaudio[19462]: [pulseaudio] alsa-ucm.c: UCM not available for card USB PnP Sound Device
Sep 02 16:40:19 eNTi pulseaudio[19462]: [pulseaudio] alsa-ucm.c: UCM not available for card Xonar DG

update 3: https://bugzilla.redhat.com/show_bug.cgi?id=746470 seems related.

Last edited by eNTi (2012-09-02 14:46:19)

Offline

#3 2012-09-02 21:48:33

Zmann
Member
Registered: 2010-04-27
Posts: 36

Re: [SOLVED] issues with soundcard after last kernel update

Hi eNTi,

thanks for your reply.

eNTi wrote:

seems to be a systemd problem... i can only wonder about the irony of systemd not working together with pulseaudio... well i got the same problem.

Hmmm, as far as I know, I didn't switch to systemd yet. Just for fun I tried starting my system with kernel option 'init=/bin/systemd', but I saw the same alsa issue at boot time (No soundcards found...) and additionally the start of X failed.

I noticed that two days ago the system booted successfully (including sound), so it seems to be a concurrency problem.

eNTi wrote:

update: try to login via "startx -- vt01" (from #archlinux)

Well sound does not work in terminal mode, either, so I think starting the X server differently can't help.

Cheers, Zmann

Offline

#4 2012-09-04 15:47:02

i42n
Member
Registered: 2012-02-28
Posts: 22

Re: [SOLVED] issues with soundcard after last kernel update

I have exactly the same problem! No sound working and strange boot messages.

I put the whole dmesg output until the system is booted here: http://pastebin.com/wQ6fqSNC

The relevant part seems to be this one:

[    5.877023] Modules linked in: i82975x_edac(+) lpc_ich sparse_keymap rfkill edac_core mfd_core soundcore libphy serio_raw wmi i2c_core psmouse kvm pcspkr ppdev evdev coretemp parport_pc parport button loop fuse acpi_cpufreq mperf processor nfs nfs_acl lockd auth_rpcgss sunrpc fscache ext4 crc16 jbd2 mbcache hid_generic hid_cherry usbhid hid sd_mod sr_mod cdrom pata_acpi ata_generic uhci_hcd ahci libahci ata_piix libata scsi_mod ehci_hcd usbcore usb_common floppy
[    5.878740] 
[    5.878777] Pid: 166, comm: systemd-udevd Not tainted 3.5.3-1-ARCH #1 Hewlett-Packard HP xw4400 Workstation/0A68h
[    5.878917] RIP: 0010:[<ffffffff81252698>]  [<ffffffff81252698>] strncpy+0x18/0x30
[    5.879003] RSP: 0018:ffff880128331b68  EFLAGS: 00010202
[    5.879045] RAX: ffff880127684fa0 RBX: ffff880127684220 RCX: ffff880127684fa0
[    5.879089] RDX: 000000000000001f RSI: 5f706f5f63616465 RDI: ffff880127684fa0
[    5.879133] RBP: ffff880128331b68 R08: ffff880127684fbf R09: ffff88012fc16830
[    5.879177] R10: ffffea00049d3000 R11: ffffffff8124ee88 R12: 0000000000000003
[    5.879221] R13: 0000000000000000 R14: ffff880127684fa0 R15: ffff880127684068
[    5.879266] FS:  00007fb0840ff780(0000) GS:ffff88012fc00000(0000) knlGS:0000000000000000
[    5.879319] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    5.879361] CR2: 0000000001ef8248 CR3: 00000001274f2000 CR4: 00000000000007f0
[    5.879405] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    5.879450] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    5.879494] Process systemd-udevd (pid: 166, threadinfo ffff880128330000, task ffff88012765b060)
[    5.879547] Stack:
[    5.879586]  ffff880128331c18 ffffffffa04e8645 00040000276c8700 ffff880127684070
[    5.879751]  ffffc90005646000 ffff880127684000 ffff880129b88000 0000000000000000
[    5.879916]  0000000000000000 0004000000000000 fed1400028331bf8 0000000000000246
[    5.880082] Call Trace:
[    5.880124]  [<ffffffffa04e8645>] i82975x_init_one+0x2b7/0x39a [i82975x_edac]
[    5.880159]  [<ffffffff812747fc>] local_pci_probe+0x5c/0xd0
[    5.880159]  [<ffffffff81275101>] pci_device_probe+0x111/0x120
[    5.880159]  [<ffffffff8132053e>] driver_probe_device+0x7e/0x220
[    5.880159]  [<ffffffff8132078b>] __driver_attach+0xab/0xb0
[    5.880159]  [<ffffffff813206e0>] ? driver_probe_device+0x220/0x220
[    5.880159]  [<ffffffff8131e7e5>] bus_for_each_dev+0x55/0x90
[    5.880159]  [<ffffffff8132006e>] driver_attach+0x1e/0x20
[    5.880159]  [<ffffffff8131fc08>] bus_add_driver+0x198/0x270
[    5.880159]  [<ffffffffa04ea000>] ? 0xffffffffa04e9fff
[    5.880159]  [<ffffffff81320e57>] driver_register+0x77/0x150
[    5.880159]  [<ffffffffa04ea000>] ? 0xffffffffa04e9fff
[    5.880159]  [<ffffffff8127538e>] __pci_register_driver+0x5e/0xe0
[    5.880159]  [<ffffffffa04ea000>] ? 0xffffffffa04e9fff
[    5.880159]  [<ffffffffa04ea035>] i82975x_init+0x35/0xa5 [i82975x_edac]
[    5.880159]  [<ffffffff8100212a>] do_one_initcall+0x12a/0x180
[    5.880159]  [<ffffffff810b398e>] sys_init_module+0x101e/0x1e30
[    5.880159]  [<ffffffff810af190>] ? sys_getegid16+0x50/0x50
[    5.880159]  [<ffffffff814830a9>] system_call_fastpath+0x16/0x1b
[    5.880159] Code: 84 c9 75 ef 5d c3 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 55 48 85 d2 48 89 f8 4c 8d 04 17 48 89 f9 48 89 e5 74 1a 0f 1f 44 00 00 <0f> b6 16 80 fa 01 88 11 48 83 de ff 48 83 c1 01 4c 39 c1 75 eb 
[    5.880159] RIP  [<ffffffff81252698>] strncpy+0x18/0x30
[    5.880159]  RSP <ffff880128331b68>
[    5.883027] ---[ end trace 86faa24603284a1a ]---

Offline

#5 2012-09-06 21:39:41

Zmann
Member
Registered: 2010-04-27
Posts: 36

Re: [SOLVED] issues with soundcard after last kernel update

Hi i42n,

so you also have a 'Hewlett-Packard HP xw4400 Workstation/0A68h' and you got similar problems, good to know. So now we need a good idea, how to continue.

Due to the line

[    2.350971] BUG: unable to handle kernel paging request at 63616465

in my dmesg output (could not find something similar in your output), I ran a memtest, but that didn't report any problems.

I noticed, that the system is hanging for a short period during startup immediately after reporting several scsi disks. I didn't notice anything similar in the past. Additionally the system hangs for a while at shutdown, when it is trying to shutdown udev daemon. After that it fails to terminate all processes using SIGTERM first, then SIGKILL.

I tried to boot into a Ubuntu live system once again and sound is definitely working there, so it is not a hardware problem. The system was running flawlessly in the past. I would be glad, if someone could give a hint or a link, what to try next.

Cheers, Zmann

Offline

#6 2012-09-07 09:13:56

i42n
Member
Registered: 2012-02-28
Posts: 22

Re: [SOLVED] issues with soundcard after last kernel update

That is VERY interesting! Yes I have the very same machine. You said, you didn't notice anything similar in the past. Me too. It appeared about 2 weeks ago.

I already opened a new thread here, where I tried to fix it myself (no external answer yet): https://bbs.archlinux.org/viewtopic.php?id=148413 But I had no luck fixing it by switching to systemd.

If you actually have the same problem, I think we found a kernel bug. Its pretty bad to have a bug that breaks audio completly.

Offline

#7 2012-09-07 09:39:12

i42n
Member
Registered: 2012-02-28
Posts: 22

Re: [SOLVED] issues with soundcard after last kernel update

Offline

#8 2012-09-07 12:17:00

Zmann
Member
Registered: 2010-04-27
Posts: 36

Re: [SOLVED] issues with soundcard after last kernel update

Hi i42n,

I managed to get my sound back by adding

blacklist i82975x_edac

to

/etc/modprobe.d/blacklist.conf

Good idea to contact the kernel guys!

Cheers, Zmann

Offline

#9 2012-09-07 13:03:46

i42n
Member
Registered: 2012-02-28
Posts: 22

Re: [SOLVED] issues with soundcard after last kernel update

Fixed it for me too.

So I assume that it is actually a bug in the edac driver and therefore we have
to wait for them to fix it.

EDAC module does not seem to be a module I want to miss for a long time: http://www.kernel.org/doc/Documentation/edac.txt

Last edited by i42n (2012-09-07 13:07:23)

Offline

#10 2012-09-07 21:23:12

Zmann
Member
Registered: 2010-04-27
Posts: 36

Re: [SOLVED] issues with soundcard after last kernel update

I saw you updated your bug report at kernel.org, good.

i42n wrote:

EDAC module does not seem to be a module I want to miss for a long time

No need to be too paranoid about that: you have ecc-ram, so the probability of errors in your memory modules is low.  I will simply wait for a while and then give it a try again.

Cheers, Zmann

Offline

#11 2013-01-17 21:48:18

jdkdonk
Member
Registered: 2009-11-23
Posts: 23

Re: [SOLVED] issues with soundcard after last kernel update

Thanks Zmann.

This also fixes another problem I've had for quite a while.

https://bbs.archlinux.org/viewtopic.php … 1#p1178531

Offline

Board footer

Powered by FluxBB