** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+attachment/5716489/+files/version.log
** Summary changed: - kernel crash after wakeup: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46 + kernel crash after suspend: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2042851 Title: kernel crash after suspend: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46 Status in linux package in Ubuntu: New Bug description: Laptop may or may not wake up after resume. 2 out of 10 times it will display an error message and become unresponsive: nov 06 10:36:14 ASUS kernel: UBSAN: invalid-load in /build/linux-25O3Ed/linux-5.15.0/sound/core/pcm_native.c:602:46 nov 06 10:36:14 ASUS kernel: load of value 130 is not a valid value for type '_Bool Attaching dmesg log file for analysis. === At a minimum every hibernate/resume report should contain responses to each item in this section before being considered Triaged. 1. Is this really a failure? Yes, as machine hangs and becomes unresponsive. 2. Is it reproducible? If not, how often would it be reproducible? I'd say it happens 20% of the time. 3. Did it work before on a prior kernel in the same release, or prior release? Not really sure. I started using the suspend functionality quite recently. 4. Do the symptoms vary at all between hibernation attempts? For example, one time WiFi didn't work, but another a kernel error shows on the screen. It is the same symptoms each time. 5. Do you end up with a flashing Caps Lock light? No. Keybiard becomes unresponsive. Clicking on Caps lock key does not turn light on. Only solution is to press power off key. 6. Please advise on how the computer hibernated, and resumed specifically. I suspended it by clicking on the word 'Suspend' in the Gui and then closed the lid. When I opened the lid the computer showed the error. 7. Did the machine break while going into hibernation or waking up? According to the log it broke when suspending. 8. Did you see any error messages leading up to the failure? Nope. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042851/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
