Bug 26537 - Nouveau Driver Causing Display Issues after Kernel 5.6.6-1 upgrade
Summary: Nouveau Driver Causing Display Issues after Kernel 5.6.6-1 upgrade
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-24 19:36 CEST by Brian Rockwell
Modified: 2020-06-06 18:20 CEST (History)
3 users (show)

See Also:
Source RPM: kernel-5.6.6-1.mga7.src.rpm
CVE:
Status comment:


Attachments
Screen shot of dithering (122.53 KB, image/png)
2020-04-24 19:36 CEST, Brian Rockwell
Details
Journal from server (500.98 KB, application/gzip)
2020-04-24 19:37 CEST, Brian Rockwell
Details
dmesg from server (15.73 KB, application/gzip)
2020-04-24 19:38 CEST, Brian Rockwell
Details
nouveau_screen_desktop_artefacts_missing_characters_and_menus (601.48 KB, image/jpeg)
2020-06-06 18:20 CEST, marc laan
Details

Description Brian Rockwell 2020-04-24 19:36:13 CEST
Description of problem: Computer started experiencing screen dithering and artifacts after upgrade to Kernel 5.6.6-1.  This uses the Nouveau display driver.



Version-Release number of selected component (if applicable): 5.6.6-1  Kernel-Server-latest.i686

Hardware:

Video:  Vendor: ‎NVIDIA Corporation
Description: ‎C51 [GeForce 6150 LE]
Media class: ‎VGA compatible controller

$ uname -a
Linux localhost 5.6.6-server-1.mga7 #1 SMP Tue Apr 21 22:45:17 UTC 2020 i686 i686 i386 GNU/Linux


Boot Parameters:  noapic splash quiet noiswmd resume=UUID=afd38e0c-b4a5-46b9-bbc5-a3ed905b66b4 audit=0


How reproducible:  system starts dithering on the desktop after moving the mouse over different parts of the screen.  

this also happens in LibreOffice Writer.  It does not happen in Firefox.


Steps to Reproduce:
1.
2.
3.
Comment 1 Brian Rockwell 2020-04-24 19:36:49 CEST
Created attachment 11606 [details]
Screen shot of dithering
Comment 2 Brian Rockwell 2020-04-24 19:37:36 CEST
Created attachment 11607 [details]
Journal from server

Look at April 22nd and after.
Comment 3 Brian Rockwell 2020-04-24 19:38:00 CEST
Created attachment 11608 [details]
dmesg from server
Thomas Backlund 2020-04-24 19:44:33 CEST

Assignee: bugsquad => kernel
CC: (none) => tmb

Comment 4 Morgan Leijström 2020-04-24 20:36:38 CEST
I will check this on a couple machines this weekend.

CC: (none) => fri

