Created attachment 135581 [details] dmesg output for drm-tip b4da247 on Inspiron 1525 Per comment 68 of bug 96781, I am filing this separate bug. Affected machine is Dell Inspiron 1525 with GM965. Running the `xrandr` command or switching VTs is sufficient to trigger this issue. Currently using Ubuntu 17.10 (64 bit), though this issue has been present for the past few versions. At the moment, my ability to test any fixes is limited to using drm-tip debs from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/ . The issue is still present as of commit b4da24717364bc69bb981a1536be64413a582f3a. Example dmesg output is attached.
Hello Christopher, Could you please attach a dmesg with debug information, drm.debug=0xe parameter on grub? Thank you.
Created attachment 135655 [details] dmesg output with drm.debug=0xe for drm-tip b4da247 on Inspiron 1525 (In reply to Elizabeth from comment #1) > Hello Christopher, > Could you please attach a dmesg with debug information, drm.debug=0xe > parameter on grub? Thank you. Done, attached. (I have stuck with b4da247 due to a regression as of 8ec4b7c that prevents the system from booting.)
First of all. Sorry about spam. This is mass update for our bugs. Sorry if you feel this annoying but with this trying to understand if bug still valid or not. If bug investigation still in progress, please ignore this and I apologize! If you think this is not anymore valid, please comment to the bug that can be closed. If you haven't tested with our latest pre-upstream tree(drm-tip), can you do that also to see if issue is valid there still and if you cannot see issue there, please comment to the bug.
Created attachment 138613 [details] dmesg output with drm.debug=0xe for drm-tip e29a105 on Inspiron 1525 (In reply to Jani Saarinen from comment #3) > If you haven't tested with our latest pre-upstream tree(drm-tip), can you do > that also to see if issue is valid there still and if you cannot see issue > there, please comment to the bug. I have tested again with drm-tip commit e29a105, and it appears that the issue is still present. Attached is a new dmesg output.
Again a dupe of 93782 :( *** This bug has been marked as a duplicate of bug 93782 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.