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

Bug #1643719 reported by aaronfranke
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

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
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC0D0p: aaronfranke 2674 F...m pulseaudio
 /dev/snd/controlC0: aaronfranke 2674 F.... pulseaudio
 /dev/snd/controlC2: aaronfranke 2674 F.... pulseaudio
 /dev/snd/controlC1: aaronfranke 2674 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=1fcb1225-87da-4148-9227-bedf5fe47d08
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04b4:1007 Cypress Semiconductor Corp.
 Bus 001 Device 003: ID 045e:076c Microsoft Corp. Comfort Mouse 4500
 Bus 001 Device 002: ID 046d:09a1 Logitech, Inc. QuickCam Communicate MP/S5500
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=b5b971ee-cfa4-435f-9699-2543a4f50bd3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-47-generic N/A
 linux-backports-modules-4.4.0-47-generic N/A
 linux-firmware 1.157.5
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: xenial
Uname: Linux 4.4.0-47-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/13/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.40
dmi.board.name: Z170M Pro4S
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd08/13/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ170MPro4S:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1643719

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9-rc6

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: kernel-da-key
Revision history for this message
aaronfranke (arnfranke) wrote :

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.

Revision history for this message
aaronfranke (arnfranke) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected xenial
description: updated
Revision history for this message
aaronfranke (arnfranke) wrote : CRDA.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : CurrentDmesg.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : IwConfig.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : JournalErrors.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : Lspci.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : ProcEnviron.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : ProcInterrupts.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : ProcModules.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : PulseList.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : UdevDb.txt

apport information

Revision history for this message
aaronfranke (arnfranke) wrote : WifiSyslog.txt

apport information

aaronfranke (arnfranke)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
tags: added: bios-outdated-7.00 needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
aaronfranke (arnfranke) wrote :

I noticed that the bug has been already set to expired and I would like to post that this bug has been confirmed and seems to be fixed in upstream, though it will take time for the fix to be pushed downstream. I will re-test for this bug in a few years or so, but I'll mark as solved for now.

Changed in linux (Ubuntu):
status: Expired → Fix Committed
Revision history for this message
aaronfranke (arnfranke) wrote :
Revision history for this message
penalvch (penalvch) wrote :

aaronfranke, to advise, this isn't Fix Committed as defined in:
https://wiki.ubuntu.com/Bugs/Status

Despite this, have you personally tested the patch on your hardware?

If not, one may follow https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream to test it.

Once the patch has been tested, please advise to the results and mark this Status Confirmed.

Changed in linux (Ubuntu):
status: Fix Committed → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.