Comment 5 Thomas Backlund 2020-04-24 22:00:06 CEST
(In reply to Brian Rockwell from comment #2)
> Created attachment 11607 [details]
> Journal from server
> 
> Look at April 22nd and after.

You should check the health of that disc...

I see:
Apr 22 14:09:57 localhost kernel: ata3: ATA_REG 0x41 ERR_REG 0x84
Apr 22 14:09:57 localhost kernel: ata3: tag : dhfis dmafis sdbfis sactive
Apr 22 14:09:57 localhost kernel: ata3: tag 0x10: 1 1 0 1  
Apr 22 14:09:57 localhost kernel: ata3: tag 0x11: 1 0 0 1  
Apr 22 14:09:57 localhost kernel: ata3: tag 0x12: 1 0 0 1  
Apr 22 14:09:58 localhost kernel: ata3: tag 0x13: 0 0 0 1  
Apr 22 14:09:58 localhost kernel: ata3.00: limiting speed to UDMA/100:PIO4
Apr 22 14:09:58 localhost kernel: ata3.00: exception Emask 0x1 SAct 0x4f0000 SErr 0x3800000 action 0x6 frozen
Apr 22 14:09:58 localhost kernel: ata3.00: Ata error. fis:0x21
Apr 22 14:09:58 localhost kernel: ata3: SError: { LinkSeq TrStaTrns UnrecFIS }
Apr 22 14:09:58 localhost kernel: ata3.00: failed command: READ FPDMA QUEUED
Apr 22 14:09:58 localhost kernel: ata3.00: cmd 60/18:80:e0:3c:04/00:00:00:00:00/40 tag 16 ncq dma 12288 in
                                           res 41/84:98:78:3d:04/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 14:09:58 localhost kernel: ata3.00: status: { DRDY ERR }
Apr 22 14:09:58 localhost kernel: ata3.00: error: { ICRC ABRT }
Apr 22 14:09:58 localhost kernel: ata3.00: failed command: READ FPDMA QUEUED
Apr 22 14:09:58 localhost kernel: ata3.00: cmd 60/30:88:08:3d:04/00:00:00:00:00/40 tag 17 ncq dma 24576 in
                                           res 41/84:98:78:3d:04/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 14:09:58 localhost kernel: ata3.00: status: { DRDY ERR }
Apr 22 14:09:58 localhost kernel: ata3.00: error: { ICRC ABRT }
Apr 22 14:09:58 localhost kernel: ata3.00: failed command: READ FPDMA QUEUED
Apr 22 14:09:58 localhost kernel: ata3.00: cmd 60/20:90:50:3d:04/00:00:00:00:00/40 tag 18 ncq dma 16384 in
                                           res 41/84:98:78:3d:04/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 14:09:58 localhost kernel: ata3.00: status: { DRDY ERR }
Apr 22 14:09:58 localhost kernel: ata3.00: error: { ICRC ABRT }
Apr 22 14:09:58 localhost kernel: ata3.00: failed command: READ FPDMA QUEUED
Apr 22 14:09:58 localhost kernel: ata3.00: cmd 60/18:98:78:3d:04/00:00:00:00:00/40 tag 19 ncq dma 12288 in
                                           res 41/84:98:78:3d:04/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 14:09:58 localhost kernel: ata3.00: status: { DRDY ERR }
Apr 22 14:09:58 localhost kernel: ata3.00: error: { ICRC ABRT }
Apr 22 14:09:58 localhost kernel: ata3.00: failed command: READ FPDMA QUEUED
Apr 22 14:09:58 localhost kernel: ata3.00: cmd 60/38:b0:78:e0:20/00:00:00:00:00/40 tag 22 ncq dma 28672 in
                                           res 41/84:98:78:3d:04/84:00:00:00:00/40 Emask 0x10 (ATA bus error)
Apr 22 14:09:58 localhost kernel: ata3.00: status: { DRDY ERR }
Apr 22 14:09:58 localhost kernel: ata3.00: error: { ICRC ABRT }
Apr 22 14:09:58 localhost kernel: ata3: hard resetting link
Apr 22 14:09:58 localhost kernel: ata3: nv: skipping hardreset on occupied port
Apr 22 14:09:58 localhost kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Apr 22 14:09:58 localhost kernel: ata3.00: configured for UDMA/100
Apr 22 14:09:58 localhost kernel: sd 2:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Apr 22 14:09:58 localhost kernel: sd 2:0:0:0: [sda] tag#16 Sense Key : Aborted Command [current] 
Apr 22 14:09:58 localhost kernel: sd 2:0:0:0: [sda] tag#16 Add. Sense: Scsi parity error
Apr 22 14:09:58 localhost kernel: sd 2:0:0:0: [sda] tag#16 CDB: Read(10) 28 00 00 04 3c e0 00 00 18 00
Apr 22 14:09:58 localhost kernel: blk_update_request: I/O error, dev sda, sector 277728 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
Apr 22 14:09:58 localhost kernel: sd 2:0:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
Comment 6 Brian Rockwell 2020-04-24 23:39:59 CEST
Thanks TMB

Yes I've been watching that and checking ECC errors.
Comment 7 Morgan Leijström 2020-04-29 21:14:33 CEST
No visual problems on my workstation, 64 bit i7, Nvidia GK104 [GeForce GTX 760], Plasma

[root@svarten morgan]# journalctl -b | grep nouveau
apr 29 20:47:36 svarten.tribun kernel: fb0: switching to nouveaufb from EFI VGA
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: NVIDIA GK104 (0e4070a2)
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: bios: version 80.04.bf.00.0a
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
...
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: allocated 3840x2160 fb: 0xa0000, bo 000000004a08f848
apr 29 20:47:36 svarten.tribun kernel: fbcon: nouveaudrmfb (fb0) is primary device
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: core notifier timeout
apr 29 20:47:36 svarten.tribun kernel: nouveau 0000:01:00.0: fb0: nouveaudrmfb frame buffer device
apr 29 20:47:36 svarten.tribun kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv
...
apr 29 20:47:36 svarten.tribun kernel: snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])


