[Kernel-packages] [Bug 1829189] Re: linux-snapdragon: 4.15.0-1054.58 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Thursday, 23. May 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap dragonboard-kernel not in expected channel(s): - arch=arm64:channel=18/beta' - snap-release-to-edge: 'Pending -- snap dragonboard-kernel not in expected channel(s): - arch=arm64:channel=18/edge' + snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1829189 Title: linux-snapdragon: 4.15.0-1054.58 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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: 1829219 phase: Testing phase-changed: Thursday, 23. May 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-certification-testing 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: 1829209 phase: Testing phase-changed: Thursday, 23. May 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap dragonboard-kernel not in expected channel(s): - arch=arm64:channel=latest/beta' - snap-release-to-edge: 'Pending -- snap dragonboard-kernel not in expected channel(s): - arch=arm64:channel=latest/edge' + snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1829201 Title: linux-snapdragon: 4.4.0-1114.119 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Confirmed Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1829209 phase: Testing phase-changed: Thursday, 23. May 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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 ** Changed in: kernel-sru-workflow/prepare-package-signed 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: 1829173 - phase: Packaging - phase-changed: Friday, 17. May 2019 00:03 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 24. May 2019 07:03 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828665] Re: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May
For the confirmation, I'd need guidance. Which source/mutter link to click to reinstall the prior version (or is it all of them?). Since writing the above report, by reflex more Ubuntu updates have been accepted (there have been very many this week - perhaps four or five) - new dpkg.log attached. After each new update the resolutions and frequencies sent to both monitors were correct; without problem. This morning, monitor 2 (the new one) followed the boot sequence in a mode I've never seen before - all pink and at ordinary HD 1920 (it seems). Then it went blank for half a second. Then it put up the usual message that it was changing to 4K at 30 Hz, then the desktop came up fine. [Coincidentally, an email arrived that bug 1714178 (and my bug duplicate 1795439) have been fixed (released) to overcome the modesetting driver 8192x8192 limitation. I may try again using three 4K horizontal monitors - when the third is repaired. Are the patchset and merge to drm-tip before or after this particular incident?]. I feel to add (by experience) that the former damaged monitor 2 was perhaps more vulnerable than most to sudden fast mode changes. With a previous PC (ubuntu 16.04) with Intel HD600, that monitor had to receive a valid mode at a very specific moment (which meant the user had to learn to push on the power buttons precisely one second apart) else the monitor would revert immediately to high Hz modes at inferior resolutions or shut down. With this configuration Intel HD620 and Ubuntu Bionic Beaver, both monitors can be on, will move to sleep mode and wait - great! The user can switch on the PC when they're ready. Just to say that, perhaps monitor 2 was vulnerable to even a blip at 60Hz. On the other hand, that doesn't explain how monitor 1 found itself attempting 4096 which is also part of this bug report. Can I still help in confirmation work by going back to the prior version? ** Attachment added: "dpkg.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1828665/+attachment/5266146/+files/dpkg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828665 Title: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Incomplete Bug description: Now at Ubuntu 18.04.2 LTS, Gnome 3.28.2 Deduction. The user device settings menu for desktop control dual monitors offer the correct modes available. The Bionic Beaver update does something different. Dual monitor configuration (Formerly Primary on Display Port 3840x2160 30Hz, Secondary on HDMI 3840x2160 30Hz on a three video output Intel HD620) for Cancer Research using LibreOffice Calc across both. Upgrades permitted manually rather than auto and usually done within a day. Since five months both monitors were operating HDMI (Display port not connected, not used) with Primary on HDMI2 and Secondary on HDMI1, both at 3840x2160 30Hz. Neither monitor is capable of 60Hz at UHD which is quite alright for office work. When installing such devices, strictly only the 3840x2160 30Hz mode is available on the settings page. After the most recent update (7/8th may), the primary screen was blank on reboot (abnormal) and the secondary screen showed the extended desktop without menus (as usual). Rebooting to see the primary was unsuccessful and then the secondary monitor failed completely (confirmed the next day as graphics card hardware, broken). Cold disconnect of the secondary (awaiting repair), another boot brought up Primary display only yet flickering occasionally. Primary Display. Considering the possibility of error in the graphics since the update - the Device settings (normal user page) revealed that the update had changed the output to HDMI 4096 lines (which the PC monitor can't do and the user can't select - outside specification). I was in such a hurry to save it also from damage that I put back the resolution to 3840x2160 30Hz immediately, without looking at which frequency had been set with the 4096 value. Now on rebooting, the display settings menu shows appropriately only 3840x2160 30 Hz as choice. It seems the Bionic Beaver update needed something else and set 4096 (which the user can't and notwithstanding the original user configuration). Secondary Display. I don't know what it set, but it blew the monitor card. The linux sent either 3840 at 60 Hz or 4096 at any frequency without negociation, without being able to respect the user settings. It's also possible that it used a very low resolution for a few seconds which the secondary monitor can't do either; it's (well, it was) a real PC monitor with choices of DP or HDMI yet can jump into various modes (such as 60/75Hz for gamers). After some Ubuntu
[Kernel-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
Thankyou (my bug report a duplicate of this one). Although my third monitor is defective at the moment I will be using three 4K horizontal (Intel HD620) to run Libreoffice Calc across all three. Thankyou again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828665] Re: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May
It sounds like this bug is now fixed(?). If so then we don't need any further investigation thanks. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1828665 Title: [regression] Reboot after dpkg update set invalid Graphics resolutions (Dual Monitor) since ~7th/8th May Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: Now at Ubuntu 18.04.2 LTS, Gnome 3.28.2 Deduction. The user device settings menu for desktop control dual monitors offer the correct modes available. The Bionic Beaver update does something different. Dual monitor configuration (Formerly Primary on Display Port 3840x2160 30Hz, Secondary on HDMI 3840x2160 30Hz on a three video output Intel HD620) for Cancer Research using LibreOffice Calc across both. Upgrades permitted manually rather than auto and usually done within a day. Since five months both monitors were operating HDMI (Display port not connected, not used) with Primary on HDMI2 and Secondary on HDMI1, both at 3840x2160 30Hz. Neither monitor is capable of 60Hz at UHD which is quite alright for office work. When installing such devices, strictly only the 3840x2160 30Hz mode is available on the settings page. After the most recent update (7/8th may), the primary screen was blank on reboot (abnormal) and the secondary screen showed the extended desktop without menus (as usual). Rebooting to see the primary was unsuccessful and then the secondary monitor failed completely (confirmed the next day as graphics card hardware, broken). Cold disconnect of the secondary (awaiting repair), another boot brought up Primary display only yet flickering occasionally. Primary Display. Considering the possibility of error in the graphics since the update - the Device settings (normal user page) revealed that the update had changed the output to HDMI 4096 lines (which the PC monitor can't do and the user can't select - outside specification). I was in such a hurry to save it also from damage that I put back the resolution to 3840x2160 30Hz immediately, without looking at which frequency had been set with the 4096 value. Now on rebooting, the display settings menu shows appropriately only 3840x2160 30 Hz as choice. It seems the Bionic Beaver update needed something else and set 4096 (which the user can't and notwithstanding the original user configuration). Secondary Display. I don't know what it set, but it blew the monitor card. The linux sent either 3840 at 60 Hz or 4096 at any frequency without negociation, without being able to respect the user settings. It's also possible that it used a very low resolution for a few seconds which the secondary monitor can't do either; it's (well, it was) a real PC monitor with choices of DP or HDMI yet can jump into various modes (such as 60/75Hz for gamers). After some Ubuntu upgrades in the past (blank secondary screen), it was necessary to go back into the monitor menu to switch off again the gamer mode. Something similar happened in 2017 with Light Ubuntu Update. The Secondary (very expensive) display making very alarming noises and staying blank for half a day. Now it's truly broken (I know it's the driver circuit and which parts). Waiting for repair or replacement, the system is in use now with the same Primary PC monitor and a UHD television as secondary to get by. I worked 20 years on PC systems and monitors (for ship control) and accept that in the past we nearly always used a simple basic portable VGA monitor for system upgrades, then reconnected the user's gear later. I think I'll only do (and postpone) Linux upgrades from now using a spare single desktop monitor at 1920x1080. That was a very worrying experience. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sat May 11 11:21:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 620 [1297:4052] InstallationDate: Installed on 2018-09-13 (239 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux F
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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 -- kernel-stable-master-bug: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:building + promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:queued -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:queued To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
for cosmic it's the very same package sudo apt install intel-microcode=3.20180312.0~ubuntu18.04.1 and so far it seems to fix the issue, thanks a lot for the easy to implement workaround. -- 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/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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 -- kernel-stable-master-bug: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building,main:queued + promote-to-proposed: Pending -- builds not complete in ppa signed:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1819413] Re: [ICL] S0ix Enabling
** Changed in: intel
Status: Fix Committed => 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/1819413
Title:
[ICL] S0ix Enabling
Status in intel:
Incomplete
Status in linux package in Ubuntu:
Triaged
Status in linux-oem-osp1 package in Ubuntu:
New
Status in linux-oem-osp1 source package in Bionic:
In Progress
Bug description:
Description:
S0ix-states represent the residency in the Intel® SoC idle standby power
states.
The S0ix states shut off part of the SoC when they are not in use. The S0ix
states are triggered when specific conditions within the SoC have been
achieved,
for example: certain components are in low power states. The SoC consumes the
least amount of power in the deepest (for example, S0i3) state.
S0ix is triggered by two paths:
(1) by system PM, e.g "suspend-to-idle" triggered by pressing the power button
on Android device or command manually triggered on any Linux based distros;
(2) by runtime PM, i.e no system activities with display off.
S0ix should simply work in theory with trigger path (1) if we have the device
drivers ready. On GLK, we require the below PCI device drivers with system PM
support. ACPI device requirements are WIP.
I2C designware PCI driver
USB XHCI PCI ID
Intel trace Hub[NPK) PCI ID
SPI BXT PCI ID
SCSI UFS BXT PCI host ID
Graphics
Audio
PWM
HSUART
Security engine
S0ix with trigger path (2) require work as defined below.
All the above device drivers need to support runtime PM (already defined in
the same LCK above)
PCI root port to support runtime PM
Both paths will require intel_idle driver support for S0ix support.
238f9c11351f8af8534ae0318b4d9acc77b09ee8
8aba056a4ea6da18186025a335a96b2f071e69d3
6769fdbe27d782dfee5e459e25b44baacc7c8459
cfb55af9add9c19806300fdb31f4cd25e67c6d1a
4a5861f714293767980e4948c9a7c9e5e09c9b94
2a13096ac7da07a1bfc9d91fc4a982020e7ded2b
cd89e92b7399a69512b8d855a2dd145c47399bf8
d6827015e671cd17871c9b7a0fabe06c044f7470
0e68eeea9894feeba2edf7ec63e4551b87f39621
e50af8332785355de3cb40d9f5e8c45dbfc86f53
Target Kernel: 5.1
Target Release: 19.10
SRU Justification
[Impact]
Requires patches to make new INTEL CPU IceLake support s0ix
[Fix]
The patch list is provided by Intel
238f9c11351f platform/x86: intel_pmc_core: Quirk to ignore XTAL
shutdown
8aba056a4ea6 platform/x86: intel_pmc_core: Add Package cstates residency
info
6769fdbe27d7 platform/x86: intel_pmc_core: Add ICL platform support
cfb55af9add9 platform/x86: intel_pmc_core: Convert to INTEL_CPU_FAM6 macro
4a5861f71429 platform/x86: intel_pmc_core: Avoid a u32 overflow
2a13096ac7da platform/x86: intel_pmc_core: Include Reserved IP for LTR
cd89e92b7399 platform/x86: intel_pmc_core: Fix file permissions for
ltr_show
d6827015e671 platform/x86: intel_pmc_core: Fix PCH IP name
0e68eeea9894 platform/x86: intel_pmc_core: Fix PCH IP sts reading
e50af8332785 platform/x86: intel_pmc_core: Handle CFL regmap properly
Below commit fix 238f9c11351f ("platform/x86: intel_pmc_core: Quirk to ignore
XTAL shutdown")
9ae11e237d95 platform/x86: intel_pmc_core: Mark local function static
[Test]
Verified on Intel ICL-Y SDP with fwts s2idle test 30 times, the system is
still working.
[Regression Risk]
Low. Those patches are all small changes, and most of them are adding IDs,
should be safe to include them.
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1819413/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266161/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266168/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266164/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266171/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829209 phase: Testing phase-changed: Thursday, 23. May 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-certification-testing: Ongoing -- testing in progress + snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in expected channel(s): + arch=arm64:channel=latest/candidate:rev=91' verification-testing: Ongoing -- testing 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/1829201 Title: linux-snapdragon: 4.4.0-1114.119 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1829209 phase: Testing phase-changed: Thursday, 23. May 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in expected channel(s): arch=arm64:channel=latest/candidate:rev=91' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266162/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829189] Re: linux-snapdragon: 4.15.0-1054.58 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Thursday, 23. May 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-certification-testing: Ongoing -- testing in progress + snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in expected channel(s): + arch=arm64:channel=18/candidate:rev=92' verification-testing: Ongoing -- testing 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/1829189 Title: linux-snapdragon: 4.15.0-1054.58 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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: 1829219 phase: Testing phase-changed: Thursday, 23. May 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in expected channel(s): arch=arm64:channel=18/candidate:rev=92' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266166/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266159/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266165/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266158/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829189] Re: linux-snapdragon: 4.15.0-1054.58 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/HtjuDyma/1040-dragonboard- kernel-4150-105458-92-18 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1829189 Title: linux-snapdragon: 4.15.0-1054.58 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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: 1829219 phase: Testing phase-changed: Thursday, 23. May 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in expected channel(s): arch=arm64:channel=18/candidate:rev=92' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C KVM
** Summary changed:
- test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on
Bionic with PowerPC
+ test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C
KVM
--
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/1811981
Title:
test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
on B/C KVM
Status in QA Regression Testing:
Fix Released
Status in ubuntu-kernel-tests:
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:
New
Bug description:
Kernel Version: 4.15.0-44.47
This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
Power8 and Power9
FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
Ensure kernel efi lockdown is enabled
--
Traceback (most recent call last):
File "./test-kernel-security.py", line 2668, in
test_410_config_lock_down_kernel
self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
File "./test-kernel-security.py", line 207, in assertKernelConfig
self.assertKernelConfigSet(name)
File "./test-kernel-security.py", line 194, in assertKernelConfigSet
'%s option was expected to be set in the kernel config' % name)
AssertionError: LOCK_DOWN_KERNEL 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/1811981/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266167/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker
Snap beta testing complete, no regressions found. Ready for promotion. Results here: https://trello.com/c/TZR30TfI/1041-dragonboard- kernel-440-1114119-91 ** Changed in: kernel-sru-workflow/snap-certification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1829201 Title: linux-snapdragon: 4.4.0-1114.119 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1829209 phase: Testing phase-changed: Thursday, 23. May 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in expected channel(s): arch=arm64:channel=latest/candidate:rev=91' verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] Re: linux-image-4.15.0-48-lowlatency and newer don't boot after update (16.04)(i386)
It does happen for 4.15.0-50-generic too. ** Summary changed: - linux-image-4.15.0-48-lowlatency doesn't boot after update (16.04)(i386) + linux-image-4.15.0-48-lowlatency and newer don't boot after update (16.04)(i386) ** Summary changed: - linux-image-4.15.0-48-lowlatency and newer don't boot after update (16.04)(i386) + linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) ** Tags added: apport-collected ** Description changed: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: user 1820 F pulseaudio + CurrentDesktop: LXDE + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb + InstallationDate: Installed on 2018-10-01 (234 days ago) + InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) + MachineType: TOSHIBA Satellite L300 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid + ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-47-lowlatency N/A + linux-backports-modules-4.15.0-47-lowlatency N/A + linux-firmware1.157.21 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: xenial + Uname: Linux 4.15.0-47-lowlatency i686 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/10/2008 + dmi.bios.vendor: INSYDE + dmi.bios.version: 1.50 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: Base Board Product Name + dmi.board.vendor: Intel Corp. + dmi.board.version: Base Board Version + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: Chassis Manufacturer + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: + dmi.product.family: Type1Family + dmi.product.name: Satellite L300 + dmi.product.version: PSLB0E-014012RU + dmi.sys.vendor: TOSHIBA -- 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/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect pri
[Kernel-packages] [Bug 1827725] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266163/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266170/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266160/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1827725/+attachment/5266169/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827725] Re: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386)
It floods this before reboot: IP: print_modules+0x40/0xbd *pdpt = 36445001 *pde = 0de36063 *pte = Thread overran stack, or stack corrupted Oops: 000 [a1672] PREEMPI SMP PTI Modules linked in: BUG: unable to handle kernel paging request at fffc I don't know which string is first. I can see some video artifacts before rebooting. -- 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/1827725 Title: linux-image-4.15.0-48-lowlatency and newer don't boot after update from 4.15.0-47 (16.04)(i386) Status in linux package in Ubuntu: Incomplete Bug description: Currently I am on 4.15.0-47-lowlatency. I will attach kern.log if ubuntu-bug didn't it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-48-lowlatency 4.15.0-48.51~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-47-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: LXDE Date: Sat May 4 16:49:24 2019 InstallationDate: Installed on 2018-10-01 (214 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1820 F pulseaudio CurrentDesktop: LXDE DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a1a12e2a-cc5c-4136-82c0-e30ab9c9febb InstallationDate: Installed on 2018-10-01 (234 days ago) InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720) MachineType: TOSHIBA Satellite L300 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-47-lowlatency root=UUID=50c3a930-a3e9--b4ea-1646d276c7c6 ro rootflags=subvol=@ ipv6.disable=1 zswap.enabled=0 raid=noautodetect priority=low video=SVIDEO-1:d module_blacklist=r8169,mii,msr,jfs,xfs,bluetooth,hfs,hfsplus,ufs,minix,ntfs,joydev,mac_hid ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-47-lowlatency N/A linux-backports-modules-4.15.0-47-lowlatency N/A linux-firmware1.157.21 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.15.0-47-lowlatency i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/10/2008 dmi.bios.vendor: INSYDE dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.50:bd07/10/2008:svnTOSHIBA:pnSatelliteL300:pvrPSLB0E-014012RU:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.family: Type1Family dmi.product.name: Satellite L300 dmi.product.version: PSLB0E-014012RU dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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 -- kernel-stable-master-bug: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building + promote-to-proposed: Pending -- builds not complete in ppa signed:retry-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:retry-needed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827427] Re: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows
[ 668.026515] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out -- 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/1827427 Title: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows Status in linux package in Ubuntu: Incomplete Bug description: Steps to reproduce: boot into Windows, obtain DHCP IP. either hibernate PC or reboot then boot into Linux; a DHCP IP is not obtainable even if I power cycle my router. To obtain a DHCP IP in Linux on the PC, I must either fully shutdown Windows then cold boot into Linux, or manually reset the ethernet adapter with echo 1 > /sys/bus/pci/devices/:00:19.0/reset The connection then comes good. I can see various DHCPDISCOVER and network-related traffic in journalctl -f during the time the machine is attempting to set an address on the interface, periodically the "activation of network connection failed" error message displays. Other discussion online suggests setting a spoofed, different MAC on the interface I am using Ubuntu 19 and Mint Cinnamon 19.1 to test and can reproduce this over multiple boots. It has apparently been a longstanding bug, perhaps due to how Windows is setting some aspect of the ethernet controller for a WOL or other boot-related operation. Either way, it's entirely confusing. Perhaps resetting the adapter should occur if this situation arises, particularly in LiveUSB/LiveCD scenarios. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 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 CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME Date: Thu May 2 22:06:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME lan1 cbe6c8b2-dab9-347f-8a1d-613294b87483 ethernet 1556833444 Thu May 2 21:44:04 2019 yes -999 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- /etc/NetworkManager/system-connections/lan1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet disconnected limited limited /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 disconnected started limited enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/ubuntu.seed noprompt persistent boot=casper iso-scan/filename=/multiboot/ubuntu-19.04-desktop-amd64/ubuntu-19.04-desktop-amd64.iso quiet -- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True
[Kernel-packages] [Bug 1778932] Re: rsync can trigger system crash
un 26 19:49:20 music kernel: [ 242.955115] BUG: unable to handle kernel paging request at 0220 Jun 26 19:49:20 music kernel: [ 242.955125] IP: find_get_entry+0x4c/0x140 Jun 26 19:49:20 music kernel: [ 242.955126] PGD 0 P4D 0 Jun 26 19:49:20 music kernel: [ 242.955129] Oops: [#1] PREEMPT SMP NOPTI Please test mainline kernel and see if it helps: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc1/ -- 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/1778932 Title: rsync can trigger system crash Status in linux package in Ubuntu: Confirmed Bug description: I'm not sure how much of this is rsync or something else in my system. I can reliably trigger this using rsync to transfer files from one drive to another drive on my computer. the source is ssd and destination is mdadm raid 1 partition. will attach syslog messages. after it is triggered, the the system becomes unresponsive and requires a hard reboot. running rysnc as user, no special privileges. root@music:~# lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 apt-cache policy rsync rsync: Installed: 3.1.2-2.1ubuntu1 Candidate: 3.1.2-2.1ubuntu1 Version table: *** 3.1.2-2.1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status uname -a Linux music 4.15.0-23-lowlatency #25-Ubuntu SMP PREEMPT Wed May 23 20:39:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rsync 3.1.2-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Jun 27 10:08:36 2018 InstallationDate: Installed on 2018-03-31 (87 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_US PATH=(custom, no user) SourcePackage: rsync UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: papa 5200 F pulseaudio /dev/snd/controlC0: papa 5200 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=ca9d6033-d98d-4fba-be24-599f112ac941 InstallationDate: Installed on 2018-03-31 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-lowlatency root=/dev/mapper/xubuntu--vg-root ro splash fsck.mode=force fsck.repair=yes vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-lowlatency N/A linux-backports-modules-4.15.0-23-lowlatency N/A linux-firmware1.173.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-23-lowlatency x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: False 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/1778932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827427] Re: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows
Please test mainline kernel and see if it helps: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc1/ -- 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/1827427 Title: DHCP IP not obtainable if booting into Linux from suspended/hibernated/rebooted Windows Status in linux package in Ubuntu: Incomplete Bug description: Steps to reproduce: boot into Windows, obtain DHCP IP. either hibernate PC or reboot then boot into Linux; a DHCP IP is not obtainable even if I power cycle my router. To obtain a DHCP IP in Linux on the PC, I must either fully shutdown Windows then cold boot into Linux, or manually reset the ethernet adapter with echo 1 > /sys/bus/pci/devices/:00:19.0/reset The connection then comes good. I can see various DHCPDISCOVER and network-related traffic in journalctl -f during the time the machine is attempting to set an address on the interface, periodically the "activation of network connection failed" error message displays. Other discussion online suggests setting a spoofed, different MAC on the interface I am using Ubuntu 19 and Mint Cinnamon 19.1 to test and can reproduce this over multiple boots. It has apparently been a longstanding bug, perhaps due to how Windows is setting some aspect of the ethernet controller for a WOL or other boot-related operation. Either way, it's entirely confusing. Perhaps resetting the adapter should occur if this situation arises, particularly in LiveUSB/LiveCD scenarios. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 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 CasperVersion: 1.405 CurrentDesktop: ubuntu:GNOME Date: Thu May 2 22:06:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME lan1 cbe6c8b2-dab9-347f-8a1d-613294b87483 ethernet 1556833444 Thu May 2 21:44:04 2019 yes -999 no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- /etc/NetworkManager/system-connections/lan1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet disconnected limited limited /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 disconnected started limited enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: lono wireless extensions. eno1 no wireless extensions. LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUS All Series Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: file=/cdrom/preseed/ubuntu.seed noprompt persistent boot=casper iso-scan/filename=/multiboot/ubuntu-19.04-desktop-amd64/ubuntu-19.04-desktop-amd64.iso quiet -- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 RfKill: Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGro
[Kernel-packages] [Bug 1829605] Re: Asus N53SV laptop's Internal bluetooth is not working
I attach image from the Asus Support center, confirming that Asus N53SV computer does have previously mentioned bluetooth module. ** Attachment added: "unnamed.jpg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829605/+attachment/5266187/+files/unnamed.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829605 Title: Asus N53SV laptop's Internal bluetooth is not working Status in linux package in Ubuntu: Incomplete Bug description: I have just installed latest Ubuntu 19.04 operating system and Bluetooth seems to be not enabled. I think that it needs additional drivers, but unsure. If anyone needs, here is laptop's specific internal receiver model: Asus N53SV Laptop's internal bluetooth Module: BLUETOOTH 2.1 BCM2070 MODULE (Built-in Bluetooth™ V2.1+EDR) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: naudotojas 1495 F pulseaudio /dev/snd/pcmC0D0p: naudotojas 1495 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK Computer Inc. N53SV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7dd0eb68-06dc-4ae1-b0d8-1652b55f7ac3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SV.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SV.212:bd04/07/2011:svnASUSTeKComputerInc.:pnN53SV:pvr1.0:rvnASUSTeKComputerInc.:rnN53SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N53SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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 -- kernel-stable-master-bug: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:retry-needed + promote-to-proposed: Pending -- builds not complete in ppa signed:building -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Holding before Promote to Proposed phase-changed: Friday, 24. May 2019 07:03 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:building To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825753] Re: fan speed not reported with Ubuntu 18.10 and 19.04
So it works on Linux v4.15, but not v4.18 and v5.0? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825753 Title: fan speed not reported with Ubuntu 18.10 and 19.04 Status in Hardware Sensors Indicator: Invalid Status in linux package in Ubuntu: Incomplete Bug description: after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list of available sensors --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jean-luc 1975 F pulseaudio /dev/snd/controlC1: jean-luc 1975 F pulseaudio /dev/snd/pcmC1D0p: jean-luc 1975 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-21 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS13 9333 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/27/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0D13CR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay System dmi.product.name: XPS13 9333 dmi.product.sku: 060A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2
** Changed in: linux-raspi2 (Ubuntu) Assignee: Paolo Pisati (p-pisati) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1808056 Title: vmlinuz is very large in arm64 -raspi2 Status in flash-kernel package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: The debs are close to the same size: mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb But the vmlinuz on arm64 is several times larger: $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw--- root/root 6633048 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw--- root/root 23914504 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 This forced us to make the boot partition larger for the raspi3 b+ arm64 image we made. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1808056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829191] Re: linux-oem: 4.15.0-1039.44 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Promote to Proposed phase-changed: Thursday, 23. May 2019 20:39 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed -- 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/1829191 Title: linux-oem: 4.15.0-1039.44 -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: 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-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: 1829219 phase: Promote to Proposed phase-changed: Thursday, 23. May 2019 20:39 UTC reason: promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829605] Re: Asus N53SV laptop's Internal bluetooth is not working
Thanks. I still can't see any trace of any Bluetooth hardware installed in your machine, according to the attached files. Maybe a kernel engineer would have a better idea than me... ** 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/1829605 Title: Asus N53SV laptop's Internal bluetooth is not working Status in linux package in Ubuntu: Confirmed Bug description: I have just installed latest Ubuntu 19.04 operating system and Bluetooth seems to be not enabled. I think that it needs additional drivers, but unsure. If anyone needs, here is laptop's specific internal receiver model: Asus N53SV Laptop's internal bluetooth Module: BLUETOOTH 2.1 BCM2070 MODULE (Built-in Bluetooth™ V2.1+EDR) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: naudotojas 1495 F pulseaudio /dev/snd/pcmC0D0p: naudotojas 1495 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK Computer Inc. N53SV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7dd0eb68-06dc-4ae1-b0d8-1652b55f7ac3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SV.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SV.212:bd04/07/2011:svnASUSTeKComputerInc.:pnN53SV:pvr1.0:rvnASUSTeKComputerInc.:rnN53SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N53SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829605] 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/1829605 Title: Asus N53SV laptop's Internal bluetooth is not working Status in linux package in Ubuntu: Confirmed Bug description: I have just installed latest Ubuntu 19.04 operating system and Bluetooth seems to be not enabled. I think that it needs additional drivers, but unsure. If anyone needs, here is laptop's specific internal receiver model: Asus N53SV Laptop's internal bluetooth Module: BLUETOOTH 2.1 BCM2070 MODULE (Built-in Bluetooth™ V2.1+EDR) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: naudotojas 1495 F pulseaudio /dev/snd/pcmC0D0p: naudotojas 1495 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK Computer Inc. N53SV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7dd0eb68-06dc-4ae1-b0d8-1652b55f7ac3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SV.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SV.212:bd04/07/2011:svnASUSTeKComputerInc.:pnN53SV:pvr1.0:rvnASUSTeKComputerInc.:rnN53SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N53SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-disco ** 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: 1829173 - phase: Holding before Promote to Proposed - phase-changed: Friday, 24. May 2019 07:03 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 24. May 2019 10:03 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:building + 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Ready for Promote to Proposed phase-changed: Friday, 24. May 2019 10:03 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/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829605] Re: Asus N53SV laptop's Internal bluetooth is not working
BCM2070 is a USB device but it's not listed in lsusb. -- 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/1829605 Title: Asus N53SV laptop's Internal bluetooth is not working Status in linux package in Ubuntu: Confirmed Bug description: I have just installed latest Ubuntu 19.04 operating system and Bluetooth seems to be not enabled. I think that it needs additional drivers, but unsure. If anyone needs, here is laptop's specific internal receiver model: Asus N53SV Laptop's internal bluetooth Module: BLUETOOTH 2.1 BCM2070 MODULE (Built-in Bluetooth™ V2.1+EDR) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: naudotojas 1495 F pulseaudio /dev/snd/pcmC0D0p: naudotojas 1495 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-05-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK Computer Inc. N53SV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=lt_LT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=7dd0eb68-06dc-4ae1-b0d8-1652b55f7ac3 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/07/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N53SV.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N53SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN53SV.212:bd04/07/2011:svnASUSTeKComputerInc.:pnN53SV:pvr1.0:rvnASUSTeKComputerInc.:rnN53SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: N dmi.product.name: N53SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829201] Re: linux-snapdragon: 4.4.0-1114.119 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829209 phase: Testing phase-changed: Thursday, 23. May 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in expected channel(s): - arch=arm64:channel=latest/candidate:rev=91' verification-testing: Ongoing -- testing 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/1829201 Title: linux-snapdragon: 4.4.0-1114.119 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1829209 phase: Testing phase-changed: Thursday, 23. May 2019 13:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress 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/1829201/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829189] Re: linux-snapdragon: 4.15.0-1054.58 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Testing phase-changed: Thursday, 23. May 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap dragonboard-kernel not in expected channel(s): - arch=arm64:channel=18/candidate:rev=92' verification-testing: Ongoing -- testing 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/1829189 Title: linux-snapdragon: 4.15.0-1054.58 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-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: 1829219 phase: Testing phase-changed: Thursday, 23. May 2019 13:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress 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/1829189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Ready for Promote to Proposed phase-changed: Friday, 24. May 2019 10:03 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/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827697] Please test proposed package
Hello 林博仁(Buo-ren, or anyone else affected, Accepted dkms into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu11.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dkms (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1827697 Title: Enroll key whiptail prompt blocks kernel header package upgrades Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Cosmic: Fix Committed Status in dkms source package in Disco: Fix Committed Status in dkms source package in Eoan: Fix Released Bug description: I noticed that sometimes the system upgrade is blocked in the kernel header package's configure phase, in the process manager I found that it is blocked by the "Configuring Secure Boot" whiptail prompt started by `update-secureboot-policy --enroll-key` which doesn't surface to the terminal and hence not interactable. Refer the attached screenshot for the process status at the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827697] Re: Enroll key whiptail prompt blocks kernel header package upgrades
Hello 林博仁(Buo-ren, or anyone else affected, Accepted dkms into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.6.1-4ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dkms (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco ** Changed in: dkms (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Tags added: verification-needed-cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1827697 Title: Enroll key whiptail prompt blocks kernel header package upgrades Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Cosmic: Fix Committed Status in dkms source package in Disco: Fix Committed Status in dkms source package in Eoan: Fix Released Bug description: I noticed that sometimes the system upgrade is blocked in the kernel header package's configure phase, in the process manager I found that it is blocked by the "Configuring Secure Boot" whiptail prompt started by `update-secureboot-policy --enroll-key` which doesn't surface to the terminal and hence not interactable. Refer the attached screenshot for the process status at the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827697] Please test proposed package
Hello 林博仁(Buo-ren, or anyone else affected, Accepted dkms into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu9.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: dkms (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1827697 Title: Enroll key whiptail prompt blocks kernel header package upgrades Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Cosmic: Fix Committed Status in dkms source package in Disco: Fix Committed Status in dkms source package in Eoan: Fix Released Bug description: I noticed that sometimes the system upgrade is blocked in the kernel header package's configure phase, in the process manager I found that it is blocked by the "Configuring Secure Boot" whiptail prompt started by `update-secureboot-policy --enroll-key` which doesn't surface to the terminal and hence not interactable. Refer the attached screenshot for the process status at the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827697] Please test proposed package
Hello 林博仁(Buo-ren, or anyone else affected, Accepted dkms into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-2ubuntu11.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1827697 Title: Enroll key whiptail prompt blocks kernel header package upgrades Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Xenial: Fix Committed Status in dkms source package in Bionic: Fix Committed Status in dkms source package in Cosmic: Fix Committed Status in dkms source package in Disco: Fix Committed Status in dkms source package in Eoan: Fix Released Bug description: I noticed that sometimes the system upgrade is blocked in the kernel header package's configure phase, in the process manager I found that it is blocked by the "Configuring Secure Boot" whiptail prompt started by `update-secureboot-policy --enroll-key` which doesn't surface to the terminal and hence not interactable. Refer the attached screenshot for the process status at the time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1827697/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830359] [NEW] cpuset_base_ops from controller test suite in LTP failed
Public bug reported: Issue found on Disco with node glameow: startup='Fri May 24 10:23:44 2019' cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected string cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result - Expected string - "0" cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 65 TFAIL: cpuset.mems: Test result - Expected string - "0" cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 101 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 103 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 105 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 107 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 109 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 111 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 113 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 115 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 117 TPASS: cpuset.memory_spread_slab: Get the expected string cpuset_base_ops 119 TPASS: cpuset.memory_spread_slab: Get the expected string cpuset_base_ops 121 TPASS: cpuset.memory_spread_slab: Get the expected string cpuset_base_ops 123 TPASS: cpuset.memory_spread_slab: Get the expected string cpuset_base_ops 125 TPASS: cpuset.memory_spread_slab: Get the expected string cpuset_base_ops 127 TPASS: cpuset.sched_load_balance: Get the expected string cpuset_base_ops 129 TPASS: cpuset.sched_load_balance: Get the expected string cpuset_base_ops 131 TPASS: cpuset.sched_load_balance: Get the expected string cpuset_base_ops 133 TPASS: cpuset.sched_load_balance: Get the expected string cpuset_base_ops 135 TPASS: cpuset.sched_load_balance: Get the expected string cpuset_base_ops 137 TPASS: cpuset.memory_pressure_enabled: Get the expected
[Kernel-packages] [Bug 1830359] 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 1830359 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/1830359 Title: cpuset_base_ops from controller test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:23:44 2019' cpuset_base_ops 1 TPASS: cpuset.cpus(READONLY): Get the expected string cpuset_base_ops 3 TPASS: cpuset.mems(READONLY): Get the expected string cpuset_base_ops 5 TPASS: cpuset.memory_pressure(READONLY): Get the expected string cpuset_base_ops 7 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 9 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 11 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 13 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 15 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 17 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 19 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 21 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 23 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 25 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 27 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 29 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 31 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 33 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 35 TPASS: cpuset.cpus: Get the expected string cpuset_base_ops 37 TFAIL: cpuset.cpus: Test result - Expected string - "0" cpuset_base_ops 39 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 41 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 43 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 45 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 47 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 49 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 51 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 53 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 55 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 57 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 59 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 61 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 63 TPASS: cpuset.mems: Get the expected string cpuset_base_ops 65 TFAIL: cpuset.mems: Test result - Expected string - "0" cpuset_base_ops 67 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 69 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 71 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 73 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 75 TPASS: cpuset.cpu_exclusive: Get the expected string cpuset_base_ops 77 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 79 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 81 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 83 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 85 TPASS: cpuset.mem_exclusive: Get the expected string cpuset_base_ops 87 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 89 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 91 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 93 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 95 TPASS: cpuset.mem_hardwall: Get the expected string cpuset_base_ops 97 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 99 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 101 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 103 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 105 TPASS: cpuset.memory_migrate: Get the expected string cpuset_base_ops 107 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 109 TPASS: cpuset.memory_spread_page: Get the expected string cpuset_base_ops 111 TPASS: cpuset.memory_spread_page: Get the expecte
[Kernel-packages] [Bug 1830360] [NEW] cpuset_load_balance from controller test suite in LTP failed
Public bug reported: Issue found on Disco with node glameow: startup='Fri May 24 10:24:55 2019' cpuset_load_balance 1 TINFO: general group load balance test cpuset_load_balance 1 TINFO: root group info: cpuset_load_balance 1 TINFO: sched load balance: 0 cpuset_load_balance 1 TINFO: general group info: cpuset_load_balance 1 TINFO: cpus: - cpuset_load_balance 1 TINFO: sched load balance: 1 cpuset_load_balance 1 TFAIL: load balance test failed. cpuset_load_balance 3 TINFO: general group load balance test cpuset_load_balance 3 TINFO: root group info: cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TINFO: general group info: cpuset_load_balance 3 TINFO: cpus: 1 cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TFAIL: load balance test failed. cpuset_load_balance 5 TINFO: general group load balance test cpuset_load_balance 5 TINFO: root group info: cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TINFO: general group info: cpuset_load_balance 5 TINFO: cpus: - cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TFAIL: load balance test failed. cpuset_load_balance 7 TINFO: general group load balance test cpuset_load_balance 7 TINFO: root group info: cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TINFO: general group info: cpuset_load_balance 7 TINFO: cpus: 1 cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TFAIL: load balance test failed. cpuset_load_balance 9 TINFO: general group load balance test cpuset_load_balance 9 TINFO: root group info: cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TINFO: general group info: cpuset_load_balance 9 TINFO: cpus: 1,2 cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TFAIL: load balance test failed. cpuset_load_balance 11 TINFO: general group load balance test cpuset_load_balance 11 TINFO: root group info: cpuset_load_balance 11 TINFO: sched load balance: 0 cpuset_load_balance 11 TINFO: general group info: cpuset_load_balance 11 TINFO: cpus: 1,2 cpuset_load_balance 11 TINFO: sched load balance: 1 cpuset_load_balance 11 TFAIL: load balance test failed. cpuset_load_balance 13 TINFO: general group load balance test cpuset_load_balance 13 TINFO: root group info: cpuset_load_balance 13 TINFO: sched load balance: 0 cpuset_load_balance 13 TINFO: general group info: cpuset_load_balance 13 TINFO: cpus: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39 cpuset_load_balance 13 TINFO: sched load balance: 1 cpuset_load_balance 13 TFAIL: load balance test failed. cpuset_load_balance 15 TINFO: general group load balance test cpuset_load_balance 15 TINFO: root group info: cpuset_load_balance 15 TINFO: sched load balance: 0 cpuset_load_balance 15 TINFO: general group1 info: cpuset_load_balance 15 TINFO: cpus: 1 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: general group2 info: cpuset_load_balance 15 TINFO: cpus: 0 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: CPU hotplug: none cpuset_load_balance 15 TFAIL: load balance test failed. cpuset_load_balance 17 TINFO: general group load balance test cpuset_load_balance 17 TINFO: root group info: cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: general group1 info: cpuset_load_balance 17 TINFO: cpus: 1,2 cpuset_load_balance 17 TINFO: sched load balance: 1 cpuset_load_balance 17 TINFO: general group2 info: cpuset_load_balance 17 TINFO: cpus: 0-3 cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: CPU hotplug: none cpuset_load_balance 17 TFAIL: load balance test failed. cpuset_load_balance 19 TINFO: general group load balance test cpuset_load_balance 19 TINFO: root group info: cpuset_load_balance 19 TINFO: sched load balance: 0 cpuset_load_balance 19 TINFO: general group1 info: cpuset_load_balance 19 TINFO: cpus: 1,2 cpuset_load_balance 19 TINFO: sched load balance: 1 cpuset_load_balance 19 TINFO: general group2 info: cpuset_load_balance 19 TINFO: cpus: 0,3 cpuset_load_balance 19 TINFO: sched load balance: 1 cpuset_load_balance 19 TINFO: CPU hotplug: none cpuset_load_balance 19 TFAIL: load balance test failed. cpuset_load_balance 21 TINFO: general group load balance test cpuset_load_balance 21 TINFO: root group info: cpuset_load_balance 21 TINFO: sched load balance: 0 cpuset_load_balance 21 TINFO: general group1 info: cpuset_load_balance 21 TINFO: cpus: 1,2 cpuset_load_balance 21 TINFO: sched load balance: 1 cpuset_load_balance 21 TINFO: general group2 info: cpuset_load_balance 21 TINFO:
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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: 1829173 - phase: Ready for Promote to Proposed - phase-changed: Friday, 24. May 2019 10:03 UTC + phase: Promote to Proposed + phase-changed: Friday, 24. May 2019 11:03 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Promote to Proposed phase-changed: Friday, 24. May 2019 11:03 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/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830361] [NEW] cpuset_sched_domains from controller test suite in LTP failed
Public bug reported: Issue found on Disco with node glameow: startup='Fri May 24 10:24:26 2019' cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 1 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 1 TFAIL: partition sched domains failed. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 3 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 5 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 5 TFAIL: partition sched domains failed. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 7 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 7 TFAIL: partition sched domains failed. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 9 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 11 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 11 TFAIL: partition sched domains failed. cpuset_sched_domains 13 TINFO: general group load balance test cpuset_sched_domains 13 TINFO: root group info: cpuset_sched_domains 13 TINFO: sched load balance: 0 cpuset_sched_domains 13 TINFO: general group info: cpuset_sched_domains 13 TINFO: cpus: - cpuset_sched_domains 13 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 13 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 13 TFAIL: partition sched domains failed. cpuset_sched_domains 15 TINFO: general group load balance test cpuset_sched_domains 15 TINFO: root group info: cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_sched_domains 15 TINFO: general group info: cpuset_sched_domains 15 TINFO: cpus: 1 cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 15 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 15 TFAIL: partition sched domains failed. cpuset_sched_domains 17 TINFO: general group load balance test cpuset_sched_domains 17 TINFO: root group info: cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_sched_domains 17 TINFO: general group info: cpuset_sched_domains 17 TINFO: cpus: - cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 17 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 17 TFAIL: partition sched domains failed. cpuset_sched_domains 19 TINFO: general group load balance test cpuset_sched_domains 19 TINFO: root group info: cpuset_sched_domains 19 TINFO: sched load balance: 1 cpuset_sched_domains 19 TINFO: general group info: cpuset_sched_domains 19 TINFO: cpus: 1 cpuset_sched_domains 19 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 19 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 19 TFAIL: partition sched domains failed. cpuset_sched_domains 21 TINFO: general group load balance test cpuset_sched_domains 21 TINFO: root group info:
[Kernel-packages] [Bug 1828035] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2019-05-24 07:01 EDT--- Does the problem goes away when you unload the aes_s390 module and also prevent loading it. (maybe use a blacklist statement in modprobe.conf) -- 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/1828035 Title: StrongSwan with GCM and large packet sizes produces unstable behavior Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Status in strongswan package in Ubuntu: Incomplete Bug description: StrongSwan with GCM and large packet sizes produces unstable behavior when used in Linux native environment. ---uname output--- Linux ubu01 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:29:11 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = 3906 / M04 (z14), LPAR (dedicated) ---Debugger--- A debugger is not configured ---Steps to Reproduce--- On two separate machines (Linux native), install StrongSwan and on both machines, configure the encryption with aes128gcm8 for IPsec. Then run the following command from one of the machine: ``` $# ping -s 1024 ``` Small packet sizes are working as expected. However, anything large (around 1024 bytes or more) are sometimes returning wrong values, or the packets are getting lost. This problem does not occur for ciphers not involving GCM. Userspace tool common name: StrongSwan The userspace tool has the following bit modes: both Userspace package: StrongSwan Userspace tool obtained from project website: na -Attach ltrace and strace of userspace application. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828035/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657952] Re: package ocl-icd-opencl-dev 2.2.8-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/ocl-icd-opencl-dev/changelog.Debian.gz', which is different
this works fine now since bionic at least ** Changed in: ocl-icd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hundredpapercuts Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ocl-icd in Ubuntu. https://bugs.launchpad.net/bugs/1657952 Title: package ocl-icd-opencl-dev 2.2.8-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/ocl-icd-opencl- dev/changelog.Debian.gz', which is different from other instances of package ocl-icd-opencl-dev:i386 Status in One Hundred Papercuts: Fix Released Status in ocl-icd package in Ubuntu: Fix Released Bug description: When trying to install the olc-icd-opencl-dev:i386 package (there is already an ocl-icd-opencl-dev:amd64 package) it will complain about: $ sudo apt-get install ocl-icd-opencl-dev:i386 Reading package lists... Done Building dependency tree Reading state information... Done Recommended packages: libpoclu-dev:i386 The following NEW packages will be installed: ocl-icd-opencl-dev:i386 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/3,546 B of archives. After this operation, 20.5 kB of additional disk space will be used. (Reading database ... 223711 files and directories currently installed.) Preparing to unpack .../ocl-icd-opencl-dev_2.2.8-1_i386.deb ... Unpacking ocl-icd-opencl-dev:i386 (2.2.8-1) ... dpkg: error processing archive /var/cache/apt/archives/ocl-icd-opencl-dev_2.2.8-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/ocl-icd-opencl-dev/changelog.Debian.gz', which is different from other instances of package ocl-icd-opencl-dev:i386 Errors were encountered while processing: /var/cache/apt/archives/ocl-icd-opencl-dev_2.2.8-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: ocl-icd-opencl-dev 2.2.8-1 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 AptOrdering: ocl-icd-libopencl1: Install ocl-icd-opencl-dev: Install ocl-icd-libopencl1: Configure ocl-icd-opencl-dev: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 19 05:47:41 2017 DuplicateSignature: package:ocl-icd-opencl-dev:2.2.8-1 Unpacking ocl-icd-opencl-dev:i386 (2.2.8-1) ... dpkg: error processing archive /var/cache/apt/archives/ocl-icd-opencl-dev_2.2.8-1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/ocl-icd-opencl-dev/changelog.Debian.gz', which is different from other instances of package ocl-icd-opencl-dev:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/ocl-icd-opencl-dev/changelog.Debian.gz', which is different from other instances of package ocl-icd-opencl-dev:i386 InstallationDate: Installed on 2017-01-19 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: ocl-icd Title: package ocl-icd-opencl-dev 2.2.8-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/ocl-icd-opencl-dev/changelog.Debian.gz', which is different from other instances of package ocl-icd-opencl-dev:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1657952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1466194] Re: package ocl-icd-libopencl1:amd64 2.2.3-1 failed to install/upgrade: package ocl-icd-libopencl1:amd64 is already installed and configured
no idea why, but isn't related to the package being buggy at least ** Changed in: ocl-icd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ocl-icd in Ubuntu. https://bugs.launchpad.net/bugs/1466194 Title: package ocl-icd-libopencl1:amd64 2.2.3-1 failed to install/upgrade: package ocl-icd-libopencl1:amd64 is already installed and configured Status in ocl-icd package in Ubuntu: Invalid Bug description: . ProblemType: Package DistroRelease: Ubuntu 15.04 Package: ocl-icd-libopencl1:amd64 2.2.3-1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu3.1 Architecture: amd64 Date: Wed Jun 17 20:45:46 2015 Dependencies: gcc-5-base 5.1~rc1-0ubuntu1 libc6 2.21-0ubuntu4 libgcc1 1:5.1~rc1-0ubuntu1 multiarch-support 2.21-0ubuntu4 DuplicateSignature: package:ocl-icd-libopencl1:amd64:2.2.3-1:package ocl-icd-libopencl1:amd64 is already installed and configured ErrorMessage: package ocl-icd-libopencl1:amd64 is already installed and configured InstallationDate: Installed on 2015-06-17 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: ocl-icd Title: package ocl-icd-libopencl1:amd64 2.2.3-1 failed to install/upgrade: package ocl-icd-libopencl1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocl-icd/+bug/1466194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830362] [NEW] runpwtests03 from power_management_tests test suite in LTP failed
Public bug reported: Issue found on Disco with node glameow: startup='Fri May 24 10:57:20 2019' /opt/ltp/testcases/bin/runpwtests03.sh: 29: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found find: ‘/sys/devices/system/cpu/cpu40/cpufreq/’: No such file or directory /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Checking cpu freq sysfs files Power_Management03 1 TPASS: CPUFREQ sysfs tests /opt/ltp/testcases/bin/runpwtests03.sh: 55: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found /opt/ltp/testcases/bin/runpwtests03.sh: 62: /opt/ltp/testcases/bin/runpwtests03.sh: cannot create /sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- performance for cpu40 /opt/ltp/testcases/bin/runpwtests03.sh: 62: /opt/ltp/testcases/bin/runpwtests03.sh: cannot create /sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- powersave for cpu40 Power_Management03 2 TFAIL: Changing governors cat: '/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies': No such file or directory /opt/ltp/testcases/bin/runpwtests03.sh: 83: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Changing cpu frequencies Power_Management03 3 TPASS: Changing frequncies modprobe: invalid option -- 'l' modprobe: invalid option -- 'l' Power_Management03 4 TPASS: Loading and Unloading of governor kernel modules tag=runpwtests03 stime=1558695440 dur=2 exit=exited stat=1 core=no cu=28 cs=7 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 07:49 seq crw-rw 1 root audio 116, 33 May 21 07:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri May 24 11:07:37 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco uec-images ** Also affects: ubuntu-kernel-tests 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/1830362 Title: runpwtests03 from power_management_tests test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:57:20 2019' /opt/ltp/testcases/bin/runpwtests03.sh: 29: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found find: ‘/sys/devices/system/cpu/cpu40/cpufreq/’: No such file or directory /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Checking cpu freq sysfs files Power_Management03 1 TPASS: CPUFREQ sysfs tests /opt/ltp/testcases/bin/runpwtests03.sh: 55: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found /opt/ltp/testcases/bin/runpwtests03.sh: 62: /opt/ltp/testcases/bin/runpwtests03.sh: cannot create /sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- performance for cpu40 /opt/ltp/testcases/bin/runpwtests03.sh: 62: /opt/ltp/testcases/bin/runpwtests03.sh: cannot create /sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Promote to Proposed phase-changed: Friday, 24. May 2019 11:03 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/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830011] Re: cve-2017-17053 from cve test suite in LTP failed
It's the insmod01_sh test from commands test suite that taints the kernel: glameow kernel: [271396.718171] ltp_insmod01: loading out-of-tree module taints kernel. glameow kernel: [271396.718175] ltp_insmod01: module license 'unspecified' taints kernel. glameow kernel: [271396.718176] Disabling lock debugging due to kernel taint glameow kernel: [271396.718238] ltp_insmod01: module verification failed: signature and/or required key missing - tainting kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830011 Title: cve-2017-17053 from cve test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Cosmic: Confirmed Bug description: This CVE (2017-17053)[1] has been fixed in our kernels However the cve-2017-17053 test in CVE test suite from LTP will complain that: tag=cve-2017-17053 stime=1558483177 cmdline="cve-2017-17053" contacts="" analysis=exit <<>> tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s tst_taint.c:88: BROK: Kernel is already tainted: 14849 Summary: passed 0 failed 0 skipped 0 warnings 0 <<>> This is because there are some other tests failed before this one, and taints the kernel. [1] https://people.canonical.com/~ubuntu- security/cve/2017/CVE-2017-17053.html ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-20-generic 4.18.0-20.21 ProcVersionSignature: User Name 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 09:45 seq crw-rw 1 root audio 116, 33 May 22 09:45 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.3 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: Wed May 22 09:49:10 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.175.4 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830360] 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 1830360 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/1830360 Title: cpuset_load_balance from controller test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:24:55 2019' cpuset_load_balance 1 TINFO: general group load balance test cpuset_load_balance 1 TINFO: root group info: cpuset_load_balance 1 TINFO: sched load balance: 0 cpuset_load_balance 1 TINFO: general group info: cpuset_load_balance 1 TINFO: cpus: - cpuset_load_balance 1 TINFO: sched load balance: 1 cpuset_load_balance 1 TFAIL: load balance test failed. cpuset_load_balance 3 TINFO: general group load balance test cpuset_load_balance 3 TINFO: root group info: cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TINFO: general group info: cpuset_load_balance 3 TINFO: cpus: 1 cpuset_load_balance 3 TINFO: sched load balance: 0 cpuset_load_balance 3 TFAIL: load balance test failed. cpuset_load_balance 5 TINFO: general group load balance test cpuset_load_balance 5 TINFO: root group info: cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TINFO: general group info: cpuset_load_balance 5 TINFO: cpus: - cpuset_load_balance 5 TINFO: sched load balance: 1 cpuset_load_balance 5 TFAIL: load balance test failed. cpuset_load_balance 7 TINFO: general group load balance test cpuset_load_balance 7 TINFO: root group info: cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TINFO: general group info: cpuset_load_balance 7 TINFO: cpus: 1 cpuset_load_balance 7 TINFO: sched load balance: 1 cpuset_load_balance 7 TFAIL: load balance test failed. cpuset_load_balance 9 TINFO: general group load balance test cpuset_load_balance 9 TINFO: root group info: cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TINFO: general group info: cpuset_load_balance 9 TINFO: cpus: 1,2 cpuset_load_balance 9 TINFO: sched load balance: 0 cpuset_load_balance 9 TFAIL: load balance test failed. cpuset_load_balance 11 TINFO: general group load balance test cpuset_load_balance 11 TINFO: root group info: cpuset_load_balance 11 TINFO: sched load balance: 0 cpuset_load_balance 11 TINFO: general group info: cpuset_load_balance 11 TINFO: cpus: 1,2 cpuset_load_balance 11 TINFO: sched load balance: 1 cpuset_load_balance 11 TFAIL: load balance test failed. cpuset_load_balance 13 TINFO: general group load balance test cpuset_load_balance 13 TINFO: root group info: cpuset_load_balance 13 TINFO: sched load balance: 0 cpuset_load_balance 13 TINFO: general group info: cpuset_load_balance 13 TINFO: cpus: 0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39 cpuset_load_balance 13 TINFO: sched load balance: 1 cpuset_load_balance 13 TFAIL: load balance test failed. cpuset_load_balance 15 TINFO: general group load balance test cpuset_load_balance 15 TINFO: root group info: cpuset_load_balance 15 TINFO: sched load balance: 0 cpuset_load_balance 15 TINFO: general group1 info: cpuset_load_balance 15 TINFO: cpus: 1 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: general group2 info: cpuset_load_balance 15 TINFO: cpus: 0 cpuset_load_balance 15 TINFO: sched load balance: 1 cpuset_load_balance 15 TINFO: CPU hotplug: none cpuset_load_balance 15 TFAIL: load balance test failed. cpuset_load_balance 17 TINFO: general group load balance test cpuset_load_balance 17 TINFO: root group info: cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: general group1 info: cpuset_load_balance 17 TINFO: cpus: 1,2 cpuset_load_balance 17 TINFO: sched load balance: 1 cpuset_load_balance 17 TINFO: general group2 info: cpuset_load_balance 17 TINFO: cpus: 0-3 cpuset_load_balance 17 TINFO: sched load balance: 0 cpuset_load_balance 17 TINFO: CPU hotp
[Kernel-packages] [Bug 1830361] 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 1830361 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/1830361 Title: cpuset_sched_domains from controller test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:24:26 2019' cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 1 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 1 TFAIL: partition sched domains failed. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 3 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 5 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 5 TFAIL: partition sched domains failed. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 7 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 7 TFAIL: partition sched domains failed. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 9 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 11 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 11 TFAIL: partition sched domains failed. cpuset_sched_domains 13 TINFO: general group load balance test cpuset_sched_domains 13 TINFO: root group info: cpuset_sched_domains 13 TINFO: sched load balance: 0 cpuset_sched_domains 13 TINFO: general group info: cpuset_sched_domains 13 TINFO: cpus: - cpuset_sched_domains 13 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 13 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 13 TFAIL: partition sched domains failed. cpuset_sched_domains 15 TINFO: general group load balance test cpuset_sched_domains 15 TINFO: root group info: cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_sched_domains 15 TINFO: general group info: cpuset_sched_domains 15 TINFO: cpus: 1 cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:72: partition domains failed. cpuset_sched_domains 15 TINFO: cpuset_sched_domains_check: find domain cpusets failed. cpuset_sched_domains 15 TFAIL: partition sched domains failed. cpuset_sched_domains 17 TINFO: general group load balance test cpuset_sched_domains 17 TINFO: root group info: cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_sched_domains 17 TINFO: general group info: c
[Kernel-packages] [Bug 1763323] Re: ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Cosmic) 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/1763323 Title: ubuntu_fan_smoke_test failed on 4.4/4.15/4.18 kvm & azure kernel Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Triaged Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: Triaged Status in linux-kvm source package in Xenial: 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: New Bug description: The "enable disable fan test" will fail with Xenial KVM kernel Error message: RTNETLINK answers: Operation not supported /usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 0 local 10.246.72.56 fan-map 250.0.0.0/8:10.246.0.0/16 /usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation RTNETLINK answers: Cannot assign requested address iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory Try `iptables -h' or 'iptables --help' for more information. iptables: Bad rule (does a matching rule exist in that chain?). iptables: Bad rule (does a matching rule exist in that chain?). iptables: No chain/target/match by that name. rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory /usr/sbin/fanatic: unable to bring fan up, unable to configure ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26 ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117 Uname: Linux 4.4.0-1021-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 12 10:22:57 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1763323/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830362] 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 1830362 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/1830362 Title: runpwtests03 from power_management_tests test suite in LTP failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Issue found on Disco with node glameow: startup='Fri May 24 10:57:20 2019' /opt/ltp/testcases/bin/runpwtests03.sh: 29: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found find: ‘/sys/devices/system/cpu/cpu40/cpufreq/’: No such file or directory /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Checking cpu freq sysfs files Power_Management03 1 TPASS: CPUFREQ sysfs tests /opt/ltp/testcases/bin/runpwtests03.sh: 55: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found /opt/ltp/testcases/bin/runpwtests03.sh: 62: /opt/ltp/testcases/bin/runpwtests03.sh: cannot create /sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- performance for cpu40 /opt/ltp/testcases/bin/runpwtests03.sh: 62: /opt/ltp/testcases/bin/runpwtests03.sh: cannot create /sys/devices/system/cpu/cpu40/cpufreq/scaling_governor: Directory nonexistent /opt/ltp/testcases/bin/runpwtests03.sh: FAIL: Unable to set governor -- powersave for cpu40 Power_Management03 2 TFAIL: Changing governors cat: '/sys/devices/system/cpu/cpu*/cpufreq/scaling_available_frequencies': No such file or directory /opt/ltp/testcases/bin/runpwtests03.sh: 83: /opt/ltp/testcases/bin/runpwtests03.sh: total_cpus-=1: not found /opt/ltp/testcases/bin/runpwtests03.sh: PASS: Changing cpu frequencies Power_Management03 3 TPASS: Changing frequncies modprobe: invalid option -- 'l' modprobe: invalid option -- 'l' Power_Management03 4 TPASS: Loading and Unloading of governor kernel modules tag=runpwtests03 stime=1558695440 dur=2 exit=exited stat=1 core=no cu=28 cs=7 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-15-generic 5.0.0-15.16 ProcVersionSignature: User Name 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 21 07:49 seq crw-rw 1 root audio 116, 33 May 21 07:49 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri May 24 11:07:37 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-15-generic N/A linux-backports-modules-5.0.0-15-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1830362/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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: 1829173 phase: Promote to Proposed phase-changed: Friday, 24. May 2019 11:03 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Promote to Proposed phase-changed: Friday, 24. May 2019 11:03 UTC reason: promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829972] Re: Require improved hypervisor detection patch in Ubuntu 18.04
** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) -- 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/1829972 Title: Require improved hypervisor detection patch in Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: This kernel commit is requested to be included into the bionic's 4.15.0 LTS kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=03aa047ef2db4985e444af6ee1c1dd084ad9fb4c s390/early: improve machine detection Right now the early machine detection code check stsi 3.2.2 for "KVM" and set MACHINE_IS_VM if this is different. As the console detection uses diagnose 8 if MACHINE_IS_VM returns true this will crash Linux early for any non z/VM system that sets a different value than KVM. So instead of assuming z/VM, do not set any of MACHINE_IS_LPAR, MACHINE_IS_VM, or MACHINE_IS_KVM. This is required for a dedicated SSC exploiter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1829972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828166] Re: perf top problem on z with Ubuntu 18.04
Changed to Incomplete while waiting for new analysis results. ** Changed in: ubuntu-z-systems Status: In Progress => 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/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Incomplete 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: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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: 1829173 phase: Promote to Proposed phase-changed: Friday, 24. May 2019 11:03 UTC reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed + promote-to-proposed: Pending -- packages copied to Proposed signed:queued -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Promote to Proposed phase-changed: Friday, 24. May 2019 11:03 UTC reason: promote-to-proposed: Pending -- packages copied to Proposed signed:queued To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817097] Re: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices
Modified version e2fsprogs 1.45.1-1ubuntu1 still in eoan-proposed. Once it left proposed this ticket will be changed to Fix Released (e2fsprogs and project). -- 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/1817097 Title: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices Status in lvm2: Confirmed Status in Ubuntu on IBM z Systems: Incomplete Status in e2fsprogs package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Invalid Bug description: Problem Description--- Summary === Environment: IBM Z13 LPAR and z/VM Guest IBM Type: 2964 Model: 701 NC9 OS: Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic s390x) Package: lvm2 version 2.02.176-4.1ubuntu3 LVM: pvmove operation corrupts file system when using 4096 (4k) logical block size and default block size being 512 bytes in the underlying devices The problem is immediately reproducible. We see a real usability issue with data destruction as consequence - which is not acceptable. We expect 'pvmove' to fail with error in such situations to prevent fs destruction, which might possibly be overridden by a force flag. Details === After a 'pvmove' operation is run to move a physical volume onto an ecrypted device with 4096 bytes logical block size we experience a file system corruption. There is no need for the file system to be mounted, but the problem surfaces differently if so. Either, the 'pvs' command after the pvmove shows /dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument or a subsequent mount shows (after umount if the fs had previously been mounted as in our setup) mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mapper/LOOP_VG-LV, missing codepage or helper program, or other error. A minimal setup of LVM using one volume group with one logical volume defined, based on one physical volume is sufficient to raise the problem. One more physical volume of the same size is needed to run the pvmove operation to. LV | VG: LOOP_VG [ ] | PV: /dev/loop0 --> /dev/mapper/enc-loop ( backed by /dev/mapper/enc-loop ) The physical volumes are backed by loopback devices (losetup) to base the problem report on, but we have seen the error on real SCSI multipath volumes also, with and without cryptsetup mapper devices in use. Further discussion == https://www.saout.de/pipermail/dm-crypt/2019-February/006078.html The problem does not occur on block devices with native size of 4k. E.g. DASDs, or file systems with mkfs -b 4096 option. Terminal output === See attached file pvmove-error.txt Debug data == pvmove was run with -dd (maximum debug level) See attached journal file. Contact Information = christian.r...@de.ibm.com ---uname output--- Linux system 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:00:35 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM Type: 2964 Model: 701 NC9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1.) Create two image files of 500MB in size and set up two loopback devices with 'losetup -fP FILE' 2.) Create one physical volume and one volume group 'LOOP_VG', and one logical volume 'VG' Run: pvcreate /dev/loop0 vgcreate LOOP_VG /dev/loop0 lvcreate -L 300MB LOOP_VG -n LV /dev/loop0 3.) Create a file system on the logical volume device: mkfs.ext4 /dev/mapper/LOOP_VG-LV 4.) mount the file system created in the previous step to some empty available directory: mount /dev/mapper/LOOP_VG-LV /mnt 5.) Set up a second physical volume, this time encrypted with LUKS2, and open the volume to make it available: cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1 cryptsetup luksOpen /dev/loop1 enc-loop 6.) Create the second physical volume, and add it to the LOOP_VG pvcreate /dev/mapper/enc-loop vgextend LOOP_VG /dev/mapper/enc-loop 7.) Ensure the new physical volume is part of the volume group: pvs 8.) Move the /dev/loop0 volume onto the encrypted volume with maximum debug option: pvmove -dd /dev/loop0 /dev/mapper/enc-loop 9.) The previous step succeeds, but corrupts the file system on the logical volume We expect an error here. There might be a command line flag to override used because corruption does not cau
[Kernel-packages] [Bug 1828166] Comment bridged from LTC Bugzilla
--- Comment From tmri...@de.ibm.com 2019-05-24 08:19 EDT--- I have debugged this issue and created three patches. Two have been accepted by the perf maintainer and the third is currently under review. Once the patches are upstream I will post the commit id's for further processing by 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/1828166 Title: perf top problem on z with Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Incomplete 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: SRU Justification: == [Impact] * The perf top tool hangs and shows error messages, like 'Not enough memory for annotating' [Fix] * edeb0c90df3581b821a764052d185df985f8b8dc edeb0c9 "perf tools: Stop fallbacking to kallsyms for vdso symbols lookup" [Test Case] * start a benchmark (mem_alloc, but it doesn't really matter what) * execute perf top in a second terminal * the output of perf top is correct * now stop the benchmark * and perf top shows an error message, like "Not enough memory for annotating '__irf_end' symbol!)" * and perf top can't be exited anymore [Regression Potential] * The regression potential can be considered as low since this happens only while using the perf top tool * and it is known that the commit (above) fixes the problem * and the fix is upstream since 4.19 [Other Info] * current disco and eoan kernels don't show that problem * bisecting result points to above commit * applies cleanly on cosmic, but has a little conflict on bionic (both master-next) _ perf top hangs and shows error messages ---uname output--- Linux weather 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:32:27 UTC 2019 s390x s390x s390x GNU/Linux ---Steps to Reproduce--- I start a benchmark (mem_alloc, but it really doesn't matter) and then issue perf top in a second terminal, the output from perf top is correct. Now I stop the benchmark: perf top shows a error message (Not enough memory for annotating '__irf_end' symbol!) and I can't quit from perf top anymore Following analyse took place: No problem with current kernel . Bi-Secting of perf tool took place and following commit was found: commit edeb0c90df3581b821a764052d185df985f8b8dc (HEAD, refs/bisect/bad) Author: Arnaldo Carvalho de Melo Date: Tue Oct 16 17:08:29 2018 -0300 perf tools: Stop fallbacking to kallsyms for vdso symbols lookup When you apply this patch the issue is gone, however it is contained in these versions: git tag --contains edeb0c90df3581b821 v4.19 v4.20 The level I was debugging was kernel 4.15 which does not contain this patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1828166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1825753] Re: fan speed not reported with Ubuntu 18.10 and 19.04
this is correct Jean-Luc Botto 10, chemin des Pringets F-73100 Tresserve, France Mobile: +33 6 74 88 70 91 e-mail: jean-luc.bo...@protonmail.ch https://www.instagram.com/gitedespringets/ https://www.cybevasion.fr//gi16599 https://www.gites.fr//gi16599 http://www.gites-de-france-savoie.com/gite-rural-tresserve-73G300105.html Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ Le vendredi 24 mai 2019 11:28, Kai-Heng Feng a écrit : > So it works on Linux v4.15, but not v4.18 and v5.0? > > > > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1825753 > > Title: > fan speed not reported with Ubuntu 18.10 and 19.04 > > Status in Hardware Sensors Indicator: > Invalid > Status in linux package in Ubuntu: > Incomplete > > Bug description: > after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list > of available sensors > > - > > ProblemType: Bug > ApportVersion: 2.20.10-0ubuntu27 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: jean-luc 1975 F pulseaudio > /dev/snd/controlC1: jean-luc 1975 F pulseaudio > /dev/snd/pcmC1D0p: jean-luc 1975 F...m pulseaudio > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 19.04 > InstallationDate: Installed on 2019-04-21 (8 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) > MachineType: Dell Inc. XPS13 9333 > Package: linux (not installed) > ProcEnviron: > TERM=xterm-256color > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=fr_FR.UTF-8 > SHELL=/bin/bash > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic > root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1 > ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 > RelatedPackageVersions: > linux-restricted-modules-5.0.0-13-generic N/A > linux-backports-modules-5.0.0-13-generic N/A > linux-firmware 1.178 > Tags: disco > Uname: Linux 5.0.0-13-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > dmi.bios.date: 03/27/2015 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A07 > dmi.board.name: 0D13CR > dmi.board.vendor: Dell Inc. > dmi.board.version: A00 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.chassis.version: 0.1 > dmi.modalias: > dmi:bvnDellInc.:bvrA07:bd03/27/2015:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1: > dmi.product.family: Shark Bay System > dmi.product.name: XPS13 9333 > dmi.product.sku: 060A > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/indicator-sensors/+bug/1825753/+subscriptions -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825753 Title: fan speed not reported with Ubuntu 18.10 and 19.04 Status in Hardware Sensors Indicator: Invalid Status in linux package in Ubuntu: Incomplete Bug description: after upgrade with Ubuntu 18.10 or 19.04, fan speed is missing from the list of available sensors --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jean-luc 1975 F pulseaudio /dev/snd/controlC1: jean-luc 1975 F pulseaudio /dev/snd/pcmC1D0p: jean-luc 1975 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-04-21 (8 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS13 9333 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=66b8191e-1372-4898-89fd-16b53712783c ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/27/2015 d
[Kernel-packages] [Bug 1829972] Comment bridged from LTC Bugzilla
--- Comment From kieni...@de.ibm.com 2019-05-24 08:46 EDT--- The test kernel has been successfully verified by the SSC team and the requesting exploiter. From our perspective it is good to go. -- 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/1829972 Title: Require improved hypervisor detection patch in Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: This kernel commit is requested to be included into the bionic's 4.15.0 LTS kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=03aa047ef2db4985e444af6ee1c1dd084ad9fb4c s390/early: improve machine detection Right now the early machine detection code check stsi 3.2.2 for "KVM" and set MACHINE_IS_VM if this is different. As the console detection uses diagnose 8 if MACHINE_IS_VM returns true this will crash Linux early for any non z/VM system that sets a different value than KVM. So instead of assuming z/VM, do not set any of MACHINE_IS_LPAR, MACHINE_IS_VM, or MACHINE_IS_KVM. This is required for a dedicated SSC exploiter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1829972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830370] [NEW] Ubuntu Studio Live CD i915 Driver. System Freeze after a while.
Public bug reported: ubuntu@ubuntu:~$ lshw -c video WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 21 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:118 memory:9000-90ff memory:8000-8fff ioport:f000(size=64) memory:c-d WARNING: output may be incomplete or inaccurate, you should run this program as super-user. ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.0.0-13-lowlatency #14-Ubuntu SMP PREEMPT Mon Apr 15 15:37:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-lowlatency 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1824 F pulseaudio CurrentDesktop: XFCE Date: Fri May 24 12:48:29 2019 MachineType: LENOVO F0BB009ULD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/multibootusb/ubuntustudio-19.04-dvd-amd64/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/multibootusb/ubuntustudio-19.04-dvd-amd64/casper/initrd quiet splash ignore_bootid live-media-path=/multibootusb/ubuntustudio-19.04-dvd-amd64/casper cdrom-detect/try-usb=true floppy.allowed_drive_mask=0 ignore_uuid root=UUID=6C57-02E1 --- RelatedPackageVersions: linux-restricted-modules-5.0.0-13-lowlatency N/A linux-backports-modules-5.0.0-13-lowlatency N/A linux-firmware 1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: O1TKT29AUS dmi.board.name: Aptio CRB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40706 WIN 3274523257661 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO1TKT29AUS:bd01/18/2016:svnLENOVO:pnF0BB009ULD:pvrLenovoC20-00:rvnLENOVO:rnAptioCRB:rvrSDK0J40706WIN3274523257661:cvnLENOVO:ct13:cvrNone: dmi.product.family: Lenovo C20-00 dmi.product.name: F0BB009ULD dmi.product.sku: LENOVO_MT_F0BB_BU_LENOVO_FM_Lenovo C20-00 dmi.product.version: Lenovo C20-00 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug disco ** Summary changed: - Ubuntu Studio Live CD i915 Driver. System Freeze after a wghile. + Ubuntu Studio Live CD i915 Driver. System Freeze after a while. -- 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/1830370 Title: Ubuntu Studio Live CD i915 Driver. System Freeze after a while. Status in linux package in Ubuntu: Confirmed Bug description: ubuntu@ubuntu:~$ lshw -c video WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 21 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:118 memory:9000-90ff memory:8000-8fff ioport:f000(size=64) memory:c-d WARNING: output may be incomplete or inaccurate, you should run this program as super-user. ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.0.0-13-lowlatency #14-Ubuntu SMP PREEMPT Mon Apr 15 15:37:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-lowlatency 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1824 F pulseaudio CurrentDesktop: XFCE Date: Fri May 24 12:48:29 2019 MachineType: LENOVO F0BB009ULD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/multibootusb/ubuntustudio-19.04-dvd-amd64/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/multibootusb/ubuntustudio-19.04-dvd-amd64/casper/initrd
[Kernel-packages] [Bug 1830370] 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/1830370 Title: Ubuntu Studio Live CD i915 Driver. System Freeze after a while. Status in linux package in Ubuntu: Confirmed Bug description: ubuntu@ubuntu:~$ lshw -c video WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 21 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:118 memory:9000-90ff memory:8000-8fff ioport:f000(size=64) memory:c-d WARNING: output may be incomplete or inaccurate, you should run this program as super-user. ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.0.0-13-lowlatency #14-Ubuntu SMP PREEMPT Mon Apr 15 15:37:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-lowlatency 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-lowlatency 5.0.6 Uname: Linux 5.0.0-13-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1824 F pulseaudio CurrentDesktop: XFCE Date: Fri May 24 12:48:29 2019 MachineType: LENOVO F0BB009ULD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/multibootusb/ubuntustudio-19.04-dvd-amd64/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/multibootusb/ubuntustudio-19.04-dvd-amd64/casper/initrd quiet splash ignore_bootid live-media-path=/multibootusb/ubuntustudio-19.04-dvd-amd64/casper cdrom-detect/try-usb=true floppy.allowed_drive_mask=0 ignore_uuid root=UUID=6C57-02E1 --- RelatedPackageVersions: linux-restricted-modules-5.0.0-13-lowlatency N/A linux-backports-modules-5.0.0-13-lowlatency N/A linux-firmware 1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2016 dmi.bios.vendor: LENOVO dmi.bios.version: O1TKT29AUS dmi.board.name: Aptio CRB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40706 WIN 3274523257661 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO1TKT29AUS:bd01/18/2016:svnLENOVO:pnF0BB009ULD:pvrLenovoC20-00:rvnLENOVO:rnAptioCRB:rvrSDK0J40706WIN3274523257661:cvnLENOVO:ct13:cvrNone: dmi.product.family: Lenovo C20-00 dmi.product.name: F0BB009ULD dmi.product.sku: LENOVO_MT_F0BB_BU_LENOVO_FM_Lenovo C20-00 dmi.product.version: Lenovo C20-00 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830175] Re: Add support to Comet Lake LPSS
** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => 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/1830175 Title: Add support to Comet Lake LPSS Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Cosmic: Incomplete Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Incomplete Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] I2C touchpad doesn't work when it's connected to Comet Lake LPSS, which isn't supported. [Fix] Add CML LPSS PCI IDs to intel-lpss module. [Test] The I2C touchpad connected to CML LPSS works after applying the patch. [Regression Potential] None. It's a new device enablement. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1830175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working
** Changed in: ubuntu-z-systems
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1790788
Title:
Customize 'crashkernel' parameter is not properly working
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in makedumpfile package in Ubuntu:
Fix Released
Status in makedumpfile source package in Xenial:
New
Status in makedumpfile source package in Bionic:
Fix Released
Status in makedumpfile source package in Cosmic:
Fix Released
Status in makedumpfile source package in Disco:
Fix Released
Bug description:
SRU Justification:
--
[Impact]
* While installing makedumpfile the "crashkernel=" argument is not
properly set, hence dump is not triggered on reboot.
* Means the triggering of dumpfiles is currently not possible using
makedumpfile.
* Dumpfiles are obviously only needed in rare cases, but if they are
needed (e.g. in production environments) the situation is usually
critical.
* Hence fixing this is needed to allow post-mortem analysis of a
dumps.
* The provided shell code snippet provides a fixed sed statement that
makes sure that the kernel parameter is propoerly set.
[Test Case]
* Create and boot a s390x (KVM virtual) machine
* Install kdump-tools and makedumpfile
Select 'yes' on question 'Should kdump-tools be enabled by default?'
during installation
* [ Reboot system ]
* Look for crashkernel line in zipl boot-loader
grep crashkernel /etc/zipl.conf
crashkernel line is missing in case this bug still exists
one or more lines like this should be given:
parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89
crashkernel=196M
* One may further trigger a crash (for a full positiv test)
sudo -s
sysctl -w kernel.sysrq=1
echo c > /proc/sysrq-trigger
(in case this bug still exists the system will not come up again - check
console in parallel)
Finally dump files should be visible in /var/crash
[Regression Potential]
* The regression potential is very low, since:
* it's limited to the zipl boot loader configuration file only
and this means again it's on the s390x platform only (IBM Z)
* kdump-tools and makedumpfile are not installed by default and only used in
debug situations
hence only system where the package(s) got manually installed get updated
* The function is today broken anyway, hence it can actually only get
better
* I successfully verified this in disco.
_
Trying to use crashdump especially in a KVM machine.
Installation looks fine and the reboot is triggered.
But it does not work because the kernel does not have a 'crashkernel='
parameter.
Nothing in /proc/cmdline:
$ cat /proc/cmdline
root=LABEL=cloudimg-rootfs
Issue seems to be in adding the crashkernel line in this snippet:
# Customize crashkernel= value according to architecture
ARCH="$(arch)"
DEF_PRESET="384M-:128M"
case "$ARCH" in
s390x)
HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
if test -z "$HAS_CRASHKERNEL"; then
sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}"
/etc/zipl.conf
zipl
fi
CIO_IGNORE="$(cio_ignore -u -k)"
sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}"
$INITCONFFILE
;;
esac
(especially 1st sed stmt)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1790788/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776631] Re: [19.04 FEAT] I/O device pre-configuration
** Tags added: installer -- 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/1776631 Title: [19.04 FEAT] I/O device pre-configuration Status in subiquity: Invalid Status in Ubuntu on IBM z Systems: Fix Released Status in debian-installer package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: Fix Released Bug description: I/O device auto-configuration is a mechanism by which users can specify IDs and settings of I/O devices that should be automatically enabled in Linux. Users enter this information for an LPAR via an HMC running in DPM mode. During boot, Linux obtains this information via an SCLP call (details to be defined) and triggers the resulting configuration actions (e.g. using the chzdev command). Available with kernel 4.17 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1776631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829173] Re: linux: 5.0.0-16.17 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** 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 1829171 (bionic/linux-hwe-edge), bug 1829172 (bionic/linux-oem-osp1) derivatives: bug 1829164 (linux-raspi2), bug 1829165 (linux-aws), bug 1829166 (linux-azure), bug 1829168 (linux-gcp), bug 1829169 (linux-kvm), bug 1829170 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 17. May 2019 09:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress 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 in Ubuntu. https://bugs.launchpad.net/bugs/1829173 Title: linux: 5.0.0-16.17 -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: Confirmed 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-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 Disco: 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 1829171 (bionic/linux-hwe-edge), bug 1829172 (bionic/linux-oem-osp1) derivatives: bug 1829164 (linux-raspi2), bug 1829165 (linux-aws), bug 1829166 (linux-azure), bug 1829168 (linux-gcp), bug 1829169 (linux-kvm), bug 1829170 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 17. May 2019 09:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress 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/1829173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829972] Re: Require improved hypervisor detection patch in Ubuntu 18.04
** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- 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/1829972 Title: Require improved hypervisor detection patch in Ubuntu 18.04 Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: This kernel commit is requested to be included into the bionic's 4.15.0 LTS kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=03aa047ef2db4985e444af6ee1c1dd084ad9fb4c s390/early: improve machine detection Right now the early machine detection code check stsi 3.2.2 for "KVM" and set MACHINE_IS_VM if this is different. As the console detection uses diagnose 8 if MACHINE_IS_VM returns true this will crash Linux early for any non z/VM system that sets a different value than KVM. So instead of assuming z/VM, do not set any of MACHINE_IS_LPAR, MACHINE_IS_VM, or MACHINE_IS_KVM. This is required for a dedicated SSC exploiter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1829972/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727290] Re: ubuntu_unionmount_overlayfs_suite failed on 4.15 Azure
This is affecting azure linux-azure cosmic 4.18.0-1019.19. Logs attached. ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags added: azure cosmic ** Attachment added: "client.DEBUG-azure-union" https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1727290/+attachment/5266283/+files/client.DEBUG-azure-union ** Changed in: linux-azure (Ubuntu) Status: New => Confirmed ** Summary changed: - ubuntu_unionmount_overlayfs_suite failed on 4.15 Azure + ubuntu_unionmount_overlayfs_suite failed on Azure -- 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/1727290 Title: ubuntu_unionmount_overlayfs_suite failed on Azure Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Bug description: Kernel 4.15.0-1022.23 azure This test has failed on all the azure instances this cycle, it looks like it has stopped at the "rename-empty-dir" test: TEST rename-file.py:110: Rename file over a dir ./run --rename /mnt/a/foo108/ /mnt/a/empty108/ -E ENOTDIR ./run --rename /mnt/a/foo108/ /mnt/a/dir108/ -E ENOTDIR ./run --open-file /mnt/a/foo108/ -r -R :xxx:yyy:zzz -E ENOTDIR TEST rename-file.py:121: Rename file over parent dir ./run --rename /mnt/a/foo109/ /mnt/a -E ENOTDIR ./run --open-file /mnt/a/foo109/ -r -R :xxx:yyy:zzz -E ENOTDIR *** *** ./run --ov --ts=0 rename-empty-dir *** TEST rename-empty-dir.py:10: Rename empty dir and rename back ./run --rename /mnt/a/empty100 /mnt/a/no_dir100 -E EXDEV /mnt/a/empty100: Expected error (Invalid cross-device link) was not produced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1727290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727290] Re: ubuntu_unionmount_overlayfs_suite failed on Azure
So far the previous comment has cropped up on the following instance types: - Basic_A2 - Standard_B1ms - Standard_D2_v3 - Standard_D2s_v3 - Standard_D16s_v3 - Standard_A2_v2 - Standard_F2s_v2 - Standard_F32s_v2 - Standard_E2s_v3 - Standard_F1s - Standard_D11_v2 - Standard_L4s - Standard_L8s_v2 -- 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/1727290 Title: ubuntu_unionmount_overlayfs_suite failed on Azure Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Bug description: Kernel 4.15.0-1022.23 azure This test has failed on all the azure instances this cycle, it looks like it has stopped at the "rename-empty-dir" test: TEST rename-file.py:110: Rename file over a dir ./run --rename /mnt/a/foo108/ /mnt/a/empty108/ -E ENOTDIR ./run --rename /mnt/a/foo108/ /mnt/a/dir108/ -E ENOTDIR ./run --open-file /mnt/a/foo108/ -r -R :xxx:yyy:zzz -E ENOTDIR TEST rename-file.py:121: Rename file over parent dir ./run --rename /mnt/a/foo109/ /mnt/a -E ENOTDIR ./run --open-file /mnt/a/foo109/ -r -R :xxx:yyy:zzz -E ENOTDIR *** *** ./run --ov --ts=0 rename-empty-dir *** TEST rename-empty-dir.py:10: Rename empty dir and rename back ./run --rename /mnt/a/empty100 /mnt/a/no_dir100 -E EXDEV /mnt/a/empty100: Expected error (Invalid cross-device link) was not produced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1727290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829180] Re: linux-azure: 4.18.0-1019.19 -proposed tracker
Regression Testing: amd64 monotonic_time: (1774959): clock test in monotonic_time will fail on Azure Instances ubuntu_kernel_selftests:(1830016): run_netsocktests from net in ubuntu_kernel_selftests failed with Socket type not supported ubuntu_ltp_syscalls:(1819116): sync_file_range02 in ubuntu_ltp_syscalls fails C/D ubuntu_lxc: (1821152): lxc-test-no-new-privs failed with Temporary failure resolving 'archive.ubuntu.com' ubuntu_unionmount_overlayfs_suite:(1727290) ubuntu_unionmount_overlayfs_suite failed on Azure ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1829180 Title: linux-azure: 4.18.0-1019.19 -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 1829179 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829186 phase: Testing phase-changed: Monday, 20. May 2019 10:35 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/1829180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829180] Re: linux-azure: 4.18.0-1019.19 -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 1829179 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829186 phase: Testing phase-changed: Monday, 20. May 2019 10:35 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/1829180 Title: linux-azure: 4.18.0-1019.19 -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 1829179 (bionic/linux-azure) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829186 phase: Testing phase-changed: Monday, 20. May 2019 10:35 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/1829180/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829173] Re: linux: 5.0.0-16.17 -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 backports: bug 1829171 (bionic/linux-hwe-edge), bug 1829172 (bionic/linux-oem-osp1) derivatives: bug 1829164 (linux-raspi2), bug 1829165 (linux-aws), bug 1829166 (linux-azure), bug 1829168 (linux-gcp), bug 1829169 (linux-kvm), bug 1829170 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Testing - phase-changed: Friday, 17. May 2019 09:31 UTC + phase: Signoff + phase-changed: Friday, 24. May 2019 14:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress 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 in Ubuntu. https://bugs.launchpad.net/bugs/1829173 Title: linux: 5.0.0-16.17 -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: Confirmed 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-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 Disco: 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 1829171 (bionic/linux-hwe-edge), bug 1829172 (bionic/linux-oem-osp1) derivatives: bug 1829164 (linux-raspi2), bug 1829165 (linux-aws), bug 1829166 (linux-azure), bug 1829168 (linux-gcp), bug 1829169 (linux-kvm), bug 1829170 (linux-snapdragon) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Friday, 24. May 2019 14:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812978] Re: rtnetlink.sh in net from ubuntu_kernel_selftests fails
I'm seeing similar , possibly related failures on Bionic linux-aws, 4.15.0-1040.42, I'm going to start consolidating this bug to track these failures on the various clouds. 05/20 17:49:07 DEBUG| utils:0153| [stdout] 05/20 17:49:09 DEBUG| utils:0153| [stdout] test_bpf: ok 05/20 17:49:09 DEBUG| utils:0153| [stdout] ok 1..8 selftests: test_bpf.sh [PASS] 05/20 17:49:09 DEBUG| utils:0153| [stdout] selftests: netdevice.sh 05/20 17:49:09 DEBUG| utils:0153| [stdout] 05/20 17:49:09 DEBUG| utils:0153| [stdout] SKIP: enp4s0: interface already up 05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: enp4s0: ethtool list features 05/20 17:49:09 ERROR| utils:0153| [stderr] Cannot get register dump: Operation not supported 05/20 17:49:09 DEBUG| utils:0153| [stdout] SKIP: enp4s0: ethtool dump not supported 05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: enp4s0: ethtool stats 05/20 17:49:09 DEBUG| utils:0153| [stdout] SKIP: enp4s0: interface kept up 05/20 17:49:09 DEBUG| utils:0153| [stdout] ok 1..9 selftests: netdevice.sh [PASS] 05/20 17:49:09 DEBUG| utils:0153| [stdout] selftests: rtnetlink.sh 05/20 17:49:09 DEBUG| utils:0153| [stdout] 05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: policy routing 05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: route get 05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: tc htb hierarchy 05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: gre tunnel endpoint 05/20 17:49:09 DEBUG| utils:0153| [stdout] PASS: bridge setup 05/20 17:49:11 DEBUG| utils:0153| [stdout] PASS: ipv6 addrlabel 05/20 17:49:11 DEBUG| utils:0153| [stdout] PASS: set ifalias 4488186b-9d9c-473a-89bc-29dba7fd5d44 for test-dummy0 05/20 17:49:11 ERROR| utils:0153| [stderr] RTNETLINK answers: Operation not supported 05/20 17:49:11 DEBUG| utils:0153| [stdout] FAIL: can't add vrf interface, skipping test 05/20 17:49:11 DEBUG| utils:0153| [stdout] PASS: vxlan 05/20 17:49:11 DEBUG| utils:0153| [stdout] FAIL: can't add fou port , skipping test 05/20 17:49:11 ERROR| utils:0153| [stderr] RTNETLINK answers: Operation not supported 05/20 17:49:11 DEBUG| utils:0153| [stdout] FAIL: can't add macsec interface, skipping test 05/20 17:49:11 DEBUG| utils:0153| [stdout] not ok 1..10 selftests: rtnetlink.sh [FAIL] ** Summary changed: - rtnetlink.sh in net from ubuntu_kernel_selftests failed on Cosmic + rtnetlink.sh in net from ubuntu_kernel_selftests fails ** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests 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/1812978 Title: rtnetlink.sh in net from ubuntu_kernel_selftests fails Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Bionic: New Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-aws source package in Cosmic: New Bug description: There are several failures in this test: * ipv6 addrlabel * macsec * ipsec $ sudo ./rtnetlink.sh PASS: policy routing PASS: route get PASS: tc htb hierarchy PASS: gre tunnel endpoint PASS: gretap PASS: ip6gretap PASS: erspan PASS: ip6erspan PASS: bridge setup FAIL: ipv6 addrlabel PASS: set ifalias 485dc5aa-b024-4952-88a7-414355fc2bdc for test-dummy0 PASS: vrf PASS: vxlan FAIL: can't add fou port , skipping test *** stack smashing detected ***: terminated ./rtnetlink.sh: line 468: 5132 Aborted (core dumped) ip macsec show > /dev/null FAIL: macsec ./rtnetlink.sh: line 527: 5146 Terminated ip x m > $tmpfile FAIL: ipsec ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-14-generic 4.18.0-14.15 ProcVersionSignature: User Name 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 09:53 seq crw-rw 1 root audio 116, 33 Jan 23 09:53 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: c
[Kernel-packages] [Bug 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled
Tried this on 19.04 and it still isn't fixed for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694225 Title: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled Status in linux package in Ubuntu: Fix Released Bug description: The disabled touchpad of my Thinkpad T450s sometimes triggers a click lock when I touch it with my palm. This is typical when I'm reaching to click the trackpoint's (red pointing stick) left button. Reproduction steps: 1. Disable the touchpad via Ubuntu's "Mouse & Touchpad" setting. 2. Place and hold two fingers in contact with the touchpad. 3. Click then release the trackpoint's left button once while the cursor is on the desktop area. Then immediately move the cursor with the pointing stick. 4. If the click lock effect gets triggered, a selection would have been made and dragged on the desktop area. If the click lock doesn't happen, repeat step 3. The evtest log on the trackpoint: $evtest /dev/input/event15 Input driver version is 1.0.1 Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0 Input device name: "TPPS/2 IBM TrackPoint" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 273 (BTN_RIGHT) Event code 274 (BTN_MIDDLE) Event type 2 (EV_REL) Event code 0 (REL_X) Event code 1 (REL_Y) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 5 (INPUT_PROP_POINTING_STICK) Testing ... (interrupt to exit) Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047216.720823, -- SYN_REPORT Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 Event: time 1496047216.778898, -- SYN_REPORT Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047220.234518, -- SYN_REPORT If the click lock is not triggered, you would see BTN_LEFT's value 1 & 0: Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0 But if the click lock is triggered, you would only see value 1: Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1 I am guessing "value 0" means release the button. So when click lock is happening, the button left is not released at all, thus it's producing "hold the button" effect. This issue doesn't happen with Windows. I can confirm it happens on Ubuntu v17/v16, Kubuntu, Ubuntu Mate, Xubuntu, Lubuntu, Linux Mint, Fedora, and Open Suse. Also, the issue doesn't occur on older thinkpad models which doesn't use the same clickpad, e.g. T430 or X230. WORKAROUND: Execute at a terminal: sudo rmmod psmouse && sudo modprobe psmouse proto=imps --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 3980 F pulseaudio /dev/snd/controlC0: ubuntu 3980 F pulseaudio CasperVersion: 1.387 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: LENOVO 20BX001LUS Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 Tags: artful Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/16/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET64WW (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX001LUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET64WW(1.28):bd03/16/2017:svnLENOVO:pn20BX001LUS:pvrThinkPadT450s:rvnLENOVO:rn20BX001LUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX001LUS dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694225/+subscriptions -- M
[Kernel-packages] [Bug 1830350] [NEW] System freezes repeatedly for several seconds; wifi driver related errors
You have been subscribed to a public bug: I updated my system about a month ago (Fri 26 April 2019). This was the first update in several weeks and installed fresh versions of a whole truck load of applications including a kernel update. Since this latest bunch of updates the system freezes for a few seconds at regular intervals. Not fatal, but very annoying. Output from "journalctl -f" shows the following errors occurring at the same time as these freezes: May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw scan: -110 Corresponding lines in /var/log/syslog: May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record for fe80::424:c75b:2a2d:52e2 on wlp3s0.*. May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for fe80::424:c75b:2a2d:52e2 on wlp3s0. May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: failed to start hw scan: -110 I do note the interval between the avahi-daemon entry and the subsequent errors related to the wireless network interface, but the former precede the latter consistently in syslog, suggesting they may be related, which is why I'm including it in this report. The freezes last a few seconds. Keyboard input is preserved at this time and typed input appears after the freeze is resolved. Mouse cursor continues to move during freezes but mouse clicks are only processed after the freeze is resolved, i.e. the result of the mouse click is suspended (e.g. buffered) until the system becomes responsive again. For example, clicking on a window during the freeze will focus that window after the freeze has been resolved. The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk: 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Output of lsb_release -rd: Description:Ubuntu 18.04.2 LTS Release:18.04 Output of uname -a: Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux As already said, this is a new issue that has began occurring only after the recent batch of updates that included a kernel update. I reported the bug (maybe in the wrong place) but so far I have received no response. I've lived with this for a month or so hoping that further updates would fix the problem but it still persists. Installing the latest firmware update (14 Mar 2019) has no effect. No other changes were made to either hardware or OS configuration. Logfile snippets attached. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kernel-bug -- System freezes repeatedly for several seconds; wifi driver related errors https://bugs.launchpad.net/bugs/1830350 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 1830350] Re: System freezes repeatedly for several seconds; wifi driver related errors
** Package changed: ubuntu => linux (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/1830350 Title: System freezes repeatedly for several seconds; wifi driver related errors Status in linux package in Ubuntu: New Bug description: I updated my system about a month ago (Fri 26 April 2019). This was the first update in several weeks and installed fresh versions of a whole truck load of applications including a kernel update. Since this latest bunch of updates the system freezes for a few seconds at regular intervals. Not fatal, but very annoying. Output from "journalctl -f" shows the following errors occurring at the same time as these freezes: May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw scan: -110 Corresponding lines in /var/log/syslog: May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record for fe80::424:c75b:2a2d:52e2 on wlp3s0.*. May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for fe80::424:c75b:2a2d:52e2 on wlp3s0. May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: failed to start hw scan: -110 I do note the interval between the avahi-daemon entry and the subsequent errors related to the wireless network interface, but the former precede the latter consistently in syslog, suggesting they may be related, which is why I'm including it in this report. The freezes last a few seconds. Keyboard input is preserved at this time and typed input appears after the freeze is resolved. Mouse cursor continues to move during freezes but mouse clicks are only processed after the freeze is resolved, i.e. the result of the mouse click is suspended (e.g. buffered) until the system becomes responsive again. For example, clicking on a window during the freeze will focus that window after the freeze has been resolved. The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk: 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Output of lsb_release -rd: Description: Ubuntu 18.04.2 LTS Release: 18.04 Output of uname -a: Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux As already said, this is a new issue that has began occurring only after the recent batch of updates that included a kernel update. I reported the bug (maybe in the wrong place) but so far I have received no response. I've lived with this for a month or so hoping that further updates would fix the problem but it still persists. Installing the latest firmware update (14 Mar 2019) has no effect. No other changes were made to either hardware or OS configuration. Logfile snippets attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830396] [NEW] Broadcomm PCE-AC88 wifi drops out - system freezes
Public bug reported: With update 1.173.6 of linux-firmware (bionic-updates) a new firmware file was installed : /lib/firmware/brcm/brcmfmac4366c-pcie.bin Package revision 1.173 does not have the 4366c file (it only has the 4366b file). Under 16.04 the ASUS PCE-AC88 was wrongly loading a 4366b firmware, and did not work out of the box. I followed instructions to retrieve the correct firmware from drivers available on the manufacturer web site, and I was having no issue. I upgraded my system to 18.04.2, and wifi worked very well until the installation of linux-firmware 1.173.6, which came with bionic-updates. After this update, the remotely operated server dropped the wifi connection, requiring a local intervention, and had long freezes making it drop connection and sometimes seem to fail to boot up. In addition syslog was filled with messages: brcmfmac: brcmf_msgbuf_alloc_pktid: dma_map_single failed !! brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !! I also had in kern.log: [191882.330601] brcmfmac :04:00.0: swiotlb buffer is full (sz: 2048 bytes) [191882.330603] brcmfmac :04:00.0: DMA: Out of SW-IOMMU space for 2048 bytes [191882.330605] brcmfmac: brcmf_msgbuf_alloc_pktid: dma_map_single failed !! [191882.330607] brcmfmac: brcmf_msgbuf_rxbuf_data_post: No PKTID available !! Both pointing to potentially serious DMA problems. When I noticed that my firmware had been overwritten, I recovered another one from ASUS support web site, using the same method I had used previously. The system and wifi now seem to work correctly. This computer lacks an IOMMU. The problem might not occur on more modern hardware equipped with a hardware IOMMU. More information on the fairly old system (issue might be also hardware dependent): computer description: Desktop Computer product: P5K-VM (To Be Filled By O.E.M.) vendor: System manufacturer version: System Version serial: [REMOVED] width: 64 bits capabilities: smbios-2.4 dmi-2.4 smp vsyscall32 configuration: boot=normal chassis=desktop family=To Be Filled By O.E.M. sku=To Be Filled By O.E.M. uuid=[REMOVED] *-core description: Motherboard product: P5K-VM vendor: ASUSTeK Computer INC. physical id: 0 version: Rev 1.xx serial: [REMOVED] slot: To Be Filled By O.E.M. *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: 1001 date: 08/07/2008 size: 64KiB capacity: 960KiB capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification *-cpu description: CPU product: Intel(R) Core(TM)2 Quad CPUQ9550 @ 2.83GHz vendor: Intel Corp. physical id: 4 bus info: cpu@0 version: Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz serial: [REMOVED] slot: LGA775 size: 2453MHz capacity: 3800MHz width: 64 bits clock: 382MHz capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority dtherm cpufreq *-cache:0 description: L1 cache physical id: 5 slot: L1-Cache size: 128KiB capacity: 128KiB capabilities: internal write-back data configuration: level=1 *-cache:1 description: L2 cache physical id: 6 slot: L2-Cache size: 12MiB capacity: 12MiB capabilities: internal write-back instruction configuration: level=2 *-memory description: System Memory physical id: 37 slot: System board or motherboard size: 8GiB *-bank:0 description: DIMM DDR2 Synchronous 1872 MHz (0,5 ns) product: PartNum0 vendor: Manufacturer0 physical id: 0 serial: [REMOVED] slot: DIMM0 size: 2GiB width: 64 bits clock: 1872MHz (0.5ns) *-bank:1 description: DIMM DDR2 Synchronous 1872 MHz (0,5 ns) product: PartNum1 vendor: Manufacturer1 physical id: 1 serial: [REMOVED] slot: DIMM1 size: 2GiB width: 64 bits clock: 1872MHz (0.5ns) *-bank:2 description: DIMM DDR2 Synchronous 1872 MHz (0,5
[Kernel-packages] [Bug 1830350] 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 1830350 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830350 Title: System freezes repeatedly for several seconds; wifi driver related errors Status in linux package in Ubuntu: Incomplete Bug description: I updated my system about a month ago (Fri 26 April 2019). This was the first update in several weeks and installed fresh versions of a whole truck load of applications including a kernel update. Since this latest bunch of updates the system freezes for a few seconds at regular intervals. Not fatal, but very annoying. Output from "journalctl -f" shows the following errors occurring at the same time as these freezes: May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: ath10k_pci :03:00.0: failed to start hw scan: -110 Corresponding lines in /var/log/syslog: May 24 10:29:16 dellfvw avahi-daemon[1053]: Registering new address record for fe80::424:c75b:2a2d:52e2 on wlp3s0.*. May 24 10:29:55 dellfvw avahi-daemon[1053]: Withdrawing address record for fe80::424:c75b:2a2d:52e2 on wlp3s0. May 24 10:31:18 dellfvw wpa_supplicant[1078]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-110 May 24 10:31:18 dellfvw kernel: [45569.661175] ath10k_pci :03:00.0: failed to receive scan abortion completion: timed out May 24 10:31:18 dellfvw kernel: [45569.661183] ath10k_pci :03:00.0: failed to stop scan: -110 May 24 10:31:18 dellfvw kernel: [45569.661187] ath10k_pci :03:00.0: failed to start hw scan: -110 I do note the interval between the avahi-daemon entry and the subsequent errors related to the wireless network interface, but the former precede the latter consistently in syslog, suggesting they may be related, which is why I'm including it in this report. The freezes last a few seconds. Keyboard input is preserved at this time and typed input appears after the freeze is resolved. Mouse cursor continues to move during freezes but mouse clicks are only processed after the freeze is resolved, i.e. the result of the mouse click is suspended (e.g. buffered) until the system becomes responsive again. For example, clicking on a window during the freeze will focus that window after the freeze has been resolved. The system is a Dell Inspiron 15 3576. Relevant output of lspci -nnk: 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] (rev 31) Output of lsb_release -rd: Description: Ubuntu 18.04.2 LTS Release: 18.04 Output of uname -a: Linux dellfvw 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux As already said, this is a new issue that has began occurring only after the recent batch of updates that included a kernel update. I reported the bug (maybe in the wrong place) but so far I have received no response. I've lived with this for a month or so hoping that further updates would fix the problem but it still persists. Installing the latest firmware update (14 Mar 2019) has no effect. No other changes were made to either hardware or OS configuration. Logfile snippets attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -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: 1829173 phase: Promote to Proposed phase-changed: Friday, 24. May 2019 11:03 UTC reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed 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-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Promote to Proposed phase-changed: Friday, 24. May 2019 11:03 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829191] Re: linux-oem: 4.15.0-1039.44 -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: 1829219 phase: Promote to Proposed phase-changed: Thursday, 23. May 2019 20:39 UTC reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:retry-needed + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync -- 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/1829191 Title: linux-oem: 4.15.0-1039.44 -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: 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-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: 1829219 phase: Promote to Proposed phase-changed: Thursday, 23. May 2019 20:39 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
Same issue with HP EliteDesk 705 G2 MINI
Turned off all power saving options in BIOS.
Currently running 18.04 HWE EDGE (Linux 5.0.0-15-generic) compiled with:
CONFIG_TIGON3=m
CONFIG_TIGON3_HWMON=y
Tempted to turn off HWMON.
[1.314002] tg3 :01:00.0 eth0: Tigon3 [partno(BCM95762) rev 5762100]
(PCI Express) MAC address c8:d3:ff:a2:96:e9
[1.314915] tg3 :01:00.0 eth0: attached PHY is 5762C (10/100/1000Base-T
Ethernet) (WireSpeed[1], EEE[1])
[1.315781] tg3 :01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0]
TSOcap[1]
[1.316661] tg3 :01:00.0 eth0: dma_rwctrl[0001] dma_mask[64-bit]
[1.324241] tg3 :01:00.0 eno1: renamed from eth0
[6.950429] tg3 :01:00.0 eno1: Link is up at 1000 Mbps, full duplex
[6.950471] tg3 :01:00.0 eno1: Flow control is on for TX and on for RX
[6.950475] tg3 :01:00.0 eno1: EEE is disabled
Has anybody found a stable fix for this 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/1447664
Title:
14e4:1687 broadcom tg3 network driver disconnects under high load
Status in linux package in Ubuntu:
Triaged
Status in linux package in Debian:
New
Bug description:
The tg3 broadcom network driver that binds with chipset 5762 goes offline and
unable to recover (even with tg3 watchdog timeout) when network transmit is
under high load. Call trace:
https://launchpadlibrarian.net/204185480/dmesg
When this happens, only a reboot would be able to fix it. Sometimes,
however, bringing the interface offline and online (via ifconfig)
would recover networking. I've also tested with the latest tg3 driver
(dec 2014 version) and networking is still problematic. I have also
disabled TSO, GSO etc... with ethtool and the bug still surfaces.
This bug may be related to the integrated Firmware.
Here is the procedure to replicate the issue because it is hard to
replicate it under moderate network load.
1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a
Ubuntu/Kubunu Live CD 14.04-15.04.
2. from another machine: start 5 sessions, repetitively copy (scp with public
key authentication) a 70 meg file back and forth to the tg3 machine in each
session. (not sure if this is necessary)
3. create a 1GB file on the tg3 machine, with something like dd
if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
4. from another machine: repetitively scp copy that 1GB file from the tg3
machine. This can be done with something like:
while [ 0 ]; do
scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
done;
Networking will mostly goes offline in about 10-30 minutes.
WORKAROUND: Add udev rule to make the changes permanent in
/etc/udev/rules.d/80-tg3-fix.rules :
ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4",
ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: kubuntu3748 F pulseaudio
/dev/snd/controlC0: kubuntu3748 F pulseaudio
CasperVersion: 1.360
Date: Thu Apr 23 11:16:24 2015
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
ProcEnviron:
LANGUAGE=
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity 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.
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill:
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/22/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L06 v02.15
dmi.board.asset.tag: 2UA5041TG4
dmi.board.name: 2215
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: 2UA5041TG4
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP EliteDesk 705 G1 MT
dmi.sys.ve
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
** Description changed: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. - - Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. - This is a clean cherry pick from mainline of - 8aafaaf2212192012f5bae305bb31cdf7681d777 + Treat exclusion ranges as reserved regions in the iommu-core to fix the + problem. + This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 + 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] - [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain + 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly [Regression Risk] Only affects the amd_iommu driver: - drivers/iommu/amd_iommu* + drivers/iommu/amd_iommu* -- 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/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 3c677d206210f53a4be972211066c0f1cd47fe12 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829191] Re: linux-oem: 4.15.0-1039.44 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 - phase: Promote to Proposed - phase-changed: Thursday, 23. May 2019 20:39 UTC + phase: Testing + phase-changed: Friday, 24. May 2019 18:10 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + 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/1829191 Title: linux-oem: 4.15.0-1039.44 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow 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: 1829219 phase: Testing phase-changed: Friday, 24. May 2019 18:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress 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/1829191/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829168] Re: linux-gcp: 5.0.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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: 1829173 - phase: Promote to Proposed - phase-changed: Friday, 24. May 2019 11:03 UTC + phase: Testing + phase-changed: Friday, 24. May 2019 18:03 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + 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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1829168 Title: linux-gcp: 5.0.0-1007.7 -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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: 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: 1829173 phase: Testing phase-changed: Friday, 24. May 2019 18:03 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757422] Re: Fix Runtime PM for r8169
** No longer affects: linux (Ubuntu) ** Changed in: linux-oem (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1757422 Title: Fix Runtime PM for r8169 Status in HWE Next: New Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Status in linux-oem source package in Bionic: New Bug description: ===SRU Justification=== [Impact] r8169 stays in D0 even when no ethernet cable is plugged in. This drains lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0, 1.8W when r8169 is in D3. The power saved is substantial. [Fix] Improved rumtime PM logic to let the device gets suspended (D3) when the port is not in used and the link is down. [Test Case] The chip version is 8168h/8111h. Test when no ethernet gets plugged. Powertop shows power consumption is roughly 5.5W. lspci shows the device is in D0. With the patch, The power consumption is reduced to 1.8W. lspci shows the device is in D3, PME# is correctly enabled. Plug ethernet cable can corretly wake up the device. Unplug the cable, the device gets suspended to D3 correctly. [Regression Potential] Medium. - r8169 is so ubiquitous, with lots of different chip versions. It's hard to test all of them. - PCI D3 needs system firmware (ACPI) support, this might hit some plaform bugs. - the code is still in v4.16-rc*, so it's not well tested by end users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1757422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
I have not experienced the issue since I started using kernel 4.20.11 .
On Fri., May 24, 2019, 9:54 a.m. Shane R. Spencer,
wrote:
> Same issue with HP EliteDesk 705 G2 MINI
>
> Turned off all power saving options in BIOS.
>
> Currently running 18.04 HWE EDGE (Linux 5.0.0-15-generic) compiled with:
>
> CONFIG_TIGON3=m
> CONFIG_TIGON3_HWMON=y
>
> Tempted to turn off HWMON.
>
> [1.314002] tg3 :01:00.0 eth0: Tigon3 [partno(BCM95762) rev
> 5762100] (PCI Express) MAC address c8:d3:ff:a2:96:e9
> [1.314915] tg3 :01:00.0 eth0: attached PHY is 5762C
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
> [1.315781] tg3 :01:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0]
> ASF[0] TSOcap[1]
> [1.316661] tg3 :01:00.0 eth0: dma_rwctrl[0001] dma_mask[64-bit]
> [1.324241] tg3 :01:00.0 eno1: renamed from eth0
> [6.950429] tg3 :01:00.0 eno1: Link is up at 1000 Mbps, full duplex
> [6.950471] tg3 :01:00.0 eno1: Flow control is on for TX and on for
> RX
> [6.950475] tg3 :01:00.0 eno1: EEE is disabled
>
> Has anybody found a stable fix for this problem?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1447664
>
> Title:
> 14e4:1687 broadcom tg3 network driver disconnects under high load
>
> Status in linux package in Ubuntu:
> Triaged
> Status in linux package in Debian:
> New
>
> Bug description:
> The tg3 broadcom network driver that binds with chipset 5762 goes
> offline and unable to recover (even with tg3 watchdog timeout) when network
> transmit is under high load. Call trace:
> https://launchpadlibrarian.net/204185480/dmesg
>
> When this happens, only a reboot would be able to fix it. Sometimes,
> however, bringing the interface offline and online (via ifconfig)
> would recover networking. I've also tested with the latest tg3 driver
> (dec 2014 version) and networking is still problematic. I have also
> disabled TSO, GSO etc... with ethtool and the bug still surfaces.
> This bug may be related to the integrated Firmware.
>
> Here is the procedure to replicate the issue because it is hard to
> replicate it under moderate network load.
>
> 1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705)
> using a Ubuntu/Kubunu Live CD 14.04-15.04.
> 2. from another machine: start 5 sessions, repetitively copy (scp with
> public key authentication) a 70 meg file back and forth to the tg3 machine
> in each session. (not sure if this is necessary)
> 3. create a 1GB file on the tg3 machine, with something like dd
> if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000))
> 4. from another machine: repetitively scp copy that 1GB file from the
> tg3 machine. This can be done with something like:
>
> while [ 0 ]; do
> scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp
> done;
>
> Networking will mostly goes offline in about 10-30 minutes.
>
> WORKAROUND: Add udev rule to make the changes permanent in
> /etc/udev/rules.d/80-tg3-fix.rules :
> ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4",
> ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off"
>
> ProblemType: Bug
> DistroRelease: Ubuntu 15.04
> Package: linux-image-3.19.0-15-generic 3.19.0-15.15
> ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
> Uname: Linux 3.19.0-15-generic x86_64
> ApportVersion: 2.17.2-0ubuntu1
> Architecture: amd64
> AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1: kubuntu3748 F pulseaudio
>/dev/snd/controlC0: kubuntu3748 F pulseaudio
> CasperVersion: 1.360
> Date: Thu Apr 23 11:16:24 2015
> IwConfig:
>eth0 no wireless extensions.
>
>lono wireless extensions.
> LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
> MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT
> ProcEnviron:
>LANGUAGE=
>TERM=xterm
>PATH=(custom, no user)
>LANG=en_US.UTF-8
>SHELL=/bin/bash
> ProcFB: 0 radeondrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi
> file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity 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.
> RelatedPackageVersions:
>linux-restricted-modules-3.19.0-15-generic N/A
>linux-backports-modules-3.19.0-15-generic N/A
>linux-firmware 1.143
> RfKill:
>
> SourcePackage: linux
> UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 10/22/2014
> dmi.bios.vendor: Hewlett-Packard
> dmi.bios.version: L06 v02.15
> dmi.board.asset.tag: 2UA5041TG4
> dmi.board.name: 2215
> dmi.board.vendor: Hewlett-Packard
> dmi.cha
