Bug 1483037 - nouveau screen corruption after kernel 4.12.5 update
Summary: nouveau screen corruption after kernel 4.12.5 update
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 26
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-18 16:13 UTC by Barry Scott
Modified: 2018-03-27 18:04 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-27 18:04:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Barry Scott 2017-08-18 16:13:35 UTC
Description of problem:

After updating to kernel 4.12.5-300 from 4.11.11-300 screen is draw with
corrupt areas. For example start a new Konsole and start typing a the
bash prompt to see the problem.

Also seen in PyQt apps and firefix.

Version-Release number of selected component (if applicable):

kernel 4.12.5-300

How reproducible:

Steps to Reproduce:
1. Boot with 4.12.5-300 kernel
2. Login with KDE
3. Start Konsole
4. type at bash prompt
5. text echoed will show graphics corruption
6. After you type enough lines the problem will go away.
7. start new konsole to get the problem back.

Actual results:

Text is not draw correctly, graphical corruption over text.

Expected results:

Nice text without corruption.


Additional info:

Problem is not present with kernel 4.11.11-300.

[    1.509500] fb: switching to nouveaufb from EFI VGA
[    1.509611] nouveau 0000:01:00.0: NVIDIA GP106 (136000a1)
[    1.625196] nouveau 0000:01:00.0: bios: version 86.06.4b.00.20
[    1.625932] nouveau 0000:01:00.0: fb: 6144 MiB GDDR5
[    1.628896] nouveau 0000:01:00.0: DRM: VRAM: 6144 MiB
[    1.628897] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    1.628898] nouveau 0000:01:00.0: DRM: BIT table 'A' not found
[    1.628899] nouveau 0000:01:00.0: DRM: BIT table 'L' not found
[    1.628900] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[    1.628900] nouveau 0000:01:00.0: DRM: DCB version 4.1
[    1.628901] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f42 04620030
[    1.628902] nouveau 0000:01:00.0: DRM: DCB outp 01: 04811f96 04600020
[    1.628903] nouveau 0000:01:00.0: DRM: DCB outp 02: 04011f92 04620020
[    1.628903] nouveau 0000:01:00.0: DRM: DCB outp 03: 04822f86 04600010
[    1.628904] nouveau 0000:01:00.0: DRM: DCB outp 04: 04022f82 04620010
[    1.628904] nouveau 0000:01:00.0: DRM: DCB outp 06: 02033f62 04620010
[    1.628905] nouveau 0000:01:00.0: DRM: DCB outp 07: 02844f76 04600020
[    1.628905] nouveau 0000:01:00.0: DRM: DCB outp 08: 02044f72 00020020
[    1.628906] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001031
[    1.628906] nouveau 0000:01:00.0: DRM: DCB conn 01: 02000146
[    1.628907] nouveau 0000:01:00.0: DRM: DCB conn 02: 01000246
[    1.628907] nouveau 0000:01:00.0: DRM: DCB conn 03: 00010361
[    1.628908] nouveau 0000:01:00.0: DRM: DCB conn 04: 00020446
[    1.628908] nouveau 0000:01:00.0: DRM: Pointer to flat panel table invalid
[    1.799222] nouveau 0000:01:00.0: hwmon_device_register() is deprecated. Please convert the driver to use hwmon_device_register_with_info().
[    1.855790] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[    2.232913] nouveau 0000:01:00.0: DRM: allocated 1920x1200 fb: 0x60000, bo ffff96b58c380000
[    2.232964] fbcon: nouveaufb (fb0) is primary device
[    2.641449] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[    2.655034] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0

Comment 1 Barry Scott 2017-10-16 17:46:58 UTC
It turns out that the problem here is that the wrong driver is used.

"modesetting" was used and not "nouveau".

I raised this on the nouveau bug tracker and using the nouveau driver fixed all problems. https://bugs.freedesktop.org/show_bug.cgi?id=103132

They said on that the bug could be that distro defaults to the wrong driver.

Comment 2 Laura Abbott 2018-02-28 03:44:38 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs.
 
Fedora 26 has now been rebased to 4.15.4-200.fc26.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Barry Scott 2018-03-27 17:28:25 UTC
Current kernels work well.

I consider that whatever was wrong has been fixed.

Comment 4 Laura Abbott 2018-03-27 18:04:31 UTC
Thanks for letting us know


Note You need to log in before you can comment on or make changes to this bug.