Attachments
|
1. magic numbers 2. dmesg 3.lspci
|
Details
|
config file for kernel 4.2
|
Details
|
dmesg after failed resume, with hibernation done using Method 1)
|
Details
|
dmesg after failed resume, with hibernation done using Method 2)
|
Details
|
dmesg after failed resume, with hibernation done using Method 3)
|
Details
|
dmesg after failed resume, with hibernation done using Method 4)
|
Details
|
Video of resume failure using Method 1 and 2
|
Details
|
Video of resume failure using Method 3 and 4
|
Details
|
Video of resume success and failure using Method suggested by Chen Yu in Comment 30
|
Details
|
dmesg after successful resume, using Method suggested by Chen Yu in Comment 30
|
Details
|
dmesg after failed resume (2nd try), using Method suggested by Chen Yu in Comment 30
|
Details
|
Dmesg before doing hibernation, in response to Comment 38
|
Details
|
Dmesg after doing hibernation, in response to Comment 38
|
Details
|
Screen photo no_console_suspend with all messages before to failure (1/4)
|
Details
|
Screen photo no_console_suspend with all messages before failure (2/4)
|
Details
|
Screen photo no_console_suspend with all messages before failure (3/4)
|
Details
|
Screen photo no_console_suspend with all messages before failure (4/4)
|
Details
|
config file for kernel 4.2 with USB keyboard (so that init=/bin/bash works) and CONFIG_SATA_AHCI=y
|
Details
|
Screen photo init=/bin/bash with all messages before failure (1/6)
|
Details
|
Screen photo init=/bin/bash with all messages before failure (2/6)
|
Details
|
Screen photo init=/bin/bash with all messages before failure (3/6)
|
Details
|
Screen photo init=/bin/bash with all messages before failure (4/6)
|
Details
|
Screen photo init=/bin/bash with all messages before failure (5/6)
|
Details
|
Screen photo init=/bin/bash with all messages before failure (6/6)
|
Details
|
Dmesg after doing resume with init=/bin/bash
|
Details
|
debug patch to track resume after cpu offline
|
Details
|
kernel panic with parameter "text" in kernel command line 1/2
|
Details
|
kernel panic with parameter "text" in kernel command line 2/2
|
Details
|
screenshot with new debug info 1st try 1/2
|
Details
|
screenshot with new debug info 1st try 2/2
|
Details
|
lucky success screenshot with s4 patch 1/7
|
Details
|
lucky success screenshot with s4 patch 2/7
|
Details
|
lucky success screenshot with s4 patch 3/7
|
Details
|
lucky success screenshot with s4 patch 4/7
|
Details
|
lucky success screenshot with s4 patch 5/7
|
Details
|
lucky success screenshot with s4 patch 6/7
|
Details
|
lucky success screenshot with s4 patch 7/7
|
Details
|
lucky success screenshot with s4 patch - dmesg output
|
Details
|
screenshots of failure on second try with s4 patch 1/7
|
Details
|
screenshots of failure on second try with s4 patch 2/7
|
Details
|
screenshots of failure on second try with s4 patch 3/7
|
Details
|
screenshots of failure on second try with s4 patch 4/7
|
Details
|
screenshots of failure on second try with s4 patch 5/7
|
Details
|
screenshots of failure on second try with s4 patch 6/7
|
Details
|
screenshots of failure on second try with s4 patch 7/7
|
Details
|
dmesg after second failure with s4 patch, with pm_trace
|
Details
|
trial patch to enable the temporary direct-mapping for non-boot cpus before they die
|
Details
|
freeze with nonboot.diff 1/8
|
Details
|
freeze with nonboot.diff 2/8
|
Details
|
freeze with nonboot.diff 3/8
|
Details
|
freeze with nonboot.diff 4/8
|
Details
|
freeze with nonboot.diff 5/8
|
Details
|
freeze with nonboot.diff 6/8
|
Details
|
freeze with nonboot.diff 7/8
|
Details
|
freeze with nonboot.diff 8/8
|
Details
|
freeze with nonboot.diff 2/8 (as jpg, mistakenly uploaded as text earlier)
|
Details
|
force nonboot cpus to switch to safe pagetable when restoring page frames
|
Details
|
Dmesg after successful resume with hibernate_mapping.diff
|
Details
|
Dmesg after failed resume with hibernate_mapping.diff 1
|
Details
|
Dmesg after failed resume with hibernate_mapping.diff 2
|
Details
|
Dmesg after failed resume with hibernate_mapping.diff 3
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 1/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 2/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 3/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 4/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 5/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 6/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 7/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 8/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 9/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 10/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 11/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 12/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 13/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 14/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 15/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 16/17
|
Details
|
Screenshot of successful resume with hibernate_mapping.diff 17/17
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 1/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 2/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 3/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 4/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 5/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 6/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 7/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 8/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 9/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 10/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 11/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 12/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 13/14
|
Details
|
Screenshot of failed 1 resume with hibernate_mapping.diff 14/14
|
Details
|
Screenshot of failed 2 resume with hibernate_mapping.diff 1/2
|
Details
|
Screenshot of failed 2 resume with hibernate_mapping.diff 2/2
|
Details
|
Screenshot of failed 3 resume with hibernate_mapping.diff 1/5
|
Details
|
Screenshot of failed 3 resume with hibernate_mapping.diff 2/5
|
Details
|
Screenshot of failed 3 resume with hibernate_mapping.diff 3/5
|
Details
|
Screenshot of failed 3 resume with hibernate_mapping.diff 4/5
|
Details
|
Screenshot of failed 3 resume with hibernate_mapping.diff 5/5
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 1/9
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 2/9
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 3/9
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 4/9
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 5/9
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 6/9
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 7/9
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 8/9
|
Details
|
Screenshot of failed 4 resume with hibernate_mapping.diff 9/9
|
Details
|
Disable the warn_on invoking when nonboot cpus are not ready for exception handling
|
Details
|
dmesg after failed resume with forbid_rcu patch
|
Details
|
dmesg after succesful resume with forbid_rcu patch
|
Details
|
screenshot of critical moment during successful resume with forbid_rcu patch 1/2
|
Details
|
screenshot of critical moment during successful resume with forbid_rcu patch 2/2
|
Details
|
screenshot of critical moment during failed resume with forbid_rcu patch 1/2
|
Details
|
screenshot of critical moment during failed resume with forbid_rcu patch 2/2
|
Details
|
kernel config for 4.6.0-rc7
|
Details
|
messages before reboot on failed resume
|
Details
|
messages after freeze during 2nd hibernation
|
Details
|
resume failure messages 4.7-rc2 with patch/9158227/
|
Details
|
resume failure dmesg PM_TRACE 4.7-rc2 with patch/9158227/
|
Details
|
hibernation failure messages 4.7-rc2 with patch/9158227/
|
Details
|
hibernation failure PM_TRACE dmesg 4.7-rc2 with patch/9158227/
|
Details
|
hibernation failure messages2 4.7-rc2 with patch/9158227/
|
Details
|
hibernation failure PM_TRACE dmesg2 4.7-rc2 with patch/9158227/
|
Details
|
resume failure4 messages 4.7-rc2 with patch/9158227/
|
Details
|
resume failed photo 0: 4.7-rc3 + patch/9172981
|
Details
|
resume failed photo 1: 4.7-rc3 + patch/9172981
|
Details
|
resume failed dmesg 1 (PM_TRACE): 4.7-rc3 + patch/9172981
|
Details
|
resume failed photo 2: 4.7-rc3 + patch/9172981
|
Details
|
resume failed dmesg 2 (PM_TRACE): 4.7-rc3 + patch/9172981
|
Details
|
hibernation failed photo 3: 4.7-rc3 + patch/9172981
|
Details
|
hibernation failed dmesg 3 (PM_TRACE): 4.7-rc3 + patch/9172981
|
Details
|
resume failed photo 4: 4.7-rc3 + patch/9172981
|
Details
|
resume failed dmesg 4 (PM_TRACE): 4.7-rc3 + patch/9172981
|
Details
|
2nd hibernate attempt failed messages 4.7-rc5+patch9202321
|
Details
|
2nd hibernate attempt failed dmesg after reboot 4.7-rc5+patch9202321
|
Details
|
hibernation snapshot option
|
Details
|
we check what is after i8237A_resume during hibernation: it is ioapic_resume
|
Details
|
track i8237
|
Details
|
v2 debug i8237a
|
Details
|
dmesg 4.7-rc5+patch_9202321+attachment_221771_v2_debug_i8237a
|
Details
|
freeze photo 4.7-rc5+patch_9202321+attachment_221771_v2_debug_i8237a
|
Details
|
debug - show lock trace when deadlock
|
Details
|
dmesg after 1000 invocations of echo q > /proc/sysrq-trigger; 4.7-rc5+patch9202321+attachment221801
|
Details
|
kernel config for 4.7-rc5+patch9202321+attachment221801
|
Details
|
dma lock debug
|
Details
|
2nd hibernation freeze photo
|
Details
|
System.map for 4.7.0-rc5 + patch9202321 + attachment221841
|
Details
|
test dma_lock, dump more lockup info
|
Details
|
4.7-rc5 + patch/9202321 + attachment 221881
|
Details
|
system freeze photo, 4.7-rc5 + patch/9202321 + attachment 221881
|
Details
|
echo q > /proc/sysrq-trigger after 1rs hibernate-resume cycle.
|
Details
|
echo q > /proc/sysrq-trigger after 1rs hibernate-resume cycle. next photo
|
Details
|
echo q > /proc/sysrq-trigger after 1rs hibernate-resume cycle. I presses ctrl-alt-delete dozen times and I got this:
|
Details
|
config used for latest recompile without ARCH_USE_QUEUED_SPINLOCKS
|
Details
|
kernel config for 4.7-rc5+patch9202321+debug-qspinlock
|
Details
|