Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. 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#46798 - [linux-grsec] Audio not working after update

Attached to Project: Community Packages
Opened by Michael Schönitzer (Nudin) - Monday, 19 October 2015, 10:47 GMT
Last edited by Daniel Micay (thestinger) - Monday, 26 October 2015, 01:01 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Daniel Micay (thestinger)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After yesterdays upgrade (linux-grsec 4.2.3.201510130858-1 -> 4.2.3.201510171833-1 and systemd 226-3 -> 227-1 and other non system-critical) the audiosystem does not work anymore.
The error messages talk about "waiting for sourndcards/audio backend to answer".

Booting the normal kernel works fine.
This task depends upon

Closed by  Daniel Micay (thestinger)
Monday, 26 October 2015, 01:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  4.2.4.201510251836-1
Comment by Nail (nail) - Monday, 19 October 2015, 14:14 GMT
Does system freeze at boot time with 4.2.3.201510171833-1 ?
What is your system configuration: cpu, video, chipset ?
Desktop environment?
Display manager?

PS: i'm asking because my note hang at boot time with linux-grsec-4.2.3.201510171833-1.
Comment by PaX Team (paxteam) - Monday, 19 October 2015, 19:57 GMT
can you post your dmesg (or at least any size overflow reports from it)?
Comment by Michael Schönitzer (Nudin) - Wednesday, 21 October 2015, 23:43 GMT
With Kernel 4.2.3.201510202025-1-grsec the problem is gone. Thus it is probably not worth debugging any further. => Bug can be closed.
Comment by Daniel Micay (thestinger) - Thursday, 22 October 2015, 01:58 GMT
I doubt the problem is gone. The size_overflow plugin is temporarily set to report overflows without it being a fatal error. If you provide logs, the size_overflow false positive(s) and/or genuine overflow bugs can be fixed.
Comment by Daniel Micay (thestinger) - Thursday, 22 October 2015, 19:52 GMT
All that's needed to get this fixed is your dmesg output. I'll be turning off PAX_SIZE_OVERFLOW_DISABLE_KILL as soon as they've worked their way through the backlog of reported issues (maybe a week or two?), but this one won't count if there's no log output to work from. As soon as it's turned off, it's going to break for you again.
Comment by Michael Schönitzer (Nudin) - Thursday, 22 October 2015, 20:14 GMT
No problem. Here's the dmesg-log.
   dmesg (68 KiB)
Comment by Daniel Micay (thestinger) - Thursday, 22 October 2015, 20:21 GMT
So yeah, still an issue:

[ 3.301059] PAX: size overflow detected in function snd_cmipci_put_native_mixer sound/pci/cmipci.c:2031 cicus.439_83 max, count: 43, decl: stereo; num: 0; context: cmipci_sb_reg;
[ 3.301061] CPU: 3 PID: 374 Comm: alsactl Not tainted 4.2.3.201510202025-1-grsec #1
[ 3.301061] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77-DS3H, BIOS F9 09/19/2012
[ 3.301063] ffffffffaba0a847 816e5330df158dac 0000000000000000 ffffffffc0519c43
[ 3.301064] ffffc90001d4bbf8 ffffffffab5d59d8 00000000000000a6 ffffffffc0519ca5
[ 3.301065] ffffc90001d4bc28 ffffffffab1a87ea 0000000001092424 0000000000000000
[ 3.301065] Call Trace:
[ 3.301069] [<ffffffffc0519c43>] ? cmipci_driver_exit+0x129a/0x27cf [snd_cmipci]
[ 3.301071] [<ffffffffab5d59d8>] dump_stack+0x4c/0x7f
[ 3.301073] [<ffffffffc0519ca5>] ? cmipci_driver_exit+0x12fc/0x27cf [snd_cmipci]
[ 3.301074] [<ffffffffab1a87ea>] report_size_overflow+0x5a/0x60
[ 3.301076] [<ffffffffc0515253>] snd_cmipci_put_native_mixer+0x243/0x270 [snd_cmipci]
[ 3.301078] [<ffffffffab1823a4>] ? check_heap_object+0x44/0x100
[ 3.301081] [<ffffffffc0423a18>] snd_ctl_elem_write+0x128/0x1b0 [snd]
[ 3.301083] [<ffffffffab2d56b6>] ? copy_user_enhanced_fast_string+0x16/0x20
[ 3.301084] [<ffffffffab13d942>] ? memdup_user+0x112/0x1b0
[ 3.301086] [<ffffffffc0424119>] snd_ctl_ioctl+0xe9/0xbc0 [snd]
[ 3.301087] [<ffffffffab1b62d2>] do_vfs_ioctl+0x5c2/0x8a0
[ 3.301088] [<ffffffffab1b662d>] SyS_ioctl+0x7d/0x90
[ 3.301090] [<ffffffffab5dbbf0>] entry_SYSCALL_64_fastpath+0x12/0x8a
Comment by Emese Revfy (ephox) - Sunday, 25 October 2015, 12:09 GMT
Thanks for the report, it will be fixed in the next grsec patch.

Loading...