But why is nvidia module repeatedly initialised and unregistered??  (this is the same second)

[root@svarten morgan]# journalctl -b | grep nvidia
apr 29 20:47:36 svarten.tribun kernel: nvidia: loading out-of-tree module taints kernel.
apr 29 20:47:36 svarten.tribun kernel: nvidia: module license 'NVIDIA' taints kernel.
apr 29 20:47:36 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 29 20:47:36 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246
apr 29 20:47:36 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 29 20:47:36 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246
apr 29 20:47:36 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 245
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 29 20:47:36 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 245
apr 29 20:47:36 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 244
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 29 20:47:36 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 244
apr 29 20:47:37 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 240
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 29 20:47:37 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 240
apr 29 20:47:37 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 240
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 29 20:47:37 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 240
apr 29 20:47:38 svarten.tribun dkms-autorebuild.sh[1294]: nvidia-current (430.64-8.mga7.nonfree): Already installed on this kernel.
Comment 8 Morgan Leijström 2020-04-29 21:48:24 CEST
Meh!
Just a few minutes after posting that the desktop froze.
That was while changing desktop i think, i have four, with different programs.  One physical screen.  It froze while everything was semi-translucent.
I could move the mouse, but nothing responded, not even Ctrl-Alt-F3, nor clrl-del-del or ctrl-bkspc-bkspc.  Had to pull plug after some waiting.

Now on next boot:

# journalctl -b-1 | grep nouveau
...
apr 29 21:17:20 svarten.tribun kernel: nouveau 0000:01:00.0: gr: TRAP ch 6 [007f53d000 kwin_x11[9178]]
apr 29 21:17:20 svarten.tribun kernel: nouveau 0000:01:00.0: gr: GPC1/TPC1/MP trap: global 00000000 [] warp 3e0009 [ILLEGAL_INSTR_ENCODING]
apr 29 21:17:20 svarten.tribun kernel: nouveau 0000:01:00.0: gr: GPC2/TPC1/MP trap: global 00000000 [] warp 3e0009 [ILLEGAL_INSTR_ENCODING]
Comment 9 Morgan Leijström 2020-04-30 08:19:02 CEST
Tried to stress it to recreate that problem but, no.

Got another nouveau line in log though:

apr 29 22:21:32 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: core notifier timeout

But no visual problem.


Same line appeared after unlock of screensaver, and the desktop shold appear from faded, but flickered instead.  Switching desktops, it hung temporarily but this tim i could just waut a few swconds, and try again and it is back.  New line in log:

apr 30 08:10:22 svarten.tribun kwin_x11[6412]: qt.qpa.xcb: Unhandled client message:  "_NET_CURRENT_DESKTOP"

Can nvidia be interfering?  Now uninstalling nvidia:
- dkms-nvidia-current-430.64-8.mga7.nonfree.x86_64
- nvidia-current-cuda-opencl-430.64-8.mga7.nonfree.x86_64
- nvidia-current-doc-html-430.64-8.mga7.nonfree.x86_64
- nvidia-current-utils-430.64-8.mga7.nonfree.x86_64
- x11-driver-video-nvidia-current-430.64-8.mga7.nonfree.x86_64

And rebooting...
Comment 10 Morgan Leijström 2020-04-30 08:22:21 CEST
Now before reboot another issue: switching desktops it may switch but not update: i initially show image of one dektop, moving the mouse it updates parts of a program that is on the actual desktop. Kinda spooky.  Unusable.
Comment 11 Morgan Leijström 2020-04-30 11:26:20 CEST
I still get now and then:
apr 30 09:56:36 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: core notifier timeout

And it still seem to be loading nvidia proprieatary i assume? 
"out-of-tree module taints kernel", "license 'NVIDIA' taints kernel"

