[regression]ACPI tables parsing issue (WARNING in dmesg, no /proc/acpi, no display DPMS, no ATX power off)

[MMlosh]

Occurs on:
13.10 Saucy (linux 3.11)
14.04-dev (linux 3.13)

Does not occur on:
all previous releases since 2008 or so

The machine has 2 PentiumIII processors
It's BIOS dates back to 1999, but till now it worked well with acpi=force

There is a warning in DMESG that seems ACPI-related
WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/arch/x86/mm/ioremap.c:536 __early_ioremap+0x13c/0x1ce()
-- snip --
 [ 0.000000] [<c19b37d4>] early_ioremap+0x1a/0x1c
 [ 0.000000] [<c19ab389>] __acpi_map_table+0x14/0x19
-- snip --

[MMlosh (mmlosh)]

uname -a: 3.13.0-2-generic #17-Ubuntu SMP Fri Jan 10 12:14:58 UTC 2014 i686 i686 i686 GNU/Linux

[MMlosh (mmlosh)]

I never got suspend/resume running on that machine

/proc/acpi directory is not present

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

MMlosh, thank you for reporting this and helping make Ubuntu better. Could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux REPLACE-WITH-BUG-NUMBER

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[MMlosh (mmlosh)]

@ Upstream testing - OK, I'll do that

@ Rest of the required steps - what? The system is already running Trusty Tahr -dev

[MMlosh (mmlosh)]

It's pretty much the same on mainline 3.13-rc2 (That is the closest kernel to one I'm running in Trusty right now I guess)

[MMlosh (mmlosh)]

Same on -rc8, the issue exists there too.
The raw hex values taken from (presumed) ACPI tables have changed quite considerably, though.

[MMlosh (mmlosh)]

Did I miss any piece of missing information?

[penalvch (penalvch)]

MMlosh, this report is still missing the apport-collect requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1268340/comments/7 and the latest mainline kernel (3.13 not 3.13-rc8).

[MMlosh (mmlosh)]

It's not really my fault that a new kernel was published since my last post... but OK, I can test again.

[MMlosh (mmlosh)]

The WARNING is still there, the symptoms are still there.

@ apport-collect
Is there a way how that can be done WHILE keeping my launchpad login away from the machine?
(Hey, I downloaded a kernel over plain HTTP and ran it few hours after you asked me to. No way I'll give it my login details)

[penalvch (penalvch)]

MMlosh, one would not want to execute the requested apport-collect using the mainline kernel, but the one supplied by a supported Ubuntu repository.

[MMlosh (mmlosh)]

so?
It'll still be a machine I downloaded a kernel via plain HTTP on and ran it.
A reboot won't make it any more trustworthy, why should it?

[Launchpad Janitor (janitor)]

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