Hello Joseph,

This issue seems to happen randomly. Between the time I posted this bug
and now, I decided to mount /var/log on a separate partition, to allow
me to use my system the next time this error occurs and to be able to
better report bugs. I have not yet experienced the bug but it will
probably happen again randomly.

I will try upgrading my kernel to the upstream version you linked, and
I'll let you guys know the next time this happens.

However, before I do that, I want to ask, on that page it says "First,
if one is using select proprietary or out-of-tree modules (ex.
vitualbox, nvidia, fglrx, bcmwl, etc.)...", does this mean I would have
to use the nouveau drivers instead of Nvidia's proprietary drivers if I
wanted to test this against the upstream kernel? As a gamer, I wouldn't
be willing to do that until it happens again, the nouveau drivers are
not very good. Also, I have several other proprietary applications on my
system, such as Dropbox, and TeamViewer, and Google Chrome.

Note, also, that I'm not really asking for the fix to be preventing this
error, because I'm sure that there is some other problem with my system
causing such an error, but I'm instead asking for a "speed limit" for
these error messages, to prevent systems from becoming unusable due to
gigantic log files, which would be bad should anyone else have this same
issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1643719

Title:
  ACPI AE_NOT_FOUND errors aggressively being spawned, filling up log
  files.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  OS: Xubuntu 16.04.1 LTS - Ubuntu 4.4.0-47.68-generic 4.4.24

  Motherboard: ASRock Z170M Pro4S

  GPU: Asus Nvidia GTX 770 with 367.57 drivers

  Storage: Corsair 256 GB SSD, Toshiba 3 TB HDD, Hitachi 2 TB HDD

  
  Here's a small sample of the errors: http://pastebin.com/b2Jv8z37

  While these errors definitely have a purpose, these error messages are
  created far too quickly, and this causes severe problems on my system
  at least, the logs become bloated with these messages, completely
  filling my root partition, preventing me from using my system.  I
  believe that anyone else who is able to trigger these messages at such
  a high rate will have the same problem.

  Based on the amount of messages and the time given for each, it
  appears that this error message appears approximately 1000 times per
  second (on my system), creating 3000 lines per second or ~400000 bytes
  per second (on my system). This fills up about 1.4 GB per hour (on my
  system) which fills up my root partition in less than a day. Once my
  root partition is filled, my system becomes unusable.

  My preferred solution to this issue is to limit the rate at which
  these messages appear. A limit of one error message per second seems
  like a good idea.

  Also, I tried reporting this to the Linux kernel devs, I'm not exactly
  sure if either of these places is the right place but hopefully
  somebody will be able to fix this issue. Here is the link to the other
  bug report https://bugzilla.kernel.org/show_bug.cgi?id=188331

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643719/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to