[Kernel-packages] [Bug 1751268]

2019-06-17 Thread Ahabig
Bisecting is a manual process, since it's some option (or combination thereof) enabled in Fedora's .config that's the problem rather than a bad commit which git can help with. You're right in that it's not drm-tip itself. In fact, while the original weirdness manifested itself in drm, it also

[Kernel-packages] [Bug 1751268]

2019-04-04 Thread Ahabig
nuts. Going to 4.20.15-200.fc29.x86_64 failed again... and backing up to 4.20.13-200 also failed. Tricked by a race condition into thinking that that version actually worked? Bad interaction with some other update applied since? Dunno. drm-tip (now at 5.1-rc3) continues to work. Fedora 29 is

[Kernel-packages] [Bug 1751268]

2019-03-10 Thread Ahabig
Just accidentally booted into fedora's 4.20.13-200.fc29.x86_64 (have been happily running the drm-tip)... and it worked! Will try reading changelogs to get some clues. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1751268]

2019-01-19 Thread Ahabig
Sorry for the long silence. Going has been slow: it takes a while to do a tweak/test/reboot/hang cycle. Especially since the disk controller gets munged upon the bug happening, even persisting across a power cycle (!) about 50% of the time (I have no idea how such a thing is even possible).

[Kernel-packages] [Bug 1751268]

2018-11-07 Thread Ahabig
ok, all's not wine and roses. When exiting X, it goes into the same style lockup as used to happen on boot. Which includes crashing so hard that often times (but not all the time) the BIOS can't find the boot disk after the next power cycle. At least the bug moving further back in the chain

[Kernel-packages] [Bug 1751268]

2018-11-07 Thread Ahabig
So since last week, kernel-4.18.7-100.fc27.x86_64 came out on the Fedora updates repo. Tried it just now in the process of looking at the next batch of options differences... and it didn't crash! And all the other drivers I need on this laptop are enabled (which wasn't the case with your drm-tip

[Kernel-packages] [Bug 1751268]

2018-09-17 Thread Ahabig
I do: even with the current Fedora Kernel (4.17.19) and the latest Lenovo BIOS (which got updated recently, presumably for spectre mitigation). Just verified this when booting this morning (accidentally chose the wrong kernel in grub). I have made little progress on narrowing down which kernel