[Kernel-packages] [Bug 1683587] Re: LSI Harpoon support in megaraid_sas module
Hi even though I'm late to the party, I could offer to test the modified kernel with H330, H710 and H730. If you send me all the necessary things and provide a list of what things to look out for, then I could test these. -- 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/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Confirmed Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. There is a series of kernel patches required to support these: http://www.mail-archive.com/linux- ker...@vger.kernel.org/msg1307314.html There is also a relevant follow-up series: https://www.spinics.net/lists/linux-scsi/msg104667.html especially patches 1 and 12. The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Xenial onwards. The upstream commit is going in for 4.11, so this will need to be backported to v4.4 and v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
http://marc.info/?l=linux-fbdev=150157026614752=2 -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: Confirmed Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
I have sent a message to the mailing list. You are correct. When blacklisting the module everything is working fine again. Can you maybe also tell me how do I properly link this bug report to the mailing list? ** 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: Confirmed Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
I have attached the dmesg log from the booted Fedora and the Kernel config as requested: ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4925000/+files/dmesg.txt -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: Incomplete Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
** Attachment added: "config-4.11.11-300.fc26.x86_64" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4925001/+files/config-4.11.11-300.fc26.x86_64 -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: Incomplete Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
Yes, exactly. There is no issue with Kernel 4.10 (16.04 HWE or 17.04). Current 17.10 Kernel does not boot properly. Unfortunately there are no logs, even on persistent journald. The OS freezes after switching from initramfs to real rootfs. Any hints what logs I could try to gather to pinpoint this issue? -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: Incomplete Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
** Attachment added: "policy.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924570/+files/policy.log ** Changed in: linux (Ubuntu) Status: Incomplete => New -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: Incomplete Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
** Attachment added: "release.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924569/+files/release.log -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: Incomplete Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924550/+files/lspci-vnvn.log -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: New Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924551/+files/uname-a.log -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: New Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] Re: Sunix 2D VGA controller causes kernel panic and crash on boot
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+attachment/4924552/+files/version.log -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: New Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1707641] [NEW] Sunix 2D VGA controller causes kernel panic and crash on boot
Public bug reported: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/1707641/+attachment/4924549/+files/journal.txt -- 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/1707641 Title: Sunix 2D VGA controller causes kernel panic and crash on boot Status in linux package in Ubuntu: New Bug description: When using Sunix latest low power VGA or DVI controller (see link below) on Ubuntu 16.04, 17.04 or 17.10 with Kernel 4.11 and later cause the system to crash on boot (the system will not become reachable via network too, so I cannot extract any logs). By using a second graphics controller I was able to extract the attached kernel message from the system. The issue also occurs with the latest mainline kernel (tested up to 4.13-rc3). Sunix changed their graphics chip at some point from Volari Z11 to Silicon Motion SM750. With the older generation, which uses the Z11, everything is working. Links to the graphics controllers which were previously mentioned: http://www.sunix.com/en/product_detail.php?cid=1=2=15=1760 http://www.sunix.com/en/product_detail.php?cid=1=2=15=1766 previous generation Sunix 2D VGA controller: http://www.sunix.com.tw/product/vga0411.html When using Fedora 26 Server, which also uses Kernel 4.11+, everything is working, too. So I'm not sure, if this is actually an upstream issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1707641/+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 1704718] Re: random freeze of AMD Ryzen based workstations
I installed Kernel 4.13-rc1 on 3 workstations so far and tonight one of them froze once again, this time leaving the attached Kernel panics in the journal. ** Attachment added: "panic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4918653/+files/panic.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- 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/1704718 Title: random freeze of AMD Ryzen based workstations Status in linux package in Ubuntu: Confirmed Bug description: I'm currently looking into stability issues of several AMD Ryzen based PCs in our company using Ubuntu 16.04 HWE and 17.04. So far I was only able to find a single journal or log entry, which may be related to the problem: ->%- Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:0 val:18739 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:1 val:9897 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:3 val:229 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27 -%<- The issue appears to occur mostly after the system was running idle for a long time (e.g. several days during a weekend). When you return to the frozen system it appears to show the last image, which was displayed before the freeze. The attached files were taken from the same workstation where I was able to recover these log entries from. All systems are using the latest BIOS version available at ASUS or MSI. All memory was chosen by QVL and has already been replaced several times. Here the hardware configuration: AMD Ryzen 7 1700X or AMD Ryzen 5 1600X ASUS Prime B350M-A or MSI B350M PRO-VDH Let me know if you need any additional information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+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 1704718] Re: random freeze of AMD Ryzen based workstations
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915932/+files/journal.txt -- 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/1704718 Title: random freeze of AMD Ryzen based workstations Status in linux package in Ubuntu: Confirmed Bug description: I'm currently looking into stability issues of several AMD Ryzen based PCs in our company using Ubuntu 16.04 HWE and 17.04. So far I was only able to find a single journal or log entry, which may be related to the problem: ->%- Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:0 val:18739 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:1 val:9897 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:3 val:229 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27 -%<- The issue appears to occur mostly after the system was running idle for a long time (e.g. several days during a weekend). When you return to the frozen system it appears to show the last image, which was displayed before the freeze. The attached files were taken from the same workstation where I was able to recover these log entries from. All systems are using the latest BIOS version available at ASUS or MSI. All memory was chosen by QVL and has already been replaced several times. Here the hardware configuration: AMD Ryzen 7 1700X or AMD Ryzen 5 1600X ASUS Prime B350M-A or MSI B350M PRO-VDH Let me know if you need any additional information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+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 1704718] Re: random freeze of AMD Ryzen based workstations
** Attachment added: "policy.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915928/+files/policy.log -- 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/1704718 Title: random freeze of AMD Ryzen based workstations Status in linux package in Ubuntu: Confirmed Bug description: I'm currently looking into stability issues of several AMD Ryzen based PCs in our company using Ubuntu 16.04 HWE and 17.04. So far I was only able to find a single journal or log entry, which may be related to the problem: ->%- Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:0 val:18739 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:1 val:9897 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:3 val:229 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27 -%<- The issue appears to occur mostly after the system was running idle for a long time (e.g. several days during a weekend). When you return to the frozen system it appears to show the last image, which was displayed before the freeze. The attached files were taken from the same workstation where I was able to recover these log entries from. All systems are using the latest BIOS version available at ASUS or MSI. All memory was chosen by QVL and has already been replaced several times. Here the hardware configuration: AMD Ryzen 7 1700X or AMD Ryzen 5 1600X ASUS Prime B350M-A or MSI B350M PRO-VDH Let me know if you need any additional information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+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 1704718] Re: random freeze of AMD Ryzen based workstations
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915930/+files/version.log -- 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/1704718 Title: random freeze of AMD Ryzen based workstations Status in linux package in Ubuntu: Confirmed Bug description: I'm currently looking into stability issues of several AMD Ryzen based PCs in our company using Ubuntu 16.04 HWE and 17.04. So far I was only able to find a single journal or log entry, which may be related to the problem: ->%- Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:0 val:18739 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:1 val:9897 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:3 val:229 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27 -%<- The issue appears to occur mostly after the system was running idle for a long time (e.g. several days during a weekend). When you return to the frozen system it appears to show the last image, which was displayed before the freeze. The attached files were taken from the same workstation where I was able to recover these log entries from. All systems are using the latest BIOS version available at ASUS or MSI. All memory was chosen by QVL and has already been replaced several times. Here the hardware configuration: AMD Ryzen 7 1700X or AMD Ryzen 5 1600X ASUS Prime B350M-A or MSI B350M PRO-VDH Let me know if you need any additional information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+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 1704718] Re: random freeze of AMD Ryzen based workstations
** Attachment added: "release.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+attachment/4915929/+files/release.txt -- 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/1704718 Title: random freeze of AMD Ryzen based workstations Status in linux package in Ubuntu: Confirmed Bug description: I'm currently looking into stability issues of several AMD Ryzen based PCs in our company using Ubuntu 16.04 HWE and 17.04. So far I was only able to find a single journal or log entry, which may be related to the problem: ->%- Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:0 val:18739 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:1 val:9897 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:3 val:229 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27 -%<- The issue appears to occur mostly after the system was running idle for a long time (e.g. several days during a weekend). When you return to the frozen system it appears to show the last image, which was displayed before the freeze. The attached files were taken from the same workstation where I was able to recover these log entries from. All systems are using the latest BIOS version available at ASUS or MSI. All memory was chosen by QVL and has already been replaced several times. Here the hardware configuration: AMD Ryzen 7 1700X or AMD Ryzen 5 1600X ASUS Prime B350M-A or MSI B350M PRO-VDH Let me know if you need any additional information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+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 1704718] [NEW] random freeze of AMD Ryzen based workstations
Public bug reported: I'm currently looking into stability issues of several AMD Ryzen based PCs in our company using Ubuntu 16.04 HWE and 17.04. So far I was only able to find a single journal or log entry, which may be related to the problem: ->%- Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:0 val:18739 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:1 val:9897 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:3 val:229 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27 -%<- The issue appears to occur mostly after the system was running idle for a long time (e.g. several days during a weekend). When you return to the frozen system it appears to show the last image, which was displayed before the freeze. The attached files were taken from the same workstation where I was able to recover these log entries from. All systems are using the latest BIOS version available at ASUS or MSI. All memory was chosen by QVL and has already been replaced several times. Here the hardware configuration: AMD Ryzen 7 1700X or AMD Ryzen 5 1600X ASUS Prime B350M-A or MSI B350M PRO-VDH Let me know if you need any additional information. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1704718/+attachment/4915927/+files/lspci-vnvn.log -- 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/1704718 Title: random freeze of AMD Ryzen based workstations Status in linux package in Ubuntu: Confirmed Bug description: I'm currently looking into stability issues of several AMD Ryzen based PCs in our company using Ubuntu 16.04 HWE and 17.04. So far I was only able to find a single journal or log entry, which may be related to the problem: ->%- Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:0 val:18739 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:1 val:9897 Jul 17 06:03:24 workstation kernel: BUG: Bad rss-counter state mm:94692f171f00 idx:3 val:229 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_ptes on freeing mm: 496 Jul 17 06:03:24 workstation kernel: BUG: non-zero nr_pmds on freeing mm: 27 -%<- The issue appears to occur mostly after the system was running idle for a long time (e.g. several days during a weekend). When you return to the frozen system it appears to show the last image, which was displayed before the freeze. The attached files were taken from the same workstation where I was able to recover these log entries from. All systems are using the latest BIOS version available at ASUS or MSI. All memory was chosen by QVL and has already been replaced several times. Here the hardware configuration: AMD Ryzen 7 1700X or AMD Ryzen 5 1600X ASUS Prime B350M-A or MSI B350M PRO-VDH Let me know if you need any additional information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1704718/+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 1626894] Re: nvme drive probe failure
Thanks everyone for your quick response and fix of the problem! I can also confirm that Kamal's Kernel works. $ cat /proc/version Linux version 4.4.0-41-generic (root@gomeisa) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) ) #61~lp1626894KamalPatched SMP Mon Sep 26 19:28:58 UTC 2016 $ ls /dev/nvme* /dev/nvme0 /dev/nvme0n1 /dev/nvme0n1p1 /dev/nvme0n1p2 /dev/nvme0n1p3 /dev/nvme1 /dev/nvme1n1 /dev/nvme1n1p1 /dev/nvme1n1p2 /dev/nvme1n1p3 -- 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/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1626894] Re: nvme drive probe failure
Sorry for the late respond, I didn't have access to the hardware during the weekend. I've just tested both kernels and can confirm, that the second one works correctly: ->%- root@Ubuntu-1604-xenial-64-minimal ~ # uname -a Linux Ubuntu-1604-xenial-64-minimal 4.4.0-40-generic #60~lp1626894Commit30d6592Reverted SMP Fri Sep 23 17:06:33 UTC 2 x86_64 x86_64 x86_64 GNU/Linux root@Ubuntu-1604-xenial-64-minimal ~ # ls /dev/nvme* /dev/nvme0 /dev/nvme0n1 /dev/nvme1 /dev/nvme1n1 -%<- Let me know, if you need any additional testing. -- 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/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1626894] Re: nvme drive probe failure
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746845/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1626894] Re: nvme drive probe failure
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746844/+files/uname-a.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1626894] Re: nvme drive probe failure
** Attachment added: "release.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746843/+files/release.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1626894] Re: nvme drive probe failure
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746841/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1626894] Re: nvme drive probe failure
** Attachment added: "policy.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1626894/+attachment/4746842/+files/policy.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626894/+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 1626894] [NEW] nvme drive probe failure
Public bug reported: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource[1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu -%<- ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1626894/+attachment/4746840/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1626894 Title: nvme drive probe failure Status in linux package in Ubuntu: Confirmed Bug description: After upgrading from linux-image-4.4.0-38-generic to proposed update linux-image-4.4.0-39-generic, NVMe drives are no longer working. dmesg shows a probe failure. On the previous kernel version everything is working as expected. ->%- [1.005243] Hardware name: FUJITSU D3417-B1/D3417-B1, BIOS V5.0.0.11 R1.12.0.SR.2 for D3417-B1x 04/01/2016 [1.005349] Workqueue: events nvme_remove_dead_ctrl_work [nvme] [1.005484] 0286 b6c91251 880fe6e8bce0 813f1f83 [1.005800] 880fe02150f0 c90006a7c000 880fe6e8bd00 8106bdff [1.006117] 880fe02150f0 880fe0215258 880fe6e8bd10 8106be3c [1.006433] Call Trace: [1.006509] [] dump_stack+0x63/0x90 [1.006589] [] iounmap.part.1+0x7f/0x90 [1.006668] [] iounmap+0x2c/0x30 [1.006770] [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme] [1.007048] [] nvme_remove+0xce/0xe0 [nvme] [1.007140] [] pci_device_remove+0x39/0xc0 [1.007220] [] __device_release_driver+0xa1/0x150 [1.007301] [] device_release_driver+0x23/0x30 [1.007382] [] pci_stop_bus_device+0x8a/0xa0 [1.007462] [] pci_stop_and_remove_bus_device_locked+0x1a/0x30 [1.007559] [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme] [1.007642] [] process_one_work+0x165/0x480 [1.007722] [] worker_thread+0x4b/0x4c0 [1.007801] [] ? process_one_work+0x480/0x480 [1.007881] [] kthread+0xd8/0xf0 [1.007959] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008041] [] ret_from_fork+0x3f/0x70 [1.008120] [] ? kthread_create_on_node+0x1e0/0x1e0 [1.008222] Trying to free nonexistent resource [1.008276] genirq: Flags mismatch irq 0. 0080 (nvme1q0) vs. 00015a00 (timer) [1.008281] Trying to free nonexistent resource [1.008282] nvme :02:00.0: Removing after probe failure [1.008645] Trying to free nonexistent resource [1.027213] iounmap: bad address c90006ae [1.027456] CPU: 2 PID: 86 Comm: kworker/2:1 Not tainted 4.4.0-39-generic #59-Ubuntu
