unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: 24087@debbugs.gnu.org
Subject: bug#24087: recovery from suspend is broken with recent libreboot +	linux-libre 4.7
Date: Fri, 29 Jul 2016 10:51:14 +0000	[thread overview]
Message-ID: <87oa5gvhst.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87k2g5da0b.fsf@we.make.ritual.n0.is>

This is the boot up messages of one of the affected (running GuixSD)
devices. As I was assured this is a GuixSD specific problem, parabola,
trisquel and others do behave as expected (recover from
suspend/hibernate works).


Jul 28 15:32:29 localhost vmunix: [    0.000000] KERNEL supported cpus:
Jul 28 15:32:29 localhost vmunix: [    0.000000]   Intel GenuineIntel
Jul 28 15:32:29 localhost vmunix: [    0.000000]   AMD AuthenticAMD
Jul 28 15:32:29 localhost vmunix: [    0.000000]   Centaur CentaurHauls

I am used to individual configured kernels, so this might be just my
impression. Should this not be more specific, include core2 etc, or is
this just a listing of vendors there and not the cpu selection I
remember from the makemenuconfig dialog?

Then further on there's a call trace, this will be pasted here and leave
out some lines because I don't like to be that transparent in clear
public communication about my hardware.  Then again I don't know how
much this will tell, so if anyone says it's easier to debug with the
full information provided, I could do so.  This trace happens every time
I boot:

Jul 28 15:32:36 localhost vmunix: [    0.000000] ------------[ cut here ]------------
Jul 28 15:32:36 localhost vmunix: [    0.000000] WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:830 warn_invalid_dmar.part.7+0x78/0x90
Jul 28 15:32:36 localhost vmunix: [    0.000000] Your BIOS is broken; DMAR reported at address fed92000 returns all ones!
-- snip for bios vendor etc etc --
Jul 28 15:32:37 localhost vmunix: [    0.000000] Modules linked in:
Jul 28 15:32:37 localhost vmunix: [    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.7.0-gnu #1
-- snip for hardware name etc --
Jul 28 15:32:37 localhost vmunix: [    0.000000] Call Trace:
Jul 28 15:32:37 localhost vmunix: [    0.000000]  [<ffffffff813dce53>] dump_stack+0x63/0x90
Jul 28 15:32:37 localhost vmunix: [    0.000000]  [<ffffffff81080ef1>] __warn+0xd1/0xf0
Jul 28 15:32:38 localhost vmunix: [    0.000000]  [<ffffffff81080fe7>] warn_slowpath_fmt_taint+0x57/0x70
Jul 28 15:32:38 localhost vmunix: [    0.000000]  [<ffffffff81fa81fc>] ? __early_ioremap+0x14b/0x1d2
Jul 28 15:32:38 localhost vmunix: [    0.000000]  [<ffffffff815271b8>] warn_invalid_dmar.part.7+0x78/0x90
Jul 28 15:32:38 localhost vmunix: [    0.000000]  [<ffffffff8181e524>] dmar_validate_one_drhd+0x84/0xe0
Jul 28 15:32:38 localhost vmunix: [    0.000000]  [<ffffffff81526b53>] dmar_walk_remapping_entries+0x83/0x1a0
Jul 28 15:32:38 localhost vmunix: [    0.000000]  [<ffffffff81fc612c>] detect_intel_iommu+0x5f/0xf2
Jul 28 15:32:38 localhost vmunix: [    0.000000]  [<ffffffff8181e4a0>] ? xen_swiotlb_init+0x4b0/0x4b0
Jul 28 15:32:39 localhost vmunix: [    0.000000]  [<ffffffff81f8124e>] pci_iommu_alloc+0x4a/0x6c
Jul 28 15:32:39 localhost vmunix: [    0.000000]  [<ffffffff81f907a3>] mem_init+0x11/0xa3
Jul 28 15:32:39 localhost vmunix: [    0.000000]  [<ffffffff81f71dc9>] start_kernel+0x230/0x489
Jul 28 15:32:39 localhost vmunix: [    0.000000]  [<ffffffff81f71120>] ? early_idt_handler_array+0x120/0x120
Jul 28 15:32:39 localhost vmunix: [    0.000000]  [<ffffffff81f71481>] x86_64_start_reservations+0x2f/0x31
Jul 28 15:32:39 localhost vmunix: [    0.000000]  [<ffffffff81f715cd>] x86_64_start_kernel+0x14a/0x16d
Jul 28 15:32:39 localhost vmunix: [    0.000000] ---[ end trace e301e3fe181525a1 ]---


Moving on:

Jul 28 15:32:43 localhost vmunix: [    0.040144] DMAR: Host address width 36
Jul 28 15:32:44 localhost vmunix: [    0.040150] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
Jul 28 15:32:44 localhost vmunix: [    0.040166] DMAR: dmar0: reg_base_addr fed90000 ver 1:0 cap c9008020e30260 ecap 1000
Jul 28 15:32:44 localhost vmunix: [    0.040175] DMAR: DRHD base: 0x000000fed91000 flags: 0x0
Jul 28 15:32:44 localhost vmunix: [    0.040184] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap c0000020630260 ecap 1000
Jul 28 15:32:44 localhost vmunix: [    0.040193] DMAR: DRHD base: 0x000000fed92000 flags: 0x0
Jul 28 15:32:44 localhost vmunix: [    0.040207] DMAR: Failed to map dmar2
Jul 28 15:32:44 localhost vmunix: [    0.040212] DMAR: Parse DMAR table failure.

Then there are some lines about some devices and  "System wakeup disabled by ACPI"

...

Jul 28 15:33:01 localhost vmunix: [    0.482055] ACPI Exception: AE_NOT_FOUND, Error reading AC Adapter state (20160422/ac-128)
Jul 28 15:33:01 localhost vmunix: [    0.482218] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2a/PNP0C09:00/PNP0C0E:00/input/input0
Jul 28 15:33:01 localhost vmunix: [    0.482290] ACPI: Sleep Button [SLPB]
Jul 28 15:33:01 localhost vmunix: [    0.482388] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:2a/PNP0C09:00/PNP0C0D:00/input/input1
Jul 28 15:33:01 localhost vmunix: [    0.482578] ACPI: Lid Switch [LID] Jul 28 15:33:01 localhost vmunix: [    0.482680] input: Power Button as
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
Jul 28 15:33:02 localhost vmunix: [    0.482732] ACPI: Power Button [PWRF]
Jul 28 15:33:02 localhost vmunix: [    0.484295] tsc: Marking TSC unstable due to TSC halts in idle
Jul 28 15:33:02 localhost vmunix: [    0.486639] thermal LNXTHERM:00: registered as thermal_zone0
Jul 28 15:33:02 localhost vmunix: [    0.486685] ACPI: Thermal Zone [THM0] (32 C)
Jul 28 15:33:02 localhost vmunix: [    0.488684] thermal LNXTHERM:01: registered as thermal_zone1
Jul 28 15:33:02 localhost vmunix: [    0.489901] ACPI: Thermal Zone [THM1] (29 C)
Jul 28 15:33:02 localhost vmunix: [    0.491148] GHES: HEST is not enabled!

...


Jul 28 15:33:16 localhost vmunix: [    7.389127] acpi device:04: registered as cooling_device2
Jul 28 15:33:16 localhost vmunix: [    7.389897] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5
Jul 28 15:33:16 localhost vmunix: [    7.546204] ACPI Warning: SystemIO range 0x0000000000000528-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\PMIO) (20160422/utaddress-255)
Jul 28 15:33:17 localhost vmunix: [    7.547836] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 15:33:17 localhost vmunix: [    7.548752] ACPI Warning: SystemIO range 0x00000000000005B0-0x00000000000005BF conflicts with OpRegion 0x0000000000000580-0x00000000000005BE (\GPCM) (20160422/utaddress-255)
Jul 28 15:33:17 localhost vmunix: [    7.550626] ACPI Warning: SystemIO range 0x00000000000005B0-0x00000000000005BF conflicts with OpRegion 0x0000000000000580-0x00000000000005BB (\GPIO) (20160422/utaddress-255)
Jul 28 15:33:17 localhost vmunix: [    7.552731] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 15:33:17 localhost vmunix: [    7.553853] ACPI Warning: SystemIO range 0x0000000000000580-0x00000000000005AF conflicts with OpRegion 0x0000000000000580-0x00000000000005BE (\GPCM) (20160422/utaddress-255)
Jul 28 15:33:17 localhost vmunix: [    7.556230] ACPI Warning: SystemIO range 0x0000000000000580-0x00000000000005AF conflicts with OpRegion 0x0000000000000580-0x00000000000005BB (\GPIO) (20160422/utaddress-255)
Jul 28 15:33:17 localhost vmunix: [    7.558815] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 15:33:17 localhost vmunix: [    7.560144] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 28 15:33:18 localhost vmunix: [    7.670414] Non-volatile memory driver v1.3

