[Kernel-packages] [Bug 1831371] Re: Touchpad stops working for a period of time
Rob, Please attach dmesg, thanks! -- 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/1831371 Title: Touchpad stops working for a period of time Status in linux package in Ubuntu: Confirmed Bug description: Occasionally the touchpad will stop working for a period of time, the mouse cursor disappears but the touchpad buttons still work. The keyboard and touchscreen still work normally. Eventually after a few minutes the touchpad starts working again. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob 13195 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jun 2 22:09:46 2019 InstallationDate: Installed on 2019-04-24 (38 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831371/+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 1831494] Re: USB-related kernel problem with scanner
Does kernel parameter "mds=off" help? -- 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/1831494 Title: USB-related kernel problem with scanner Status in linux package in Ubuntu: Confirmed Bug description: My Canon CanoScan LiDE 220 scanner had worked reasonably well, until a new kernel has been installed. It went into stop-and-go mode, and made funny noises. This is worse in higher resolutions. I had a notion that it might be a problem with USB, which in turn resides in the kernel. I was right. The most current kernel, which has been installed, was version 4.15.0-50. The previous one (which still is available via GRUB) was version 4.15.0-48. I tried that version, and the problem went away. I'm using Kubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: v 1488 F pulseaudio /dev/snd/controlC1: v 1488 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 3 21:34:57 2019 HibernationDevice: RESUME=UUID=94cdbaee-30e1-44b4-aa58-3de0b89bddf3 InstallationDate: Installed on 2018-10-05 (241 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 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.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name 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/1831494/+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 1824879] Re: linux-azure: Add the Catapult FPGA Driver
** Changed in: linux-azure (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1824879 Title: linux-azure: Add the Catapult FPGA Driver Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure source package in Disco: Fix Committed Bug description: [Impact] Add the Catapult FPGA Driver to the custom linux-azure kernel while a version is not available upstream. [Test Case] The catapult driver must be present as a module in the linux-modules package (not in the linux-modules-extra). [Regression Potential] Low risk of regression since that's a new driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1824879/+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 1827460] Re: [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep in kernel 4.15.0-48.51-generic (but v4.15.0-47.50 works).
Thank you for posting such a great blog! I found your website perfect for my needs. It contains wonderful and helpful posts. Keep up the good work. Thank you for this wonderful Blog! https://www.canonprintersupport247.com/blog/how-to-fix-error-5200-in-canon-printers/;>canon printer error 5200 Call us : Toll-Free : USA: +1-888-633-7151 UK: +44-808-164-5280 -- 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/1827460 Title: [Lenovo IdeaPad 330-15IGM] No sound at all after resuming from sleep in kernel 4.15.0-48.51-generic (but v4.15.0-47.50 works). Status in linux package in Ubuntu: Confirmed Bug description: My Lenovo ideapad 330 laptop with Ubuntu 18.04 sounds works fine initially. However, when I close it down (to sleep) and then return, all the sound disappears. The only way to get back the sound is to restart the laptop. The issue seem to start after a recent automatic update. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rickodesea 1545 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 2 22:49:12 2019 InstallationDate: Installed on 2019-03-28 (36 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1139 F pulseaudio rickodesea 1545 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7XCN29WW 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 ideapad 330-15IGM dmi.modalias: dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM: dmi.product.family: ideapad 330-15IGM dmi.product.name: 81D1 dmi.product.version: Lenovo ideapad 330-15IGM dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rickodesea 1519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-03-28 (37 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 81D1 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.15.0-47-generic root=UUID=a88315b7-573d-4436-b91a-79b15c95e85c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-generic N/A linux-backports-modules-4.15.0-47-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 7XCN29WW 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 ideapad 330-15IGM dmi.modalias: dmi:bvnLENOVO:bvr7XCN29WW:bd12/18/2018:svnLENOVO:pn81D1:pvrLenovoideapad330-15IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IGM: dmi.product.family: ideapad 330-15IGM dmi.product.name: 81D1 dmi.product.version: Lenovo ideapad 330-15IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827460/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1769391] Re: 18.04 Install, not detecting bluetooth
Does this issue still happen? -- 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/1769391 Title: 18.04 Install, not detecting bluetooth Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Incomplete Bug description: tyoma@HP-Pavilion-g7-Notebook-PC:~$ lspci -knn | grep Net -A3; lsusb 01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter [103c:1785] Kernel driver in use: ath9k Kernel modules: ath9k 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 05) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 004: ID 0cf3:311d Atheros Communications, Inc. Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 058f:a001 Alcor Micro Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 0e8f:00a7 GreenAsia Inc. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub tyoma@HP-Pavilion-g7-Notebook-PC:~$ 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no tyoma@HP-Pavilion-g7-Notebook-PC:~$ sudo /etc/init.d/bluetooth start [ ok ] Starting bluetooth (via systemctl): bluetooth.service. tyoma@HP-Pavilion-g7-Notebook-PC:~$ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:6 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0 commands:6 errors:5 Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: SLAVE ACCEPT tyoma@HP-Pavilion-g7-Notebook-PC:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1769391/+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 1829220] Re: Add in-kernel support for Realtek 8821CE WiFi device
Will use DKMS instead. ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Won't Fix -- 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/1829220 Title: Add in-kernel support for Realtek 8821CE WiFi device Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: [Impact] There's no in-kernel support for rtl8821ce. [Fix] Include the driver to kernel. [Test Case] The basic function like scan, connect and transmit packet works. [Regression Potential] None. It's a new driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829220/+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 1812014] Re: keyboard not responding after suspend after some time
[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Expired -- 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/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in upower package in Ubuntu: Expired Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1823146] Re: network namespaces error
[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/1823146 Title: network namespaces error Status in linux package in Ubuntu: Expired Bug description: Hi, I have ubuntu 18.04 server. I have installed iproute2 pkg '4.15.0-2ubuntu1' . When I try creating a network namespace with the command "ip netns add test", the command hangs and never completes. --- root@b1v:~# uname -a Linux b1v 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@b1v:~# --- I took a strace and it hangs at a point when the command hangs. I have attached the strace file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823146/+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 1812014] Re: keyboard not responding after suspend after some time
[Expired for upower (Ubuntu) because there has been no activity for 60 days.] ** Changed in: upower (Ubuntu) Status: Incomplete => Expired -- 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/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in upower package in Ubuntu: Expired Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1812014] Re: keyboard not responding after suspend after some time
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Expired Status in nvidia-graphics-drivers-390 package in Ubuntu: Expired Status in upower package in Ubuntu: Expired Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1813883] Re: reuseport_bpf in net from kernel_selftests failed to build on X-4.15
** Also affects: linux-azure (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/1813883 Title: reuseport_bpf in net from kernel_selftests failed to build on X-4.15 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: New Bug description: make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' gcc -Wall -Wl,--no-as-needed -O2 -g -I../../../../usr/include/ reuseport_bpf.c -o /home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf ../lib.mk:109: recipe for target '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf' failed make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' Makefile:72: recipe for target 'all' failed make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' stderr: reuseport_bpf.c: In function ‘attach_ebpf’: reuseport_bpf.c:126:33: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first use in this function) if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd, ^ reuseport_bpf.c:126:33: note: each undeclared identifier is reported only once for each function it appears in reuseport_bpf.c: In function ‘attach_cbpf’: reuseport_bpf.c:148:33: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first use in this function) if (setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , sizeof(p))) ^ reuseport_bpf.c: In function ‘test_filter_no_reuseport’: reuseport_bpf.c:378:34: error: ‘SO_ATTACH_REUSEPORT_EBPF’ undeclared (first use in this function) if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_EBPF, _fd, ^ reuseport_bpf.c:383:34: error: ‘SO_ATTACH_REUSEPORT_CBPF’ undeclared (first use in this function) if (!setsockopt(fd, SOL_SOCKET, SO_ATTACH_REUSEPORT_CBPF, , ^ make[1]: *** [/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/reuseport_bpf] Error 1 make: *** [all] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1813883/+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 1831536] 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 1831536 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/1831536 Title: crash with "Data Access Out of Range" when using nx-842 zswap on POWER9 Status in linux package in Ubuntu: Incomplete Bug description: On my two socket POWER9 system (powernv) with 842 zwap set up, I recently got a crash with the Ubuntu kernel (I haven't tried with upstream, and this is the first time the system has died like this, so I'm not sure how repeatable it is). [2.891463] zswap: loaded using pool 842-nx/zbud ... [15626.124646] nx_compress_powernv: ERROR: CSB still not valid after 500 us, giving up : 00 00 00 00 [16868.932913] Unable to handle kernel paging request for data at address 0x6655f67da816cdb8 [16868.933726] Faulting instruction address: 0xc0391600 cpu 0x68: Vector: 380 (Data Access Out of Range) at [c01c9d98b9a0] pc: c0391600: kmem_cache_alloc+0x2e0/0x340 lr: c03915ec: kmem_cache_alloc+0x2cc/0x340 sp: c01c9d98bc20 msr: 9280b033 dar: 6655f67da816cdb8 current = 0xc01ad43cb400 paca= 0xcfac7800 softe: 0irq_happened: 0x01 pid = 8319, comm = make Linux version 4.15.0-50-generic (buildd@bos02-ppc64el-006) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #54-Ubuntu SMP Mon May 6 18:55:18 UTC 2019 (Ubuntu 4.15.0-50.54-generic 4.15.18) 68:mon> t [c01c9d98bc20] c03914d4 kmem_cache_alloc+0x1b4/0x340 (unreliable) [c01c9d98bc80] c03b1e14 __khugepaged_enter+0x54/0x220 [c01c9d98bcc0] c010f0ec copy_process.isra.5.part.6+0xebc/0x1a10 [c01c9d98bda0] c010fe4c _do_fork+0xec/0x510 [c01c9d98be30] c000b584 ppc_clone+0x8/0xc --- Exception: c00 (System Call) at 7afe9daf87f4 SP (7fffca606880) is in userspace So, it looks like there could be a problem in the error path, plausibly fixed by this patch: commit 656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca5 Author: Haren Myneni Date: Wed Jun 13 00:32:40 2018 -0700 crypto/nx: Initialize 842 high and normal RxFIFO control registers NX increments readOffset by FIFO size in receive FIFO control register when CRB is read. But the index in RxFIFO has to match with the corresponding entry in FIFO maintained by VAS in kernel. Otherwise NX may be processing incorrect CRBs and can cause CRB timeout. VAS FIFO offset is 0 when the receive window is opened during initialization. When the module is reloaded or in kexec boot, readOffset in FIFO control register may not match with VAS entry. This patch adds nx_coproc_init OPAL call to reset readOffset and queued entries in FIFO control register for both high and normal FIFOs. Signed-off-by: Haren Myneni [mpe: Fixup uninitialized variable warning] Signed-off-by: Michael Ellerman $ git describe --contains 656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca5 v4.19-rc1~24^2~50 Which was never backported to any stable release, so probably needs to be for v4.14 through v4.18. Notably, Ubuntu is on v4.15 and it doesn't seem to have picked up the patch. Reported to upstream (and there may be further discussion) over at https://lists.ozlabs.org/pipermail/linuxppc-dev/2019-June/191438.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831536/+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 1831536] [NEW] crash with "Data Access Out of Range" when using nx-842 zswap on POWER9
Public bug reported: On my two socket POWER9 system (powernv) with 842 zwap set up, I recently got a crash with the Ubuntu kernel (I haven't tried with upstream, and this is the first time the system has died like this, so I'm not sure how repeatable it is). [2.891463] zswap: loaded using pool 842-nx/zbud ... [15626.124646] nx_compress_powernv: ERROR: CSB still not valid after 500 us, giving up : 00 00 00 00 [16868.932913] Unable to handle kernel paging request for data at address 0x6655f67da816cdb8 [16868.933726] Faulting instruction address: 0xc0391600 cpu 0x68: Vector: 380 (Data Access Out of Range) at [c01c9d98b9a0] pc: c0391600: kmem_cache_alloc+0x2e0/0x340 lr: c03915ec: kmem_cache_alloc+0x2cc/0x340 sp: c01c9d98bc20 msr: 9280b033 dar: 6655f67da816cdb8 current = 0xc01ad43cb400 paca= 0xcfac7800 softe: 0irq_happened: 0x01 pid = 8319, comm = make Linux version 4.15.0-50-generic (buildd@bos02-ppc64el-006) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #54-Ubuntu SMP Mon May 6 18:55:18 UTC 2019 (Ubuntu 4.15.0-50.54-generic 4.15.18) 68:mon> t [c01c9d98bc20] c03914d4 kmem_cache_alloc+0x1b4/0x340 (unreliable) [c01c9d98bc80] c03b1e14 __khugepaged_enter+0x54/0x220 [c01c9d98bcc0] c010f0ec copy_process.isra.5.part.6+0xebc/0x1a10 [c01c9d98bda0] c010fe4c _do_fork+0xec/0x510 [c01c9d98be30] c000b584 ppc_clone+0x8/0xc --- Exception: c00 (System Call) at 7afe9daf87f4 SP (7fffca606880) is in userspace So, it looks like there could be a problem in the error path, plausibly fixed by this patch: commit 656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca5 Author: Haren Myneni Date: Wed Jun 13 00:32:40 2018 -0700 crypto/nx: Initialize 842 high and normal RxFIFO control registers NX increments readOffset by FIFO size in receive FIFO control register when CRB is read. But the index in RxFIFO has to match with the corresponding entry in FIFO maintained by VAS in kernel. Otherwise NX may be processing incorrect CRBs and can cause CRB timeout. VAS FIFO offset is 0 when the receive window is opened during initialization. When the module is reloaded or in kexec boot, readOffset in FIFO control register may not match with VAS entry. This patch adds nx_coproc_init OPAL call to reset readOffset and queued entries in FIFO control register for both high and normal FIFOs. Signed-off-by: Haren Myneni [mpe: Fixup uninitialized variable warning] Signed-off-by: Michael Ellerman $ git describe --contains 656ecc16e8fc2ab44b3d70e3fcc197a7020d0ca5 v4.19-rc1~24^2~50 Which was never backported to any stable release, so probably needs to be for v4.14 through v4.18. Notably, Ubuntu is on v4.15 and it doesn't seem to have picked up the patch. Reported to upstream (and there may be further discussion) over at https://lists.ozlabs.org/pipermail/linuxppc-dev/2019-June/191438.html ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 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/1831536 Title: crash with "Data Access Out of Range" when using nx-842 zswap on POWER9 Status in linux package in Ubuntu: Incomplete Bug description: On my two socket POWER9 system (powernv) with 842 zwap set up, I recently got a crash with the Ubuntu kernel (I haven't tried with upstream, and this is the first time the system has died like this, so I'm not sure how repeatable it is). [2.891463] zswap: loaded using pool 842-nx/zbud ... [15626.124646] nx_compress_powernv: ERROR: CSB still not valid after 500 us, giving up : 00 00 00 00 [16868.932913] Unable to handle kernel paging request for data at address 0x6655f67da816cdb8 [16868.933726] Faulting instruction address: 0xc0391600 cpu 0x68: Vector: 380 (Data Access Out of Range) at [c01c9d98b9a0] pc: c0391600: kmem_cache_alloc+0x2e0/0x340 lr: c03915ec: kmem_cache_alloc+0x2cc/0x340 sp: c01c9d98bc20 msr: 9280b033 dar: 6655f67da816cdb8 current = 0xc01ad43cb400 paca= 0xcfac7800 softe: 0irq_happened: 0x01 pid = 8319, comm = make Linux version 4.15.0-50-generic (buildd@bos02-ppc64el-006) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #54-Ubuntu SMP Mon May 6 18:55:18 UTC 2019 (Ubuntu 4.15.0-50.54-generic 4.15.18) 68:mon> t [c01c9d98bc20] c03914d4 kmem_cache_alloc+0x1b4/0x340 (unreliable) [c01c9d98bc80] c03b1e14 __khugepaged_enter+0x54/0x220 [c01c9d98bcc0] c010f0ec copy_process.isra.5.part.6+0xebc/0x1a10 [c01c9d98bda0] c010fe4c _do_fork+0xec/0x510 [c01c9d98be30] c000b584 ppc_clone+0x8/0xc ---
[Kernel-packages] [Bug 1830792] Re: [i915] Rotated display is overscaled and overdrawn
... then if the new kernel log continues to show similar errors we will have at least narrowed this bug down to the kernel (or a hardware/connection fault). -- 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/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1830792] Re: [i915] Rotated display is overscaled and overdrawn
Thanks for your efforts. If you feel you have checked the connections thoroughly then the next step is to wait until the problem happens again and then run: dmesg > newdmesg.txt and send us the file 'newdmesg.txt'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
@Thorsten Synaptics engineer wants to take time to review it. I had pong him again. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None
[Kernel-packages] [Bug 1820666] Re: wifi disconnects when a device connects with bluetooth to the computer
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1820666 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** 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/1820666 Title: wifi disconnects when a device connects with bluetooth to the computer Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Incomplete Bug description: When a device connects to the computer using Bluetooth the Wi-Fi disconnects for some reason. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1820666/+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 1769391] Re: 18.04 Install, not detecting bluetooth
** No longer affects: bluez (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1769391 Title: 18.04 Install, not detecting bluetooth Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Incomplete Bug description: tyoma@HP-Pavilion-g7-Notebook-PC:~$ lspci -knn | grep Net -A3; lsusb 01:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01) Subsystem: Hewlett-Packard Company AR9485 Wireless Network Adapter [103c:1785] Kernel driver in use: ath9k Kernel modules: ath9k 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller [10ec:8136] (rev 05) Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 004: ID 0cf3:311d Atheros Communications, Inc. Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 0518:0001 EzKEY Corp. USB to PS2 Adaptor v1.09 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 003: ID 058f:a001 Alcor Micro Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 0e8f:00a7 GreenAsia Inc. Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub tyoma@HP-Pavilion-g7-Notebook-PC:~$ 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no tyoma@HP-Pavilion-g7-Notebook-PC:~$ sudo /etc/init.d/bluetooth start [ ok ] Starting bluetooth (via systemctl): bluetooth.service. tyoma@HP-Pavilion-g7-Notebook-PC:~$ hciconfig -a hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:6 acl:0 sco:0 events:1 errors:0 TX bytes:3 acl:0 sco:0 commands:6 errors:5 Features: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Packet type: DM1 DH1 HV1 Link policy: Link mode: SLAVE ACCEPT tyoma@HP-Pavilion-g7-Notebook-PC:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1769391/+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 1812310] Re: No more sound on lenovo R61i booting MATE 16.04
** Changed in: pulseaudio (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/1812310 Title: No more sound on lenovo R61i booting MATE 16.04 Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I was able to listen to a YouTube video from the laptop when booting Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04 Thanks for your consideration, Abu Billy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1812310/+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 1831490] 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 1831490 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: 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/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable?
[Kernel-packages] [Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation
Can you run apport-collect 1831490 on this machine to collect additional logs and data? Thanks ** 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/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB (UM) 835*8kB
[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls fails
affects linux-oem-osp1 5.0.0-1008.9 -- 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/1819116 Title: sync_file_range02 in ubuntu_ltp_syscalls fails Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-gke source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-aws source package in Cosmic: New Status in linux-azure source package in Cosmic: New Status in linux source package in Disco: Incomplete Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: New Bug description: syslog output attached as attachment. <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_supported_fs_types.c:72: INFO: Kernel supports ext2 tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext3 tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext4 tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:72: INFO: Kernel supports xfs tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports btrfs tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports vfat tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:72: INFO: Kernel supports ntfs tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist tst_test.c:1157: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on vfat tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ntfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts='' The partition start sector was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. safe_macros.c:739: INFO: Trying FUSE... tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:56: FAIL: Synced 0, expected 33554432 Summary: passed 6 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=11 termination_type=exited termination_id=1 corefile=no cutime=10 cstime=157 <<>> INFO: ltp-pan reported some tests FAIL LTP Version: 20190115 ### Done executing testcases. LTP Version: 20190115 ### ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8
Re: [Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors
On Mon, Jun 03, 2019 at 12:26:44PM -, Frank van Wensveen wrote: > OK. The "modinfo -F" command you gave me returns a list of files: > > ath10k/QCA9377/hw1.0/board.bin > ath10k/QCA9377/hw1.0/firmware-5.bin > ath10k/QCA6174/hw3.0/board-2.bin > ath10k/QCA6174/hw3.0/board.bin > ath10k/QCA6174/hw3.0/firmware-6.bin > ath10k/QCA6174/hw3.0/firmware-5.bin > ath10k/QCA6174/hw3.0/firmware-4.bin > ath10k/QCA6174/hw2.1/board-2.bin > ath10k/QCA6174/hw2.1/board.bin > ath10k/QCA6174/hw2.1/firmware-5.bin > ath10k/QCA6174/hw2.1/firmware-4.bin > ath10k/QCA9887/hw1.0/board-2.bin > ath10k/QCA9887/hw1.0/board.bin > ath10k/QCA9887/hw1.0/firmware-5.bin > ath10k/QCA988X/hw2.0/board-2.bin > ath10k/QCA988X/hw2.0/board.bin > ath10k/QCA988X/hw2.0/firmware-5.bin > ath10k/QCA988X/hw2.0/firmware-4.bin > ath10k/QCA988X/hw2.0/firmware-3.bin > ath10k/QCA988X/hw2.0/firmware-2.bin > > but not all these files exist in the updated firmware build I downloaded > as per Kai-Heng Feng's instructions above. It's possible not all the files will be there. I would do something like this: $ sudo mv /lib/firmware/ath10k /lib/firmware/ath10k.bak $ sudo cp -r /ath10k /lib/firmware Then when you're finished you can restore the old files: $ sudo rm -r /lib/firmware/ath10k $ sudo mv /lib/firmware/ath10k.bak /lib/firmware/ath10k > And in the directory you had > me check are only *.ko files. So I'm not sure what to replace with what > here. Firmware files are located under /lib/firmware. -- 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/1830350 Title: System freezes repeatedly for several seconds; wifi driver related errors Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: I updated my system about a month ago (Fri 26 April 2019). This was the first update in several weeks and installed fresh versions of a whole truck load of applications including a kernel update. Since this latest bunch of updates the system freezes for a few seconds at regular intervals. Not fatal, but very annoying. Output from "journalctl -f" shows the following errors occurring at the same time as these freezes: May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw scan: -110 Corresponding lines in /var/log/syslog: May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record for fe80::424:c75b:2a2d:52e2 on wlp3s0.*. May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for fe80::424:c75b:2a2d:52e2 on wlp3s0. May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: failed to start hw scan: -110 I do note the interval between the avahi-daemon entry and the subsequent errors related to the wireless network interface, but the former precede the latter consistently in syslog, suggesting they may be related, which is why I'm including it in this report. The freezes last a few seconds. Keyboard input is preserved at this time and typed input appears after the freeze is resolved. Mouse cursor continues to move during freezes but mouse clicks are only processed after the freeze is resolved, i.e. the result of the mouse click is suspended (e.g. buffered) until the system becomes responsive again. For example, clicking on a window during the freeze will focus that window after the freeze has been resolved. The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk: 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Output of lsb_release -rd: Description: Ubuntu 18.04.2 LTS Release: 18.04 Output of uname -a: Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux As already said, this is a new issue that has began occurring only after the recent batch of updates that included a kernel update. I reported the bug (maybe in the wrong place) but so far I have received no response. I've lived with this for a month or so hoping that further updates would fix the problem but it still persists. Installing the latest firmware update (14 Mar 2019) has no effect. No other changes were made to either hardware or OS configuration.
[Kernel-packages] [Bug 1828868] Re: crashdump fails on HiSilicon D06
** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Cosmic) 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/1828868 Title: crashdump fails on HiSilicon D06 Status in linux package in Ubuntu: In Progress 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: Fix Committed Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) Add "arm_smmu_v3.disable_bypass=1" to the kernel command line sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger (Note to self - the following is needed on our systems w/ Mellanox adapters: ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service module_blacklist=mlx5_core") [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+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 1829812] Re: Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to build on disco
affects linux-oem-osp1 5.0.0-1008.9 ** Tags added: linux-oem-osp1 -- 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/1829812 Title: Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to build on disco Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: In Progress Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: New Bug description: [SRU Justification] == Impact == Some upstream stable change modified the bpf selftest to use a function that probes for existing eBPF program types. However that function does not exist in the 5.0 kernel sources. == Fix == Picking two additional changes from upstream (which only modify the tools sub-directory), allows to compile the selftests again. == Risk of Regression == Since the kernel itself is not touched, the risk is low. == Testcase == With build-essential installed and the Disco kernel tree cloned: cd tools/testing/selftests/ TARGET=net make --- This test will failed to build on 5.0.0-16 Disco. 5.0.0-16 Disco + 5.0.0-15 source code - build OK 5.0.0-16 Disco + 5.0.0-16 source code - Failed Bisect shows this one e38969c9 (selftests/bpf: skip verifier tests for unsupported program types) in our tree is the cause (upstream commit: 8184d44c) Which uses a "recently introduced bpf_probe_prog_type()" to skip test. And we don't have it implemented. make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' gcc -o /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read -static urandom_read.c -Wl,--build-id make -C ../../../lib/bpf OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/ make[2]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf' Auto-detecting system features: ...libelf: [ on ] ... bpf: [ on ] HOSTCC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep.o HOSTLD /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep-in.o LINK /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/nlattr.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/btf.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf_errno.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/str_error.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/netlink.o CC /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_prog_linfo.o LD /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf-in.o LINK /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a LINK /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.so LINK /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_libbpf make[2]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf' gcc -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf -I../../../../include/generated -I../../../includetest_verifier.c /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a -lcap -lelf -lrt -lpthread -o /home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_verifier make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests' stderr: Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs from latest version at 'include/uapi/linux/if_link.h' test_verifier.c: In function ‘do_test_single’: test_verifier.c:15951:22: warning: implicit declaration of function ‘bpf_probe_prog_type’; did you mean ‘bpf_program__set_type’?
[Kernel-packages] [Bug 1828868] Re: crashdump fails on HiSilicon D06
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Description changed: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) + Add "arm_smmu_v3.disable_bypass=1" to the kernel command line sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger + + (Note to self - the following is needed on our systems w/ Mellanox adapters: + ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools + KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service module_blacklist=mlx5_core") [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. -- 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/1828868 Title: crashdump fails on HiSilicon D06 Status in linux package in Ubuntu: In Progress 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: Fix Committed Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) Add "arm_smmu_v3.disable_bypass=1" to the kernel command line sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger (Note to self - the following is needed on our systems w/ Mellanox adapters: ubuntu@d06-3:~$ grep blacklist /etc/default/kdump-tools KDUMP_CMDLINE_APPEND="nr_cpus=1 systemd.unit=kdump-tools-dump.service module_blacklist=mlx5_core") [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+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 1831482] Re: VIMC module not available (CONFIG_VIDEO_VIMC not set)
Log files are irrelevant. This is not a bug in the running kernel, just an issue with the kernel config used to build the modules. Issue changed to confirmed. ** 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/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) Status in linux package in Ubuntu: Confirmed Bug description: The Multimedia VIMC module provides a test interface for the linux- media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+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 1831494] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) 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/1831494 Title: USB-related kernel problem with scanner Status in linux package in Ubuntu: Confirmed Bug description: My Canon CanoScan LiDE 220 scanner had worked reasonably well, until a new kernel has been installed. It went into stop-and-go mode, and made funny noises. This is worse in higher resolutions. I had a notion that it might be a problem with USB, which in turn resides in the kernel. I was right. The most current kernel, which has been installed, was version 4.15.0-50. The previous one (which still is available via GRUB) was version 4.15.0-48. I tried that version, and the problem went away. I'm using Kubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: v 1488 F pulseaudio /dev/snd/controlC1: v 1488 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 3 21:34:57 2019 HibernationDevice: RESUME=UUID=94cdbaee-30e1-44b4-aa58-3de0b89bddf3 InstallationDate: Installed on 2018-10-05 (241 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 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.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name 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/1831494/+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 1831494] [NEW] USB-related kernel problem with scanner
Public bug reported: My Canon CanoScan LiDE 220 scanner had worked reasonably well, until a new kernel has been installed. It went into stop-and-go mode, and made funny noises. This is worse in higher resolutions. I had a notion that it might be a problem with USB, which in turn resides in the kernel. I was right. The most current kernel, which has been installed, was version 4.15.0-50. The previous one (which still is available via GRUB) was version 4.15.0-48. I tried that version, and the problem went away. I'm using Kubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: v 1488 F pulseaudio /dev/snd/controlC1: v 1488 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 3 21:34:57 2019 HibernationDevice: RESUME=UUID=94cdbaee-30e1-44b4-aa58-3de0b89bddf3 InstallationDate: Installed on 2018-10-05 (241 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 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.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware 1.173.6 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1503:bd11/14/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78LLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1831494 Title: USB-related kernel problem with scanner Status in linux package in Ubuntu: New Bug description: My Canon CanoScan LiDE 220 scanner had worked reasonably well, until a new kernel has been installed. It went into stop-and-go mode, and made funny noises. This is worse in higher resolutions. I had a notion that it might be a problem with USB, which in turn resides in the kernel. I was right. The most current kernel, which has been installed, was version 4.15.0-50. The previous one (which still is available via GRUB) was version 4.15.0-48. I tried that version, and the problem went away. I'm using Kubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: v 1488 F pulseaudio /dev/snd/controlC1: v 1488 F pulseaudio CurrentDesktop: KDE Date: Mon Jun 3 21:34:57 2019 HibernationDevice: RESUME=UUID=94cdbaee-30e1-44b4-aa58-3de0b89bddf3 InstallationDate: Installed on 2018-10-05 (241 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-48-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=1 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.15.0-48-generic N/A linux-backports-modules-4.15.0-48-generic N/A linux-firmware
Re: [Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
On Mon, Jun 3, 2019 at 2:05 PM Andrey Grebennikov <
agrebennikov1...@gmail.com> wrote:
> Is there an estimate on getting this package in bionic-updates please?
>
We are starting an SRU of curtin this week. SRU's take at least 7 days
from when they hit -proposed
possibly longer depending on test results.
I should have something up in -proposed this week and we'll go from there
on testing.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1796292
>
> Title:
> Tight timeout for bcache removal causes spurious failures
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
>
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1796292] Re: Tight timeout for bcache removal causes spurious failures
Is there an estimate on getting this package in bionic-updates please?
--
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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+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 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
This appears related: https://bugzilla.kernel.org/show_bug.cgi?id=199689 My SSD is model KXG50ZNV1T02, firmware revision AADA4102. Aside: can launchpad comments be edited? ** Bug watch added: Linux Kernel Bug Tracker #199689 https://bugzilla.kernel.org/show_bug.cgi?id=199689 -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep Status in linux package in Ubuntu: Confirmed Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
I'm not familiar enough with launchpad to know that I could change the bug status to "Confirmed". Please correct me if that change is inappropriate. I have an XPS 9370. This is definitely a major issue for me. -- 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep Status in linux package in Ubuntu: Confirmed Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep
I disagree with the "Incomplete" status of this bug, specifically because it is now Expired. This bug is infuriating. Any time I reboot, if I forget to cat deep to /sys/power/mem_sleep, my laptop is dead the next time I go to use it. The battery lasts for days when using "deep" sleep. In s2idle, it actually heats up in my backpack, and I worry it may overheat if I don't notice it. I understand that the bug may not be fully understood yet, but allowing the bug to expire is entirely inappropriate. Even if only for this one reason, it should not be "Incomplete". A proper s2idle would be wonderful, but until then, deep should be the default. ** Changed in: linux (Ubuntu) Status: Expired => Incomplete ** 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/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep Status in linux package in Ubuntu: Confirmed Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1831482] 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 1831482 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/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) Status in linux package in Ubuntu: Incomplete Bug description: The Multimedia VIMC module provides a test interface for the linux- media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+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 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot
I've posted https://devtalk.nvidia.com/default/topic/1054978/linux /ubuntu-boot-delayed-by-30s-due-to-non-functional-rtx2060-usb- controller/ -- 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/1830905 Title: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot Status in linux package in Ubuntu: Confirmed Bug description: From dmesg: [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0 [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC bug?) status = 0x801 [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 took 5615333 usecs [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using xhci_hcd [ 10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.10 [ 10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110 [ 34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered [ 34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110 [ 34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110 $ lspci -k -s :07:00 07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia 07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller 07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C Port Policy Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy Controller Kernel driver in use: nvidia-gpu Kernel modules: i2c_nvidia_gpu ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 4470 F pulseaudio /dev/snd/controlC1: daniel 4470 F pulseaudio /dev/snd/controlC2: daniel 4470 F pulseaudio CurrentDesktop: i3 Date: Wed May 29 09:36:51 2019 InstallationDate: Installed on 2019-05-07 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.179 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-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.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830905/+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 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-
** Attachment added: "arecord-L.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+attachment/5268566/+files/arecord-L.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831301 Title: sound doesn't works in both kernel. no one cards is recognize by system- Status in linux package in Ubuntu: Confirmed Bug description: . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 1 04:26:10 2019 InstallationDate: Installed on 2019-04-03 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+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 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-
** Attachment added: "aplay-L.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+attachment/5268564/+files/aplay-L.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831301 Title: sound doesn't works in both kernel. no one cards is recognize by system- Status in linux package in Ubuntu: Confirmed Bug description: . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 1 04:26:10 2019 InstallationDate: Installed on 2019-04-03 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+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 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-
** Attachment added: "arecord-l.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+attachment/5268565/+files/arecord-l.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831301 Title: sound doesn't works in both kernel. no one cards is recognize by system- Status in linux package in Ubuntu: Confirmed Bug description: . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 1 04:26:10 2019 InstallationDate: Installed on 2019-04-03 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+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 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-
** Attachment added: "aplay-l.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+attachment/5268563/+files/aplay-l.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831301 Title: sound doesn't works in both kernel. no one cards is recognize by system- Status in linux package in Ubuntu: Confirmed Bug description: . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 1 04:26:10 2019 InstallationDate: Installed on 2019-04-03 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+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 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
FYI, please note that seccomp 2.4.1 was pushed to bionic in
https://usn.ubuntu.com/4001-1/ on 2019/05/30. It shouldn't affect this
bug report AFAICT because while the 2.4.1 Ubuntu packaging drops these
patches, the upstream commits for lp-1815415-arch-update-syscalls-for-
Linux-4.9.patch and lp-1815415-update-the-syscall-tables-to-4.10.patch
are both included in 2.4.1. Based on the 2.4.1 changelog, nothing else
was changed in this area, so 2.4.1 should be affected in the same way as
2.3.1-2.1ubuntu4.1.
--
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/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Incomplete
Status in linux source package in Bionic:
In Progress
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+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 1831482] [NEW] VIMC module not available (CONFIG_VIDEO_VIMC not set)
Public bug reported: The Multimedia VIMC module provides a test interface for the linux-media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. ** 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/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) Status in linux package in Ubuntu: New Bug description: The Multimedia VIMC module provides a test interface for the linux- media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+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 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls fails
affects bionic linux-gke 4.15.0-1033.35 ** Also affects: linux-gke (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-gke (Ubuntu Cosmic) ** No longer affects: linux-gke (Ubuntu Disco) -- 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/1819116 Title: sync_file_range02 in ubuntu_ltp_syscalls fails Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-gke source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-aws source package in Cosmic: New Status in linux-azure source package in Cosmic: New Status in linux source package in Disco: Incomplete Status in linux-aws source package in Disco: New Status in linux-azure source package in Disco: New Bug description: syslog output attached as attachment. <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_supported_fs_types.c:72: INFO: Kernel supports ext2 tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext3 tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist tst_supported_fs_types.c:72: INFO: Kernel supports ext4 tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist tst_supported_fs_types.c:72: INFO: Kernel supports xfs tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports btrfs tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist tst_supported_fs_types.c:72: INFO: Kernel supports vfat tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported tst_supported_fs_types.c:72: INFO: Kernel supports ntfs tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist tst_test.c:1157: INFO: Testing on ext2 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext3 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ext4 tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on btrfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on vfat tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts='' tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:54: PASS: Test file range synced to device tst_test.c:1157: INFO: Testing on ntfs tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts='' The partition start sector was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of sectors per track was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. The number of heads was not specified for /dev/loop2 and it could not be obtained automatically. It has been set to 0. To boot from a device, Windows needs the 'partition start sector', the 'sectors per track' and the 'number of heads' to be set. Windows will not be able to boot from this device. safe_macros.c:739: INFO: Trying FUSE... tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s sync_file_range02.c:56: FAIL: Synced 0, expected 33554432 Summary: passed 6 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=11 termination_type=exited termination_id=1 corefile=no cutime=10 cstime=157 <<>> INFO: ltp-pan reported some tests FAIL LTP Version: 20190115 ### Done executing testcases. LTP Version: 20190115
[Kernel-packages] [Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
Filofel, Would you mind to send a kernel patch to make the change persistent? -- 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/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+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 1831128] Re: ACPI error on boot
Does kernel parameter "ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=0:00.2" help? -- 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/1831128 Title: ACPI error on boot Status in linux package in Ubuntu: Fix Committed Bug description: i have a laptop with ryzen 5 2500u processor.and i got this error when boot, i tried ubuntu 16.04,18.04,19.04 and the result is same. system stuck on acpi error.i tried to disable it then the system is shut down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831128/+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 1824136] Re: ubuntu_k8s_unit_tests failed with GCP
also affects linux-gke 4.15.0-1033.35
** Tags added: gcp gke
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1824136
Title:
ubuntu_k8s_unit_tests failed with GCP
Status in ubuntu-kernel-tests:
New
Status in linux-signed-gcp package in Ubuntu:
New
Bug description:
There are 3 failures found on Cosmic GCP (n1-highcpu-16)
* k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
* k8s.io/kubernetes/pkg/master
* k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpstream/spdy
[build failed]
Steps to reproduce:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_k8s_unit_tests/control
Error messages:
* k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
--- FAIL: TestUpdateNodeWithMultiplePods (2.56s)
taint_manager_test.go:486: Starting testcase "Pods with different toleration
times are evicted appropriately"
taint_manager_test.go:512: Sleeping for 499.999448ms
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:538: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:512: Sleeping for 594.563805ms
taint_manager_test.go:532: Failed to deleted pod pod2 after 0
taint_manager_test.go:486: Starting testcase "Evict all pods not matching
all taints instantly"
taint_manager_test.go:512: Sleeping for 499.999844ms
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:538: Found not-delete action with verb list. Ignoring.
FAIL
FAIL k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
35.544s
* k8s.io/kubernetes/pkg/master
2019-03-21 16:02:16.793715 I | integration: launching 2444030890339279063
(unix://localhost:24440308903392790630)
2019-03-21 16:02:16.798460 I | etcdserver: name = 2444030890339279063
2019-03-21 16:02:16.798550 I | etcdserver: data dir = /tmp/etcd396328703
2019-03-21 16:02:16.798566 I | etcdserver: member dir =
/tmp/etcd396328703/member
2019-03-21 16:02:16.798576 I | etcdserver: heartbeat = 10ms
2019-03-21 16:02:16.798585 I | etcdserver: election = 100ms
2019-03-21 16:02:16.798594 I | etcdserver: snapshot count = 0
2019-03-21 16:02:16.798635 I | etcdserver: advertise client URLs =
unix://127.0.0.1:2100211086
2019-03-21 16:02:16.798657 I | etcdserver: initial advertise peer URLs =
unix://127.0.0.1:2100111086
2019-03-21 16:02:16.798676 I | etcdserver: initial cluster =
2444030890339279063=unix://127.0.0.1:2100111086
2019-03-21 16:02:16.804030 I | etcdserver: starting member d951fd13cdcf6e11
in cluster b8d26aa038f828d
2019-03-21 16:02:16.804137 I | raft: d951fd13cdcf6e11 became follower at
term 0
2019-03-21 16:02:16.804164 I | raft: newRaft d951fd13cdcf6e11 [peers: [],
term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2019-03-21 16:02:16.804206 I | raft: d951fd13cdcf6e11 became follower at
term 1
2019-03-21 16:02:16.818807 W | auth: simple token is not cryptographically
signed
2019-03-21 16:02:16.822703 I | etcdserver: set snapshot count to default
10
2019-03-21 16:02:16.822805 I | etcdserver: starting server... [version:
3.2.13, cluster version: to_be_decided]
2019-03-21 16:02:16.823182 I | integration: launched 2444030890339279063
(unix://localhost:24440308903392790630)
2019-03-21 16:02:16.825229 I | etcdserver/membership: added member
d951fd13cdcf6e11 [unix://127.0.0.1:2100111086] to cluster b8d26aa038f828d
2019-03-21 16:02:16.885057 I | raft: d951fd13cdcf6e11 is starting a new
election at term 1
2019-03-21 16:02:16.885151 I | raft: d951fd13cdcf6e11 became candidate at
term 2
2019-03-21 16:02:16.885168 I | raft: d951fd13cdcf6e11 received MsgVoteResp
from d951fd13cdcf6e11 at term 2
2019-03-21 16:02:16.885180 I | raft: d951fd13cdcf6e11 became leader at term 2
2019-03-21 16:02:16.885187 I | raft: raft.node: d951fd13cdcf6e11 elected
leader d951fd13cdcf6e11 at term 2
2019-03-21 16:02:16.885759 I | etcdserver: setting up the initial cluster
version to 3.2
2019-03-21 16:02:16.886707 N | etcdserver/membership: set the initial
cluster version to 3.2
2019-03-21 16:02:16.886797 I | etcdserver/api: enabled capabilities for
version 3.2
2019-03-21 16:02:16.886857 I | etcdserver: published
{Name:2444030890339279063 ClientURLs:[unix://127.0.0.1:2100211086]} to cluster
[Kernel-packages] [Bug 1824136] Re: ubuntu_k8s_unit_tests failed with GCP
affects linux-gcp 4.18.0-1012.13~18.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1824136
Title:
ubuntu_k8s_unit_tests failed with GCP
Status in ubuntu-kernel-tests:
New
Status in linux-signed-gcp package in Ubuntu:
New
Bug description:
There are 3 failures found on Cosmic GCP (n1-highcpu-16)
* k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
* k8s.io/kubernetes/pkg/master
* k8s.io/kubernetes/vendor/k8s.io/apimachinery/pkg/util/httpstream/spdy
[build failed]
Steps to reproduce:
sudo apt-get install git python-minimal python-yaml gdb -y
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local
--verbose autotest/client/tests/ubuntu_k8s_unit_tests/control
Error messages:
* k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
--- FAIL: TestUpdateNodeWithMultiplePods (2.56s)
taint_manager_test.go:486: Starting testcase "Pods with different toleration
times are evicted appropriately"
taint_manager_test.go:512: Sleeping for 499.999448ms
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:538: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:512: Sleeping for 594.563805ms
taint_manager_test.go:532: Failed to deleted pod pod2 after 0
taint_manager_test.go:486: Starting testcase "Evict all pods not matching
all taints instantly"
taint_manager_test.go:512: Sleeping for 499.999844ms
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:521: Found not-delete action with verb list. Ignoring.
taint_manager_test.go:538: Found not-delete action with verb list. Ignoring.
FAIL
FAIL k8s.io/kubernetes/pkg/controller/nodelifecycle/scheduler
35.544s
* k8s.io/kubernetes/pkg/master
2019-03-21 16:02:16.793715 I | integration: launching 2444030890339279063
(unix://localhost:24440308903392790630)
2019-03-21 16:02:16.798460 I | etcdserver: name = 2444030890339279063
2019-03-21 16:02:16.798550 I | etcdserver: data dir = /tmp/etcd396328703
2019-03-21 16:02:16.798566 I | etcdserver: member dir =
/tmp/etcd396328703/member
2019-03-21 16:02:16.798576 I | etcdserver: heartbeat = 10ms
2019-03-21 16:02:16.798585 I | etcdserver: election = 100ms
2019-03-21 16:02:16.798594 I | etcdserver: snapshot count = 0
2019-03-21 16:02:16.798635 I | etcdserver: advertise client URLs =
unix://127.0.0.1:2100211086
2019-03-21 16:02:16.798657 I | etcdserver: initial advertise peer URLs =
unix://127.0.0.1:2100111086
2019-03-21 16:02:16.798676 I | etcdserver: initial cluster =
2444030890339279063=unix://127.0.0.1:2100111086
2019-03-21 16:02:16.804030 I | etcdserver: starting member d951fd13cdcf6e11
in cluster b8d26aa038f828d
2019-03-21 16:02:16.804137 I | raft: d951fd13cdcf6e11 became follower at
term 0
2019-03-21 16:02:16.804164 I | raft: newRaft d951fd13cdcf6e11 [peers: [],
term: 0, commit: 0, applied: 0, lastindex: 0, lastterm: 0]
2019-03-21 16:02:16.804206 I | raft: d951fd13cdcf6e11 became follower at
term 1
2019-03-21 16:02:16.818807 W | auth: simple token is not cryptographically
signed
2019-03-21 16:02:16.822703 I | etcdserver: set snapshot count to default
10
2019-03-21 16:02:16.822805 I | etcdserver: starting server... [version:
3.2.13, cluster version: to_be_decided]
2019-03-21 16:02:16.823182 I | integration: launched 2444030890339279063
(unix://localhost:24440308903392790630)
2019-03-21 16:02:16.825229 I | etcdserver/membership: added member
d951fd13cdcf6e11 [unix://127.0.0.1:2100111086] to cluster b8d26aa038f828d
2019-03-21 16:02:16.885057 I | raft: d951fd13cdcf6e11 is starting a new
election at term 1
2019-03-21 16:02:16.885151 I | raft: d951fd13cdcf6e11 became candidate at
term 2
2019-03-21 16:02:16.885168 I | raft: d951fd13cdcf6e11 received MsgVoteResp
from d951fd13cdcf6e11 at term 2
2019-03-21 16:02:16.885180 I | raft: d951fd13cdcf6e11 became leader at term 2
2019-03-21 16:02:16.885187 I | raft: raft.node: d951fd13cdcf6e11 elected
leader d951fd13cdcf6e11 at term 2
2019-03-21 16:02:16.885759 I | etcdserver: setting up the initial cluster
version to 3.2
2019-03-21 16:02:16.886707 N | etcdserver/membership: set the initial
cluster version to 3.2
2019-03-21 16:02:16.886797 I | etcdserver/api: enabled capabilities for
version 3.2
2019-03-21 16:02:16.886857 I | etcdserver: published
{Name:2444030890339279063 ClientURLs:[unix://127.0.0.1:2100211086]} to cluster
b8d26aa038f828d
[restful]
[Kernel-packages] [Bug 1584557] Re: Seagate external drive causes SCSI bus resets when UAS enabled
FWIW, I changed my notebook and reinstalled 18.04.2 64-bit on the new machine. I then plugged my 4 external disks (see comment #6) to the new machine. And much to my dismay, when plugged into USB 3.x ports, the disks didn't mount... It did on USB 2.0 ports, though. Looking at sysdev reminded me of this problem I had experienced in 2016 on the same devices, and the same fix worked just as well: - Creating a "blacklist-uas-on-quirks.conf" in /etc/modprobe.d and - Adding the line options usb-storage quirks=059f:105e:u,059f:107e:u in the file to blacklist uas for the two listed devices and use usb-storage instead. That fixed it for me. -- 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/1584557 Title: Seagate external drive causes SCSI bus resets when UAS enabled Status in linux package in Ubuntu: Confirmed Bug description: Seagate STEA1000400 external USB hard disk (USB ID 0bc2:2322) causes continuous SCSI bus resets by default. As a workaround, disabling UAS causes the device to work fine. To disable UAS, I created a file in /etc/modprobe.d with the following contents: options usb-storage quirks=0bc2:02322:u ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CrashDB: ubuntu Date: Sun May 22 22:02:26 2016 InstallationDate: Installed on 2012-10-07 (1323 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4) PackageArchitecture: all ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-04-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1584557/+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 1830905] Re: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot
> Can you direct me towards the appropriate Nvidia forum to use? https://devtalk.nvidia.com/default/board/98/linux/ > And is there any way I could configure my system to perform that blacklisting > in the meantime? Not really. Module xhci_hcd is built into kernel, so a custom compiled kernel is needed here. -- 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/1830905 Title: Nvidia RTX 2060 USB bus timeouts cause ~30s delay in boot Status in linux package in Ubuntu: Confirmed Bug description: From dmesg: [0.132667] kernel: pci :07:00.1: Linked as a consumer to :07:00.0 [5.882727] kernel: pci :07:00.2: xHCI HW not ready after 5 sec (HC bug?) status = 0x801 [5.882781] kernel: pci :07:00.2: quirk_usb_early_handoff+0x0/0x6a6 took 5615333 usecs [9.984204] kernel: usb 1-7: new full-speed USB device number 4 using xhci_hcd [ 10.308689] kernel: usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b, bcdDevice= 0.10 [ 10.308690] kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 34.654721] kernel: xhci_hcd :07:00.2: can't setup: -110 [ 34.654730] kernel: xhci_hcd :07:00.2: USB bus 3 deregistered [ 34.654769] kernel: xhci_hcd :07:00.2: init :07:00.2 fail, -110 [ 34.654771] kernel: xhci_hcd: probe of :07:00.2 failed with error -110 $ lspci -k -s :07:00 07:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 Kernel driver in use: nvidia Kernel modules: nvidiafb, nouveau, nvidia_drm, nvidia 07:00.1 Audio device: NVIDIA Corporation TU106 High Definition Audio Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 High Definition Audio Controller Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 07:00.2 USB controller: NVIDIA Corporation TU106 USB 3.1 Host Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 USB 3.1 Host Controller 07:00.3 Serial bus controller [0c80]: NVIDIA Corporation TU106 USB Type-C Port Policy Controller (rev a1) Subsystem: Gigabyte Technology Co., Ltd TU106 USB Type-C Port Policy Controller Kernel driver in use: nvidia-gpu Kernel modules: i2c_nvidia_gpu ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 4470 F pulseaudio /dev/snd/controlC1: daniel 4470 F pulseaudio /dev/snd/controlC2: daniel 4470 F pulseaudio CurrentDesktop: i3 Date: Wed May 29 09:36:51 2019 InstallationDate: Installed on 2019-05-07 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.179 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-05-08 (20 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-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.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830905/+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 1828995] Re: POSIX fix for ftrace test in ubuntu_kernel_selftests
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1828995 Title: POSIX fix for ftrace test in ubuntu_kernel_selftests Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: In Progress Bug description: == Justification == There are some non-POSIX implementations in the test script, which will generate some noise in the test reports like: -e -n [1] Basic trace file check -e [PASS] -e -n [2] Basic test for tracers -e [PASS] == Fix == * 4ce55a9c (selftests/ftrace: Replace \e with \033) * 37fb665b (selftests/ftrace: Replace echo -e with printf) These two patches can be cherry-picked into D/E == Test == Tested on a P8 box with Disco, the patched test will print the report in a proper format: [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] == Regression Potential == No regression is expected. This patchset just make sure this test comply with POSIX standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828995/+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 1830934] Re: Disco update: 5.0.12 upstream stable release
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1830934 Title: Disco update: 5.0.12 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Committed 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: 5.0.12 upstream stable release from git://git.kernel.org/ The following patches were applied: * selinux: use kernel linux/socket.h for genheaders and mdp * Revert "ACPICA: Clear status of GPEs before enabling them" * drm/i915: Do not enable FEC without DSC * mm: make page ref count overflow check tighter and more explicit * mm: add 'try_get_page()' helper function * mm: prevent get_user_pages() from overflowing page refcount * fs: prevent page refcount overflow in pipe_buf_get * arm64: dts: renesas: r8a77990: Fix SCIF5 DMA channels * ARM: dts: bcm283x: Fix hdmi hpd gpio pull * s390: limit brk randomization to 32MB * mt76x02: fix hdr pointer in write txwi for USB * mt76: mt76x2: fix external LNA gain settings * mt76: mt76x2: fix 2.4 GHz channel gain settings * net: ieee802154: fix a potential NULL pointer dereference * ieee802154: hwsim: propagate genlmsg_reply return code * Btrfs: fix file corruption after snapshotting due to mix of buffered/DIO writes * net: stmmac: don't set own bit too early for jumbo frames * net: stmmac: fix jumbo frame sending with non-linear skbs * qlcnic: Avoid potential NULL pointer dereference * xsk: fix umem memory leak on cleanup * staging: axis-fifo: add CONFIG_OF dependency * staging, mt7621-pci: fix build without pci support * netfilter: nft_set_rbtree: check for inactive element after flag mismatch * netfilter: bridge: set skb transport_header before entering NF_INET_PRE_ROUTING * netfilter: fix NETFILTER_XT_TARGET_TEE dependencies * netfilter: ip6t_srh: fix NULL pointer dereferences * s390/qeth: fix race when initializing the IP address table * ARM: imx51: fix a leaked reference by adding missing of_node_put * sc16is7xx: missing unregister/delete driver on error in sc16is7xx_init() * serial: ar933x_uart: Fix build failure with disabled console * KVM: arm64: Reset the PMU in preemptible context * arm64: KVM: Always set ICH_HCR_EL2.EN if GICv4 is enabled * KVM: arm/arm64: vgic-its: Take the srcu lock when writing to guest memory * KVM: arm/arm64: vgic-its: Take the srcu lock when parsing the memslots * usb: dwc3: pci: add support for Comet Lake PCH ID * usb: gadget: net2280: Fix overrun of OUT messages * usb: gadget: net2280: Fix net2280_dequeue() * usb: gadget: net2272: Fix net2272_dequeue() * ARM: dts: pfla02: increase phy reset duration * i2c: i801: Add support for Intel Comet Lake * KVM: arm/arm64: Fix handling of stage2 huge mappings * net: ks8851: Dequeue RX packets explicitly * net: ks8851: Reassert reset pin if chip ID check fails * net: ks8851: Delay requesting IRQ until opened * net: ks8851: Set initial carrier state to down * staging: rtl8188eu: Fix potential NULL pointer dereference of kcalloc * staging: rtlwifi: rtl8822b: fix to avoid potential NULL pointer dereference * staging: rtl8712: uninitialized memory in read_bbreg_hdl() * staging: rtlwifi: Fix potential NULL pointer dereference of kzalloc * net: phy: Add DP83825I to the DP83822 driver * net: macb: Add null check for PCLK and HCLK * net/sched: don't dereference a->goto_chain to read the chain index * ARM: dts: imx6qdl: Fix typo in imx6qdl-icore-rqs.dtsi * drm/tegra: hub: Fix dereference before check * NFS: Fix a typo in nfs_init_timeout_values() * net: xilinx: fix possible object reference leak * net: ibm: fix possible object reference leak * net: ethernet: ti: fix possible object reference leak * drm: Fix drm_release() and device unplug * gpio: aspeed: fix a potential NULL pointer dereference * drm/meson: Fix invalid pointer in meson_drv_unbind() * drm/meson: Uninstall IRQ handler * ARM: davinci: fix build failure with allnoconfig * sbitmap: order READ/WRITE freed instance and setting clear bit * staging: vc04_services: Fix an error code in vchiq_probe() * scsi: mpt3sas: Fix kernel panic during expander reset * scsi: aacraid: Insure we don't access PCIe space during AER/EEH * scsi: qla4xxx: fix a potential NULL pointer dereference * usb: usb251xb: fix to avoid potential NULL
[Kernel-packages] [Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** 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 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing - phase-changed: Friday, 31. May 2019 20:32 UTC + phase-changed: Monday, 03. June 2019 15:32 UTC reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present - snap-certification-testing: Ongoing -- testing in progress + snap-release-to-candidate: 'Pending -- snap pc-kernel not in expected channel(s): + arch=amd64:channel=latest/candidate:rev=223 arch=i386:channel=latest/candidate:rev=222' -- 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/1830941 Title: linux: 4.4.0-150.176 -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: Fix Released 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: Fix Released 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 backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Monday, 03. June 2019 15:32 UTC reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present snap-release-to-candidate: 'Pending -- snap pc-kernel not in expected channel(s): arch=amd64:channel=latest/candidate:rev=223 arch=i386:channel=latest/candidate:rev=222' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
any news? Is the patch submission ignored? This bug is still present in 5.1.6 :/ I am using your patch since you published it and it is working great, no issues at all. -- 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/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
This patch is also needed for kernels before 4.18
cd28325249 KVM: VMX: support MSR_IA32_ARCH_CAPABILITIES as a feature
MSR ( 25-6-18)
This patchset populates the structure in arch/x86/kvm/x86.c:
msr_based_features{}
With out this patch, qemu asserts at
kvm_get_supported_feature_msrs(KVMState *s):
assert(msr_list.nmsrs > 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/1828495
Title:
[KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Status in intel:
New
Status in linux package in Ubuntu:
Confirmed
Status in qemu package in Ubuntu:
Triaged
Bug description:
This is a bug.
Test Environment:
Repro Steps:
1. Boot up guest using: -cpu Cascadelake-Server
[root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive
if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu
Cascadelake-Server -serial stdio
char device redirected to /dev/pts/3 (label serial0)
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:ECX [bit 4]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:ECX [bit 4]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:ECX [bit 4]
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:ECX [bit 4]
2. To check CPU ID related to features[FEAT_7_0_EDX]
：CPUID_7_0_EDX_ARCH_CAPABILITIES
Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be
1.
Actual Result:
Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b
ecx=0x0818 edx=0xbc00 (EDX bit 29=1)
Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9
ecx=0x0818 edx=0x8400 (EDX bit 29=0)
Commit:2bdb76c015df7125783d8394d6339d181cb5bc30
Target Kerned: 5.1
Target Release: 19.10
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1828495/+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 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/ZtkqccNY/1077-pc- kernel-440-150176-223 ** Changed in: kernel-sru-workflow/snap-certification-testing 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/1830941 Title: linux: 4.4.0-150.176 -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: Fix Released 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: 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: Fix Released 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 backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Friday, 31. May 2019 20:32 UTC reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present snap-certification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+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 1830929] Re: Disco update: 5.0.11 upstream stable release
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1830929 Title: Disco update: 5.0.11 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Committed 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: 5.0.11 upstream stable release from git://git.kernel.org/ The following patches were applied: * netfilter: nf_tables: bogus EBUSY when deleting set after flush * netfilter: nf_tables: bogus EBUSY in helper removal from transaction * intel_th: gth: Fix an off-by-one in output unassigning * powerpc/vdso32: fix CLOCK_MONOTONIC on PPC64 * ALSA: hda/realtek - Move to ACT_INIT state * fs/proc/proc_sysctl.c: Fix a NULL pointer dereference * block, bfq: fix use after free in bfq_bfqq_expire * cifs: fix memory leak in SMB2_read * cifs: fix page reference leak with readv/writev * cifs: do not attempt cifs operation on smb2+ rename error * tracing: Fix a memory leak by early error exit in trace_pid_write() * tracing: Fix buffer_ref pipe ops * crypto: xts - Fix atomic sleep when walking skcipher * crypto: lrw - Fix atomic sleep when walking skcipher * gpio: eic: sprd: Fix incorrect irq type setting for the sync EIC * zram: pass down the bvec we need to read into in the work struct * lib/Kconfig.debug: fix build error without CONFIG_BLOCK * MIPS: scall64-o32: Fix indirect syscall number load * trace: Fix preempt_enable_no_resched() abuse * mm: do not boost watermarks to avoid fragmentation for the DISCONTIG memory model * arm64: mm: Ensure tail of unaligned initrd is reserved * IB/rdmavt: Fix frwr memory registration * RDMA/mlx5: Do not allow the user to write to the clock page * RDMA/mlx5: Use rdma_user_map_io for mapping BAR pages * RDMA/ucontext: Fix regression with disassociate * sched/numa: Fix a possible divide-by-zero * ceph: only use d_name directly when parent is locked * ceph: ensure d_name stability in ceph_dentry_hash() * ceph: fix ci->i_head_snapc leak * nfsd: Don't release the callback slot unless it was actually held * nfsd: wake waiters blocked on file_lock before deleting it * nfsd: wake blocked file lock waiters before sending callback * sunrpc: don't mark uninitialised items as VALID. * perf/x86/intel: Update KBL Package C-state events to also include PC8/PC9/PC10 counters * Input: synaptics-rmi4 - write config register values to the right offset * dmaengine: sh: rcar-dmac: With cyclic DMA residue 0 is valid * dmaengine: sh: rcar-dmac: Fix glitch in dmaengine_tx_status * dmaengine: mediatek-cqdma: fix wrong register usage in mtk_cqdma_start * ARM: 8857/1: efi: enable CP15 DMB instructions before cleaning the cache * powerpc/mm/radix: Make Radix require HUGETLB_PAGE * drm/vc4: Fix memory leak during gpu reset. * drm/ttm: fix re-init of global structures * drm/vc4: Fix compilation error reported by kbuild test bot * ext4: fix some error pointer dereferences * loop: do not print warn message if partition scan is successful * tipc: handle the err returned from cmd header function * slip: make slhc_free() silently accept an error pointer * workqueue: Try to catch flush_work() without INIT_WORK(). * sched/deadline: Correctly handle active 0-lag timers * mac80211_hwsim: calculate if_combination.max_interfaces * NFS: Forbid setting AF_INET6 to "struct sockaddr_in"->sin_family. * netfilter: ebtables: CONFIG_COMPAT: drop a bogus WARN_ON * fm10k: Fix a potential NULL pointer dereference * tipc: check bearer name with right length in tipc_nl_compat_bearer_enable * tipc: check link name with right length in tipc_nl_compat_link_set * net: netrom: Fix error cleanup path of nr_proto_init * net/rds: Check address length before reading address family * rxrpc: fix race condition in rxrpc_input_packet() * pin iocb through aio. * aio: fold lookup_kiocb() into its sole caller * aio: keep io_event in aio_kiocb * aio: store event at final iocb_put() * Fix aio_poll() races * x86, retpolines: Raise limit for generating indirect calls from switch-case * x86/retpolines: Disable switch jump tables when retpolines are enabled * rdma: fix build errors on s390 and MIPS due to bad ZERO_PAGE use * ipv4: add sanity checks in ipv4_link_failure() * ipv4: set the tcp_min_rtt_wlen range from 0 to one day *
[Kernel-packages] [Bug 1830922] Re: Disco update: 5.0.10 upstream stable release
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1830922 Title: Disco update: 5.0.10 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Committed 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: 5.0.10 upstream stable release from git://git.kernel.org/ The following patches were applied: * bonding: fix event handling for stacked bonds * failover: allow name change on IFF_UP slave interfaces * net: atm: Fix potential Spectre v1 vulnerabilities * net: bridge: fix per-port af_packet sockets * net: bridge: multicast: use rcu to access port list from br_multicast_start_querier * net: fec: manage ahb clock in runtime pm * net: Fix missing meta data in skb with vlan packet * net: fou: do not use guehdr after iptunnel_pull_offloads in gue_udp_recv * tcp: tcp_grow_window() needs to respect tcp_space() * team: set slave to promisc if team is already in promisc mode * tipc: missing entries in name table of publications * vhost: reject zero size iova range * ipv4: recompile ip options in ipv4_link_failure * ipv4: ensure rcu_read_lock() in ipv4_link_failure() * mlxsw: spectrum_switchdev: Add MDB entries in prepare phase * mlxsw: core: Do not use WQ_MEM_RECLAIM for EMAD workqueue * mlxsw: core: Do not use WQ_MEM_RECLAIM for mlxsw ordered workqueue * mlxsw: core: Do not use WQ_MEM_RECLAIM for mlxsw workqueue * mlxsw: spectrum_router: Do not check VRF MAC address * net: thunderx: raise XDP MTU to 1508 * net: thunderx: don't allow jumbo frames with XDP * net/tls: fix the IV leaks * net/tls: don't leak partially sent record in device mode * net: strparser: partially revert "strparser: Call skb_unclone conditionally" * net/tls: fix build without CONFIG_TLS_DEVICE * net: bridge: fix netlink export of vlan_stats_per_port option * net/mlx5e: XDP, Avoid checksum complete when XDP prog is loaded * net/mlx5e: Protect against non-uplink representor for encap * net/mlx5e: Switch to Toeplitz RSS hash by default * net/mlx5e: Rx, Fixup skb checksum for packets with tail padding * net/mlx5e: Rx, Check ip headers sanity * Revert "net/mlx5e: Enable reporting checksum unnecessary also for L3 packets" * net/mlx5: FPGA, tls, hold rcu read lock a bit longer * net/tls: prevent bad memory access in tls_is_sk_tx_device_offloaded() * net/mlx5: FPGA, tls, idr remove on flow delete * route: Avoid crash from dereferencing NULL rt->from * nfp: flower: replace CFI with vlan present * nfp: flower: remove vlan CFI bit from push vlan action * sch_cake: Use tc_skb_protocol() helper for getting packet protocol * sch_cake: Make sure we can write the IP header before changing DSCP bits * NFC: nci: Add some bounds checking in nci_hci_cmd_received() * nfc: nci: Potential off by one in ->pipes[] array * sch_cake: Simplify logic in cake_select_tin() * CIFS: keep FileInfo handle live during oplock break * cifs: Fix lease buffer length error * cifs: Fix use-after-free in SMB2_write * cifs: Fix use-after-free in SMB2_read * cifs: fix handle leak in smb2_query_symlink() * fs/dax: Deposit pagetable even when installing zero page * KVM: x86: Don't clear EFER during SMM transitions for 32-bit vCPU * KVM: x86: svm: make sure NMI is injected after nmi_singlestep * Staging: iio: meter: fixed typo * staging: iio: ad7192: Fix ad7193 channel address * iio: gyro: mpu3050: fix chip ID reading * iio/gyro/bmg160: Use millidegrees for temperature scale * iio:chemical:bme680: Fix, report temperature in millidegrees * iio:chemical:bme680: Fix SPI read interface * iio: cros_ec: Fix the maths for gyro scale calculation * iio: ad_sigma_delta: select channel when reading register * iio: dac: mcp4725: add missing powerdown bits in store eeprom * iio: Fix scan mask selection * iio: adc: at91: disable adc channel interrupt in timeout case * iio: core: fix a possible circular locking dependency * io: accel: kxcjk1013: restore the range after resume. * staging: most: core: use device description as name * staging: comedi: vmk80xx: Fix use of uninitialized semaphore * staging: comedi: vmk80xx: Fix possible double-free of ->usb_rx_buf * staging: comedi: ni_usb6501: Fix use of uninitialized mutex * staging: comedi: ni_usb6501: Fix possible double-free of
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
Dan, thanks for the review/fixes/upload! -- 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/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: In Progress Status in hw-detect source package in Bionic: In Progress Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: In Progress Status in debian-installer source package in Cosmic: In Progress Status in hw-detect source package in Cosmic: In Progress Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: In Progress Status in debian-installer source package in Disco: In Progress Status in hw-detect source package in Disco: In Progress Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: In Progress Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact] * It's not possible to access iBFT (iSCSI Boot Firmware Table) information (settings for network interface, initiator, and target) in the installer because the 'iscsi_ibft' module is not present in udeb packages. * Even if it was, the installer does not handle iBFT information at all, thus any settings are ignored, and iSCSI-related configuration has to be done manually or with workarounds. * This impacts user-experience and automatic installation on systems and deployments which actually do provide the iBFT feature and information, but cannot use it practically. * With proper iBFT support in the installer (kernel module in udeb package and automatic iSCSI-related configuration) users will be able to rely on iBFT to install/deploy Ubuntu on their servers and datacenters. * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb, and configure network/iSCSI according to iBFT information in disk-detect. This is done in disk-detect so that the iSCSI LUNs are detected as disks (useful in case of no other disks in the system so the installer doesn't complain nor wait too long) and that any partman-related preseed options are not required and may be still available for the user. [Test Case] * linux package / kernel module in udeb: $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko Check the module loads in the installer environment. See comment with example for disco. * d-i/hw-detect/partman-iscsi package: See comments 11, 12, 13. [Regression Potential] * linux package: low, the kernel module is not loaded by default, and only checks whether iBFT information is present in firmware, then exposes that in sysfs in read-only mode. * d-i/hw-detect/partman-iscsi: - d-i: kernel version update to include iscsi_ibft module, based on kernel released to -updates plus one week monitoring bug reports -- it should be OK. Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64 on baremetal -- see comment 11. - hw-detect: low, the changes are enabled by a preseed option. see comment 12. - partman-iscsi: low, simple changes, plus one fix that has been tested in detail, and falls back to previous behavior if it fails. see comment 13. [Other Info] * This has been verified both by the developer with a simple iSCSI iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE) and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+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 1828868] Re: crashdump fails on HiSilicon D06
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1828868 Title: crashdump fails on HiSilicon D06 Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: [Impact] The crashdump kernel fails to boot on HiSilicon D06, and likely other SMMUv3 ARM systems. [Test Case] sudo apt install linux-crashdump Adjust crashkernel= parameter in /etc/default/grub.d/kdump-tools.cfg as appropriate (for D06, crashkernel=512M) sudo reboot (needed to add crashkernel= param) echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 3f54c447df34f iommu/arm-smmu-v3: Don't disable SMMU in kdump kernel [Regression Risk] Restricted to SMMUv3 arm64-based systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828868/+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 1830906] Re: Disco update: 5.0.9 upstream stable release
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- 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/1830906 Title: Disco update: 5.0.9 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Fix Committed 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: 5.0.9 upstream stable release from git://git.kernel.org/ The following patches were applied: * ARC: u-boot args: check that magic number is correct * arc: hsdk_defconfig: Enable CONFIG_BLK_DEV_RAM * perf/core: Restore mmap record type correctly * mips: bcm47xx: Enable USB power on Netgear WNDR3400v2 * ext4: avoid panic during forced reboot * ext4: add missing brelse() in add_new_gdb_meta_bg() * ext4: report real fs size after failed resize * ALSA: echoaudio: add a check for ioremap_nocache * ALSA: sb8: add a check for request_region * auxdisplay: hd44780: Fix memory leak on ->remove() * drm/udl: use drm_gem_object_put_unlocked. * IB/mlx4: Fix race condition between catas error reset and aliasguid flows * i40iw: Avoid panic when handling the inetdev event * mmc: davinci: remove extraneous __init annotation * ALSA: opl3: fix mismatch between snd_opl3_drum_switch definition and declaration * paride/pf: cleanup queues when detection fails * paride/pcd: cleanup queues when detection fails * thermal/intel_powerclamp: fix __percpu declaration of worker_data * thermal: samsung: Fix incorrect check after code merge * thermal: bcm2835: Fix crash in bcm2835_thermal_debugfs * thermal/int340x_thermal: Add additional UUIDs * thermal/int340x_thermal: fix mode setting * thermal/intel_powerclamp: fix truncated kthread name * scsi: iscsi: flush running unbind operations when removing a session * sched/cpufreq: Fix 32-bit math overflow * sched/core: Fix buffer overflow in cgroup2 property cpu.max * x86/mm: Don't leak kernel addresses * tools/power turbostat: return the exit status of a command * scsi: core: Also call destroy_rcu_head() for passthrough requests * scsi: qla2xxx: Fix NULL pointer crash due to stale CPUID * perf stat: Fix --no-scale * perf list: Don't forget to drop the reference to the allocated thread_map * perf tools: Fix errors under optimization level '-Og' * perf config: Fix an error in the config template documentation * perf config: Fix a memory leak in collect_config() * perf build-id: Fix memory leak in print_sdt_events() * perf top: Fix error handling in cmd_top() * perf hist: Add missing map__put() in error case * perf map: Remove map from 'names' tree in __maps__remove() * perf maps: Purge all maps from the 'names' tree * perf top: Fix global-buffer-overflow issue * perf evsel: Free evsel->counts in perf_evsel__exit() * perf tests: Fix a memory leak of cpu_map object in the openat_syscall_event_on_all_cpus test * perf tests: Fix memory leak by expr__find_other() in test__expr() * perf tests: Fix a memory leak in test__perf_evsel__tp_sched_test() * ACPI / utils: Drop reference in test for device presence * PM / Domains: Avoid a potential deadlock * blk-iolatency: #include "blk.h" * drm/exynos/mixer: fix MIXER shadow registry synchronisation code * irqchip/stm32: Don't clear rising/falling config registers at init * irqchip/stm32: Don't set rising configuration registers at init * irqchip/mbigen: Don't clear eventid when freeing an MSI * x86/hpet: Prevent potential NULL pointer dereference * x86/hyperv: Prevent potential NULL pointer dereference * x86/cpu/cyrix: Use correct macros for Cyrix calls on Geode processors * drm/nouveau/debugfs: Fix check of pm_runtime_get_sync failure * iommu/vt-d: Check capability before disabling protected memory * iommu/vt-d: Save the right domain ID used by hardware * x86/hw_breakpoints: Make default case in hw_breakpoint_arch_parse() return an error * cifs: fix that return -EINVAL when do dedupe operation * fix incorrect error code mapping for OBJECTID_NOT_FOUND * cifs: Fix slab-out-of-bounds when tracing SMB tcon * x86/gart: Exclude GART aperture from kcore * ext4: prohibit fstrim in norecovery mode * lkdtm: Print real addresses * lkdtm: Add tests for NULL pointer dereference * drm/amdgpu: psp_ring_destroy cause psp->km_ring.ring_mem NULL * drm/panel: panel-innolux: set display off in innolux_panel_unprepare * crypto: axis - fix for
[Kernel-packages] [Bug 1830792] Re: [i915] Rotated display is overscaled and overdrawn
I did plug/unplug the monitor because if I do that enough times is generally resolves the problem until the next time I reboot. It has not done so this time. I also tried a new cable, but that does not fix the problem 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/1830792 Title: [i915] Rotated display is overscaled and overdrawn Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: On my system I have two display: one in landscape, and one in portrait. The landscape display is fine, but the portrait display is corrupted. If I unplug the display from the computer for some time and then plug it back in it will occasionally fix the problem. Once the problem is fixed, the display works perfectly fine, indefinitely. However, as soon as I reboot the computer the display will come up corrupted again and never recovers without many rounds of plug/unplug turn off/turn on. It's extremely frustrating. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.0+git20190410-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 28 15:57:02 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' redacted by apport b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-shell UpgradeStatus: Upgraded to disco on 2019-04-22 (36 days ago) modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.logrotate.d.apport: 2019-01-12T15:50:59.090583 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+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 1828763] Re: Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Fix Committed
--
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/1828763
Title:
Cannot build kernel 4.15.0-48.51 due to an in-source-tree ZFS module.
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
* In b49151d684f44 tx_waited has been renamed to tx_dirty_delayed, but
only in the tracepoint definition (in trace_dmu.h) and not in the rest
of the code, causing build errors if zfs tracepoints are enabled.
* Fix by reverting tx_dirty_delayed back to the original name
tx_waited
NOTE: this bug doesn't show up in regular kernel builds, because zfs
tracepoints are not enabled by default, it is possible to see this
problem only by enabling them and recompiling zfs outside our regular
build process, but it's a good cleanup anyway (in case we need to
enable zfs tracepoints in the future).
[Test Case]
* enable zfs tracepoints in config and build zfs
[Fix]
* Restore the old struct name to fix the build bug
[Regression Potential]
* It is a very small fix (just a rename of a struct member), so
regression potential is minimal
[Original bug report]
I tried to build a kernel 4.15.0-48.51 that cloned from the Ubuntu
kernel git (x86_64-generic flavour).
commit c50532b9d7b623ff98aeaf0b848e58adae54ca75 (HEAD -> master, tag:
Ubuntu-4.15.0-48.51, origin/master, origin/HEAD)
Author: Andrea Righi
Date: Tue Apr 2 18:31:55 2019 +0200
UBUNTU: Ubuntu-4.15.0-48.51
Signed-off-by: Andrea Righi
1. Build a kernel image with 'zfs_enable' flag set as false.
2. Build SPL/ZFS modules independently by 'make' command (debug purpose;
DECLARE_EVENT_CLASS() enabled).
But 'make' was always failed at the same point,
'zfs/module/zfs/trace.c' (as seem as below).
In file included from /home/np/linux-4.15/include/trace/define_trace.h:96:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘trace_event_raw_event_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/trace_events.h:719:4: note: in definition
of macro ‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
In file included from /home/np/linux-4.15/include/trace/define_trace.h:97:0,
from /home/np/linux-4.15/zfs/include/sys/trace_dmu.h:127,
from /home/np/linux-4.15/zfs/module/zfs/trace.c:45:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h: In function
‘perf_trace_zfs_delay_mintime_class’:
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:65:37: error: ‘dmu_tx_t {aka
struct dmu_tx}’ has no member named ‘tx_dirty_delayed’
__entry->tx_dirty_delayed = tx->tx_dirty_delayed;
^
/home/np/linux-4.15/include/trace/perf.h:66:4: note: in definition of macro
‘DECLARE_EVENT_CLASS’
{ assign; } \
^~
/home/np/linux-4.15/zfs/include/sys/trace_dmu.h:60:2: note: in expansion of
macro ‘TP_fast_assign’
TP_fast_assign(
^~
I tried to debug this issue with myself and found something intriguing.
In 'zfs/include/sys/trace_dmu.h', the failed code accessing
'tx_dirty_delayed' from 'dmu_tx_t' (which same as 'struct dmu_tx').
DECLARE_EVENT_CLASS(zfs_delay_mintime_class,
TP_PROTO(dmu_tx_t *tx, uint64_t dirty, uint64_t min_tx_time),
TP_ARGS(tx, dirty, min_tx_time),
TP_STRUCT__entry(
__field(uint64_t, tx_txg)
__field(uint64_t, tx_lastsnap_txg)
__field(uint64_t, tx_lasttried_txg)
__field(boolean_t, tx_anyobj)
__field(boolean_t, tx_dirty_delayed)
__field(hrtime_t, tx_start)
__field(boolean_t, tx_wait_dirty)
__field(int,tx_err)
__field(uint64_t, min_tx_time)
__field(uint64_t, dirty)
),
TP_fast_assign(
__entry->tx_txg = tx->tx_txg;
__entry->tx_lastsnap_txg= tx->tx_lastsnap_txg;
[Kernel-packages] [Bug 1828935] Re: Add powerpc/alignment_handler test for selftests
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1828935 Title: Add powerpc/alignment_handler test for selftests Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: == Justification == There is a powerpc/alignment_handler available in the upstream for PowerPC self-testing tool. Bring this in to cover more bits in the ubuntu_kernel_selftest test suite. == Fix == * 8d191587 (selftests/powerpc: Add alignment handler selftest) * ecdf06e1 (selftests/powerpc: Fix to use ucontext_t instead of struct ucontext) Both of them can be cherry-picked into Bionic kernel. The second patch is essential to fix a build error. It's already available in Cosmic and onward. == Test == Test was successfully built and passed on a Power9 node with Bionic kernel: selftests: alignment_handler test: test_alignment_handler_vsx_206 tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty VSX: 2.06B Doing lxvd2x: PASSED Doing lxvw4x: PASSED Doing lxsdx:PASSED Doing lxvdsx: PASSED Doing stxvd2x: PASSED Doing stxvw4x: PASSED Doing stxsdx: PASSED success: test_alignment_handler_vsx_206 test: test_alignment_handler_vsx_207 tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty VSX: 2.07B Doing lxsspx: PASSED Doing lxsiwax: PASSED Doing lxsiwzx: PASSED Doing stxsspx: PASSED Doing stxsiwx: PASSED success: test_alignment_handler_vsx_207 test: test_alignment_handler_vsx_300 tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty VSX: 3.00B Doing lxsd: PASSED Doing lxsibzx: PASSED Doing lxsihzx: PASSED Doing lxssp:PASSED Doing lxv: PASSED Doing lxvb16x: PASSED Doing lxvh8x: PASSED Doing lxvx: PASSED Doing lxvwsx: PASSED Doing lxvl: PASSED Doing lxvll:PASSED Doing stxsd:PASSED Doing stxsibx: PASSED Doing stxsihx: PASSED Doing stxssp: PASSED Doing stxv: PASSED Doing stxvb16x: PASSED Doing stxvh8x: PASSED Doing stxvx:PASSED Doing stxvl:PASSED Doing stxvll: PASSED success: test_alignment_handler_vsx_300 test: test_alignment_handler_integer tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty Integer Doing lbz: PASSED Doing lbzu: PASSED Doing lbzx: PASSED Doing lbzux:PASSED Doing lhz: PASSED Doing lhzu: PASSED Doing lhzx: PASSED Doing lhzux:PASSED Doing lha: PASSED Doing lhau: PASSED Doing lhax: PASSED Doing lhaux:PASSED Doing lhbrx:PASSED Doing lwz: PASSED Doing lwzu: PASSED Doing lwzx: PASSED Doing lwzux:PASSED Doing lwa: PASSED Doing lwax: PASSED Doing lwaux:PASSED Doing lwbrx:PASSED Doing ld: PASSED Doing ldu: PASSED Doing ldx: PASSED Doing ldux: PASSED Doing ldbrx:PASSED Doing lmw: PASSED Doing stb: PASSED Doing stbx: PASSED Doing stbu: PASSED Doing stbux:PASSED Doing sth: PASSED Doing sthx: PASSED Doing sthu: PASSED Doing sthux:PASSED Doing sthbrx: PASSED Doing stw: PASSED Doing stwx: PASSED Doing stwu: PASSED Doing stwux:PASSED Doing stwbrx: PASSED Doing std: PASSED Doing stdx: PASSED Doing stdu: PASSED Doing stdux:PASSED Doing stdbrx: PASSED Doing stmw: PASSED success: test_alignment_handler_integer test: test_alignment_handler_vmx tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty VMX Doing lvx: PASSED Doing stvx: PASSED Doing stvebx: PASSED Doing stvehx: PASSED Doing stvewx: PASSED Doing stvxl:PASSED success: test_alignment_handler_vmx test: test_alignment_handler_fp tags: git_version:Ubuntu-4.15.0-48.51-2-g705784d93589-dirty Floating point Doing lfd: PASSED Doing lfdx: PASSED Doing lfdp: PASSED Doing lfdpx:PASSED Doing lfdu: PASSED Doing lfdux:PASSED Doing lfs: PASSED Doing lfsx: PASSED Doing lfsu: PASSED Doing lfsux:PASSED Doing lfiwzx: PASSED
[Kernel-packages] [Bug 1828798] Re: Eletrical noise occurred when external headset enter powersaving mode on a DEll machine
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: New => Fix Committed -- 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/1828798 Title: Eletrical noise occurred when external headset enter powersaving mode on a DEll machine Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: [Impact] Eletrical noise occurred when external headset enter powersaving mode (around 7 seconds) [Fix] Don't clear pinctl when runtime suspend. [Test Case] Plug headset and wait for the codec to enter runtime suspend, there is no any noise from headphone. [Regression Risk] Low. the 1st patch is specific to a Dell machine and the 2nd patch is specific to the machine with the codec alc298 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1828798/+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 1829187] Re: linux-raspi2: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** 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: 1829219 phase: Ready for Testing - phase-changed: Wednesday, 29. May 2019 07:39 UTC + phase-changed: Monday, 03. June 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release - snap-certification-testing: Ongoing -- testing in progress + snap-release-to-candidate: 'Pending -- snap pi-kernel not in expected channel(s): + arch=arm64:channel=18-pi3/candidate:rev=33 arch=armhf:channel=18-pi3/candidate:rev=34 + arch=armhf:channel=18-cm3/candidate:rev=34 arch=armhf:channel=18-pi2/candidate:rev=34' -- 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/1829187 Title: linux-raspi2: 4.15.0-1037.39 -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: Fix Released 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: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1829219 phase: Ready for Testing phase-changed: Monday, 03. June 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release snap-release-to-candidate: 'Pending -- snap pi-kernel not in expected channel(s): arch=arm64:channel=18-pi3/candidate:rev=33 arch=armhf:channel=18-pi3/candidate:rev=34 arch=armhf:channel=18-cm3/candidate:rev=34 arch=armhf:channel=18-pi2/candidate:rev=34' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829187/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
systemd 'storage' test case pass on all releases for ppc64el except disco due to bug 1831459, which i'll queue up to fix in the next upload. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done verification-done-bionic verification-done-cosmic verification-done-disco -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Committed Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Committed Status in systemd package in Debian: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1829187] Re: linux-raspi2: 4.15.0-1037.39 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/XJxWiqK8/1030-pi- kernel-4150-103739-34-18-pi3 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => 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/1829187 Title: linux-raspi2: 4.15.0-1037.39 -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: Fix Released 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: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1829219 phase: Ready for Testing phase-changed: Monday, 03. June 2019 14:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release snap-release-to-candidate: 'Pending -- snap pi-kernel not in expected channel(s): arch=arm64:channel=18-pi3/candidate:rev=33 arch=armhf:channel=18-pi3/candidate:rev=34 arch=armhf:channel=18-cm3/candidate:rev=34 arch=armhf:channel=18-pi2/candidate:rev=34' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829187/+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 1713017] Re: Enable MIDI support
The option is off by default in the upstream build see https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/README#n252 Since the option is flagged experimental by upstream it doesn't seem like something we want to enable in Ubuntu yet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1713017 Title: Enable MIDI support Status in bluez package in Ubuntu: Triaged Bug description: Now that bluez has landed with 5.46-0ubuntu2, it would be nice to enable Bluetooth MIDI support. This did not seem to be enabled by default in the build from https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE MIDI devices, gatttool could talk to them, but no MIDI device was made; also ldd showed no linkage to libasound.so.2). After recompiling it with libasound2-dev installed and --enable-midi in debian/rules, it worked. Suggestion: add libasound2-dev to bluez dependencies, add --enable- midi to rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+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 1802233] Re: hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change
Michael,
Is there any information from supermicro that you can share with us over
here? If this is not going to be fixed then we might have to modify the
testcase to use a workaround. Please let us know.
--
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/1802233
Title:
hwclock test failed on Power9 due to 0.x sec differences / time out
waiting for time change
Status in ubuntu-kernel-tests:
New
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
The hwclock test will fail on the Power9 system "baltar" due to a
<0.02 second difference.
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File "/home/ubuntu/autotest/client/tests/hwclock/hwclock.py", line 50, in
run_once
raise error.TestFail("Failed to set hwclock back to Warthog's birthday.
Output of hwclock is '%s'" % date)
TestFail: Failed to set hwclock back to Warthog's birthday. Output of hwclock
is '2004-10-20 04:09:59.582146+'
Didn't see this on Power8 boxes
Sometimes it will fail because "time out waiting for time change" on the same
node:
$ sudo /sbin/hwclock --set --date "2004/10/20 04:10:00"; sudo /sbin/hwclock
hwclock: Timed out waiting for time change.
Workaround for these is to add "sleep 1".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Nov 8 03:45 seq
crw-rw 1 root audio 116, 33 Nov 8 03:45 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.4
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: Thu Nov 8 06:03:54 2018
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.31 0.11 0.03 1/1392 5654
ProcLocks:
1: POSIX ADVISORY WRITE 3544 00:17:582 0 EOF
2: POSIX ADVISORY WRITE 1798 00:17:338 0 EOF
3: POSIX ADVISORY WRITE 3603 00:17:576 0 EOF
4: FLOCK ADVISORY WRITE 3535 00:17:564 0 EOF
5: FLOCK ADVISORY WRITE 4081 00:17:481 0 EOF
ProcSwaps:
Filename TypeSizeUsedPriority
/swap.img file 8388544 0 -2
ProcVersion: Linux version 4.15.0-38-generic (buildd@bos02-ppc64el-018) (gcc
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:57:45 UTC
2018
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
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
-- Firmware information on Baltar --
pnor: P9DSU20190404_IBM_prod_sign.pnor
bmc: SMT_P9_206.bin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802233/+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 1768115] Re: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160.
Closing this bug since there is no activity or response for the last 3 months. Please re-open if you think this is still an issue that needs to be resolved. ** Changed in: ubuntu-power-systems Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => 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/1768115 Title: ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3g1: Migration guest running with IO stress crashed@security_file_permission+0xf4/0x160. Status in The Ubuntu-power-systems project: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: Problem Description: Migration Guest running with IO stress crashed@security_file_permission+0xf4/0x160 after couple of migrations. Steps to re-create: Source host - boslcp3 Destination host - boslcp4 1.boslcp3 & boslcp4 installed with latest kernel root@boslcp3:~# uname -a Linux boslcp3 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# root@boslcp4:~# uname -a Linux boslcp4 4.15.0-20-generic #21+bug166588 SMP Thu Apr 26 15:05:59 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux root@boslcp3:~# 2. Installed guest boslcp3g1 with kernel and started LTP run from boslcp3 host root@boslcp3g1:~# uname -a Linux boslcp3g1 4.15.0-15-generic #16+bug166877 SMP Wed Apr 18 14:47:30 CDT 2018 ppc64le ppc64le ppc64le GNU/Linux 3. Started migrating boslcp3g1 guest from source to destination & viceversa. 4. After couple of migrations it crashed at boslcp4 & enters into xmon 8:mon> t [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> S msr= 80001033 sprg0 = pvr= 004e1202 sprg1 = c7a85800 dec= 591e3e03 sprg2 = c7a85800 sp = c004f8a234a0 sprg3 = 00010008 toc= c16eae00 dar = 023c srr0 = c00c355c srr1 = 80001033 dsisr = 4000 dscr = ppr = 0010 pir= 0011 amr= uamor = dpdes = tir = cir= fscr = 05000180 tar = pspb = mmcr0 = 8000 mmcr1 = mmcr2 = pmc1 = pmc2 = pmc3 = pmc4 = mmcra = siar = pmc5 = 026c sdar = sier = pmc6 = 0861 ebbhr = ebbrr = bescr = iamr = 4000 pidr = 0034 tidr = cpu 0x8: Vector: 700 (Program Check) at [c004f8a23220] pc: c00e4854: xmon_core+0x1f24/0x3520 lr: c00e4850: xmon_core+0x1f20/0x3520 sp: c004f8a234a0 msr: 80041033 current = 0xc004f89faf00 paca= 0xc7a85800 softe: 0irq_happened: 0x01 pid = 24028, comm = top Linux version 4.15.0-20-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 2018 (Ubuntu 4.15.0-20.21-generic 4.15.17) cpu 0x8: Exception 700 (Program Check) in xmon, returning to main loop [c004f8a23d20] c05a7674 security_file_permission+0xf4/0x160 [c004f8a23d60] c03d1d30 rw_verify_area+0x70/0x120 [c004f8a23d90] c03d375c vfs_read+0x8c/0x1b0 [c004f8a23de0] c03d3d88 SyS_read+0x68/0x110 [c004f8a23e30] c000b184 system_call+0x58/0x6c --- Exception: c01 (System Call) at 71f1779fe280 SP (7fffe99ece50) is in userspace 8:mon> r R00 = c043b7fc R16 = R01 = c004f8a23c90 R17 = ff70 R02 = c16eae00 R18 = 0a51b4bebfc8 R03 = c00279557200 R19 = 7fffe99edbb0 R04 = c003242499c0 R20 = 0a51b4c04db0 R05 = 0002 R21 = 0a51b4c20e90 R06 = 0004 R22 = 00040f00 R07 = ff81 R23 = 0a51b4c06560 R08 = ff80 R24 = ff80 R09 = R25 = 0a51b4bec2b8 R10 = R26 = 71f177bb0b20 R11 = R27 = R12 = 2000 R28 =
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
autopkgtest failures for this upload analyzed in bug 1825997 -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Committed Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Committed Status in systemd package in Debian: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1829210] Re: linux-oracle: 4.15.0-1014.16 -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 1829208 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 - phase: Ready for Testing - phase-changed: Tuesday, 28. May 2019 23:41 UTC + phase: Holding before Release + phase-changed: Monday, 03. June 2019 13:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1829210 Title: linux-oracle: 4.15.0-1014.16 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 1829208 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Holding before Release phase-changed: Monday, 03. June 2019 13:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829210/+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 1829210] Re: linux-oracle: 4.15.0-1014.16 -proposed tracker
4.15.0-1014.16 - oracle Regression test CMPL, RTB. Issue to note in oracle (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) access (bug 1831451) memory (bug 1831449) port80 (bug 1748105) pcid (bug 1827979) vmx (bug 1821394) ept (bug 1824228) vmx_hlt_with_rvi_test (bug 1822308) vmx_apicv_test (bug 1827866) vmx_apic_passthrough_thread (bug 1822309) hyperv_synic (bug 1827980) hyperv_stimer (bug 1827982) ubunut_ltp - took 4 hours and gets killed, need to be investigated ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) preadv203, preadv203_64 (bug 1831207) sync_file_range02 (bug 1819116) getrandom02 (bug 1831229) Skipped / blacklisted: * libhugetlbfs * ubuntu_seccomp ** 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1829210 Title: linux-oracle: 4.15.0-1014.16 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 1829208 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Ready for Testing phase-changed: Tuesday, 28. May 2019 23:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829210/+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 1831128] Re: ACPI error on boot
I added " noapic " to boot settings and the system jumped over the error and finally started. -- 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/1831128 Title: ACPI error on boot Status in linux package in Ubuntu: Fix Committed Bug description: i have a laptop with ryzen 5 2500u processor.and i got this error when boot, i tried ubuntu 16.04,18.04,19.04 and the result is same. system stuck on acpi error.i tried to disable it then the system is shut down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831128/+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 1831229] Re: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM
Issue found on Oracle B-4.15 instance: VM.Standard2.24 ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- 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/1831229 Title: getrandom02 from ubuntu_ltp_syscalls failed with timeout multiplier = 3 on D-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Even with the timeout multiplier set to 3, the test is still failing: Waiting for pid 1892 for 21600 seconds Checking virt-what to see if we need to set LTP_TIMEOUT_MUL... Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 (lp:1797327) == Test Suite Summary == 7 test cases failed 0 test cases blacklisted Failed test cases : acct01 getrandom02 msgstress03 quotactl01 quotactl02 quotactl03 sync_file_range02 startup='Thu May 30 21:36:06 2019' tst_test.c:1096: INFO: Timeout per run is 0h 15m 00s getrandom02.c:72: PASS: getrandom returned 256 Test timeouted, sending SIGKILL! tst_test.c:1136: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1137: BROK: Test killed! (timeout?) Summary: passed 1 failed 0 skipped 0 warnings 0 tag=getrandom02 stime=1559252166 dur=900 exit=exited stat=2 core=no cu=0 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831229/+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 1824228] Re: ept test fails in kvm_unit_tests
Found on B-4.15 Oracle, instance VM.DenseIO2.16 TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append "ept_access*" FAIL ept (8489 tests, 5 unexpected failures) ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- 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/1824228 Title: ept test fails in kvm_unit_tests Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Reproducible: Yes, Series: cosmic Kernel: "linux-azure 4.18.0-1015.15" Steps: 1.) apt-get install -y 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.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append "ept_access*" 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/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd /tmp/tmp.RcwfbGP5Ou enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: ept_access_test_not_present Test suite: ept_access_test_read_only Test suite: ept_access_test_write_only Test suite: ept_access_test_read_write Test suite: ept_access_test_execute_only Test suite: ept_access_test_read_execute Test suite: ept_access_test_write_execute Test suite: ept_access_test_read_write_execute Test suite: ept_access_test_reserved_bits Test suite: ept_access_test_ignored_bits Test suite: ept_access_test_paddr_not_present_ad_disabled Test suite: ept_access_test_paddr_not_present_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_only_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312 Test suite: ept_access_test_paddr_read_only_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_write Test suite: ept_access_test_paddr_read_write_execute Test suite: ept_access_test_paddr_read_execute_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fdfc 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed:
[Kernel-packages] [Bug 1827982] Re: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM
Failed on B-4.15 Oracle instance VM.DenseIO2.16 (passed with VM.DenseIO1.8) ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- 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/1827982 Title: hyperv_stimer in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Test timeouted. # 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 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/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev # -initrd /tmp/tmp.ouYfwUEdq5 qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic cpus = 2 qemu-system-x86_64: terminating on signal 15 from pid 2224 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:39:16 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827982/+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 1827980] Re: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM
Failed on B-4.15 Oracle instance VM.DenseIO2.16 (passed with VM.DenseIO1.8) ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- 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/1827980 Title: hyperv_synic in ubuntu_kvm_unit_tests failed on B-KVM Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Bug description: Test timeout. # TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev 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/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev # -initrd /tmp/tmp.LeYhxJZmHV qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:EDX.vme [bit 1] enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 enabling apic ncpus = 2 prepare qemu-system-x86_64: terminating on signal 15 from pid 1658 (timeout) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1032-kvm 4.15.0-1032.32 ProcVersionSignature: User Name 4.15.0-1032.32-kvm 4.15.18 Uname: Linux 4.15.0-1032-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue May 7 03:36:32 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1827980/+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 1831449] Re: memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15
Oops, spoke too soon. This has passed with Oracle Bionic 4.15 on VM.DenseIO1.8, but failed on VM.DenseIO2.16 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831449 Title: memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15 Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host FAIL memory (8 tests, 2 unexpected failures) But so far Oracle X-4.15 is the only cloud that's failing with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+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 1831449] Re: memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15
Passed with Oracle Bionic 4.15 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831449 Title: memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15 Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host FAIL memory (8 tests, 2 unexpected failures) But so far Oracle X-4.15 is the only cloud that's failing with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+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 1829213] Re: linux-azure: 4.15.0-1046.50~14.04.1 -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: 1829214 - phase: Ready for Testing - phase-changed: Tuesday, 28. May 2019 23:46 UTC + phase: Ready for Signoff + phase-changed: Monday, 03. June 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff -- 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/1829213 Title: linux-azure: 4.15.0-1046.50~14.04.1 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1829214 phase: Ready for Signoff phase-changed: Monday, 03. June 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829213/+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 1829208] Re: linux-oracle: 4.15.0-1014.16~16.04.1 -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: 1829210 - phase: Ready for Testing - phase-changed: Tuesday, 28. May 2019 23:46 UTC + phase: Holding before Release + phase-changed: Monday, 03. June 2019 13:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1829208 Title: linux-oracle: 4.15.0-1014.16~16.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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1829210 phase: Holding before Release phase-changed: Monday, 03. June 2019 13:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829208/+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 1829213] Re: linux-azure: 4.15.0-1046.50~14.04.1 -proposed tracker
4.15.0-1046.50~14.04.1 - azure Regression test CMPL, RTB. Issue to note in x86_64 (azure): libhugetlbfs - 1 failed (brk_near_huge, bug 1653597), Killed by signal 1, bad config 3 on Standard_B1ms and Standard_F1s monotonic_time - tsc failed on Standard_E2s_v3 (bug 1774959) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) port80 (bug 1748105) umip (1821905) failed on Standard_D16s_v3, Standard_D2_v3, Standard_D2s_v3, Standard_E2s_v3, Standard_F2s_v2, Standard_F32s_v2 ubuntu_ltp - test disabled on azure ubuntu_ltp_syscalls - fallocate05, fdatasync03, fsetxattr01, fremovexattr01, fremovexattr02, fgetxattr01, fsync01, fsync04, lremovexattr01, msync04, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01, statx04, sync_file_range02, syncfs01, sync03 (bug 1785198) statx05 (bug 1798524) inotify08 (bug 1775784) openat03 (bug 1798027) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) ubuntu_lxc - lxc test failed on Azure T-4.15 (bug 1813878) ubunut_qrt_apparmor - timed out on Standard-B1ms, Standard_D11_v2, Standard-F1s ubuntu_unionmount_overlayfs_suite - Rename empty dir and rename back failed (bug 1727290) Skipped / blacklisted: * ubuntu_fan_smoke_test * ubuntu_kernel_selftests * ubuntu_lttng_smoke_test * ubuntu_nbd_smoke_test * ubuntu_sysdig_smoke_test * ubuntu_zfs_smoke_test ** 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-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829213 Title: linux-azure: 4.15.0-1046.50~14.04.1 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed 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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released 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: 1829214 phase: Ready for Signoff phase-changed: Monday, 03. June 2019 13:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829213/+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 1831128] Re: ACPI error on boot
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- 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/1831128 Title: ACPI error on boot Status in linux package in Ubuntu: Fix Committed Bug description: i have a laptop with ryzen 5 2500u processor.and i got this error when boot, i tried ubuntu 16.04,18.04,19.04 and the result is same. system stuck on acpi error.i tried to disable it then the system is shut down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831128/+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 1827916] Re: Enable eBPF JIT in the linux-azure kernels
Any updates on that? Besides that eBPF is already enabled, most of the mlx and ib modules are already built as modules, the exceptions are the modules listed on bug #1785822, where it was explicitly requested to built them statically. Is it possible to compile an exact list of the modules that should be changed? That way we can discuss if those changes conflicts or not with past requests. -- 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/1827916 Title: Enable eBPF JIT in the linux-azure kernels Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Xenial: In Progress Status in linux-azure source package in Cosmic: In Progress Status in linux-azure source package in Disco: In Progress Bug description: eBPF is available as of kernel version 4.15, which is used on AKS nodes. Enabling JIT eBPF (built-in kernel feature) will speed-up execution of eBPF aware tools. eBPF JIT is controlled by the file /proc/sys/net/core/bpf_jit_enable. More details for eBPF JIT - https://www.kernel.org/doc/Documentation/sysctl/net.txt The file /proc/sys/net/core/bpf_jit_enable is not present on AKS nodes. Also, to support eBPF in AKS, we are requesting to switch the mlx* and ib* drivers to loadable modules instead of static. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1827916/+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 1831453] 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 1831453 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/1831453 Title: [Hyper-V] Install issue for Ubuntu 19.04 in Hyper-V Status in linux package in Ubuntu: Incomplete Bug description: Hi, While trying to install Ubuntu 19.04 on Hyper-V (using this image http://releases.ubuntu.com/19.04/ubuntu-19.04-live-server-amd64.iso), I found out that the installation hanged and went to terminal. No data was written to the VHDx file. Tried multiple variations: - Windows Server 2019 and Windows Server 2016 - Gen 1 and Gen 2 VM - 1/2/4 vCPUS - Static Memory/Dynamic Memory - w/o NIC attached - Live boot / install Kernel version is 5.0.0-13-generic. I'm attaching dmesg output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 3 11:39 seq crw-rw+ 1 root audio 116, 33 Jun 3 11:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 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: CRDA: N/A CasperVersion: 1.405 Date: Mon Jun 3 12:33:51 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' LiveMediaBuild: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.2) Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper quiet --- RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4159-4754-0782-4271-8692-8073-78 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831453/+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 1829208] Re: linux-oracle: 4.15.0-1014.16~16.04.1 -proposed tracker
4.15.0-1014.16~16.04.1 - oracle Regression test CMPL, RTB. Issue to note in oracle (amd64): ubuntu_kernel_selftests - global.get_metadata in seccomp (bug 1811057) net test failed to build (bug 1813883) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) access (bug 1831451) memory (bug 1831449) port80 (bug 1748105) pcid (bug 1827979) vmx (bug 1821394) vmx_hlt_with_rvi_test (bug 1822308) vmx_apicv_test (bug 1827866) vmx_apic_passthrough_thread (bug 1822309) debug (bug 1821906) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09-2 (bug 1804594) statx05 (bug 1798524) sync_file_range02 (bug 1819116) ubuntu_lxc - Failed to fetch GPG key on VM.Standard2.24, passed on the rest Skipped / blacklisted: * libhugetlbfs * ubuntu_ltp * ubuntu_seccomp ** 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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1829208 Title: linux-oracle: 4.15.0-1014.16~16.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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1829210 phase: Ready for Testing phase-changed: Tuesday, 28. May 2019 23:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829208/+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 1831453] Re: [Hyper-V] Install issue for Ubuntu 19.04 in Hyper-V
Also attaching subiquity-debug.log from /var/log/installer ** Attachment added: "ubuntu19_installer_subiquity-debug.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831453/+attachment/5268541/+files/ubuntu19_installer_subiquity-debug.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831453 Title: [Hyper-V] Install issue for Ubuntu 19.04 in Hyper-V Status in linux package in Ubuntu: New Bug description: Hi, While trying to install Ubuntu 19.04 on Hyper-V (using this image http://releases.ubuntu.com/19.04/ubuntu-19.04-live-server-amd64.iso), I found out that the installation hanged and went to terminal. No data was written to the VHDx file. Tried multiple variations: - Windows Server 2019 and Windows Server 2016 - Gen 1 and Gen 2 VM - 1/2/4 vCPUS - Static Memory/Dynamic Memory - w/o NIC attached - Live boot / install Kernel version is 5.0.0-13-generic. I'm attaching dmesg output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 3 11:39 seq crw-rw+ 1 root audio 116, 33 Jun 3 11:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 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: CRDA: N/A CasperVersion: 1.405 Date: Mon Jun 3 12:33:51 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' LiveMediaBuild: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.2) Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper quiet --- RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4159-4754-0782-4271-8692-8073-78 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831453/+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 1831453] [NEW] [Hyper-V] Install issue for Ubuntu 19.04 in Hyper-V
Public bug reported: Hi, While trying to install Ubuntu 19.04 on Hyper-V (using this image http://releases.ubuntu.com/19.04/ubuntu-19.04-live-server-amd64.iso), I found out that the installation hanged and went to terminal. No data was written to the VHDx file. Tried multiple variations: - Windows Server 2019 and Windows Server 2016 - Gen 1 and Gen 2 VM - 1/2/4 vCPUS - Static Memory/Dynamic Memory - w/o NIC attached - Live boot / install Kernel version is 5.0.0-13-generic. I'm attaching dmesg output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 3 11:39 seq crw-rw+ 1 root audio 116, 33 Jun 3 11:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 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: CRDA: N/A CasperVersion: 1.405 Date: Mon Jun 3 12:33:51 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' LiveMediaBuild: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.2) Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper quiet --- RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmwareN/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 4159-4754-0782-4271-8692-8073-78 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco uec-images ** Attachment added: "ubuntu19_install_dmesg.log" https://bugs.launchpad.net/bugs/1831453/+attachment/5268533/+files/ubuntu19_install_dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831453 Title: [Hyper-V] Install issue for Ubuntu 19.04 in Hyper-V Status in linux package in Ubuntu: New Bug description: Hi, While trying to install Ubuntu 19.04 on Hyper-V (using this image http://releases.ubuntu.com/19.04/ubuntu-19.04-live-server-amd64.iso), I found out that the installation hanged and went to terminal. No data was written to the VHDx file. Tried multiple variations: - Windows Server 2019 and Windows Server 2016 - Gen 1 and Gen 2 VM - 1/2/4 vCPUS - Static Memory/Dynamic Memory - w/o NIC attached - Live boot / install Kernel version is 5.0.0-13-generic. I'm attaching dmesg output. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jun 3 11:39 seq crw-rw+ 1 root audio 116, 33 Jun 3 11:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 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: CRDA: N/A CasperVersion: 1.405 Date: Mon Jun 3 12:33:51 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' LiveMediaBuild: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 (20190416.2) Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine PciMultimedia: ProcEnviron:
[Kernel-packages] [Bug 1826868] Re: Sound device not detected after resume from hibernate
** Description changed: - When I close my laptop, it goes to sleep. When I wake it up, it switches - to " headphones ". Then, if I go to " sound device ", my main speaker - does not show. There's only the headphones that are here. I can't get my - speakers back... I had to reboot the computer to get my device back. + [Impact] + After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi + monitor is not plugged before s3 or s4, the re-probe will fail on cnl + and glk machines. + + [Fix] + Keep the cdclk alive when re-probing + + [Test Case] + do s3 and s4 without hdmi monitor plugged, after s3 or s4, plug the hdmi + monitor, to check if the hdmi audio works well, it works well indeed. + + [Regression Risk] + Low. the 1st patch is specific to cnl and glk machines, and without this patch, + the cdclk is 0, after applying this patch, if hdmi audio want to probe hw, the + patch just set the a non-zero freq on cdclk. + + + When I close my laptop, it goes to sleep. When I wake it up, it switches to " headphones ". Then, if I go to " sound device ", my main speaker does not show. There's only the headphones that are here. I can't get my speakers back... I had to reboot the computer to get my device back. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: rob1551 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) - Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. - 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 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) + Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: - linux-restricted-modules-5.0.0-13-generic N/A - linux-backports-modules-5.0.0-13-generic N/A - linux-firmware1.178 + linux-restricted-modules-5.0.0-13-generic N/A + linux-backports-modules-5.0.0-13-generic N/A + linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP -- 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/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi monitor is not plugged before s3 or s4, the re-probe will fail on cnl and glk machines. [Fix] Keep the cdclk alive when re-probing [Test Case] do s3 and s4 without hdmi monitor plugged, after s3 or s4, plug the hdmi monitor, to check if the hdmi audio works well, it works well indeed. [Regression Risk] Low. the 1st patch is specific to cnl and glk machines, and without this patch, the cdclk is 0, after applying this patch, if hdmi audio want to probe hw, the patch just set the a non-zero freq on cdclk. When I close my laptop, it goes to sleep. When I wake it up, it switches to
[Kernel-packages] [Bug 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors
@Seth Forshee: > I think you would be better off making backup copies of the specific > files the driver uses, then replace the original files with the versions > from the link. Running "modinfo -F firmware /lib/modules/$(uname > -r)/kernel/drivers/net/wireless/ath/ath10k/ath10k_pci.ko" in a terminal > will give you a list of the firmware files the driver may be using. Note > that the paths it prints need to have /lib/firmware/ prepended. OK. The "modinfo -F" command you gave me returns a list of files: ath10k/QCA9377/hw1.0/board.bin ath10k/QCA9377/hw1.0/firmware-5.bin ath10k/QCA6174/hw3.0/board-2.bin ath10k/QCA6174/hw3.0/board.bin ath10k/QCA6174/hw3.0/firmware-6.bin ath10k/QCA6174/hw3.0/firmware-5.bin ath10k/QCA6174/hw3.0/firmware-4.bin ath10k/QCA6174/hw2.1/board-2.bin ath10k/QCA6174/hw2.1/board.bin ath10k/QCA6174/hw2.1/firmware-5.bin ath10k/QCA6174/hw2.1/firmware-4.bin ath10k/QCA9887/hw1.0/board-2.bin ath10k/QCA9887/hw1.0/board.bin ath10k/QCA9887/hw1.0/firmware-5.bin ath10k/QCA988X/hw2.0/board-2.bin ath10k/QCA988X/hw2.0/board.bin ath10k/QCA988X/hw2.0/firmware-5.bin ath10k/QCA988X/hw2.0/firmware-4.bin ath10k/QCA988X/hw2.0/firmware-3.bin ath10k/QCA988X/hw2.0/firmware-2.bin but not all these files exist in the updated firmware build I downloaded as per Kai-Heng Feng's instructions above. And in the directory you had me check are only *.ko files. So I'm not sure what to replace with what here. Sorry, guys, but the last time I built my own kernel was on Slackware Linux 1.18 in 1994 (if memory serves) and the current structure and organization of the various kernel components is a little beyond me. I'm eager to do whatever you need me to do to provide you with the data you need in order to find out what the problem is, but I'm going to need a little bit of hand-holding here. Sorry to be a pain but I'm not at all sure how to proceed at this point to install the updated kernel and firmware modules you need me to try. Any further advise would be appreciated! -- 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/1830350 Title: System freezes repeatedly for several seconds; wifi driver related errors Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: I updated my system about a month ago (Fri 26 April 2019). This was the first update in several weeks and installed fresh versions of a whole truck load of applications including a kernel update. Since this latest bunch of updates the system freezes for a few seconds at regular intervals. Not fatal, but very annoying. Output from "journalctl -f" shows the following errors occurring at the same time as these freezes: May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw scan: -110 Corresponding lines in /var/log/syslog: May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record for fe80::424:c75b:2a2d:52e2 on wlp3s0.*. May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for fe80::424:c75b:2a2d:52e2 on wlp3s0. May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: failed to start hw scan: -110 I do note the interval between the avahi-daemon entry and the subsequent errors related to the wireless network interface, but the former precede the latter consistently in syslog, suggesting they may be related, which is why I'm including it in this report. The freezes last a few seconds. Keyboard input is preserved at this time and typed input appears after the freeze is resolved. Mouse cursor continues to move during freezes but mouse clicks are only processed after the freeze is resolved, i.e. the result of the mouse click is suspended (e.g. buffered) until the system becomes responsive again. For example, clicking on a window during the freeze will focus that window after the freeze has been resolved. The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk: 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Output of lsb_release -rd: Description: Ubuntu 18.04.2 LTS Release: 18.04 Output of uname -a: Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08
[Kernel-packages] [Bug 1831449] [NEW] memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15
Public bug reported: Need to run this on oracle manually to get the full output: TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host FAIL memory (8 tests, 2 unexpected failures) But so far Oracle X-4.15 is the only cloud that's failing with this ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831449 Title: memory in ubuntu_kvm_unit_tests failed on Oracle X-4.15 Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=memory TIMEOUT=90s ACCEL= ./x86/run x86/memory.flat -smp 1 -cpu host FAIL memory (8 tests, 2 unexpected failures) But so far Oracle X-4.15 is the only cloud that's failing with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831449/+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 1831451] [NEW] access in ubuntu_kvm_unit_tests failed on Oracle X-4.15
Public bug reported: Need to run this on oracle manually to get the full output: TESTNAME=access TIMEOUT=90s ACCEL= ./x86/run x86/access.flat -smp 1 -cpu host FAIL access (timeout; duration=90s) But so far Oracle X-4.15 is the only cloud that's failing with this ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-oracle (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oracle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1831451 Title: access in ubuntu_kvm_unit_tests failed on Oracle X-4.15 Status in ubuntu-kernel-tests: New Status in linux-oracle package in Ubuntu: New Bug description: Need to run this on oracle manually to get the full output: TESTNAME=access TIMEOUT=90s ACCEL= ./x86/run x86/access.flat -smp 1 -cpu host FAIL access (timeout; duration=90s) But so far Oracle X-4.15 is the only cloud that's failing with this To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831451/+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 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
I'm leaving this as marked against libseccomp, as I don't understand why
it is redefining kernel header values as invalid numbers in its public
header file (so that other programs using its header files pull in those
invalid syscall numbers). I don't think it should but I'll leave the
decision to discuss this upstream to someone more familiar with
libseccomp.
** Changed in: libseccomp (Ubuntu)
Status: Fix Released => 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/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Incomplete
Status in linux source package in Bionic:
In Progress
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+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 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
> After these patches are applied to bionic, both libseccomp and systemd
> will need to be rebuilt - libseccomp rebuilt against the kernel
> headers, and systemd against the libseccomp headers.
technically both will need to be rebuilt against the new kernel headers,
but systemd doesn't need to wait for libseccomp to be rebuilt, as it
should get the correct value as soon as the kernel headers are updated,
since the libseccomp header file only defines __NR_pkey_mprotect (as an
invalid value) if the kernel header doesn't define it.
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: libseccomp (Ubuntu Bionic)
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/1821625
Title:
systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-
seccomp)
Status in libseccomp package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Invalid
Status in libseccomp source package in Bionic:
Incomplete
Status in linux source package in Bionic:
In Progress
Status in systemd source package in Bionic:
Invalid
Bug description:
Starting with systemd 237-3ubuntu10.14, the testcase test-seccomp is
failing on Bionic on ppc64el with the error messages:
Operating on architecture: ppc
Failed to add n/a() rule for architecture ppc, skipping: Bad address
Operating on architecture: ppc64
Failed to add n/a() rule for architecture ppc64, skipping: Bad address
Operating on architecture: ppc64-le
Failed to add n/a() rule for architecture ppc64-le, skipping: Numerical
argument out of domain
Assertion 'p == MAP_FAILED' failed at ../src/test/test-seccomp.c:413,
function test_memory_deny_write_execute_mmap(). Aborting.
memoryseccomp-mmap terminated by signal ABRT.
Assertion 'wait_for_terminate_and_check("memoryseccomp-mmap", pid, WAIT_LOG)
== EXIT_SUCCESS' failed at ../src/test/test-seccomp.c:427, function
test_memory_deny_write_execute_mmap(). Aborting.
Aborted (core dumped)
FAIL: test-seccomp (code: 134)
Full logs at:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190302_025135_d0e38@/log.gz
The testcase passed with systemd version 237-3ubuntu10.13 running on the same
4.15.0-45 kernel on ppc64el:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/s/systemd/20190228_154406_6b12f@/log.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1821625/+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 1821625] Re: systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp)
coverletter explanation as sent to kernel-team list: In bionic, all archs provided by Ubuntu either define __NR_pkey_mprotect (arm/x86) or define __IGNORE_pkey_mprotect (powerpc/s390). This value was used, until libseccomp was updated via bug 1815415, to instead (if __NR_pkey_mprotect was not defined by the kernel headers) define it as a negative error value: +#define __PNR_pkey_mprotect-10201 +#ifndef __NR_pkey_mprotect +#define __NR_pkey_mprotect __PNR_pkey_mprotect +#endif /* __NR_pkey_mprotect */ systemd, the next time it was built against libseccomp, pulled that __NR_pkey_mprotect value and started using it for ppc64el, though it was a negative error value, so it would not actually work as a syscall number. This caused the systemd test-seccomp autopkgtest to start failing, as the systemd function it tested only issued the pkey_mprotect syscall if __NR_pkey_mprotect was defined.
[Kernel-packages] [Bug 1831301] Re: sound doesn't works in both kernel. no one cards is recognize by system-
Looks like it is the I2S codoc on your machine. First let us check if your sound card is registered successfully. please run: aplay -l > /tmp/aplay-l.txt aplay -L > /tmp/aplay-L.txt arecord -l > /tmp/arecord-l.txt arecord -L > /tmp/arecord-L.txt Then upload them. thx. -- 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/1831301 Title: sound doesn't works in both kernel. no one cards is recognize by system- Status in linux package in Ubuntu: Confirmed Bug description: . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base (not installed) ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sat Jun 1 04:26:10 2019 InstallationDate: Installed on 2019-04-03 (58 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-05-31T22:19:11.232515 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831301/+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 1824690] Re: proc_thermal flooding dmesg
I've applied the patch to the Ubuntu Bionic kernel, please re-test by downloading and installing all the packages in: https://kernel.ubuntu.com/~cking/lp-1824690/disco/ ..and let me know if that helps. And to answer your questions in comment #27, the kernel is packages are just build using the current tip of the disco ubuntu kernel with Srinivas' patch applied. This is something that cannot be fixed by using dkms. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1824690 Title: proc_thermal flooding dmesg Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: Incomplete Bug description: [ 11.520358] proc_thermal :00:00.1: Unsupported event [0x91] [ 16.532358] proc_thermal :00:00.1: Unsupported event [0x91] [ 21.572719] proc_thermal :00:00.1: Unsupported event [0x91] [ 26.580855] proc_thermal :00:00.1: Unsupported event [0x91] [ 31.588851] proc_thermal :00:00.1: Unsupported event [0x91] [ 36.592827] proc_thermal :00:00.1: Unsupported event [0x91] [ 41.572682] random: crng init done [ 41.572690] random: 7 urandom warning(s) missed due to ratelimiting Kernel 4.18.0-18-generic No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juno 1175 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-15 (0 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 1ea7:0064 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N24_25GU Package: thermald 1.7.0-5ubuntu2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=a23ca3ac-6284-45ce-9aa8-6670879910e7 ro quiet splash acpi_osi= acpi_os_name=Linux vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/18/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.06 dmi.board.asset.tag: Tag 12345 dmi.board.name: N24_25GU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.06:bd05/18/2018:svnNotebook:pnN24_25GU:pvrNotApplicable:rvnNotebook:rnN24_25GU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N24_25GU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824690/+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 1830941] Re: linux: 4.4.0-150.176 -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 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Friday, 31. May 2019 20:32 UTC reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present snap-certification-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/1830941 Title: linux: 4.4.0-150.176 -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: Fix Released 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: Fix Released 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 backports: bug 1829205 (trusty/linux-aws), bug 1830947 (trusty/linux-lts-xenial) derivatives: bug 1829193 (linux-aws), bug 1829195 (linux-kvm), bug 1829198 (linux-raspi2), bug 1829201 (linux-snapdragon), bug 1829203 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Friday, 31. May 2019 20:32 UTC reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present snap-certification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+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
@Timo, tried to upgrade to xorg-server into bionic-proposed and confirmed it fixes a laggy desktop issue found in some OEM CML platforms running on bionic image. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/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: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Invalid Status in linux-oem source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Committed Status in libdrm source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in mesa source package in Disco: Fix Released Status in xorg-server source package in Disco: Fix Released 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
