Launchpad has imported 10 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=203877.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2019-06-12T15:10:07+00:00 coderight+kernelbug wrote: Starting with kernel 5.1 suspend on my ASUS C302 will crash and reset the machine when resumed. This machine is a Skylake (CAVE) based ChromeBook running Arch Linux. The suspend itself seems to work to put the machine to sleep but when resuming the machine resets and displays the white "BIOS" boot screen. After this happens the machine can no longer boot using legacy mode and I have to boot to ChromeOS and re-enable legacy boot. Also the headphones get screwed up and will not work until the machine is suspended then resumed in ChromeOS with headphones plugged in. Seems like some sort of possible firmware corruption when the crash occurs. There is nothing generated in the kernel logs when this happens. The last entry in the log is me pushing the power button to suspend the machine then nothing after that. Kernel 5.0 works fine. This started with 5.1 and all versions up to the current 5.1.8 are affected. Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/0 ------------------------------------------------------------------------ On 2019-06-13T20:01:36+00:00 coderight+kernelbug wrote: I meant to mention this is NOT fixed by the "'nosmt' vs hibernation triple fault during resume" patch in 949525fff5f722245ee2e2b1fe1e860e7e603579 Issue still present in kernel 5.1.9 Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/1 ------------------------------------------------------------------------ On 2019-08-09T00:31:53+00:00 hawson wrote: Still present in 5.2.6. 5.0.13 works, 5.1.0 onward does not. Running on an Acer C720 (also a brainwashed chromebook), also running Arch. This laptop seems to handle things a little better than the ASUS: legacy boots still works, and I do not see any evidence of audio problems or firmware corruption (the filesystems are, however, unhappy with the hard shutdown). There are no logs after the suspend. Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/2 ------------------------------------------------------------------------ On 2019-08-27T23:43:19+00:00 coderight+kernelbug wrote: This bug or a version of it has now been ported over to kernel 4.19.68 (at least that's the one I tested). I suppose I should update the kernel version on this bug but want to see if I can get more confirmation first. I'm running out of workable kernels now. :/ Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/3 ------------------------------------------------------------------------ On 2019-08-29T14:15:21+00:00 coderight+kernelbug wrote: I find that Arch Linux kernel 4.19.66-1-lts works. Then kernel 4.19.67-1-lts and above is broken (though I have not tested 4.19.69). So if someone wants to bisect whatever changed between .66 and .67 then that's likely the problem code. Maybe something to do with power management? I'm not sure. This might also find the problem in the 5.1+ kernels. Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/4 ------------------------------------------------------------------------ On 2019-08-29T14:20:33+00:00 hawson wrote: > changed between .66 and .67 then And is also common with the deltas between 5.0.13 and 5.1.0? That may help narrow down the scope of changes. Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/5 ------------------------------------------------------------------------ On 2019-09-09T09:18:07+00:00 yu.c.chen wrote: (In reply to Chris Osgood from comment #4) > I find that Arch Linux kernel 4.19.66-1-lts works. Then kernel 4.19.67-1-lts > and above is broken (though I have not tested 4.19.69). > Since 66 and 67 are with lts suffix, it might be more straightforward to test on upstream vanilla kernel. > So if someone wants to bisect whatever changed between .66 and .67 then > that's likely the problem code. Maybe something to do with power management? > I'm not sure. This might also find the problem in the 5.1+ kernels. Yeah, it looks like you are at the front line to bisect this out : ) Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/6 ------------------------------------------------------------------------ On 2019-09-30T01:09:48+00:00 yu.c.chen wrote: @Chris, just wonder if you have time for a bisect if this issue is still there? Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/7 ------------------------------------------------------------------------ On 2019-09-30T14:39:18+00:00 coderight+kernelbug wrote: Still broken in kernel 5.3.1. I haven't had a chance to bisect the issue. I'm busy fighting all sorts of fires related to kernel 5, which in general has been a disaster. Almost every new version breaks more stuff (5.1 broke the chromebooks, 5.2 broke some of our servers, 5.3 broke the e1000e driver, the list goes on). So I'm still stuck running older version 4 kernels for a while. Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/8 ------------------------------------------------------------------------ On 2019-10-23T07:07:35+00:00 ferry.toth wrote: I confirm this issue also occurs on Acer 720P (ex)chromebook (with touch screen + 4Gb ram). After updating Ubuntu to 19.10 (linux v5.3) it suspends fine but will not resume. The issue does not occur with Ubuntu 19.04 (linux v5.0). With 720P the machine just reboots to legacy, no other issues. Using Ubuntu kernel PPA versions I test linux v5.0, v5.1, v5.2 and fount the issue first occurs with v5.1. The number of backported patches from 4.19.66 -> 67 should be very limited right? Maybe we can identify from the commit message? Reply at: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1848771/comments/18 ** Changed in: ubuntu-release-upgrader Status: Unknown => Incomplete ** Changed in: ubuntu-release-upgrader Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
