system reboots after acpi error

[Paul]

system rebooting at least once per day after this error appears in syslog

kernel: [ 2.786805] ACPI Warning: 0x0000000000001828-0x000000000000182f SystemIO conflicts with Region \PMIO 1 (20131115/utaddress-251)
kernel: [ 2.786814] ACPI Warning: 0x0000000000001c30-0x0000000000001c3f SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
kernel: [ 2.786817] ACPI Warning: 0x0000000000001c30-0x0000000000001c3f SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)
kernel: [ 2.786820] ACPI Warning: 0x0000000000001c00-0x0000000000001c2f SystemIO conflicts with Region \GPRL 1 (20131115/utaddress-251)
kernel: [ 2.786822] ACPI Warning: 0x0000000000001c00-0x0000000000001c2f SystemIO conflicts with Region \GPR_ 2 (20131115/utaddress-251)

any suggestions gratefully received

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-79-generic 3.13.0-79.123
ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33
Uname: Linux 3.13.0-79-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.13.0-79-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CurrentDmesg:
 [ 11.857681] init: plexmediaserver main process (986) terminated with status 255
 [ 11.857693] init: plexmediaserver main process ended, respawning
 [ 15.156202] init: plymouth-upstart-bridge main process ended, respawning
Date: Thu Mar 10 00:03:10 2016
HibernationDevice: RESUME=/dev/mapper/ibiza--vg-swap_1
InstallationDate: Installed on 2014-07-26 (592 days ago)
InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3)
MachineType: Shuttle Inc. SZ87R
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-79-generic root=/dev/mapper/hostname--vg-root ro processor.nocst=1
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-79-generic N/A
 linux-backports-modules-3.13.0-79-generic N/A
 linux-firmware 1.127.20
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.01
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: FZ87
dmi.board.vendor: Shuttle Inc.
dmi.board.version: 1.0
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.:bvr2.01:bd02/21/2014:svnShuttleInc.:pnSZ87R:pvrV1.0:rvnShuttleInc.:rnFZ87:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: SZ87R
dmi.product.version: V1.0
dmi.sys.vendor: Shuttle Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Paul (pau3)]

Hi Christopher,

Thanks for the prompt feedback. I was able to upgrade the bios but the issue re-occurred 24 hours later.

As requested:

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2.05
01/04/2016

As far as I can tell there is no improvement, typically the problem happens at least once every 24 hours.

Kind regards,
Paul

[penalvch (penalvch)]

Paul, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[Paul (pau3)]

Thanks Christopher.
I'm going to test some new Crucial memory to rule that out - then will follow your suggestion r.e. upstream kernel.
Memtest doesn't reveal any errors but my Corsair isn't on the supported list so will test new Crucial memory for the next 48 hours to rule that out.
http://global.shuttle.com/news/productsSupportList?productId=1723

[Launchpad Janitor (janitor)]

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