From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: bug#24087: recovery from suspend is broken with recent libreboot + linux-libre 4.7 Date: Fri, 29 Jul 2016 10:51:14 +0000 Message-ID: <87oa5gvhst.fsf@we.make.ritual.n0.is> References: <87r3af4fux.fsf@we.make.ritual.n0.is> <20160728142137.1aeb86fb@scratchpost.org> <87k2g5da0b.fsf@we.make.ritual.n0.is> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55357) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bT5Oh-0001Hk-Iw for bug-guix@gnu.org; Fri, 29 Jul 2016 06:52:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bT5Oc-0006qG-It for bug-guix@gnu.org; Fri, 29 Jul 2016 06:52:06 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:52705) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bT5Oc-0006py-ET for bug-guix@gnu.org; Fri, 29 Jul 2016 06:52:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1bT5Oc-0005Qa-1F for bug-guix@gnu.org; Fri, 29 Jul 2016 06:52:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87k2g5da0b.fsf@we.make.ritual.n0.is> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 24087@debbugs.gnu.org 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] [] dump_stack+0x63/0x90 Jul 28 15:32:37 localhost vmunix: [ 0.000000] [] __warn+0xd1/0xf0 Jul 28 15:32:38 localhost vmunix: [ 0.000000] [] warn_slowpath_fmt_taint+0x57/0x70 Jul 28 15:32:38 localhost vmunix: [ 0.000000] [] ? __early_ioremap+0x14b/0x1d2 Jul 28 15:32:38 localhost vmunix: [ 0.000000] [] warn_invalid_dmar.part.7+0x78/0x90 Jul 28 15:32:38 localhost vmunix: [ 0.000000] [] dmar_validate_one_drhd+0x84/0xe0 Jul 28 15:32:38 localhost vmunix: [ 0.000000] [] dmar_walk_remapping_entries+0x83/0x1a0 Jul 28 15:32:38 localhost vmunix: [ 0.000000] [] detect_intel_iommu+0x5f/0xf2 Jul 28 15:32:38 localhost vmunix: [ 0.000000] [] ? xen_swiotlb_init+0x4b0/0x4b0 Jul 28 15:32:39 localhost vmunix: [ 0.000000] [] pci_iommu_alloc+0x4a/0x6c Jul 28 15:32:39 localhost vmunix: [ 0.000000] [] mem_init+0x11/0xa3 Jul 28 15:32:39 localhost vmunix: [ 0.000000] [] start_kernel+0x230/0x489 Jul 28 15:32:39 localhost vmunix: [ 0.000000] [] ? early_idt_handler_array+0x120/0x120 Jul 28 15:32:39 localhost vmunix: [ 0.000000] [] x86_64_start_reservations+0x2f/0x31 Jul 28 15:32:39 localhost vmunix: [ 0.000000] [] 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