[root@svarten morgan]# journalctl -b | grep nvidia
apr 30 08:23:37 svarten.tribun kernel: nvidia: loading out-of-tree module taints kernel.
apr 30 08:23:37 svarten.tribun kernel: nvidia: module license 'NVIDIA' taints kernel.
apr 30 08:23:37 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 30 08:23:37 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246
apr 30 08:23:37 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 246
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 30 08:23:37 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 246
apr 30 08:23:37 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 245
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 30 08:23:37 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 245
apr 30 08:23:37 svarten.tribun kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 244
                                       NVRM: nouveau, rivafb, nvidiafb or rivatv 
apr 30 08:23:37 svarten.tribun kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 244
apr 30 08:23:37 svarten.tribun systemd-udevd[993]: ctx=0x55a180 path=/lib/modules/5.6.6-desktop-1.mga7/dkms/drivers/char/drm/nvidia-modeset.ko.xz error=No such file or directory


So how to really clean out all nvidia proprietary parts from the system more than removing nvidia packages?

/!\ Note this is a production machine and i need to get back to using nvidia-current with opencl and cuda !
Comment 12 Brian Rockwell 2020-04-30 16:33:41 CEST
sounds like I need to try kernel-desktop-latest and see if that behaves differently than kernel-server.

May try swapping drives later today.

Thanks everyone, seems nouveau is wonky regardless.
Comment 13 marc laan 2020-04-30 18:23:51 CEST
After upgrading my kernel on the 64 bit AMD pc from 5.5.15 to 5.6.6-1, the video began acting strange (see attached screenshot). 
On the screen names of files and titles of menus showed missing characters at random. Using the menus is almost impossible.

It seems mainly a desktop screen affair, as the Konsole is readable o.k.

I went back to kernel version 5.5.15, and the problem is not there.

My system is:

Advanced Micro Devices, Inc. [AMD]|K8 [Athlon64/Opteron] HyperTransport Technology Configuration.

Driver is nouveau, not nvidia (although my graphics card is nvidia, but not supported by MGA 7.1).

rpm -qa|grep -iE "kernel|nouveau"|sort
kernel-desktop-5.5.15-3.mga7-1-1.mga7
kernel-desktop-5.6.6-1.mga7-1-1.mga7
kernel-desktop-latest-5.6.6-1.mga7
kernel-firmware-20190603-1.mga7
kernel-firmware-nonfree-20200316-1.mga7.nonfree
lib64drm_nouveau2-2.4.101-2.mga7
x11-driver-video-nouveau-1.0.16-1.mga7

$ lspcidrake -v|grep -i vga
Card:NVIDIA GeForce 6100 to GeForce 7950: NVIDIA Corporation|NV44 [GeForce 6200 TurboCache] [DISPLAY_VGA] (vendor:10de device:0161 subv:1043 subd:81fe) (rev: a1)

marc.

CC: (none) => laan.marc

Comment 14 Thomas Backlund 2020-04-30 20:07:15 CEST
There is now several updates queued that can affect this:

x11-driver-video-nouveau-1.0.16-3.mga7:
https://bugs.mageia.org/show_bug.cgi?id=26575

x11-server-1.20.8-1.mga7:
https://bugs.mageia.org/show_bug.cgi?id=26573

mesa-20.0.6-1.mga7:
https://bugs.mageia.org/show_bug.cgi?id=26571

kernel-5.6.8-1.mga7:
https://bugs.mageia.org/show_bug.cgi?id=26570
Comment 15 Morgan Leijström 2020-04-30 20:16:12 CEST
Great!
I will try them tomorrow.

For a clean test and make sure no stuff or settings for nvidia proprietary drivers are left, do we need to do more than select to not use proprieatrye driver, and then remove nvidia packages, or can we do more?
Like removing files, settings, edit kernel boot arguments?
Comment 16 Morgan Leijström 2020-05-01 12:02:43 CEST
From Thomas on qa-discuss:
To clean out any nVidia stuff:

1. use mcc to switch to nouveau
2. switch to text console (Control-Alt-Fx and log in as root)
3. remove any nvidia rpms
4. run "dracut -f" to remove nvidia modules and references from initrd
5. reboot

(The reason for step 2 is that the DE can/will lock up when you remove the drivers) 


And before that I updated to all in comment 14
Rebooted, and journal is much cleaner now than before:

[root@svarten morgan]# journalctl -b | grep nvidia
maj 01 11:53:04 svarten.tribun systemd-udevd[1002]: ctx=0x231b180 path=/lib/modules/5.6.8-desktop-1.mga7/dkms/drivers/char/drm/nvidia-modeset.ko.xz error=No such file or directory

