[nouveau] [GeForce 6150SE nForce 430] PC freezes and crashes

[Diogo Gomes]

When using the nouveau graphics driver my pc freezes and crashes.

WORKAROUND: Use the proprietary nvidia driver.

WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Thu Feb 1 01:36:25 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] [1043:8234]
InstallationDate: Installed on 2017-11-23 (69 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus CX3900/DX4000/DX4050]
 Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0602
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M2N-MX SE Plus
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev x.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Feb 1 01:34:53 2018
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input HID 1241:1166 MOUSE, id 8
 input AT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: nouveau

[penalvch (penalvch)]

Diogo Gomes, thank you for reporting this and helping make Ubuntu better.

1) To clarify, after the freeze/crash, are there crash files in /var/crash?

2) Could you please advise when the freeze/crash happens?

3) Could you please post a log and screenshot of the freeze/crash?

4) To clarify, if you use the proprietary nvidia drivers, does the computer still freeze/crash?

5) To see if this is already resolved in Ubuntu, could you please test http://cdimage.ubuntu.com/daily-live/20180131/ and advise to the results?

[Diogo Gomes (diogogomes)]

1) I have this files in /var/crash but I think that is not related:
_usr_bin_gnome-disks.1000.crash _usr_bin_gnucash.1000.uploaded _usr_bin_nautilus.1000.upload
_usr_bin_gnome-disks.1000.upload _usr_bin_lutris.1000.crash _usr_bin_nautilus.1000.uploaded
_usr_bin_gnome-disks.1000.uploaded _usr_bin_lutris.1000.upload _usr_lib_xdg-desktop-portal_xdg-desktop-portal.0.crash
_usr_bin_gnucash.1000.crash _usr_bin_lutris.1000.uploaded _usr_lib_xdg-desktop-portal_xdg-desktop-portal.0.upload
_usr_bin_gnucash.1000.upload _usr_bin_nautilus.1000.crash

2) The freeze/crash is random and every time that happens, I need to reboot manually.

3) Can you explain what log do you need? A screenshot is impossible because of 2).

4) With proprietary drivers do not crash.

5) This is my production machine and if you don't mind I don't want to install 18.04 until it's stable. I have 90% sure that is not yet resolved because I see a lot of bugs related with this (years) and until now none have been fixed.

I'm able to continue to reporting and testing without replace all system.

(I deleted some attachments with private information. If you need them, please say me what is and I re-upload it)

[Diogo Gomes (diogogomes)]

Christopher, I changed to new because I answered to your questions, please tell me if you need something more to be completed.

[penalvch (penalvch)]

>"3) Can you explain what log do you need?"

dmesg and xorg.

>"5) This is my production machine and if you don't mind I don't want to install 18.04 until it's stable."

If the problem is reproducible with a live environment, then testing that is fine.

[Diogo Gomes (diogogomes)]

dmesg is empty, xorg logs are already uploaded.

I'll test with a live environment, thanks

[penalvch (penalvch)]

Diogo Gomes, to advise, you would need to reproduce the freeze/crash then upload the logs. Just uploading logs without this is useless.

[Diogo Gomes (diogogomes)]

These are the logs, when the system crashes, I can't use the system. These are the logs after reboot after the crash.

I remember that 1 year or so ago, I saw one log finishing with something like a kernel panic error (with many 000000) but I don't remember what is to upload after the reboot after the crash.

[penalvch (penalvch)]

Diogo Gomes:

>"These are the logs, when the system crashes, I can't use the system. These are the logs after reboot after the crash."

I'm not sure what you mean here.

>"I remember that 1 year or so ago, I saw one log finishing with something like a kernel panic error (with many 000000)"

Unfortunately, this is too vague to be useful.

>"but I don't remember what is to upload after the reboot after the crash."

You want to capture logs after the crash, and before a reboot. Please see https://help.ubuntu.com/community/DebuggingSystemCrash .

[Diogo Gomes (diogogomes)]

Christopher M. Penalver,

It was what I did. Since the system crashes, I can't do nothing without reboot manually in the hardware button.

All logs are from reboot after the crash, it's the only way to submit them.

I remember an error from a year ago that looked like panic kernel. Something with tens of "000000" on the last line before rebooting. But I can not remember which log is to upload it.

I think it was in the /var/log/journal folder but it does not exist in this version...

[Diogo Gomes (diogogomes)]

Sorry, launchpad do not update and I didn't see my and your message (it's why it's duplicated).

I'll capture the logs after the crash an then upload it.

