ACPI error message flooding syslog

Bug #1738736 reported by Alex Garel
38
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This message :

Dec 18 09:20:13 tignasse kernel: [ 85.652805] ACPI Error: Needed type [Reference], found [Integer] ffff99eae08481f8 (20170531/exresop-103)
Dec 18 09:20:13 tignasse kernel: [ 85.652831] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [OpcodeName unavailable] (20170531/dswexec-461)
Dec 18 09:20:13 tignasse kernel: [ 85.652847] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE (20170531/psparse-550)

Is flooding my syslog at a pace of on message every 200 ms !

This is really annoying.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-19-generic 4.13.0-19.22
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alex 5166 F.... pulseaudio
 /dev/snd/controlC1: alex 5166 F.... pulseaudio
CurrentDesktop: GNOME
Date: Mon Dec 18 09:22:16 2017
HibernationDevice: RESUME=UUID=870c2fd1-8a8f-49bb-9bf4-dbefaa08e583
InstallationDate: Installed on 2015-11-10 (768 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: Intel Corporation Skylake Platform
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=6814e3c1-8cea-4ecc-964d-535fd18782e9 ro quiet splash crashkernel=384M-:128M vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-19-generic N/A
 linux-backports-modules-4.13.0-19-generic N/A
 linux-firmware 1.169.1
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-11-23 (24 days ago)
dmi.bios.date: 11/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: WhiteTip Mountain1 Fab2
dmi.board.vendor: Topstar
dmi.board.version: RVP7
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 9
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd11/06/2015:svnIntelCorporation:pnSkylakePlatform:pvr0.1:rvnTopstar:rnWhiteTipMountain1Fab2:rvrRVP7:cvnDefaultstring:ct9:cvrDefaultstring:
dmi.product.family: Skylake System
dmi.product.name: Skylake Platform
dmi.product.version: 0.1
dmi.sys.vendor: Intel Corporation

Revision history for this message
Alex Garel (alex-garel) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Alex Garel (alex-garel) wrote :

Side note :

echo "disable" >> /sys/firmware/acpi/interrupts/gpe50

as root, permits to end syslog flooding.

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.15 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.15-rc4

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Alex Garel (alex-garel) wrote :

FYI, still got it with "4.13.0-21-generic".

Sorry, but I still won't be able to test on the upstream kernel this week…

Revision history for this message
Alex Garel (alex-garel) wrote :

Ok I finally got the time to test it on upstream kernel.

$ uname -a
Linux tignasse 4.15.0-041500rc9-generic #201801212130 SMP Mon Jan 22 02:31:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

# lsb_release -a
LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description: Ubuntu 17.10
Release: 17.10
Codename: artful

The bug is still there, flooding my syslog very fast

$ tail -f /var/log/syslog
Jan 28 21:15:00 tignasse kernel: [ 115.269198] ACPI Error: Needed type [Reference], found [Integer] 00000000a4664840 (20170831/exresop-103)
Jan 28 21:15:00 tignasse kernel: [ 115.269227] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20170831/dswexec-461)
Jan 28 21:15:00 tignasse kernel: [ 115.269254] No Local Variables are initialized for Method [_Q50]
Jan 28 21:15:00 tignasse kernel: [ 115.269260] No Arguments are initialized for method [_Q50]
Jan 28 21:15:00 tignasse kernel: [ 115.269269] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE (20170831/psparse-550)

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Peter Curtis (pdcurtis) wrote :

I have the same flooding of /var/log/syslog about every 200 msecs with:

Oct 27 21:17:01 helios kernel: [11807.295919] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE (20170831/psparse-550)
Oct 27 21:17:02 helios kernel: [11807.497617] ACPI Error: Needed type [Reference], found [Integer] 00000000dfb12c24 (20170831/exresop-103)
Oct 27 21:17:02 helios kernel: [11807.497647] ACPI Exception: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20170831/dswexec-461)
Oct 27 21:17:02 helios kernel: [11807.497677] No Local Variables are initialized for Method [_Q50]
Oct 27 21:17:02 helios kernel: [11807.497683] No Arguments are initialized for method [_Q50]

 ~ $ inxi -Fx
