On Thu, 2018-07-26 at 10:38 +-0200, Patrick Steinhardt wrote: +AD4- That still leaves the other problem of broken suspend. I've just +AD4- checked with v4.17.10, and it's still there: as soon as I resume +AD4- from suspend, the kernel oopses and reboots the machine. I guess +AD4- I'll have to do another debugging session and see where it fails +AD4- exactly (and no, this time there are no more changes to the +AD4- kernel tree). Can you share the kernel oops details before you start running a bisect? Thanks, Bart.
