[Kernel-packages] [Bug 1891931] Re: [linux-azure] Panic when triggering hibernation

2020-08-31 Thread Dexuan Cui
I can confirm now hibernation can work with 5.4.0-1023, despite a
harmless warning:

root@decui-tmp-2004:~# echo disk >/sys/power/state
[   56.945758] PM: hibernation entry
[   57.165520] Filesystems sync: 0.007 seconds
[   57.169492] Freezing user space processes ... (elapsed 0.001 seconds) done.
[   57.177529] OOM killer disabled.
[   57.180702] PM: Marking nosave pages: [mem 0x-0x0fff]
[   57.185925] PM: Marking nosave pages: [mem 0x0009f000-0x000f]
[   57.191239] PM: Marking nosave pages: [mem 0x3fff-0x]
[   57.197810] PM: Basic memory bitmaps created
[   57.201563] PM: Preallocating image memory... done (allocated 210160 pages)
[   57.623616] PM: Allocated 840640 kbytes in 0.41 seconds (2050.34 MB/s)
[   57.629195] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) 
done.
[   57.637795] serial 00:04: disabled
[   58.847939] Disabling non-boot CPUs ...
[   58.852140] smpboot: CPU 1 is now offline
[   58.857921] smpboot: CPU 2 is now offline
[   58.863623] smpboot: CPU 3 is now offline
[   58.869363] unchecked MSR access error: WRMSR to 0x4106 (tried to write 
0x412d4f49 000100ee) at rIP: 0x9ee1d9b8 (hv_cpu_die+0xe8/0x110)
[   58.870052] Call Trace:
[   58.870052]  hv_suspend+0x5a/0x87
[   58.870052]  syscore_suspend+0x59/0x1a0
[   58.870052]  hibernation_snapshot+0x1bc/0x460
[   58.870052]  hibernate.cold+0x6d/0x1f6
[   58.870052]  state_store+0xde/0xe0
[   58.870052]  kobj_attr_store+0x12/0x20
[   58.870052]  sysfs_kf_write+0x3e/0x50
[   58.870052]  kernfs_fop_write+0xda/0x1b0
[   58.870052]  __vfs_write+0x1b/0x40
[   58.870052]  vfs_write+0xb9/0x1a0
[   58.870052]  ksys_write+0x67/0xe0
[   58.870052]  __x64_sys_write+0x1a/0x20
[   58.870052]  do_syscall_64+0x5e/0x200
[   58.870052]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[   58.870052] RIP: 0033:0x7f2f9dfcb057
[   58.870052] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 
f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 
f0 ff ff 77 51 c3 48 83 ec 28 48 89 54 24 18 48 89 74 24
[   58.870052] RSP: 002b:7ffe96046608 EFLAGS: 0246 ORIG_RAX: 
0001
[   58.870052] RAX: ffda RBX: 0005 RCX: 7f2f9dfcb057
[   58.870052] RDX: 0005 RSI: 55ca5250c450 RDI: 0001
[   58.870052] RBP: 55ca5250c450 R08: 000a R09: 0004
[   58.870052] R10: 55ca50a2d017 R11: 0246 R12: 0005
[   58.870052] R13: 7f2f9e0a66a0 R14: 7f2f9e0a74a0 R15: 7f2f9e0a68a0
[   58.870052] PM: Creating hibernation image:
[   58.870052] PM: Need to copy 201788 pages
[   58.870052] PM: Normal pages needed: 201788 + 1024, available pages: 3992087
[   58.870052] PM: Hibernation image created (201788 pages copied)
[   58.870052] Enabling non-boot CPUs ...
[   58.870052] x86: Booting SMP configuration:
[   58.871862] smpboot: Booting Node 0 Processor 1 APIC 0x1
[   58.875719] CPU1 is up
[   58.877194] smpboot: Booting Node 0 Processor 2 APIC 0x2
[   58.881047] CPU2 is up
[   58.882499] smpboot: Booting Node 0 Processor 3 APIC 0x3
[   58.886033] CPU3 is up
[   58.891099] hv_utils: KVP IC version 4.0
[   58.893181] hv_utils: Shutdown IC version 3.2
[   58.896580] hv_balloon: Using Dynamic Memory protocol version 2.0
[   60.186366] hv_utils: Heartbeat IC version 3.0
[   61.952674] hv_utils: TimeSync IC version 4.0
[   68.108243] hv_balloon: Max. dynamic memory size: 16384 MB
[   70.552511] serial 00:03: activated
[   70.620778] serial 00:04: activated
[   70.692760] PM: Using 3 thread(s) for compression
[   70.716148] ata1.01: host indicates ignore ATA devices, ignored
[   70.760736] PM: Compressing and saving image data (202183 pages)...
[   70.760749] PM: Image saving progress:   0%
[   70.831492] ata1.00: host indicates ignore ATA devices, ignored
[   74.568857] PM: Image saving progress:  10%
[   89.707652] PM: Image saving progress:  20%
[  109.659651] PM: Image saving progress:  30%
[  125.565315] PM: Image saving progress:  40%
[  140.112605] PM: Image saving progress:  50%
[  146.074334] PM: Image saving progress:  60%
[  152.507964] PM: Image saving progress:  70%
[  161.068827] PM: Image saving progress:  80%
[  170.115167] PM: Image saving progress:  90%
[  177.616417] PM: Image saving progress: 100%
[  178.566922] PM: Image saving done
[  178.623924] PM: Wrote 808732 kbytes in 107.80 seconds (7.50 MB/s)
[  178.686742] PM: S|
[  178.791430] kvm: exiting hardware virtualization
[  178.851852] sd 0:0:0:0: [sdb] Synchronizing SCSI cache
[  178.913444] ACPI: Preparing to enter system sleep state S5
[  178.975244] reboot: Power down
[  179.043250] acpi_power_off called

