[Kernel-packages] [Bug 1817225] Re: 18.04.2 breaks xrdp
I'll maintain the following repo: https://launchpad.net/~martinx/+archive/ubuntu/xrdp-hwe-18.04 ...until Ubuntu fixes it in an LTS version, maybe 20.04? That's okay... -- 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in xrdp package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+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 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+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 1813075] Re: Line Out audio output rapidly disapears and reappears
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1813075 Title: Line Out audio output rapidly disapears and reappears Status in alsa-driver package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: Today my audio became choppy. At first I thought it was a bad audio file, but it turned out that everything I play is choppy. Then I thought that some process is clogging the CPU or IO, but it wasn't that either. After some searching, I opened sound settings and found out that Line Out audio output is rapidly disappearing and reappearing from the list. I checked the alsamixer and same thing was happening in its window. I tried to restart the computer, and the problem disappeared only to come back again after a short time. I still have my old 14.04 installation, I rebooted to that and everything worked as it should. I have never seen anything like this, I have no clue what is happening and I have no idea what to check. dmesg output showed nothing related to sound. Since it is very unusual, I have attached a video of what is going on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813075/+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 1817225] Re: 18.04.2 breaks xrdp
And here is the xrdp-0.9.9 and xorgxrdp-0.2.9 for Bionic HWE! https://launchpad.net/~martinx/+archive/ubuntu/xrdp-next Awesome Friday night! LOL -- 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in xrdp package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1817225] Re: 18.04.2 breaks xrdp
So, there is a need to rebuild xrdp against HWE 18.04. Maybe Ubuntu should provide a new binary package, let's say "xrdp- hwe-18.04" For now, I've recompiled the same xrdp from Ubuntu 18.04, on Ubuntu 18.04.2 and uploaded to my "XRP PPA", here: https://launchpad.net/~martinx/+archive/ubuntu/xrdp-hwe-18.04 To enjoy xrdp on Ubuntu 18.04 with HWE, just do: sudo add-apt-repository ppa:martinx/xrdp-hwe-18.04 sudo apt install xrdp xorgxrdp ;-) -- 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/1817225 Title: 18.04.2 breaks xrdp Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Status in xrdp package in Ubuntu: Confirmed Bug description: I have observed the following on two different computers: On both computers, running Ubuntu 18.04, I am able to install xrdp and log in remotely using a third computer via Reminna or Windows RDP client without any problems. If I do a fresh install of Ubuntu 18.04.2 and install xrdp OR if I update my working 18.04 installation by running sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04 then xrdp stops working. That is, when I login using an RDP client, I am presented with the xrdp login screen, but when I select xorg and try to login with my username and password, I see a blue screen for about a minute and then connecting to sesman ip 127.0.0.1 sesman connect ok sending login info to session manager, please wait... login successful for display 10 started connecting connection problem, giving up some problem The only difference between the working configuration and the broken one is Ubuntu 18.04 vs 18.04.2 (OR HWE installed using the above command). Out of the two computers I tried one has nvidia graphics and one has intel on-board graphics. For the nvidia computer, I tried both nvidia and nouveau drivers to no avail. Not sure if this is a problem with xrdp or xorg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rushik 4016 F pulseaudio /dev/snd/controlC1: rushik 4016 F pulseaudio /dev/snd/controlC0: rushik 4016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=007a0916-b97e-4f06-b096-9694f8b3085c InstallationDate: Installed on 2019-01-11 (41 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=UUID=5c3c3434-9b1d-40dd-8388-8005cf88989e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-15-generic N/A linux-backports-modules-4.18.0-15-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/04/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX Z390-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd01/04/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ390-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817225/+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 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
The same hanging behaviour in Centos-7 DVD name = CentOS-7 family = CentOS timestamp = 1543162874.22 variant = version = 7 packagedir = arch = x86_64 The card HW pics are for ex. there: https://www.amazon.de/Cablematic-PCI-zu-SuperSpeed-USB-2-Port-External/dp/B00AGGBUE8 -- 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/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+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 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
I can't boot to do logs with any kernel pci options when Etron PCI USB 3.0 is present in slot. ** 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/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+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 1822385] [NEW] hisi_sas updates for disco
Public bug reported: A number of changes for the hisi_sas driver landed upstream post-5.0 (see below). Most of these are fixes for bugs, with a few "tidy" patches intermixed. I recommend we sync up the changes for disco so that we have an established base for future changes. 0716752a7ee1d scsi: hisi_sas: Add softreset in hisi_sas_I_T_nexus_reset() 567e0d481f8a3 scsi: hisi_sas: Change SERDES_CFG init value to increase reliability of HiLink 782c2c01aaa07 scsi: hisi_sas: Send HARD RESET to clear the previous affiliation of STP target port 3713f7e96cedf scsi: hisi_sas: Set PHY linkrate when disconnected 667236dc259e6 scsi: hisi_sas: print PHY RX errors count for later revision of v3 hw 87b8498eb092d scsi: hisi_sas: Fix a timeout race of driver internal and SMP IO 3271fc647898a scsi: hisi_sas: Change return variable type in phy_up_v3_hw() 00ad4b01191cc scsi: hisi_sas: Do some more tidy-up b0086632e64a0 scsi: hisi_sas: Use pci_irq_get_affinity() for v3 hw as experimental 34f56e847589b scsi: hisi_sas: Issue internal abort on all relevant queues 3d3c109d9d548 scsi: hisi_sas: change queue depth from 512 to 4096 19866cc0d12b6 scsi: hisi_sas: Add manual trigger for debugfs dump dab1bf2064600 scsi: hisi_sas: Add support for DIX feature for v3 hw f00a9ea36d566 scsi: hisi_sas: Add missing seq_printf() call in hisi_sas_show_row_32() bf34bf475233e scsi: hisi_sas: Fix to only call scsi_get_prot_op() for non-NULL scsi_cmnd 9c362dce84885 scsi: hisi_sas: Some misc tidy-up 975006dbbc543 scsi: hisi_sas: Correct memory allocation size for DQ debugfs b6e355afa007d scsi: hisi_sas: Fix losing directly attached disk when hot-plug af3e4db3d1691 scsi: hisi_sas: Reject setting programmed minimum linkrate > 1.5G 51f3b8abee279 scsi: hisi_sas: Remove unused parameter of function hisi_sas_alloc() 7e612893d2ae9 scsi: hisi_sas: remove the check of sas_dev status in hisi_sas_I_T_nexus_reset() 571f1a2632c45 scsi: hisi_sas: shutdown axi bus to avoid exception CQ returned 06c6267f0ea1d scsi: hisi_sas: send primitive NOTIFY to SSP situation only ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- 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/1822385 Title: hisi_sas updates for disco Status in linux package in Ubuntu: In Progress Bug description: A number of changes for the hisi_sas driver landed upstream post-5.0 (see below). Most of these are fixes for bugs, with a few "tidy" patches intermixed. I recommend we sync up the changes for disco so that we have an established base for future changes. 0716752a7ee1d scsi: hisi_sas: Add softreset in hisi_sas_I_T_nexus_reset() 567e0d481f8a3 scsi: hisi_sas: Change SERDES_CFG init value to increase reliability of HiLink 782c2c01aaa07 scsi: hisi_sas: Send HARD RESET to clear the previous affiliation of STP target port 3713f7e96cedf scsi: hisi_sas: Set PHY linkrate when disconnected 667236dc259e6 scsi: hisi_sas: print PHY RX errors count for later revision of v3 hw 87b8498eb092d scsi: hisi_sas: Fix a timeout race of driver internal and SMP IO 3271fc647898a scsi: hisi_sas: Change return variable type in phy_up_v3_hw() 00ad4b01191cc scsi: hisi_sas: Do some more tidy-up b0086632e64a0 scsi: hisi_sas: Use pci_irq_get_affinity() for v3 hw as experimental 34f56e847589b scsi: hisi_sas: Issue internal abort on all relevant queues 3d3c109d9d548 scsi: hisi_sas: change queue depth from 512 to 4096 19866cc0d12b6 scsi: hisi_sas: Add manual trigger for debugfs dump dab1bf2064600 scsi: hisi_sas: Add support for DIX feature for v3 hw f00a9ea36d566 scsi: hisi_sas: Add missing seq_printf() call in hisi_sas_show_row_32() bf34bf475233e scsi: hisi_sas: Fix to only call scsi_get_prot_op() for non-NULL scsi_cmnd 9c362dce84885 scsi: hisi_sas: Some misc tidy-up 975006dbbc543 scsi: hisi_sas: Correct memory allocation size for DQ debugfs b6e355afa007d scsi: hisi_sas: Fix losing directly attached disk when hot-plug af3e4db3d1691 scsi: hisi_sas: Reject setting programmed minimum linkrate > 1.5G 51f3b8abee279 scsi: hisi_sas: Remove unused parameter of function hisi_sas_alloc() 7e612893d2ae9 scsi: hisi_sas: remove the check of sas_dev status in hisi_sas_I_T_nexus_reset() 571f1a2632c45 scsi: hisi_sas: shutdown axi bus to avoid exception CQ returned 06c6267f0ea1d scsi: hisi_sas: send primitive NOTIFY to SSP situation only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1821823] Re: No wireless networks displayed for broadcom BCM43142
** Description changed: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. - On reboot I could not see and wireless networks. I went to the + On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. - ProblemType: Bug - DistroRelease: Ubuntu 19.04 + ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: dad1060 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: - lono wireless extensions. - - enp3s0no wireless extensions. + lono wireless extensions. + + enp3s0no wireless extensions. Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 - Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) - Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 + Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) + Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: - linux-restricted-modules-5.0.0-7-generic N/A - linux-backports-modules-5.0.0-7-generic N/A - linux-firmware 1.178 + linux-restricted-modules-5.0.0-7-generic N/A + linux-backports-modules-5.0.0-7-generic N/A + linux-firmware 1.178 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no - SourcePackage: linux + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: noSourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: - + dmi.bios.date: 02/15/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.1F dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80BF dmi.board.vendor: HP dmi.board.version: 95.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: N9S73EA#ABU dmi.sys.vendor: HP ** Tags added: rls-dd-incoming -- 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/1821823 Title: No wireless networks displayed for broadcom BCM43142 Status in linux package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: New Bug description: For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1)
[Kernel-packages] [Bug 1822175] Re: i3.metal flavour type fails to respond after a reboot
I've been running 4 i3 instances running bionic, cosmic and xenial without any boot hangs using the following kernel boot parameters: nmi_watchdog=0 pcie_aspm=off nohpet These have been running now for 8+ hours, with easily over 70 reboots per instance w/o any issues. I'll try and factor out which one(s) are the ones that are required. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1822175 Title: i3.metal flavour type fails to respond after a reboot Status in linux-aws package in Ubuntu: In Progress Bug description: Series: Cosmic Instance Size: I3.Metal Region: (Default) US-WEST-2 Kernel: linux-aws During SRU testing the i3.metal instance flavor type will sometimes fail to respond after the instance is rebooted. Usually this has been seen at least 2 or 3 times during at test cycle. While rebooting an I3.Metal instance on the AWS Cloud. I observed the following crash which resulting in tearing down the instance and starting over. The instance was only restarted ~4 times at the time of this failure. [[0;32m OK [0m] Reached target Shutdown. [[0;32m OK [0m] Reached target Final Step. Starting Reboot... Stopping LVM2 metadata daemon... [[0;32m OK [0m] Stopped LVM2 metadata daemon. [ 447.340575] INFO: rcu_sched self-detected stall on CPU [ 447.340577] INFO: rcu_sched self-detected stall on CPU [ 447.340580] INFO: rcu_sched self-detected stall on CPU [ 447.340587] INFO: rcu_sched self-detected stall on CPU [ 447.340590] INFO: rcu_sched self-detected stall on CPU [ 447.340592] INFO: rcu_sched self-detected stall on CPU [ 447.340595] Uhhuh. NMI received for unknown reason 21 on CPU 0. [ 447.340599] INFO: rcu_sched self-detected stall on CPU [ 447.340602] INFO: rcu_sched self-detected stall on CPU [ 447.340606] INFO: rcu_sched self-detected stall on CPU [ 447.340614]53-...!: (43 GPs behind) idle=7ce/1/0 softirq=392/392 fqs=0 [ 447.340617] INFO: rcu_sched self-detected stall on CPU [ 447.340621] Do you have a strange power saving mode enabled? [ 447.340628]1-...!: (1 ticks this GP) idle=79e/1/0 softirq=881/881 fqs=0 [ 447.340632] INFO: rcu_sched self-detected stall on CPU [ 447.340634] INFO: rcu_sched self-detected stall on CPU [ 447.340636] INFO: rcu_sched self-detected stall on CPU [ 447.340639] INFO: rcu_sched self-detected stall on CPU [ 447.340641] INFO: rcu_sched self-detected stall on CPU [ 447.340644] INFO: rcu_sched self-detected stall on CPU [ 447.340647] INFO: rcu_sched self-detected stall on CPU The full log can be seen in the attached file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1822175/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power
Is there a way to test this patch with the 418 driver? I have an RTX 2070, which is not supported by the 390 driver, but I'd really like my battery life back. When I try to follow the instructions from the report, but replacing 390 with 418, it doesn't work (predictably). $ sudo apt install nvidia-driver-418/bionic-proposed gdm3/bionic- proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic- proposed nvidia-settings/bionic-proposed libnvidia-gl-418/bionic- proposed libnvidia-compute-418/bionic-proposed libnvidia-decode-418 /bionic-proposed libnvidia-encode-418/bionic-proposed libnvidia-ifr1-418 /bionic-proposed libnvidia-fbc1-418/bionic-proposed Reading package lists... Done Building dependency tree Reading state information... Done E: Release 'bionic-proposed' for 'nvidia-driver-418' was not found E: Release 'bionic-proposed' for 'nvidia-prime' was not found E: Release 'bionic-proposed' for 'nvidia-settings' was not found E: Release 'bionic-proposed' for 'libnvidia-gl-418' was not found E: Release 'bionic-proposed' for 'libnvidia-compute-418' was not found E: Release 'bionic-proposed' for 'libnvidia-decode-418' was not found E: Release 'bionic-proposed' for 'libnvidia-encode-418' was not found E: Release 'bionic-proposed' for 'libnvidia-ifr1-418' was not found E: Release 'bionic-proposed' for 'libnvidia-fbc1-418' was not found It may be worth noting that nvidia-prime and nvidia-settings are also not found, even though their names don't include the driver version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1778011 Title: SRU: PRIME Power Saving mode draws too much power Status in HWE Next: New Status in gdm3 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in sddm package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in gdm3 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in sddm source package in Bionic: Confirmed Status in ubuntu-drivers-common source package in Bionic: Fix Released Bug description: SRU Request: [Impact] Relying on the nouveau driver and on the vga switcheroo (to get around a change in systemd LP: #1777099) caused increased power consumption, and slowed down the switching process. Furthermore, if the main X/Xwayland session was started by Gdm when the nvidia driver was loaded, the session will keep the nvidia module loaded, and prevent the system from switching off the dGPU. Also, the nouveau driver will be loaded, if nvidia is not, and this can cause problems to unsupported NVIDIA GPUs. The solution involves the following changes: 1) Solving the problem in systemd (LP: #1777099) 2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia modules, and to allow the PCI device to sleep. 3) Making a slight change to the current patch in Gdm, used to call the PRIME scripts before and after a Gdm session (so that gpu-manager gets actually called on log out) 4) Adding code in gpu-manager to kill the main X/Xwayland session on log out, if the session is preventing us from unloading the nvidia driver. A new X/Xwayland session will be created after unload the module. 5) Removing the systemd service that loads nouveau from the nvidia packages. [Test Case] 1) Enable the -proposed repository, and install the new "ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 * 2) Make sure the nvidia packages are installed, and enable performance mode (if it is already enabled, call "sudo prime-select intel" first): sudo prime-select nvidia 3) Restart your computer and attach your /var/log/gpu-manager.log. see if the system boots correctly. If unsure, please attach your /var/log /gpu-manager.log and /var/log/Xorg.0.log 4) Select power saving mode: sudo prime-select intel 5) Log out and log back in 6) Check if the nvidia driver is still loaded: lsmod | grep nvidia [Regression Potential] Low, as hybrid graphics support does not work correctly, and the changes only affect this use case. _ * Steps to test the updates: 1) Enable the bionic-proposed repositories 2) Create /etc/apt/preferences.d/proposed-updates with the following content: Package: * Pin: release a=bionic-proposed Pin-Priority: 400 3) Update the list of packages: sudo apt-get update 4) Install the packages from -proposed using the following command: sudo apt install
[Kernel-packages] [Bug 1578650] Re: Lenovo X1 Carbon 4th freezes after suspend-resume
Is anyone still impacted by this bug wit later Ubuntu-4.4.0-*-generic kernel ? -- 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/1578650 Title: Lenovo X1 Carbon 4th freezes after suspend-resume Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: I have a Lenovo X1 Carbon 4th generation and a fresh 16.04 LTS installation. The machine always freezes after suspend and resume. Sometimes the freeze happens a few seconds after resuming, so that I have been able to capture the dmesg errors, see below. To me it seems like the same bug as in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1570484 but I'm filing a separate bug as instructed in https://help.ubuntu.com/community/ReportingBugs. Dmesg log: [ 377.341710] [ cut here ] [ 377.341734] kernel BUG at /build/linux-Ay7j_C/linux-4.4.0/mm/rmap.c:411! [ 377.341758] invalid opcode: [#2] SMP [ 377.341775] Modules linked in: ctr ccm rfcomm bnep nls_iso8859_1 arc4 intel_rapl x86_pkg_temp_thermal intel_powerclam p snd_soc_skl snd_hda_codec_hdmi acer_wmi snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_conexant sparse_keymap snd_hda_ codec_generic snd_soc_sst_ipc coretemp snd_soc_sst_dsp snd_soc_core kvm snd_compress ac97_bus snd_pcm_dmaengine dw_dmac_ core irqbypass snd_hda_intel input_leds snd_hda_codec iwlmvm joydev snd_hda_core mac80211 snd_hwdep serio_raw snd_pcm uv cvideo videobuf2_vmalloc videobuf2_memops qcserial cdc_mbim cdc_wdm usb_wwan iwlwifi cdc_ncm videobuf2_v4l2 usbnet usbse rial mii videobuf2_core rtsx_pci_ms v4l2_common cfg80211 videodev memstick media btusb snd_seq_midi btrtl snd_seq_midi_e vent thinkpad_acpi btbcm btintel nvram bluetooth snd_rawmidi mei_me shpchp mei snd_seq snd_seq_device [ 377.342074] snd_timer snd soundcore mac_hid parport_pc ppdev lp parport autofs4 drbg ansi_cprng algif_skcipher af_al g dm_crypt crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc aesni_intel aes_x86_64 lrw i915_bpo gf128mul glue_helper ablk_he lper cryptd intel_ips psmouse e1000e i2c_algo_bit drm_kms_helper ptp syscopyarea pps_core sysfillrect sysimgblt fb_sys_f ops nvme drm rtsx_pci wmi video fjes [ 377.342209] CPU: 1 PID: 5361 Comm: systemd-udevd Tainted: G D 4.4.0-21-generic #37-Ubuntu [ 377.342234] Hardware name: LENOVO 20FB0043MS/20FB0043MS, BIOS N1FET37W (1.11 ) 03/15/2016 [ 377.342256] task: 8803b7958000 ti: 88040b654000 task.ti: 88040b654000 [ 377.342277] RIP: 0010:[] [] unlink_anon_vmas+0x17f/0x1f0 [ 377.342304] RSP: 0018:88040b657d58 EFLAGS: 00010202 [ 377.342318] RAX: 88040d26ddb0 RBX: 88040b4c1e00 RCX: 00018047 [ 377.342337] RDX: 001a RSI: ea00102d3040 RDI: 880035132c80 [ 377.342356] RBP: 88040b657d90 R08: 0b4c1d01 R09: 00018047 [ 377.342375] R10: 88040b4c1dc0 R11: 88040b4c1e20 R12: 88040b4c1e00 [ 377.342394] R13: 88040d26ddb0 R14: 88040d26ddc0 R15: 880035132c80 [ 377.342414] FS: () GS:88042144() knlGS: [ 377.342435] CS: 0010 DS: ES: CR0: 80050033 [ 377.342451] CR2: 55d1d1b6f160 CR3: 00040b67d000 CR4: 003406e0 [ 377.342470] DR0: DR1: DR2: [ 377.342489] DR3: DR6: fffe0ff0 DR7: 0400 [ 377.342508] Stack: [ 377.342514] 811c4002 88040d26dd48 88040d26de10 7f62d4277000 [ 377.342539] 88040b657de8 88040d26dd48 88040b657dd0 [ 377.342562] 811bd1b1 88040901a1c0 [ 377.342586] Call Trace: [ 377.342594] [] ? __remove_shared_vm_struct+0x32/0x40 [ 377.342615] [] free_pgtables+0xa1/0x120 [ 377.342630] [] exit_mmap+0xc1/0x170 [ 377.342646] [] mmput+0x57/0x130 [ 377.342661] [] do_exit+0x27d/0xae0 [ 377.342676] [] do_group_exit+0x43/0xb0 [ 377.342691] [] SyS_exit_group+0x14/0x20 [ 377.342710] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ 377.342727] Code: 48 89 43 18 e8 43 06 02 00 49 8b 44 24 10 49 8d 54 24 10 48 83 e8 10 49 39 d6 74 2f 49 8b 7c 24 08 4c 89 e3 8b 57 34 85 d2 74 9b <0f> 0b e8 ba fd ff ff eb 9b 48 8b 45 d0 45 31 e4 48 8b 80 88 00 [ 377.342833] RIP [] unlink_anon_vmas+0x17f/0x1f0 [ 377.342852] RSP [ 377.342863] ---[ end trace 89ca45209ebd1854 ]--- [ 377.342864] BUG: unable to handle kernel NULL pointer dereference at 0008 [ 377.342866] IP: [] anon_vma_interval_tree_remove+0x133/0x250 [ 377.342867] PGD 0 [ 377.342868] Oops: [#3] SMP [ 377.342888] Modules linked in: ctr ccm rfcomm bnep nls_iso8859_1 arc4 intel_rapl x86_pkg_temp_thermal intel_powerclam p snd_soc_skl
[Kernel-packages] [Bug 1795857] Re: enable CONFIG_DRM_BOCHS
What was the host system (ie: what version of qemu)? I want to be sure this works going back as far as we support (so, trusty hosts). -- 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/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1821936] Re: No sound output on Zen AIO 27 Z272SD_Z272SD
Added this and rebooted, did not help at all. No sound. -- 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/1821936 Title: No sound output on Zen AIO 27 Z272SD_Z272SD Status in linux package in Ubuntu: Confirmed Bug description: I find this to be an issue with current LTS 18.04's latest 4.19 kernel. I tested this on mainline 4.20 and 5.0 kernels as well. No audio because ALC274 not properly loaded for use, so no audio output. A related card had a similar bug, which was fixed, and may be of use in resolving this one: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485 # cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC274 Codec: Intel Kabylake HDMI # cat /proc/asound/card0/pcm0c/info card: 0 device: 0 subdevice: 0 stream: CAPTURE id: ALC274 Analog name: ALC274 Analog subname: subdevice #0 class: 0 subclass: 0 subdevices_count: 1 subdevices_avail: 0 aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC274 Analog [ALC274 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 d# hwinfo --sound 21: PCI 1f.3: 0403 Audio device [Created at pci.378] Unique ID: nS1_.WnojYJLVCm0 SysFS ID: /devices/pci:00/:00:1f.3 SysFS BusID: :00:1f.3 Hardware Class: sound Model: "Intel Audio device" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0xa348 SubVendor: pci 0x1043 "ASUSTeK Computer Inc." SubDevice: pci 0x31d0 Revision: 0x10 Driver: "snd_hda_intel" Driver Modules: "snd_hda_intel" Memory Range: 0xdd398000-0xdd39bfff (rw,non-prefetchable) Memory Range: 0xdd10-0xdd1f (rw,non-prefetchable) IRQ: 145 (663 events) Module Alias: "pci:v8086dA348sv1043sd31D0bc04sc03i80" Driver Info #0: Driver Status: snd_hda_intel is active Driver Activation Cmd: "modprobe snd_hda_intel" Config Status: cfg=new, avail=yes, need=no, active=unknown --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1903 F pulseaudio derek 2464 F pulseaudio DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-23 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: ASUSTeK COMPUTER INC. Zen AIO 27 Z272SD_Z272SD NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=a3d569a1-6262-4609-b2f5-199dbabf57cb ro quiet splash ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: bionic Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/26/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Z272SD.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Z272SD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 13 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrZ272SD.300:bd09/26/2018:svnASUSTeKCOMPUTERINC.:pnZenAIO27Z272SD_Z272SD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnZ272SD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct13:cvr1.0: dmi.product.family: Zen AIO dmi.product.name: Zen AIO 27 Z272SD_Z272SD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1814308] Re: amdgpu with mst WARNING on blanking
booted both 4.15.0-47.50 and 4.18.0-17.18 kernels; blanked screen for both kernels, and after unblanking checked dmesg; the kernel warnings were not shown. ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-cosmic -- 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/1814308 Title: amdgpu with mst WARNING on blanking Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [impact] The amdgpu driver, when configured with MST monitors (i.e. displayport "daisy-chaining"), encounters a WARNING when blanking - such as when the display(s) are put to sleep after idle timeout. [test case] on a system with a amd gpu using the amdgpu driver, that is capable and configured for displayport mst (with multiple dp daisy chained monitors), blank the screen and then wake up the screen. This will be logged: [drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries - dce110_stream_encoder_dp_blank line:944 [ cut here ] WARNING: CPU: 0 PID: 2201 at /var/lib/dkms/amdgpu/18.50-690240/build/amd/amdgpu/../display/dc/dc_helper.c:249 generic_reg_wait+0xe7/0x160 [amdgpu] Call Trace: dce110_stream_encoder_dp_blank+0x11c/0x180 [amdgpu] core_link_disable_stream+0x40/0x230 [amdgpu] ? generic_reg_update_ex+0xdb/0x130 [amdgpu] dce110_reset_hw_ctx_wrap+0xb7/0x1f0 [amdgpu] dce110_apply_ctx_to_hw+0x30/0x430 [amdgpu] ? dce110_apply_ctx_for_surface+0x206/0x260 [amdgpu] dc_commit_state+0x2ba/0x4d0 [amdgpu] amdgpu_dm_atomic_commit_tail+0x297/0xd70 [amdgpu] ? amdgpu_bo_pin_restricted+0x58/0x260 [amdgpu] ? wait_for_completion_timeout+0x1f/0x120 ? wait_for_completion_interruptible+0x1c/0x160 commit_tail+0x3d/0x60 [drm_kms_helper] drm_atomic_helper_commit+0xf6/0x100 [drm_kms_helper] drm_atomic_connector_commit_dpms+0xe5/0xf0 [drm] drm_mode_obj_set_property_ioctl+0x14f/0x250 [drm] drm_mode_connector_property_set_ioctl+0x2e/0x40 [drm] drm_ioctl+0x1e0/0x430 [drm] ? drm_mode_connector_set_obj_prop+0x70/0x70 [drm] ? ep_read_events_proc+0xb0/0xb0 ? ep_scan_ready_list.constprop.18+0x1e6/0x1f0 ? timerqueue_add+0x52/0x80 amdgpu_drm_ioctl+0x49/0x80 [amdgpu] do_vfs_ioctl+0x90/0x5f0 SyS_ioctl+0x74/0x80 do_syscall_64+0x74/0x140 entry_SYSCALL_64_after_hwframe+0x3d/0xa2 ---[ end trace 3ed7b77a97d60f72 ]--- [regression potential] this modifies the sequence of actions during link disabling, so any regressions would appear at that time. [other info] this is from upstream 8c9d90eebd23b6d40ddf4ce5df5ca2b932336a06 this is included in disco from bug 1812427 this is needed in bionic and cosmic the xenial kernel does not (reliably) support dp mst, so this is not needed there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814308/+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 1822363] Missing required logs.
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 1822363 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 ** Tags added: bionic -- 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/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Incomplete Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+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 1820363] Re: NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19
What Firmware does Your card have? There are many versions online and some of them are for Motherboards only (has different config for chips mounted on MB embedded chipset than for expansion card PCI/PCI_E). -- 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/1820363 Title: NEC/Renesas PCI USB3 Cards (uPD720201) Host halt failed, -19 Status in linux package in Ubuntu: Incomplete Bug description: Hello, Using Ubuntu installation media (ubuntu-18.04.2-server-amd64.iso / ubuntu-18.04.[1-2]-live-server-amd64.iso / Ubuntu Live 18.04.2 iso / Ubuntu Mate Live Ubuntu Live 18.04.[1-2] iso) Startup is hanging with : [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 I'm facing exactly the same bug as these one: https://www.mail-archive.com/linux-usb@vger.kernel.org/msg102138.html https://bugs.gentoo.org/show_bug.cgi?id=612704 I installed Ubuntu Server 18.04.2 without the PCI card without trouble and then reinserted the PCI Card computer never start always hanging at the same steps as above. I managed to start only once time with the PCI card plugged by adding "pci=nomsi" to the kernel command line using an Ubuntu Mate Live media with persistence and had this output: [0.214796] pci :0d:00.0: [1912:0014] type 00 class 0x0c0330 [0.215620] pci :0d:00.0: reg 0x10: [mem 0xfdbf-0xfdbf1fff 64bit] [0.219160] pci :0d:00.0: PME# supported from D0 D3hot D3cold [8.041967] xhci_hcd :0d:00.0: Resetting [9.062082] xhci_hcd :0d:00.0: timed out waiting for pending transaction; performing function level reset anyway [ 10.406071] xhci_hcd :0d:00.0: not ready 1123ms after FLR; waiting [ 11.462075] xhci_hcd :0d:00.0: not ready 2147ms after FLR; waiting [ 13.542072] xhci_hcd :0d:00.0: not ready 4195ms after FLR; waiting [ 17.894085] xhci_hcd :0d:00.0: not ready 8291ms after FLR; waiting [ 26.342086] xhci_hcd :0d:00.0: not ready 16483ms after FLR; waiting [ 44.006072] xhci_hcd :0d:00.0: not ready 32867ms after FLR; waiting [ 78.822072] xhci_hcd :0d:00.0: not ready 65635ms after FLR; giving up [ 79.222070] xhci_hcd :0d:00.0: Refused to change power state, currently in D3 [ 79.272644] xhci_hcd :0d:00.0: xHCI Host Controller [ 79.272710] xhci_hcd :0d:00.0: new USB bus registered, assigned bus number 7 [ 79.535236] xhci_hcd :0d:00.0: Host halt failed, -19 [ 79.535291] xhci_hcd :0d:00.0: can't setup: -19 [ 79.535347] xhci_hcd :0d:00.0: USB bus 7 deregistered [ 79.78] xhci_hcd :0d:00.0: init :0d:00.0 fail, -19 It was lucky because it never worked again. PCI card was not working but computer started. Here you can find included lspci -vv, lshw and full dmesg taken from during this unique startup with the PCI Card. I tried the same PCI Card with two computers and always had the same results. Kernel is hanging with "xhci_hcd :0d:00.0: init :0d:00.0 fail, -19" and nothing more. I tried this PCI Card with a CentOS 7.3 on same computer and kernel (3.10) is starting well and PCI card is fully working. Many thanks for your assistance. I apologize if it's an already reported bug. Kind Regards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820363/+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 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 20:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1819658 Title: linux-aws: 4.4.0-1040.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 20:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819658/+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 1819711] Re: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819713 phase: Testing phase-changed: Wednesday, 20. March 2019 21:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819711 Title: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819713 phase: Testing phase-changed: Wednesday, 20. March 2019 21:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819711/+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 1819658] Re: linux-aws: 4.4.0-1040.43 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1819658 Title: linux-aws: 4.4.0-1040.43 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 20:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819658/+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 1819711] Re: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1819711 Title: linux-azure: 4.15.0-1041.45~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819713 phase: Testing phase-changed: Wednesday, 20. March 2019 21:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819711/+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 1822363] [NEW] Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
Public bug reported: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 3.0 card ej168 pci usb ** Attachment added: "Screenshot logs" https://bugs.launchpad.net/bugs/1822363/+attachment/5250744/+files/report.jpg -- 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/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: New Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+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 1813955] Re: CONFIG_TEST_BPF is disabled
Running linux 4.18.0-17-generic, loaded test_bpf, all went well. Cascardo. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1813955 Title: CONFIG_TEST_BPF is disabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Released Bug description: [Impact] Our bpf testing will fail or be skipped without notice. So, real bpf failures might end up being missed. [Test case] Both ADT and SRU will end up testing the built module. [Regression potential] Our tests will start showing real failures we don't want to miss. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813955/+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 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
I've not been able to reproduce this on my VMs, can I get access to one of these machines to figure out why it is failing and how to fix this. -- 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/1822247 Title: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Incomplete Bug description: Reproduce rate: 2 out of 3 runs This issue can be found on other arches as well, normally it will fail with the first run and pass with the second attempt. * Command: /home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke _test.sh Exit status: 1 Duration: 7.90551400185 stdout: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-13924 Date: Fri Mar 29 06:06:04 UTC 2019 Host: baltar Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019 Machine: baltar ppc64le ppc64le CPUs online: 160 CPUs total:160 Page size: 65536 Pages avail: 1904339 Pages total: 2089666 Free space: Filesystem Size Used Avail Use% Mounted on udev 61G 0 61G 0% /dev tmpfs13G 12M 13G 1% /run /dev/sda2 1.8T 11G 1.7T 1% / tmpfs64G 0 64G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs64G 0 64G 0% /sys/fs/cgroup tmpfs13G 0 13G 0% /run/user/1000 NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.31.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-13924 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-13924 creating large file /mnt/nbd-test-13924/largefile -rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-13924 removing file /mnt/nbd-test-13924/largefile unmounting /mnt/nbd-test-13924 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 694.662746] creating backing nbd image /tmp/nbd_image.img [ 695.821047] NBD device /dev/nbd0 created [ 696.271555] found nbd export [ 697.318393] starting client with NBD device /dev/nbd0 [ 697.323210] creating ext4 on /dev/nbd0 [ 697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 697.821953] checking ext4 on /dev/nbd0 [ 697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 697.925418] mounted on /dev/nbd0 [ 697.927107] creating large file /mnt/nbd-test-13924/largefile [ 698.839327] removing file /mnt/nbd-test-13924/largefile [ 699.596736] unmounting /mnt/nbd-test-13924 [ 700.664881] stopping client [ 700.667573] block nbd0: NBD_DISCONNECT [ 700.667733] block nbd0: shutting down sockets [ 700.668690] nbd0: detected capacity change from 0 to 134217728 [ 700.668758] print_req_error: I/O error, dev nbd0, sector 0 [ 700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669068] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669124] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669203] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669243] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669315] ldm_validate_partition_table(): Disk read failed. [ 700.669324] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669364] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669542] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669580] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669646] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669686] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669747] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669785] Buffer I/O error on
[Kernel-packages] [Bug 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-signing Status: Confirmed => 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/1819707 Title: linux-fips: 4.15.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-signing series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Holding before Promote to Proposed phase-changed: Friday, 29. March 2019 06:21 UTC reason: promote-to-signing: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+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 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-signing Status: New => 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/1819707 Title: linux-fips: 4.15.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-signing series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Holding before Promote to Proposed phase-changed: Friday, 29. March 2019 06:21 UTC reason: promote-to-signing: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+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 1795857] Re: enable CONFIG_DRM_BOCHS
I have tested that the module loads and works fine on POWER, on a KVM guest on top of a Power8 system. -- 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/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1821863] Re: Need to add Intel CML related pci-id's
This bug was fixed in the package libdrm - 2.4.97-1ubuntu1 --- libdrm (2.4.97-1ubuntu1) disco; urgency=medium * sync-i915-pciids.diff: Sync pci-ids with the kernel. (LP: #1821863) -- Timo Aaltonen Fri, 29 Mar 2019 11:21:10 +0200 ** Changed in: libdrm (Ubuntu) Status: New => Fix Released -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1819759] Re: linux: 5.0.0-8.9 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow/promote-to-release Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1820315 (linux-hwe-edge) derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 (linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm) -- swm properties -- phase: Ready for Release phase-changed: Thursday, 21. March 2019 16:59 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-release: Pending -- ready to copy ** Tags removed: kernel-release-tracking-bug-live -- 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/1819759 Title: linux: 5.0.0-8.9 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1820315 (linux-hwe-edge) derivatives: bug 1820878 (linux-aws), bug 1820605 (linux-azure), bug 1820308 (linux-raspi2), bug 1820310 (linux-gcp), bug 1820311 (linux-kvm) -- swm properties -- phase: Ready for Release phase-changed: Thursday, 21. March 2019 16:59 UTC proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819759/+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 1821726] Re: linux-aws: 4.4.0-1079.89 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1821726 Title: linux-aws: 4.4.0-1079.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821726/+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 1821726] Re: linux-aws: 4.4.0-1079.89 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1821726 Title: linux-aws: 4.4.0-1079.89 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821726/+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 1818617] Re: [amdgpu] screen corruption when using touchpad
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress -- 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/1818617 Title: [amdgpu] screen corruption when using touchpad Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: Fix Committed Bug description: [Impact] An OEM system is suffering from screen corruption when the touchpad is used. This would be fixed by backporting these commits from 4.18: ebdef28ebbcf767 drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3) 6f752ec2c20c6a5 drm/amdgpu: Free VGA stolen memory as soon as possible. [Test case] boot a fixed kernel on the affected system, check that it doesn't suffer from the corruption [Regression potential] low, this has been upstream since 4.18, and AMD asked us to backport these To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818617/+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 1819500] Re: hisi_sas: add debugfs support
This bug was fixed in the package linux - 5.0.0-8.9 --- linux (5.0.0-8.9) disco; urgency=medium * linux: 5.0.0-8.9 -proposed tracker (LP: #1819759) * hisi_sas: add debugfs support (LP: #1819500) - scsi: hisi_sas: Create root and device debugfs directories - scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers - scsi: hisi_sas: Take debugfs snapshot for all regs - scsi: hisi_sas: Debugfs global register create file and add file operations - scsi: hisi_sas: Add debugfs for port registers - scsi: hisi_sas: Add debugfs CQ file and add file operations - scsi: hisi_sas: Add debugfs DQ file and add file operations - scsi: hisi_sas: Add debugfs IOST file and add file operations - scsi: hisi_sas: No need to check return value of debugfs_create functions - scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code - scsi: hisi_sas: Add debugfs ITCT file and add file operations * [disco] hns driver updates from 5.1 merge window (LP: #1819535) - net: hns: Use struct_size() in devm_kzalloc() - net: hns3: modify enet reinitialization interface - net: hns3: remove unused member in struct hns3_enet_ring - net: hns3: remove unnecessary hns3_adjust_tqps_num - net: hns3: reuse reinitialization interface in the hns3_set_channels - net: hns3: add interface hclge_tm_bp_setup - net: hns3: modify parameter checks in the hns3_set_channels - net: hns3: remove redundant codes in hclge_knic_setup - net: hns3: fix user configuration loss for ethtool -L - net: hns3: adjust the use of alloc_tqps and num_tqps - net: hns3: fix wrong combined count returned by ethtool -l - net: hns3: do reinitialization while ETS configuration changed - net: hns3: add HNAE3_RESTORE_CLIENT interface in enet module - net: hns3: add calling roce callback function when link status change - net: hns3: add rx multicast packets statistic - net: hns3: refactor the statistics updating for netdev - net: hns3: fix rss configuration lost problem when setting channel - net: hns3: fix for shaper not setting when TC num changes - net: hns3: fix bug of ethtool_ops.get_channels for VF - net: hns3: clear param in ring when free ring - net: hns3: Change fw error code NOT_EXEC to NOT_SUPPORTED - net: hns3: do not return GE PFC setting err when initializing - net: hns3: add ETS TC weight setting in SSU module - net: hns3: add statistics for PFC frames and MAC control frames - net: hns3: fix PFC not setting problem for DCB module - net: hns3: don't update packet statistics for packets dropped by hardware - net: hns3: clear pci private data when unload hns3 driver - net: hns3: add error handling in hclge_ieee_setets - net: hns3: fix return value handle issue for hclge_set_loopback() - net: hns3: fix broadcast promisc issue for revision 0x20 - net: hns3: After setting the loopback, add the status of getting MAC - net: hns3: do reinitialization while mqprio configuration changed - net: hns3: remove dcb_ops->map_update in hclge_dcb - net: hns3: call hns3_nic_set_real_num_queue with netdev down - net: hns3: add 8 BD limit for tx flow - net: hns3: add initialization for nic state - net: hns3: don't allow vf to enable promisc mode - net: hns3: reuse the definition of l3 and l4 header info union - net: hns3: fix VF dump register issue - net: hns3: use the correct interface to stop|open port - net: hns3: change hnae3_register_ae_dev() to int - net: hns3: only support tc 0 for VF - net: hns3: Fix NULL deref when unloading driver - net: hns3: fix netif_napi_del() not do problem when unloading - net: hns3: fix for rss result nonuniform - net: hns3: fix improper error handling in the hclge_init_ae_dev() - net: hns3: fix an issue for hclgevf_ae_get_hdev - net: hns3: stop sending keep alive msg to PF when VF is resetting - net: hns3: keep flow director state unchanged when reset - net: hns3: Check for allocation failure - net: hns3: fix a code style issue for hns3_update_new_int_gl() - net: hns3: fix an issue for hns3_update_new_int_gl - net: hns3: Modify parameter type from int to bool in set_gro_en - net: hns3: code optimization for hclge_rx_buffer_calc - net: hns3: add hclge_cmd_check_retval() to parse comman's return value - net: hns3: move some set_bit statement into hclge_prepare_mac_addr - net: hns3: fix a wrong checking in the hclge_tx_buffer_calc() - net: hns3: fix the problem that the supported port is empty - net: hns3: optimize the maximum TC macro - net: hns3: don't allow user to change vlan filter state - net: hns3: modify the upper limit judgment condition - net: hns3: MAC table entry count function increases operation 0 value protection measures - net: hns3: make function hclge_set_all_vf_rst() static - net:
[Kernel-packages] [Bug 1819759] Re: linux: 5.0.0-8.9 -proposed tracker
This bug was fixed in the package linux - 5.0.0-8.9 --- linux (5.0.0-8.9) disco; urgency=medium * linux: 5.0.0-8.9 -proposed tracker (LP: #1819759) * hisi_sas: add debugfs support (LP: #1819500) - scsi: hisi_sas: Create root and device debugfs directories - scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers - scsi: hisi_sas: Take debugfs snapshot for all regs - scsi: hisi_sas: Debugfs global register create file and add file operations - scsi: hisi_sas: Add debugfs for port registers - scsi: hisi_sas: Add debugfs CQ file and add file operations - scsi: hisi_sas: Add debugfs DQ file and add file operations - scsi: hisi_sas: Add debugfs IOST file and add file operations - scsi: hisi_sas: No need to check return value of debugfs_create functions - scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code - scsi: hisi_sas: Add debugfs ITCT file and add file operations * [disco] hns driver updates from 5.1 merge window (LP: #1819535) - net: hns: Use struct_size() in devm_kzalloc() - net: hns3: modify enet reinitialization interface - net: hns3: remove unused member in struct hns3_enet_ring - net: hns3: remove unnecessary hns3_adjust_tqps_num - net: hns3: reuse reinitialization interface in the hns3_set_channels - net: hns3: add interface hclge_tm_bp_setup - net: hns3: modify parameter checks in the hns3_set_channels - net: hns3: remove redundant codes in hclge_knic_setup - net: hns3: fix user configuration loss for ethtool -L - net: hns3: adjust the use of alloc_tqps and num_tqps - net: hns3: fix wrong combined count returned by ethtool -l - net: hns3: do reinitialization while ETS configuration changed - net: hns3: add HNAE3_RESTORE_CLIENT interface in enet module - net: hns3: add calling roce callback function when link status change - net: hns3: add rx multicast packets statistic - net: hns3: refactor the statistics updating for netdev - net: hns3: fix rss configuration lost problem when setting channel - net: hns3: fix for shaper not setting when TC num changes - net: hns3: fix bug of ethtool_ops.get_channels for VF - net: hns3: clear param in ring when free ring - net: hns3: Change fw error code NOT_EXEC to NOT_SUPPORTED - net: hns3: do not return GE PFC setting err when initializing - net: hns3: add ETS TC weight setting in SSU module - net: hns3: add statistics for PFC frames and MAC control frames - net: hns3: fix PFC not setting problem for DCB module - net: hns3: don't update packet statistics for packets dropped by hardware - net: hns3: clear pci private data when unload hns3 driver - net: hns3: add error handling in hclge_ieee_setets - net: hns3: fix return value handle issue for hclge_set_loopback() - net: hns3: fix broadcast promisc issue for revision 0x20 - net: hns3: After setting the loopback, add the status of getting MAC - net: hns3: do reinitialization while mqprio configuration changed - net: hns3: remove dcb_ops->map_update in hclge_dcb - net: hns3: call hns3_nic_set_real_num_queue with netdev down - net: hns3: add 8 BD limit for tx flow - net: hns3: add initialization for nic state - net: hns3: don't allow vf to enable promisc mode - net: hns3: reuse the definition of l3 and l4 header info union - net: hns3: fix VF dump register issue - net: hns3: use the correct interface to stop|open port - net: hns3: change hnae3_register_ae_dev() to int - net: hns3: only support tc 0 for VF - net: hns3: Fix NULL deref when unloading driver - net: hns3: fix netif_napi_del() not do problem when unloading - net: hns3: fix for rss result nonuniform - net: hns3: fix improper error handling in the hclge_init_ae_dev() - net: hns3: fix an issue for hclgevf_ae_get_hdev - net: hns3: stop sending keep alive msg to PF when VF is resetting - net: hns3: keep flow director state unchanged when reset - net: hns3: Check for allocation failure - net: hns3: fix a code style issue for hns3_update_new_int_gl() - net: hns3: fix an issue for hns3_update_new_int_gl - net: hns3: Modify parameter type from int to bool in set_gro_en - net: hns3: code optimization for hclge_rx_buffer_calc - net: hns3: add hclge_cmd_check_retval() to parse comman's return value - net: hns3: move some set_bit statement into hclge_prepare_mac_addr - net: hns3: fix a wrong checking in the hclge_tx_buffer_calc() - net: hns3: fix the problem that the supported port is empty - net: hns3: optimize the maximum TC macro - net: hns3: don't allow user to change vlan filter state - net: hns3: modify the upper limit judgment condition - net: hns3: MAC table entry count function increases operation 0 value protection measures - net: hns3: make function hclge_set_all_vf_rst() static - net:
[Kernel-packages] [Bug 1819515] Re: Disco update: v5.0.1 upstream stable release
This bug was fixed in the package linux - 5.0.0-8.9 --- linux (5.0.0-8.9) disco; urgency=medium * linux: 5.0.0-8.9 -proposed tracker (LP: #1819759) * hisi_sas: add debugfs support (LP: #1819500) - scsi: hisi_sas: Create root and device debugfs directories - scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers - scsi: hisi_sas: Take debugfs snapshot for all regs - scsi: hisi_sas: Debugfs global register create file and add file operations - scsi: hisi_sas: Add debugfs for port registers - scsi: hisi_sas: Add debugfs CQ file and add file operations - scsi: hisi_sas: Add debugfs DQ file and add file operations - scsi: hisi_sas: Add debugfs IOST file and add file operations - scsi: hisi_sas: No need to check return value of debugfs_create functions - scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code - scsi: hisi_sas: Add debugfs ITCT file and add file operations * [disco] hns driver updates from 5.1 merge window (LP: #1819535) - net: hns: Use struct_size() in devm_kzalloc() - net: hns3: modify enet reinitialization interface - net: hns3: remove unused member in struct hns3_enet_ring - net: hns3: remove unnecessary hns3_adjust_tqps_num - net: hns3: reuse reinitialization interface in the hns3_set_channels - net: hns3: add interface hclge_tm_bp_setup - net: hns3: modify parameter checks in the hns3_set_channels - net: hns3: remove redundant codes in hclge_knic_setup - net: hns3: fix user configuration loss for ethtool -L - net: hns3: adjust the use of alloc_tqps and num_tqps - net: hns3: fix wrong combined count returned by ethtool -l - net: hns3: do reinitialization while ETS configuration changed - net: hns3: add HNAE3_RESTORE_CLIENT interface in enet module - net: hns3: add calling roce callback function when link status change - net: hns3: add rx multicast packets statistic - net: hns3: refactor the statistics updating for netdev - net: hns3: fix rss configuration lost problem when setting channel - net: hns3: fix for shaper not setting when TC num changes - net: hns3: fix bug of ethtool_ops.get_channels for VF - net: hns3: clear param in ring when free ring - net: hns3: Change fw error code NOT_EXEC to NOT_SUPPORTED - net: hns3: do not return GE PFC setting err when initializing - net: hns3: add ETS TC weight setting in SSU module - net: hns3: add statistics for PFC frames and MAC control frames - net: hns3: fix PFC not setting problem for DCB module - net: hns3: don't update packet statistics for packets dropped by hardware - net: hns3: clear pci private data when unload hns3 driver - net: hns3: add error handling in hclge_ieee_setets - net: hns3: fix return value handle issue for hclge_set_loopback() - net: hns3: fix broadcast promisc issue for revision 0x20 - net: hns3: After setting the loopback, add the status of getting MAC - net: hns3: do reinitialization while mqprio configuration changed - net: hns3: remove dcb_ops->map_update in hclge_dcb - net: hns3: call hns3_nic_set_real_num_queue with netdev down - net: hns3: add 8 BD limit for tx flow - net: hns3: add initialization for nic state - net: hns3: don't allow vf to enable promisc mode - net: hns3: reuse the definition of l3 and l4 header info union - net: hns3: fix VF dump register issue - net: hns3: use the correct interface to stop|open port - net: hns3: change hnae3_register_ae_dev() to int - net: hns3: only support tc 0 for VF - net: hns3: Fix NULL deref when unloading driver - net: hns3: fix netif_napi_del() not do problem when unloading - net: hns3: fix for rss result nonuniform - net: hns3: fix improper error handling in the hclge_init_ae_dev() - net: hns3: fix an issue for hclgevf_ae_get_hdev - net: hns3: stop sending keep alive msg to PF when VF is resetting - net: hns3: keep flow director state unchanged when reset - net: hns3: Check for allocation failure - net: hns3: fix a code style issue for hns3_update_new_int_gl() - net: hns3: fix an issue for hns3_update_new_int_gl - net: hns3: Modify parameter type from int to bool in set_gro_en - net: hns3: code optimization for hclge_rx_buffer_calc - net: hns3: add hclge_cmd_check_retval() to parse comman's return value - net: hns3: move some set_bit statement into hclge_prepare_mac_addr - net: hns3: fix a wrong checking in the hclge_tx_buffer_calc() - net: hns3: fix the problem that the supported port is empty - net: hns3: optimize the maximum TC macro - net: hns3: don't allow user to change vlan filter state - net: hns3: modify the upper limit judgment condition - net: hns3: MAC table entry count function increases operation 0 value protection measures - net: hns3: make function hclge_set_all_vf_rst() static - net:
[Kernel-packages] [Bug 1819535] Re: [disco] hns driver updates from 5.1 merge window
This bug was fixed in the package linux - 5.0.0-8.9 --- linux (5.0.0-8.9) disco; urgency=medium * linux: 5.0.0-8.9 -proposed tracker (LP: #1819759) * hisi_sas: add debugfs support (LP: #1819500) - scsi: hisi_sas: Create root and device debugfs directories - scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers - scsi: hisi_sas: Take debugfs snapshot for all regs - scsi: hisi_sas: Debugfs global register create file and add file operations - scsi: hisi_sas: Add debugfs for port registers - scsi: hisi_sas: Add debugfs CQ file and add file operations - scsi: hisi_sas: Add debugfs DQ file and add file operations - scsi: hisi_sas: Add debugfs IOST file and add file operations - scsi: hisi_sas: No need to check return value of debugfs_create functions - scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code - scsi: hisi_sas: Add debugfs ITCT file and add file operations * [disco] hns driver updates from 5.1 merge window (LP: #1819535) - net: hns: Use struct_size() in devm_kzalloc() - net: hns3: modify enet reinitialization interface - net: hns3: remove unused member in struct hns3_enet_ring - net: hns3: remove unnecessary hns3_adjust_tqps_num - net: hns3: reuse reinitialization interface in the hns3_set_channels - net: hns3: add interface hclge_tm_bp_setup - net: hns3: modify parameter checks in the hns3_set_channels - net: hns3: remove redundant codes in hclge_knic_setup - net: hns3: fix user configuration loss for ethtool -L - net: hns3: adjust the use of alloc_tqps and num_tqps - net: hns3: fix wrong combined count returned by ethtool -l - net: hns3: do reinitialization while ETS configuration changed - net: hns3: add HNAE3_RESTORE_CLIENT interface in enet module - net: hns3: add calling roce callback function when link status change - net: hns3: add rx multicast packets statistic - net: hns3: refactor the statistics updating for netdev - net: hns3: fix rss configuration lost problem when setting channel - net: hns3: fix for shaper not setting when TC num changes - net: hns3: fix bug of ethtool_ops.get_channels for VF - net: hns3: clear param in ring when free ring - net: hns3: Change fw error code NOT_EXEC to NOT_SUPPORTED - net: hns3: do not return GE PFC setting err when initializing - net: hns3: add ETS TC weight setting in SSU module - net: hns3: add statistics for PFC frames and MAC control frames - net: hns3: fix PFC not setting problem for DCB module - net: hns3: don't update packet statistics for packets dropped by hardware - net: hns3: clear pci private data when unload hns3 driver - net: hns3: add error handling in hclge_ieee_setets - net: hns3: fix return value handle issue for hclge_set_loopback() - net: hns3: fix broadcast promisc issue for revision 0x20 - net: hns3: After setting the loopback, add the status of getting MAC - net: hns3: do reinitialization while mqprio configuration changed - net: hns3: remove dcb_ops->map_update in hclge_dcb - net: hns3: call hns3_nic_set_real_num_queue with netdev down - net: hns3: add 8 BD limit for tx flow - net: hns3: add initialization for nic state - net: hns3: don't allow vf to enable promisc mode - net: hns3: reuse the definition of l3 and l4 header info union - net: hns3: fix VF dump register issue - net: hns3: use the correct interface to stop|open port - net: hns3: change hnae3_register_ae_dev() to int - net: hns3: only support tc 0 for VF - net: hns3: Fix NULL deref when unloading driver - net: hns3: fix netif_napi_del() not do problem when unloading - net: hns3: fix for rss result nonuniform - net: hns3: fix improper error handling in the hclge_init_ae_dev() - net: hns3: fix an issue for hclgevf_ae_get_hdev - net: hns3: stop sending keep alive msg to PF when VF is resetting - net: hns3: keep flow director state unchanged when reset - net: hns3: Check for allocation failure - net: hns3: fix a code style issue for hns3_update_new_int_gl() - net: hns3: fix an issue for hns3_update_new_int_gl - net: hns3: Modify parameter type from int to bool in set_gro_en - net: hns3: code optimization for hclge_rx_buffer_calc - net: hns3: add hclge_cmd_check_retval() to parse comman's return value - net: hns3: move some set_bit statement into hclge_prepare_mac_addr - net: hns3: fix a wrong checking in the hclge_tx_buffer_calc() - net: hns3: fix the problem that the supported port is empty - net: hns3: optimize the maximum TC macro - net: hns3: don't allow user to change vlan filter state - net: hns3: modify the upper limit judgment condition - net: hns3: MAC table entry count function increases operation 0 value protection measures - net: hns3: make function hclge_set_all_vf_rst() static - net:
[Kernel-packages] [Bug 1807259] Re: sky2 ethernet card doesn't work after returning from suspend
This bug was fixed in the package linux - 5.0.0-8.9 --- linux (5.0.0-8.9) disco; urgency=medium * linux: 5.0.0-8.9 -proposed tracker (LP: #1819759) * hisi_sas: add debugfs support (LP: #1819500) - scsi: hisi_sas: Create root and device debugfs directories - scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers - scsi: hisi_sas: Take debugfs snapshot for all regs - scsi: hisi_sas: Debugfs global register create file and add file operations - scsi: hisi_sas: Add debugfs for port registers - scsi: hisi_sas: Add debugfs CQ file and add file operations - scsi: hisi_sas: Add debugfs DQ file and add file operations - scsi: hisi_sas: Add debugfs IOST file and add file operations - scsi: hisi_sas: No need to check return value of debugfs_create functions - scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code - scsi: hisi_sas: Add debugfs ITCT file and add file operations * [disco] hns driver updates from 5.1 merge window (LP: #1819535) - net: hns: Use struct_size() in devm_kzalloc() - net: hns3: modify enet reinitialization interface - net: hns3: remove unused member in struct hns3_enet_ring - net: hns3: remove unnecessary hns3_adjust_tqps_num - net: hns3: reuse reinitialization interface in the hns3_set_channels - net: hns3: add interface hclge_tm_bp_setup - net: hns3: modify parameter checks in the hns3_set_channels - net: hns3: remove redundant codes in hclge_knic_setup - net: hns3: fix user configuration loss for ethtool -L - net: hns3: adjust the use of alloc_tqps and num_tqps - net: hns3: fix wrong combined count returned by ethtool -l - net: hns3: do reinitialization while ETS configuration changed - net: hns3: add HNAE3_RESTORE_CLIENT interface in enet module - net: hns3: add calling roce callback function when link status change - net: hns3: add rx multicast packets statistic - net: hns3: refactor the statistics updating for netdev - net: hns3: fix rss configuration lost problem when setting channel - net: hns3: fix for shaper not setting when TC num changes - net: hns3: fix bug of ethtool_ops.get_channels for VF - net: hns3: clear param in ring when free ring - net: hns3: Change fw error code NOT_EXEC to NOT_SUPPORTED - net: hns3: do not return GE PFC setting err when initializing - net: hns3: add ETS TC weight setting in SSU module - net: hns3: add statistics for PFC frames and MAC control frames - net: hns3: fix PFC not setting problem for DCB module - net: hns3: don't update packet statistics for packets dropped by hardware - net: hns3: clear pci private data when unload hns3 driver - net: hns3: add error handling in hclge_ieee_setets - net: hns3: fix return value handle issue for hclge_set_loopback() - net: hns3: fix broadcast promisc issue for revision 0x20 - net: hns3: After setting the loopback, add the status of getting MAC - net: hns3: do reinitialization while mqprio configuration changed - net: hns3: remove dcb_ops->map_update in hclge_dcb - net: hns3: call hns3_nic_set_real_num_queue with netdev down - net: hns3: add 8 BD limit for tx flow - net: hns3: add initialization for nic state - net: hns3: don't allow vf to enable promisc mode - net: hns3: reuse the definition of l3 and l4 header info union - net: hns3: fix VF dump register issue - net: hns3: use the correct interface to stop|open port - net: hns3: change hnae3_register_ae_dev() to int - net: hns3: only support tc 0 for VF - net: hns3: Fix NULL deref when unloading driver - net: hns3: fix netif_napi_del() not do problem when unloading - net: hns3: fix for rss result nonuniform - net: hns3: fix improper error handling in the hclge_init_ae_dev() - net: hns3: fix an issue for hclgevf_ae_get_hdev - net: hns3: stop sending keep alive msg to PF when VF is resetting - net: hns3: keep flow director state unchanged when reset - net: hns3: Check for allocation failure - net: hns3: fix a code style issue for hns3_update_new_int_gl() - net: hns3: fix an issue for hns3_update_new_int_gl - net: hns3: Modify parameter type from int to bool in set_gro_en - net: hns3: code optimization for hclge_rx_buffer_calc - net: hns3: add hclge_cmd_check_retval() to parse comman's return value - net: hns3: move some set_bit statement into hclge_prepare_mac_addr - net: hns3: fix a wrong checking in the hclge_tx_buffer_calc() - net: hns3: fix the problem that the supported port is empty - net: hns3: optimize the maximum TC macro - net: hns3: don't allow user to change vlan filter state - net: hns3: modify the upper limit judgment condition - net: hns3: MAC table entry count function increases operation 0 value protection measures - net: hns3: make function hclge_set_all_vf_rst() static - net:
[Kernel-packages] [Bug 1809843] Re: sky2 ethernet card link not up after suspend
This bug was fixed in the package linux - 5.0.0-8.9 --- linux (5.0.0-8.9) disco; urgency=medium * linux: 5.0.0-8.9 -proposed tracker (LP: #1819759) * hisi_sas: add debugfs support (LP: #1819500) - scsi: hisi_sas: Create root and device debugfs directories - scsi: hisi_sas: Alloc debugfs snapshot buffer memory for all registers - scsi: hisi_sas: Take debugfs snapshot for all regs - scsi: hisi_sas: Debugfs global register create file and add file operations - scsi: hisi_sas: Add debugfs for port registers - scsi: hisi_sas: Add debugfs CQ file and add file operations - scsi: hisi_sas: Add debugfs DQ file and add file operations - scsi: hisi_sas: Add debugfs IOST file and add file operations - scsi: hisi_sas: No need to check return value of debugfs_create functions - scsi: hisi_sas: Fix type casting and missing static qualifier in debugfs code - scsi: hisi_sas: Add debugfs ITCT file and add file operations * [disco] hns driver updates from 5.1 merge window (LP: #1819535) - net: hns: Use struct_size() in devm_kzalloc() - net: hns3: modify enet reinitialization interface - net: hns3: remove unused member in struct hns3_enet_ring - net: hns3: remove unnecessary hns3_adjust_tqps_num - net: hns3: reuse reinitialization interface in the hns3_set_channels - net: hns3: add interface hclge_tm_bp_setup - net: hns3: modify parameter checks in the hns3_set_channels - net: hns3: remove redundant codes in hclge_knic_setup - net: hns3: fix user configuration loss for ethtool -L - net: hns3: adjust the use of alloc_tqps and num_tqps - net: hns3: fix wrong combined count returned by ethtool -l - net: hns3: do reinitialization while ETS configuration changed - net: hns3: add HNAE3_RESTORE_CLIENT interface in enet module - net: hns3: add calling roce callback function when link status change - net: hns3: add rx multicast packets statistic - net: hns3: refactor the statistics updating for netdev - net: hns3: fix rss configuration lost problem when setting channel - net: hns3: fix for shaper not setting when TC num changes - net: hns3: fix bug of ethtool_ops.get_channels for VF - net: hns3: clear param in ring when free ring - net: hns3: Change fw error code NOT_EXEC to NOT_SUPPORTED - net: hns3: do not return GE PFC setting err when initializing - net: hns3: add ETS TC weight setting in SSU module - net: hns3: add statistics for PFC frames and MAC control frames - net: hns3: fix PFC not setting problem for DCB module - net: hns3: don't update packet statistics for packets dropped by hardware - net: hns3: clear pci private data when unload hns3 driver - net: hns3: add error handling in hclge_ieee_setets - net: hns3: fix return value handle issue for hclge_set_loopback() - net: hns3: fix broadcast promisc issue for revision 0x20 - net: hns3: After setting the loopback, add the status of getting MAC - net: hns3: do reinitialization while mqprio configuration changed - net: hns3: remove dcb_ops->map_update in hclge_dcb - net: hns3: call hns3_nic_set_real_num_queue with netdev down - net: hns3: add 8 BD limit for tx flow - net: hns3: add initialization for nic state - net: hns3: don't allow vf to enable promisc mode - net: hns3: reuse the definition of l3 and l4 header info union - net: hns3: fix VF dump register issue - net: hns3: use the correct interface to stop|open port - net: hns3: change hnae3_register_ae_dev() to int - net: hns3: only support tc 0 for VF - net: hns3: Fix NULL deref when unloading driver - net: hns3: fix netif_napi_del() not do problem when unloading - net: hns3: fix for rss result nonuniform - net: hns3: fix improper error handling in the hclge_init_ae_dev() - net: hns3: fix an issue for hclgevf_ae_get_hdev - net: hns3: stop sending keep alive msg to PF when VF is resetting - net: hns3: keep flow director state unchanged when reset - net: hns3: Check for allocation failure - net: hns3: fix a code style issue for hns3_update_new_int_gl() - net: hns3: fix an issue for hns3_update_new_int_gl - net: hns3: Modify parameter type from int to bool in set_gro_en - net: hns3: code optimization for hclge_rx_buffer_calc - net: hns3: add hclge_cmd_check_retval() to parse comman's return value - net: hns3: move some set_bit statement into hclge_prepare_mac_addr - net: hns3: fix a wrong checking in the hclge_tx_buffer_calc() - net: hns3: fix the problem that the supported port is empty - net: hns3: optimize the maximum TC macro - net: hns3: don't allow user to change vlan filter state - net: hns3: modify the upper limit judgment condition - net: hns3: MAC table entry count function increases operation 0 value protection measures - net: hns3: make function hclge_set_all_vf_rst() static - net:
[Kernel-packages] [Bug 1816806] Re: Update ENA driver to version 2.0.3K
** Tags removed: verification-needed-bionic verification-needed-cosmic
verification-needed-xenial
** Tags added: verification-done-bionic verification-done-cosmic
verification-done-xenial
--
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/1816806
Title:
Update ENA driver to version 2.0.3K
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Cosmic:
Fix Committed
Status in linux source package in Disco:
Fix Committed
Bug description:
The following mainline commits are needed to update the Amazon ENA
driver to version 2.0.3K:
e76ad21d070f net: ena: fix crash during failed resume from hibernation
e1f1bd9bfbed net: ena: fix race between link up and device initalization
d9b8656da922 net: ena: update driver version from 2.0.2 to 2.0.3
All three commits are needed for {Xenial,Bionic,Cosmic}. Disco 4.19
already carries the first (e76a) so needs the other two.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816806/+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 1822239] Re: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta
** Package changed: ubuntu => nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1822239 Title: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: Summary: I use a Dell Precision 5530 (I+N) machine and switch to Nivida card. (The Nvidia driver installed via Additional driver of Software & Update - nvida-driver-390) Try to run glxgears and got the error - Error: couldn't get an RGB, Double-buffered visual Steps to reproduce: 1. Install the tool: $ sudo apt install mesa-utils 2. Run glxgears $ glxgears Expected result: Open up a window with an OpenGL rendering of a simple arrangement of three rotating gears. Actual result: An error returns: Error: couldn't get an RGB, Double-buffered visual Failure rate: 100% - CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b system-product-name: Precision 5530 bios-version: 1.6.0 system-manufacturer: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1822239/+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 1822239] [NEW] NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta
You have been subscribed to a public bug: Summary: I use a Dell Precision 5530 (I+N) machine and switch to Nivida card. (The Nvidia driver installed via Additional driver of Software & Update - nvida-driver-390) Try to run glxgears and got the error - Error: couldn't get an RGB, Double-buffered visual Steps to reproduce: 1. Install the tool: $ sudo apt install mesa-utils 2. Run glxgears $ glxgears Expected result: Open up a window with an OpenGL rendering of a simple arrangement of three rotating gears. Actual result: An error returns: Error: couldn't get an RGB, Double-buffered visual Failure rate: 100% - CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b system-product-name: Precision 5530 bios-version: 1.6.0 system-manufacturer: Dell Inc. ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment ce-qa-concern disco hwe-graphics -- NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta https://bugs.launchpad.net/bugs/1822239 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. -- 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 1795857] Re: enable CONFIG_DRM_BOCHS
I'm rejecting the kmod upload in the disco queue until the above comment is addressed, so we don't get into a revert war. -- 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/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker
HMAC package seems broken in this version, so we will keep it blocked in fips-proposed. ** Tags added: kernel-block-proposed -- 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/1820326 Title: linux-fips: 4.4.0-1007.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Thursday, 28. March 2019 12:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+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 1795857] Re: enable CONFIG_DRM_BOCHS
The original bug report was on PowerKVM (ppc64el qemu). In testing that it was okay to revert this wholesale in both kmod and kernel, did anyone test POWER? -- 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/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1822118] Re: Kernel Panic while rebooting cloud instance
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Status in systemd package in Ubuntu: New Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+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 1686048] Re: Touchpad not detected on Lenovo S21e-20
** Changed in: linux Status: Confirmed => Fix Released -- 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/1686048 Title: Touchpad not detected on Lenovo S21e-20 Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB OPTICAL MOUSEid=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ Lenovo EasyCamera cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=15d9 Product=0a4c Version=0111 N: Name=" USB OPTICAL MOUSE" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:15D9:0A4C.0001/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Front Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=5986 Product=0674 Version=4207 N: Name="Lenovo EasyCamera" P: Phys=usb-:00:14.0-3/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1146 F pulseaudio CurrentDesktop: KDE Date: Tue Apr 25 11:15:33 2017 InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Foxconn
[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance
Thanks Sean and Colin! I'm going to see if I can reproduce it. If I can, I do the usual investigation to see if its a regression, fixed upstream and if a bisect will help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822118 Title: Kernel Panic while rebooting cloud instance Status in linux-azure package in Ubuntu: In Progress Bug description: Description: In the event a particular Azure cloud instance is rebooted it's possible that it may never recover and the instance will break indefinitely. In My case, it was a kernel panic. See specifics below.. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I had a simple script to reboot an instance (X) amount of times, I chose 50, so the machine would power cycle by issuing a "reboot" from the terminal prompt just as a user would. Once the machine came up, it captured dmesg and other bits then rebooted again until it reached 50. After the 4th attempt, my script timed out, I took a look at the instance console log and the following displayed on the console. [ OK ] Reached target Reboot. /shutdown: error while loading shared libra[ 89.498980] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.498980] [ 89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure #13-Ubuntu [ 89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 89.508026] Call Trace: [ 89.508026] dump_stack+0x63/0x8a [ 89.508026] panic+0xe7/0x247 [ 89.508026] do_exit.cold.23+0x26/0x75 [ 89.508026] do_group_exit+0x43/0xb0 [ 89.508026] __x64_sys_exit_group+0x18/0x20 [ 89.508026] do_syscall_64+0x5a/0x110 [ 89.508026] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 89.508026] RIP: 0033:0x7f7bf0154d86 [ 89.508026] Code: Bad RIP value. [ 89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 00e7 [ 89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 7f7bf0154d86 [ 89.508026] RDX: 007f RSI: 003c RDI: 007f [ 89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: [ 89.508026] R10: 7ffd6be6974c R11: 0206 R12: 0018 [ 89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: [ 89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation range: 0x8000-0xbfff) [ 89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 [ 89.508026] ]--- this only occurred once in my testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822118/+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 1787775] Re: touchpad not working on lenovo yoga 530
And please remove the MP2 DKMS to really test the kernel. ** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Kai-Heng Feng (kaihengfeng) Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1795292] Re: ELAN469D touch pad not working
I just updated the BIOS to the latest 7VCN46WW (Jan 2019). Tried to boot without the `ivrs_ioapic[32]=00:14.0` kernel parameter, and the stock 4.18.0-16-generic kernel just wouldn't boot at all. Added the parameter back and it works. I have to note though that although the touch pad works, I cannot right click with it. Every click is interpreted as a left click. Very annoying since the keyboard doesn't have the context menu button either. -- 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/1795292 Title: ELAN469D touch pad not working Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on this Lenovo Ideapad 330S-15ARR laptop. The touch pad doesn't work in either. Some possibly relevant info from dmesg: i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy regulator i2c_designware AMDI0010:01: controller timed out ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-7-generic 4.18.0-7.8 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2086 F pulseaudio /dev/snd/pcmC1D0p: xorbit 2086 F...m pulseaudio /dev/snd/controlC0: xorbit 2086 F pulseaudio CurrentDesktop: GNOME Date: Sun Sep 30 23:14:26 2018 InstallationDate: Installed on 2018-09-20 (10 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 elan_i2c.dyndbg=+p RelatedPackageVersions: linux-restricted-modules-4.18.0-7-generic N/A linux-backports-modules-4.18.0-7-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago) dmi.bios.date: 06/08/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN22WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-09-20 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: cosmic Uname: Linux 4.19.0-041900rc6-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1795292/+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 1787775] Re: touchpad not working on lenovo yoga 530
I built kernels for Bionic, Cosmic and Disco, please test: https://people.canonical.com/~khfeng/lp1787775/ -- 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/1787775 Title: touchpad not working on lenovo yoga 530 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Confirmed Bug description: The touchpad is not working and does not show up in cat /proc/bus/input/devices on multiple kernels. I've tried the newest kernel to date (19.08.18) and a few others. The touchpad works on windows. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-08-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Package: linux (not installed) Tags: bionic Uname: Linux 4.18.3-041803-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to bionic on 2018-08-18 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+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 1796582] Re: Internal microphone not working on Lenovo Ideapad 330S-15ARR
The dumb thing is: it was working! For a while. Then I updated the BIOS to the 1/2/2019 7VCN46WW version to see if the `ivrs_ioapic` parameter was still required for the touch pad issue, and now the microphone stopped working again! :( Using the stock cosmic 4.18.0-16-generic kernel. -- 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/1796582 Title: Internal microphone not working on Lenovo Ideapad 330S-15ARR Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The internal microphone on this troublesome laptop stopped working after upgrading from Bionic to Cosmic. There is no signal from the microphone with kernel 4.18.0-7 or 4.18.0-8. This DOES work correctly with kernel 4.15.0-34 that is still present on Cosmic after the upgrade. I recommend Canonical gets this laptop for testing since a ton of stuff is troublesome on this Raven Ridge laptop. Would be a good specimen to get support for this platform improved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-8-generic 4.18.0-8.9 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: xorbit 2295 F pulseaudio /dev/snd/controlC0: xorbit 2295 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 7 12:02:45 2018 InstallationDate: Installed on 2018-09-20 (17 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81FB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-8-generic N/A linux-backports-modules-4.18.0-8-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago) dmi.bios.date: 09/05/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7WCN26WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330S-15ARR dmi.modalias: dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR: dmi.product.family: ideapad 330S-15ARR dmi.product.name: 81FB dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR dmi.product.version: Lenovo ideapad 330S-15ARR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1796582/+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 1822267] Re: [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response
The kernel boot log is listed as attached file here in case someone is interested. ** Attachment added: "RV2 Boot Log" https://bugs.launchpad.net/amd/+bug/1822267/+attachment/5250650/+files/rv2-boot-log.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: amd Status: New => 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/1822267 Title: [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response Status in amd: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Description: Raven 2 platform fails to boot on ubuntu 19.04 (disco) with kernel 5.0.0. The issue is related to a fixed patch in linux-mainline about psp response code status. In some cases, psp response status is not 0 even there is no problem while the command is submitted. Some version of PSP FW doesn't write 0 to that field. So here we would like to only print a warning instead of an error during psp initialization to avoid breaking hw_init and it doesn't return -EINVAL. Steps: 1. Install Ubuntu 19.04 daily build on AMD Raven 2 platform (reproduced with 2019.03.18 version) 2. Reboot and it fails at kernel initialization. Current patch status: A patch has already accepted in the linux mainline. (id: 466bcb75b0791ba301817cdadeed20398f2224fe) See: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=466bcb75b0791ba301817cdadeed20398f2224fe Backport status: A backport patch is available and verified. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1822267/+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 1786139] Re: [GLK/CLX] Enhanced IBRS
Disco is based on a 5.0 upstream kernel so it has enhanced IBRS support. ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released -- 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/1786139 Title: [GLK/CLX] Enhanced IBRS Status in intel: Triaged Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Description: [Impact] Future Intel CPU's like Cascade Lake and GLK+ support Enhanced IBRS. Enhanced IBRS is a H/W mitigation technique for Spectre V2 bug. So, it's important for us to make sure that all the OSV's are using this feature. The patch that enables kernel support for this feature has been taken by Thomas and it's in TIP tree. So, please back port it to all the OSV's. Please find the patch here: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/pti=706d51681d636a0c4a5ef53395ec3b803e45ed4d [Test Case] For processors that don't support Enhanced IBRS, the test is to ensure that /sys/devices/system/cpu/vulnerabilities/spectre_v2 doesn't change state after applying the patches. This will typically be the string when running on Intel processors that don't support Enhanced IBRS: "Mitigation: Full generic retpoline, IBPB, IBRS_FW" New Intel processors that do support Enhanced IBRS will display "Enhanced IBRS" in place of "Full generic retpoline" [Regression Potential] Pretty low. The patches are fairly simple and they should only affect new processors. The main concern is around the possibility of regressing IBRS support on processors that don't support Enhanced IBRS Target Kernel:TBD Target Release: 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1786139/+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 1795857] Re: enable CONFIG_DRM_BOCHS
I've send a patch for the kernel part of this request: https://lists.ubuntu.com/archives/kernel-team/2019-March/099704.html Additionally to it the kmod's "blacklist bochs-drm" entry from it's /etc/modprobe.d/blacklist-framebuffer.conf file it ships would need to get removed. With this I can successfully start VMs wit stdvga as display under QEMU and/or QEMU/KVM again. Without this it's completely broken, but note that the installation itself works, you'll only see the issues after you boot in the fresh installed system. -- 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/1795857 Title: enable CONFIG_DRM_BOCHS Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: CONFIG_DRM_BOCHS got disabled for https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648 but doing so regressed running qemu with the 'std' VGA driver, where it'd fail to start X after install, as mentioned on bug 1794280 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1795857/+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 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate - channel verification-testing: Ongoing -- testing in progress -- 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/1821724 Title: linux: 4.4.0-145.171 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+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 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/xenial/4.4.0-145.171 /xenial-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- 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/1821724 Title: linux: 4.4.0-145.171 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+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 1821713] Re: linux-raspi2: 4.4.0-1106.114 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in armhf:latest/candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1821713 Title: linux-raspi2: 4.4.0-1106.114 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821713/+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 1818811] Re: The swapfile on the Btrfs file system is not activated
I don't know if it's useful, but I paste my "/etc/fstab" configuration $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/sda2 during installation UUID=b383c3a8-39dd-4edd-98e1-0217a87d266a / btrfs defaults,noatime,compress=lzo,autodefrag,subvol=@ 0 1 # /boot/efi was on /dev/sda1 during installation UUID=76C5-B080 /boot/efi vfatumask=0077 0 1 # /home was on /dev/sda2 during installation UUID=b383c3a8-39dd-4edd-98e1-0217a87d266a /home btrfs defaults,noatime,compress=lzo,autodefrag,subvol=@home 0 2 /swapfile noneswapsw 0 0 LABEL=dati1 /media/emanu/dati btrfs defaults,compress=zstd,autodefrag 0 3 LABEL=backup /media/emanu/backup btrfs defaults,compress-force=zstd,autodefrag,nofail,noauto 0 0 -- 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/1818811 Title: The swapfile on the Btrfs file system is not activated Status in linux package in Ubuntu: Confirmed Bug description: From 5.0 kernel is implemented support for the swapfile on Btrfs (https://patchwork.kernel.org/cover/10584515/), today arrived on the repositories of Ubuntu 19.04 proposed kernel 5.0, but the swapfile is not activated. Log: mar 06 11:17:55 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:55 notebook-Lenovo-V110 swapon[517]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 swapon[916]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 swapon[1006]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanu 1744 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 11:19:52 2019 InstallationDate: Installed on 2019-01-30 (34 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5745 IMC Networks Bus 001 Device 002: ID 10c4:8105 Cygnal Integrated Products, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80TL ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-7-generic root=UUID=91fdf6c0-1b5d-4bb5-9aa4-aeb946236b8a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.177 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN46WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V110-15ISK dmi.modalias:
[Kernel-packages] [Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in i386:latest/candidate,amd64:latest/candidate + snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate channel verification-testing: Ongoing -- testing in progress -- 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/1821724 Title: linux: 4.4.0-145.171 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+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 1819692] Re: linux-oem: 4.15.0-1035.40 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Wednesday, 20. March 2019 08:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1819692 Title: linux-oem: 4.15.0-1035.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Wednesday, 20. March 2019 08:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819692/+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 1819692] Re: linux-oem: 4.15.0-1035.40 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/oem/4.15.0-1035.40/oem-4.15-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1819692 Title: linux-oem: 4.15.0-1035.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Testing phase-changed: Wednesday, 20. March 2019 08:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819692/+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 1817628] Re: Regular D-state processes impacting LXD containers
Marking X/B as verification done. The user reports the issue occurs much less often now. Apparently that environment hits some corner case or this may still be expected sometimes under memory pressure (i.e., one big shrinking operation acquired the lock and must finish). Nonetheless, the fix reduced the frequency the problem occurs, so it does address most of that and is beneficial on its own. As discussed with @klebers on IRC, in this scenario we agreed to ship the fix, and address the pending behavior (if an actual issue) with additional fixes later. cheers, Mauricio ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial -- 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/1817628 Title: Regular D-state processes impacting LXD containers Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] * Systems running under memory pressure may hit stalls in the order of seconds to minutes in systemd-logind and lxd mount operations (e.g., ZFS backend), which get stuck in D state. * The processes stuck in D state have a common stack trace, (cat /proc/PID/stack) all blocked in register_shrinker(). * The fix checks in shrink_slab() (shrinkers are called under memory pressure) for contention/usage of the semaphore used by register_shrinker() and returns early in that case. This allows the register_shrinker() callers to unblock, and not stall until the shrink operation releases that lock. [Test Case] * In a system under memory pressure, specifically having the memory shrinkers being called often and taking time to run, perform mount operations (or other operations that acquire the shrinker_rwsem semaphore). * The user who reported the problem has verified the fix in systems that exhibted the problem often (sometimes daily), and tells it resolves the problem. [Regression Potential] * Low. The fix just returns early from slab memory shrinker if there's usage/contention for 'shrinker_rwsem'. * In some scenarios, this may cause the slab memory shrinker to require more invocations to actually finish and potentially release memory, but this seems minor since other shrinkers can release memory as well, and compared to the fact that this fix allows other applications to make progress / continue to run, which would otherwise be stalled. [Other Info] * This patch is already applied in Cosmic and later (v4.16+). It is needed only in Xenial and Bionic at this time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817628/+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 1752072] Re: [Packaging] Allow overlay of config annotations
For the master kernels, the change was only a single commit which added to add support on config-check for the include file format (UBUNTU: [Packaging] config-check: Add an include directive). Since that support will be mostly used by derivatives and backports, the only verification we can do for now with these kernels is checking that these changes don't introduce any regression on config-check. ** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-cosmic verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1752072 Title: [Packaging] Allow overlay of config annotations Status in linux package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux-gcp source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-gcp source package in Cosmic: New Bug description: Currently for custom kernels, it's necessary to keep a separate annotations file that often gets out of sync with the corresponding file in debian.master/. The "debian/scripts/config-check" script can be changed to allow additional annotations files to act as overlays over the original annotations file, allowing custom kernels to override the policies just for the relevant configs. As an initial proposal, any file matching the pattern "$DEBIAN/config/*.annotations" could be considered as an overlay file and policies could be overridden on a config basis. That means that any mention to a config in the overlay file would discard all the policies for that config in the original file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752072/+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 1786013] Re: Packaging resync
** Tags removed: verification-needed-cosmic verification-needed-trusty verification-needed-xenial ** Tags added: verification-done-cosmic verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Precise: Fix Committed Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: New Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: New Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1822271] Re: Xenial update: 4.4.177 upstream stable release
Skipped (already applied for bug #1817784): "scsi: libsas: Fix rphy
phy_identifier for PHYs with end devices attached".
Skipped (already applied for CVE-2019-9213); "mm: enforce min addr even
if capable() in expand_downwards()".
Skipped (reasoning below): "scsi: libiscsi: Fix race between iscsi_xmit_task
and iscsi_complete_task".
-> Reasoning: The race seems to depend on having the locking split into
back_lock and fwd_lock. This split got introduced in v3.15 upstream but was
reverted in Xenial for bug #1517142 in 4.4.0-9.24. Without that the code which
gets modified is still holding the bigger lock, so should be safe. At least
these things should get applied together and rather with more testing.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9213
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ 4.4.177 upstream stable release
+ from git://git.kernel.org/
-4.4.177 upstream stable release
-from git://git.kernel.org/
+ The following patches were applied:
+ * ceph: avoid repeatedly adding inode to mdsc->snap_flush_list
+ * numa: change get_mempolicy() to use nr_node_ids instead of MAX_NUMNODES
+ * KEYS: allow reaching the keys quotas exactly
+ * mfd: ti_am335x_tscadc: Use PLATFORM_DEVID_AUTO while registering mfd cells
+ * mfd: twl-core: Fix section annotations on {,un}protect_pm_master
+ * mfd: db8500-prcmu: Fix some section annotations
+ * mfd: ab8500-core: Return zero in get_register_interruptible()
+ * mfd: qcom_rpm: write fw_version to CTRL_REG
+ * mfd: wm5110: Add missing ASRC rate register
+ * mfd: mc13xxx: Fix a missing check of a register-read failure
+ * net: hns: Fix use after free identified by SLUB debug
+ * MIPS: ath79: Enable OF serial ports in the default config
+ * scsi: qla4xxx: check return code of qla4xxx_copy_from_fwddb_param
+ * scsi: isci: initialize shost fully before calling scsi_add_host()
+ * MIPS: jazz: fix 64bit build
+ * isdn: i4l: isdn_tty: Fix some concurrency double-free bugs
+ * atm: he: fix sign-extension overflow on large shift
+ * leds: lp5523: fix a missing check of return value of lp55xx_read
+ * isdn: avm: Fix string plus integer warning from Clang
+ * RDMA/srp: Rework SCSI device reset handling
+ * KEYS: user: Align the payload buffer
+ * KEYS: always initialize keyring_index_key::desc_len
+ * batman-adv: fix uninit-value in batadv_interface_tx()
+ * net/packet: fix 4gb buffer limit due to overflow check
+ * team: avoid complex list operations in team_nl_cmd_options_set()
+ * sit: check if IPv6 enabled before calling ip6_err_gen_icmpv6_unreach()
+ * net/mlx4_en: Force CHECKSUM_NONE for short ethernet frames
+ * ARCv2: Enable unaligned access in early ASM code
+ * Revert "bridge: do not add port to router list when receives query with
source
+ 0.0.0.0"
+ * libceph: handle an empty authorize reply
+ * drm/msm: Unblock writer if reader closes file
+ * ASoC: Intel: Haswell/Broadwell: fix setting for .dynamic field
+ * ALSA: compress: prevent potential divide by zero bugs
+ * thermal: int340x_thermal: Fix a NULL vs IS_ERR() check
+ * usb: dwc3: gadget: Fix the uninitialized link_state when udc starts
+ * usb: gadget: Potential NULL dereference on allocation error
+ * ASoC: dapm: change snprintf to scnprintf for possible overflow
+ * ASoC: imx-audmux: change snprintf to scnprintf for possible overflow
+ * ARC: fix __ffs return value to avoid build warnings
+ * mac80211: fix miscounting of ttl-dropped frames
+ * serial: fsl_lpuart: fix maximum acceptable baud rate with over-sampling
+ * scsi: csiostor: fix NULL pointer dereference in csio_vport_set_state()
+ * net: altera_tse: fix connect_local_phy error path
+ * ibmveth: Do not process frames after calling napi_reschedule
+ * mac80211: don't initiate TDLS connection if station is not associated to AP
+ * cfg80211: extend range deviation for DMG
+ * KVM: nSVM: clear events pending from svm_complete_interrupts() when exiting
to
+ L1
+ * arm/arm64: KVM: Feed initialized memory to MMIO accesses
+ * KVM: arm/arm64: Fix MMIO emulation data handling
+ * powerpc: Always
[Kernel-packages] [Bug 1822271] Re: Xenial update: 4.4.177 upstream stable release
Applied patches were test-compiled for all supported arches. Build summary:
amd64-binary: PASSED
arm64-binary: PASSED
armhf-binary: PASSED
i386-binary:PASSED
powerpc-binary: PASSED
ppc64el-binary: PASSED
s390x-binary: PASSED
--
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/1822271
Title:
Xenial update: 4.4.177 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
4.4.177 upstream stable release
from git://git.kernel.org/
The following patches were applied:
* ceph: avoid repeatedly adding inode to mdsc->snap_flush_list
* numa: change get_mempolicy() to use nr_node_ids instead of MAX_NUMNODES
* KEYS: allow reaching the keys quotas exactly
* mfd: ti_am335x_tscadc: Use PLATFORM_DEVID_AUTO while registering mfd cells
* mfd: twl-core: Fix section annotations on {,un}protect_pm_master
* mfd: db8500-prcmu: Fix some section annotations
* mfd: ab8500-core: Return zero in get_register_interruptible()
* mfd: qcom_rpm: write fw_version to CTRL_REG
* mfd: wm5110: Add missing ASRC rate register
* mfd: mc13xxx: Fix a missing check of a register-read failure
* net: hns: Fix use after free identified by SLUB debug
* MIPS: ath79: Enable OF serial ports in the default config
* scsi: qla4xxx: check return code of qla4xxx_copy_from_fwddb_param
* scsi: isci: initialize shost fully before calling scsi_add_host()
* MIPS: jazz: fix 64bit build
* isdn: i4l: isdn_tty: Fix some concurrency double-free bugs
* atm: he: fix sign-extension overflow on large shift
* leds: lp5523: fix a missing check of return value of lp55xx_read
* isdn: avm: Fix string plus integer warning from Clang
* RDMA/srp: Rework SCSI device reset handling
* KEYS: user: Align the payload buffer
* KEYS: always initialize keyring_index_key::desc_len
* batman-adv: fix uninit-value in batadv_interface_tx()
* net/packet: fix 4gb buffer limit due to overflow check
* team: avoid complex list operations in team_nl_cmd_options_set()
* sit: check if IPv6 enabled before calling ip6_err_gen_icmpv6_unreach()
* net/mlx4_en: Force CHECKSUM_NONE for short ethernet frames
* ARCv2: Enable unaligned access in early ASM code
* Revert "bridge: do not add port to router list when receives query with
source
0.0.0.0"
* libceph: handle an empty authorize reply
* drm/msm: Unblock writer if reader closes file
* ASoC: Intel: Haswell/Broadwell: fix setting for .dynamic field
* ALSA: compress: prevent potential divide by zero bugs
* thermal: int340x_thermal: Fix a NULL vs IS_ERR() check
* usb: dwc3: gadget: Fix the uninitialized link_state when udc starts
* usb: gadget: Potential NULL dereference on allocation error
* ASoC: dapm: change snprintf to scnprintf for possible overflow
* ASoC: imx-audmux: change snprintf to scnprintf for possible overflow
* ARC: fix __ffs return value to avoid build warnings
* mac80211: fix miscounting of ttl-dropped frames
* serial: fsl_lpuart: fix maximum acceptable baud rate with over-sampling
* scsi: csiostor: fix NULL pointer dereference in csio_vport_set_state()
* net: altera_tse: fix connect_local_phy error path
* ibmveth: Do not process frames after calling napi_reschedule
* mac80211: don't initiate TDLS connection if station is not associated to AP
* cfg80211: extend range deviation for DMG
* KVM: nSVM: clear events pending from svm_complete_interrupts() when exiting
to
L1
* arm/arm64: KVM: Feed initialized memory to MMIO accesses
* KVM: arm/arm64: Fix MMIO emulation data handling
* powerpc: Always initialize input array when calling epapr_hypercall()
* mmc: spi: Fix card detection during probe
* x86/uaccess: Don't leak the AC flag into __put_user() value evaluation
* USB: serial: option: add Telit ME910 ECM composition
* USB: serial: cp210x: add ID for Ingenico 3070
* USB: serial: ftdi_sio: add ID for Hjelmslund Electronics USB485
* cpufreq: Use struct kobj_attribute instead of struct global_attr
* sockfs: getxattr: Fail with -EOPNOTSUPP for invalid attribute names
* ncpfs: fix build warning of strncpy
* isdn: isdn_tty: fix build warning of strncpy
* staging: lustre: fix buffer overflow of string buffer
* net-sysfs: Fix mem leak in netdev_register_kobject
* sky2: Disable MSI on Dell Inspiron 1545 and Gateway P-79
* team: Free BPF filter
[Kernel-packages] [Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate + snap-release-to-candidate: Pending -- snap not in i386:latest/candidate,amd64:latest/candidate channel verification-testing: Ongoing -- testing in progress -- 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/1821724 Title: linux: 4.4.0-145.171 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in i386:latest/candidate,amd64:latest/candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+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 1821712] Re: linux-kvm: 4.4.0-1043.49 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 13:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1821712 Title: linux-kvm: 4.4.0-1043.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 13:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821712/+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 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Hi Daniel, I've seen you marked my bug as this duplicate, but for me this doesn't happen on Ubuntu 18.10, only after the 19.04 upgrade -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1822267] Re: [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response
** Tags added: patch -- 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/1822267 Title: [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response Status in amd: New Status in linux package in Ubuntu: Incomplete Bug description: Description: Raven 2 platform fails to boot on ubuntu 19.04 (disco) with kernel 5.0.0. The issue is related to a fixed patch in linux-mainline about psp response code status. In some cases, psp response status is not 0 even there is no problem while the command is submitted. Some version of PSP FW doesn't write 0 to that field. So here we would like to only print a warning instead of an error during psp initialization to avoid breaking hw_init and it doesn't return -EINVAL. Steps: 1. Install Ubuntu 19.04 daily build on AMD Raven 2 platform (reproduced with 2019.03.18 version) 2. Reboot and it fails at kernel initialization. Current patch status: A patch has already accepted in the linux mainline. (id: 466bcb75b0791ba301817cdadeed20398f2224fe) See: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=466bcb75b0791ba301817cdadeed20398f2224fe Backport status: A backport patch is available and verified. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1822267/+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 1822267] Missing required logs.
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 1822267 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 -- 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/1822267 Title: [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response Status in amd: New Status in linux package in Ubuntu: Incomplete Bug description: Description: Raven 2 platform fails to boot on ubuntu 19.04 (disco) with kernel 5.0.0. The issue is related to a fixed patch in linux-mainline about psp response code status. In some cases, psp response status is not 0 even there is no problem while the command is submitted. Some version of PSP FW doesn't write 0 to that field. So here we would like to only print a warning instead of an error during psp initialization to avoid breaking hw_init and it doesn't return -EINVAL. Steps: 1. Install Ubuntu 19.04 daily build on AMD Raven 2 platform (reproduced with 2019.03.18 version) 2. Reboot and it fails at kernel initialization. Current patch status: A patch has already accepted in the linux mainline. (id: 466bcb75b0791ba301817cdadeed20398f2224fe) See: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=466bcb75b0791ba301817cdadeed20398f2224fe Backport status: A backport patch is available and verified. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1822267/+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 1820187] Re: Huawei Hi1822 NIC has poor performance
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => In Progress -- 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/1820187 Title: Huawei Hi1822 NIC has poor performance Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: Incomplete Bug description: [Impact] Connect Hi1822 NIC with 10G switch but the performance is only 1-2Gb/s $ iperf -c 10.228.68.133 Client connecting to 10.228.68.133, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.228.68.116 port 56810 connected with 10.228.68.133 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 1.53 GBytes 1.32 Gbits/sec [Test Case] iperf -c [Fix] Backporting all patches from mainline for drivers/net/ethernet/huawei solves this issue. [Regression Risk] Only modify codes in drivers/net/ethernet/huawei. Lowest risk to other devices and platform without it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820187/+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 1821712] Re: linux-kvm: 4.4.0-1043.49 -proposed tracker
4.4.0-1043.49 - kvm Regression test CMPL, RTB. Issue to note in amd64: ubuntu_fan_smoke_test - ubuntu_fan_smoke_test failed on 4.4 X-kvm kernel (bug 1763323) ubuntu_kernel_selftests - psock_tpacket in net failed (bug 1812176) test_bpf in net (bug 1812189) test_user_copy return code in user (bug 1812352) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) vmx (bug 1821394) vmx_hlt_with_rvi_test (bug 1822308) port80 (bug 1748105) vmx_apic_passthrough_thread (bug 1822309) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) getrandom02 (bug 1797327) inotify07 (bug 1774387) inotify08 (bug 1775784) msgstress03 (bug 1797341) quotactl01, quotactl02, quotactl03 (bug 1797325) sync_file_range02 (bug 1819116) tested manually for nfs-kernel-server issue (bug 1821275) ubuntu_lxc - python3 API failed (bug 1764618) ubuntu_qrt_kernel_security - SCHED_STACK_END_CHECK should be enabled (bug 1812159) ubuntu_quota_smoke_test - failed with KVM kernel (bug 1784535) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1821712 Title: linux-kvm: 4.4.0-1043.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 13:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821712/+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 1748105] Re: port80 test in kvm-unit-test failed on E4v3 azure node with 4.13/4.14 kernel
Spotted on X-KVM. ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1748105 Title: port80 test in kvm-unit-test failed on E4v3 azure node with 4.13/4.14 kernel Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test port80 test will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the port80 test as root: # TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/port80.flat -smp 1 # -initrd /tmp/tmp.3p9PWc2SRi enabling apic begining port 0x80 write test qemu-system-x86_64: terminating on signal 15 from pid 7790 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:13:18 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748105/+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 1805835] Re: Infinite aer_status and aer_agent output in tty
I can confirm having exactly the same issue with the WS-C621E-SAGE
Complete configuration:
* CPU: Intel Xeon Gold 6140
* Motherboard WS-C621E-SAGE
* RAM: 12*Kingston 32G
* GPUs: 3*RTX2080Ti
I get the same "aer*" messages, that can be of different flavors:
* "Bad DLLP"
* "Bad TLP"
* "Replay Timer Timeout"
Ex of a full error:
```
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: Hardware error from APEI
Generic Hardware Error Source: 0
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: It has been corrected by
h/w and requires no further action
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: event severity: corrected
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: Error 0, type: corrected
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: section_type: PCIe error
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: port_type: 4, root port
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: version: 3.0
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: command: 0x0540, status:
0x0010
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: device_id: :00:00.0
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: slot: 0
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: secondary_bus: 0x00
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: vendor_id: 0x8086,
device_id: 0x2020
Mar 28 19:23:25 tasty kernel: {56}[Hardware Error]: class_code: 06
Mar 28 19:23:25 tasty kernel: pci :00:00.0: aer_status: 0x0080,
aer_mask: 0x
Mar 28 19:23:25 tasty kernel: Bad DLLP
```
--
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/1805835
Title:
Infinite aer_status and aer_agent output in tty
Status in linux package in Ubuntu:
Confirmed
Bug description:
A fresh install of Ubuntu Server 18.04.1. It keeps printing the same
messages to the terminal:
[ 1475.344317] pci :00:00.0: aer_status: 0x0080, aer_mask: 0x
[ 1475.345586] pci :00:00.0: aer_layer=Data Link Layer,
aer_agent=Receiver ID
The same two lines, over and over (except number in brackets), every
10 minutes or so. After logging in it still keeps printing them. The
interval is not constant, sometimes longer, sometimes shorter.
Performed apt-get update and dist-upgrade, rebooted. Now 0 packages
pending update, but the above output is not affected.
Googled to find that AER is supposed to report PCIe errors. However
the above output does not look like an error. Seems like some log
output?
Naturally this randomly appearing output is extremely annoying and
interferes with the normal use of the console. My guess is that a
normally functioning install should have nothing of this sort, hence
this bug-report.
Any fix or workaround that will silence this output will be
appreciated greatly.
Let me know if any additional information or tests are needed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-39-generic 4.15.0-39.42
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-39-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p',
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0',
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p',
'/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p',
'/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer':
'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer':
'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer':
'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer':
'amixer'
Date: Thu Nov 29 12:07:18 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: ASUSTeK COMPUTER INC. WS-C621E-SAGE Series
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
TERM=linux
XDG_RUNTIME_DIR=
PATH=(custom, no user)
ProcFB:
0 astdrmfb
1 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic
root=UUID=e2d7aa3a-f3be-11e8-9d19-0c9d925bd3e9 ro maybe-ubiquity
RelatedPackageVersions:
linux-restricted-modules-4.15.0-39-generic N/A
linux-backports-modules-4.15.0-39-generic N/A
linux-firmware 1.173.2
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present
[Kernel-packages] [Bug 1822267] Re: [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response
** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: 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/1822267 Title: [Patch][Raven 2] kernel 5.0.0 cannot boot because of psp response Status in amd: New Status in linux package in Ubuntu: New Bug description: Description: Raven 2 platform fails to boot on ubuntu 19.04 (disco) with kernel 5.0.0. The issue is related to a fixed patch in linux-mainline about psp response code status. In some cases, psp response status is not 0 even there is no problem while the command is submitted. Some version of PSP FW doesn't write 0 to that field. So here we would like to only print a warning instead of an error during psp initialization to avoid breaking hw_init and it doesn't return -EINVAL. Steps: 1. Install Ubuntu 19.04 daily build on AMD Raven 2 platform (reproduced with 2019.03.18 version) 2. Reboot and it fails at kernel initialization. Current patch status: A patch has already accepted in the linux mainline. (id: 466bcb75b0791ba301817cdadeed20398f2224fe) See: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=466bcb75b0791ba301817cdadeed20398f2224fe Backport status: A backport patch is available and verified. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1822267/+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 1821394] Re: vmx tests fail in kvm_unit_tests
Found on X KVM as well. ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1821394 Title: vmx tests fail in kvm_unit_tests Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: Reproducible: Yes, every time. Series: cosmic Kernel: "linux-aws 4.18.0-1012.14" Steps: 1.) apt-get install --yes --allow build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) TESTNAME=vmx TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,+vmx -append "-exit_monitor_from_l2_test -ept_access* -vmx_smp* -vmx_vmcs_shadow_test" PASS: Enable-EPT enabled; EPT memory type 6: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT memory type 7: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 0: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 8: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 16: vmlaunch fails PASS: Enable-EPT enabled; EPT page walk length 24: vmlaunch succeeds FAIL: Enable-EPT enabled; EPT page walk length 32: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 40: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 48: vmlaunch fails FAIL: Enable-EPT enabled; EPT page walk length 56: vmlaunch fails INFO: Processor supports accessed and dirty flag PASS: Enable-EPT enabled; EPT accessed and dirty flag 0: vmlaunch succeeds PASS: Enable-EPT enabled; EPT accessed and dirty flag 1: vmlaunch succeeds PASS: Enable-EPT enabled; reserved bits [11:7] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [11:7] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 3: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 5: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 6: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 7: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 9: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 10: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 11: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 12: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 13: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 14: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 15: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 17: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 18: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 19: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 20: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 21: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 22: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 23: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 24: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 25: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 26: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 27: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 28: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 29: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 30: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [11:7] 31: vmlaunch fails PASS: Enable-EPT enabled; reserved bits [63:N] 0: vmlaunch succeeds FAIL: Enable-EPT enabled; reserved bits [63:N] 1: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 8: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 16: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 32: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 64: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 128: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 256: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 512: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 1024: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 2048: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits [63:N] 4096: vmlaunch fails FAIL: Enable-EPT enabled; reserved bits
[Kernel-packages] [Bug 1818811] Re: The swapfile on the Btrfs file system is not activated
Unfortunately it doesn't help. mar 29 12:01:18 notebook-Lenovo-V110 sudo[11977]:emanu : TTY=pts/1 ; PWD=/home/emanu ; USER=root ; COMMAND=/usr/bin/chattr +C /swapfile mar 29 12:02:20 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 29 12:02:20 notebook-Lenovo-V110 swapon[538]: swapon: /swapfile: swapon failed: Argomento non valido mar 29 12:02:22 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 29 12:02:22 notebook-Lenovo-V110 swapon[1059]: swapon: /swapfile: swapon failed: Argomento non valido mar 29 12:02:22 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 29 12:02:22 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 29 12:02:22 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 29 12:02:22 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. -- 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/1818811 Title: The swapfile on the Btrfs file system is not activated Status in linux package in Ubuntu: Confirmed Bug description: From 5.0 kernel is implemented support for the swapfile on Btrfs (https://patchwork.kernel.org/cover/10584515/), today arrived on the repositories of Ubuntu 19.04 proposed kernel 5.0, but the swapfile is not activated. Log: mar 06 11:17:55 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:55 notebook-Lenovo-V110 swapon[517]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 swapon[916]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Activating swap /swapfile... mar 06 11:17:57 notebook-Lenovo-V110 kernel: BTRFS warning (device sda1): swapfile must not be copy-on-write mar 06 11:17:57 notebook-Lenovo-V110 swapon[1006]: swapon: /swapfile: swapon failed: Argomento non valido mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Swap process exited, code=exited, status=255/EXCEPTION mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: swapfile.swap: Failed with result 'exit-code'. mar 06 11:17:57 notebook-Lenovo-V110 systemd[1]: Failed to activate swap /swapfile. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanu 1744 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 6 11:19:52 2019 InstallationDate: Installed on 2019-01-30 (34 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 13d3:5745 IMC Networks Bus 001 Device 002: ID 10c4:8105 Cygnal Integrated Products, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80TL ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-7-generic root=UUID=91fdf6c0-1b5d-4bb5-9aa4-aeb946236b8a ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.177 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 1KCN46WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: No Asset Tag
[Kernel-packages] [Bug 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- 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/1822247 Title: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Incomplete Bug description: Reproduce rate: 2 out of 3 runs This issue can be found on other arches as well, normally it will fail with the first run and pass with the second attempt. * Command: /home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke _test.sh Exit status: 1 Duration: 7.90551400185 stdout: creating backing nbd image /tmp/nbd_image.img Image path:/tmp/nbd_image.img Mount point: /mnt/nbd-test-13924 Date: Fri Mar 29 06:06:04 UTC 2019 Host: baltar Kernel:4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019 Machine: baltar ppc64le ppc64le CPUs online: 160 CPUs total:160 Page size: 65536 Pages avail: 1904339 Pages total: 2089666 Free space: Filesystem Size Used Avail Use% Mounted on udev 61G 0 61G 0% /dev tmpfs13G 12M 13G 1% /run /dev/sda2 1.8T 11G 1.7T 1% / tmpfs64G 0 64G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs64G 0 64G 0% /sys/fs/cgroup tmpfs13G 0 13G 0% /run/user/1000 NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.31.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-13924 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550112111 2% /mnt/nbd-test-13924 creating large file /mnt/nbd-test-13924/largefile -rw-r--r-- 1 root root 100M Mar 29 06:06 /mnt/nbd-test-13924/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-13924 removing file /mnt/nbd-test-13924/largefile unmounting /mnt/nbd-test-13924 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 694.662746] creating backing nbd image /tmp/nbd_image.img [ 695.821047] NBD device /dev/nbd0 created [ 696.271555] found nbd export [ 697.318393] starting client with NBD device /dev/nbd0 [ 697.323210] creating ext4 on /dev/nbd0 [ 697.589620] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 697.821953] checking ext4 on /dev/nbd0 [ 697.919173] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 697.925418] mounted on /dev/nbd0 [ 697.927107] creating large file /mnt/nbd-test-13924/largefile [ 698.839327] removing file /mnt/nbd-test-13924/largefile [ 699.596736] unmounting /mnt/nbd-test-13924 [ 700.664881] stopping client [ 700.667573] block nbd0: NBD_DISCONNECT [ 700.667733] block nbd0: shutting down sockets [ 700.668690] nbd0: detected capacity change from 0 to 134217728 [ 700.668758] print_req_error: I/O error, dev nbd0, sector 0 [ 700.668840] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669068] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669124] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669203] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669243] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669315] ldm_validate_partition_table(): Disk read failed. [ 700.669324] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669364] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669542] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669580] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669646] print_req_error: I/O error, dev nbd0, sector 0 [ 700.669686] Buffer I/O error on dev nbd0, logical block 0, async page read [ 700.669747]
[Kernel-packages] [Bug 1822247] Re: ubuntu_nbd_smoke_test failed on P9 with Bionic kernel
Similar failure could be found on X-4.15, AMD64 (onibi) / i386 (pepe) * Command: /home/ubuntu/autotest/client/tests/ubuntu_nbd_smoke_test/ubuntu_nbd_smoke _test.sh Exit status: 1 Duration: 8.1468269825 stdout: creating backing nbd image /tmp/nbd_image.img Image path: /tmp/nbd_image.img Mount point: /mnt/nbd-test-18217 Date: Fri Mar 29 07:44:02 UTC 2019 Host: onibi Kernel: 4.15.0-47-generic #50~16.04.1-Ubuntu SMP Fri Mar 15 16:06:21 UTC 2019 Machine: onibi x86_64 x86_64 CPUs online: 4 CPUs total: 4 Page size: 4096 Pages avail: 1340920 Pages total: 2038430 Free space: Filesystem Size Used Avail Use% Mounted on udev 3.9G 0 3.9G 0% /dev tmpfs 797M 17M 780M 3% /run /dev/sda1 917G 9.1G 861G 2% / tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup tmpfs 797M 0 797M 0% /run/user/1000 tmpfs 100K 0 100K 0% /var/lib/lxd/shmounts tmpfs 100K 0 100K 0% /var/lib/lxd/devlxd cgmfs 100K 0 100K 0% /run/cgmanager/fs NBD device /dev/nbd0 created found nbd export NBD exports found: test starting client with NBD device /dev/nbd0 Negotiation: ..size = 128MB creating ext4 on /dev/nbd0 mkfs on /dev/nbd0 succeeded after 0 attempt(s) checking ext4 on /dev/nbd0 fsck from util-linux 2.27.1 /dev/nbd0: clean, 11/32768 files, 9787/131072 blocks mount: /dev/nbd0 on /mnt/nbd-test-18217 type ext4 (rw,relatime,data=ordered) mounted on /dev/nbd0 free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 1550 112111 2% /mnt/nbd-test-18217 creating large file /mnt/nbd-test-18217/largefile -rw-r--r-- 1 root root 100M Mar 29 07:44 /mnt/nbd-test-18217/largefile free: Filesystem 1K-blocks Used Available Use% Mounted on /dev/nbd0 122835 103951 9710 92% /mnt/nbd-test-18217 removing file /mnt/nbd-test-18217/largefile unmounting /mnt/nbd-test-18217 stopping client disconnect, sock, done Found kernel warning, IO error and/or call trace echo [ 4088.409864] creating backing nbd image /tmp/nbd_image.img [ 4090.412514] NBD device /dev/nbd0 created [ 4090.464858] found nbd export [ 4091.510701] starting client with NBD device /dev/nbd0 [ 4091.512739] creating ext4 on /dev/nbd0 [ 4091.799747] mkfs on /dev/nbd0 succeeded after 0 attempt(s) [ 4092.155113] checking ext4 on /dev/nbd0 [ 4092.232523] EXT4-fs (nbd0): mounted filesystem with ordered data mode. Opts: (null) [ 4092.237839] mounted on /dev/nbd0 [ 4092.239111] creating large file /mnt/nbd-test-18217/largefile [ 4093.429863] removing file /mnt/nbd-test-18217/largefile [ 4093.685500] unmounting /mnt/nbd-test-18217 [ 4094.741235] stopping client [ 4094.741850] block nbd0: NBD_DISCONNECT [ 4094.741892] block nbd0: shutting down sockets [ 4094.741988] nbd0: detected capacity change from 0 to 134217728 [ 4094.742025] print_req_error: 1 callbacks suppressed [ 4094.742026] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742053] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742091] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742113] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742147] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742169] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742197] ldm_validate_partition_table(): Disk read failed. [ 4094.742204] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742225] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742288] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742313] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742354] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742378] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742419] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742440] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742468] Dev nbd0: unable to read RDB block 0 [ 4094.742492] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742513] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742599] print_req_error: I/O error, dev nbd0, sector 24 [ 4094.742625] Buffer I/O error on dev nbd0, logical block 3, async page read [ 4094.742723] print_req_error: I/O error, dev nbd0, sector 0 [ 4094.742749] Buffer I/O error on dev nbd0, logical block 0, async page read [ 4094.742918] nbd0: unable to read partition table [ 4095.465090] Found kernel warning, IO error and/or call trace [ 4095.465145] echo killing server Completed Kernel issues: Found kernel warning, IO error and/or call trace: TEST: [ 4088.409864] creating backing nbd image /tmp/nbd_image.img [ 4090.412514] NBD device /dev/nbd0 created [ 4090.464858] found nbd export [ 4091.510701] starting client with NBD device /dev/nbd0 [ 4091.512739] creating ext4 on
[Kernel-packages] [Bug 1819716] Re: linux: 4.15.0-47.50 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe) derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 (linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 (linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips), bug 1822167 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 15. March 2019 23:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- 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/1819716 Title: linux: 4.15.0-47.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe) derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 (linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 (linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips), bug 1822167 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 15. March 2019 23:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819716/+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 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in i386:latest/candidate,amd64:latest/candidate + snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate channel verification-testing: Ongoing -- testing in progress -- 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/1821724 Title: linux: 4.4.0-145.171 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+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 1818881] Re: ath10k_pci crashing
I tried ping out for about 2 hours on the same machine (CID:201810-26508) of #12 But not see this issue yet, I will put the machine ping out for over weekend to see if I can reproduce this issue. But I afraid the issue has been fixed by the new kernel (4.18.0-16.17~18.04.1). Could you please try if updating kernel fix the issue on your machine? -- 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/1818881 Title: ath10k_pci crashing Status in linux package in Ubuntu: Confirmed Bug description: The below happens on a regular basis on my DELL XPS 13 9380: [77451.338493] RIP: 0010:ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core] [77451.338494] Code: 74 32 48 8b 87 10 02 00 00 48 85 c0 74 26 48 8b 40 28 48 85 c0 74 17 45 31 c0 b9 02 00 00 00 e8 dd c1 d7 db 48 89 d8 5b 5d c3 <0f> 0b 31 db 48 89 d8 5b 5d c3 48 8b 05 de 67 5a dc eb d1 0f 1f 40 [77451.338531] RSP: 0018:9d996e503d78 EFLAGS: 00010246 [77451.338533] RAX: RBX: 9d97b7c12290 RCX: 9d96cbfd5528 [77451.338534] RDX: 37af2804 RSI: 9d9944c51ed4 RDI: 9d9944c51de0 [77451.338535] RBP: 9d996e503d80 R08: 0020 R09: [77451.338537] R10: 9d94f045ecd8 R11: 01ff R12: 9d9944c51520 [77451.338538] R13: 9d996e503e40 R14: 0040 R15: 9d996e503e28 [77451.338540] FS: () GS:9d996e50() knlGS: [77451.338541] CS: 0010 DS: ES: CR0: 80050033 [77451.338542] CR2: 1f1104c31000 CR3: 00017aa0a005 CR4: 003606e0 [77451.338543] Call Trace: [77451.338545] [77451.338557] ath10k_htt_txrx_compl_task+0x3d6/0xe40 [ath10k_core] [77451.338561] ? ath10k_pci_irq_msi_fw_unmask+0x70/0x70 [ath10k_pci] [77451.338563] ? ath10k_pci_wake.part.24+0xa0/0xa0 [ath10k_pci] [77451.338567] ath10k_pci_napi_poll+0x54/0x110 [ath10k_pci] [77451.338571] net_rx_action+0x140/0x3a0 [77451.338575] __do_softirq+0xe4/0x2d4 [77451.338580] irq_exit+0xc5/0xd0 [77451.338582] do_IRQ+0x8a/0xe0 [77451.338585] common_interrupt+0xf/0xf [77451.338586] [77451.338589] RIP: 0010:cpuidle_enter_state+0xa5/0x2c0 [77451.338590] Code: 8b 3d df bf 9d 63 e8 6a 09 89 ff 48 89 c3 0f 1f 44 00 00 31 ff e8 cb 14 89 ff 45 84 ff 0f 85 c8 01 00 00 fb 66 0f 1f 44 00 00 <48> 2b 5d d0 48 ba cf f7 53 e3 a5 9b c4 20 48 89 d8 48 c1 fb 3f 48 [77451.338621] RSP: 0018:af4601993e50 EFLAGS: 0246 ORIG_RAX: ffde [77451.338623] RAX: 9d996e522c40 RBX: 46710b80e2b6 RCX: 001f [77451.338624] RDX: 46710b80e2b6 RSI: 4041cc98 RDI: [77451.338625] RBP: af4601993e90 R08: 0002 R09: 000224c0 [77451.338626] R10: af4601993e20 R11: 00d9 R12: 0004 [77451.338626] R13: 9d996e52ce00 R14: 9d3849f8 R15: [77451.338630] cpuidle_enter+0x17/0x20 [77451.338632] call_cpuidle+0x23/0x40 [77451.338634] do_idle+0x204/0x280 [77451.338636] cpu_startup_entry+0x73/0x80 [77451.338639] start_secondary+0x1ab/0x200 [77451.338642] secondary_startup_64+0xa5/0xb0 [77451.338643] ---[ end trace 22914e3b3a848f81 ]--- [77451.338655] ath10k_pci :02:00.0: failed to pop paddr list: -2 $ uname -a Linux perseus 4.18.0-15-generic #16~18.04.1-Ubuntu SMP Thu Feb 7 14:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ modinfo ath10k_pci filename: /lib/modules/4.18.0-15-generic/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko firmware: ath10k/QCA9377/hw1.0/board.bin firmware: ath10k/QCA9377/hw1.0/firmware-5.bin firmware: ath10k/QCA9377/hw1.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/board-2.bin firmware: ath10k/QCA6174/hw3.0/board.bin firmware: ath10k/QCA6174/hw3.0/firmware-6.bin firmware: ath10k/QCA6174/hw3.0/firmware-5.bin firmware: ath10k/QCA6174/hw3.0/firmware-4.bin firmware: ath10k/QCA6174/hw2.1/board-2.bin firmware: ath10k/QCA6174/hw2.1/board.bin firmware: ath10k/QCA6174/hw2.1/firmware-5.bin firmware: ath10k/QCA6174/hw2.1/firmware-4.bin firmware: ath10k/QCA9887/hw1.0/board-2.bin firmware: ath10k/QCA9887/hw1.0/board.bin firmware: ath10k/QCA9887/hw1.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/board-2.bin firmware: ath10k/QCA988X/hw2.0/board.bin firmware: ath10k/QCA988X/hw2.0/firmware-5.bin firmware: ath10k/QCA988X/hw2.0/firmware-4.bin firmware: ath10k/QCA988X/hw2.0/firmware-3.bin firmware: ath10k/QCA988X/hw2.0/firmware-2.bin license:Dual BSD/GPL description:Driver support for Qualcomm Atheros 802.11ac WLAN PCIe/AHB devices author: Qualcomm Atheros srcversion: D49EBAB0107B6CE28383BB8 alias:
[Kernel-packages] [Bug 1821713] Re: linux-raspi2: 4.4.0-1106.114 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in armhf:latest/candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1821713 Title: linux-raspi2: 4.4.0-1106.114 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in armhf:latest/candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821713/+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 1822274] Missing required logs.
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 1822274 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 Bionic) Status: New => Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: New => Incomplete -- 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/1822274 Title: 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B/C P9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: This test will timeout on our P9 node "baltar" (it's the most time- consuming job) A manual run shows that the sysbench command in this test will take about 2 hours to complete: # sysbench --num-threads=1 --test=fileio --file-num=81920 --file-total-size=80M --file-block-size=1K --file-io-mode=sync --file-test-mode=seqwr prepare ... ... ... Creating file test_file.81917 Creating file test_file.81918 Creating file test_file.81919 83886080 bytes written in 7231.40 seconds (0.01 MiB/sec). # And our timeout threshold is exactly 2 hours. An easy fix for this is to bump the threshold. But it's weird that this test only fail on Bionic 4.15. Here is the performance matrix for how long does it take for this test to execute: * Bionic 4.18 - 90 minutes * Disco 5.0 - 99 minutes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 07:04 seq crw-rw 1 root audio 116, 33 Mar 29 07:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 29 09:55:09 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.09 0.04 0.27 1/1367 5463 ProcLocks: 1: FLOCK ADVISORY WRITE 3539 00:17:524 0 EOF 2: POSIX ADVISORY WRITE 3875 00:17:602 0 EOF 3: FLOCK ADVISORY WRITE 3912 00:17:598 0 EOF 4: POSIX ADVISORY WRITE 3902 00:17:580 0 EOF 5: POSIX ADVISORY WRITE 1820 00:17:373 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-46-generic (buildd@bos02-ppc64el-009) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.862 GHz (cpu 1) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822274/+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 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-signing Status: Confirmed => 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/1819707 Title: linux-fips: 4.15.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-signing series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Holding before Promote to Proposed phase-changed: Friday, 29. March 2019 06:21 UTC reason: promote-to-signing: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+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 1819707] Re: linux-fips: 4.15.0-1002.3 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-signing Status: New => 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/1819707 Title: linux-fips: 4.15.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-signing series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819716 phase: Holding before Promote to Proposed phase-changed: Friday, 29. March 2019 06:21 UTC reason: promote-to-signing: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819707/+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 1822235] Re: All 29 tests in kvm-unit-test failed (timeouted) on i386
Bump the timeout threshold to 360 seconds for each test, they're still failing. -- 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/1822235 Title: All 29 tests in kvm-unit-test failed (timeouted) on i386 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: All the available tests in kvm-unit-test have failed on Cosmic i386 with node "onza". They all timeout with the default 90 second threshold. TESTNAME=smptest TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 2 FAIL smptest (timeout; duration=90s) TESTNAME=smptest3 TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 3 FAIL smptest3 (timeout; duration=90s) TESTNAME=vmexit_cpuid TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'cpuid' FAIL vmexit_cpuid (timeout; duration=90s) TESTNAME=vmexit_vmcall TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'vmcall' FAIL vmexit_vmcall (timeout; duration=90s) TESTNAME=vmexit_mov_from_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_from_cr8' FAIL vmexit_mov_from_cr8 (timeout; duration=90s) TESTNAME=vmexit_mov_to_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_to_cr8' FAIL vmexit_mov_to_cr8 (timeout; duration=90s) TESTNAME=vmexit_inl_pmtimer TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'inl_from_pmtimer' FAIL vmexit_inl_pmtimer (timeout; duration=90s) TESTNAME=vmexit_ipi TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi' FAIL vmexit_ipi (timeout; duration=90s) TESTNAME=vmexit_ipi_halt TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi_halt' FAIL vmexit_ipi_halt (timeout; duration=90s) TESTNAME=vmexit_ple_round_robin TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'ple_round_robin' FAIL vmexit_ple_round_robin (timeout; duration=90s) TESTNAME=vmexit_tscdeadline TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline FAIL vmexit_tscdeadline (timeout; duration=90s) TESTNAME=vmexit_tscdeadline_immed TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline_immed FAIL vmexit_tscdeadline_immed (timeout; duration=90s) TESTNAME=smap TIMEOUT=90s ACCEL= ./x86/run x86/smap.flat -smp 1 -cpu host FAIL smap (timeout; duration=90s) TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1 FAIL eventinj (timeout; duration=90s) TESTNAME=hypercall TIMEOUT=90s ACCEL= ./x86/run x86/hypercall.flat -smp 1 FAIL hypercall (timeout; duration=90s) TESTNAME=msr TIMEOUT=90s ACCEL= ./x86/run x86/msr.flat -smp 1 FAIL msr (timeout; duration=90s) TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 FAIL port80 (timeout; duration=90s) TESTNAME=realmode TIMEOUT=90s ACCEL= ./x86/run x86/realmode.flat -smp 1 FAIL realmode (timeout; duration=90s) TESTNAME=s3 TIMEOUT=90s ACCEL= ./x86/run x86/s3.flat -smp 1 FAIL s3 (timeout; duration=90s) TESTNAME=sieve TIMEOUT=90s ACCEL= ./x86/run x86/sieve.flat -smp 1 FAIL sieve (timeout; duration=90s) TESTNAME=tsc TIMEOUT=90s ACCEL= ./x86/run x86/tsc.flat -smp 1 -cpu kvm64,+rdtscp FAIL tsc (timeout; duration=90s) TESTNAME=tsc_adjust TIMEOUT=90s ACCEL= ./x86/run x86/tsc_adjust.flat -smp 1 -cpu host FAIL tsc_adjust (timeout; duration=90s) TESTNAME=taskswitch TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch.flat -smp 1 FAIL taskswitch (timeout; duration=90s) TESTNAME=taskswitch2 TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch2.flat -smp 1 FAIL taskswitch2 (timeout; duration=90s) TESTNAME=kvmclock_test TIMEOUT=90s ACCEL= ./x86/run x86/kvmclock_test.flat -smp 2 --append "1000 `date +%s`" FAIL kvmclock_test (timeout; duration=90s) TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu qemu64,+umip FAIL umip (timeout; duration=90s) TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev FAIL hyperv_synic (timeout; duration=90s) TESTNAME=hyperv_connections TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_connections.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev FAIL hyperv_connections (timeout; duration=90s) TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev FAIL hyperv_stimer (timeout; duration=90s) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-16-generic 4.18.0-16.17 ProcVersionSignature: User Name 4.18.0-16.17-generic 4.18.20 Uname: Linux
[Kernel-packages] [Bug 1822274] Re: 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B P9
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Description changed: This test will timeout on our P9 node "baltar" A manual run shows that the sysbench command in this test will take about 2 hours to complete: # sysbench --num-threads=1 --test=fileio --file-num=81920 --file-total-size=80M --file-block-size=1K --file-io-mode=sync --file-test-mode=seqwr prepare ... ... ... Creating file test_file.81917 Creating file test_file.81918 Creating file test_file.81919 83886080 bytes written in 7231.40 seconds (0.01 MiB/sec). - # + # And our timeout threshold is exactly 2 hours. An easy fix for this is to bump the threshold. But it's weird that this test only fail on Bionic 4.15. - On Bionic 4.18, it took only 90 minute to finish this test. + Here is the performance matrix for how long does it take for this test to execute: + * Bionic 4.18 - 90 minutes + * Disco 5.0 - 99 minutes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic ppc64le AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Mar 29 07:04 seq - crw-rw 1 root audio 116, 33 Mar 29 07:04 timer + total 0 + crw-rw 1 root audio 116, 1 Mar 29 07:04 seq + crw-rw 1 root audio 116, 33 Mar 29 07:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - + Date: Fri Mar 29 09:55:09 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. - Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd - Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. + Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd + Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: - + ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.09 0.04 0.27 1/1367 5463 ProcLocks: - 1: FLOCK ADVISORY WRITE 3539 00:17:524 0 EOF - 2: POSIX ADVISORY WRITE 3875 00:17:602 0 EOF - 3: FLOCK ADVISORY WRITE 3912 00:17:598 0 EOF - 4: POSIX ADVISORY WRITE 3902 00:17:580 0 EOF - 5: POSIX ADVISORY WRITE 1820 00:17:373 0 EOF + 1: FLOCK ADVISORY WRITE 3539 00:17:524 0 EOF + 2: POSIX ADVISORY WRITE 3875 00:17:602 0 EOF + 3: FLOCK ADVISORY WRITE 3912 00:17:598 0 EOF + 4: POSIX ADVISORY WRITE 3902 00:17:580 0 EOF + 5: POSIX ADVISORY WRITE 1820 00:17:373 0 EOF ProcSwaps: - Filename TypeSizeUsedPriority - /swap.img file 8388544 0 -2 + Filename TypeSizeUsedPriority + /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-46-generic (buildd@bos02-ppc64el-009) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019 RelatedPackageVersions: - linux-restricted-modules-4.15.0-46-generic N/A - linux-backports-modules-4.15.0-46-generic N/A - linux-firmware 1.173.3 + linux-restricted-modules-4.15.0-46-generic N/A + linux-backports-modules-4.15.0-46-generic N/A + linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 16 cpu_freq: - min: 2.862 GHz (cpu 159) - max: 2.862 GHz (cpu 1) - avg: 2.862 GHz + min: 2.862 GHz (cpu 159) + max: 2.862 GHz (cpu 1) + avg: 2.862 GHz cpu_runmode: - Could not retrieve current diagnostics mode, - No kernel interface to firmware + Could not retrieve current diagnostics mode, + No kernel interface to firmware cpu_smt: SMT=4 ** Summary changed: - 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B P9 + 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B/C P9 ** Description changed: - This test will timeout on our P9 node "baltar" + This test
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
SMART long offline test was successful. Everything is fine. I formatted the ext4 partition. I assume the corruption came, because I turned of the external HDD hub too early several times. But this weird bug happened one time I unplugged the external HDD before waking up my ThinkPad T460P. PS: I hope the issue can be found and fixed. A crashing user session is a bit weird. -- 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/1818974 Title: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+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 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses
** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: Confirmed ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: 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/1675949 Title: perf report can't annotate kernel and dbgsym package has wrong addresses Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Confirmed Bug description: Impact: Under some condition, 'perf report' is unable to show the assembly code of a kernel function (perf report -> select a kernel function -> annotate). This is not an issue of the kernel itself or the perf tool, instead it's your environment that is missing the objdump binary (and perf, unfortunately, doesn't complain about it). Make sure binutils is not installed, or move away the objdump binary: # mv /usr/bin/objdump /usr/bin/objdump.foo Run a perf session and write down all events: # perf record -a -- sleep 10 # perf report selct a kernel function, press 'Annotate', a blank screen will appears (instead of the assembly code). Now put the objdump binary back (or install binutils): # mv /usr/bin/objdump.foo /usr/bin/objdump and run again perf report: # perf report select a kernel function, annotate, the disassembly will show up. Fix: Make binutils a Depends in SRCPKGNAME-tools-PKGVER-ABINUM - see the attached patch. How to test: Install a patched linux-tools-PKGVER-ABINUM.deb package: it will require binutils. Regression: We are adding a new dependency on a package, so code wise there's no regression potential - on the other hand, image creation, or development environment will experience a slight increase in size (1.8MB on x86-64 and 2.1M on arm64) if they didn't install binutils already. -- Running zesty 4.10.0-13-generic kernel and running: $ perf record followed by $ perf report results in output that can't be annotated (even when run as root). The following message appears: Couldn't annotate do_io_submit: No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e was found in the path. Note that annotation using /proc/kcore requires CAP_SYS_RAWIO capability. Please use: perf buildid-cache -vu vmlinux Note this is being run as root and /proc/kcore is accessible with dd from the same shell: $ dd if=/proc/kcore bs=8 count=16 | hexdump 000 457f 464c 0102 0001 010 0004 00b7 0001 020 0040 030 0040 0038 0003 040 0004 00e8 Additionally, installing the linux-image-4.10.0-13-generic-dbgsym actually hurts the situation because the symbol addresses in the dbgsym don't match the kernel addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+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 1822271] [NEW] Xenial update: 4.4.177 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.177 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1822271 Title: Xenial update: 4.4.177 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.177 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822271/+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 1822274] [NEW] 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B P9
Public bug reported: This test will timeout on our P9 node "baltar" A manual run shows that the sysbench command in this test will take about 2 hours to complete: # sysbench --num-threads=1 --test=fileio --file-num=81920 --file-total-size=80M --file-block-size=1K --file-io-mode=sync --file-test-mode=seqwr prepare ... ... ... Creating file test_file.81917 Creating file test_file.81918 Creating file test_file.81919 83886080 bytes written in 7231.40 seconds (0.01 MiB/sec). # And our timeout threshold is exactly 2 hours. An easy fix for this is to bump the threshold. But it's weird that this test only fail on Bionic 4.15. On Bionic 4.18, it took only 90 minute to finish this test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 07:04 seq crw-rw 1 root audio 116, 33 Mar 29 07:04 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Mar 29 09:55:09 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0451:80ff Texas Instruments, Inc. Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: root=UUID=acd1a0d7-f6fc-4130-928c-c8b11ad6e4be ro console=hvc0 ProcLoadAvg: 0.09 0.04 0.27 1/1367 5463 ProcLocks: 1: FLOCK ADVISORY WRITE 3539 00:17:524 0 EOF 2: POSIX ADVISORY WRITE 3875 00:17:602 0 EOF 3: FLOCK ADVISORY WRITE 3912 00:17:598 0 EOF 4: POSIX ADVISORY WRITE 3902 00:17:580 0 EOF 5: POSIX ADVISORY WRITE 1820 00:17:373 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-46-generic (buildd@bos02-ppc64el-009) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #49-Ubuntu SMP Wed Feb 6 09:32:48 UTC 2019 RelatedPackageVersions: linux-restricted-modules-4.15.0-46-generic N/A linux-backports-modules-4.15.0-46-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_dscr: DSCR is 16 cpu_freq: min: 2.862 GHz (cpu 159) max: 2.862 GHz (cpu 1) avg: 2.862 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=4 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: apport-bug bionic ppc64el uec-images ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: 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/1822274 Title: 9e622d6bea0202e9fe267955362c01918562c09b in ubuntu_btrfs_kernel_fixes timeouted on B P9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: This test will timeout on our P9 node "baltar" A manual run shows that the sysbench command in this test will take about 2 hours to complete: # sysbench --num-threads=1 --test=fileio --file-num=81920 --file-total-size=80M --file-block-size=1K --file-io-mode=sync --file-test-mode=seqwr prepare ... ... ... Creating file test_file.81917 Creating file test_file.81918 Creating file test_file.81919 83886080 bytes written in 7231.40 seconds (0.01 MiB/sec). # And our timeout threshold is exactly 2 hours. An easy fix for this is to bump the threshold. But it's weird that this test only fail on Bionic 4.15. On Bionic 4.18, it took only 90 minute to finish this test. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-46-generic 4.15.0-46.49 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 07:04 seq crw-rw 1 root audio 116, 33 Mar 29 07:04 timer
[Kernel-packages] [Bug 1821713] Re: linux-raspi2: 4.4.0-1106.114 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/raspi2/4.4.0-1106.114/raspi2-4.4-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1821713 Title: linux-raspi2: 4.4.0-1106.114 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Testing phase-changed: Wednesday, 27. March 2019 14:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: Pending -- snap not in armhf:latest/candidate channel verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821713/+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 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6
I have had no issues anymore since I switched to my self built 1.177~ppa0f22c85 (PPA) - while before they were rather common. Thanks for accepting that into Bionic-Proposed. I have switched to 1.173.5 from Proposed and unplugged the cables. The install (a downgrade for me as outlined) itself worked fine, I'll reboot now and check on Monday I'll check if any connectivity issues came up over the weekend. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1808389 Title: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6 Status in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Committed Status in The Bionic Beaver: Confirmed Status in linux-firmware source package in Bionic: Fix Committed Status in The Cosmic Cuttlefish: Confirmed Status in linux-firmware source package in Cosmic: Fix Committed Bug description: SRU Justification: === [Impact] repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. [Fix] New iwlwifi firmware fix it. [Test] Bug reporter verified with positive result. [Regression Potential] Upstream fix, low risk. Bug reporter confirms fix. Original bug report: = Seeing repeated crashes of the Intel 8265 wireless card on a Lenovo X1 Gen6. Firmware: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.840159] wlp2s0: send auth to 60:38:e0:70:a2:11 (try 1/3) Dec 13 11:53:36 james-x1 kernel: [ 856.844875] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. Dec 13 11:53:36 james-x1 kernel: [ 856.845015] iwlwifi :02:00.0: Start IWL Error Log Dump: Dec 13 11:53:36 james-x1 kernel: [ 856.845018] iwlwifi :02:00.0: Status: 0x0100, count: 6 Dec 13 11:53:36 james-x1 kernel: [ 856.845021] iwlwifi :02:00.0: Loaded firmware version: 36.7596afd4.0 Dec 13 11:53:36 james-x1 kernel: [ 856.845024] iwlwifi :02:00.0: 0x1006 | ADVANCED_SYSASSERT Dec 13 11:53:36 james-x1 kernel: [ 856.845026] iwlwifi :02:00.0: 0x02F0 | trm_hw_status0 Dec 13 11:53:36 james-x1 kernel: [ 856.845029] iwlwifi :02:00.0: 0x | trm_hw_status1 Dec 13 11:53:36 james-x1 kernel: [ 856.845031] iwlwifi :02:00.0: 0x000248DC | branchlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845034] iwlwifi :02:00.0: 0x0003A7DA | interruptlink1 Dec 13 11:53:36 james-x1 kernel: [ 856.845036] iwlwifi :02:00.0: 0x | interruptlink2 Dec 13 11:53:36 james-x1 kernel: [ 856.845039] iwlwifi :02:00.0: 0xFEDA | data1 Dec 13 11:53:36 james-x1 kernel: [ 856.845041] iwlwifi :02:00.0: 0xDEADBEEF | data2 Dec 13 11:53:36 james-x1 kernel: [ 856.845044] iwlwifi :02:00.0: 0xDEADBEEF | data3 Dec 13 11:53:36 james-x1 kernel: [ 856.845046] iwlwifi :02:00.0: 0x0007E1DC | beacon time Dec 13 11:53:36 james-x1 kernel: [ 856.845048] iwlwifi :02:00.0: 0x003B0850 | tsf low Dec 13 11:53:36 james-x1 kernel: [ 856.845051] iwlwifi :02:00.0: 0x | tsf hi Dec 13 11:53:36 james-x1 kernel: [ 856.845053] iwlwifi :02:00.0: 0x | time gp1 Dec 13 11:53:36 james-x1 kernel: [ 856.845055] iwlwifi :02:00.0: 0x003B0852 | time gp2 Dec 13 11:53:36 james-x1 kernel: [ 856.845058] iwlwifi :02:00.0: 0x0001 | uCode revision type Dec 13 11:53:36 james-x1 kernel: [ 856.845060] iwlwifi :02:00.0: 0x0024 | uCode version major Dec 13 11:53:36 james-x1 kernel: [ 856.845063] iwlwifi :02:00.0: 0x7596AFD4 | uCode version minor Dec 13 11:53:36 james-x1 kernel: [ 856.845065] iwlwifi :02:00.0: 0x0230 | hw version Dec 13 11:53:36 james-x1 kernel: [ 856.845068] iwlwifi :02:00.0: 0x18489000 | board version Dec 13 11:53:36 james-x1 kernel: [ 856.845070] iwlwifi :02:00.0: 0x0501001C | hcmd Dec 13 11:53:36 james-x1 kernel: [ 856.845072] iwlwifi :02:00.0: 0x00023008 | isr0 Dec 13 11:53:36 james-x1 kernel: [ 856.845075] iwlwifi :02:00.0: 0x000D | isr1 Dec 13 11:53:36 james-x1 kernel: [ 856.845077] iwlwifi :02:00.0: 0x08001802 | isr2 Dec 13 11:53:36 james-x1 kernel: [ 856.845080] iwlwifi :02:00.0: 0x0041FDC0 | isr3 Dec 13 11:53:36 james-x1 kernel: [ 856.845082] iwlwifi :02:00.0: 0x | isr4 Dec 13 11:53:36 james-x1 kernel: [ 856.845084] iwlwifi :02:00.0: 0x00580118 | last cmd Id Dec 13 11:53:36 james-x1 kernel: [ 856.845087] iwlwifi :02:00.0: 0x | wait_event Dec 13 11:53:36 james-x1 kernel: [ 856.845089] iwlwifi :02:00.0: 0x76DD | l2p_control Dec 13 11:53:36 james-x1 kernel: [ 856.845091] iwlwifi :02:00.0: 0x0020 | l2p_duration Dec 13 11:53:36 james-x1 kernel: [ 856.845094] iwlwifi :02:00.0: 0x | l2p_mhvalid Dec 13 11:53:36 james-x1 kernel: [ 856.845096] iwlwifi :02:00.0: 0x00A0 | l2p_addr_match Dec 13
[Kernel-packages] [Bug 1819716] Re: linux: 4.15.0-47.50 -proposed tracker
4.15.0-47.50 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kernel_selftests - global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ubuntu_kvm_unit_tests - apic-split timeouted (bug 1821390) apic timeouted (bug 1748103) vmware_backdoors (bug 1821393) svm (bug 1821903) ubunut_ltp - binfmt_misc02 (bug 1822246) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ubuntu_kvm_unit_tests - gicv3-ipi and gicv3-active failed on Moonshot (bug 1790825) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in i386: ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) Kprobe event string type argument in ftrace (bug 1812645) ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - all 29 test failed on i386 (bug 1822235) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) Issue to note in ppc64le (P8): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 1812796) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ebb in powerpc (bug 1812805) Kprobe event argument syntax in ftrace (bug 1812809) ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) ubuntu_ltp_syscalls - fallocate05 (bug 1783880) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) 48 / 49 tests were run, missing: xfstests Issue to note in ppc64le (P9): hwclock - hwclock test failed on Power9 system with Bionic kernel (bug 1775858) ubuntu_bpf - test_map failed (bug 1788562) ubuntu_btrfs_kernel_fixes - test 9e622d6bea0202e9fe267955362c01918562c09b timeouted ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 1812796) global.get_metadata in seccomp (bug 1811057) raw_skew in timer (bug 1811194) ebb in powerpc (bug 1812805) tm-unavailable in powerpc (bug 1813129) ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) buntu_ltp_syscalls - fallocate05 (bug 1783880) inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (KVM): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 1811057) ftrace (bug 1812836) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) ubuntu_lxc - Container "reboot" is defined (bug 1788574) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (Ubuntu on LPAR): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 1811057) ftrace (bug 1812836) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is defined (bug 1788574) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (zVM): ubuntu_bpf - test_map failed (bug 1788562) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) TRACE_syscall in seccomp (bug 1812824) global.get_metadata in seccomp (bug 1811057) ftrace (bug 1812836) ubuntu_kvm_unit_tests - skey failed (bug 1778705) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) ubuntu_lxc - Container "reboot" is defined (bug 1788574) Note: No xfstests for P9 as it does not have a scratch drive Note: Missing ubuntu_btrfs_kernel_fixes for s390x (bug 1809860) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug
[Kernel-packages] [Bug 1821863] Missing required logs.
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 1821863 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 -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1821863] Re: Need to add Intel CML related pci-id's
** Changed in: linux (Ubuntu Bionic) Status: New => Invalid -- 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/1821863 Title: Need to add Intel CML related pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: New Status in linux-oem package in Ubuntu: New Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] Please make it happen in the coming oem-kernel as there will be a flood of Intel Comet Lake (CML) platforms that would need it. Thank you. The same is needed for the rest of the stack. CML is basically another iteration of Skylake/Kabylake/Coffee Lake, and doesn't need other changes than pci-id's and support for the PCH (similar to Cannon point, already supported by the kernel). [Test case] Test that i915 graphics works on CML. [Regression potential] None really, these only add a bunch of new pci-id's across the stack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1817817] Re: To add power setting bin file for SAR support (QCA6174)
** Tags added: verification-needed-bionic ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1817817 Title: To add power setting bin file for SAR support (QCA6174) Status in HWE Next: Fix Released Status in OEM Priority Project: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Cosmic: Fix Committed Bug description: [Impact] To meet the policy requirement of the RF radiation, we need to reduce the power of the device. [Fix] Qualcomm provides a new firmware for this. 97b1f938 ath10k: QCA6174 hw3.0: update board-2.bin [Test] We can't verify it. [Regression Potential] Low, it's a fix from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817817/+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
