Bug 69168 - [NVA8]Arbitrary crashes
Summary: [NVA8]Arbitrary crashes
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-10 08:12 UTC by Wompy Dompy
Modified: 2013-10-10 15:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg-log with log_buf_len=1M (60.17 KB, text/plain)
2013-09-10 08:12 UTC, Wompy Dompy
no flags Details
latest Xorg-log (44.37 KB, text/plain)
2013-09-10 18:31 UTC, Wompy Dompy
no flags Details

Description Wompy Dompy 2013-09-10 08:12:51 UTC
Created attachment 85540 [details]
dmesg-log with log_buf_len=1M

Hi,
using nouveau on arch linux my system crashes arbitrarily. I tried to force it with maximum load (running tons of videos in parallel) but it would crash with log on. Unplugging the external monitor was finally the trigger, even though I am not sure if that is my actual problem. The picture on my external monitor looks crappy (don't know how to describe, but some kind of "fuzzy", like Win 98) even though the right resolution 1920*1080 is used. 
uname -a
Linux wom 3.11.0-1-ARCH #1 SMP PREEMPT Tue Sep 3 08:58:01 CEST 2013 x86_64 GNU/Linux

lspci|grep NVIDIA
01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2)
01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1)

xf86-video-nouveau-1.0.9-1
mesa-9.2.0-1
libdrm-2.4.46-2

Attached the dmesg-log with log_buf_len=1M
Comment 1 Ilia Mirkin 2013-09-10 15:06:06 UTC
What you have in your logs is a warning (one that was supposed to be fixed in 3.11, odd, but it should be harmless). There's also an error in the fifo command pusher (claims to be an invalid command, but that command looks fine to me), but it happens much before the warning.

When you say "crashes", what do you mean? Just that X restarts? In that case, seeing a Xorg.0.log.old would be instructional.
Comment 2 Wompy Dompy 2013-09-10 18:31:18 UTC
Created attachment 85581 [details]
latest Xorg-log

Thanks for that quick response.

That one is from the latest crash today. I don't think X restarts though. What happens is that I can move my mice, but gnome is not reacting any more, but I can still switch to the tty-consoles. Sometimes the gdm-login appears on tty2 though. Since I heard about a lot of improvements in 3.11 I asked the guys in #archlinux and they told me I could try to go the "testing" repo, install the kernel and go back. That's what I did. When it crahes, is there a possiblity to "restore" the gnome session? I tried to work with gnome-shell --replace --display :0 but that didn't work.

Kind regards,
wompy
Comment 3 Ilia Mirkin 2013-10-09 08:30:52 UTC
The xorg log that you attached seems fine. That was produced after the hang? If so, it must be the compositor hanging. Try disabling the compositor.

As for your gnome-related question, I don't know -- I stay away from gnome-shell & co; however it's very unlikely that it'd be possible to restore a session after X exits, due to the way that the X protocol works. However if X stays alive, no reason (in theory) that you can't restart your WM. (In fact, most WMs support this explicitly.)
Comment 4 Wompy Dompy 2013-10-10 08:11:53 UTC
Sorry about the latest reply, but with linux 3.12 kernel it seems to run stable again. I've installed a late 3.11 kernel as well and that one seems to work too.

This bug can be closed. Thanks!


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.