[root@svarten morgan]# journalctl -b | grep nouveau
maj 01 11:53:04 svarten.tribun kernel: fb0: switching to nouveaufb from EFI VGA
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: NVIDIA GK104 (0e4070a2)
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: bios: version 80.04.bf.00.0a
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: fb: 2048 MiB GDDR5
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: VRAM: 2048 MiB
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: TMDS table version 2.0
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB version 4.0
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB outp 00: 01000f02 00020030
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB outp 01: 02000f00 00000000
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB outp 02: 08011f82 00020030
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB outp 03: 02822f62 0f420010
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB outp 05: 04833fb6 0f420010
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB outp 06: 04033f72 00020010
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB conn 01: 01000131
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB conn 02: 00010261
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB conn 03: 00020346
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: DCB conn 04: 00000460
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: allocated 3840x2160 fb: 0xa0000, bo 000000004034530a
maj 01 11:53:04 svarten.tribun kernel: fbcon: nouveaudrmfb (fb0) is primary device
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: DRM: core notifier timeout
maj 01 11:53:04 svarten.tribun kernel: nouveau 0000:01:00.0: fb0: nouveaudrmfb frame buffer device
maj 01 11:53:04 svarten.tribun kernel: [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0
maj 01 11:53:04 svarten.tribun kernel: snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])
maj 01 11:53:09 svarten.tribun sensord[2171]: Chip: nouveau-pci-0100



I will continue to use the system like this occasionally over the weekend, and report back.
Comment 17 Morgan Leijström 2020-05-01 21:17:54 CEST
Less problems, but still desktop hung on me:

I have used it an hour accumulated, including thunderbird, libreoffice, video in firefox, test OK msw7 in virtualbox with firefox with video.
No visual artifact of any kind, no percieved delays.  All time BOINC have been chewing on all day.

But then i changed desktop, which visually works nicely, and have severalt imes durign the day, but this time it became unresponsive except for mouse pointer.  No keyboard chord works. Log say power button is detected but no shutting down action starts from that either.

I see it have logged:

maj 01 20:58:59 svarten.tribun kernel: nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
maj 01 20:58:59 svarten.tribun kernel: nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
maj 01 20:58:59 svarten.tribun kernel: nouveau 0000:01:00.0: fifo: channel 8: killed
maj 01 20:58:59 svarten.tribun kernel: nouveau 0000:01:00.0: fifo: engine 7: scheduled for recovery
maj 01 20:58:59 svarten.tribun kernel: nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery
maj 01 20:58:59 svarten.tribun kernel: nouveau 0000:01:00.0: fifo: fault 00 [READ] at 00000000a8001000 engine 1b [CE2] client 00 [GPC0/L1_0] reason 04 [UNBOUND_INST_BLOCK] on channel -1 [a0a2622000>
maj 01 20:58:59 svarten.tribun kernel: nouveau 0000:01:00.0: plasmashell[6529]: channel 8 killed!
maj 01 21:00:25 svarten.tribun systemd-logind[2047]: Power key pressed.
maj 01 21:00:40 svarten.tribun systemd-logind[2047]: Power key pressed.

...And later i held button for 4s to power it off.

Now i have to switch back to nvidia proprietary.
Comment 18 marc laan 2020-05-08 12:04:28 CEST
Updating to x11-driver-video-nouveau-1.0.16-3.mga7 didn't solve my problem of getting artifacts on the desktop screen.

Is there a way I can contribute by searching in the logs?

My system is:

Advanced Micro Devices, Inc. [AMD]|K8 [Athlon64/Opteron] HyperTransport Technology Configuration.

Driver is nouveau, not nvidia (although my graphics card is nvidia, but not supported by MGA 7.1).

Card:NVIDIA GeForce 6100 to GeForce 7950: NVIDIA Corporation|NV44 [GeForce 6200 TurboCache] [DISPLAY_VGA]

Marc.
Comment 19 marc laan 2020-06-06 18:20:37 CEST
Created attachment 11681 [details]
nouveau_screen_desktop_artefacts_missing_characters_and_menus

As mentioned in an earlier post, here's a screenshot of my desktop screen: many artefacts and missing menu lines after upgrading. Last three recent updates of MGA7 didn't correct this problem.

Marc.

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