| Summary: | KDE hangs and system freezes while journalctl lists complains of kernel (nouveau). Nvidia graphics | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | stakanov | ||||||||
| Component: | Driver/nouveau | Assignee: | stakanov | ||||||||
| Status: | RESOLVED MOVED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | medium | CC: | tiwai | ||||||||
| Version: | unspecified | ||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||
| OS: | Linux (All) | ||||||||||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=92892 | ||||||||||
| Whiteboard: | |||||||||||
| i915 platform: | i915 features: | ||||||||||
| Attachments: |
|
||||||||||
|
Description
stakanov
2015-11-15 12:12:34 UTC
Created attachment 119681 [details]
exerpt of systemdjournal complaining about nouveau
(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. 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. (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)? 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?
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 -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/issues/236. |
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.