| Summary: | Kernel 4.13.1 breaks screen output | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Axel braun <axel.braun> | ||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
| Severity: | major | ||||||||||
| Priority: | medium | CC: | 2bluesc, alexvillacislasso, creideiki+freedesktop-bugzilla, freedesktop_bugzilla, intel-gfx-bugs, jano.vesely, jefferym, serhiy.int | ||||||||
| Version: | unspecified | Keywords: | regression | ||||||||
| Hardware: | Other | ||||||||||
| OS: | All | ||||||||||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=98930 | ||||||||||
| Whiteboard: | ReadyForDev | ||||||||||
| i915 platform: | I945GM | i915 features: | display/Other | ||||||||
| Attachments: |
|
||||||||||
|
Description
Axel braun
2017-09-21 16:15:49 UTC
Hello Axel, Could you please attach dmesg with drm.debug=0x1e log_bug_len=2M parameter on grub from boot till problem. Also is your bios updated? Thanks. Created attachment 134496 [details]
dmesg output
(In reply to Elizabeth from comment #1) > Hello Axel, > Could you please attach dmesg with drm.debug=0x1e log_bug_len=2M parameter > on grub from boot till problem. Also is your bios updated? BIOS is the one before the last - changed in 2009. there is no update anymore for this old hardware Can confirm this problem on a Samsung NC10 with Intel Atom (945GSE) graphics. Using newest Arch Linux 32 bit kernel 4.13.9, the left ~70% of the screen becomes a flickering mess after the modesetting driver is loaded. Kernel 4.12.8 works. (In reply to Felix W from comment #4) > Can confirm this problem on a Samsung NC10 with Intel Atom (945GSE) > graphics. Using newest Arch Linux 32 bit kernel 4.13.9, the left ~70% of the > screen becomes a flickering mess after the modesetting driver is loaded. > Kernel 4.12.8 works. Thanks for the update Felix, in that case, it could be a regression, if easy reproducible could you please try to bisect the issue?? (In reply to Elizabeth from comment #5) > (In reply to Felix W from comment #4) > > Can confirm this problem on a Samsung NC10 with Intel Atom (945GSE) > > graphics. Using newest Arch Linux 32 bit kernel 4.13.9, the left ~70% of the > > screen becomes a flickering mess after the modesetting driver is loaded. > > Kernel 4.12.8 works. > Thanks for the update Felix, in that case, it could be a regression, if easy > reproducible could you please try to bisect the issue?? I've been doing bisection for the users [1], but it's blocked by another issue, which hang the system at initramfs. Instead of bisecting the bisection, can you take a look directly? [1] https://bugs.launchpad.net/linux/+bug/1724639 Took the time to bisect the issue on my NC10. Compiling the kernel on this machine takes nearly 3 hours even with an SSD, so sorry for the delay. ;-) git bisect start # bad: [569dbb88e80deb68974ef6fdd6a13edb9d686261] Linux 4.13 git bisect bad 569dbb88e80deb68974ef6fdd6a13edb9d686261 # good: [6f7da290413ba713f0cdd9ff1a2a9bb129ef4f6c] Linux 4.12 git bisect good 6f7da290413ba713f0cdd9ff1a2a9bb129ef4f6c # good: [ac7b75966c9c86426b55fe1c50ae148aa4571075] Merge tag 'pinctrl-v4.13-1' of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl git bisect good ac7b75966c9c86426b55fe1c50ae148aa4571075 # bad: [9c284c41c0886f09e75c323a16278b6d353b0b4a] mmc: tmio-mmc: fix bad pointer math git bisect bad 9c284c41c0886f09e75c323a16278b6d353b0b4a # good: [f263fbb8d60824993c1b64385056a3cfdbb21d45] Merge tag 'pci-v4.13-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci git bisect good f263fbb8d60824993c1b64385056a3cfdbb21d45 # bad: [04d4fb5fa63876d8e7cf67f2788aecfafc6a28a7] Merge branch 'drm-next-4.13' of git://people.freedesktop.org/~agd5f/linux into drm-next git bisect bad 04d4fb5fa63876d8e7cf67f2788aecfafc6a28a7 # bad: [562ff059bd5f8f04881256532c6d835af3db55bd] Merge tag 'omapdrm-4.13-v2' of git://git.kernel.org/pub/scm/linux/kernel/git/tomba/linux into drm-next git bisect bad 562ff059bd5f8f04881256532c6d835af3db55bd # bad: [d2f5e36df61f4f06b9a52605fba23b3c3608efca] drm/i915/skl+: Perform wm level calculations in separate function git bisect bad d2f5e36df61f4f06b9a52605fba23b3c3608efca # good: [29ef3fa987edb9768e19a6325030e1d2d58e29de] drm/i915: Unwrap top level fence-array git bisect good 29ef3fa987edb9768e19a6325030e1d2d58e29de # bad: [659056f257e01fbc81e7d0887af7551d4f145130] drm/i915: Split cursor check_plane into i845 and i9xx variants git bisect bad 659056f257e01fbc81e7d0887af7551d4f145130 # good: [9bacd4b1f8553428c5723e4c8f2ca491b400e429] drm/i915/dp: Check error return during DPCD capability queries git bisect good 9bacd4b1f8553428c5723e4c8f2ca491b400e429 # good: [0f95ff8505b25aa29530818afcf12ff08399ccf5] drm/i915: Refactor the g4x TLB miss w/a to a helper git bisect good 0f95ff8505b25aa29530818afcf12ff08399ccf5 # good: [d509e28b70e45ea0699128764d05893bcf347007] drm/i915: Parametrize cursor/primary pipe select bits git bisect good d509e28b70e45ea0699128764d05893bcf347007 # bad: [cd5dcbf1b26c60dfa8fd8628fd2fcf3d33877c63] drm/i915: Clean up cursor junk from intel_crtc git bisect bad cd5dcbf1b26c60dfa8fd8628fd2fcf3d33877c63 # bad: [1cecc830e6b662a765d60860112cf69182b56b8e] drm/i915: Refactor CURBASE calculation git bisect bad 1cecc830e6b662a765d60860112cf69182b56b8e # bad: [282dbf9b017bc6d5fdaeadf14e534c2fe22fee2d] drm/i915: Pass intel_plane and intel_crtc to plane hooks git bisect bad 282dbf9b017bc6d5fdaeadf14e534c2fe22fee2d # first bad commit: [282dbf9b017bc6d5fdaeadf14e534c2fe22fee2d] drm/i915: Pass intel_plane and intel_crtc to plane hooks I reverted the bad commit on top of v4.13 and added some possibly dirty workarounds to make it compile. Will attach both commits as patches. Unfortunately, I had no time to look into it further but maybe you'll identify the culprit quickly. It may be relevant that the cursor is still rendered fine over the whole screen area even if the regression is present in the kernel. Created attachment 135694 [details] [review] Patch for 4.13 reverting bad commit Created attachment 135695 [details] [review] Patch (2) for 4.13 fixing compilation after reverting the bad commit *** Bug 102931 has been marked as a duplicate of this bug. *** (In reply to Felix W from comment #7) > # first bad commit: [282dbf9b017bc6d5fdaeadf14e534c2fe22fee2d] drm/i915: > Pass intel_plane and intel_crtc to plane hooks Hmm. I failed to realize this was such a recent regression, and so widespread. Thanks for the bisect. Can someone please verify that these backports work: git://github.com/vsyrjala/linux.git plane_assert_v4.13 git://github.com/vsyrjala/linux.git plane_assert_v4.14 If everything looks good I'll try to get the fixes into the next 4.15-rc so that we can get the backports flowing into the stable kernels ASAP. (In reply to Ville Syrjala from comment #11) > (In reply to Felix W from comment #7) > > # first bad commit: [282dbf9b017bc6d5fdaeadf14e534c2fe22fee2d] drm/i915: > > Pass intel_plane and intel_crtc to plane hooks > > Hmm. I failed to realize this was such a recent regression, and so > widespread. Thanks for the bisect. > > Can someone please verify that these backports work: > git://github.com/vsyrjala/linux.git plane_assert_v4.13 > git://github.com/vsyrjala/linux.git plane_assert_v4.14 > > If everything looks good I'll try to get the fixes into the next 4.15-rc so > that we can get the backports flowing into the stable kernels ASAP. Alex here, plane_assert_v4.14 works correctly for me on my Acer Aspire One that exhibited the bug with unpatched 4.13.x . Just finished testing plane_assert_v4.13 and plane_assert_v4.14 on my Samsung NC10 - they both work without any graphical issues. Thank you! I also have a Intel Atom N270 (with 945GSE) device that is affected by this regression. The console is shifted down and offscreen by two lines and X would just produce some colorful pixels at the top. plane_assert_v4.14 fixed this for me as well. Thank you. Just a quick inquire. Is this fix already in some 4.15rc? (In reply to sergio.callegari from comment #15) > Just a quick inquire. Is this fix already in some 4.15rc? As far as I can see, no (up to v4.15-rc5). I'm on a triple-boot Asus eee-pc 1000H (2 Mint, 1 Manjaro (intel-ucode removed)), hope my findings can help to fix this: This is not a kernel issue by itself but also grub issue, triggered by the ‘fixed’ kernels of the 4.13/4.14 series, both in Mint and Manjaro. In a nutshell: If you want to boot a ‘fixed’ kernel of the 4.13 or 4.14 series via the 2 top lines of your grub menu it will glitch, both on Mint and on Manjaro, but booting the ‘fixed’ kernels further down the grub menu works fine. If you then sudo grub-install /dev/sda from an OS further down the menu, the error shifts to the new OS in control of grub, allowing the others to boot without problem, including the one that glitched when in control of grub. Other peculiarities of this glitch: - clicks on the black bit are ‘getting through’ to windows below, mouse-overs of windows below are visible on cursor icon status changes, you can ‘feel’ your way to the title bar, drag it into the 20% and use it - if you remote desktop into your glitched machine there is no glitch Also, you can fix the glitch from within the glitched system, here 2 ways: I use ‘newrez’ script to change my eee-pc resolution on the fly, (https://www.linux-apps.com/content/show … nt=1346861) Place newrez.sh where you can see it, the 20% strip, run it (e.g reloading default) and the glitch is gone (Run ‘newrez default' at startup and you can use the machine normally without GRUB_GFXPAYLOAD_LINUX="text"). Similarly, I can fix it on my eee-pc by running: xrandr --newmode "1024x600_60.00" 49.00 1024 1072 1168 1312 600 603 613 624 -hsync +vsync xrandr --addmode VGA1 1024x600_60.00 xrandr --output VGA1 --mode 1024x600_60.00 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. (In reply to Jani Saarinen from comment #18) > 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. Currently running 4.15.10 in Fedora 27 on the Acer Aspire One. The bug has been fixed since 4.15.3 . OK, thanks for the feedback, resolving. |
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.