System: Host: helios Kernel: 4.15.0-38-generic x86_64 bits: 64 gcc: 7.3.0
           Desktop: Cinnamon 3.8.9 (Gtk 3.22.30-1ubuntu1)
           Distro: Linux Mint 19 Tara
Machine: Device: laptop System: Intel product: Skylake Platform v: 0.1 serial: N/A
           Mobo: Topstar model: WhiteTip Mountain1 Fab2 v: RVP7 serial: N/A
           UEFI: American Megatrends v: 5.11 date: 09/10/2015
Battery BAT0: charge: 42.0 Wh 98.6% condition: 42.6/46.6 Wh (91%)
           model: TPS S10 status: N/A
CPU: Dual core Intel Core i5-6200U (-MT-MCP-)
           arch: Skylake rev.3 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 9600
           clock speeds: max: 2800 MHz 1: 500 MHz 2: 500 MHz 3: 500 MHz
           4: 500 MHz
Graphics: Card: Intel HD Graphics 520 bus-ID: 00:02.0
           Display Server: x11 (X.Org 1.19.6 )
           drivers: modesetting (unloaded: fbdev,vesa)
           Resolution: 1920x1080@60.00hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
           version: 4.5 Mesa 18.0.5 Direct Render: Yes
Audio: Card Intel Sunrise Point-LP HD Audio
           driver: snd_hda_intel bus-ID: 00:1f.3
           Sound: Advanced Linux Sound Architecture v: k4.15.0-38-generic
Network: Card: Intel Wireless 3160 driver: iwlwifi bus-ID: 01:00.0
           IF: wlp1s0 state: up mac: b4:6d:83:95:8c:b0
Drives: HDD Total Size: 250.1GB (57.3% used)
           ID-1: /dev/sda model: Samsung_SSD_850 size: 250.1GB
Partition: ID-1: / size: 31G used: 24G (81%) fs: ext4 dev: /dev/sda2
           ID-2: /home size: 62G used: 17G (29%) fs: ext4 dev: /dev/sda3
           ID-3: swap-1 size: 10.49GB used: 0.00GB (0%)
           fs: swap dev: /dev/dm-0
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 34.0C mobo: N/A
           Fan Speeds (in rpm): cpu: N/A
Info: Processes: 223 Uptime: 7:10 Memory: 1671.1/7886.5MB
           Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56

Revision history for this message
aidans (aidans) wrote :

I also have this issue with Cosmic (4.18.0-13) and also with the latest upstream kernel:

$ uname -a
Linux alaptop 5.0.0-050000rc1-generic #201901062130 SMP Mon Jan 7 02:32:47 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.10
Release: 18.10
Codename: cosmic

$ tail /var/log/syslog
Jan 11 09:26:07 alaptop kernel: [ 44.303945] ACPI Error: Needed type [Reference], found [Integer] 0000000006c06c7b (20181213/exresop-69)
Jan 11 09:26:07 alaptop kernel: [ 44.303975] ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20181213/dswexec-427)
Jan 11 09:26:07 alaptop kernel: [ 44.304003] No Local Variables are initialized for Method [_Q50]
Jan 11 09:26:07 alaptop kernel: [ 44.304009] No Arguments are initialized for method [_Q50]
Jan 11 09:26:07 alaptop kernel: [ 44.304020] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.H_EC._Q50, AE_AML_OPERAND_TYPE (20181213/psparse-531)

Revision history for this message
Alex Garel (alex-garel) wrote :

I can confirm on my side that it's still there after I also upgrade to Cosmic.

Revision history for this message
crt (crt-mori) wrote :

It appeared for me after upgrade to Cosmic (did not have it before). And on both desktop PC and laptop.

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
Peter Curtis (pdcurtis) wrote :

Has there been any progress on this.

I still have the same problem on both kernel 4.15 and 5.4.

I still have to modify logrotate to limit logging or more recently I have tried stopping the logging of any errors which was not as simple as I expected as rsyslog uses socket activation under systemd. So whenever there is a log message coming in, rsyslog will be started on demand. The unit is named syslog.socket. So to stop the rsyslog service one needs to stop both units:

systemctl stop syslog.socket rsyslog.service

or completely to disable logging from the next boot by:

systemctl disable syslog.socket rsyslog.service

None of these are satisfactory long term solutions

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.