FS#66088 - System freezes suddenly with "BUG: unable to handle page fault for address" present in the journal

Attached to Project: Arch Linux
Opened by Radoslav Georgiev (maximaman) - Thursday, 02 April 2020, 23:14 GMT
Last edited by freswa (frederik) - Thursday, 02 April 2020, 23:29 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I've been experiencing sudden freezes of the whole system approximately since 5.5 become the stable minor kernel version. To be more specific, they usually happen after attempting to resume from a suspended state or unlock my screen. What follows is that the screen remains blank (there is not even a mouse pointer), and I cannot even switch to a TTY; basically, the system is hung and I cannot do anything besides powering off or rebooting my system using the power button.

After I hard-rebooted the system (turned it off and then turned it on from the power button) the last time the freeze happened, the following journal entries of interest were present among those from the previous boot:

kernel: Bluetooth: hci0: unexpected event for opcode 0xfc2f
kernel: rmi4_physical rmi4-07: rmi_driver_clear_irq_bits: Failed to change enabled interrupts!
kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
kernel: BUG: unable to handle page fault for address: ffff980704cc4180
kernel: #PF: supervisor instruction fetch in kernel mode
kernel: #PF: error_code(0x0011) - permissions violation

Additional info:
* Kernel version: linux 5.5.13.arch2-1
* System information:
* Manufacturer: LENOVO
* Product Name: 20C60078BM
* Version: ThinkPad Edge E540

I can provide more information on demand if necessary.

Steps to reproduce: Sadly, I cannot provide any method to reproduce the freezes in a consistent manner.
This task depends upon

Closed by  freswa (frederik)
Thursday, 02 April 2020, 23:29 GMT
Reason for closing:  Not a bug
Additional comments about closing:  This doesn't seem to be a packaging issue. Please get in touch with the kernel people to report a bug or visit our forums for help in general.

Loading...