This warning can be fixed by this upstream fix:
38dce4195f0d ("x86/hyperv: Properly suspend/resume reenlightenment 
notifications")

How to reproduce the warning: before following
https://bugs.launchpad.net/ubuntu/+source/linux-
azure/+bug/1880032/comments/14 to test hibernation, make sure that
"lsmod" 

[Kernel-packages] [Bug 1891931] Re: [linux-azure] Panic when triggering hibernation

2020-08-31 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-azure - 5.4.0-1023.23

---
linux-azure (5.4.0-1023.23) focal; urgency=medium

  * focal/linux-azure: 5.4.0-1023.23 -proposed tracker (LP: #1890736)

  * Focal update: v5.4.52 upstream stable release (LP: #1887853)
- [Packaging] module intel-rapl-perf rename

  * Focal update: v5.4.53 upstream stable release (LP: #1888560)
- [Config] updateconfigs for BLK_DEV_SR_VENDOR

  * Focal update: v5.4.51 upstream stable release (LP: #1886995)
- [Config] updateconfigs for EFI_CUSTOM_SSDT_OVERLAYS

  * Packaging resync (LP: #1786013)
- [Packaging] update variants
- [Packaging] update update.conf

  * [linux-azure] Panic when triggering hibernation (LP: #1891931)
- Revert "video: hyperv_fb: Fix hibernation for the deferred IO feature"

  [ Ubuntu: 5.4.0-44.48 ]

  * focal/linux: 5.4.0-44.48 -proposed tracker (LP: #1891049)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
  * ipsec: policy priority management is broken (LP: #1890796)
- xfrm: policy: match with both mark and mask on user interfaces

  [ Ubuntu: 5.4.0-43.47 ]

  * focal/linux: 5.4.0-43.47 -proposed tracker (LP: #1890746)
  * Packaging resync (LP: #1786013)
- update dkms package versions
  * Devlink -  add RoCE disable kernel support  (LP: #1877270)
- devlink: Add new "enable_roce" generic device param
- net/mlx5: Document flow_steering_mode devlink param
- net/mlx5: Handle "enable_roce" devlink param
- IB/mlx5: Rename profile and init methods
- IB/mlx5: Load profile according to RoCE enablement state
- net/mlx5: Remove unneeded variable in mlx5_unload_one
- net/mlx5: Add devlink reload
- IB/mlx5: Do reverse sequence during device removal
  * msg_zerocopy.sh in net from ubuntu_kernel_selftests failed (LP: #1812620)
- selftests/net: relax cpu affinity requirement in msg_zerocopy test
  * Enlarge hisi_sec2 capability (LP: #1890222)
- Revert "UBUNTU: [Config] Disable hisi_sec2 temporarily"
- crypto: hisilicon - update SEC driver module parameter
  * Fix missing HDMI/DP Audio on an HP Desktop (LP: #1890441)
- ALSA: hda/hdmi: Add quirk to force connectivity
  * Fix IOMMU error on AMD Radeon Pro W5700 (LP: #1890306)
- PCI: Mark AMD Navi10 GPU rev 0x00 ATS as broken
  * ASoC:amd:renoir:  the dmic can't record sound after suspend and resume
(LP: #1890220)
- SAUCE: ASoC: amd: renoir: restore two more registers during resume
  * No sound, Dummy output on Acer Swift 3 SF314-57G with Ice Lake core-i7  CPU
(LP: #1877757)
- ASoC: SOF: Intel: hda: fix generic hda codec support
  * Fix right speaker of HP laptop (LP: #1889375)
- SAUCE: hda/realtek: Fix right speaker of HP laptop
  * blk_update_request error when mount nvme partition (LP: #1872383)
- SAUCE: nvme-pci: prevent SK hynix PC400 from using Write Zeroes command
  * soc/amd/renoir: detect dmic from acpi table (LP: #1887734)
- ASoC: amd: add logic to check dmic hardware runtime
- ASoC: amd: add ACPI dependency check
- ASoC: amd: fixed kernel warnings
  * soc/amd/renoir: change the module name to make it work with ucm3
(LP: #1888166)
- AsoC: amd: add missing snd- module prefix to the acp3x-rn driver kernel
  module
- SAUCE: remove a kernel module since its name is changed
  * Focal update: v5.4.55 upstream stable release (LP: #1890343)
- AX.25: Fix out-of-bounds read in ax25_connect()
- AX.25: Prevent out-of-bounds read in ax25_sendmsg()
- dev: Defer free of skbs in flush_backlog
- drivers/net/wan/x25_asy: Fix to make it work
- ip6_gre: fix null-ptr-deref in ip6gre_init_net()
- net-sysfs: add a newline when printing 'tx_timeout' by sysfs
- net: udp: Fix wrong clean up for IS_UDPLITE macro
- qrtr: orphan socket in qrtr_release()
- rtnetlink: Fix memory(net_device) leak when ->newlink fails
- rxrpc: Fix sendmsg() returning EPIPE due to recvmsg() returning ENODATA
- tcp: allow at most one TLP probe per flight
- AX.25: Prevent integer overflows in connect and sendmsg
- sctp: shrink stream outq only when new outcnt < old outcnt
- sctp: shrink stream outq when fails to do addstream reconf
- udp: Copy has_conns in reuseport_grow().
- udp: Improve load balancing for SO_REUSEPORT.
- regmap: debugfs: check count when read regmap file
- PM: wakeup: Show statistics for deleted wakeup sources again
- Revert "dpaa_eth: fix usage as DSA master, try 3"
- Linux 5.4.55
  * Add support for Atlantic NIC firmware v4 (LP: #1886908)
- net: atlantic: simplify hw_get_fw_version() usage
- net: atlantic: align return value of ver_match function with function name
- net: atlantic: add support for FW 4.x
  * perf vendor events s390: Add new deflate counters for IBM z15 (LP: #1888551)
- perf vendor events s390: Add new deflate counters for IBM z15
  * Focal update: v5.4.54 upstream stable release (LP: #1889669)
- soc: qcom: rpmh: Dirt 

[Kernel-packages] [Bug 1891931] Re: [linux-azure] Panic when triggering hibernation

2020-08-18 Thread Stefan Bader
** Changed in: linux-azure (Ubuntu)
   Status: New => Invalid

** Changed in: linux-azure (Ubuntu Focal)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1891931

Title:
  [linux-azure] Panic when triggering hibernation

Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  We backported several upstream commits in LP #1880032, but the
  following commit wasn't necessary and it's causing a panic when trying
  to hibernate an azure instance, as described by comment #8 in LP
  #1880032 (https://bugs.launchpad.net/ubuntu/+source/linux-
  azure/+bug/1880032/comments/8):

  0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO 
feature"):
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6

  We should include the patch only if the kernel also includes
  a4ddb11d297e ("video: hyperv: hyperv_fb: Support deferred IO for Hyper-V 
frame buffer driver"

  I manage to reproduce the panic and I can confirm that reverting the
  offending commit solves the problem. I managed to test it on several D
  and E instances types and the system successfully hibernates. I also
  tried to test the scenarios where the system has high memory usage and
  on a 8GB VM hibernation worked up until 70% of memory utilization.

  [ 67.736061] [ cut here ]
  [ 67.736068] WARNING: CPU: 5 PID: 1358 at kernel/workqueue.c:3040 
__flush_work+0x1b5/0x1d0
  [ 67.736068] Modules linked in: xt_owner iptable_security xt_conntrack 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter nls_iso8859_1 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sb_edac crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper 
joydev hid_generic hyperv_fb cfbfillrect hid_hyperv intel_rapl_perf serio_raw 
hyperv_keyboard pata_acpi hv_netvsc hv_balloon hid cfbimgblt pci_hyperv 
cfbcopyarea hv_utils pci_hyperv_intf sch_fq_codel drm 
drm_panel_orientation_quirks i2c_core ip_tables x_tables autofs4
  [ 67.736088] CPU: 5 PID: 1358 Comm: bash Not tainted 5.4.0-1022-azure 
#22-Ubuntu
  [ 67.736089] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007 06/02/2017
  [ 67.736091] RIP: 0010:__flush_work+0x1b5/0x1d0
  [ 67.736092] Code: f0 eb e3 4d 8b 7c 24 20 e9 f3 fe ff ff 8b 0b 48 8b 53 08 
83 e1 08 48 0f ba 2b 03 80 c9 f0 e9 4f ff ff ff 0f 0b e9 68 ff ff ff <0f> 0b 45 
31 f6 e9 5e ff ff ff e8 ec e0 fd ff 66 66 2e 0f 1f 84 00
  [ 67.736095] RSP: 0018:a7ce8a8ffb78 EFLAGS: 00010246
  [ 67.736096] RAX:  RBX: 8be3621f02a0 RCX: 
  [ 67.736096] RDX: 0001 RSI: 0001 RDI: 8be3621f02a0
  [ 67.736097] RBP: a7ce8a8ffbf0 R08:  R09: ff010101
  [ 67.736098] R10: 8be363f7a320 R11: 0001 R12: 8be3621f02a0
  [ 67.736098] R13: 0001 R14: 0001 R15: bc390fd1
  [ 67.736099] FS: 7f6df35fe740() GS:8be375d4() 
knlGS:
  [ 67.736100] CS: 0010 DS:  ES:  CR0: 80050033
  [ 67.736100] CR2: 561eef2c1b50 CR3: 000e40a14004 CR4: 001706e0
  [ 67.736102] Call Trace:
  [ 67.736108] __cancel_work_timer+0x107/0x180
  [ 67.736119] cancel_delayed_work_sync+0x13/0x20
  [ 67.736121] hvfb_suspend+0x48/0x80 [hyperv_fb]
  [ 67.736122] vmbus_suspend+0x2a/0x40
  [ 67.736125] dpm_run_callback+0x5b/0x150
  [ 67.736127] __device_suspend_noirq+0x9e/0x2f0
  [ 67.736128] dpm_suspend_noirq+0x101/0x2d0
  [ 67.736130] dpm_suspend_end+0x53/0x80
  [ 67.736132] hibernation_snapshot+0xd8/0x460
  [ 67.736133] hibernate.cold+0x6d/0x1f6
  [ 67.736135] state_store+0xde/0xe0
  [ 67.736138] kobj_attr_store+0x12/0x20
  [ 67.736141] sysfs_kf_write+0x3e/0x50
  [ 67.736142] kernfs_fop_write+0xda/0x1b0
  [ 67.736145] __vfs_write+0x1b/0x40
  [ 67.736147] vfs_write+0xb9/0x1a0
  [ 67.736149] ksys_write+0x67/0xe0
  [ 67.736150] __x64_sys_write+0x1a/0x20
  [ 67.736152] do_syscall_64+0x5e/0x200
  [ 67.736156] entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 67.736157] RIP: 0033:0x7f6df3712057

  [Test Case]

  Follow the steps from https://bugs.launchpad.net/ubuntu/+source/linux-
  azure/+bug/1880032/comments/14.

  [Regression Potential]

  The revert touches the Hyper-V framebuffer driver and can potentially
  cause the VM to not boot or cause hibernation to fail (again).
  Although the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1891931/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : 

[Kernel-packages] [Bug 1891931] Re: [linux-azure] Panic when triggering hibernation

2020-08-17 Thread Marcelo Cerri
** Changed in: linux-azure (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1891931

Title:
  [linux-azure] Panic when triggering hibernation

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  We backported several upstream commits in LP #1880032, but the
  following commit wasn't necessary and it's causing a panic when trying
  to hibernate an azure instance, as described by comment #8 in LP
  #1880032 (https://bugs.launchpad.net/ubuntu/+source/linux-
  azure/+bug/1880032/comments/8):

  0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO 
feature"):
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6

  We should include the patch only if the kernel also includes
  a4ddb11d297e ("video: hyperv: hyperv_fb: Support deferred IO for Hyper-V 
frame buffer driver"

  I manage to reproduce the panic and I can confirm that reverting the
  offending commit solves the problem. I managed to test it on several D
  and E instances types and the system successfully hibernates. I also
  tried to test the scenarios where the system has high memory usage and
  on a 8GB VM hibernation worked up until 70% of memory utilization.

  [ 67.736061] [ cut here ]
  [ 67.736068] WARNING: CPU: 5 PID: 1358 at kernel/workqueue.c:3040 
__flush_work+0x1b5/0x1d0
  [ 67.736068] Modules linked in: xt_owner iptable_security xt_conntrack 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter nls_iso8859_1 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sb_edac crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper 
joydev hid_generic hyperv_fb cfbfillrect hid_hyperv intel_rapl_perf serio_raw 
hyperv_keyboard pata_acpi hv_netvsc hv_balloon hid cfbimgblt pci_hyperv 
cfbcopyarea hv_utils pci_hyperv_intf sch_fq_codel drm 
drm_panel_orientation_quirks i2c_core ip_tables x_tables autofs4
  [ 67.736088] CPU: 5 PID: 1358 Comm: bash Not tainted 5.4.0-1022-azure 
#22-Ubuntu
  [ 67.736089] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007 06/02/2017
  [ 67.736091] RIP: 0010:__flush_work+0x1b5/0x1d0
  [ 67.736092] Code: f0 eb e3 4d 8b 7c 24 20 e9 f3 fe ff ff 8b 0b 48 8b 53 08 
83 e1 08 48 0f ba 2b 03 80 c9 f0 e9 4f ff ff ff 0f 0b e9 68 ff ff ff <0f> 0b 45 
31 f6 e9 5e ff ff ff e8 ec e0 fd ff 66 66 2e 0f 1f 84 00
  [ 67.736095] RSP: 0018:a7ce8a8ffb78 EFLAGS: 00010246
  [ 67.736096] RAX:  RBX: 8be3621f02a0 RCX: 
  [ 67.736096] RDX: 0001 RSI: 0001 RDI: 8be3621f02a0
  [ 67.736097] RBP: a7ce8a8ffbf0 R08:  R09: ff010101
  [ 67.736098] R10: 8be363f7a320 R11: 0001 R12: 8be3621f02a0
  [ 67.736098] R13: 0001 R14: 0001 R15: bc390fd1
  [ 67.736099] FS: 7f6df35fe740() GS:8be375d4() 
knlGS:
  [ 67.736100] CS: 0010 DS:  ES:  CR0: 80050033
  [ 67.736100] CR2: 561eef2c1b50 CR3: 000e40a14004 CR4: 001706e0
  [ 67.736102] Call Trace:
  [ 67.736108] __cancel_work_timer+0x107/0x180
  [ 67.736119] cancel_delayed_work_sync+0x13/0x20
  [ 67.736121] hvfb_suspend+0x48/0x80 [hyperv_fb]
  [ 67.736122] vmbus_suspend+0x2a/0x40
  [ 67.736125] dpm_run_callback+0x5b/0x150
  [ 67.736127] __device_suspend_noirq+0x9e/0x2f0
  [ 67.736128] dpm_suspend_noirq+0x101/0x2d0
  [ 67.736130] dpm_suspend_end+0x53/0x80
  [ 67.736132] hibernation_snapshot+0xd8/0x460
  [ 67.736133] hibernate.cold+0x6d/0x1f6
  [ 67.736135] state_store+0xde/0xe0
  [ 67.736138] kobj_attr_store+0x12/0x20
  [ 67.736141] sysfs_kf_write+0x3e/0x50
  [ 67.736142] kernfs_fop_write+0xda/0x1b0
  [ 67.736145] __vfs_write+0x1b/0x40
  [ 67.736147] vfs_write+0xb9/0x1a0
  [ 67.736149] ksys_write+0x67/0xe0
  [ 67.736150] __x64_sys_write+0x1a/0x20
  [ 67.736152] do_syscall_64+0x5e/0x200
  [ 67.736156] entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 67.736157] RIP: 0033:0x7f6df3712057

  [Test Case]

  Follow the steps from https://bugs.launchpad.net/ubuntu/+source/linux-
  azure/+bug/1880032/comments/14.

  [Regression Potential]

  The revert touches the Hyper-V framebuffer driver and can potentially
  cause the VM to not boot or cause hibernation to fail (again).
  Although the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1891931/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1891931] Re: [linux-azure] Panic when triggering hibernation

2020-08-17 Thread Marcelo Cerri
Revert submitted for review: https://lists.ubuntu.com/archives/kernel-
team/2020-August/112766.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1891931

Title:
  [linux-azure] Panic when triggering hibernation

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Focal:
  In Progress

Bug description:
  [Impact]

  We backported several upstream commits in LP #1880032, but the
  following commit wasn't necessary and it's causing a panic when trying
  to hibernate an azure instance, as described by comment #8 in LP
  #1880032 (https://bugs.launchpad.net/ubuntu/+source/linux-
  azure/+bug/1880032/comments/8):

  0a14dbaa0736 ("video: hyperv_fb: Fix hibernation for the deferred IO 
feature"):
  
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-azure/+git/focal/commit/?h=Ubuntu-azure-5.4.0-1022.22=0a14dbaa0736a6021c02e74d42cf3a7ca5438da6

  We should include the patch only if the kernel also includes
  a4ddb11d297e ("video: hyperv: hyperv_fb: Support deferred IO for Hyper-V 
frame buffer driver"

  I manage to reproduce the panic and I can confirm that reverting the
  offending commit solves the problem. I managed to test it on several D
  and E instances types and the system successfully hibernates. I also
  tried to test the scenarios where the system has high memory usage and
  on a 8GB VM hibernation worked up until 70% of memory utilization.

  [ 67.736061] [ cut here ]
  [ 67.736068] WARNING: CPU: 5 PID: 1358 at kernel/workqueue.c:3040 
__flush_work+0x1b5/0x1d0
  [ 67.736068] Modules linked in: xt_owner iptable_security xt_conntrack 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter nls_iso8859_1 
dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sb_edac crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper 
joydev hid_generic hyperv_fb cfbfillrect hid_hyperv intel_rapl_perf serio_raw 
hyperv_keyboard pata_acpi hv_netvsc hv_balloon hid cfbimgblt pci_hyperv 
cfbcopyarea hv_utils pci_hyperv_intf sch_fq_codel drm 
drm_panel_orientation_quirks i2c_core ip_tables x_tables autofs4
  [ 67.736088] CPU: 5 PID: 1358 Comm: bash Not tainted 5.4.0-1022-azure 
#22-Ubuntu
  [ 67.736089] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007 06/02/2017
  [ 67.736091] RIP: 0010:__flush_work+0x1b5/0x1d0
  [ 67.736092] Code: f0 eb e3 4d 8b 7c 24 20 e9 f3 fe ff ff 8b 0b 48 8b 53 08 
83 e1 08 48 0f ba 2b 03 80 c9 f0 e9 4f ff ff ff 0f 0b e9 68 ff ff ff <0f> 0b 45 
31 f6 e9 5e ff ff ff e8 ec e0 fd ff 66 66 2e 0f 1f 84 00
  [ 67.736095] RSP: 0018:a7ce8a8ffb78 EFLAGS: 00010246
  [ 67.736096] RAX:  RBX: 8be3621f02a0 RCX: 
  [ 67.736096] RDX: 0001 RSI: 0001 RDI: 8be3621f02a0
  [ 67.736097] RBP: a7ce8a8ffbf0 R08:  R09: ff010101
  [ 67.736098] R10: 8be363f7a320 R11: 0001 R12: 8be3621f02a0
  [ 67.736098] R13: 0001 R14: 0001 R15: bc390fd1
  [ 67.736099] FS: 7f6df35fe740() GS:8be375d4() 
knlGS:
  [ 67.736100] CS: 0010 DS:  ES:  CR0: 80050033
  [ 67.736100] CR2: 561eef2c1b50 CR3: 000e40a14004 CR4: 001706e0
  [ 67.736102] Call Trace:
  [ 67.736108] __cancel_work_timer+0x107/0x180
  [ 67.736119] cancel_delayed_work_sync+0x13/0x20
  [ 67.736121] hvfb_suspend+0x48/0x80 [hyperv_fb]
  [ 67.736122] vmbus_suspend+0x2a/0x40
  [ 67.736125] dpm_run_callback+0x5b/0x150
  [ 67.736127] __device_suspend_noirq+0x9e/0x2f0
  [ 67.736128] dpm_suspend_noirq+0x101/0x2d0
  [ 67.736130] dpm_suspend_end+0x53/0x80
  [ 67.736132] hibernation_snapshot+0xd8/0x460
  [ 67.736133] hibernate.cold+0x6d/0x1f6
  [ 67.736135] state_store+0xde/0xe0
  [ 67.736138] kobj_attr_store+0x12/0x20
  [ 67.736141] sysfs_kf_write+0x3e/0x50
  [ 67.736142] kernfs_fop_write+0xda/0x1b0
  [ 67.736145] __vfs_write+0x1b/0x40
  [ 67.736147] vfs_write+0xb9/0x1a0
  [ 67.736149] ksys_write+0x67/0xe0
  [ 67.736150] __x64_sys_write+0x1a/0x20
  [ 67.736152] do_syscall_64+0x5e/0x200
  [ 67.736156] entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [ 67.736157] RIP: 0033:0x7f6df3712057

  [Test Case]

  Follow the steps from https://bugs.launchpad.net/ubuntu/+source/linux-
  azure/+bug/1880032/comments/14.

  [Regression Potential]

  The revert touches the Hyper-V framebuffer driver and can potentially
  cause the VM to not boot or cause hibernation to fail (again).
  Although the risk is low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1891931/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   :