| What | Removed | Added |
|---|---|---|
| Component | DRM/other | Driver/nouveau |
| Assignee | dri-devel@lists.freedesktop.org | nouveau@lists.freedesktop.org |
| Product | DRI | xorg |
| QA Contact | xorg-team@lists.x.org |
(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)?
| What | Removed | Added |
|---|---|---|
| Status | NEW | NEEDINFO |
| Assignee | nouveau@lists.freedesktop.org | stakanov@freenet.de |
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?
| Bug ID | 92962 |
|---|---|
| Summary | KDE hangs and system freezes while journalctl lists complains of kernel (nouveau). Nvidia graphics |
| Product | DRI |
| Version | unspecified |
| Hardware | x86-64 (AMD64) |
| OS | Linux (All) |
| Status | NEW |
| Severity | normal |
| Priority | medium |
| Component | DRM/other |
| Assignee | dri-devel@lists.freedesktop.org |
| Reporter | stakanov@freenet.de |
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.
Created attachment 119681 [details]
exerpt of systemdjournal complaining about nouveau
| What | Removed | Added |
|---|---|---|
| Component | DRM/other | Driver/nouveau |
| Assignee | dri-devel@lists.freedesktop.org | nouveau@lists.freedesktop.org |
| Product | DRI | xorg |
| QA Contact | xorg-team@lists.x.org |