Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55801 - [linux] 4.13.3-1 breaks support for Creative Labs EMU10k1 [Sound Blaster Live! Series]

Attached to Project: Arch Linux
Opened by Nick Fisher (nfisher) - Thursday, 28 September 2017, 20:07 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 30 September 2017, 12:41 GMT
Task Type Bug Report
Category Kernel
Status Assigned
Assigned To Tobias Powalowski (tpowa)
Jan Steffens (heftig)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Description:
After updating to most recent Kernel, audio broke. The device is listed and configurable in alsa, however not available in puvecontrol. Only Dummy Audio is available for output device.

Additional info:

upgrade log:

38242 [2017-09-28 11:47] [ALPM] upgraded libutil-linux (2.30.1-2 -> 2.30.2-1)
38243 [2017-09-28 11:47] [ALPM] upgraded git (2.14.1-1 -> 2.14.2-1)
38244 [2017-09-28 11:47] [ALPM] upgraded util-linux (2.30.1-2 -> 2.30.2-1)
38245 [2017-09-28 11:47] [ALPM] upgraded linux (4.12.13-1 -> 4.13.3-1)
38246 [2017-09-28 11:47] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
38247 [2017-09-28 11:47] [ALPM] upgraded linux-headers (4.12.13-1 -> 4.13.3-1)

journalctl prints 2 E's:

Sep 28 20:07:33 tubulus pulseaudio[521]: E: [alsa-sink-emu10k1 efx] alsa-sink.c: snd_pcm_rewind() failed: Invalid argument
Sep 28 20:07:33 tubulus pulseaudio[521]: E: [alsa-sink-emu10k1 efx] alsa-sink.c: process_rewind: Invalid argument


Steps to reproduce:
Having a similar setup and upgrade the Kernel, I suppose
This task depends upon

Comment by Nick Fisher (nfisher) - Thursday, 28 September 2017, 21:08 GMT
Downgrading made audio function again; upgrades undone:

linux (4.12.13-1 -> 4.13.3-1)
linux-headers (4.12.13-1 -> 4.13.3-1)

((nvidia-utils (384.69-1 -> 384.90-1)
nvidia (384.69-2 -> 384.90-1))) due to downgrade of linux
Comment by Nick Fisher (nfisher) - Saturday, 09 December 2017, 20:02 GMT
Any hope that this gets fixed at some point? Can't update since 4.12.13
Comment by loqs (loqs) - Saturday, 09 December 2017, 20:35 GMT
https://wiki.archlinux.org/index.php/Reporting_bug_guidelines#Upstream_or_Arch.3F
Why do you think it is a packaging and integration issue that should be fixed by the package maintainer rather than upstream?
If you think it is not a packaging and integration issue have you contacted upstream to request upstream fix the issue?
Comment by Nick Fisher (nfisher) - Saturday, 09 December 2017, 21:10 GMT
Thanks for the answer. I'm not too intricately knowledgeable as to discern whether or not it is an upstream issue or not. If you are, please let me know. Obviously you are insinuating that it in fact is an issue upstream. I will see to report it there again.
Comment by loqs (loqs) - Saturday, 09 December 2017, 21:16 GMT
Yes I think it is either a bug in the kernel itself or in the systems audio configuration.
If you can get audio to work correctly with the linux-lts kernel then that would indicate the configuration is valid.
See http://alsa-project.org/main/index.php/Bug_Tracking http://alsa-project.org/main/index.php/Help_To_Debug http://alsa-project.org/main/index.php/Mailing-lists
Edit:
Missed it functions on a kernel downgrade then yes I think it is either a kernel bug or a change in the kernel module configuration.
Comment by Nick Fisher (nfisher) - Saturday, 09 December 2017, 21:19 GMT
Will do, thanks
Edit: Yeah, that's what I thought. Ok, will see to reach upstream.
Comment by Nick Fisher (nfisher) - Saturday, 09 December 2017, 23:44 GMT
You were right, it is an upstream issue: https://bugzilla.kernel.org/show_bug.cgi?id=196687. Will request closure. Thanks again
Comment by loqs (loqs) - Sunday, 10 December 2017, 11:42 GMT Comment by Nick Fisher (nfisher) - Sunday, 17 December 2017, 22:04 GMT
Oh, thanks for the heads up. Thought it was just not rolled out yet.
Comment by Nick Fisher (nfisher) - Friday, 22 December 2017, 21:53 GMT

Loading...