You are not logged in.

#1 2019-10-23 20:28:02

Alad
Wiki Admin/IRC Op
From: Bagelstan
Registered: 2014-05-04
Posts: 2,420
Website

[SOLVED] kernel: unable to handle paging request

This one has me stumped and has haunted me since at least kernel 5.1.16. At some point after booting, applications like amixer, i3status, ... stop working - they simply hang. Graphical applications such as browsers however remain functional.

Looking at the journal I notice the following messages:

Oct 23 21:56:47 foxden kernel: BUG: unable to handle kernel paging request at 0000000007000050

journalctl -b 0 output: https://paste.xinu.at/OeyuS/

Note that I'm using linux-lts because linux 5.3 has severe hibernate/suspend issues on this laptop (HP EliteBook 840 G1).

Linux foxden 4.19.80-1-lts #1 SMP Fri Oct 18 05:03:40 UTC 2019 x86_64 GNU/Linux

lspci -v: https://paste.xinu.at/4fy/

When searching for this issue only vague reports with no solution come up, e.g. https://bugs.launchpad.net/ubuntu/+sour … ug/1787695. Shutting down the system afterward is no longer possible, because systemd-shutdown is waiting for processes, and sending SIGKILL has no effect.

Any thoughts on how to proceed?

Last edited by Alad (2019-11-26 10:32:37)


Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

Offline

#2 2019-10-23 21:20:55

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,171

Re: [SOLVED] kernel: unable to handle paging request

The particular issue seems directly after waking from a hibernation and crashes in the soundcore module - is this significant or random?
Can you launch new (graphical) processes after this happens?

Offline

#3 2019-10-23 23:22:21

Alad
Wiki Admin/IRC Op
From: Bagelstan
Registered: 2014-05-04
Posts: 2,420
Website

Re: [SOLVED] kernel: unable to handle paging request

Thanks. I use hibernation fairly often due to LUKS. It does appear to happen more or less consistently after a few hibernates. Launching graphical processes still seems to work.

Would reloading the soundcore module help in this case? I've tried removing it first, but had:

[root@foxden ~]# rmmod -f soundcore
rmmod: ERROR: could not remove 'soundcore': Resource temporarily unavailable
rmmod: ERROR: could not remove module soundcore: Resource temporarily unavailable

The same when trying to remove the modules that use soundcore:

[root@foxden ~]# rmmod -f snd_hda_codec_generic snd_hda_codec_hdmi snd_hwdep snd_hda_intel snd_hda_codec snd_timer snd_pcm snd_hda_codec_idt snd soundcore
rmmod: ERROR: could not remove 'snd_hda_codec_hdmi': No such file or directory
rmmod: ERROR: could not remove module snd_hda_codec_hdmi: No such file or directory
rmmod: ERROR: could not remove 'snd_hwdep': Resource temporarily unavailable
rmmod: ERROR: could not remove module snd_hwdep: Resource temporarily unavailable
rmmod: ERROR: could not remove 'snd_hda_intel': No such file or directory
rmmod: ERROR: could not remove module snd_hda_intel: No such file or directory
rmmod: ERROR: could not remove 'snd_timer': Resource temporarily unavailable
rmmod: ERROR: could not remove module snd_timer: Resource temporarily unavailable
rmmod: ERROR: could not remove 'snd_pcm': Resource temporarily unavailable
rmmod: ERROR: could not remove module snd_pcm: Resource temporarily unavailable
rmmod: ERROR: could not remove 'snd_hda_codec_idt': No such file or directory
rmmod: ERROR: could not remove module snd_hda_codec_idt: No such file or directory
rmmod: ERROR: could not remove 'snd': Resource temporarily unavailable
rmmod: ERROR: could not remove module snd: Resource temporarily unavailable
rmmod: ERROR: could not remove 'soundcore': Resource temporarily unavailable
rmmod: ERROR: could not remove module soundcore: Resource temporarily unavailable

Surely there is a way to recover from a crash in the module? Since most of the unkillable processes were instances of amixer, I'm guessing you're on the right path.


Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

Offline

#4 2019-10-24 07:40:15

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,171

Re: [SOLVED] kernel: unable to handle paging request