...

Jul 28 15:33:23 localhost vmunix: [    9.259071] i915 0000:00:02.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x0000
Jul 28 15:33:23 localhost vmunix: [    9.259077] [drm] failed to find VBIOS tables
Jul 28 15:33:23 localhost vmunix: [    9.259614] vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem

...

Jul 28 15:33:24 localhost vmunix: [    9.398653] [drm] RC6 disabled, disabling runtime PM support
Jul 28 15:33:24 localhost vmunix: [    9.398720] [drm] Initialized i915 1.6.0 20160425 for 0000:00:02.0 on minor 0
Jul 28 15:33:24 localhost vmunix: [   10.153770] intel_powerclamp: No package C-state available
Jul 28 15:33:25 localhost vmunix: [   10.276405] intel_powerclamp: No package C-state available


-- 
♥Ⓐ  ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org

  reply	other threads:[~2016-07-29 10:52 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-27  8:58 bug#24087: recovery from suspend is broken with recent libreboot + linux-libre 4.7 ng0
2016-07-28 12:21 ` Danny Milosavljevic
2016-07-28 16:04   ` ng0
2016-07-29 10:51     ` ng0 [this message]
2016-07-30  4:26   ` Mark H Weaver
2016-07-30  6:24     ` Clément Lassieur
2016-07-30  8:38       ` ng0
2016-07-30 20:38         ` Clément Lassieur
2016-07-31  2:49         ` Mark H Weaver
2016-07-31 20:18       ` Ricardo Wurmus
2016-08-01 14:23     ` ng0
2016-08-08 22:23   ` Danny Milosavljevic
2016-07-31  0:40 ` Danny Milosavljevic
2016-07-31 19:23   ` Vincent Legoll
2016-08-19  7:58 ` ng0
2016-08-22 22:50   ` Clément Lassieur
2017-05-27 15:26     ` Clément Lassieur
2017-05-27 18:38       ` Christopher Allan Webber
2017-05-27 19:30         ` Clément Lassieur
     [not found] ` <handler.24087.B.146963323422208.ack@debbugs.gnu.org>
2016-08-19  8:03   ` bug#24087: Acknowledgement (recovery from suspend is broken with recent libreboot + linux-libre 4.7) ng0
2016-08-22 22:39 ` bug#24087: ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oa5gvhst.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=24087@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).