[Kernel-packages] [Bug 1703339] Re: Unable to install Ubuntu on the NVMe disk under VMD PCI domain
The intended use for VMD is as a PCIe storage domain, so we expect only to see root ports, switches and NVMe SSDs in the VMD domain. Linux VMD is implemented just as a PCIe host bridge driver in order to reuse existing device drivers, though, so you could theoretically connect any pci device in the domain. The drivers for those devices do not need to be aware that it is part of a VMD domain, and it does indeed work, but we don't support such usage at this time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1703339 Title: Unable to install Ubuntu on the NVMe disk under VMD PCI domain Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Bug description: It is not possible to install Ubuntu on the NVMe disk under VMD (Volume Management Device) PCI domain. The disk is not visible in the installer because VMD module is not available at this stage. I'm raising it against kernel package as I have impression VMD module must be included in linux-image dpkg package, not linux-image-extra. Please also assure VMD module gets included in initramfs by installer (if necessary). For more information about VMD please see bug 1591806. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.10.0.26.28 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: tomasz 1659 F...m pulseaudio /dev/snd/controlC0: tomasz 1659 F pulseaudio /dev/snd/timer: tomasz 1659 f pulseaudio CurrentDesktop: GNOME Date: Mon Jul 10 10:40:20 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2017-07-06 (3 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 (20170702) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic root=/dev/mapper/hostname--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.167 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703339/+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 1626679] Re: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!"
A couple issues here. The nvme driver was ported from 4.5, but the block layer was based on 4.4, so there was a mismatch in how to handle timeouts. That was this launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908 But also, there is a bug handling legacy IRQ that only affected the 4.5 version of this driver, and that was fixed in commit: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=a5229050b69cfffb690b546c357ca5a60434c0c8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626679 Title: NVMe triggering kernel panic followed by "bad: scheduling from the idle thread!" Status in linux package in Ubuntu: Triaged Bug description: On an NVMe system I'm using, Ubuntu 16.04.1 regularly seems to trigger off a kernel panic against somepart of the NVMe driver it looks like, after which the logs get filled with entries over and over again of: "bad: scheduling from the idle thread!" Here's the initial stack trace that seems to trigger off the bug: Sep 22 15:51:46 ubuntu kernel: [ 97.478175] [ cut here ] Sep 22 15:51:46 ubuntu kernel: [ 97.478185] WARNING: CPU: 13 PID: 0 at /build/linux-dcxD3m/linux-4.4.0/kernel/irq/manage.c:1438 __free_irq+0x1d2/0x280() Sep 22 15:51:46 ubuntu kernel: [ 97.478188] Trying to free IRQ 38 from IRQ context! Sep 22 15:51:46 ubuntu kernel: [ 97.478191] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ioatdma me i_me sb_edac shpchp edac_core lpc_ich mei 8250_fintek ipmi_msghandler mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr autofs4 btrfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul ixgbe crc32_pclmu l dca vxlan aesni_intel ip6_udp_tunnel udp_tunnel aes_x86_64 lrw gf128mul ptp glue_helper ahci ablk_helper pps_core cryptd nvme libahci mdio wmi fjes Sep 22 15:51:46 ubuntu kernel: [ 97.478257] CPU: 13 PID: 0 Comm: swapper/13 Not tainted 4.4.0-31-generic #50-Ubuntu Sep 22 15:51:46 ubuntu kernel: [ 97.478260] Hardware name: Oracle Corporation ORACLE SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30080100 04/13/2016 Sep 22 15:51:46 ubuntu kernel: [ 97.478263] 0286 4fea3140a01056a3 883f7f743b10 813f1143 Sep 22 15:51:46 ubuntu kernel: [ 97.478267] 883f7f743b58 81cb61f8 883f7f743b48 81081102 Sep 22 15:51:46 ubuntu kernel: [ 97.478271] 0026 883f5b2ea700 0026 Sep 22 15:51:46 ubuntu kernel: [ 97.478275] Call Trace: Sep 22 15:51:46 ubuntu kernel: [ 97.478277][] dump_stack+0x63/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478290] [] warn_slowpath_common+0x82/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478294] [] warn_slowpath_fmt+0x5c/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478299] [] ? try_to_grab_pending+0xb3/0x160 Sep 22 15:51:46 ubuntu kernel: [ 97.478302] [] __free_irq+0x1d2/0x280 Sep 22 15:51:46 ubuntu kernel: [ 97.478306] [] free_irq+0x3c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478314] [] nvme_suspend_queue+0x89/0xb0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478320] [] nvme_disable_admin_queue+0x27/0x90 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478325] [] nvme_dev_disable+0x29e/0x2c0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478330] [] ? __nvme_process_cq+0x210/0x210 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478334] [] ? dev_warn+0x6c/0x90 Sep 22 15:51:46 ubuntu kernel: [ 97.478340] [] nvme_timeout+0x110/0x1d0 [nvme] Sep 22 15:51:46 ubuntu kernel: [ 97.478344] [] ? cpumask_next_and+0x2f/0x40 Sep 22 15:51:46 ubuntu kernel: [ 97.478348] [] ? load_balance+0x18c/0x980 Sep 22 15:51:46 ubuntu kernel: [ 97.478354] [] blk_mq_rq_timed_out+0x2f/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478358] [] blk_mq_check_expired+0x4e/0x80 Sep 22 15:51:46 ubuntu kernel: [ 97.478363] [] bt_for_each+0xd8/0xe0 Sep 22 15:51:46 ubuntu kernel: [ 97.478367] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478370] [] ? blk_mq_rq_timed_out+0x70/0x70 Sep 22 15:51:46 ubuntu kernel: [ 97.478375] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 Sep 22 15:51:46 ubuntu kernel: [ 97.478379] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478383] [] blk_mq_rq_timer+0x41/0xf0 Sep 22 15:51:46 ubuntu kernel: [ 97.478389] [] call_timer_fn+0x35/0x120 Sep 22 15:51:46 ubuntu kernel: [ 97.478393] [] ? blk_mq_attempt_merge+0xb0/0xb0 Sep 22 15:51:46 ubuntu kernel: [ 97.478397] [] run_timer_softirq+0x23a/0x2f0 Sep 22 15:51:46 ubuntu kernel: [ 97.478403] []
[Kernel-packages] [Bug 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
Kamil, For your issue, this is potentially a bug specific to the 4.5 driver. We used to poll once a second, which would hide legacy irq issues during initialization, but 4.5 removed it. A patch[*] to 4.6 removed all use of legacy interrupts, and should have been applied to 4.5 stable (they were cc'ed on the mailing list). * https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=a5229050b69cfffb690b546c357ca5a60434c0c8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
Hi Kamil, It looks like the kernel issue is resolved. Your drive just appears to be in a bad state and the driver reacts accordingly. I think this launchpad's issue is resolved and should request the fix go forward. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
Thanks for the quick build! I forwarded this onto the original reporter and will send the results when I hear them. We'll get it tested though might be next week for the results due to holiday weekend. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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 1597908] Re: linux-kernel: Freeing IRQ from IRQ context
This system crashes making apport-collect not possible after the fact, though I confirm it is a bug. As the upstream nvme driver maintainer, I can recommend either which driver commits need to be reverted, or which kernel commit needs to be cherry-picked (preferring the latter :)). Here is a snippet of stack trace: <3>[51827.132142] BUG: scheduling while atomic: swapper/19/0/0x0100 <4>[51827.242686] Modules linked in: nvme binfmt_misc PlxSvc(OE) ipmi_devintf intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm irqbypass input_leds joydev sb_edac ipmi_ssif edac_core mei_me mei lpc_ich ioatdma shpchp ipmi_si ipmi_msghandler 8250_fintek acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear igb dca ptp ahci crct10dif_pclmul crc32_pclmul hid_generic mxm_wmi aesni_intel aes_x86_64 lrw gf128mul usbhid glue_helper ablk_helper pps_core cryptd hid libahci i2c_algo_bit fjes wmi <4>[51827.242743] CPU: 19 PID: 0 Comm: swapper/19 Tainted: GW OE 4.4.0-24-generic #43-Ubuntu <4>[51827.242746] Hardware name: Intel Corporation S2600WT2/S2600WT2, BIOS SE5C610.86B.11.01.0132.060620160917 06/06/2016 <4>[51827.242748] 0286 374975818f2884ca 88105de43a98 813eab23 <4>[51827.242752] 88105de56d00 88105de43aa8 810a5ceb <4>[51827.242762] 88105de43af8 818217d6 88105de43ac8 374975810013 <4>[51827.242765] Call Trace: <4>[51827.242768][] dump_stack+0x63/0x90 <4>[51827.242781] [] __schedule_bug+0x4b/0x60 <4>[51827.242788] [] __schedule+0x726/0xa30 <4>[51827.242792] [] schedule+0x35/0x80 <4>[51827.242797] [] schedule_timeout+0x129/0x270 <4>[51827.242802] [] ? trace_event_raw_event_tick_stop+0x120/0x120 <4>[51827.242807] [] msleep+0x2d/0x40 <4>[51827.242813] [] nvme_wait_ready+0x90/0x100 [nvme] <4>[51827.242818] [] nvme_disable_ctrl+0x40/0x50 [nvme] <4>[51827.242823] [] nvme_disable_admin_queue+0x8d/0x90 [nvme] <4>[51827.242828] [] nvme_dev_disable+0x29e/0x2c0 [nvme] <4>[51827.242833] [] ? __nvme_process_cq+0x200/0x200 [nvme] <4>[51827.242838] [] ? dev_warn+0x6c/0x90 <4>[51827.242843] [] nvme_timeout+0x110/0x1d0 [nvme] <4>[51827.242847] [] ? cpumask_next_and+0x2f/0x40 <4>[51827.242850] [] ? load_balance+0x18c/0x980 <4>[51827.242854] [] blk_mq_rq_timed_out+0x2f/0x70 <4>[51827.242857] [] blk_mq_check_expired+0x4e/0x80 <4>[51827.242861] [] bt_for_each+0xd8/0xe0 <4>[51827.242864] [] ? blk_mq_rq_timed_out+0x70/0x70 <4>[51827.242868] [] ? blk_mq_rq_timed_out+0x70/0x70 <4>[51827.242871] [] blk_mq_queue_tag_busy_iter+0x47/0xc0 <4>[51827.242875] [] ? blk_mq_attempt_merge+0xb0/0xb0 <4>[51827.242878] [] blk_mq_rq_timer+0x41/0xf0 <4>[51827.242882] [] call_timer_fn+0x35/0x120 <4>[51827.242885] [] ? blk_mq_attempt_merge+0xb0/0xb0 <4>[51827.242890] [] run_timer_softirq+0x23a/0x2f0 <4>[51827.242894] [] __do_softirq+0x101/0x290 <4>[51827.242899] [] irq_exit+0xa3/0xb0 <4>[51827.242902] [] smp_apic_timer_interrupt+0x42/0x50 <4>[51827.242905] [] apic_timer_interrupt+0x82/0x90 <4>[51827.242907][] ? cpuidle_enter_state+0x111/0x2b0 <4>[51827.242914] [] cpuidle_enter+0x17/0x20 <4>[51827.242918] [] call_cpuidle+0x32/0x60 <4>[51827.242921] [] ? cpuidle_select+0x13/0x20 <4>[51827.242925] [] cpu_startup_entry+0x290/0x350 <4>[51827.242929] [] start_secondary+0x154/0x190 <3>[51827.242934] bad: scheduling from the idle thread! ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1597908 Title: linux-kernel: Freeing IRQ from IRQ context Status in linux package in Ubuntu: Confirmed Bug description: It looks like the Ubuntu 16.04 took the nvme driver from 4.5 kernel, but is missing some critical block updates that it was depending on. Specifically this one moving the timeout handler to a work queue instead of a irq context timer task: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=287922eb0b186e2a5bf54fdd04b734c25c90035c This mismatch causes lots of warnings and errors during recovery from failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1597908/+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 1382221] Re: please add linux nvme block driver commit
** Tags removed: verification-needed-trusty ** Tags added: verification-done-trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382221 Title: please add linux nvme block driver commit Status in “linux” package in Ubuntu: Fix Released Status in “linux” source package in Trusty: Fix Committed Status in “linux” source package in Utopic: Fix Released Bug description: SRU Justification: [Impact] When using the NVMe driver we could potentially have a crash. [Test Case] Use the NVMe driver. [Fix] commit fb35e914b3f88cda9ee6f9d776910c35269c4ecf -- This is a bug in a linux kernel driver, I'm basing off ubuntu trusty tree: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary We need an unpstream commit from the NVMe driver to prevent a kernel crash. It's this one here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block /nvme-core.c?id=fb35e914b3f88cda9ee6f9d776910c35269c4ecf I really should have marked that commit for stable, but I'm requesting it get applied back anyway since there are people hitting this bug in the field and hoping this can be add in the next kernel update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382221/+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 1382221] [NEW] please add linux nvme block driver commit
Public bug reported: This is a bug in a linux kernel driver, I'm basing off ubuntu trusty tree: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary We need an unpstream commit from the NVMe driver to prevent a kernel crash. It's this one here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block /nvme-core.c?id=fb35e914b3f88cda9ee6f9d776910c35269c4ecf I really should have marked that commit for stable, but I'm requesting it get applied back anyway since there are people hitting this bug in the field and hoping this can be add in the next kernel update. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: trusty ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382221 Title: please add linux nvme block driver commit Status in “linux” package in Ubuntu: Incomplete Bug description: This is a bug in a linux kernel driver, I'm basing off ubuntu trusty tree: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary We need an unpstream commit from the NVMe driver to prevent a kernel crash. It's this one here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block /nvme-core.c?id=fb35e914b3f88cda9ee6f9d776910c35269c4ecf I really should have marked that commit for stable, but I'm requesting it get applied back anyway since there are people hitting this bug in the field and hoping this can be add in the next kernel update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382221/+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 1382221] Re: please add linux nvme block driver commit
We already confirmed the bug and fix upstream during 3.14 merge. I should have marked the commit for stable. I (embarrassingly) wrote the original code that committed this bug upstream, but I also wrote and committed the fix! :) ** Patch added: Fixes the bug, attaching patch committed upstream https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382221/+attachment/4238516/+files/ubuntu.patch ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1382221 Title: please add linux nvme block driver commit Status in “linux” package in Ubuntu: Confirmed Bug description: This is a bug in a linux kernel driver, I'm basing off ubuntu trusty tree: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-trusty.git;a=summary We need an unpstream commit from the NVMe driver to prevent a kernel crash. It's this one here: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block /nvme-core.c?id=fb35e914b3f88cda9ee6f9d776910c35269c4ecf I really should have marked that commit for stable, but I'm requesting it get applied back anyway since there are people hitting this bug in the field and hoping this can be add in the next kernel update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1382221/+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
