[Kernel-packages] [Bug 1824886] [NEW] Battery level stuck at 100% and Estimating...
You have been subscribed to a public bug: Battery applet does not display battery charge. Always shows 100%. ASUS 1215T-RED008S. Description:Ubuntu 18.04.2 LTS Release:18.04 gnome-control-center: Установлен: 1:3.28.2-0ubuntu0.18.04.2 Кандидат: 1:3.28.2-0ubuntu0.18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 00:48:18 2019 InstallationDate: Installed on 2019-04-10 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Low Status: New ** Tags: amd64 apport-bug bionic -- Battery level stuck at 100% and Estimating... https://bugs.launchpad.net/bugs/1824886 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824886] Re: Battery level stuck at 100% and Estimating...
Thanks for testing, it confirms it's a kernel issue (and see the status is still wrong, worth reporting upstream probably) ** Package changed: gnome-power-manager (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824886 Title: Battery level stuck at 100% and Estimating... Status in linux package in Ubuntu: New Bug description: Battery applet does not display battery charge. Always shows 100%. ASUS 1215T-RED008S. Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-control-center: Установлен: 1:3.28.2-0ubuntu0.18.04.2 Кандидат: 1:3.28.2-0ubuntu0.18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 00:48:18 2019 InstallationDate: Installed on 2019-04-10 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886/+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 1824981] Re: cifs set_oplock buffer overflow in strcat
Seems there is already a discussion thread on Linux-CIFS: https://lore.kernel.org/linux- cifs/cadjhv_utw3yi1ujrvde_kkrf4gnjwnup1tuzuihcefzbo7h...@mail.gmail.com/T/ -- 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/1824981 Title: cifs set_oplock buffer overflow in strcat Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.2 LTS Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM top - 12:39:53 up 3:41, 4 users, load average: 66.19, 64.06, 76.90 Tasks: 1076 total, 1 running, 675 sleeping, 12 stopped, 1 zombie %Cpu(s): 28.2 us, 0.3 sy, 0.0 ni, 71.5 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 39483801+total, 24077185+free, 57428284 used, 96637872 buff/cache KiB Swap: 999420 total, 999420 free,0 used. 33477683+avail Mem We've seen the following bug many times since we introduced new machines running Ubuntu 18. Wasn't an issue older machines running Ubuntu 16. Three different machines are affected, so it's rather not a hardware issue. | detected buffer overflow in strcat | [ cut here ] | kernel BUG at /build/linux-6ZmFRN/linux-4.15.0/lib/string.c:1052! | invalid opcode: [#1] SMP PTI | Modules linked in: [...] | Hardware name: Dell Inc. PowerEdge R740/0923K0, BIOS 1.6.11 11/20/2018 | RIP: 0010:fortify_panic+0x13/0x22 | [...] | Call Trace: | smb21_set_oplock_level+0x147/0x1a0 [cifs] | smb3_set_oplock_level+0x22/0x90 [cifs] | smb2_set_fid+0x76/0xb0 [cifs] | cifs_new_fileinfo+0x259/0x390 [cifs] | ? smb2_get_lease_key+0x40/0x40 [cifs] | ? cifs_new_fileinfo+0x259/0x390 [cifs] | cifs_open+0x3db/0x8d0 [cifs] | [...] (Full dmesg output attached) After hitting this bug there are many cifs related dmesg entries, processes lock up and eventually the systems freezes. The share is mounted using: //server/share /mnt/server/ cifs defaults,auto,iocharset=utf8,noperm,file_mode=0777,dir_mode=0777,credentials=/root/passwords/share,domain=myDomain,uid=myUser,gid=10513,mfsymlinks Currently we're testing the cifs mount options "cache=none" as the bug seems to be oplock related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824981/+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 1824886] 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 1824886 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/1824886 Title: Battery level stuck at 100% and Estimating... Status in linux package in Ubuntu: Incomplete Bug description: Battery applet does not display battery charge. Always shows 100%. ASUS 1215T-RED008S. Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-control-center: Установлен: 1:3.28.2-0ubuntu0.18.04.2 Кандидат: 1:3.28.2-0ubuntu0.18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 00:48:18 2019 InstallationDate: Installed on 2019-04-10 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Xorg can't do anything about intercepting Alt-key, it's the kernel which takes the shortcut away. Again, as mentioned on https://bugs.launchpad.net/ubuntu/+source /console-setup/+bug/520546/comments/66 « proposed fix: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch. » Can somebody with t he proper rights do something about this? That patch exists since months now... -- 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/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1823227] Re: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker
*** This bug is a duplicate of bug 1825324 *** https://bugs.launchpad.net/bugs/1825324 ** This bug is no longer a duplicate of bug 1824382 linux-oem-osp1: 5.0.0-1003.4 -proposed tracker ** This bug has been marked a duplicate of bug 1825324 linux-oem-osp1: 5.0.0-1004.5 -proposed tracker -- 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/1823227 Title: linux-oem-osp1: 5.0.0-1001.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promote to Proposed phase-changed: Tuesday, 09. April 2019 13:32 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823227/+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 1824008] Re: linux-oem-osp1: 5.0.0-1002.3 -proposed tracker
*** This bug is a duplicate of bug 1825324 *** https://bugs.launchpad.net/bugs/1825324 ** This bug is no longer a duplicate of bug 1824382 linux-oem-osp1: 5.0.0-1003.4 -proposed tracker ** This bug has been marked a duplicate of bug 1825324 linux-oem-osp1: 5.0.0-1004.5 -proposed tracker -- 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/1824008 Title: linux-oem-osp1: 5.0.0-1002.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Wednesday, 10. April 2019 19:43 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824008/+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 1825058] Re: mac80211_hwsim unable to handle kernel NULL pointer dereference at0000000000000000
** Changed in: linux (Ubuntu) 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/1825058 Title: mac80211_hwsim unable to handle kernel NULL pointer dereference at Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] Kernel NULL pointer dereference in mac80211_hwsim. [Fix] a1881c9b8a1e mac80211_hwsim: Timer should be initialized before device registered This fix has been included in 4.19.9 or above. [Test Case] $ git clone https://github.com/aircrack-ng/aircrack-ng # Tested with 69a406c $ cd aircrack-ng $ grep 'sudo apt' README.md | bash $ autoreconf -i $ ./configure --with-experimental $ make check $ sudo bash scripts/airmon-ng.linux check kill $ sudo make integration # Run integration test again and check dmesg $ sudo bash scripts/airmon-ng.linux check kill $ sudo make integration Verified with VMs setup locally. [Regression Risk] Low. Move forward data structure initialization only. This patch has also been included in LTS stable kernel. Original Bug Report The issue happens on 16.04 with linux-image-4.15.0-47-generic (as well as linux-image-4.15.0-45-generic). It also happens with linux- image-4.15.0-47-generic on 18.04 as well as the HWE kernel (4.18.0-17-generic). All test were done on 64 bit in a virtual machine and can be reproduced. It doesn't happen on 18.10 (mac80211_hwsim has other issues on this kernel that are solved in 19.04, most likely unrelated to this) or 19.04. Output: [ 406.036796] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 406.048785] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 406.110060] mac80211_hwsim: initializing netlink [ 406.153872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 406.154217] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 406.316376] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 406.316829] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 406.894434] device wlan1 entered promiscuous mode [ 407.623768] mac80211_hwsim: initializing netlink [ 407.627809] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht' [ 407.761474] device wlan0 entered promiscuous mode [ 412.293557] mac80211_hwsim: initializing netlink [ 412.298984] ieee80211 phy3: Selected rate control algorithm 'minstrel_ht' [ 412.410453] device wlan0 entered promiscuous mode [ 417.040581] mac80211_hwsim: initializing netlink [ 417.045603] ieee80211 phy4: Selected rate control algorithm 'minstrel_ht' [ 417.048093] ieee80211 phy5: Selected rate control algorithm 'minstrel_ht' [ 417.221470] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 417.223812] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 417.755334] device wlan1 entered promiscuous mode [ 419.690453] mac80211_hwsim: initializing netlink [ 419.696569] ieee80211 phy6: Selected rate control algorithm 'minstrel_ht' [ 419.697137] ieee80211 phy7: Selected rate control algorithm 'minstrel_ht' [ 419.870739] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 419.871090] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 420.406242] device wlan1 entered promiscuous mode [ 422.434785] mac80211_hwsim: initializing netlink [ 422.435399] ieee80211 phy8: Selected rate control algorithm 'minstrel_ht' [ 422.579207] device wlan0 entered promiscuous mode [ 427.126059] mac80211_hwsim: initializing netlink [ 427.128889] ieee80211 phy9: Selected rate control algorithm 'minstrel_ht' [ 427.133435] ieee80211 phy10: Selected rate control algorithm 'minstrel_ht' [ 427.135756] ieee80211 phy11: Selected rate control algorithm 'minstrel_ht' [ 427.385722] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 427.386258] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 427.932765] device wlan2 entered promiscuous mode [ 430.923486] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [ 434.757426] wlan1: authenticate with 02:00:00:00:00:00 [ 434.757476] wlan1: send auth to 02:00:00:00:00:00 (try 1/3) [ 434.758851] wlan1: authenticated [ 434.758940] mac80211_hwsim hwsim1 wlan1: disabling HT/VHT due to WEP/TKIP use [ 434.758942] mac80211_hwsim hwsim1 wlan1: disabling HT as WMM/QoS is not supported by the AP [ 434.758943] mac80211_hwsim hwsim1 wlan1: disabling VHT as WMM/QoS is not supported by the AP [ 434.761333] wlan1: associate with 02:00:00:00:00:00 (try 1/3) [ 434.761750] wlan1: RX AssocResp from 02:00:00:00:00:00 (capab=0x11 status=0 aid=1) [ 434.761761] wlan1: associated [ 434.762107] IPv6:
[Kernel-packages] [Bug 1820868] Re: bionic: fork out linux-snapdragon into its own topic kernel
** Changed in: linux-snapdragon (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/1820868 Title: bionic: fork out linux-snapdragon into its own topic kernel Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge package in Ubuntu: New Status in linux-meta package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Committed Status in linux source package in Bionic: New Status in linux-hwe-edge source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: New Status in linux-snapdragon source package in Bionic: Fix Committed Bug description: Impact: During the Bionic cycle, a decision was made to incorporate the linux-snapdragon kernel into the master branch, thus reducing the number of topic kernels and the stable maintenance burden. But as time passed and new patches were produced by Qualcomm, incorporating them into master while avoiding to destabilize generic became more and more problematic, down to the point where it was not a viable approach anymore. At that point, the decision was made to fork out linux-snapdragon into its own topic kernel (e.g. linux-raspi2), giving more room to incorporate new code coming from the Qualcomm tree and avoiding to destabilize any other target in generic. Fix: This is a three step process: 1) disable building linux-snapdragon from master by applying the attached patch to bionic/master 2) create a new bionic/linux-snapdragon branch and reset hard to my lp:snapdragon-topic-kernel branch (see below) 3) update bionic-meta to point to the new bionic/linux-snapdragon kernel Regression potential From the point of view of bionic/master, this pull request doesn't introduce any substantial change, and in the future will let us purge generic from several external patches. While from the point of view of linux-snapdragon, with ~600 code commits and ~4k config changes, this represent a brand new kernel and while great care was used while putting together this branch, there's clearly a regression potential here but we can't leave linux-snapdragon stagnate behind the curve, so the sooner we bite the bullet, the better we can the deal with the eventual fallout. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820868/+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 1824204] Re: linux-snapdragon: 4.15.0-1051.55 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Incomplete ** 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: 1822820 - phase: Promote to Proposed - phase-changed: Tuesday, 16. April 2019 16:07 UTC + phase: Packaging + phase-changed: Thursday, 18. April 2019 09:57 UTC reason: - promote-to-proposed: Ongoing -- review in progress + prepare-package: Pending -- package not yet uploaded + promote-to-proposed: Stalled -- packages no longer available -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1824204 Title: linux-snapdragon: 4.15.0-1051.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1822820 phase: Packaging phase-changed: Thursday, 18. April 2019 09:57 UTC reason: prepare-package: Pending -- package not yet uploaded promote-to-proposed: Stalled -- packages no longer available To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824204/+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 1825322] Re: linux: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-release Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: linux (Ubuntu) Status: New => Invalid ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825322 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-release series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Invalid 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 1825324 (bionic/linux-oem-osp1) -- swm properties -- To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825322/+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 1822803] Re: linux-oem: 4.15.0-1036.41 -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: 1822820 phase: Testing phase-changed: Monday, 08. April 2019 15:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1822803 Title: linux-oem: 4.15.0-1036.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Monday, 08. April 2019 15:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+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 1822796] Re: linux: 4.18.0-18.19 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822795 (bionic/linux-hwe) derivatives: bug 1822786 (linux-raspi2), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm), bug 1824771 (linux-aws), bug 1824841 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Thursday, 04. April 2019 18:01 UTC + phase: Signoff + phase-changed: Thursday, 18. April 2019 09:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822796 Title: linux: 4.18.0-18.19 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Cosmic: 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 1822795 (bionic/linux-hwe) derivatives: bug 1822786 (linux-raspi2), bug 1822793 (linux-gcp), bug 1822794 (linux-kvm), bug 1824771 (linux-aws), bug 1824841 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Thursday, 18. April 2019 09:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822796/+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 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker
4.15.0-1036.41 - oem Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kernel_selftests - global.get_metadata in seccomp (bug 1811057) ubuntu_kvm_unit_tests - apic-split timeouted (bug 1821390) apic timeouted (bug 1748103) svm (bug 1821903) ubuntu_ltp_syscalls - inotify08 (bug 1775784) fanotify09 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - timed out on ext4 generic/430 test (bug 1755999) ** 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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1822803 Title: linux-oem: 4.15.0-1036.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Monday, 08. April 2019 15:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+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 1825229] Re: request to supercede the interim changes for 1815268 with upstream commit 8065a779
** Description changed: - The interm patch in LP# 1815268 was positioned as a way of mitigation to + The interm patch in LP#1815268 was positioned as a way of mitigation to the rename race condition as described in that bug. Now, the upstream patch has been accepted and it eliminates the need of the delay. The patch is now in staging tree and should be pulled into mainline soon: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97 Hence we request to back out the delay patch for 1815268 and instead apply the upstream patch above. ** Description changed: - The interm patch in LP#1815268 was positioned as a way of mitigation to + The interm patch in bug 1815268 was positioned as a way of mitigation to the rename race condition as described in that bug. Now, the upstream patch has been accepted and it eliminates the need of the delay. The patch is now in staging tree and should be pulled into mainline soon: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97 Hence we request to back out the delay patch for 1815268 and instead apply the upstream patch above. -- 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/1825229 Title: request to supercede the interim changes for 1815268 with upstream commit 8065a779 Status in linux package in Ubuntu: Incomplete Bug description: The interm patch in bug 1815268 was positioned as a way of mitigation to the rename race condition as described in that bug. Now, the upstream patch has been accepted and it eliminates the need of the delay. The patch is now in staging tree and should be pulled into mainline soon: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=8065a779f17e94536a1c4dcee4f9d88011672f97 Hence we request to back out the delay patch for 1815268 and instead apply the upstream patch above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825229/+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 1821823] Re: No wireless networks displayed for broadcom BCM43142
** Description changed: + [Impact] + + The dkms version available in disco regressed in behavior in comparison + to earlier series, causing `dkms uninstall` removing the module from the + built tree instead of only uninstalling it. Per the dkms manpage, an + uninstall operation should leave the module in the 'built' state, while + currently it ends up only in the 'added' state. + + This breaks our current shim-signed logic, since on postinst we're + uninstalling every dkms module, checking if we uninstalled it correctly + by making sure it's in the 'built' state and then signing it if + everything is ok. And this is now broken. + + This seemed to have been introduced unintentionally as the manpage still notes for `dkms uninstall`: + "Uninstalls an installed module/module-version combo from the kernel/arch passed in the -k option, or the current kernel if the -k option was not passed upon. After uninstall completion, the driver will be left in the built state. + To completely remove a driver, the remove action should be utilized." + + The bug has been made visible with the bcmwl-kernel-source driver, + which, if installed before shim-signed, will then become uninstalled and + not reinstalled again (because of the failed status check before + signing). + + [Test Case] + + An easy way of checking if the uninstall logic has been reverted: + + 1. On a disco system, install the dkms and bcmwl-kernel-source packages (-proposed disabled). + 2. Check the version of the module installed `dkms status`. + 3. Once the installation completes, uninstall the bcmwl dkms module from the system: + `dkms uninstall bcmwl/` + 4. Checks that the status is not reported as 'built' (should be something like 'added' only): + `dkms status bcmwl` + 5. Enable disco-proposed and upgrade dkms. + 6. Re-install the bcmwl-kernel-source package. + 7. Once again uninstall the bcmwl dkms module: + `dkms uninstall bcmwl/` + 8. Check the status and notice that it is now reported as 'built': + `dkms status bcmwl` + + Another way would be checking on a secureboot-enabled system that has + Broadcom wireless installing the -proposed dkms, then bcmwl-kernel- + source and finally shim-signed (reinstalling if necessary). This + operation should result in the broadcom dkms module still being + installed and active. But this test should be counted as an optional + 'additional test'. + + [Regression Potential] + + Since this does change the dkms uninstall behavior, there is always some + risk involved. One of the potential regressions could be related to + kernel uninstallation, as we are reverting parts of the kernel prerm + scripts along with the revert - but the risk should be low as we're + actually reverting to the state we had in all series prior to disco. In + overall the uninstall command of dkms might have regressed its behavior + in case some other place started assuming the removals of modules from + the built directory, but seeing the disco diff it's highly improbable. + + [Original Description] + For 19.04 UB did a minimal install. I selected the ubiquity proprietary option and expected the broadcom driver to be found and installed. On reboot I could not see any wireless networks. I went to the Additional Drivers window and it stated that the computer was indeed using Broadcom 802.11 Linux STA wireless driver and was in use. This is a regression - in both 18.04 and 18.10, the same steps also installed the driver, and wireless networks were found and could be connected to. ProblemType: BugDistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-7-generic 5.0.0-7.8 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dad1060 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Wed Mar 27 00:25:09 2019 InstallationDate: Installed on 2019-03-27 (0 days ago) InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0 Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Notebook ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=25581458-0e76-468f-8318-628c1a279716 ro nomodeset quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-7-generic N/A linux-backports-modules-5.0.0-7-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked:
[Kernel-packages] [Bug 1825324] Re: linux-oem-osp1: 5.0.0-1004.5 -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: 1824819 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 08:49 UTC reason: - prepare-package: Pending -- Ready - prepare-package-meta: Pending -- Ready - prepare-package-signed: Pending -- Ready promote-to-proposed: Pending -- ready for review -- 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/1825324 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824819 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 08:49 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825324/+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 1822830] Re: linux-fips: 4.4.0-1008.10 -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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete - promote-to-proposed: Ongoing -- packages copied but not yet published to -proposed + promote-to-proposed: Ongoing -- packages copied but not yet published to Signing -- 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/1822830 Title: linux-fips: 4.4.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete promote-to-proposed: Ongoing -- packages copied but not yet published to Signing To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822830/+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 1799019] Re: Linux crashed so severly that I have to reinstall.
Hello, do you still have this issue with the latest Bionic kernel (4.15.0-47-generic)? thanks. ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1799019 Title: Linux crashed so severly that I have to reinstall. Status in linux-signed package in Ubuntu: Incomplete Bug description: First Google Chrome and Chromium crashed closing all their windows. Then most, but not all, of the VisualWorks windows diappeared. (Unfortunately the System window closed so I could not exit properly). Then the list of open windows at the bottom of the screen disappeared, as did the menu bar at the top. With no menu to shutdown, I had to turn power off. When I tried to reboot I got the Ubuntu symbol and the progress dots underneath. After more than an hour, I got a command line to log in. (Not a terminal window - Ubuntu never started.) I was able to log in but could do nothing since this was a system without MATE or any window GUI. Every time I try to reboot, I get the save progress dots for over an hour and then the terminal mode login prompt. I had to boot from the distribution DVD to make this report before re- installing the system. Please fix your documentation on reporting system crashes. What is "apport" and how do I run it? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: MATE Date: Sun Oct 21 02:13:33 2018 LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1799019/+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 1742626] Re: Unstable LTS kernel 4.13
Hello, do you still experiencing this issue with the latest HWE kernel (4.15) on Xenial? Thanks ** Changed in: linux-signed (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux-lts-xenial (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux-hwe (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1742626 Title: Unstable LTS kernel 4.13 Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Incomplete Bug description: At job, after upgrading many Lubuntu 16.04 LTS 64 bit systems from 4.10 to 4.13 they are (most of them) unstable. Acer TravelMate B117-M (SSD disk) freeze at boot or show errors at startup such: unexpected irq trap at vector similar to https://forum.manjaro.org/t/manjaro-kernel-4-13-unexpected- irq-trap-at-vector-e3-error/30942 At home (no signed kernel, old machine) my VirtualBox freezes also the machine, as explained at https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1736116/comments/14 --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuari 1178 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=6bcea77a-5eea-4993-87b7-5007d7816838 InstallationDate: Installed on 2017-05-25 (246 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: Acer TravelMate B117-M Package: linux-signed ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=4472d672-c062-4877-b3ad-689003c70743 ro quiet splash ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.157.15 Tags: xenial Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/08/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Lepus_BA dmi.board.vendor: Acer dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd09/08/2016:svnAcer:pnTravelMateB117-M:pvrV1.11:rvnAcer:rnLepus_BA:rvrV1.11:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: BSW dmi.product.name: TravelMate B117-M dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742626/+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 1771206] Re: mouse left click registers as right click
Hello, do you still have this issue with the latest Bionic kernel (4.15.0-47-generic)? Thanks ** Changed in: linux-signed (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1771206 Title: mouse left click registers as right click Status in linux-signed package in Ubuntu: Incomplete Bug description: Randomly a mouse left click will register as a mouse right click, and then return to normal function. This happens in any application during any activity. This behavior was not present prior to upgrade to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 14 13:43:26 2018 InstallationDate: Installed on 2016-10-24 (566 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-12 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1771206/+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 1812636] Re: Kprobe probing module in ftrace from ubuntu_kernel_selftest failed on B/C
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812636 Title: Kprobe probing module in ftrace from ubuntu_kernel_selftest failed on B/C Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: This test: [27] Kprobe dynamic event - probing module[FAIL] Failed in the ftrace test of the ubuntu_kernel_selftests on Bionic and Cosmic ARM64 / i386 (passed with AMD64 / Power8 / Power9 / s390x) $ sudo make -C linux/tools/testing/selftests TARGETS=ftrace run_tests 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/ftrace' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace' TAP version 13 selftests: ftracetest === Ftrace unit tests === [1] Basic trace file check[PASS] [2] Basic test for tracers[PASS] [3] Basic trace clock test[PASS] [4] Basic event tracing check [PASS] [5] event tracing - enable/disable with event level files [PASS] [6] event tracing - restricts events based on pid [PASS] [7] event tracing - enable/disable with subsystem level files [PASS] [8] event tracing - enable/disable with top level files [PASS] [9] ftrace - function graph filters with stack tracer [PASS] [10] ftrace - function graph filters [PASS] [11] ftrace - function glob filters [PASS] [12] ftrace - function pid filters[PASS] [13] ftrace - test for function event triggers[PASS] [14] ftrace - function profiler with function tracing [PASS] [15] ftrace - test reading of set_ftrace_filter [PASS] [16] ftrace - test for function traceon/off triggers [PASS] [17] Test creation and deletion of trace instances while setting an event [PASS] [18] Test creation and deletion of trace instances[PASS] [19] Kprobe dynamic event - adding and removing [PASS] [20] Kprobe dynamic event - busy event check [PASS] [21] Kprobe dynamic event with arguments [PASS] [22] Kprobe event string type argument[PASS] [23] Kprobe event argument syntax [PASS] [24] Kprobes event arguments with types [PASS] [25] Kprobe event auto/manual naming [PASS] [26] Kprobe dynamic event with function tracer[PASS] [27] Kprobe dynamic event - probing module[FAIL] [28] Kretprobe dynamic event with arguments [PASS] [29] Kretprobe dynamic event with maxactive [PASS] [30] Register/unregister many kprobe events [PASS] [31] Kprobe events - probe points [PASS] [32] event trigger - test multiple actions on hist trigger[UNSUPPORTED] [33] event trigger - test event enable/disable trigger[PASS] [34] event trigger - test trigger filter [PASS] [35] event trigger - test histogram modifiers [PASS] [36] event trigger - test histogram trigger [PASS] [37] event trigger - test multiple histogram triggers [PASS] [38] event trigger - test snapshot-trigger[PASS] [39] event trigger - test stacktrace-trigger [PASS] [40] event trigger - test traceon/off trigger [PASS] [41] (instance) Basic test for tracers [PASS] [42] (instance) Basic trace clock test [PASS] [43] (instance) event tracing - enable/disable with event level files [PASS] [44] (instance) event tracing - restricts events based on pid[PASS] [45] (instance) event tracing - enable/disable with subsystem level files [PASS] [46] (instance) ftrace - test for function event triggers[PASS] [47] (instance) ftrace - test for function traceon/off triggers [PASS] [48] (instance) event trigger - test event enable/disable trigger[PASS] [49] (instance) event trigger - test trigger filter [PASS] [50] (instance) event trigger - test histogram modifiers [PASS] [51] (instance) event trigger - test histogram trigger [PASS] [52] (instance) event trigger - test multiple histogram triggers [PASS] # of passed: 50 # of failed: 1 # of unresolved: 0 # of untested: 0 # of unsupported: 1 # of xfailed: 0 # of undefined(test bug): 0 not ok 1..1 selftests: ftracetest [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name
[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg
what's the output of "dpkg -l | grep screen-resolution-extra"? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: New Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1812805] Re: powerpc/pmu/ebb test in ubuntu_kernel_selftest failed on Bionic PowerPC
This issue affects Cosmic as well: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic/cosmic/ppc64el/l/linux/20190417_093633_573ec@/log.gz ** Summary changed: - powerpc/pmu/ebb test in ubuntu_kernel_selftest failed on Bionic PowerPC + powerpc/pmu/ebb test in ubuntu_kernel_selftest failed on Bionic/Cosmic PowerPC ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812805 Title: powerpc/pmu/ebb test in ubuntu_kernel_selftest failed on Bionic/Cosmic PowerPC Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: In linux/tools/testing/selftests/powerpc/pmu/ebb: selftests: reg_access_test ./reg_access_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0e3dcc384550 for symbol `' out of range not ok 1..1 selftests: reg_access_test [FAIL] selftests: event_attributes_test ./event_attributes_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x059efa3c4af0 for symbol `' out of range not ok 1..2 selftests: event_attributes_test [FAIL] selftests: cycles_test ./cycles_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0baa1a664750 for symbol `' out of range not ok 1..3 selftests: cycles_test [FAIL] selftests: cycles_with_freeze_test ./cycles_with_freeze_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x03b22e124920 for symbol `' out of range not ok 1..4 selftests: cycles_with_freeze_test [FAIL] selftests: pmc56_overflow_test ./pmc56_overflow_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0a07e9bb47e0 for symbol `' out of range not ok 1..5 selftests: pmc56_overflow_test [FAIL] selftests: ebb_vs_cpu_event_test ./ebb_vs_cpu_event_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x01b0f3644820 for symbol `' out of range not ok 1..6 selftests: ebb_vs_cpu_event_test [FAIL] selftests: cpu_event_vs_ebb_test ./cpu_event_vs_ebb_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0ac0538147e0 for symbol `' out of range not ok 1..7 selftests: cpu_event_vs_ebb_test [FAIL] selftests: cpu_event_pinned_vs_ebb_test ./cpu_event_pinned_vs_ebb_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0d1eaeab4800 for symbol `' out of range not ok 1..8 selftests: cpu_event_pinned_vs_ebb_test [FAIL] selftests: task_event_vs_ebb_test ./task_event_vs_ebb_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x034ed21e4730 for symbol `' out of range not ok 1..9 selftests: task_event_vs_ebb_test [FAIL] selftests: task_event_pinned_vs_ebb_test ./task_event_pinned_vs_ebb_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0a5b9a844780 for symbol `' out of range not ok 1..10 selftests: task_event_pinned_vs_ebb_test [FAIL] selftests: multi_ebb_procs_test ./multi_ebb_procs_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x08b649fb4870 for symbol `' out of range not ok 1..11 selftests: multi_ebb_procs_test [FAIL] selftests: multi_counter_test ./multi_counter_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x063184dc4970 for symbol `' out of range not ok 1..12 selftests: multi_counter_test [FAIL] selftests: pmae_handling_test ./pmae_handling_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0e62316248d0 for symbol `' out of range not ok 1..13 selftests: pmae_handling_test [FAIL] selftests: close_clears_pmcc_test ./close_clears_pmcc_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0f02572846c0 for symbol `' out of range not ok 1..14 selftests: close_clears_pmcc_test [FAIL] selftests: instruction_count_test ./instruction_count_test: error while loading shared libraries: R_PPC64_ADDR16_HI reloc at 0x0ef1f78f4ae0 for symbol `' out of range not ok 1..15
[Kernel-packages] [Bug 1812824] Re: Multiple TRACE_syscall related failures in seccomp test from ubuntu_kernel_selftests found on B s390x
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812824 Title: Multiple TRACE_syscall related failures in seccomp test from ubuntu_kernel_selftests found on B s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: There are multiple failures related to the TRACE_SYSCALL: [ FAIL ] TRACE_syscall.ptrace_syscall_dropped [ FAIL ] TRACE_syscall.syscall_dropped [ FAIL ] TRACE_syscall.skip_after_RET_TRACE [ FAIL ] TRACE_syscall.kill_after_RET_TRACE [ FAIL ] TRACE_syscall.skip_after_ptrace [ FAIL ] TRACE_syscall.kill_after_ptrace TRACE_syscall.ptrace_syscall_dropped: Test failed at step #223 TRACE_syscall.syscall_dropped: Test failed at step #2 seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (9627) seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12 TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0) seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (9627) seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_ptrace: Test failed at step #15 TAP version 13 selftests: seccomp_bpf seccomp_bpf.c:608:global.KILL_one_arg_six:Expected ((void *) -1) (18446744073709551615) != map1 (18446744073709551615) [==] Running 64 tests from 1 test cases. [ RUN ] global.mode_strict_support [ OK ] global.mode_strict_support [ RUN ] global.mode_strict_cannot_call_prctl [ OK ] global.mode_strict_cannot_call_prctl [ RUN ] global.no_new_privs_support [ OK ] global.no_new_privs_support [ RUN ] global.mode_filter_support [ OK ] global.mode_filter_support [ RUN ] global.mode_filter_without_nnp [ OK ] global.mode_filter_without_nnp [ RUN ] global.filter_size_limits [ OK ] global.filter_size_limits [ RUN ] global.filter_chain_limits [ OK ] global.filter_chain_limits [ RUN ] global.mode_filter_cannot_move_to_strict [ OK ] global.mode_filter_cannot_move_to_strict [ RUN ] global.mode_filter_get_seccomp [ OK ] global.mode_filter_get_seccomp [ RUN ] global.ALLOW_all [ OK ] global.ALLOW_all [ RUN ] global.empty_prog [ OK ] global.empty_prog [ RUN ] global.log_all [ OK ] global.log_all [ RUN ] global.unknown_ret_is_kill_inside [ OK ] global.unknown_ret_is_kill_inside [ RUN ] global.unknown_ret_is_kill_above_allow [ OK ] global.unknown_ret_is_kill_above_allow [ RUN ] global.KILL_all [ OK ] global.KILL_all [ RUN ] global.KILL_one [ OK ] global.KILL_one [ RUN ] global.KILL_one_arg_one [ OK ] global.KILL_one_arg_one [ RUN ] global.KILL_one_arg_six [ OK ] global.KILL_one_arg_six [ RUN ] global.KILL_thread TRACE_syscall.ptrace_syscall_dropped: Test failed at step #223 TRACE_syscall.syscall_dropped: Test failed at step #2 seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (9627) seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12 TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0) seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (9627) seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_ptrace: Test failed at step #15 [==] Running 64 tests from 1 test cases. [ RUN ] global.mode_strict_support [ OK ] global.mode_strict_support [ RUN ] global.mode_strict_cannot_call_prctl [ OK ] global.mode_strict_cannot_call_prctl [ RUN ] global.no_new_privs_support [ OK ] global.no_new_privs_support [ RUN ] global.mode_filter_support [ OK ] global.mode_filter_support [ RUN ] global.mode_filter_without_nnp [ OK ] global.mode_filter_without_nnp [ RUN ] global.filter_size_limits [ OK ] global.filter_size_limits [ RUN ] global.filter_chain_limits [ OK ] global.filter_chain_limits [ RUN ] global.mode_filter_cannot_move_to_strict [ OK ] global.mode_filter_cannot_move_to_strict [ RUN ] global.mode_filter_get_seccomp [ OK ] global.mode_filter_get_seccomp [ RUN ] global.ALLOW_all [ OK ] global.ALLOW_all [ RUN ] global.empty_prog [ OK ] global.empty_prog [ RUN ] global.log_all [ OK ] global.log_all
[Kernel-packages] [Bug 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822811 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Testing - phase-changed: Friday, 05. April 2019 17:07 UTC + phase: Signoff + phase-changed: Thursday, 18. April 2019 08:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822812 Title: linux-oracle: 4.15.0-1011.13 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Fix Released 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 1822811 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Signoff phase-changed: Thursday, 18. April 2019 08:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822812/+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 1824771] Re: linux-aws: 4.18.0-1014.16 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 1822787 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Wednesday, 17. April 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1824771 Title: linux-aws: 4.18.0-1014.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Cosmic: 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 1822787 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Wednesday, 17. April 2019 08:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824771/+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 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in
What's the output of `cat /sys/module/mt76x0u/parameters/disable_usb_sg`? -- 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/1824650 Title: Ubuntu freezes when AC 430 WiFi Dongle is plugged in Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu crashes after a short time after plugging in the WiFi stick "AC430". The kernel fails to load the driver and the following message appears repeatedly: [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 ... Tested with Kernel 4.19 and 5.0 (5.0.2) Tested with the following distributions: Ubuntu Cosmic Cuttlefish 18.10 Ubuntu Studio 18.10 Ubuntu Disco Dingo 19.04 40-usb_modeswitch.rules was already modified to load the driver, otherwise the system chooses Driver=option. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-03-31 (13 days ago) InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.2-050002-lowlatency x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+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 1824204] Re: linux-snapdragon: 4.15.0-1051.55 -proposed tracker
** Summary changed: - linux-snapdragon: 4.15.0-1051.54 -proposed tracker + linux-snapdragon: 4.15.0-1051.55 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1824204 Title: linux-snapdragon: 4.15.0-1051.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1822820 phase: Promote to Proposed phase-changed: Tuesday, 16. April 2019 16:07 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824204/+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 1824372] Re: mlx5 : not able to set a high MTU on the representor port for a VF
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v5.1-rc5 kernel [0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed”, and attach dmesg. Thanks in advance. [0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc5/ -- 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/1824372 Title: mlx5 : not able to set a high MTU on the representor port for a VF Status in linux package in Ubuntu: Confirmed Bug description: Hi, Using Ubuntu 18.04, kernel 4.15.0-47, with a Mellanox MCX556M-ECAT-S25 [1]. With the distro driver, it's impossible to increase the MTU of a representor port : $ sudo ip li set enp50s0f0_0 mtu 1501 RTNETLINK answers: Invalid argument Whereas with the OFED driver [2], I can set it up to 9978 : $ sudo ip li set mtu 9978 enp50s0f0_0 $ This is blocking to use OVS offloading with jumbo frames. Could we please get the feature in the distro driver ? Thanks ! Steps to create the representor : echo 1 | sudo tee /sys/class/net/enp50s0f0/device/sriov_numvfs echo :32:00.3 | sudo tee /sys/bus/pci/drivers/mlx5_core/unbind sudo devlink dev eswitch set pci/:32:00.0 mode switchdev echo :32:00.2 | sudo tee /sys/bus/pci/drivers/mlx5_core/bind [1] http://www.mellanox.com/related-docs/prod_adapter_cards /PB_ConnectX-5_VPI_Card_SocketDirect.pdf [2] http://www.mellanox.com/page/mlnx_ofed_eula?mtag=linux_sw_drivers=downloads=ofed=MLNX_OFED-4.5-1.0.1.0=MLNX_OFED_LINUX-4.5-1.0.1.0-ubuntu18.04-x86_64.tgz ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-47-generic 4.15.0-47.50 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 11 14:18 seq crw-rw 1 root audio 116, 33 Apr 11 14:18 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 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: Date: Thu Apr 11 14:42:57 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Supermicro AS -2023US-TR4 PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=89c8c952-93fa-499c-bebe-fd9f4c4fbedb ro console=ttyS1,115200 nosplash iommu=pt amd_iommu=on l1tf=full module_blacklist=csiostor 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.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H11DSU-iN dmi.board.vendor: Supermicro dmi.board.version: 1.02A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.2:bd02/21/2019:svnSupermicro:pnAS-2023US-TR4:pvr0123456789:rvnSupermicro:rnH11DSU-iN:rvr1.02A:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: AS -2023US-TR4 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824372/+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 1824886] Re: Battery level stuck at 100% and Estimating...
Does the issue occur on non-HWE kernel, i.e. v4.15? -- 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/1824886 Title: Battery level stuck at 100% and Estimating... Status in linux package in Ubuntu: Incomplete Bug description: Battery applet does not display battery charge. Always shows 100%. ASUS 1215T-RED008S. Description: Ubuntu 18.04.2 LTS Release: 18.04 gnome-control-center: Установлен: 1:3.28.2-0ubuntu0.18.04.2 Кандидат: 1:3.28.2-0ubuntu0.18.04.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 00:48:18 2019 InstallationDate: Installed on 2019-04-10 (5 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824886/+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 1824841] Re: linux-azure: 4.18.0-1016.16 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** 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 1824839 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Wednesday, 17. April 2019 08:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1824841 Title: linux-azure: 4.18.0-1016.16 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: 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 1824839 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822796 phase: Testing phase-changed: Wednesday, 17. April 2019 08:27 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824841/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Thanks for the patch. Comment #67 seems to have a more detailed patch but even that's out of date now. Someone will need to rewrite the patch to suit Ubuntu 19.10/19.04 and then older versions after that. ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** Changed in: console-setup (Ubuntu) Status: Confirmed => In Progress ** Also affects: xorg-server (Ubuntu Ee-series) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Ee-series) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Ee-series) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Disco) Importance: High Status: Confirmed ** Also affects: console-setup (Ubuntu Disco) Importance: High Assignee: Balint Reczey (rbalint) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: High Status: Confirmed ** Also affects: xorg-server (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: console-setup (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: New Status in linux source package in Bionic: New Status in xorg-server source package in Bionic: New Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in EE-Series: New Status in linux source package in EE-Series: New Status in xorg-server source package in EE-Series: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1809630] Re: seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) 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/1809630 Title: seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Bug description: There are 7 test cases failed in secomp_bpf test, and this can be reproduced with test suites from the upstream: [ RUN ] TRACE_syscall.ptrace_syscall_dropped TRACE_syscall.ptrace_syscall_dropped: Test failed at step #159 [ FAIL ] TRACE_syscall.ptrace_syscall_dropped [ RUN ] TRACE_syscall.syscall_dropped TRACE_syscall.syscall_dropped: Test failed at step #2 [ FAIL ] TRACE_syscall.syscall_dropped [ RUN ] TRACE_syscall.skip_after_RET_TRACE seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (14184) seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12 [ FAIL ] TRACE_syscall.skip_after_RET_TRACE [ RUN ] TRACE_syscall.kill_after_RET_TRACE TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0) [ FAIL ] TRACE_syscall.kill_after_RET_TRACE [ RUN ] TRACE_syscall.skip_after_ptrace seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (14184) seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0) TRACE_syscall.skip_after_ptrace: Test failed at step #15 [ FAIL ] TRACE_syscall.skip_after_ptrace [ RUN ] TRACE_syscall.kill_after_ptrace TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0) [ FAIL ] TRACE_syscall.kill_after_ptrace [ RUN ] global.get_metadata seccomp_bpf.c:2913:global.get_metadata:Expected sizeof(md) (16) == ptrace(0x420d, pid, sizeof(md), ) (18446744073709551615) global.get_metadata: Test terminated by assertion [ FAIL ] global.get_metadata Please find the complete test report here: https://pastebin.ubuntu.com/p/tfmVypShtX/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon Dec 24 03:33:04 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809630/+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 1825089] Re: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished
The stress test finishes as expected on s390x KVM, thanks! ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: Colin Ian King (colin-king) => (unassigned) ** Changed in: linux (Ubuntu) Status: Fix Committed => Invalid ** Changed in: linux (Ubuntu) Importance: Medium => Undecided -- 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/1825089 Title: enosys test in ubuntu_stress_smoke_test won't terminate after the test has finished Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: On a s390x Bionic / Cosmic KVM, the enosys test is still running even the test has completed $ ps uax| grep stress ubuntu2037 0.0 0.4 93020 9564 ?Ssl 03:46 0:00 python3 ckct/runner --cloud maas ubuntu_stress_smoke_test root 2383 0.0 0.6 24248 13416 ?S03:46 0:00 /usr/bin/python -u autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_stress_smoke_test/control root 2384 0.0 0.6 24248 13416 ?S03:46 0:00 /usr/bin/python -u autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_stress_smoke_test/control ubuntu 13161 0.0 0.0 6072 696 ttysclp0 S+ 05:31 0:00 grep --color=auto stress root 19352 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 19395 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 19449 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 19481 0.0 0.0 16460 752 ?S03:51 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable 04:03:13 INFO | enosys STARTING 04:03:13 INFO | enosys RETURNED 0 04:03:13 INFO | enosys PASSED 04:03:13 WARNI| Please verify /home/ubuntu/autotest/client/results/default/ubuntu_stress_smoke_test.stress-smoke-test/debug/crash.stress-ng-bad-a.13395 for more info 04:03:13 INFO | GOOD ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-test timestamp=1555473793 localtime=Apr 17 04:03:13 completed successfully 04:03:13 INFO | END GOOD ubuntu_stress_smoke_test.stress-smoke-test ubuntu_stress_smoke_test.stress-smoke-test timestamp=1555473793 localtime=Apr 17 04:03:13 04:03:13 DEBUG| Persistent state client._record_indent now set to 1 04:03:13 DEBUG| Persistent state client.unexpected_reboot deleted 04:03:13 INFO | END GOOD timestamp=1555473793 localtime=Apr 17 04:03:13 04:03:13 DEBUG| Persistent state client._record_indent now set to 0 And the job on jenkins will eventually times out. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-48-generic 4.15.0-48.51 ProcVersionSignature: User Name 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed Apr 17 05:28:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=690e3389-e7e5-4fce-a58c-c7df1314da25 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.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825089/+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 1825313] [NEW] seccomp_bpf in ubuntu_kernel_selftest failed on Cosmic ppc64el
Public bug reported: ubuntu_kernel_selftests.seccomp, testcase seccomp_bpf fails on Cosmic linux 4.18.0-18.19 ppc64el ADT tests with the following error: 08:51:15 ERROR| [stderr] seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == syscall(286) (18446744073709551615) 08:51:15 ERROR| [stderr] TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13 Full logs at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/ppc64el/l/linux/20190417_093633_573ec@/log.gz Please note that this is not a regression, it has been failing for the past releases. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Status: Incomplete ** Tags: cosmic ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825313 Title: seccomp_bpf in ubuntu_kernel_selftest failed on Cosmic ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: ubuntu_kernel_selftests.seccomp, testcase seccomp_bpf fails on Cosmic linux 4.18.0-18.19 ppc64el ADT tests with the following error: 08:51:15 ERROR| [stderr] seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == syscall(286) (18446744073709551615) 08:51:15 ERROR| [stderr] TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13 Full logs at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/ppc64el/l/linux/20190417_093633_573ec@/log.gz Please note that this is not a regression, it has been failing for the past releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825313/+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 1825280] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel
Bionic linux-hwe-edge 5.0.0-13.14~18.04.1 has this config option set. Rerunning this test against that kernel will result in a passing test. -- 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/1825280 Title: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Failure found on B-hwe-edge kernel on P8 / i386 (difficulties with deployment for ARM64 / AMD64). In disco, this option was enabled: $ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/config.common.ubuntu CONFIG_RANDOM_TRUST_CPU=y $ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/annotations CONFIG_RANDOM_TRUST_CPU policy<{'amd64': 'y', 'i386': 'y', 'ppc64el': 'y', 's390x': 'y'}> FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest) Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) -- Traceback (most recent call last): File "./test-kernel-security.py", line 2835, in test_520_config_random_trust_cpu self.assertKernelConfig('RANDOM_TRUST_CPU', expected) File "./test-kernel-security.py", line 208, in assertKernelConfig self.assertKernelConfigSet(name) File "./test-kernel-security.py", line 195, in assertKernelConfigSet '%s option was expected to be set in the kernel config' % name) AssertionError: RANDOM_TRUST_CPU option was expected to be set in the kernel config To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1825280/+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 1825322] [NEW] linux: -proposed tracker
Public bug reported: 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 1825324 (bionic/linux-oem-osp1) -- swm properties -- ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: New ** Affects: linux (Ubuntu Disco) Importance: Medium Status: New ** Tags: disco kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.04.15-2 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: disco ** Tags added: kernel-release-tracking-bug ** Tags added: kernel-release-tracking-bug-live ** Tags added: kernel-sru-cycle-d2019.04.15-2 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- 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/1825322 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow
[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04
Hello folks, I've experienced same problem with usb wifi (Tenda U2), which has the same chip - mediatek mt7601u. The wifi dongle would not start and the kern.log reports same errors: Vendor request req:02 off:0080 failed:-110 I tested this with multiple ubuntu versions - 16.0.4, 14.04 and 18.04. In all of these releases the behaviour is same. Fortunately I found a solution for this and created a small patch mcu.patch - the file that require patch is mcu.c. The patch file is attached. Nevertheless the patch adds a module's parameter "vnd_reset" (by default set to 1 - preserve current behaviour). But after the module is patched and compiled, you can load the module like: insmod mt7601u.ko vnd_reset=0 The above will bypass the problematic (for some dongles) function we call in the driver - mt7601u_vendor_reset(). By doing so, I was able to fix the issue for my usb dongle, it works now like a charm. I'd like to ask Ubuntu community if this patch can be applied across all active ubuntu branches, so anyone who has issues like this can try to load the module with "vnd_reset=0" parameter and see if that fixes issues. By porting this extension to the driver, we'll avoid that the driver has to be re-compiled with a new kernel version. thanks, martin ** Patch added: "patch for the driver" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716301/+attachment/5256661/+files/mcu.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [
[Kernel-packages] [Bug 1824963] Re: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker
*** This bug is a duplicate of bug 1825324 *** https://bugs.launchpad.net/bugs/1825324 ** This bug has been marked a duplicate of bug 1825324 linux-oem-osp1: -proposed tracker -- 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/1824963 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: New Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1824819 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824963/+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 1824775] Re: linux-aws: 4.4.0-1042.45 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** 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: 1822834 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 18. April 2019 07:39 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 18. April 2019 08:40 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1824775 Title: linux-aws: 4.4.0-1042.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 08:40 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824775/+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 1825322] Re: linux: -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 1825324 (bionic/linux-oem-osp1) + + -- swm properties -- -- 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/1825322 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Invalid Status in Kernel SRU Workflow prepare-package-meta series: Invalid Status in Kernel SRU Workflow prepare-package-signed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-release series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Invalid 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 1825324 (bionic/linux-oem-osp1) -- swm properties -- To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825322/+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 1825324] [NEW] linux-oem-osp1: 5.0.0-1004.5 -proposed tracker
Public bug reported: 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: 1824819 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 08:49 UTC reason: prepare-package: Pending -- Ready prepare-package-meta: Pending -- Ready prepare-package-signed: Pending -- Ready promote-to-proposed: Pending -- ready for review ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Timo Aaltonen (tjaalton) Status: Fix Released ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Timo Aaltonen (tjaalton) Status: Fix Released ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Timo Aaltonen (tjaalton) Status: Fix Released ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: Confirmed ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Status: New ** Tags: bionic block-proposed block-proposed-bionic kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1824819 kernel-sru-cycle-d2019.04.15-2 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in:
[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04
Please upstream the patch first so we can backport it. -- 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/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601 [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4734.238757] usb 3-4: Product: 802.11 n WLAN [ 4734.238772] usb 3-4: Manufacturer: MediaTek [ 4734.238775] usb 3-4: SerialNumber: 1.0 [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500 [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146 [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110 [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110 [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110 [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110 [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110 [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110 [ 4757.730870] usbcore: registered new interface driver mt7601u // end $> sudo ifconfig -a // do not list any new interface 2)
[Kernel-packages] [Bug 1781016] Re: Slow flood of do_IRQ: No irq for vector
Thanks for the info. Have anyone filed a bug against upstream apcupsd? -- 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/1781016 Title: Slow flood of do_IRQ: No irq for vector Status in linux package in Ubuntu: Incomplete Bug description: Every few seconds I get something like this in my dmesg: [44984.933221] do_IRQ: 1.34 No irq handler for vector [44986.933976] do_IRQ: 1.34 No irq handler for vector [44991.935614] do_IRQ: 1.34 No irq handler for vector [45004.938590] do_IRQ: 1.34 No irq handler for vector [45005.939002] do_IRQ: 4.34 No irq handler for vector [45034.949161] do_IRQ: 4.34 No irq handler for vector [45051.954569] do_IRQ: 4.34 No irq handler for vector [45058.956019] do_IRQ: 4.34 No irq handler for vector [45062.957727] do_IRQ: 4.34 No irq handler for vector [45063.958204] do_IRQ: 4.34 No irq handler for vector [45073.961103] do_IRQ: 4.34 No irq handler for vector The numbers vary. Some examples are 4.34, 4.36, 1.34, 0.33, 6.34, 7.33, 5.37. Eventually dmesg's ring buffer is full and my entire log is just messages like above with varying #.## numbers. I researched it and tried disabling irqbalance. It had no effect, the messages continued. The system is a Ryzen 2700X with B350 chipset on Asus Prime B350-PLUS. I have 64GB of Kingston DDR4-2400 ECC memory and Samsung 960 PRO M.2 NVMe SSD, and an Intel I350-T4 quad port gigabit NIC. This issue never occurred before installing 18.03 on the same hardware. No overclocking whatsoever has ever been done to this machine. Also, I had to disable selective suspend on USB in this version to prevent major USB issues, which was not required in 17.10, that might be related. My system seems stable, but spurious IRQs can't be good. I'd like to resolve this if possible. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-26-generic 4.15.0-26.28 ProcVersionSignature: Ubuntu 4.15.0-26.28-generic 4.15.18 Uname: Linux 4.15.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2145 F pulseaudio doug 3736 F pulseaudio /dev/snd/controlC1: gdm2145 F pulseaudio doug 3736 F pulseaudio Date: Tue Jul 10 12:49:00 2018 HibernationDevice: InstallationDate: Installed on 2017-06-26 (379 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-26-generic root=UUID=53446747-0814-48f7-b7c4-7fd7d7234d83 ro video=vesa:off vga=normal video=efifb:off usbcore.autosuspend=-1 usbhid.quirks=0x1e71:0x170e:0x4 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.15.0-26-generic N/A linux-backports-modules-4.15.0-26-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4011 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4011:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: 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/1781016/+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 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM is enabled, on some codecs or for some hw design, there is noise with the codec runtime PM enabled. [Fix] put the machine in the power_save_black_list, this will set the power_save=0 [Test Case] just boot up and do some audio operations, there is no noise anymore [Regression Risk] Low. this patch ony applies to the specific machines. I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+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 1824775] Re: linux-aws: 4.4.0-1042.45 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822834 - phase: Packaging - phase-changed: Tuesday, 16. April 2019 07:10 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 18. April 2019 07:39 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Holding -- builds not complete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1824775 Title: linux-aws: 4.4.0-1042.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822834 phase: Holding before Promote to Proposed phase-changed: Thursday, 18. April 2019 07:39 UTC reason: promote-to-proposed: Holding -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824775/+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 1825280] Re: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel
This shouldn't be a blocker to release the B-hwe-edge kernel but it is something that we'll want to fix in that kernel's config soon. -- 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/1825280 Title: test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed with 5.0 kernel Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Failure found on B-hwe-edge kernel on P8 / i386 (difficulties with deployment for ARM64 / AMD64). In disco, this option was enabled: $ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/config.common.ubuntu CONFIG_RANDOM_TRUST_CPU=y $ grep RANDOM_TRUST_CPU ~/ubuntu-disco/debian.master/config/annotations CONFIG_RANDOM_TRUST_CPU policy<{'amd64': 'y', 'i386': 'y', 'ppc64el': 'y', 's390x': 'y'}> FAIL: test_520_config_random_trust_cpu (__main__.KernelSecurityConfigTest) Ensure RANDOM_TRUST_CPU is enabled (LP: #1823754) -- Traceback (most recent call last): File "./test-kernel-security.py", line 2835, in test_520_config_random_trust_cpu self.assertKernelConfig('RANDOM_TRUST_CPU', expected) File "./test-kernel-security.py", line 208, in assertKernelConfig self.assertKernelConfigSet(name) File "./test-kernel-security.py", line 195, in assertKernelConfigSet '%s option was expected to be set in the kernel config' % name) AssertionError: RANDOM_TRUST_CPU option was expected to be set in the kernel config To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1825280/+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 1825313] 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 1825313 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Cosmic) Status: New => Incomplete ** Tags added: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825313 Title: seccomp_bpf in ubuntu_kernel_selftest failed on Cosmic ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Incomplete Bug description: ubuntu_kernel_selftests.seccomp, testcase seccomp_bpf fails on Cosmic linux 4.18.0-18.19 ppc64el ADT tests with the following error: 08:51:15 ERROR| [stderr] seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == syscall(286) (18446744073709551615) 08:51:15 ERROR| [stderr] TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13 Full logs at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/ppc64el/l/linux/20190417_093633_573ec@/log.gz Please note that this is not a regression, it has been failing for the past releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825313/+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 1825324] Re: linux-oem-osp1: 5.0.0-1004.5 -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 + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- - kernel-stable-master-bug: 1825322 + kernel-stable-master-bug: 1824819 ** Tags removed: kernel-sru-backport-of-1825322 ** Tags added: kernel-sru-backport-of-1824819 -- 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/1825324 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824819 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 08:49 UTC reason: prepare-package: Pending -- Ready prepare-package-meta: Pending -- Ready prepare-package-signed: Pending -- Ready promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825324/+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 1824819] Re: linux: 5.0.0-13.14 -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 + https://wiki.ubuntu.com/Kernel/kernel-sru-workflow - backports: bug 1824889 (bionic/linux-hwe-edge) + backports: bug 1824889 (bionic/linux-hwe-edge), bug 1825324 (bionic/linux-oem-osp1) derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure), bug 1824835 (linux-gcp), bug 1824836 (linux-kvm) -- swm properties -- phase: Testing phase-changed: Tuesday, 16. April 2019 09:29 UTC -- 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/1824819 Title: linux: 5.0.0-13.14 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Released Bug description: This bug 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 1824889 (bionic/linux-hwe-edge), bug 1825324 (bionic/linux-oem-osp1) derivatives: bug 1824833 (linux-aws), bug 1824834 (linux-azure), bug 1824835 (linux-gcp), bug 1824836 (linux-kvm) -- swm properties -- phase: Testing phase-changed: Tuesday, 16. April 2019 09:29 UTC To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824819/+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 1825324] Re: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu Bionic) 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/1825324 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824819 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 08:49 UTC reason: prepare-package: Pending -- Ready prepare-package-meta: Pending -- Ready prepare-package-signed: Pending -- Ready promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825324/+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 1825324] Re: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Timo Aaltonen (tjaalton) ** 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: 1824819 + phase: Ready for Promote to Proposed + phase-changed: Thursday, 18. April 2019 08:49 UTC + reason: + prepare-package: Pending -- Ready + prepare-package-meta: Pending -- Ready + prepare-package-signed: Pending -- Ready + promote-to-proposed: Pending -- ready for review -- 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/1825324 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Confirmed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824819 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 08:49 UTC reason: prepare-package: Pending -- Ready prepare-package-meta: Pending -- Ready prepare-package-signed: Pending -- Ready promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825324/+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 1824382] Re: linux-oem-osp1: 5.0.0-1003.4 -proposed tracker
*** This bug is a duplicate of bug 1825324 *** https://bugs.launchpad.net/bugs/1825324 ** This bug has been marked a duplicate of bug 1825324 linux-oem-osp1: 5.0.0-1004.5 -proposed tracker -- 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/1824382 Title: linux-oem-osp1: 5.0.0-1003.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Incomplete 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824383 phase: Promote to Proposed phase-changed: Tuesday, 16. April 2019 11:10 UTC reason: promote-to-proposed: Stalled -- packages no longer available To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824382/+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 1825272] Re: headset-mic doesn't work on two Dell laptops.
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Critical Assignee: Hui Wang (hui.wang) Status: Incomplete ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux (Ubuntu Disco) Importance: Critical => High ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: linux-oem (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Disco) 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/1825272 Title: headset-mic doesn't work on two Dell laptops. Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Confirmed Status in linux-oem source package in Disco: Invalid Bug description: [Impact] the headset-mic can't be detected after we plug the headset into the audio jack [Fix] Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE. [Test Case] Boot up the system plug the headset into the audio jack The audio device selecting dialogue will show up selecting headset-mic icon, then rerord sound from headset-mic, it works well. [Regression Risk] Low. this patch only applies to specific dell machines which have the same pin config as defined in the patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825272/+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 1821663] Re: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade
** Also affects: linux (Ubuntu Disco) Importance: High Assignee: Hui Wang (hui.wang) Status: Confirmed ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: linux (Ubuntu Cosmic) 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/1821663 Title: [regression][snd_hda_codec_realtek] repeating crackling noise after 19.04 upgrade Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux source package in Disco: Confirmed Bug description: [Impact] After CONFIG_SND_HDA_POWER_SAVE_DEFAULT is changed to 1, the codec runtime PM is enabled, on some codecs or for some hw design, there is noise with the codec runtime PM enabled. [Fix] put the machine in the power_save_black_list, this will set the power_save=0 [Test Case] just boot up and do some audio operations, there is no noise anymore [Regression Risk] Low. this patch ony applies to the specific machines. I'm experiencing a repeating crackling noise after 19.04 upgrade that start just after the boot and before the login. I tried a bunch of fixes for pulseaudio I found googling, including this one https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Glitches.2C_skips_or_crackling and this one https://askubuntu.com/questions/864608/audio-crackle-through-headphones. Neither of which helped. The command "killall pulseaudio" usually stop the noise for 10 seconds, then the noise restart. The system was running smoothly on 18.10 Alessandro- ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: alessandro 3310 F pulseaudio /dev/snd/controlC0: alessandro 3310 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Mar 26 03:29:00 2019 InstallationDate: Installed on 2016-07-09 (989 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-03-25 (0 days ago) dmi.bios.date: 02/14/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: GA-8TRC410M-NF dmi.board.vendor: NEC COMPUTERS INTERNATIONAL dmi.chassis.type: 3 dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr: dmi.product.name: IMEDIA 5204 dmi.product.version: PB34310106 dmi.sys.vendor: Packard Bell NEC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821663/+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 1824204] Re: linux-snapdragon: 4.15.0-1051.55 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Packaging - phase-changed: Thursday, 18. April 2019 09:57 UTC + phase: Promote to Proposed + phase-changed: Thursday, 18. April 2019 10:37 UTC reason: - prepare-package: Pending -- package not yet uploaded promote-to-proposed: Stalled -- packages no longer available -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1824204 Title: linux-snapdragon: 4.15.0-1051.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Incomplete 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: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1822820 phase: Promote to Proposed phase-changed: Thursday, 18. April 2019 10:37 UTC reason: promote-to-proposed: Stalled -- packages no longer available To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824204/+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 1822937] Re: NVIDIA settings won't write to /etc/xorg
ii screen-resolution-extra0.17.4 all Extension for the GNOME screen resolution applet -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: New Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+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 1822830] Re: linux-fips: 4.4.0-1008.10 -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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete - promote-to-proposed: Pending -- packages copied to Signing signed:failed,signed:retry-needed + promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed -- 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/1822830 Title: linux-fips: 4.4.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822830/+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 1825324] Re: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825324 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824819 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 08:49 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825324/+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 1822830] Re: linux-fips: 4.4.0-1008.10 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 - phase: Promote to Proposed - phase-changed: Wednesday, 17. April 2019 08:31 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 18. April 2019 12:38 UTC reason: - promote-signing-to-proposed: Pending -- builds not complete in Signing signed:retry-needed - promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed + promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822830 Title: linux-fips: 4.4.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Holding before Promote to Proposed phase-changed: Thursday, 18. April 2019 12:38 UTC reason: promote-signing-to-proposed: Holding -- another kernel is currently pending in Proposed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822830/+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 1824204] Re: linux-snapdragon: 4.15.0-1051.55 -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: 1822820 - phase: Promote to Proposed - phase-changed: Thursday, 18. April 2019 10:37 UTC + phase: Holding before Promote to Proposed + phase-changed: Thursday, 18. April 2019 12:36 UTC reason: - promote-to-proposed: Stalled -- packages no longer available + promote-to-proposed: Holding -- builds not complete in ppa -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1824204 Title: linux-snapdragon: 4.15.0-1051.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1822820 phase: Holding before Promote to Proposed phase-changed: Thursday, 18. April 2019 12:36 UTC reason: promote-to-proposed: Holding -- builds not complete in ppa To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824204/+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 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
https://lists.ubuntu.com/archives/kernel-team/2019-April/100221.html ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Also affects: linux (Ubuntu Disco) Importance: High Assignee: Seth Forshee (sforshee) Status: 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/1825210 Title: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [SRU Justification] Impact: The virtualbox package was updated in disco just prior to release, with numerous bug fixes. It is standard practice during development to sync our in-kernel source with the latest version of the virtualbox-guest-dkms package, however this upload was done so late in the release that there was not time to update the source in our kernel tree. Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1. Regression Potential: This is a sync from the dkms package in the disco-release pocket, thus the code has presumably been tested against the Ubuntu Disco kernel. However, this is a very large pile of changes, and contains more than just bug fixes, so regressions are possible. Test Case: Boot a kernel with the updated driver in virtualbox and confirm that the guest drier functionality works as expected. --- * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1801574] Re: [cosmic] ipoib ping with large message size failed
Hi Tyler, do you have any update for this bug? -- 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/1801574 Title: [cosmic] ipoib ping with large message size failed Status in linux package in Ubuntu: Confirmed Bug description: We see that ping over ipoib interface stuck with large packets, this is a new degradation, this test pass on Ubuntu 18.04. After investigating the issue, we see that commit [1] introduce the issue, and it is not an upstream commit, it is canonical commit. Could you please check with the canonical kernel team why they revert that commit? To reproduce the bug, please use ConnectX-3 devices with ipoib connection with 2044 MTU (default) and run command [2]. Is there open Launchpad on it? [1] commit 77a24c313d21e3765b04d90521e9228a9bb6e332 Author: Tyler Hicks Date: Fri Aug 3 21:53:15 2018 + Revert "net: increase fragment memory usage limits" This reverts commit c2a936600f78aea00d3312ea4b66a79a4619f9b4. It made denial of service attacks on the IP fragment handling easier to carry out. CVE-2018-5391 Signed-off-by: Tyler Hicks Signed-off-by: Stefan Bader [2] ping 13.194.22.1 -I 13.194.23.1 -s 65507 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801574/+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 1825071] Re: Super + p does not work as expected, it's defective
I also checked this on my office workstation which has a similar setup but different GFX card. The exact issue happens there. I think this is how this works in general in Ubuntu. -- 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/1825071 Title: Super + p does not work as expected, it's defective Status in linux package in Ubuntu: Incomplete Bug description: I have 3 monitors (2 landscape and 1 portrait), I normally need to change between my monitors due to my setup. If I want to play a game, I typically switch to a single monitor (Built-in) then I can switch back to Join and everything goes back to normal. That is what I would expect but that is NOT what happens. When using super+p there are 4 options: - Mirror - Join - External - Built-in The first two options work correctly, but the 3rd and 4th options do not. External and Built-in do the exact same thing: they simply shift my monitors around, lose all settings (reset everything). So all 3 monitors are still in use but settings are cleared (orientation, resolution, and frequency are reset). I have to then open up the settings to change it all back. When I go back to Join, I would expect the settings to return to normal. They do not. Super + P simply wipes out monitor settings in my case. I am using: - Ubuntu 4.15.0-47.50-generic 4.15.18 - GeForce GTX 1080/PCIe/SSE2 - I have attached: lspci-vnvn.log Description: Ubuntu 18.04.2 LTS Release: 18.04 With nvidia-driver-418 from: ppa:graphics-drivers/ppa $ apt-cache policy nvidia-driver-418 nvidia-driver-418: Installed: 418.56-0ubuntu0~gpu18.04.1 Candidate: 418.56-0ubuntu0~gpu18.04.1 Version table: *** 418.56-0ubuntu0~gpu18.04.1 500 500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status I am not sure if this is actually necessary because I don't think this has to do with the graphics card. I am not sure what other information you will need for this report. I can provide more data upon request. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jpsimkins 3108 F pulseaudio /dev/snd/controlC1: jpsimkins 3108 F pulseaudio /dev/snd/controlC0: jpsimkins 3108 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-22 (298 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. Z97X-UD5H NonfreeKernelModules: nvidia_modeset nvidia wl 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 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=cc5d2207-1cfa-40c1-8401-26624ac706a4 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.3 Tags: bionic Uname: Linux 4.15.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-UD5H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF10:bd08/03/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-UD5H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-UD5H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-UD5H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825071/+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 1825324] Re: linux-oem-osp1: 5.0.0-1004.5 -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: 1824819 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 18. April 2019 08:49 UTC + phase: Promote to Proposed + phase-changed: Thursday, 18. April 2019 12:40 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review 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/1825324 Title: linux-oem-osp1: 5.0.0-1004.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1824819 phase: Promote to Proposed phase-changed: Thursday, 18. April 2019 12:40 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825324/+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 1825313] Re: seccomp_bpf in ubuntu_kernel_selftest failed on Cosmic ppc64el
** Changed in: linux (Ubuntu Cosmic) Status: Incomplete => Confirmed ** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-hwe (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-hwe (Ubuntu) ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux-hwe (Ubuntu Bionic) ** No longer affects: linux-hwe (Ubuntu Cosmic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825313 Title: seccomp_bpf in ubuntu_kernel_selftest failed on Cosmic ppc64el Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Confirmed Bug description: ubuntu_kernel_selftests.seccomp, testcase seccomp_bpf fails on Cosmic linux 4.18.0-18.19 ppc64el ADT tests with the following error: 08:51:15 ERROR| [stderr] seccomp_bpf.c:1808:TRACE_syscall.ptrace_syscall_dropped:Expected 1 (1) == syscall(286) (18446744073709551615) 08:51:15 ERROR| [stderr] TRACE_syscall.ptrace_syscall_dropped: Test failed at step #13 Full logs at: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/ppc64el/l/linux/20190417_093633_573ec@/log.gz Please note that this is not a regression, it has been failing for the past releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825313/+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 1824204] Re: linux-snapdragon: 4.15.0-1051.55 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed 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: 1822820 - phase: Holding before Promote to Proposed - phase-changed: Thursday, 18. April 2019 12:36 UTC + phase: Ready for Promote to Proposed + phase-changed: Thursday, 18. April 2019 13:07 UTC reason: - promote-to-proposed: Holding -- builds not complete in ppa + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1824204 Title: linux-snapdragon: 4.15.0-1051.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: Confirmed 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: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1822820 phase: Ready for Promote to Proposed phase-changed: Thursday, 18. April 2019 13:07 UTC reason: promote-to-proposed: Pending -- ready for review To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824204/+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 1825210] Re: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update
** Description changed: [SRU Justification] + + Impact: The virtualbox package was updated in disco just prior to + release, with numerous bug fixes. It is standard practice during + development to sync our in-kernel source with the latest version of the + virtualbox-guest-dkms package, however this upload was done so late in + the release that there was not time to update the source in our kernel + tree. + + Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1. + + Regression Potential: This is a sync from the dkms package in the disco- + release pocket, thus the code has presumably been tested against the + Ubuntu Disco kernel. However, this is a very large pile of changes, and + contains more than just bug fixes, so regressions are possible. + + Test Case: Boot a kernel with the updated driver in virtualbox and + confirm that the guest drier functionality works as expected. + + --- + * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. 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/1825210 Title: [SRU] Please sync vbox modules from virtualbox 6.0.6 on next kernel update Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [SRU Justification] Impact: The virtualbox package was updated in disco just prior to release, with numerous bug fixes. It is standard practice during development to sync our in-kernel source with the latest version of the virtualbox-guest-dkms package, however this upload was done so late in the release that there was not time to update the source in our kernel tree. Fix: Re-sync the vbox guest dkms drivers from virtualbox 6.0.6-dfsg-1. Regression Potential: This is a sync from the dkms package in the disco-release pocket, thus the code has presumably been tested against the Ubuntu Disco kernel. However, this is a very large pile of changes, and contains more than just bug fixes, so regressions are possible. Test Case: Boot a kernel with the updated driver in virtualbox and confirm that the guest drier functionality works as expected. --- * the changes are already in disco (vbox-guest-dkms), and they are fixes for the kernel 5.0. They might seem a lot of changes, but they are needed, and probably some of them are even CVE fixes... As said, vbox 6.0.6 includes lots of fixes for host/guest kernel modules, and they should be syncd when possible. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825210/+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 1822883] Re: linux: 3.13.0-169.219 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/trusty/3.13.0-169.219 /trusty-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822883 Title: linux: 3.13.0-169.219 -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: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true phase: Holding before Release phase-changed: Thursday, 18. April 2019 11:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822883/+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 1822809] Re: linux-kvm: 4.15.0-1032.32 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Testing - phase-changed: Thursday, 11. April 2019 12:36 UTC + phase: Signoff + phase-changed: Thursday, 18. April 2019 11:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1822809 Title: linux-kvm: 4.15.0-1032.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in 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: 1822820 phase: Signoff phase-changed: Thursday, 18. April 2019 11:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822809/+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 1822883] Re: linux: 3.13.0-169.219 -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 bugs-spammed: true - phase: Testing - phase-changed: Monday, 15. April 2019 02:02 UTC + phase: Holding before Release + phase-changed: Thursday, 18. April 2019 11:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- 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/1822883 Title: linux: 3.13.0-169.219 -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: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true phase: Holding before Release phase-changed: Thursday, 18. April 2019 11:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822883/+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 1824775] Re: linux-aws: 4.4.0-1042.45 -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: 1822834 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 18. April 2019 08:40 UTC + phase: Promote to Proposed + phase-changed: Thursday, 18. April 2019 12:09 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1824775 Title: linux-aws: 4.4.0-1042.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Promote to Proposed phase-changed: Thursday, 18. April 2019 12:09 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824775/+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 1824775] Re: linux-aws: 4.4.0-1042.45 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1824775 Title: linux-aws: 4.4.0-1042.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Promote to Proposed phase-changed: Thursday, 18. April 2019 12:09 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824775/+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 1822830] Re: linux-fips: 4.4.0-1008.10 -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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete - promote-to-proposed: Ongoing -- packages copied but not yet published to Signing + promote-to-proposed: Pending -- packages copied Signing ** 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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete - promote-to-proposed: Pending -- packages copied Signing + promote-to-proposed: Pending -- packages copied to Signing {}:failed,{}:retry-needed ** 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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete - promote-to-proposed: Pending -- packages copied to Signing {}:failed,{}:retry-needed + promote-to-proposed: Pending -- packages copied signed retry likely needed in Signing ** 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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete - promote-to-proposed: Pending -- packages copied signed retry likely needed in Signing + promote-to-proposed: Pending -- packages copied to Signing signed:failed,{}:retry-needed ** 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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not complete - promote-to-proposed: Pending -- packages copied to Signing signed:failed,{}:retry-needed + promote-to-proposed: Pending -- packages copied to Signing signed:failed,signed:retry-needed -- 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/1822830 Title: linux-fips: 4.4.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Holding -- builds not
[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04
The attachment "patch for the driver" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1716301 Title: wifi driver: mt7601u not work on 16.04 Status in linux package in Ubuntu: Confirmed Status in usb-modeswitch-data package in Ubuntu: Confirmed Bug description: In the beginning, when the adapter is pluged in, it's mounted as a disk including driver files for Windows, and $> lsusb Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp. after eject the disk, $> lsusb Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter I tried following 3 drivers: 1) the default mt7601u included in the kernel: 4.4.0-91-generic after eject the disk, $> lsmod|grep mt mt7601u 102400 0 mac80211 737280 1 mt7601u cfg80211 565248 2 mac80211,mt7601u binfmt_misc 20480 1 $> modinfo mt7601u filename: /lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko srcversion: E8B632D369E0C2A9F1CF7D8 alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in* .. depends: mac80211,cfg80211 intree: Y vermagic: 4.4.0-91-generic SMP mod_unload modversions $> dmesg // begin [ 4581.094119] usb 3-4: USB disconnect, device number 6 [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4585.001416] usb 3-4: Product: Љ [ 4585.001418] usb 3-4: Manufacturer: Љ [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4585.001873] scsi host6: usb-storage 3-4:1.0 [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0 [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5 [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4619.691737] ISOFS: changing to secondary root [ 4691.563347] usb 3-4: USB disconnect, device number 7 [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878 [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 4693.766903] usb 3-4: Product: Љ [ 4693.766905] usb 3-4: Manufacturer: Љ [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected [ 4693.768063] scsi host7: usb-storage 3-4:1.0 [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 CCS [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0 [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5 [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3 [ 4728.427856] ISOFS: changing to secondary root [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00 [ 4733.824218] usb 3-4: USB disconnect, device number 8 [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 00 00 00 00 00 [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601 [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4734.238757] usb 3-4: Product: 802.11 n WLAN [ 4734.238772] usb 3-4: Manufacturer: MediaTek [ 4734.238775] usb 3-4: SerialNumber: 1.0 [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500 [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146 [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110 [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110 [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110 [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110 [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110 [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110 [ 4757.730501] mt7601u 3-4:1.0: Vendor
[Kernel-packages] [Bug 1822811] Re: linux-oracle: 4.15.0-1011.13~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822812 - phase: Testing - phase-changed: Tuesday, 09. April 2019 13:13 UTC + phase: Signoff + phase-changed: Thursday, 18. April 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1822811 Title: linux-oracle: 4.15.0-1011.13~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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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: 1822812 phase: Signoff phase-changed: Thursday, 18. April 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822811/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
Fine tuning: only one extra mount is necessary .. then plymouth finishes very quickly .. and xorg/lightdm start normally! -- 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/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) Status in lightdm package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+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 1825272] Re: headset-mic doesn't work on two Dell laptops.
** Tags added: originate-from-1824479 somerville ** Tags added: originate-from-1824311 -- 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/1825272 Title: headset-mic doesn't work on two Dell laptops. Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem source package in Bionic: Confirmed Status in linux source package in Cosmic: Confirmed Status in linux-oem source package in Cosmic: Invalid Status in linux source package in Disco: Confirmed Status in linux-oem source package in Disco: Invalid Bug description: [Impact] the headset-mic can't be detected after we plug the headset into the audio jack [Fix] Apply the fixup of ALC255_FIXUP_DELL1_MIC_NO_PRESENCE. [Test Case] Boot up the system plug the headset into the audio jack The audio device selecting dialogue will show up selecting headset-mic icon, then rerord sound from headset-mic, it works well. [Regression Risk] Low. this patch only applies to specific dell machines which have the same pin config as defined in the patch. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1825272/+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 1824650] Re: Ubuntu freezes when AC 430 WiFi Dongle is plugged in
The AC860 seems to suffer from the same problem. -- 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/1824650 Title: Ubuntu freezes when AC 430 WiFi Dongle is plugged in Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu crashes after a short time after plugging in the WiFi stick "AC430". The kernel fails to load the driver and the following message appears repeatedly: [ 800.177462] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177711] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.177961] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178211] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178461] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.178712] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 [ 800.181962] mt76x0u 1-1.1.3.2:1.0: rx urb failed: -32 ... Tested with Kernel 4.19 and 5.0 (5.0.2) Tested with the following distributions: Ubuntu Cosmic Cuttlefish 18.10 Ubuntu Studio 18.10 Ubuntu Disco Dingo 19.04 40-usb_modeswitch.rules was already modified to load the driver, otherwise the system chooses Driver=option. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2019-03-31 (13 days ago) InstallationMedia: Ubuntu-Studio 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: cosmic Uname: Linux 5.0.2-050002-lowlatency x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824650/+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 1824775] Re: linux-aws: 4.4.0-1042.45 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1824775 Title: linux-aws: 4.4.0-1042.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Promote to Proposed phase-changed: Thursday, 18. April 2019 12:09 UTC reason: promote-to-proposed: Ongoing -- review in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824775/+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 1824204] Re: linux-snapdragon: 4.15.0-1051.55 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => New ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Andy Whitcroft (apw) => (unassigned) ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubuntu-sru) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1824204 Title: linux-snapdragon: 4.15.0-1051.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1822820 phase: Promote to Proposed phase-changed: Thursday, 18. April 2019 10:37 UTC reason: promote-to-proposed: Stalled -- packages no longer available To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824204/+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 1822830] Re: linux-fips: 4.4.0-1008.10 -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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: - promote-signing-to-proposed: Holding -- builds not complete + promote-signing-to-proposed: Pending -- builds not complete in Signing promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed ** 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: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: - promote-signing-to-proposed: Pending -- builds not complete in Signing + promote-signing-to-proposed: Pending -- builds not complete in Signing signed:retry-needed promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed -- 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/1822830 Title: linux-fips: 4.4.0-1008.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Promote to Proposed phase-changed: Wednesday, 17. April 2019 08:31 UTC reason: promote-signing-to-proposed: Pending -- builds not complete in Signing signed:retry-needed promote-to-proposed: Pending -- packages copied to Signing signed:retry-needed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822830/+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 1802306] Re: Network connectivity lost after a few minutes on Intel Corporation Wireless 8265 / 8275 (rev 78), ThinkPad T480s, firmware v36
None of the kernel upgrade for Cosmic would improve the situation. I've upgraded to Disco and keeping an eye on this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802306 Title: Network connectivity lost after a few minutes on Intel Corporation Wireless 8265 / 8275 (rev 78), ThinkPad T480s, firmware v36 Status in linux package in Ubuntu: Expired Bug description: STR: - connect to Mozilla or Mozilla Guest wifi networks After a few seconds / minutes (less than three in general), no more network connectivity, but no error reported in dmesg. Only solution is to disconnect / reconnect network. To date, it does not happen at home, connected on a Netgear R7000 AP, the issue is somehow triggered by the infra at Mozilla (Paris office). --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2196 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (17 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW 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 dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802306/+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 1802168] Re: Unable to get right-click working on ThinkPad T480s
Just upgraded to Disco, it seems okay, not checked if it's really fixed or just a workaround in place. -- 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/1802168 Title: Unable to get right-click working on ThinkPad T480s Status in libinput: Fix Released Status in Linux: Unknown Status in libinput package in Ubuntu: New Status in linux package in Ubuntu: Triaged Bug description: Updated to Ubuntu 18.10, I've been fighting some weird behavior of the touchpad. Now, right-click does not work, whatever solution I try within gnome-tweaks, whether relying on multi-finger tapping or not. Found a very very close report from RedHat, on the same model of laptop, around kernel 4.18, with a fix: https://bugzilla.redhat.com/show_bug.cgi?id=1628715 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alex 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 HibernationDevice: RESUME=LABEL="Swap" InstallationDate: Installed on 2012-11-03 (2195 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MachineType: LENOVO 20L7CTO1WW Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=45c5d738-161a-4a73-9614-c529fdf655be ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 Tags: cosmic Uname: Linux 4.18.0-10-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-22 (16 days ago) UserGroups: adm cdrom dialout dip disk docker kismet libvirt libvirtd lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True dmi.bios.date: 09/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N22ET49W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L7CTO1WW 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 dmi.modalias: dmi:bvnLENOVO:bvrN22ET49W(1.26):bd09/13/2018:svnLENOVO:pn20L7CTO1WW:pvrThinkPadT480s:rvnLENOVO:rn20L7CTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480s dmi.product.name: 20L7CTO1WW dmi.product.sku: LENOVO_MT_20L7_BU_Think_FM_ThinkPad T480s dmi.product.version: ThinkPad T480s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1802168/+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 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Testing - phase-changed: Friday, 05. April 2019 17:08 UTC + phase: Signoff + phase-changed: Thursday, 18. April 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1822817 Title: linux-azure: 4.15.0-1042.46 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure 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 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Signoff phase-changed: Thursday, 18. April 2019 14:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+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 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) 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/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 source package in Bionic: Confirmed 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 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed on C-KVM
Also found in cosmic/linux-azure: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic/cosmic/amd64/l/linux- azure/20190416_185145_846ae@/log.gz I'll nominate this bug against cosmic/linux. ** 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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed on C-KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: New Status in linux-kvm source package in Cosmic: New Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 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/1812622/+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 1812194] Re: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels
Also found in cosmic/linux-azure: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic/cosmic/amd64/l/linux- azure/20190416_185145_846ae@/log.gz I'll nominate this bug against cosmic/linux. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Cosmic) Status: New => Invalid -- 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/1812194 Title: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-kvm source package in Cosmic: Invalid Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 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/1812194/+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 1824773] Re: linux-aws: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Wednesday, 17. April 2019 08:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1824773 Title: linux-aws: 4.15.0-1037.39 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in 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 1822804 (xenial/linux-aws-hwe) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Testing phase-changed: Wednesday, 17. April 2019 08:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824773/+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 1825395] [NEW] thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen
Public bug reported: I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt docking station. Initial connection to the dock works great, but after a few plug/unplug and suspend/resume cycles, the system gets in a state where a reboot is needed to make the dock work. The displayport connection still works so my external monitor gets the right display, but the thunderbolt / PCIe connection does not and so the USB and network ports in the dock aren't usable. I assume it is connected to the kernel messages like [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630 [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400 [37270.096820] pci :09:00.0: enabling Extended Tags [37270.096975] pci :09:00.0: supports D1 D2 [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link) [37270.097187] pcieport :07:01.0: ASPM: current common clock configuration is broken, reconfiguring [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400 [37270.108705] pci :0a:00.0: enabling Extended Tags [37270.108865] pci :0a:00.0: supports D1 D2 [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.109066] pcieport :07:02.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330 [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit] [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit] [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit] [37270.109499] pci :0b:00.0: supports D1 [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold [37270.109686] pcieport :07:04.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109724] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109738] pci :09:00.0: devices behind bridge are unusable because [bus 0a] cannot be assigned for them [37270.109766] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 0b [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under [bus 07-0b] (conflicts with (null) [bus 07-0b]) [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70] [37270.109843] pcieport :07:04.0: bridge window [mem 0xd400-0xe9ff] [37270.109848] pcieport :07:04.0: bridge window [mem 0x9000-0xb9ff 64bit pref] [37270.109849] pcieport :07:04.0: devices behind bridge are unusable because [bus 3d-70] cannot be assigned for them 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: roland 1690 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 09:40:22 2019 InstallationDate: Installed on 2019-03-29 (20 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20JGS01000 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET45W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JGS01000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1NET45W(1.32):bd03/11/2019:svnLENOVO:pn20JGS01000:pvrThinkPadX1Yoga2nd:rvnLENOVO:rn20JGS01000:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 2nd dmi.product.name: 20JGS01000 dmi.product.sku: LENOVO_MT_20JG_BU_Think_FM_ThinkPad X1 Yoga 2nd dmi.product.version: ThinkPad X1 Yoga 2nd dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1825395] 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/1825395 Title: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt docking station. Initial connection to the dock works great, but after a few plug/unplug and suspend/resume cycles, the system gets in a state where a reboot is needed to make the dock work. The displayport connection still works so my external monitor gets the right display, but the thunderbolt / PCIe connection does not and so the USB and network ports in the dock aren't usable. I assume it is connected to the kernel messages like [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630 [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400 [37270.096820] pci :09:00.0: enabling Extended Tags [37270.096975] pci :09:00.0: supports D1 D2 [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link) [37270.097187] pcieport :07:01.0: ASPM: current common clock configuration is broken, reconfiguring [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400 [37270.108705] pci :0a:00.0: enabling Extended Tags [37270.108865] pci :0a:00.0: supports D1 D2 [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.109066] pcieport :07:02.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330 [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit] [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit] [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit] [37270.109499] pci :0b:00.0: supports D1 [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold [37270.109686] pcieport :07:04.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109724] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109738] pci :09:00.0: devices behind bridge are unusable because [bus 0a] cannot be assigned for them [37270.109766] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 0b [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under [bus 07-0b] (conflicts with (null) [bus 07-0b]) [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70] [37270.109843] pcieport :07:04.0: bridge window [mem 0xd400-0xe9ff] [37270.109848] pcieport :07:04.0: bridge window [mem 0x9000-0xb9ff 64bit pref] [37270.109849] pcieport :07:04.0: devices behind bridge are unusable because [bus 3d-70] cannot be assigned for them 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: roland 1690 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 09:40:22 2019 InstallationDate: Installed on 2019-03-29 (20 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20JGS01000 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET45W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JGS01000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1824775] Re: linux-aws: 4.4.0-1042.45 -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: 1822834 phase: Testing phase-changed: Thursday, 18. April 2019 16:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - verification-testing: Pending -- Ready -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1824775 Title: linux-aws: 4.4.0-1042.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Testing phase-changed: Thursday, 18. April 2019 16:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824775/+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 1822803] Re: linux-oem: 4.15.0-1036.41 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Testing - phase-changed: Monday, 08. April 2019 15:06 UTC + phase: Signoff + phase-changed: Thursday, 18. April 2019 17:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1822803 Title: linux-oem: 4.15.0-1036.41 -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-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 phase: Signoff phase-changed: Thursday, 18. April 2019 17:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822803/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] Corrupted wallpaper after resuming from suspend Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Every other wake from sleep presents a corrupted screen with no unlock app. There's a dock and system menu on a black background with pixel garbage. Some personal information in the dock's large window thumbnails. Bitmap garbage flashes on the screen when interacting with anything. Only workaround is doing another sleep-wake cycle. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:4b:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.87 Tue Aug 21 12:33:05 PDT 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 22:19:29 2018 DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.18.0-11-generic, x86_64: installed nvidia, 390.87, 4.18.0-12-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162] InstallationDate: Installed on 2018-10-28 (54 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. Default string ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago) dmi.bios.date: 06/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: X99P-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819689] Re: [linux-azure] Commit To Improve NVMe Performance
** Patch added: "0001-blk-mq-remove-the-request_list-usage_xenial.patch" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+attachment/5256828/+files/0001-blk-mq-remove-the-request_list-usage_xenial.patch -- 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/1819689 Title: [linux-azure] Commit To Improve NVMe Performance Status in linux-azure package in Ubuntu: New Bug description: In bug 1818138, the config option CONFIG_NO_HZ_FULL was requested to be enabled in the linux-azure kernels(currently 4.15 and 4.18) in order to increase NVME disks performance. To achieve the peak IOPs we are seeing in testing, the following commit is also needed: 7ac257b862f2c (“blk-mq: remove the request_list usage”) This commit cleans up unused code in block-mq (mq uses pre-allocated tags to allocate request, not request_list as it's used only in legacy queue). The commit saves a bunch of rcu locks on I/O queuing path, which increases the achievable IOPs seen in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1819689/+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 1825395] Re: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen
I will try the upstream kernel, although it will be a few days before I can confidently report if the issue is not present. -- 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/1825395 Title: thunderbolt / PCIe hotplug gets confused after a few cycles on X1 Yoga 2nd gen Status in linux package in Ubuntu: Confirmed Bug description: I have a Lenovo X1 Yoga 2nd gen along with the Lenovo thunderbolt docking station. Initial connection to the dock works great, but after a few plug/unplug and suspend/resume cycles, the system gets in a state where a reboot is needed to make the dock work. The displayport connection still works so my external monitor gets the right display, but the thunderbolt / PCIe connection does not and so the USB and network ports in the dock aren't usable. I assume it is connected to the kernel messages like [37269.423750] thunderbolt 0-1: new device found, vendor=0x108 device=0x1630 [37269.423751] thunderbolt 0-1: Lenovo ThinkPad Thunderbolt 3 Dock [37270.096713] pci :09:00.0: [8086:15d3] type 01 class 0x060400 [37270.096820] pci :09:00.0: enabling Extended Tags [37270.096975] pci :09:00.0: supports D1 D2 [37270.096976] pci :09:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.097068] pci :09:00.0: 8.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x4 link at :07:01.0 (capable of 31.504 Gb/s with 8 GT/s x4 link) [37270.097187] pcieport :07:01.0: ASPM: current common clock configuration is broken, reconfiguring [37270.108588] pci :0a:00.0: [8086:15d3] type 01 class 0x060400 [37270.108705] pci :0a:00.0: enabling Extended Tags [37270.108865] pci :0a:00.0: supports D1 D2 [37270.108866] pci :0a:00.0: PME# supported from D0 D1 D2 D3hot D3cold [37270.109066] pcieport :07:02.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109147] pci :0b:00.0: [1b73:1100] type 00 class 0x0c0330 [37270.109221] pci :0b:00.0: reg 0x10: [mem 0xbc00-0xbc00 64bit] [37270.109258] pci :0b:00.0: reg 0x18: [mem 0xbc01-0xbc010fff 64bit] [37270.109295] pci :0b:00.0: reg 0x20: [mem 0xbc011000-0xbc011fff 64bit] [37270.109499] pci :0b:00.0: supports D1 [37270.109500] pci :0b:00.0: PME# supported from D0 D1 D3hot D3cold [37270.109686] pcieport :07:04.0: ASPM: current common clock configuration is broken, reconfiguring [37270.109724] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109738] pci :09:00.0: devices behind bridge are unusable because [bus 0a] cannot be assigned for them [37270.109766] pci :0a:00.0: devices behind bridge are unusable because [bus 0b] cannot be assigned for them [37270.109779] pcieport :07:02.0: bridge has subordinate 0a but max busn 0b [37270.109831] pci_bus :3d: busn_res: can not insert [bus 3d-70] under [bus 07-0b] (conflicts with (null) [bus 07-0b]) [37270.109834] pcieport :07:04.0: PCI bridge to [bus 3d-70] [37270.109843] pcieport :07:04.0: bridge window [mem 0xd400-0xe9ff] [37270.109848] pcieport :07:04.0: bridge window [mem 0x9000-0xb9ff 64bit pref] [37270.109849] pcieport :07:04.0: devices behind bridge are unusable because [bus 3d-70] cannot be assigned for them 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: roland 1690 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 09:40:22 2019 InstallationDate: Installed on 2019-03-29 (20 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) MachineType: LENOVO 20JGS01000 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=323a265b-35d4-4a11-82f0-e47b38cac797 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1NET45W (1.32 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JGS01000 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias:
[Kernel-packages] [Bug 1825420] [NEW] package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash 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. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package disco staging -- 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox
[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in linux package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash 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. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825420/+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 1794055] Re: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully
Also should have mentioned the kernel was also upgraded from -proposed on bionic. ubuntu@bobone:~$ uname -a Linux bobone 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:26:19 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@bobone:~$ -- 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/1794055 Title: [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors; OS booted successfully Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-firmware source package in Bionic: Fix Committed Status in linux source package in Cosmic: Won't Fix Status in linux-firmware source package in Cosmic: Fix Released Bug description: SRU Justification Impact: Missing firmware for nouveau is causing errors to appear in dmesg. Fix: Add missing firmware files from upstream linux-firmware. Test Case: Confirm that errors in dmesg are gone once new firmware files are present. Regression Potential: New and updated firmware always has potential to cause regressions, however this firmware has been in disco for several months with no reported issues. --- == Comment: #0 - Kalpana Shetty - 2018-09-15 23:55:13 == ---Problem Description--- [Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS booting thrown with nouveau errors Contact Information = kalsh...@in.ibm.com, preeti.tha...@in.ibm.com ---uname output--- root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 4.18.0-7-generic #8-Ubuntu SMP Tue Aug 28 18:20:56 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Witherspoon DD2.2 LC Steps: 1. Netinstall Ubu 18.10 on Witherspoon-LC-DD2.2 6GPU system --> PASS 2. Boot the OS ---> PASS but error thrown on the console related open source NVIDIA driver. [Disk: sdb2 / c0302064-c5a3-49a7-8bd4-402283e6fcbe] Ubuntu, with Linux 4.18.0-7-generic (recovery mode) Ubuntu, with Linux 4.18.0-7-generic Ubuntu [Disk: nvme0n1p2 / c5d042f1-812e-49e0-94b2-ade477084061] Ubuntu, with Linux 4.18.0-7-generic (recovery mode) * Ubuntu, with Linux 4.18.0-7-generic Ubuntu System information System configuration System status log Language Rescan devices Retrieve config from URL Plugins (0) Exit to shell ?? Enter=accept, e=edit, n=new, x=exit, l=language, g=log, h=help The system is going down NOW! Sent SIGTERM to all processes Sent SIGKILL to all processes [ 57.513329] kexec_core: Starting new kernel [ 149.358703978,5] OPAL: Switch to big-endian OS [ 153.355498935,5] OPAL: Switch to little-endian OS [2.943735] integrity: Unable to open file: /etc/keys/x509_ima.der (-2) [2.943738] integrity: Unable to open file: /etc/keys/x509_evm.der (-2) [3.132733] vio vio: uevent: failed to send synthetic uevent [4.058698] nouveau 0004:04:00.0: gr: failed to load gr/sw_nonctx [4.129215] nouveau 0004:04:00.0: DRM: failed to create kernel channel, -22 [ 19.126509] nouveau 0004:04:00.0: DRM: failed to idle channel 0 [DRM] [ 19.281450] nouveau 0004:05:00.0: gr: failed to load gr/sw_nonctx [ 19.351322] nouveau 0004:05:00.0: DRM: failed to create kernel channel, -22 [ 34.350509] nouveau 0004:05:00.0: DRM: failed to idle channel 0 [DRM] [ 34.502063] nouveau 0004:06:00.0: gr: failed to load gr/sw_nonctx [ 34.572144] nouveau 0004:06:00.0: DRM: failed to create kernel channel, -22 [ 49.570509] nouveau 0004:06:00.0: DRM: failed to idle channel 0 [DRM] [ 49.734754] nouveau 0035:03:00.0: gr: failed to load gr/sw_nonctx [ 49.805057] nouveau 0035:03:00.0: DRM: failed to create kernel channel, -22 [ 64.802510] nouveau 0035:03:00.0: DRM: failed to idle channel 0 [DRM] [ 64.955442] nouveau 0035:04:00.0: gr: failed to load gr/sw_nonctx [ 65.025537] nouveau 0035:04:00.0: DRM: failed to create kernel channel, -22 [ 80.022509] nouveau 0035:04:00.0: DRM: failed to idle channel 0 [DRM] [ 80.181169] nouveau 0035:05:00.0: gr: failed to load gr/sw_nonctx [ 80.251481] nouveau 0035:05:00.0: DRM: failed to create kernel channel, -22 [ 95.250509] nouveau 0035:05:00.0: DRM: failed to idle channel 0 [DRM] /dev/nvme0n1p2: recovering journal /dev/nvme0n1p2: clean, 72569/97681408 files, 7384418/390701312 blocks -.mount kmod-static-nodes.service dev-hugepages.mount dev-mqueue.mount sys-kernel-debug.mount ufw.service lvm2-lvmetad.service systemd-remount-fs.service systemd-random-seed.service systemd-sysusers.service keyboard-setup.service systemd-tmpfiles-setup-dev.service lvm2-monitor.service finalrd.service console-setup.service