Bug 92962 - KDE hangs and system freezes while journalctl lists complains of kernel (nouveau). Nvidia graphics
Summary: KDE hangs and system freezes while journalctl lists complains of kernel (nouv...
Status: NEEDINFO
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: stakanov
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-15 12:12 UTC by stakanov
Modified: 2016-02-03 03:30 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
output dmesg with system freezes complaining about nouveau (14.63 KB, text/plain)
2015-11-15 12:12 UTC, stakanov
no flags Details
exerpt of systemdjournal complaining about nouveau (29.06 KB, text/plain)
2015-11-15 12:14 UTC, stakanov
no flags Details
journalctl with -k-b-1 (112.31 KB, text/plain)
2015-11-16 09:39 UTC, stakanov
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description stakanov 2015-11-15 12:12:34 UTC
Created attachment 119680 [details]
output dmesg with system freezes complaining about nouveau

This bug has originally reported to the bugzilla of opensuse and I was asked to report it here. 
Ref: https://bugzilla.opensuse.org/show_bug.cgi?id=954746

In this installation of Tumbleweed running Kernel 4.3:
4.3.0-1-default #1 SMP PREEMPT Mon Nov 2 15:35:09 UTC 2015 (7b374a4) x86_64 x86_64 x86_64 GNU/Linux
I get system freezes (generally necessitating hard reset) and impossibility to run more than one user session at a time. 
The attachments of journal and dmesg show the error message received. 
I allow myself to cc the developer of opensuse Takashi Iwai tiwai@suse.com. 

This system worked well with 3.x kernels and up to 4.2 
With the current kernel I get the lockups. 
Board is an old Ashrock 939DualVsta and Graphics is Nvidia GT216 based on primary PCI-e slot of the mainboard.
Comment 1 stakanov 2015-11-15 12:14:02 UTC
Created attachment 119681 [details]
exerpt of systemdjournal  complaining about nouveau
Comment 2 Pierre Moreau 2015-11-15 12:26:53 UTC
(Moved to the correct product and component)

Could you please get a full dmesg output (by using netconsole if you have a second computer, or by blacklisting Nouveau, cating dmesg or /dev/kmsg to a file and then loading Nouveau manually)? Maybe your attachments are enough for Ben to figure out what is going wrong, but some more information shouldn't hurt.
Comment 3 stakanov 2015-11-15 12:41:40 UTC
A bit embarrassing but I do not really know what to ask there. 

I think I know how to blacklist nouveau:

# echo "blacklist nouveau" >> /etc/modprobe.d/50-blacklist.conf && mkinitrd && reboot
 
Then, if I do understand rightly: 

cat /dev/kmsg > kmsgresult.txt 

Then 

modprobe nouveau 

(from the  CLI) and then again?

cat /dev/kmsg > kmsgresult2.txt 


Is this what you need? Unfortunately my skills are quite limited, so I prefer to ask.
Comment 4 Pierre Moreau 2015-11-15 12:56:25 UTC
(In reply to stakanov from comment #3)
> A bit embarrassing but I do not really know what to ask there. 
> 
> I think I know how to blacklist nouveau:
> 
> # echo "blacklist nouveau" >> /etc/modprobe.d/50-blacklist.conf && mkinitrd
> && reboot

That should do it.

(In reply to stakanov from comment #3)
> Then, if I do understand rightly: 
> 
> cat /dev/kmsg > kmsgresult.txt 
> 
> Then 
> 
> modprobe nouveau 
> 
> (from the  CLI) and then again?
> 
> cat /dev/kmsg > kmsgresult2.txt 

    cat /dev/kmsg > kmsgresult.txt&
    modprobe nouveau
    startx

would be one way to go, as `cat` will continue its job until it get killed. And then when you reboot, you can access the file (which hopefully didn't end up corrupted). Maybe `journalctl -k -b -1` will contain all the information as well (given that the previous boot, was one that froze)?
Comment 5 stakanov 2015-11-16 09:39:36 UTC
Created attachment 119699 [details]
journalctl with -k-b-1

Some more info. 
For what is the output of cat:
I do yet not understand when to blacklist nouveau.
should I just blacklist it, then start it by hand with modprobe nouveau?
Once the system freezed I cannot input anything anymore. 
So I guess I have to blacklist before and start manually? Then provoke the freeze?
Comment 6 doktor.yak 2015-12-03 20:45:13 UTC
This bug really looks like 
https://bugs.freedesktop.org/show_bug.cgi?id=92892
and seems to be linked to a modification in the nouveau driver between kernel version 4.2.4 and 4.3.0


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.