Thanks

[Diogo Gomes (diogogomes)]

I found the older kern.log with the error:

Asus kernel: [ 137.798056] nouveau 0000:00:0d.0: bus: MMIO write of 060f0001 FAULT at 00b010
Asus kernel: [ 138.454584] nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b000
Asus kernel: [ 139.001369] nouveau 0000:00:0d.0: bus: MMIO write of 04f70001 FAULT at 00b000
Asus kernel: [ 139.308534] nouveau 0000:00:0d.0: bus: MMIO write of 00000000 FAULT at 00b010
Asus kernel: [ 139.835984] nouveau 0000:00:0d.0: bus: MMIO write of 049e0001 FAULT at 00b010
\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00

The link to one of the logs: https://launchpadlibrarian.net/310562249/kern.log

I subscribe you to issue #1649566.

Maybe this is a duplicate from #1649566.

[penalvch (penalvch)]

Diogo Gomes, please stop changing the Description, adding packages to this report, subscribing me to bugs when I didn't ask, etc.

[Diogo Gomes (diogogomes)]

Sorry but I change and add because is the same bug that I have since 2016. Maybe I need to wait 2 more years or change distro...

[penalvch (penalvch)]

Diogo Gomes, to advise, nobody has enough information to debug or root cause any of the reports at this point because all the logs on all reports don't include useful information. However, developers who know what is a duplicate of what submit patches to fix the issue.

Also, here on Launchpad, each person with their hardware and issue has a separate report, versus everyone piles onto one report with similar symptom(s), wastes time claiming what is a duplicate without root causing in code, etc.

In addition, because you haven't tested latest packages and then provide useful logs, upstream developers aren't going to be focusing on your issue. Some log you grabbed years ago from an old distro isn't useful.

Hence, until you provide the requested information from https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/comments/9 you may be holding your breath for a fix that never happens.

[Diogo Gomes (diogogomes)]

Once again, it's impossible capture before reboot. The system crashes tottally.

> In addition, because you haven't tested latest packages and then provide useful logs, upstream developers aren't going to be focusing on your issue. Some log you grabbed years ago from an old distro isn't useful.
I tested in live and crashes and do not stored any logs, it's the reason why I didn't upload. I can't do it in a production machine.

> Some log you grabbed years ago from an old distro isn't useful.
I can upload the new if you want, it's same information.

> you may be holding your breath for a fix that never happens
It's disappointing and unprofessional because I already said that I can't use the system when it crashes

[penalvch (penalvch)]

Diogo Gomes:
>"I tested in live and crashes and do not stored any logs, it's the reason why I didn't upload."

Using the following in a live environment may yield something useful https://wiki.ubuntu.com/DebuggingKernelBoot .

>"I can't do it in a production machine."

If the above doesn't providing anything, then you will have to either dual boot Bionic, or backup your production install and replace with Bionic temporarily to gather something useful for upstream.

[Diogo Gomes (diogogomes)]

I add the last 10min of kern.log before crash happen.

Please tell me if is useful.

I take a picture too, should I upload it?

[Diogo Gomes (diogogomes)]

I upload a possible "screenshot" of the crash.

Al information is complete for the 16.04 LTS.

[penalvch (penalvch)]

Diogo Gomes:
>"I add the last 10min of kern.log before crash happen. Please tell me if is useful."

Please attach xorg and dmesg in full. In the future, always attach logs in their entirety (no snips).

>"I take a picture too, should I upload it?"

Yes please.

[penalvch (penalvch)]

Diogo Gomes:
>"Al information is complete for the 16.04 LTS"

Once its been completed for the latest release, then it can be upstreamed.

[Diogo Gomes (diogogomes)]

I had a full copy of kern.log, I attached it.

(Sorry for only post last 10min in other attachment)

[Diogo Gomes (diogogomes)]

Christopher M. Penalver,

I have not had availability to test version 18.04 on a new disc but I have more information:

- After updating the packages xorg-server....hwe... I decided to test the Open Source drivers again and got improvements.

- Due to these improvements and to the system crashing less, I detected a pattern in the crashes. It may not be related but crashes usually happen when I adjust the size of a window manually.

I'll let you know as soon as I have more information.

[Diogo Gomes (diogogomes)]

Christopher M. Penalver,

Just to inform that after upgrading the packages with ppa:oibaf/graphics-drivers, I have a stable system.

[Diogo Gomes (diogogomes)]

Christopher M. Penalver,

