Kernel panic on boot (m1.small in cn-north-1)

Bug #1771679 reported by Dan Watkins on 2018-05-16
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
Artful
Medium
Kamal Mostafa
Bionic
Medium
Kamal Mostafa
linux-aws (Ubuntu)
Undecided
Unassigned
Bionic
Undecided
Kamal Mostafa

Bug Description

We're observing the following panic on boot when trying to boot an m1.small in cn-north-1 (which is a region in AWS China):

[ 2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
[ 2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
[ 2.271681] RSP: 0000:ffff8e21aa003ea0 EFLAGS: 00010046
[ 2.271681] RAX: ffffffff9dd82920 RBX: ffffffffff200000 RCX: 000000008728b34e
[ 2.271681] RDX: ffff8e21a3252800 RSI: ffff8e21a724e000 RDI: 000000000000001c
[ 2.271681] RBP: ffff8e21aa003eb8 R08: ffffffff9ea05040 R09: 0000000000000000
[ 2.271681] R10: ffff8e21aa003f28 R11: 0000000000000000 R12: 0000000000000001
[ 2.271681] R13: 0000000000000000 R14: 0000000000000022 R15: ffff8e21a3246900
[ 2.271681] FS: 0000000000000000(0000) GS:ffff8e21aa000000(0000) knlGS:0000000000000000
[ 2.271681] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.271681] CR2: ffffffffff200000 CR3: 000000000b80a000 CR4: 00000000000006f0
[ 2.271681] Call Trace:
[ 2.271681] <IRQ>
[ 2.271681] xen_hvm_evtchn_do_upcall+0xe/0x10
[ 2.271681] do_hvm_evtchn_intr+0xe/0x20
[ 2.271681] __handle_irq_event_percpu+0x44/0x1a0
[ 2.271681] handle_irq_event_percpu+0x32/0x80
[ 2.271681] handle_irq_event+0x3b/0x60
[ 2.271681] handle_fasteoi_irq+0x75/0x130
[ 2.271681] handle_irq+0x20/0x30
[ 2.271681] do_IRQ+0x46/0xd0
[ 2.271681] common_interrupt+0x84/0x84
[ 2.271681] </IRQ>
[ 2.271681] RIP: 0010:native_safe_halt+0x6/0x10
[ 2.271681] RSP: 0000:ffffffff9ea03e28 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdd
[ 2.271681] RAX: ffffffff9e12fba0 RBX: 0000000000000000 RCX: 0000000000000000
[ 2.271681] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
[ 2.271681] RBP: ffffffff9ea03e28 R08: 0000000000000002 R09: ffffffff9ea03e18
[ 2.271681] R10: ffffffff9ea03da0 R11: 00000000eb8a1d25 R12: 0000000000000000
[ 2.271681] R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
[ 2.271681] ? __cpuidle_text_start+0x8/0x8
[ 2.271681] default_idle+0x20/0x100
[ 2.271681] arch_cpu_idle+0x15/0x20
[ 2.271681] default_idle_call+0x23/0x30
[ 2.271681] do_idle+0x17f/0x1b0
[ 2.271681] cpu_startup_entry+0x73/0x80
[ 2.271681] rest_init+0xae/0xb0
[ 2.271681] start_kernel+0x4dc/0x4fd
[ 2.271681] x86_64_start_reservations+0x24/0x26
[ 2.271681] x86_64_start_kernel+0x74/0x77
[ 2.271681] secondary_startup_64+0xa5/0xb0
[ 2.271681] Code: 1f 84 00 00 00 00 00 66 66 66 66 90 55 48 89 e5 41 55 41 54 53 65 48 8b 1d 92 dc 29 62 41 bc 01 00 00 00 65 44 8b 2d 8c 8c 29 62 <c6> 03 00 44 89 e0 65 0f c1 05 2e 96 2a 62 85 c0 75 3b 48 8b 05
[ 2.271681] RIP: __xen_evtchn_do_upcall+0x24/0x80 RSP: ffff8e21aa003ea0
[ 2.271681] CR2: ffffffffff200000
[ 2.271681] ---[ end trace 956d0f4244642614 ]---
[ 2.271681] Kernel panic - not syncing: Fatal exception in interrupt

I've attached the full console log.

Dan Watkins (daniel-thewatkins) wrote :
Dan Watkins (daniel-thewatkins) wrote :

We've only seen this on m1.small instances, but we haven't tested exhaustively (we do know, though, that m3.large is fine).

The command used to create the instance was:

aws --profile=china --region=cn-north-1 ec2 run-instances --key-name=Odd_Bloke --image-id=ami-8fcd13e2 --security-groups philroche-ssh-only

Kamal Mostafa (kamalmostafa) wrote :

Some more data points:

An m1.small instance running a Xenial AMI (with linux-aws-xenial) works fine in cn-north-1.

An m1.small instance running the same kernel works fine in us-west-2.

The Xen hypervisor version for m1.small in cn-north-1 differs from us-west-2:
us-west-2:
[ 0.000000] SMBIOS 2.7 present.
[ 0.000000] DMI: Xen HVM domU, BIOS 4.2.amazon 08/24/2006
[ 0.000000] Hypervisor detected: Xen HVM
[ 0.000000] Xen version 4.2.
cn-north-1:
[ 0.000000] SMBIOS 2.4 present.
[ 0.000000] DMI: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
[ 0.000000] Hypervisor detected: Xen
[ 0.000000] Xen version 3.4.

Changed in linux-aws (Ubuntu Bionic):
assignee: nobody → Kamal Mostafa (kamalmostafa)
Changed in linux-aws (Ubuntu Bionic):
status: New → In Progress
Changed in linux (Ubuntu Bionic):
assignee: nobody → Kamal Mostafa (kamalmostafa)
status: New → In Progress
Kamal Mostafa (kamalmostafa) wrote :

This is documented and fixed by mainline commit:

commit d1ecfa9d1f402366b1776fbf84e635678a51414f
Author: van der Linden, Frank <email address hidden>
Date: Fri May 4 16:11:00 2018 -0400

    x86/xen: Reset VCPU0 info pointer after shared_info remap

    This patch fixes crashes during boot for HVM guests on older (pre HVM
    vector callback) Xen versions. Without this, current kernels will always
    fail to boot on those Xen versions.

    Sample stack trace:

       BUG: unable to handle kernel paging request at ffffffffff200000
       IP: __xen_evtchn_do_upcall+0x1e/0x80
       PGD 1e0e067 P4D 1e0e067 PUD 1e10067 PMD 235c067 PTE 0
        Oops: 0002 [#1] SMP PTI
       Modules linked in:
       CPU: 0 PID: 512 Comm: kworker/u2:0 Not tainted 4.14.33-52.13.amzn1.x86_64
 #1
       Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
       task: ffff88002531d700 task.stack: ffffc90000480000
       RIP: 0010:__xen_evtchn_do_upcall+0x1e/0x80
       RSP: 0000:ffff880025403ef0 EFLAGS: 00010046
       RAX: ffffffff813cc760 RBX: ffffffffff200000 RCX: ffffc90000483ef0
       RDX: ffff880020540a00 RSI: ffff880023c78000 RDI: 000000000000001c
       RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
       R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
       R13: ffff880025403f5c R14: 0000000000000000 R15: 0000000000000000
       FS: 0000000000000000(0000) GS:ffff880025400000(0000) knlGS:0000000000000
000
       CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
       CR2: ffffffffff200000 CR3: 0000000001e0a000 CR4: 00000000000006f0
        Call Trace:
       <IRQ>
       do_hvm_evtchn_intr+0xa/0x10
       __handle_irq_event_percpu+0x43/0x1a0
       handle_irq_event_percpu+0x20/0x50
       handle_irq_event+0x39/0x60
       handle_fasteoi_irq+0x80/0x140
       handle_irq+0xaf/0x120
       do_IRQ+0x41/0xd0
       common_interrupt+0x7d/0x7d
       </IRQ>

    During boot, the HYPERVISOR_shared_info page gets remapped to make it work
    with KASLR. This means that any pointer derived from it needs to be
    adjusted.

    The only value that this applies to is the vcpu_info pointer for VCPU 0.
    For PV and HVM with the callback vector feature, this gets done via the
    smp_ops prepare_boot_cpu callback. Older Xen versions do not support the
    HVM callback vector, so there is no Xen-specific smp_ops set up in that
    scenario. So, the vcpu_info pointer for VCPU 0 never gets set to the proper
    value, and the first reference of it will be bad. Fix this by resetting it
    immediately after the remap.

    Signed-off-by: Frank van der Linden <email address hidden>
    Reviewed-by: Eduardo Valentin <email address hidden>
    Reviewed-by: Alakesh Haloi <email address hidden>
    Reviewed-by: Vallish Vaidyeshwara <email address hidden>
    Reviewed-by: Boris Ostrovsky <email address hidden>
    Cc: Juergen Gross <email address hidden>
    Cc: Boris Ostrovsky <email address hidden>
    Cc: <email address hidden>
    Signed-off-by: Boris Ostrovsky <email address hidden>

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1771679

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu Artful):
status: New → In Progress
assignee: nobody → Kamal Mostafa (kamalmostafa)
no longer affects: linux-aws (Ubuntu Artful)
Stefan Bader (smb) on 2018-05-23
Changed in linux (Ubuntu Bionic):
status: In Progress → Fix Committed
importance: Undecided → Medium
Changed in linux (Ubuntu Artful):
importance: Undecided → Medium
status: In Progress → Fix Committed
Brad Figg (brad-figg) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-bionic
Kamal Mostafa (kamalmostafa) wrote :

Verified fixed in Bionic kernel version 4.15.0-23.25-generic (installed on a Xenial m1.small in cn-north-1).

tags: added: verification-done-bionic
removed: verification-needed-bionic
Kamal Mostafa (kamalmostafa) wrote :

Fixed in Bionic linux-aws kernel version 4.15.0-1010.10

Changed in linux-aws (Ubuntu Bionic):
status: In Progress → Fix Committed
Brad Figg (brad-figg) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed-artful'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-artful
Kamal Mostafa (kamalmostafa) wrote :

Verified fixed in Artful kernel version 4.13.0-44.49-generic (installed on a Xenial m1.small in cn-north-1).

tags: added: verification-done-artful
removed: verification-needed-artful
tags: added: id-5afaf1e185d595101750bb7b
Launchpad Janitor (janitor) wrote :
Download full text (11.4 KiB)

This bug was fixed in the package linux - 4.15.0-23.25

---------------
linux (4.15.0-23.25) bionic; urgency=medium

  * linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)

  * arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
    - arm64: mmu: add the entry trampolines start/end section markers into
      sections.h
    - arm64: sdei: Add trampoline code for remapping the kernel

  * Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
    - ACPI: APEI: handle PCIe AER errors in separate function
    - ACPI: APEI: call into AER handling regardless of severity

  * qla2xxx: Fix page fault at kmem_cache_alloc_node() (LP: #1770003)
    - scsi: qla2xxx: Fix session cleanup for N2N
    - scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_deletion()
    - scsi: qla2xxx: Serialize session deletion by using work_lock
    - scsi: qla2xxx: Serialize session free in qlt_free_session_done
    - scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
    - scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
    - scsi: qla2xxx: Prevent relogin trigger from sending too many commands
    - scsi: qla2xxx: Fix double free bug after firmware timeout
    - scsi: qla2xxx: Fixup locking for session deletion

  * Several hisi_sas bug fixes (LP: #1768974)
    - scsi: hisi_sas: dt-bindings: add an property of signal attenuation
    - scsi: hisi_sas: support the property of signal attenuation for v2 hw
    - scsi: hisi_sas: fix the issue of link rate inconsistency
    - scsi: hisi_sas: fix the issue of setting linkrate register
    - scsi: hisi_sas: increase timer expire of internal abort task
    - scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
    - scsi: hisi_sas: fix return value of hisi_sas_task_prep()
    - scsi: hisi_sas: Code cleanup and minor bug fixes

  * [bionic] machine stuck and bonding not working well when nvmet_rdma module
    is loaded (LP: #1764982)
    - nvmet-rdma: Don't flush system_wq by default during remove_one
    - nvme-rdma: Don't flush delete_wq by default during remove_one

  * Warnings/hang during error handling of SATA disks on SAS controller
    (LP: #1768971)
    - scsi: libsas: defer ata device eh commands to libata

  * Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
    - ata: do not schedule hot plug if it is a sas host

  * ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
    ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
    - powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
    - powerpc/64s: return more carefully from sreset NMI
    - powerpc/64s: sreset panic if there is no debugger or crash dump handlers

  * fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
    - fsnotify: Fix fsnotify_mark_connector race

  * Hang on network interface removal in Xen virtual machine (LP: #1771620)
    - xen-netfront: Fix hang on device removal

  * HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
    - net: hns: Avoid action name truncation

  * Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
    - SAUCE: powerpc/perf: Fix memory allocation for...

Changed in linux (Ubuntu Bionic):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (4.3 KiB)

This bug was fixed in the package linux - 4.13.0-45.50

---------------
linux (4.13.0-45.50) artful; urgency=medium

  * linux: 4.13.0-45.50 -proposed tracker (LP: #1774124)

  * CVE-2018-3639 (x86)
    - SAUCE: Set generic SSBD feature for Intel cpus

linux (4.13.0-44.49) artful; urgency=medium

  * linux: 4.13.0-44.49 -proposed tracker (LP: #1772951)

  * CVE-2018-3639 (x86)
    - x86/cpu: Make alternative_msr_write work for 32-bit code
    - x86/cpu/AMD: Fix erratum 1076 (CPB bit)
    - x86/bugs: Fix the parameters alignment and missing void
    - KVM: SVM: Move spec control call after restore of GS
    - x86/speculation: Use synthetic bits for IBRS/IBPB/STIBP
    - x86/cpufeatures: Disentangle MSR_SPEC_CTRL enumeration from IBRS
    - x86/cpufeatures: Disentangle SSBD enumeration
    - x86/cpufeatures: Add FEATURE_ZEN
    - x86/speculation: Handle HT correctly on AMD
    - x86/bugs, KVM: Extend speculation control for VIRT_SPEC_CTRL
    - x86/speculation: Add virtualized speculative store bypass disable support
    - x86/speculation: Rework speculative_store_bypass_update()
    - x86/bugs: Unify x86_spec_ctrl_{set_guest,restore_host}
    - x86/bugs: Expose x86_spec_ctrl_base directly
    - x86/bugs: Remove x86_spec_ctrl_set()
    - x86/bugs: Rework spec_ctrl base and mask logic
    - x86/speculation, KVM: Implement support for VIRT_SPEC_CTRL/LS_CFG
    - KVM: SVM: Implement VIRT_SPEC_CTRL support for SSBD
    - x86/bugs: Rename SSBD_NO to SSB_NO
    - KVM: VMX: Expose SSBD properly to guests.

  * [Ubuntu 16.04] kernel: fix rwlock implementation (LP: #1761674)
    - SAUCE: (no-up) s390: fix rwlock implementation

  * CVE-2018-7492
    - rds: Fix NULL pointer dereference in __rds_rdma_map

  * CVE-2018-8781
    - drm: udl: Properly check framebuffer mmap offsets

  * fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
    - fsnotify: Fix fsnotify_mark_connector race

  * Kernel panic on boot (m1.small in cn-north-1) (LP: #1771679)
    - x86/xen: Reset VCPU0 info pointer after shared_info remap

  * Suspend to idle: Open lid didn't resume (LP: #1771542)
    - ACPI / PM: Do not reconfigure GPEs for suspend-to-idle

  * CVE-2018-1092
    - ext4: fail ext4_iget for root directory if unallocated

  * [SRU][Artful] using vfio-pci on a combination of cn8xxx and some PCI devices
    results in a kernel panic. (LP: #1770254)
    - PCI: Avoid bus reset if bridge itself is broken
    - PCI: Mark Cavium CN8xxx to avoid bus reset
    - PCI: Avoid slot reset if bridge itself is broken

  * Battery drains when laptop is off (shutdown) (LP: #1745646)
    - PCI / PM: Check device_may_wakeup() in pci_enable_wake()

  * perf record crash: refcount_inc assertion failed (LP: #1769027)
    - perf cgroup: Fix refcount usage
    - perf xyarray: Fix wrong processing when closing evsel fd

  * Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
    (LP: #1764194)
    - drm/i915/bios: filter out invalid DDC pins from VBT child devices

  * Fix an issue that some PCI devices get incorrectly suspended (LP: #1764684)
    - PCI / PM: Always check PME wakeup capability for runtime wakeup support

  * [SRU][Bionic/Artful] fix false positives in W...

Read more...

Changed in linux (Ubuntu Artful):
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (11.6 KiB)

This bug was fixed in the package linux-aws - 4.15.0-1010.10

---------------
linux-aws (4.15.0-1010.10) bionic; urgency=medium

  * linux-aws: 4.15.0-1010.10 -proposed tracker (LP: #1772931)

  * Switch Build-Depends: transfig to fig2dev (LP: #1770770)
    - [Config] update Build-Depends: transfig to fig2dev

  [ Ubuntu: 4.15.0-23.25 ]

  * linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)
  * arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
    - arm64: mmu: add the entry trampolines start/end section markers into
      sections.h
    - arm64: sdei: Add trampoline code for remapping the kernel
  * Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
    - ACPI: APEI: handle PCIe AER errors in separate function
    - ACPI: APEI: call into AER handling regardless of severity
  * qla2xxx: Fix page fault at kmem_cache_alloc_node() (LP: #1770003)
    - scsi: qla2xxx: Fix session cleanup for N2N
    - scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_deletion()
    - scsi: qla2xxx: Serialize session deletion by using work_lock
    - scsi: qla2xxx: Serialize session free in qlt_free_session_done
    - scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
    - scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
    - scsi: qla2xxx: Prevent relogin trigger from sending too many commands
    - scsi: qla2xxx: Fix double free bug after firmware timeout
    - scsi: qla2xxx: Fixup locking for session deletion
  * Several hisi_sas bug fixes (LP: #1768974)
    - scsi: hisi_sas: dt-bindings: add an property of signal attenuation
    - scsi: hisi_sas: support the property of signal attenuation for v2 hw
    - scsi: hisi_sas: fix the issue of link rate inconsistency
    - scsi: hisi_sas: fix the issue of setting linkrate register
    - scsi: hisi_sas: increase timer expire of internal abort task
    - scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
    - scsi: hisi_sas: fix return value of hisi_sas_task_prep()
    - scsi: hisi_sas: Code cleanup and minor bug fixes
  * [bionic] machine stuck and bonding not working well when nvmet_rdma module
    is loaded (LP: #1764982)
    - nvmet-rdma: Don't flush system_wq by default during remove_one
    - nvme-rdma: Don't flush delete_wq by default during remove_one
  * Warnings/hang during error handling of SATA disks on SAS controller
    (LP: #1768971)
    - scsi: libsas: defer ata device eh commands to libata
  * Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
    - ata: do not schedule hot plug if it is a sas host
  * ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
    ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
    - powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
    - powerpc/64s: return more carefully from sreset NMI
    - powerpc/64s: sreset panic if there is no debugger or crash dump handlers
  * fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
    - fsnotify: Fix fsnotify_mark_connector race
  * Hang on network interface removal in Xen virtual machine (LP: #1771620)
    - xen-netfront: Fix hang on device removal
  * HiSilicon HNS NIC names are t...

Changed in linux-aws (Ubuntu Bionic):
status: Fix Committed → Fix Released
Changed in linux-aws (Ubuntu):
status: New → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (11.4 KiB)

This bug was fixed in the package linux - 4.15.0-23.25

---------------
linux (4.15.0-23.25) bionic; urgency=medium

  * linux: 4.15.0-23.25 -proposed tracker (LP: #1772927)

  * arm64 SDEI support needs trampoline code for KPTI (LP: #1768630)
    - arm64: mmu: add the entry trampolines start/end section markers into
      sections.h
    - arm64: sdei: Add trampoline code for remapping the kernel

  * Some PCIe errors not surfaced through rasdaemon (LP: #1769730)
    - ACPI: APEI: handle PCIe AER errors in separate function
    - ACPI: APEI: call into AER handling regardless of severity

  * qla2xxx: Fix page fault at kmem_cache_alloc_node() (LP: #1770003)
    - scsi: qla2xxx: Fix session cleanup for N2N
    - scsi: qla2xxx: Remove unused argument from qlt_schedule_sess_for_deletion()
    - scsi: qla2xxx: Serialize session deletion by using work_lock
    - scsi: qla2xxx: Serialize session free in qlt_free_session_done
    - scsi: qla2xxx: Don't call dma_free_coherent with IRQ disabled.
    - scsi: qla2xxx: Fix warning in qla2x00_async_iocb_timeout()
    - scsi: qla2xxx: Prevent relogin trigger from sending too many commands
    - scsi: qla2xxx: Fix double free bug after firmware timeout
    - scsi: qla2xxx: Fixup locking for session deletion

  * Several hisi_sas bug fixes (LP: #1768974)
    - scsi: hisi_sas: dt-bindings: add an property of signal attenuation
    - scsi: hisi_sas: support the property of signal attenuation for v2 hw
    - scsi: hisi_sas: fix the issue of link rate inconsistency
    - scsi: hisi_sas: fix the issue of setting linkrate register
    - scsi: hisi_sas: increase timer expire of internal abort task
    - scsi: hisi_sas: remove unused variable hisi_sas_devices.running_req
    - scsi: hisi_sas: fix return value of hisi_sas_task_prep()
    - scsi: hisi_sas: Code cleanup and minor bug fixes

  * [bionic] machine stuck and bonding not working well when nvmet_rdma module
    is loaded (LP: #1764982)
    - nvmet-rdma: Don't flush system_wq by default during remove_one
    - nvme-rdma: Don't flush delete_wq by default during remove_one

  * Warnings/hang during error handling of SATA disks on SAS controller
    (LP: #1768971)
    - scsi: libsas: defer ata device eh commands to libata

  * Hotplugging a SATA disk into a SAS controller may cause crash (LP: #1768948)
    - ata: do not schedule hot plug if it is a sas host

  * ISST-LTE:pKVM:Ubuntu1804: rcu_sched self-detected stall on CPU follow by CPU
    ATTEMPT TO RE-ENTER FIRMWARE! (LP: #1767927)
    - powerpc/powernv: Handle unknown OPAL errors in opal_nvram_write()
    - powerpc/64s: return more carefully from sreset NMI
    - powerpc/64s: sreset panic if there is no debugger or crash dump handlers

  * fsnotify: Fix fsnotify_mark_connector race (LP: #1765564)
    - fsnotify: Fix fsnotify_mark_connector race

  * Hang on network interface removal in Xen virtual machine (LP: #1771620)
    - xen-netfront: Fix hang on device removal

  * HiSilicon HNS NIC names are truncated in /proc/interrupts (LP: #1765977)
    - net: hns: Avoid action name truncation

  * Ubuntu 18.04 kernel crashed while in degraded mode (LP: #1770849)
    - SAUCE: powerpc/perf: Fix memory allocation for...

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers