$ journalctl | grep evbug | wc -l
818321
$ uname -a
Linux gflap 5.13.0-52-generic #59~20.04.1-Ubuntu SMP Thu Jun 16 21:21:28 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
---
$ journalctl | grep evbug | sed -re 's/^.*(kernel.* )Code.*/\1/' | sort -u
kernel: evbug: Event. Dev: input13, Type: 0,
@ Muelli (ubuntu-bugs-auftrags-killer)
The correct way to restore the /etc/foo/bar* files is
sudo dpkg -i --force-confnew /var/cache/apt/archives/packagename.deb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
just got spammed with messages from evbug.c
fresh install of maverick amd64
there was no /etc/modprobe.d/blacklist.conf file present, and neither was evbug
blacklisted in the other files.
$ uname -a
Linux mango 2.6.35-28-generic #49-Ubuntu SMP Tue Mar 1 14:39:03 UTC 2011 x86_64
GNU/Linux
--
Hi,
I have this problem in maverick, here is the head of my blacklist.conf.
___
# This file lists those modules which we don't want to be loaded by
# alias expansion, usually so some other driver will be loaded for the
# device instead.
# evbug is a debug tool that should be
Okay, I was hit by this bug, too. While I see that the evdebug module
perfectly does what it's meant to do, I don't really see why this module
is being loaded automatically.
Anyway, I accidentally my /etc/modprobe.d/blacklist{,.conf} and now I
want to restore it. Unfortunately, neither apt-get
On Wed, 2009-09-09 at 21:10 +, Shang Wu wrote:
I am on Karmic, and I am start having this issue now...
The module-init-tools is on version 3.10-2.
Tried rmmod evbug, but when I plugged in my USB mouse, the issue start
happening again.
I am on 2.6.31-9-generic-pae #29-Ubuntu SMP Sun
I am on Karmic, and I am start having this issue now...
The module-init-tools is on version 3.10-2.
Tried rmmod evbug, but when I plugged in my USB mouse, the issue start
happening again.
I am on 2.6.31-9-generic-pae #29-Ubuntu SMP Sun Aug 30 18:36:39 UTC 2009
i686 GNU/Linux
--
evbug.c spams
This module has been blacklisted since almost the dawn of time.
If you are missing a blacklist line for it, it is because you have
modified your /etc/modprobe.d/blacklist.conf file
At least two reporters have obvious blacklist.conf~ files alongside it,
so no denying it please ;-)
** Changed in:
This bug is fixed in newer packages 'module-init-tools_3.10-2_amd64.deb'
and 'module-init-tools_3.10-2_i386.deb'.
Recommending version upgrade on Jaunty from 3.7~9-2 to 3.10-2.
** Package changed: linux (Ubuntu) = module-init-tools (Ubuntu)
** Changed in: module-init-tools (Ubuntu)
This is _not_ a bug, technically speaking but a configuration issue.
When the kernel module evbug is installed this is what it should do.
That said, evbug is not a module that should be automatically loaded by
a desktop linux system due to issues such as this. Developers can load
this module
Joel -
I don't have a copy of Karmic handy, nor do I have the time to test it,
but IIRC, the location that it looks for the blacklisted module is
/etc/modprobe.d/modprobe.conf. If you cat that, and then pipe it
through a grep evbug, then we've got a regression on our hands, or a
major problem.
This is occuring again in:
Description:Ubuntu karmic (development branch)
Release:9.10
Linux chickenhawk 2.6.31-4-generic #22-Ubuntu SMP Fri Jul 24 18:06:15
UTC 2009 i686 GNU/Linux
looks like a regression...
as per previously dmesg fills up with:
[80457.612191] evbug.c: Event.
obviously:
rmmod evbug
makes this stop.
the following also shows this module not being blacklisted if in fact it
should be:
r...@chickenhawk:/etc/modprobe.d# ls
alsa-base.conf blacklist-firewire.conf blacklist-watchdog.conf
blacklist-ath_pci.conf blacklist-framebuffer.conf
This is not only a nuisance; it's a real security hazard, as well! If you
think about it, having the kernel report every keycode in dmesg... is like
having a world-readable keylogger installed.
In my case (on karmic), evbug was loading even when blacklisted; to actually
disable it, I had to
I'd bet this bug affects LiveCD installs only. I installed from a 9.04
alpha6 LiveCD and suffered from random crashes caused by buffers
overflows that could only be attributed to this spamming. After reading
this bug I decided to reinstall module-init-tools and lo-and-behold!
dpkg asks me to
If the bug still persists, I haven't managed to notice anything with it
in the nearly year time since I've reported it. After blacklisting it
and removing it, the annoying spam messages have never popped up again.
No other module is loading evbug in, not to my knowledge on the machine
in
It's curious that the evbug module is getting loaded, because by default
/etc/modprobe.d/blacklist contains an entry to prevent evbug from
getting loaded. Can you confirm that it's blacklisted somewhere under
/etc/modprobe.d/ on your system? Can you report the results of lsmod
when it gets loaded,
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
Status: New = Triaged
--
evbug.c spams logs and causes high system loads
https://bugs.launchpad.net/bugs/240553
You received this bug notification because
For me, kernel 2.6.27 has the same bug.
uname -a: Linux macbook 2.6.27-7-generic #1 SMP Thu Oct 30 04:12:22 UTC
2008 x86_64 GNU/Linux
** Attachment added: dmesg.log
http://launchpadlibrarian.net/19137406/dmesg.log
--
evbug.c spams logs and causes high system loads
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/19137420/lspci-vvnn.log
** Tags added: linux-2.6.27
--
evbug.c spams logs and causes high system loads
https://bugs.launchpad.net/bugs/240553
You received this bug notification because you are a member of Ubuntu
Bugs, which
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
Here's the bash script that I wrote. It does the job pretty nicely (had
the chance to test it recently). Unfortunately, I haven't had the
chance to use it as an actual *cron*, but it will accomplish the same
thing when run as root.
** Attachment added: evbug_cron.sh
Result of uname -a: Linux LATLON-Callisto 2.6.24-19-generic #1 SMP Wed
Jun 4 16:35:01 UTC 2008 i686 GNU/Linux
** Attachment added: dmesg.log
http://launchpadlibrarian.net/15389624/dmesg.log
--
evbug.c spams logs and causes high system loads
https://bugs.launchpad.net/bugs/240553
You
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/15389633/lspci-vvnn.log
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
evbug.c spams logs and causes high system loads
https://bugs.launchpad.net/bugs/240553
You received this bug notification because you
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I am changing the package to 'Linux' because evbug
appears to be part of the kernel. Please include the following
additional information, if you have not already done so, as required by
the Ubuntu Kernel Team:
1.
25 matches
Mail list logo
