Xorg freeze / nouveau driver fault ?

[Moray]

june@june-pc:~$ lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10
(Note: upgrade today from 19.04, which also froze randomly)
----------------------------------------------------
june@june-pc:~$ apt-cache dump | grep nouveau | grep Package
Package: xserver-xorg-video-nouveau
Package: xserver-xorg-video-nouveau:i386
Package: libdrm-nouveau2
Package: libdrm-nouveau2:i386
Package: xserver-xorg-video-nouveau-hwe-18.04
Package: xserver-xorg-video-nouveau-hwe-18.04:i386
Package: nouveau-firmware

june@june-pc:~$ apt-cache policy xserver-xorg-video-nouveau libdrm-nouveau2 xserver-xorg-video-nouveau-hwe-18.04
xserver-xorg-video-nouveau:
  Installed: 1:1.0.16-1
  Candidate: 1:1.0.16-1
  Version table:
 *** 1:1.0.16-1 500
        500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
        100 /var/lib/dpkg/status
libdrm-nouveau2:
  Installed: 2.4.99-1ubuntu1
  Candidate: 2.4.99-1ubuntu1
  Version table:
 *** 2.4.99-1ubuntu1 500
        500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
        100 /var/lib/dpkg/status
xserver-xorg-video-nouveau-hwe-18.04:
  Installed: (none)
  Candidate: 3:14.5
  Version table:
     3:14.5 500
        500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
----------------------------------------------------
Kernel MMIO FAULT errors being seen in syslog; such as:

Jan 26 15:21:44 June-PC kernel: [ 354.655752] nouveau 0000:00:10.0: bus: MMIO write of 00000000 FAULT at 00b030
Jan 26 15:31:26 June-PC kernel: [ 936.671821] nouveau 0000:00:10.0: gr: intr 00100000 [ERROR] nsource 00000002 [DATA_ERROR] nstatus 02000000 [BAD_ARGUMENT] ch 6 [0006b000 gnome-shell[1987]] subc 7 class 4497 mthd 0208 data 04000248

Seeing some of these while system operating 'normally' but when systems freezes needing hard reboot there is generally one or more MMIO Fault message just prior.

No obvious correlation between activity/application in use crash. Latest instance, after 19.10 upgrade was system freeze on initial opening of Mozilla Thunderbird. Thunderbird then opened fine after reboot.

----------------------------------------------------
syslog "grep -E "(MMIO|nouv|FAULT|BOOT)" from boot onwards attached ("nouveau-driver-syslog-errors.txt")

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 26 15:59:09 2020
DistUpgraded: 2020-01-26 11:14:39,179 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: eoan
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since before I upgraded
GraphicsCard:
 NVIDIA Corporation C73 [GeForce 7100 / nForce 630i] [10de:07e1] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] C73 [GeForce 7100 / nForce 630i] [1025:026c]
InstallationDate: Installed on 2020-01-14 (12 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 001 Device 002: ID 0bda:0182 Realtek Semiconductor Corp. USB2.0-CRW
 Bus 001 Device 004: ID 04a9:178d Canon, Inc. PIXMA MG6853
 Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Packard Bell ixtreme M3720
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-26-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to eoan on 2020-01-26 (0 days ago)
dmi.bios.date: 07/21/2009
dmi.bios.vendor: AMI
dmi.bios.version: P01-A3
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: MCP73PVT-PM
dmi.board.vendor: Packard Bell
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell
dmi.modalias: dmi:bvnAMI:bvrP01-A3:bd07/21/2009:svnPackardBell:pnixtremeM3720:pvr:rvnPackardBell:rnMCP73PVT-PM:rvr:cvnPackardBell:ct3:cvr:
dmi.product.family: Packard Bell Desktop
dmi.product.name: ixtreme M3720
dmi.product.sku: To Be Filled By O.E.M.
dmi.sys.vendor: Packard Bell
modified.conffile..etc.logrotate.d.apport: [modified]
mtime.conffile..etc.logrotate.d.apport: 2020-01-14T10:55:34.061078
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Moray (morayg7)]

Hi

Basic symptom is screen/system locks up, and PC needs a power cycle to
recover it ... it's completely un-response to mouse/keyboard.

This is my wife's PC, which I've recently weaned off Win7. A vanilla
installation of Ubunto used for browsing/e-mail (Firefox/Thunderbird).

Initially I installed 19.04 a few weeks ago which had a number of
lockups, and then a few days ago updated to 19.10 which then also
exhibited the problem.

Since 19.10 didn't fix the problem I sat down and delved a bit deeper
and generated the bug report.

I haven't identified any obvious trigger activity/application, and I've
seen it occur during login process and also when launching Mozilla
Thunderbird.

Checking syslog I can usually find one of the "nouveau MMIO fault"
messages timed just before the lockup (see submitted syslog dump); but
when looking in more detail to make this report I also found some
apparently occurring during 'normal' operation - i.e system still
operational.

Any suggestions about gathering more useful info for you ?

Cheers

Moray

On 28/01/2020 03:34, Daniel van Vugt wrote:
> This looks like a nouveau kernel problem, but can you describe the
> problem you are experiencing?
>
> ** Tags added: nouveau
>
> ** Package changed: xorg (Ubuntu) => linux (Ubuntu)
>
--
Moray Goodwin

[Daniel van Vugt (vanvugt)]

Nvidia recommends driver version 304 for your model of GPU, but unfortunately that's now too old to support and stopped shipping with Ubuntu after 16.04.

So you have a few options:

  * Keep this bug open and try to solve it by trying newer kernel versions like https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/

  * Reinstall the machine with Ubuntu 16.04 which has an official Nvidia driver that supports the hardware.

  * Change the graphics card to something newer, which will then avoid the need for the unreliable nouveau driver.

[Moray (morayg7)]

Hi

I was sort of afraid of the age issue. but having just weaned wife off
one EOL O/S probably don't want to step back to another with limited
life  :-)

Looks like hardware upgrade required.

Cheers

     Moray

On 29/01/2020 02:11, Daniel van Vugt wrote:
> Nvidia recommends driver version 304 for your model of GPU, but
> unfortunately that's now too old to support and stopped shipping with
> Ubuntu after 16.04.
>
> So you have a few options:
>
> * Keep this bug open and try to solve it by trying newer kernel
> versions like https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5/
>
> * Reinstall the machine with Ubuntu 16.04 which has an official Nvidia
> driver that supports the hardware.
>
> * Change the graphics card to something newer, which will then avoid
> the need for the unreliable nouveau driver.
>