Attachment 125986 Details for Bug 97396 – dmesg (part of)

dmesg (part of)

dmesg_471_part (text/plain), 3.51 KB, created by Rainer Fiebig on 2016-08-23 19:59:16 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Rainer Fiebig

Created: 2016-08-23 19:59:16 UTC

Size: 3.51 KB

patch

obsolete

>...
>Syncing filesystems ... done.
>Freezing user space processes ... (elapsed 0.001 seconds) done.
>Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) 
>PM: Preallocating image memory... done (allocated 459207 pages)
>PM: Allocated 1836828 kbytes in 0.26 seconds (7064.72 MB/s)
>Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
>Suspending console(s) (use no_console_suspend to debug)
>serial 00:06: disabled
>i8042 kbd 00:02: System wakeup enabled by ACPI
>PM: freeze of devices complete after 102.494 msecs
>PM: late freeze of devices complete after 10.628 msecs
>PM: noirq freeze of devices complete after 0.600 msecs
>ACPI: Preparing to enter system sleep state S4
>PM: Saving platform NVS memory
>Disabling non-boot CPUs ...
>smpboot: CPU 1 is now offline
>smpboot: CPU 2 is now offline
>smpboot: CPU 3 is now offline
>PM: Creating hibernation image:
>PM: Need to copy 458379 pages
>PM: Restoring platform NVS memory
>microcode: CPU0 sig=0x20655, pf=0x2, revision=0x4
>Enabling non-boot CPUs ...
>x86: Booting SMP configuration:
>smpboot: Booting Node 0 Processor 1 APIC 0x4
> cache: parent cpu1 should not be sleeping
>microcode: CPU1 sig=0x20655, pf=0x2, revision=0x4
>CPU1 is up
>smpboot: Booting Node 0 Processor 2 APIC 0x1
> cache: parent cpu2 should not be sleeping
>microcode: CPU2 sig=0x20655, pf=0x2, revision=0x4
>CPU2 is up
>smpboot: Booting Node 0 Processor 3 APIC 0x5
> cache: parent cpu3 should not be sleeping
>microcode: CPU3 sig=0x20655, pf=0x2, revision=0x4
>CPU3 is up
>ACPI: Waking up from system sleep state S4
>PM: noirq restore of devices complete after 10.743 msecs
>PM: early restore of devices complete after 0.163 msecs
>usb usb1: root hub lost power or was reset
>ehci-pci 0000:00:1a.0: cache line size of 32 is not supported
>usb usb2: root hub lost power or was reset
>ehci-pci 0000:00:1d.0: cache line size of 32 is not supported
>rtc_cmos 00:01: System wakeup disabled by ACPI
>i8042 kbd 00:02: System wakeup disabled by ACPI
>serial 00:06: activated
>sd 0:0:0:0: [sda] Starting disk
>sd 2:0:0:0: [sdb] Starting disk
>r8169 0000:03:00.0 eth0: link down
>ata9.00: configured for UDMA/33
>usb 2-1: reset high-speed USB device number 2 using ehci-pci
>ata7: SATA link down (SStatus 0 SControl 300)
>ata8: SATA link down (SStatus 0 SControl 300)
>ata2: SATA link down (SStatus 0 SControl 300)
>ata6: SATA link down (SStatus 0 SControl 300)
>ata5: SATA link down (SStatus 0 SControl 300)
>ata4: SATA link down (SStatus 0 SControl 300)
>ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>ata3.00: configured for UDMA/133
>usb 1-1: reset high-speed USB device number 2 using ehci-pci
>ata1.00: configured for UDMA/133
>hub 2-1:1.0: hub_ext_port_status failed (err = -32)
>hub 2-1:1.0: hub_ext_port_status failed (err = -32)
>usb 1-1.6: reset low-speed USB device number 3 using ehci-pci
>PM: restore of devices complete after 1172.168 msecs
>Restarting kernel threads ... done.
>Restarting tasks ... done.
>r8169 0000:03:00.0 eth0: link up
>[drm] stuck on bsd ring
>[drm] GPU HANG: ecode 5:2:0x01000000, reason: Engine(s) hung, action: reset
>[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
>[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
>[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
>[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
>[drm] GPU crash dump saved to /sys/class/drm/card0/error
>drm/i915: Resetting chip after gpu hang
>me@linux:~>

Actions: View

Attachments on bug 97396: 125985 | 125986 | 126016 | 126019

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.