similar to: [Bug 92962] KDE hangs and system freezes while journalctl lists complains of kernel (nouveau). Nvidia graphics

https://bugs.freedesktop.org/show_bug.cgi?id=92962 --- Comment #3 from stakanov at freenet.de --- 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

https://bugs.freedesktop.org/show_bug.cgi?id=92962 --- Comment #2 from Pierre Moreau <pierre.morrow at free.fr> --- (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

https://bugs.freedesktop.org/show_bug.cgi?id=92962 stakanov at freenet.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Assignee|nouveau at lists.freedesktop.o |stakanov at freenet.de |rg |

https://bugs.freedesktop.org/show_bug.cgi?id=92962 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|DRM/other |Driver/nouveau Assignee|dri-devel at lists.freedesktop |nouveau at lists.freedesktop.o

Hi I've got serious troubles - I posted a while back about experiencing ext3 errors using 2.4.18, at the time I put the problems down to harddisk failure, but these problems are occurring more and more - not all of our systems are having this problem but 3 systems have now shown this problem. The hardware is essentially the same, the only difference is disk manufacturers but we've now

I have a rsyslog-based log server and would like to know how I can configure journalctl to send its logs to said log server.

The following messages have started to appear in the system log after the most recent update of my Centos7 machine gnome-software-service.desktop[3389]: 20:54:22:0879 Gs no app for changed places-menu at gnome-shell-extensions.gcampax.github.com gnome-software-service.desktop[3389]: 20:54:22:0886 Gs no app for changed alternate-tab at gnome-shell-extensions.gcampax.github.com

Hello Pierre-Jacques, First note that you posted your message on the developer's mailing list. For such user questions, rather email: https://www.redhat.com/mailman/listinfo/libvirt-users According to https://linuxcontainers.org/lxc/manpages//man5/lxc.container.conf.5.html lxc.kmsg is only used to symlink /dev/kmsg to /dev/console. Thus setting this to 0 only results in the lack of that

https://bugs.freedesktop.org/show_bug.cgi?id=104156 Bug ID: 104156 Summary: NVIDIA Corporation G96 [GeForce 9500 GT] (rev a1) issue finding GPIO Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=87361 Bug ID: 87361 Summary: [NV4C] Kernel lock-up after booting to desktop in Fedora 20 & 21 (Nvidia Geforce 6100 IGP) Product: Mesa Version: 10.3 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: blocker

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I''m using the "delete_lines" definition from http://reductivelabs.com/trac/puppet/wiki/SimpleTextRecipes . However, when I use it to remove a line with the pattern "/proc/kmsg" I need to escape the slashes for sed/grep and so I end up with "\/proc\/kmsg", but then I get this notices in the log of

https://bugs.freedesktop.org/show_bug.cgi?id=88822 Pierre Moreau <pierre.morrow at free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #10 from Pierre Moreau

On Tue, Feb 04, Richard W.M. Jones wrote: > > It seems to me that output is only shown once cmd.sh has finished. I > > already split cmd.sh into smaller pieces to see overall progress. But > > output from a verbose, long running single command within cmd.sh is not > > shown. > > Verbose output is carried over a separate channel from qemu, so things > like kernel

Hi, I just noticed one of my XEN domU''s rebooting by itself. No one was logged in and it wasn''t under load, but just rebooted. It rebooted again about an hour or 2 later Is there any way to see why to see what caused this, either from domU, or dom0 ? /var/log/messages has no indicative reason, but here it is: Aug 1 18:47:06 venus shutdown[13758]: shutting down for system

https://bugs.freedesktop.org/show_bug.cgi?id=99335 Bug ID: 99335 Summary: nouveau graphics often freezes when using KDE Plasma 5 Product: Mesa Version: 12.0 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=76788 Priority: medium Bug ID: 76788 Assignee: nouveau at lists.freedesktop.org Summary: Linux version 3.13 freezes X under nouveau GT 220 card QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter:

Package: logcheck-database Severity: wishlist Tags: patch Hi, ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ kernel: imklog 3\.18\.6, log source = /proc/kmsg started\.$ ^\w{3} [ :[:digit:]]{11} [._[:alnum:]-]+ rsyslogd: \[origin software="rsyslogd" swVersion="3.18.6" x-pid="[[:digit:]]+" x-info="http://www.rsyslog.com"\] restart$ Hendrik -- Hendrik Jaeger

Hello , i want all my log messages from python to have in /var/log/python Now they are in /var/log/messages: Jun 9 12:10:51 sx1 kernel: klogd 1.4.1, log source = /proc/kmsg started. Jun 9 12:11:01 sx1 python: MM_MEMBERS [it] Nothing to do. Jun 9 12:11:02 sx1 python: MM_MEMBERS [research] Nothing to do. Jun 9 12:12:01 sx1 python: MM_MEMBERS [it] Nothing to do. Jun 9 12:12:01 sx1 python:

https://bugs.freedesktop.org/show_bug.cgi?id=112123 Bug ID: 112123 Summary: Laptop freezes after suspend [write fault] Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: critical Priority: not set Component: Driver/nouveau

Hi, I noticed that some, but not all, of my CentOS 7 machines have these kernel parameters for turning on systemd debug level logging added to the grub.cfg file. systemd.log_level=debug systemd.log_target=kmsg The parameters are *not* in the /etc/default/grub file, so if I rebuild grub.cfg with grub2-mkconfig, they disappear. I am a bit puzzled over how they got introduced. Has anyone else