Kernel logs general protection fault when applying hdajackretask settings on ALC1220

Bug #1898345 reported by Florian Hars
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
alsa-tools (Ubuntu)
New
Undecided
Unassigned

Bug Description

Steps to reproduce:

1. Stop pulseaudio
2. Start hdajackretask
3. Select codec RealteK ALC1220
4. Click "Apply now"
5. Enter password

Result:

A. hdajeckretask displays a dialog "Ok, now go ahead..."
B. The terminal it was displayed in says:
0x12 0x411111f0
0x14 0x01014010
0x15 0x01011012
0x16 0x01016011
0x17 0x40370000
0x18 0x01a19040
0x19 0x02a19050
0x1a 0x0181304f
0x1b 0x02214020
0x1d 0x40e7e629
0x1e 0x01456130
1
/tmp/hda-jack-retask-HV05R0/script.sh: line 13: 3768 Done echo 1
      3769 Segmentation fault | tee /sys/class/sound/hwC4D0/reconfig 2>> /tmp/hda-jack-retask-HV05R0/errors.log

C. dmesg logs a general protection fault.
D. The next shutdown hangs.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: alsa-tools-gui 1.2.2-1
Uname: Linux 5.8.0-050800rc7drmtip20200728-generic x86_64
ApportVersion: 2.20.11-0ubuntu48
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 3 12:15:13 2020
InstallationDate: Installed on 2020-05-28 (127 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: alsa-tools
UpgradeStatus: Upgraded to groovy on 2020-10-03 (0 days ago)

Revision history for this message
Florian Hars (hars) wrote :
Revision history for this message
Florian Hars (hars) wrote :
Revision history for this message
Florian Hars (hars) wrote :

The errors.log written by hdajackretask is empty, and I accidentally booted into the wrong kernel when submitting the original report, this actually also happens with

5.8.0-20-lowlatency #21-Ubuntu SMP PREEMPT Wed Sep 23 02:09:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Another interesting thind is that after a while some programs become unkillable, like sudo, or some daemons:

Oct 3 12:46:07 alhazen systemd[1]: Starting Hostname Service...
Oct 3 12:46:59 alhazen PackageKit: daemon quit
Oct 3 12:46:59 alhazen systemd[1]: packagekit.service: Succeeded.
Oct 3 12:47:37 alhazen systemd[1]: systemd-hostnamed.service: start operation timed out. Terminating.
Oct 3 12:49:08 alhazen systemd[1]: systemd-hostnamed.service: State 'stop-sigterm' timed out. Killing.
Oct 3 12:50:32 alhazen /usr/libexec/gdm-x-session[2687]: (EE) event3 - Logitech USB Keyboard: client bug: event processing lagging behind by 19ms, your system is too slow
Oct 3 12:50:38 alhazen systemd[1]: systemd-hostnamed.service: Processes still around after SIGKILL. Ignoring.
Oct 3 12:50:53 alhazen dbus-daemon[2600]: [session uid=1000 pid=2600] Activating service name='org.gnome.Nautilus' requested by ':1.39' (uid=1000 pid=2887 comm="/usr/bin/gnome-shell " label="unconfined")
Oct 3 12:50:53 alhazen dbus-daemon[2600]: [session uid=1000 pid=2600] Successfully activated service 'org.gnome.Nautilus'
Oct 3 12:50:53 alhazen dbus-daemon[1211]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.121' (uid=1000 pid=3944 comm="/usr/bin/nautilus --gapplication-service " label="unconfined")
Oct 3 12:50:54 alhazen nautilus[3944]: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory)
Oct 3 12:51:19 alhazen /usr/libexec/gdm-x-session[2687]: (EE) event3 - Logitech USB Keyboard: client bug: event processing lagging behind by 19ms, your system is too slow
Oct 3 12:51:59 alhazen systemd[2586]: Started VTE child process 3973 launched by gnome-terminal-server process 3519.
Oct 3 12:52:08 alhazen systemd[1]: systemd-hostnamed.service: State 'final-sigterm' timed out. Killing.
Oct 3 12:53:38 alhazen systemd[1]: systemd-hostnamed.service: Processes still around after final SIGKILL. Entering failed mode.
Oct 3 12:53:38 alhazen systemd[1]: systemd-hostnamed.service: Failed with result 'timeout'.
Oct 3 12:53:38 alhazen systemd[1]: Failed to start Hostname Service.

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.