Please look at your journals and ensure that issue always resulted in a soundcode crash (at least anything in a snd_* function) to rule out that this isn't a corrupted hibernation image or maybe related to processor C-states.

Ensure to stop all audio daemons (notably pulseaudio, but really anything that shows up in "lsof -t /dev/snd/*") and try to simply reset the sound system:
https://wiki.archlinux.org/index.php/Ad … ing_codecs

Offline

#5 2019-10-31 10:54:36

Alad
Wiki Admin/IRC Op
From: Bagelstan
Registered: 2014-05-04
Posts: 2,420
Website

Re: [SOLVED] kernel: unable to handle paging request

You were right, on a next resume from hibernate it was a different crash:

Oct 30 12:37:42 foxden kernel: general protection fault: 0000 [#1] SMP PTI
Oct 30 12:37:42 foxden kernel: CPU: 2 PID: 28730 Comm: astroid Tainted: G    B             4.19.80-1-lts #1
Oct 30 12:37:42 foxden kernel: Hardware name: Hewlett-Packard HP EliteBook 840 G1/198F, BIOS L71 Ver. 01.30 12/09/2014
Oct 30 12:37:42 foxden kernel: RIP: 0010:kmem_cache_alloc+0x79/0x1a0
Oct 30 12:37:42 foxden kernel: Code: 7d 61 49 83 78 10 00 4d 8b 20 0f 84 fb 00 00 00 4d 85 e4 0f 84 f2 00 00 00 41 8b 5f 20 49 8b 3f 48 8d 4a 01 4c 89 e0 4c 01 e3 <48> 33 1b 49 33 9f 38 01 00 00 65 48 0f c7 0f 0f 94 c0 84 c0 74 b2
Oct 30 12:37:42 foxden kernel: RSP: 0018:ffffb109c52cbd60 EFLAGS: 00010202
Oct 30 12:37:42 foxden kernel: RAX: 5eb2ee522ae2314f RBX: 5eb2ee522ae2314f RCX: 0000000000ac7991
Oct 30 12:37:42 foxden kernel: RDX: 0000000000ac7990 RSI: 00000000006000c0 RDI: 00002dcac941a640
Oct 30 12:37:42 foxden kernel: RBP: 00000000006000c0 R08: ffffd109bfc9a640 R09: ffffa33ef0d3d020
Oct 30 12:37:42 foxden kernel: R10: ffffa33ef0d3dad8 R11: 0000000000000026 R12: 5eb2ee522ae2314f
Oct 30 12:37:42 foxden kernel: R13: ffffffff9e680b3a R14: ffffa33ef641de00 R15: ffffa33ef0b53200
Oct 30 12:37:42 foxden kernel: FS:  00007ff282545c40(0000) GS:ffffa33ef6880000(0000) knlGS:0000000000000000
Oct 30 12:37:42 foxden kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 30 12:37:42 foxden kernel: CR2: 00007ff282546250 CR3: 00000001751d4004 CR4: 00000000001606e0
Oct 30 12:37:42 foxden kernel: Call Trace:
Oct 30 12:37:42 foxden kernel:  vm_area_dup+0x1a/0x40
Oct 30 12:37:42 foxden kernel:  copy_process.part.0+0x1765/0x1e90
Oct 30 12:37:42 foxden kernel:  _do_fork+0xdb/0x3f0
Oct 30 12:37:42 foxden kernel:  ? syscall_trace_enter+0x1b6/0x2b0
Oct 30 12:37:42 foxden kernel:  ? __do_pipe_flags+0x53/0xd0
Oct 30 12:37:42 foxden kernel:  ? do_pipe2+0x80/0xc0
Oct 30 12:37:42 foxden kernel:  do_syscall_64+0x4e/0x100
Oct 30 12:37:42 foxden kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Oct 30 12:37:42 foxden kernel: RIP: 0033:0x7ff289419aef
Oct 30 12:37:42 foxden kernel: Code: ed 0f 85 f4 00 00 00 64 4c 8b 0c 25 10 00 00 00 45 31 c0 4d 8d 91 d0 02 00 00 31 d2 31 f6 bf 11 00 20 01 b8 38 00 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 8d 00 00 00 41 89 c5 85 c0 0f 85 9a 00 00
Oct 30 12:37:42 foxden kernel: RSP: 002b:00007fff49569390 EFLAGS: 00000246 ORIG_RAX: 0000000000000038
Oct 30 12:37:42 foxden kernel: RAX: ffffffffffffffda RBX: 0000000000000001 RCX: 00007ff289419aef
Oct 30 12:37:42 foxden kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000001200011
Oct 30 12:37:42 foxden kernel: RBP: 0000000000000001 R08: 0000000000000000 R09: 00007ff282545c40
Oct 30 12:37:42 foxden kernel: R10: 00007ff282545f10 R11: 0000000000000246 R12: 0000000000000001
Oct 30 12:37:42 foxden kernel: R13: 00007fff49569510 R14: 00007fff495697a0 R15: 0000000000000000
Oct 30 12:37:42 foxden kernel: Modules linked in: rfcomm bridge stp llc joydev ccm snd_hda_codec_hdmi intel_rapl mousedev x86_pkg_temp_thermal intel_powerclamp coretemp arc4 i915 snd_hda_codec_idt snd_hda_codec_generic kvmgt vfio_mdev mdev cmac snd_hda_intel vfio_iommu_type1 vfio algif_hash snd_hda_codec iptable_nat nf_nat_ipv4 kvm nf_nat mei_wdt iwlmvm nf_conntrack algif_skcipher uvcvideo nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c af_alg snd_hda_core bnep iptable_mangle iptable_filter mac80211 videobuf2_vmalloc snd_hwdep videobuf2_memops videobuf2_v4l2 i2c_algo_bit drm_kms_helper irqbypass videobuf2_common intel_cstate snd_pcm ofpart hp_wmi drm iwlwifi videodev sparse_keymap cmdlinepart snd_timer intel_spi_platform intel_spi intel_gtt spi_nor agpgart iTCO_wdt snd syscopyarea wmi_bmof mtd iTCO_vendor_support intel_uncore
Oct 30 12:37:42 foxden kernel:  intel_rapl_perf sysfillrect rtsx_pci_ms media pcspkr uas cfg80211 tpm_infineon mei_me sysimgblt e1000e fb_sys_fops input_leds mei soundcore i2c_i801 lpc_ich psmouse wmi battery memstick hp_accel pcc_cpufreq lis3lv02d tpm_tis tpm_tis_core input_polldev tpm evdev ac rng_core hp_wireless mac_hid intel_smartconnect btusb btrtl btbcm btintel bluetooth ecdh_generic rfkill ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 usb_storage dm_crypt dm_mod sd_mod crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc rtsx_pci_sdmmc mmc_core serio_raw atkbd libps2 aesni_intel ahci aes_x86_64 libahci crypto_simd cryptd glue_helper libata scsi_mod rtsx_pci xhci_pci ehci_pci xhci_hcd ehci_hcd i8042 serio
Oct 30 12:37:42 foxden kernel: ---[ end trace 912e4a59854a9288 ]---

The difference being that now the whole graphical interface was frozen (switching to a TTY etc. had no effect, I did not try to SSH to the machine).

Complete log: https://paste.xinu.at/sla/

Last edited by Alad (2019-10-31 10:56:16)


Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

Offline

#6 2019-10-31 13:42:03

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 78,171

Re: [SOLVED] kernel: unable to handle paging request

There're mem allocation errors all over the place, one in the i915 module (likely cause of the frozen graphics) - can you easily try a different (unencrypted) hibernation image/partition/device?

I assume this is not a dual booting system (whether windows or different distros) and nothing is supposed to touch the device that holds the hibernation image?

Offline

#7 2019-11-26 10:32:22

Alad
Wiki Admin/IRC Op
From: Bagelstan
Registered: 2014-05-04
Posts: 2,420
Website

Re: [SOLVED] kernel: unable to handle paging request

I'd have to resize my partitions to have space for an unencrypted hibernation image (or so I believe). Last time I tried resize2fs it didn't end up well...

I don't dual boot. Anyway I did as you hinted at in #4 and disabled "Deep Sleep" in the BIOS. This laptop has a host of other issues, but at least I haven't seen paging errors or similar issues on hibernate (with 5.1.16) again. Thanks!

Last edited by Alad (2019-11-26 10:33:25)


Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby

Offline

Board footer

Powered by FluxBB