mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: Multiple problems with the Linux kernel on an AMD desktop
Date: Fri, 25 Nov 2016 15:01:29 -0200	[thread overview]
Message-ID: <20161125170129.fq52k7nfukxd5efl@ime.usp.br> (raw)
In-Reply-To: <80eb4533-2233-6b75-eae9-99f6decebd88@ladisch.de>

Hi, Clemens and others.

On Nov 25 2016, Clemens Ladisch wrote:
> Rogério Brito wrote:
> >     [  130.007219] evbug: Event. Dev: input6, Type: 0, Code: 0, Value: 0
> 
> The evbug module is intended for debugging; it dumps all input events
> into syslog.  If you do not want these messages, do not load this module.
> (If it is loaded automatically, you have an actual bug.)

It *was* loaded automatically, and I didn't specifically asked it to be
loaded, but I'm not sure if other parts of userspace forced it to be
loaded. I will disable it, then.

Here is the relevant part of the config file:

,----[ grep -i evbug /boot/config-4.9.0-040900rc6-generic ]
| CONFIG_INPUT_EVBUG=m
`----


Thanks,

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFCAAAA
http://rb.doesntexist.org/blog : Projects : https://github.com/rbrito/
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

  reply	other threads:[~2016-11-25 17:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24 23:39 Rogério Brito
2016-11-25  7:01 ` Borislav Petkov
2016-11-25 16:05   ` Rogério Brito
2016-11-25 16:15     ` Clemens Ladisch
2016-11-25 17:01       ` Rogério Brito [this message]
2016-11-25 16:37     ` Borislav Petkov
2016-11-25  8:47 ` Clemens Ladisch
2016-11-25 16:53   ` Rogério Brito
2016-11-25 17:01     ` Borislav Petkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161125170129.fq52k7nfukxd5efl@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®