After upgrading to 18.04, I get the issues again and I can't select any graphics drivers (empty screen in settings).

Can we change this to confirmed?

Please let me know if you need more information.

Thank you

[penalvch (penalvch)]

Diogo Gomes:

1) This isn't Confirmed as defined by https://wiki.ubuntu.com/Bugs/Status .

2) Without providing logs in full (not snips), stating "I get the issues again" is not helpful. Please provide logs following https://help.ubuntu.com/community/DebuggingSystemCrash .

3) Please provide a screenshot of what issue are talking about in 18.04.

[Diogo Gomes (diogogomes)]

Christopher M. Penalver,

Apologize me, I was just following your past indications that it can be confirmed after tested on 18.04 and answer at your previous question like you can confirm.

2) Should I remove the old but equal logs of 16.04 and replace with the new ones of 18.04?

3) I'm talking about the same issue and same screen, do you need a screenshot equal to the older one?

Thank you for your time

[Diogo Gomes (diogogomes)]

This log contains the mentioned error:

\00\00\00\00\00\00\00\00\00\00\00\00\00\00....

[Diogo Gomes (diogogomes)]

Updates of same issue for Ubuntu 18.04:

> WORKAROUND: Use the proprietary nvidia driver.

It's not possible use this workaround because the version 18.04 not contains any driver to select in the settings.

---

> WORKAROUND: Use PPA from https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers

This workaround dos not work on version 18.04. I have the same random freeze/crash after using it.

---

> To clarify, after the freeze/crash, are there crash files in /var/crash?

No, there isn't any files in this location.

---

> Could you please advise when the freeze/crash happens?

It is random.

---

> To clarify, if you use the proprietary nvidia drivers, does the computer still freeze/crash?

In version 18.04 is not possible choose any drivers.

---

Updated all new logs and photo with prefix 18.04.

Christopher M. Penalver, please tell me if you need more information.

Thank you

[azanaz (azanaz)]

This bug has been affecting me since around 2012 or so, when I was using Arch linux (still installed btw). Same graphics chip as OP's. Upgraded ubuntu MATE to 18.04 a week ago, and today the freeze happened again. This time, I intentionally wanted to test if it was fixed, and found out that it still was not. It is random as OP said, but easily reproducible by launching any application involving accelerated 3D. So today I wanted to turn on the 3D spectrum in VLC, and the screen became garbage like on the pic below :

https://i.stack.imgur.com/FEaIj.jpg

And since it was VLC, I also heard the looping short bit of my music that was playing when my system froze.
So no screenshot possible, the only way out is the reset button.
I can confirm this never happened when I used the proprietary driver.

This is not a production machine, so I'm willing to test possible fixes if needed.
Will post my lspci output tomorrow, +whatever else is needed.

Thanks.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[azanaz (azanaz)]

Here is my lspci output, please tell me what else I can attach.

[Isaac Monteiro (nazinho)]

I can confirm I'm having the same problem. This problem arised to me since Debian Jessie. The workaround was to install Nvidia proprietary drivers, but support for nvidia-304xx was dropped on Xorg 1.20.
Adding "NvMSI=0 NvPCIE=0" to kernel boot line seems to make crashes less predictable.
The only workaround is to boot with "nouveau.noaccel=1" but this make any graphical application unusably slow.
Back to Windows.

[azanaz (azanaz)]

I'm not switching back to Windows, so any possible fix is welcome to test on my machine!
Any devs around?

[Elbarbudo (patricearnal)]

Same problem on LinuxMint TARA fresh install.

No Nvidia device in driver-manager

[Jacques Beckand (j-beckand)]

Same problem for me with Lubuntu 18.04 System freezes at random times. Screen is then completely filled with non-sens signs. Graphic card is NVIDIA GeForce 6150SE nForce 430. Driver is Nouveau.
Thanks beforehand for your help.

[Dg (silverpinball1)]

This has been happening to me for 3-4 years. I'm nearly ready to trash the AMD Athlon.... Please Please fix this...

[Tim Riker (timriker)]

This happens to me too. Note: when X is NOT running, the kernel still locks up. This appears to be a kernel driver issue and not an X issue.

[Diogo Gomes (diogogomes)]

I don't use any flavor of Ubuntu anymore and do not have this hardware to test.

Feel free to take over of this issue if is relevant to you.

Thank you

[Daniel van Vugt (vanvugt)]

OK "Won't Fix" because the original reporter can no longer contribute to the bug. If anyone else still experiences similar problems then please open new bugs.