[Kernel-packages] [Bug 1842726] Re: Random freezes on 4.15.0-60
I am having this same issue and I do run Docker Compose, but not with any name-servers set explicitly. I just downgraded to 4.15.0-58 to see if that stabilizes things. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842726 Title: Random freezes on 4.15.0-60 Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd: ` Description: Ubuntu 18.04.3 LTS Release: 18.04 ` Hi, I get random freezes on 4.15.0-60. Neither */var/log/kern.log* nor */var/crash* contains anything useful. When it happens it's like it went into a NOP-loop, everything freezes (including mouse pointer) and it reacts to nothing until power cut or reset. I wasn't able to find any steps to reproduce it, it seems fully random. Kernel 4.15.0-58 works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 4.15.0-60.67-generic 4.15.18 Uname: Linux 4.15.0-60-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andi 3522 F pulseaudio /dev/snd/controlC0: andi 3522 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 4 19:36:13 2019 HibernationDevice: RESUME=/dev/mapper/vgad--ssd-swap InstallationDate: Installed on 2018-09-16 (352 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-60-generic root=/dev/mapper/vgad--ssd-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-60-generic N/A linux-backports-modules-4.15.0-60-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO:rvrRev1.xx: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/1842726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823655] Re: Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work
[Expired for linux-raspi2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-raspi2 (Ubuntu) Status: Incomplete => Expired -- 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/1823655 Title: Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work Status in linux-raspi2 package in Ubuntu: Expired Bug description: As suggested in following thread; https://forum.snapcraft.io/t/second-sd-card-on-rpi3-cm3-with-ubuntu- core-18/10465 a bug report. The configuration works for a Ubuntu Core 16 device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1823655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 + bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 variant: debs -- 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -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 verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842606, bug 1842793 - trusty/linux-lts-xenial: bug 1842794, bug 1842607 + trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842608 Title: xenial/linux: 4.4.0-162.190 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842606, bug 1842793 trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!
For anyone who is still having this problem, hopefully this will help you get your webcam working. I was able to get my webcam working and I am using a Dell Precision 7510 Laptop running Ubuntu 18.04.3. 1.) I issued "$dmesg | grep -i camera" in a terminal window and received "uvcvideo 1-11:1.0: Entity type for entity Camera 1 was not initialized!" which landed me here at this website (FYI I am still receiving that message and my camera works... as laurent.pinchart +bugzilla-kernel pointed out already it is a harmless warning). 2) I did a search for "ubuntu uvcvideo" in google and landed on "https://help.ubuntu.com/community/UVC"; which then pointed me to "https://www.berlios.de/software/linux-uvc/#download"; which then pointed me to "http://www.ideasonboard.org/uvc/";. 3) From "http://www.ideasonboard.org/uvc/";, if you scroll down to the bottom of it you will see a Downlaod section. Navigate to the "https://www.linuxtv.org/wiki/index.php/How_to_Obtain"; webpage and follow the "Basic" User's Approach instructions. 4) You may be asked to install pre-requisites during the build process. I had to issue the following command "$sudo apt install libproc- processtable-perl". 5) Once build is complete, run "$sudo make install". 6) I installed uvcdynctrl as floe suggested. I don't know if this helped or not sorry... 7) I then found and example file to test if the camera was working from "https://linuxtv.org/downloads/v4l-dvb-apis/uapi/v4l/v4l2grab.c.html";. I saved this file and tried to compile it "$gcc -o v4l2grab v4l2grab.c" and received an error that it couldn't find the libv4l2.h header file. So i searched for it using $sudo find / -name "libv4l2.h" and didn't find it. This led me to believe that I didn't have the v4l2 development library installed so I installed it $sudo apt install libv4l-dev. 8) I searched again and found it! I then set C include environment path variable to point to the directory containing the header file $export C_INCLUDE_PATH=/usr/include/ and changed #include "../libv4l/include/libv4l2.h" to just #include "libv4l2.h" 9) Tried to recompile and got a linking error, so I issued $gcc -o v4l2grab v4l2grab.c -lv4l1 -lv4l2 and waula, it compiled. Changed its permssions to be executable $chmod +755 v4l2grab (using octal format where 7 in binary is 111 corresponding to rwx for owner and 5 or 110 rw- for group and other) and ran it ./v4l2grab where then I saw the .ppm files in the directory where the executable was ran from, but this was not good enough I want live feed. 10) I then installed v4l-utils and ran $v4l2-ctl -d /dev/video0 --list- formats-ext. This gave me the parameters that are compatible with my webcam for video capture (width=1280, height=720, format=MJPG, and device index=0). 11) As a final death blow I ran the following v4l2-ctl -V --set-fmt-video=width=1280,height=720,pixelformat=MJPG --stream-mmap --stream-count=-1 --stream-to=test.jpg -d /dev/video0 but only got a single image. I think you need to incude OpenCV. Anyways, I hope this helps you atleast get images off of the webcam. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bi
Re: [Kernel-packages] [Bug 1839693] Re: p54usb module in linux-modules-extra-5.0.0-23-generic does not work
If further testing is needed, send me the updated kernel files and I’ll install on my PC and test. On Friday, September 6, 2019, 9:11:39 AM EDT, Ubuntu Kernel Bot wrote: This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1839693 Title: p54usb module in linux-modules-extra-5.0.0-23-generic does not work Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == User report that the p54usb driver will crash when trying to load it on 5.0 kernel for a Dell Wireless 1450 Dual-band (802.11a/b/g) USB 2.0 adapter. This was caused by commit e3554197 (p54: Use skb_peek_tail() instead of direct head pointer accesses.) == Fix == * 1645ab93 (p54: fix crash during initialization) This patch added a check for target_skb to determine where to queue the buffer. It can be cherry-picked into Disco. Eoan got this patch from v5.2.1 upstream stable release update. == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1839693-p54usb/ This issue was reported against Bionic HWE 5.0 kernel, user confirmed that the patched B-hwe kernel can fix this issue. == Regression Potential == Low, change limited to p54usb driver, patch tested with positive test result. == Original Bug Report == I am using the Product: Dell Wireless 1450 Dual-band (802.11a/b/g) USB 2.0 Adapter This relies on the p54usb driver. It works great on kernel 4.18. I upgraded to 5.0.0-3 and the device fails to start. On the older kernel, things seem good: [ 1255.546620] usb 3-1: new high-speed USB device number 3 using xhci_hcd [ 1255.704106] usb 3-1: New USB device found, idVendor=413c, idProduct=8104, bcdDevice=10.50 [ 1255.704110] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1255.704112] usb 3-1: Product: Dell Wireless 1450 Dual-band (802.11a/b/g) USB 2.0 Adapter [ 1255.704115] usb 3-1: Manufacturer: DELL [ 1255.830808] usb 3-1: reset high-speed USB device number 3 using xhci_hcd [ 1255.979753] usb 3-1: Loading firmware file isl3887usb [ 1255.980055] ieee80211 phy1: p54 detected a LM87 firmware [ 1255.980058] p54: rx_mtu reduced from 3240 to 2384 [ 1255.980060] ieee80211 phy1: FW rev 2.13.25.0 - Softmac protocol 5.9 [ 1255.980063] ieee80211 phy1: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES [ 1256.974586] ieee80211 phy1: hwaddr 00:14:a5:c6:56:ca, MAC:isl3892 RF:Xbow [ 1256.976368] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 1256.976974] usb 3-1: is registered as 'phy1' [ 1256.981866] p54usb 3-1:1.0 wlx0014a5c656ca: renamed from wlan0 I'm using: Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839693/+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/1839693 Title: p54usb module in linux-modules-extra-5.0.0-23-generic does not work Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == User report that the p54usb driver will crash when trying to load it on 5.0 kernel for a Dell Wireless 1450 Dual-band (802.11a/b/g) USB 2.0 adapter. This was caused by commit e3554197 (p54: Use skb_peek_tail() instead of direct head pointer accesses.) == Fix == * 1645ab93 (p54: fix crash during initialization) This patch added a check for target_skb to determine where to queue the buffer. It can be cherry-picked into Disco. Eoan got this patch from v5.2.1 upstream stable release update. == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1839693-p54usb/ This issue was reported against Bionic HWE 5.0 kernel, user confirmed that the patched B-hwe kernel can fix this issue. == Regression Potential == Low, change limited to p54usb driver, patch tested with positive test result. == Original Bug Report == I am us
[Kernel-packages] [Bug 1801540]
Following my previous post, disabling the batch flag on both streams (patch 3 from comment 269), Steam is perfect, Discord is lagged again while acquiring. With the second patch from the comment 269, same identical problem without the patch (Discord perfect, Steam crackling for the first minute + audio slightly delayed). However when changing volume there was a little bit of distortion on the output audio (extremely small, but still audible, especially on high volumes), but it seems that using the workaround only on acquisition seems to have removed that small issue. If someone here had the same problem when changing volume, please try patch n.2 and report back. It seems that we can't have both working together simultaneously on my end. The default workaround is still the best option on my system, for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
(In reply to Takashi Iwai from comment #273) > Hmm, would it be only about playback? That is, restricting the workaround > only to capture stream works better? > > --- a/sound/pci/hda/hda_controller.c > +++ b/sound/pci/hda/hda_controller.c > @@ -617,7 +617,8 @@ static int azx_pcm_open(struct snd_pcm_substream > *substream) > * tsched=1 when a capture stream triggers. Until we figure out the > * real cause, disable tsched mode by telling the PCM info flag. > */ > - if (chip->driver_caps & AZX_DCAPS_AMD_WORKAROUND) > + if ((chip->driver_caps & AZX_DCAPS_AMD_WORKAROUND) && > + substream->stream == SNDRV_PCM_STREAM_CAPTURE) > runtime->hw.info |= SNDRV_PCM_INFO_BATCH; > > if (chip->align_buffer_size) > > > In anyway, we need to know this change makes sense at all. IOW, people need > to check whether this causes yet another regression on the devices that have > worked with BATCH workaround. With the standard flags, Discord is perfect, Steam has stutters for the first minute and a bit of delay (500 ms). With the batch flag only on the capture stream, Steam is perfect, Discord has delayed audio. With the batch flag only on the playback stream, same thing with both of them (first case). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: - xenial/linux-oracle: bug 1842724, bug 1842772 + xenial/linux-oracle: bug 1842772, bug 1842724 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842773 Title: bionic/linux-oracle: 4.15.0-1023.26 -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-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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: xenial/linux-oracle: bug 1842772, bug 1842724 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: - trusty/linux-aws: bug 1842793, bug 1842606 - trusty/linux-lts-xenial: bug 1842607, bug 1842794 + trusty/linux-aws: bug 1842606, bug 1842793 + trusty/linux-lts-xenial: bug 1842794, bug 1842607 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842608 Title: xenial/linux: 4.4.0-162.190 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842606, bug 1842793 trusty/linux-lts-xenial: bug 1842794, bug 1842607 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840806] Re: bionic/linux-gcp: 5.0.0-1015.15~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Signoff phase-changed: Monday, 02. September 2019 12:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- stakeholder signoff not verified stakeholder-signoff: Stalled -- waiting for signoff trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs -- 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/1840806 Title: bionic/linux-gcp: 5.0.0-1015.15~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1840805 (gcp-kernel), bug 1840824 (linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1840808 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Signoff phase-changed: Monday, 02. September 2019 12:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Stalled -- waiting for signoff trackers: bionic/linux-gcp-edge: bug 1840824 bionic/linux-gcp/gcp-kernel: bug 1840805 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1840806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 + bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 variant: debs -- 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -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 verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842732] Re: trusty/linux-azure: 4.15.0-1057.62~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842734 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- 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/1842732 Title: trusty/linux-azure: 4.15.0-1057.62~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842734 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842732/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
Hi, i bought Acer Aspire 3, A315-41G, Ryzen 5 2500U in January and since then i had CPU lock up, i manage to install arch but i got CPU lockUP on every second boot, on every other distribution i got CPU lockUP in installer...i never use C6 disable script, but i try all possibile kernel parameters and it never works... Three days ago i found new BIOS patch Update PI code v1.1.0.8. from 2019/08/12, on acer web site, after install everything works, no lockUPs, all distribution i try works with no problems, no need for any grub or kernel parameters... Sry for bad english, Regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Packag
[Kernel-packages] [Bug 1811182] Re: Ubuntu crashed totally. Nothing responded. Could not even shut down.
** Changed in: ubuntu-mate Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811182 Title: Ubuntu crashed totally. Nothing responded. Could not even shut down. Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu MATE 18.10 on AMD 64-bit machine. Working fine until suddenly Ubuntu stops responding to the mouse buttons or keyboard (PS2 keyboard). No warning. Was using VueScan and running two bash scripts using tesseract and VisualWorks. Chrome and Pluma running but not being used. No other symptoms visible. This is the second time in a week that Ubuntu crashed in the same way and I have had to do a hardware reset to restart. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2268 F pulseaudio /dev/snd/controlC0: robert 2268 F pulseaudio CurrentDesktop: MATE Date: Wed Jan 9 22:53:15 2019 InstallationDate: Installed on 2018-12-16 (24 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1811182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831482] Re: VIMC module not available (CONFIG_VIDEO_VIMC not set)
confirmed the 5.0.0-28-generic kernel from proposed works and provides VIMC functionality. Thanks ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == VIMC is a virtual media controller that can emulate a real media device. This is useful for automated tests, and development of multimedia frameworks. == Fix == Enable VIMC as a module in B/D/E kernel configs. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1831482-cfg-vimc/ User has reported that the Eoan kernel works as expected. I have also smoke tested the B/D kernel to make sure the VIMC modules can be loaded properly. == Regression Potential == Low, this patchset enables the VIMC module support, we might see some bug reports against this module in the future. However the acutal impact for a non-vimc user should be minimum. There is a null pointer deference issue was found while inserting the vimc module on some system (lp:1840028), it will be handled in that bug. == Original Bug report == The Multimedia VIMC module provides a test interface for the linux-media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807605] Re: Could not report Linux error
** Changed in: ubuntu-mate Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807605 Title: Could not report Linux error Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Confirmed Bug description: System tried to update and got an error due to the defective superspec package. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3284 F pulseaudio /dev/snd/controlC0: robert 3284 F pulseaudio CurrentDesktop: MATE Date: Sun Dec 9 12:41:11 2018 InstallationDate: Installed on 2018-11-30 (9 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1807605/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807838] Re: Ubuntu crashed totally. Nothing responded. Could not even shut down.
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807838 Title: Ubuntu crashed totally. Nothing responded. Could not even shut down. Status in linux package in Ubuntu: Confirmed Bug description: I was running a bash script which copied directories from a partition on my hard drive (never store data in the Linux partition) to external USB drives. After the script finished, Ubuntu 18.10 crashed. The mouse pointer moved but no window, or menu or keys responded. Could not even get the Menu to open so that I could shut down. Had to power down manually. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3117 F pulseaudio /dev/snd/controlC0: robert 3117 F pulseaudio CurrentDesktop: MATE Date: Tue Dec 11 02:54:28 2018 InstallationDate: Installed on 2018-11-30 (11 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU 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/1807838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
"ip: frags: fix crash in ip_do_fragment()" is in 4.15.0-1057 in proposed right now for a separate issue. -- 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/1822133 Title: Azure Instance never recovered during series of instance reboots. Status in linux-azure package in Ubuntu: Incomplete Bug description: Description: During SRU Testing of various Azure Instances, there will be some cases where the instance will not respond following a system reboot. SRU Testing only restarts a giving instance once, after it preps all of the necessary files to-be-tested. Series: Disco Instance Size: Basic_A3 Region: (Default) US-WEST-2 Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I initiated a series of tests which rebooted Azure Cloud instances 50 times. During the 49th Reboot, an Instance failed to return from a reboot.. Upon grabbing the console output the following was seen scrolling endlessly. I have seen this failure in cases where the instance only restarted a handful of times >5 [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus [84.247704]hyperv_fb: unable to send packet via vmbus In another test attempt I saw the following failure: ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes ERROR ExtHandler /proc/net/route contains no routes Both of these failures broke networking, Both of these failures were seen at least twice to three times, thus may explain why in some cases we never recover from an instance reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- Mailing list: https://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 1833617] Re: [amdgpu] screen freeze after suspend
More recent releases do not work. The very reason I stopped the Kernell updates on my laptop until version 5.0.0.-28 is released which should include the solution to our problem of screen never wakes up from suspend mode. On Friday, September 6, 2019, 9:30:48 AM PDT, Richard Baka wrote: Thanks, this is a patched kernel I think. I need a more recent kernel, could you give me the patch.? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Status in xserver-xorg-video-amdgpu source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in xserver-xorg-video-amdgpu source package in Eoan: Invalid Bug description: === SRU Justification === [Impact] Screen freeze after S3 on AMD Stoney Ridge. [Fix] Pin the VRAM so it won't contain garbage data after S3. [Test] After applying this patch I can confirm the issue is gone on Dell Inspiron 3180, a Stoney Ridge laptop. [Regression Potential] Low. This patch only touched a small subset of amdgpu. === Original Bug Report === It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+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/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Status in xserver-xorg-video-amdgpu source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in xserver-xorg-video-amdgpu source package in Eoan: Invalid Bug description: === SRU Justification === [Impact] Screen freeze after S3 on AMD Stoney Ridge. [Fix] Pin the VRAM so it won't contain garbage data after S3. [Test] After applying this patch I can confirm the issue is gone on Dell Inspiron 3180, a Stoney Ridge laptop. [Regression Potential] Low. This patch only touched a small subset of amdgpu. === Original Bug Report === It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanc
[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
It's possible this same issue is responsible for this crash in WireGuard: https://lists.zx2c4.com/pipermail/wireguard/2019-September/004495.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841730] 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 1841730 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/1841730 Title: kernel error, crush ext4 Status in linux package in Ubuntu: Incomplete Bug description: Use kernel 5.0.0-25. dmesg in attachment belong second system. (first system) After update and reboot system start kernel 5.0.0-25 and after about 2 hours appear tiring and frize, after reboot kernel send error mount home partition, "fsck -f" return error file system. After that i reinstall system and format all partitions. (second system) after reinstall i installed all my applications and updates system, and get error againt, after load kernel 4.18.0-15 errors no appeared. I use gpd pocket 2. thank you for youre work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841730] Re: kernel error, crush ext4
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841730 Title: kernel error, crush ext4 Status in linux package in Ubuntu: Incomplete Bug description: Use kernel 5.0.0-25. dmesg in attachment belong second system. (first system) After update and reboot system start kernel 5.0.0-25 and after about 2 hours appear tiring and frize, after reboot kernel send error mount home partition, "fsck -f" return error file system. After that i reinstall system and format all partitions. (second system) after reinstall i installed all my applications and updates system, and get error againt, after load kernel 4.18.0-15 errors no appeared. I use gpd pocket 2. thank you for youre work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I can confirm too that the BIOS update from ASUS fixed the problem (nerve wrecking moment, though, for a someone new to Linux/Ubuntu). Thanks for the help! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- 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-package
[Kernel-packages] [Bug 1843069] Re: fails to build when CONFIG_COMPACTION=n
** Changed in: linux-kvm (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1843069 Title: fails to build when CONFIG_COMPACTION=n Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Fix Committed Bug description: [Impact] linux-kvm fails to build when CONFIG_COMPACTION=n. [Test case] Use zram driver on our regression tests. [Regression potential] Use of non-initialized memory might cause breakage. Exercising the zram driver should catch any regresions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1843069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842746] Re: bionic/linux: 4.15.0-62.69 -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 -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. September 2019 17:37 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 trackers: bionic/linux-aws: bug 1842718 bionic/linux-bluefield: bug 1842722 bionic/linux-fips: bug 1842728 bionic/linux-gke-4.15: bug 1842720 bionic/linux-ibm-gt: bug 1842723 bionic/linux-kvm: bug 1842721 bionic/linux-oem: bug 1842418 bionic/linux-oracle: bug 1842773 bionic/linux-raspi2: bug 1842711 bionic/linux-snapdragon: bug 1842713 bionic/linux/pc-kernel: bug 1842708 bionic/linux/pc-lowlatency-kernel: bug 1842709 xenial/linux-azure: bug 1842734 xenial/linux-gcp: bug 1842738 xenial/linux-hwe: bug 1842744 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842746 Title: bionic/linux: 4.15.0-62.69 -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 Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. September 2019 17:37 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 trackers: bionic/linux-aws: bug 1842718 bionic/linux-bluefield: bug 1842722 bionic/linux-fips: bug 1842728 bionic/linux-gke-4.15: bug 1842720 bionic/linux-ibm-gt: bug 1842723 bionic/linux-kvm: bug 1842721 bionic/linux-oem: bug 1842418 bionic/linux-oracle: bug 1842773 bionic/linux-raspi2: bug 1842711 bionic/linux-snapdragon: bug 1842713 bionic/linux/pc-kernel: bug 1842708 bionic/linux/pc-lowlatency-kernel: bug 1842709 xenial/linux-azure: bug 1842734 xenial/linux-gcp: bug 1842738 xenial/linux-hwe: bug 1842744 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842819, bug 1842585 + trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- 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/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: - xenial/linux-oracle: bug 1842772, bug 1842724 + xenial/linux-oracle: bug 1842724, bug 1842772 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842773 Title: bionic/linux-oracle: 4.15.0-1023.26 -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-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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: xenial/linux-oracle: bug 1842724, bug 1842772 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time
yah I have actually never seen a bug fixed on the Ubuntu bug tracker, just deal with it upstream or use a different distribution. IMO Ubuntu should delete bugs.launchpad.net and just merge pull requests on github/etc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: - trusty/linux-aws: bug 1842606, bug 1842793 + trusty/linux-aws: bug 1842793, bug 1842606 trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842608 Title: xenial/linux: 4.4.0-162.190 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842793, bug 1842606 trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842561] Re: disco/linux: 5.0.0-28.30 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842561 Title: disco/linux: 5.0.0-28.30 -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: 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: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Friday, 06. September 2019 13:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1842847 bionic/linux-oem-osp1: bug 1842848 disco/linux-aws: bug 1842542 disco/linux-azure: bug 1842546 disco/linux-gcp: bug 1842553 disco/linux-kvm: bug 1842554 disco/linux-oracle: bug 1842556 disco/linux-raspi2: bug 1842540 disco/linux-snapdragon: bug 1842557 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time
This is still broken in Ubuntu 18.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842806] Re: bionic/linux-aws: 4.15.0-1049.51 -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: 1842828 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Ready for Packaging - phase-changed: Friday, 06. September 2019 10:32 UTC + phase: Packaging + phase-changed: Friday, 06. September 2019 19:10 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1842573 trackers: bionic/linux-aws-fips: bug 1842804 bionic/linux-aws/aws-kernel: bug 1842803 xenial/linux-aws-hwe: bug 1842572 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1842806 Title: bionic/linux-aws: 4.15.0-1049.51 -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: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Friday, 06. September 2019 19:10 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1842573 trackers: bionic/linux-aws-fips: bug 1842804 bionic/linux-aws/aws-kernel: bug 1842803 xenial/linux-aws-hwe: bug 1842572 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842806] Re: bionic/linux-aws: 4.15.0-1049.51 -proposed tracker
** Summary changed: - bionic/linux-aws: -proposed tracker + bionic/linux-aws: 4.15.0-1049.51 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1842806 Title: bionic/linux-aws: 4.15.0-1049.51 -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: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Friday, 06. September 2019 19:10 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1842573 trackers: bionic/linux-aws-fips: bug 1842804 bionic/linux-aws/aws-kernel: bug 1842803 xenial/linux-aws-hwe: bug 1842572 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842554] Re: disco/linux-kvm: 5.0.0-1016.17 -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: 1842561 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Promote to Proposed - phase-changed: Friday, 06. September 2019 18:31 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 06. September 2019 19:05 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building + promote-to-proposed: Pending -- ready for review variant: debs -- 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/1842554 Title: disco/linux-kvm: 5.0.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842561 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Promote to Proposed phase-changed: Friday, 06. September 2019 19:05 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
As recommended in answer # 41, reopened because the error persists with [f11] LED on. Greeting kuehhe1 ** Changed in: linux (Ubuntu Bionic) Status: Fix Released => 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/1811254 Title: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LED's in the [f5] Speaker-mute, [f8] Micro-mute and [f11] Wireless on/off Buttons do not show the status. Disturbing is also the LED in [f11] permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 12 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log rfkill_list.txt udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Previous attempts: My on-board search for other HP ProBook Hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
As recommended in answer # 41, reopened because the error persists with [f11] LED on. Greeting kuehhe1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: New Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LED's in the [f5] Speaker-mute, [f8] Micro-mute and [f11] Wireless on/off Buttons do not show the status. Disturbing is also the LED in [f11] permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 12 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log rfkill_list.txt udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Previous attempts: My on-board search for other HP ProBook Hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842810] Re: bionic/linux-kvm: 4.15.0-1045.45 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Packaging - phase-changed: Friday, 06. September 2019 10:32 UTC + phase: Packaging + phase-changed: Friday, 06. September 2019 19:00 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1842577 variant: debs -- 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/1842810 Title: bionic/linux-kvm: 4.15.0-1045.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Friday, 06. September 2019 19:00 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1842577 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842810] Re: bionic/linux-kvm: 4.15.0-1045.45 -proposed tracker
** Summary changed: - bionic/linux-kvm: -proposed tracker + bionic/linux-kvm: 4.15.0-1045.45 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- 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/1842810 Title: bionic/linux-kvm: 4.15.0-1045.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Friday, 06. September 2019 19:00 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1842577 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842718] Re: bionic/linux-aws: 4.15.0-1048.50 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Testing - phase-changed: Thursday, 05. September 2019 22:27 UTC + phase: Signoff + phase-changed: Friday, 06. September 2019 18: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 verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1842716 bionic/linux-aws/aws-kernel: bug 1842715 xenial/linux-aws-hwe: bug 1842717 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1842718 Title: bionic/linux-aws: 4.15.0-1048.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid 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 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Signoff phase-changed: Friday, 06. September 2019 18:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1842716 bionic/linux-aws/aws-kernel: bug 1842715 xenial/linux-aws-hwe: bug 1842717 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842554] Re: disco/linux-kvm: 5.0.0-1016.17 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842561 packages: main: linux-kvm meta: linux-meta-kvm - phase: Packaging - phase-changed: Friday, 06. September 2019 13:04 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 06. September 2019 18:31 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs -- 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/1842554 Title: disco/linux-kvm: 5.0.0-1016.17 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842561 packages: main: linux-kvm meta: linux-meta-kvm phase: Holding before Promote to Proposed phase-changed: Friday, 06. September 2019 18:31 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Packaging - phase-changed: Friday, 06. September 2019 10:30 UTC + phase: Packaging + phase-changed: Friday, 06. September 2019 18:20 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs -- 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/1842590 Title: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Friday, 06. September 2019 18:20 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 trackers: bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842590] Re: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker
** Summary changed: - xenial/linux-gcp: -proposed tracker + xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- 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/1842590 Title: xenial/linux-gcp: 4.15.0-1043.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Friday, 06. September 2019 18:20 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 trackers: bionic/linux-gcp: bug 1842838 bionic/linux-gke-5.0: bug 1842840 xenial/linux-gcp/gcp-kernel: bug 1842588 xenial/linux-gcp/gke-kernel: bug 1842589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842815] Re: bionic/linux-fips: 4.15.0-1016.19 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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: 1842828 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Packaging - phase-changed: Friday, 06. September 2019 10:33 UTC + phase: Packaging + phase-changed: Friday, 06. September 2019 17:55 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1842582 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842815 Title: bionic/linux-fips: 4.15.0-1016.19 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Friday, 06. September 2019 17:55 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 replaces: bug 1842582 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842815] Re: bionic/linux-fips: 4.15.0-1016.19 -proposed tracker
** Summary changed: - bionic/linux-fips: -proposed tracker + bionic/linux-fips: 4.15.0-1016.19 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842815 Title: bionic/linux-fips: 4.15.0-1016.19 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842828 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Friday, 06. September 2019 17:55 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 replaces: bug 1842582 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842734] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842746 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Friday, 06. September 2019 05:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842732 xenial/linux-azure-edge: bug 1842731 xenial/linux-azure/azure-kernel: bug 1842729 variant: debs -- 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/1842734 Title: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed 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 Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Signoff phase-changed: Friday, 06. September 2019 05:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842732 xenial/linux-azure-edge: bug 1842731 xenial/linux-azure/azure-kernel: bug 1842729 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842585, bug 1842819 + trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- 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/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: - xenial/linux-oracle: bug 1842724, bug 1842772 + xenial/linux-oracle: bug 1842772, bug 1842724 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842773 Title: bionic/linux-oracle: 4.15.0-1023.26 -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-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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: xenial/linux-oracle: bug 1842772, bug 1842724 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 + bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 variant: debs -- 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -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 verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 06. September 2019 10:26 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-aws: bug 1842806 bionic/linux-bluefield: bug 1842811 bionic/linux-fips: bug 1842815 bionic/linux-gke-4.15: bug 1842809 bionic/linux-ibm-gt: bug 1842812 bionic/linux-kvm: bug 1842810 bionic/linux-oem: bug 1842802 bionic/linux-oracle: bug 1842814 bionic/linux-raspi2: bug 1842799 bionic/linux-snapdragon: bug 1842801 bionic/linux/pc-kernel: bug 1842796 bionic/linux/pc-lowlatency-kernel: bug 1842797 xenial/linux-azure: bug 1842587 xenial/linux-gcp: bug 1842590 xenial/linux-hwe: bug 1842593 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842828 Title: bionic/linux: 4.15.0-63.72 -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-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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 06. September 2019 10:26 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-aws: bug 1842806 bionic/linux-bluefield: bug 1842811 bionic/linux-fips: bug 1842815 bionic/linux-gke-4.15: bug 1842809 bionic/linux-ibm-gt: bug 1842812 bionic/linux-kvm: bug 1842810 bionic/linux-oem: bug 1842802 bionic/linux-oracle: bug 1842814 bionic/linux-raspi2: bug 1842799 bionic/linux-snapdragon: bug 1842801 bionic/linux/pc-kernel: bug 1842796 bionic/linux/pc-lowlatency-kernel: bug 1842797 xenial/linux-azure: bug 1842587 xenial/linux-gcp: bug 1842590 xenial/linux-hwe: bug 1842593 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
Thanks, this is a patched kernel I think. I need a more recent kernel, could you give me the patch.? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Status in xserver-xorg-video-amdgpu source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in xserver-xorg-video-amdgpu source package in Eoan: Invalid Bug description: === SRU Justification === [Impact] Screen freeze after S3 on AMD Stoney Ridge. [Fix] Pin the VRAM so it won't contain garbage data after S3. [Test] After applying this patch I can confirm the issue is gone on Dell Inspiron 3180, a Stoney Ridge laptop. [Regression Potential] Low. This patch only touched a small subset of amdgpu. === Original Bug Report === It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: - xenial/linux-oracle: bug 1842772, bug 1842724 + xenial/linux-oracle: bug 1842724, bug 1842772 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842773 Title: bionic/linux-oracle: 4.15.0-1023.26 -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-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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: xenial/linux-oracle: bug 1842724, bug 1842772 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842608] Re: xenial/linux: 4.4.0-162.190 -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 -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: - trusty/linux-aws: bug 1842793, bug 1842606 + trusty/linux-aws: bug 1842606, bug 1842793 trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842608 Title: xenial/linux: 4.4.0-162.190 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 04. September 2019 07:52 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed,meta:depwait trackers: trusty/linux-aws: bug 1842606, bug 1842793 trusty/linux-lts-xenial: bug 1842607, bug 1842794 xenial/linux-aws: bug 1842597 xenial/linux-fips: bug 1842605 xenial/linux-kvm: bug 1842598 xenial/linux-raspi2: bug 1842600 xenial/linux-snapdragon: bug 1842603 xenial/linux/pc-kernel: bug 1842595 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843069] [NEW] fails to build when CONFIG_COMPACTION=n
Public bug reported: [Impact] linux-kvm fails to build when CONFIG_COMPACTION=n. [Test case] Use zram driver on our regression tests. [Regression potential] Use of non-initialized memory might cause breakage. Exercising the zram driver should catch any regresions. ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu Disco) Importance: Undecided Assignee: Andrea Righi (arighi) Status: In Progress ** Also affects: linux-kvm (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Disco) Status: New => In Progress ** Changed in: linux-kvm (Ubuntu Disco) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1843069 Title: fails to build when CONFIG_COMPACTION=n Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: In Progress Bug description: [Impact] linux-kvm fails to build when CONFIG_COMPACTION=n. [Test case] Use zram driver on our regression tests. [Regression potential] Use of non-initialized memory might cause breakage. Exercising the zram driver should catch any regresions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1843069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: - xenial/linux-oracle: bug 1842724, bug 1842772 + xenial/linux-oracle: bug 1842772, bug 1842724 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842773 Title: bionic/linux-oracle: 4.15.0-1023.26 -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-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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: xenial/linux-oracle: bug 1842772, bug 1842724 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842773/+subscriptions -- Mailing list: https://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 1833617] Re: [amdgpu] screen freeze after suspend
Richard here is the interim solution provided by Kai-Heng. It worked on my Laptop Index of /~khfeng/lp1833617 | | | | Index of /~khfeng/lp1833617 | | | On Friday, September 6, 2019, 8:01:13 AM PDT, Richard Baka wrote: Hi, I have a very similar problem with kernel 5.3rc7. Wil this be downstream patched then? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1842954 -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Status in xserver-xorg-video-amdgpu source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in xserver-xorg-video-amdgpu source package in Eoan: Invalid Bug description: === SRU Justification === [Impact] Screen freeze after S3 on AMD Stoney Ridge. [Fix] Pin the VRAM so it won't contain garbage data after S3. [Test] After applying this patch I can confirm the issue is gone on Dell Inspiron 3180, a Stoney Ridge laptop. [Regression Potential] Low. This patch only touched a small subset of amdgpu. === Original Bug Report === It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+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/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Status in xserver-xorg-video-amdgpu source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in xserver-xorg-video-amdgpu source package in Eoan: Invalid Bug description: === SRU Justification === [Impact] Screen freeze after S3 on AMD Stoney Ridge. [Fix] Pin the VRAM so it won't contain garbage data after S3. [Test] After applying this patch I can confirm the issue is gone on Dell Inspiron 3180, a Stoney Ridge laptop. [Regression Potential] Low. This patch only touched a small subset of amdgpu. === Original Bug Report === It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical Grap
[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
We updated last night (4.15.0-60) and started having issues this morning... issue has been fixed with update to 5.0.0.27 HWE. We’re up and running again, but trying to figure out where the issue stems from. Is the issue caused from a bug or an attack? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836912] Re: ipv4: enable route flushing in network namespaces
https://lists.ubuntu.com/archives/kernel-team/2019-September/103672.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836912 Title: ipv4: enable route flushing in network namespaces Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification Impact: Tools such as vpnc try to flush routes when run inside network namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This currently does not work because flush is not enabled in non-initial network namespaces. Users have complained about this at various times (cf. Link: https://github.com/lxc/lxd/issues/4257). Fix: Enable /proc/sys/net/ipv4/route/flush inside non-initial network namespaces. Regression Potential: None, since this didn't use to work before. Since routes are per network namespace it is safe to enable /proc/sys/net/ipv4/route/flush in there. Test Case: Tested with LXD on a kernel with the patch applied and by running vpnc successfully. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5cdda5f1d6adde02da591ca2196f20289977dc56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842742] Re: xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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: 1842744 packages: main: linux-deeplens meta: linux-meta-deeplens - phase: Ready for Packaging - phase-changed: Friday, 06. September 2019 02:51 UTC + phase: Packaging + phase-changed: Friday, 06. September 2019 15:20 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1840004 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842742 Title: xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842744 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Friday, 06. September 2019 15:20 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1840004 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842742] Re: xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker
** Summary changed: - xenial/linux-deeplens: -proposed tracker + xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842742 Title: xenial/linux-deeplens: 4.15.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842744 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Packaging phase-changed: Friday, 06. September 2019 15:20 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded replaces: bug 1840004 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837223] Re: shiftfs: add O_DIRECT support
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837223 Title: shiftfs: add O_DIRECT support Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Currently shiftfs does not handle O_DIRECT if the underlay supports it. This is blocking dqlite - an essential part of LXD - from profiting from the performance benefits of O_DIRECT on suitable filesystems when used with async io such as aio or io_uring. Regression Potential: Limited to shiftfs and virtually none since we have not supported this feature before. Test Case: Run LXD with dqlite on a kernel that has support for shiftfs with O_DIRECT. Target Kernels: All LTS kernels with shiftfs support. Patches: https://github.com/brauner/ubuntu-disco/tree/shiftfs_direct_io To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837231] Re: UBUNTU: SAUCE: shiftfs: pass correct point down
** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837231 Title: UBUNTU: SAUCE: shiftfs: pass correct point down Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: shiftfs is currently passing down an unsigned long to copy_from_user() which expects a void __user * pointer. This will cause the compiler to complain because of mismatching types and in general is rather ugly. Regression Potential: Limited to shiftfs. Test Case: Compile kernel with patch and see that compiler does not complain anymore. Target Kernels: All LTS kernels with shiftfs support. Patches: https://github.com/brauner/ubuntu-disco/tree/shiftfs_direct_io To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842819, bug 1842585 + trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- 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/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842773] Re: bionic/linux-oracle: 4.15.0-1023.26 -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: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: - xenial/linux-oracle: bug 1842772, bug 1842724 + xenial/linux-oracle: bug 1842724, bug 1842772 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1842773 Title: bionic/linux-oracle: 4.15.0-1023.26 -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-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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Friday, 06. September 2019 07:00 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 trackers: xenial/linux-oracle: bug 1842724, bug 1842772 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 + bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 variant: debs -- 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -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 verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 06. September 2019 10:26 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-aws: bug 1842806 bionic/linux-bluefield: bug 1842811 bionic/linux-fips: bug 1842815 bionic/linux-gke-4.15: bug 1842809 bionic/linux-ibm-gt: bug 1842812 bionic/linux-kvm: bug 1842810 bionic/linux-oem: bug 1842802 bionic/linux-oracle: bug 1842814 bionic/linux-raspi2: bug 1842799 bionic/linux-snapdragon: bug 1842801 bionic/linux/pc-kernel: bug 1842796 bionic/linux/pc-lowlatency-kernel: bug 1842797 xenial/linux-azure: bug 1842587 xenial/linux-gcp: bug 1842590 xenial/linux-hwe: bug 1842593 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842828 Title: bionic/linux: 4.15.0-63.72 -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-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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 06. September 2019 10:26 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-aws: bug 1842806 bionic/linux-bluefield: bug 1842811 bionic/linux-fips: bug 1842815 bionic/linux-gke-4.15: bug 1842809 bionic/linux-ibm-gt: bug 1842812 bionic/linux-kvm: bug 1842810 bionic/linux-oem: bug 1842802 bionic/linux-oracle: bug 1842814 bionic/linux-raspi2: bug 1842799 bionic/linux-snapdragon: bug 1842801 bionic/linux/pc-kernel: bug 1842796 bionic/linux/pc-lowlatency-kernel: bug 1842797 xenial/linux-azure: bug 1842587 xenial/linux-gcp: bug 1842590 xenial/linux-hwe: bug 1842593 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833617] Re: [amdgpu] screen freeze after suspend
Hi, I have a very similar problem with kernel 5.3rc7. Wil this be downstream patched then? https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1842954 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833617 Title: [amdgpu] screen freeze after suspend Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: New Status in xserver-xorg-video-amdgpu source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in xserver-xorg-video-amdgpu source package in Eoan: Invalid Bug description: === SRU Justification === [Impact] Screen freeze after S3 on AMD Stoney Ridge. [Fix] Pin the VRAM so it won't contain garbage data after S3. [Test] After applying this patch I can confirm the issue is gone on Dell Inspiron 3180, a Stoney Ridge laptop. [Regression Potential] Low. This patch only touched a small subset of amdgpu. === Original Bug Report === It's most likely amdgup driver needs an upgrade. Problem occurs since kernel upgrade to 5.0 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-18.19-generic 5.0.12 Uname: Linux 5.0.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Thu Jun 20 13:46:46 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-06-06 (14 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-18-generic root=UUID=a16bd163-e82f-4ec1-9c5f-c9bd32e225fa ro SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket
Tests are ok for us. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834465 Title: ipv6: fix neighbour resolution with raw socket Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: [SRU Justification] == Impact == IPv6 packets may be dropped during the neighbor resolution when a userspace program uses IPv6 raw sockets. The commit that introduces this bug has not been identified, but it's here at least from Xenial (4.4). This was fixed in the requested backport (from 5.2). == Fix == Backport the requested patches to Disco (5.0), Bionic (4.15) and Xenial (4.4). == Risk of Regregression == The change slightly modifies the target IPv6 address in neighbor resolution engine. Risk should be low and limited to ipv6. --- With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842713] Re: bionic/linux-snapdragon: 4.15.0-1062.69 -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: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: - bionic/linux-snapdragon/dragonboard-kernel: bug 1842712, bug 1839978 + bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 variant: debs -- 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/1842713 Title: bionic/linux-snapdragon: 4.15.0-1062.69 -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 verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842746 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Thursday, 05. September 2019 22:26 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 trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1839978, bug 1842712 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842828] Re: bionic/linux: 4.15.0-63.72 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 06. September 2019 10:26 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:depwait,main:building,meta:failed,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed trackers: bionic/linux-aws: bug 1842806 bionic/linux-bluefield: bug 1842811 bionic/linux-fips: bug 1842815 bionic/linux-gke-4.15: bug 1842809 bionic/linux-ibm-gt: bug 1842812 bionic/linux-kvm: bug 1842810 bionic/linux-oem: bug 1842802 bionic/linux-oracle: bug 1842814 bionic/linux-raspi2: bug 1842799 bionic/linux-snapdragon: bug 1842801 bionic/linux/pc-kernel: bug 1842796 bionic/linux/pc-lowlatency-kernel: bug 1842797 xenial/linux-azure: bug 1842587 xenial/linux-gcp: bug 1842590 xenial/linux-hwe: bug 1842593 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842828 Title: bionic/linux: 4.15.0-63.72 -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-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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Friday, 06. September 2019 10:26 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed trackers: bionic/linux-aws: bug 1842806 bionic/linux-bluefield: bug 1842811 bionic/linux-fips: bug 1842815 bionic/linux-gke-4.15: bug 1842809 bionic/linux-ibm-gt: bug 1842812 bionic/linux-kvm: bug 1842810 bionic/linux-oem: bug 1842802 bionic/linux-oracle: bug 1842814 bionic/linux-raspi2: bug 1842799 bionic/linux-snapdragon: bug 1842801 bionic/linux/pc-kernel: bug 1842796 bionic/linux/pc-lowlatency-kernel: bug 1842797 xenial/linux-azure: bug 1842587 xenial/linux-gcp: bug 1842590 xenial/linux-hwe: bug 1842593 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
Testing has been fixed now, the most recent ddcci-driver-linux tests for s390x passed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842542] Re: disco/linux-aws: 5.0.0-1015.17 -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: 1842561 packages: main: linux-aws meta: linux-meta-aws - phase: Ready for Packaging - phase-changed: Friday, 06. September 2019 05:37 UTC + phase: Packaging + phase-changed: Friday, 06. September 2019 14:00 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-aws-edge: bug 1842830 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1842542 Title: disco/linux-aws: 5.0.0-1015.17 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842561 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Friday, 06. September 2019 14:00 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-aws-edge: bug 1842830 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842542] Re: disco/linux-aws: 5.0.0-1015.17 -proposed tracker
** Summary changed: - disco/linux-aws: -proposed tracker + disco/linux-aws: 5.0.0-1015.17 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati (p-pisati) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1842542 Title: disco/linux-aws: 5.0.0-1015.17 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842561 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Friday, 06. September 2019 14:00 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: bionic/linux-aws-edge: bug 1842830 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842585, bug 1842819 + trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- 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/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842819, bug 1842585 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842447] Re: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose
** Changed in: linux (Ubuntu Bionic) Status: Fix Released => 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/1842447 Title: Kernel Panic with linux-image-4.15.0-60-generic when specifying nameserver in docker-compose Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Some fragmentation+NAT workloads will cause kernel BUG/Ooops. [Test case] sudo iptables -t nat -I POSTROUTING -j MASQUERADE sudo hping3 192.168.122.1 -s 1000 -p 2000 -d 6 [Regression potential] This could make fragmented packets stop flowing. So, make sure fragmented pings still work. ping 192.168.122.1 -s 6 still works, even with the above nat rule. Hello, there are multiple inquries in the mailcow GitHub issues over at https://github.com/mailcow/mailcow-dockerized/issues/2904 that the latest kernel linux-image-4.15.0-60-generic causes kernel panics when "- dns" setting is used within the docker-compose.yml file, for yet some unclear reasons. Multiple users on different systems (e.g. virtualized ones on VMware ESXi and KVM) were able to reproduce the same issue. I was also able to reproduce this constantly on a completely new deployed Ubuntu 18.04 VM (KVM) with a fresh mailcow installation. Steps to reproduce: 1. Install a clean Ubuntu 18.04(.03) machine 2. Upgrade the installation to linux-image-4.15.0-60-generic 3. Setup mailcow as instructed at https://mailcow.github.io/mailcow-dockerized-docs/i_u_m_install/ (just takes less than a minute, easy to reproduce) 4. Start mailcow with "dns"-settings specified in docker-compose file (Make sure using the older docker-compose version with dns settings: https://raw.githubusercontent.com/mailcow/mailcow-dockerized/a1403b7a5969637df23001d05c59c2a20774fbb5/docker-compose.yml) 5. Wait a few minutes, then kernel crash appears Using this workaround it appears to be stable again: https://github.com/mailcow/mailcow- dockerized/commit/dc6eea5142c063e26408a685b66fbb7754408ec2 I've attached the apport file to this bug. Please let me know if you need any kind of further information. (As this is my first bug report here, I hope I have included all required information helping you finding the cause.) Kind regards, Patrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842587] Re: xenial/linux-azure: 4.15.0-1057.62 -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: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - trusty/linux-azure: bug 1842819, bug 1842585 + trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs -- 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/1842587 Title: xenial/linux-azure: 4.15.0-1057.62 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1842828 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Testing phase-changed: Friday, 06. September 2019 05:48 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1842585, bug 1842819 xenial/linux-azure-edge: bug 1842584 xenial/linux-azure/azure-kernel: bug 1842583 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843051] [NEW] please include kernel module CONFIG_NETFILTER_XT_SET
Public bug reported: To use kube-router as part of a kubernetes install, it requires kernel module CONFIG_NETFILTER_XT_SET build it makes use of the 'set' module in iptables. Otherwise, since this kernel module is not built as a module nor included in the kernel itself, iptables complains: root@prod-controller1:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" root@prod-controller1:~# /sbin/iptables -t nat -A POSTROUTING -m set --match-set kube-router-pod-subnets src -m set ! --match-set kube-router-pod-subnets dst -m set ! --match-set kube-router-node-ips dst -j MASQUERADE --wait iptables: No chain/target/match by that name. root@prod-controller1:/boot# grep XT_SET config-$(uname -r) # CONFIG_NETFILTER_XT_SET is not set To fix this situation, I would kindly request that CONFIG_NETFILTER_XT_SET be incldued, at minimum, as a module in the kvm kernel. Thanks, Kube-router code that shows the iptables parameters using the 'set' module: https://github.com/cloudnativelabs/kube-router/blob/00824cd84b862d73dbdf984477178cca9bce9166/pkg/controllers/routing/pod_egress.go#L13 ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1843051 Title: please include kernel module CONFIG_NETFILTER_XT_SET Status in linux-kvm package in Ubuntu: New Bug description: To use kube-router as part of a kubernetes install, it requires kernel module CONFIG_NETFILTER_XT_SET build it makes use of the 'set' module in iptables. Otherwise, since this kernel module is not built as a module nor included in the kernel itself, iptables complains: root@prod-controller1:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS" root@prod-controller1:~# /sbin/iptables -t nat -A POSTROUTING -m set --match-set kube-router-pod-subnets src -m set ! --match-set kube-router-pod-subnets dst -m set ! --match-set kube-router-node-ips dst -j MASQUERADE --wait iptables: No chain/target/match by that name. root@prod-controller1:/boot# grep XT_SET config-$(uname -r) # CONFIG_NETFILTER_XT_SET is not set To fix this situation, I would kindly request that CONFIG_NETFILTER_XT_SET be incldued, at minimum, as a module in the kvm kernel. Thanks, Kube-router code that shows the iptables parameters using the 'set' module: https://github.com/cloudnativelabs/kube-router/blob/00824cd84b862d73dbdf984477178cca9bce9166/pkg/controllers/routing/pod_egress.go#L13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1843051/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842726] Re: Random freezes on 4.15.0-60
I don't have any docker, but I'm also using this machine as a NAT gateway with very high load, and it reliably crash in less than 2 seconds when taking over master role and start handling traffic. Note that I'm using a pretty basic configuration (NAT only, no bridge, no fancy network stuff, …) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842726 Title: Random freezes on 4.15.0-60 Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd: ` Description: Ubuntu 18.04.3 LTS Release: 18.04 ` Hi, I get random freezes on 4.15.0-60. Neither */var/log/kern.log* nor */var/crash* contains anything useful. When it happens it's like it went into a NOP-loop, everything freezes (including mouse pointer) and it reacts to nothing until power cut or reset. I wasn't able to find any steps to reproduce it, it seems fully random. Kernel 4.15.0-58 works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 4.15.0-60.67-generic 4.15.18 Uname: Linux 4.15.0-60-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andi 3522 F pulseaudio /dev/snd/controlC0: andi 3522 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 4 19:36:13 2019 HibernationDevice: RESUME=/dev/mapper/vgad--ssd-swap InstallationDate: Installed on 2018-09-16 (352 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-60-generic root=/dev/mapper/vgad--ssd-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-60-generic N/A linux-backports-modules-4.15.0-60-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO:rvrRev1.xx: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/1842726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1842726] Re: Random freezes on 4.15.0-60
Could be, I currently don't have any docker stuff running but I have lot's of bridges, network namespaces, and NAT going on in some of them. Increasing the load in there seems to increase the likelihood of running into the bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1842726 Title: Random freezes on 4.15.0-60 Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd: ` Description: Ubuntu 18.04.3 LTS Release: 18.04 ` Hi, I get random freezes on 4.15.0-60. Neither */var/log/kern.log* nor */var/crash* contains anything useful. When it happens it's like it went into a NOP-loop, everything freezes (including mouse pointer) and it reacts to nothing until power cut or reset. I wasn't able to find any steps to reproduce it, it seems fully random. Kernel 4.15.0-58 works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-60-generic 4.15.0-60.67 ProcVersionSignature: Ubuntu 4.15.0-60.67-generic 4.15.18 Uname: Linux 4.15.0-60-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andi 3522 F pulseaudio /dev/snd/controlC0: andi 3522 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Sep 4 19:36:13 2019 HibernationDevice: RESUME=/dev/mapper/vgad--ssd-swap InstallationDate: Installed on 2018-09-16 (352 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-60-generic root=/dev/mapper/vgad--ssd-root ro RelatedPackageVersions: linux-restricted-modules-4.15.0-60-generic N/A linux-backports-modules-4.15.0-60-generic N/A linux-firmware 1.173.9 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0601 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0601:bd04/19/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO:rvrRev1.xx: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/1842726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
This seems to be finally fixed by 1.15 firmware on Acer A315 41G. Everything works, can boot without kernel params, suspend and function keys works and powertop is down to ~7W idle (used to be ~14w) with 3+ hours of battery time. GRUB is slow, but it is just a minor annoyance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831482] Re: VIMC module not available (CONFIG_VIDEO_VIMC not set)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831482 Title: VIMC module not available (CONFIG_VIDEO_VIMC not set) Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == VIMC is a virtual media controller that can emulate a real media device. This is useful for automated tests, and development of multimedia frameworks. == Fix == Enable VIMC as a module in B/D/E kernel configs. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1831482-cfg-vimc/ User has reported that the Eoan kernel works as expected. I have also smoke tested the B/D kernel to make sure the VIMC modules can be loaded properly. == Regression Potential == Low, this patchset enables the VIMC module support, we might see some bug reports against this module in the future. However the acutal impact for a non-vimc user should be minimum. There is a null pointer deference issue was found while inserting the vimc module on some system (lp:1840028), it will be handled in that bug. == Original Bug report == The Multimedia VIMC module provides a test interface for the linux-media media controller framework. This is useful for automated tests, and development of multimedia frameworks. Other components similar to this such as VIVID (CONFIG_VIDEO_VIVID=m) are enabled, but VIMC is missing from the linux-modules packages: $ grep VIMC /boot/config-* /boot/config-4.15.0-32-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.17.9-041709-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.4-041804-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-4.18.7-041807-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-13-generic:# CONFIG_VIDEO_VIMC is not set /boot/config-5.0.0-15-generic:# CONFIG_VIDEO_VIMC is not set Could this be enabled in future releases as a module please? I'm running Ubuntu 19.04, with Ubuntu 5.0.0-13.14-generic 5.0.6, however I believe this issue affects all current Ubuntu kernel releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831482/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822870] Re: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3)
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822870 Title: Backport support for software count cache flush Spectre v2 mitigation. (CVE) (required for POWER9 DD2.3) Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Committed Bug description: [IMPACT] Need to further address the Spectre v2 and Meltdown vulnerability in Power with software count cache flush Spectre v2 mitigation support for Power9 DD2.3, and additional Spectre/Meltdown related patches for Power9. [Fix] List of upstream patches identified by IBM in comment #4, #5, and #8. [Test] Pre-req: requires Power9 DD2.3 hardware. A test kernel is available in PPA ppa:ubuntu-power-triage/lp1822870 and the kernel was tested by IBM. Please see comment #11 and #14 for details. [REGRESSION POTENTIAL] The patches are isolated to the ppc64el architecture and does not impact generic code. ppc64el test kernel was tested by IBM and no regressions were reported. [OTHER INFO] For the different kernels: The HWE a563fd9c62f0 UBUNTU: Ubuntu-hwe-4.18.0-17.18~18.04.1 appears to have all patches. Disco appears to be missing only this patch: 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting Cosmic (which is supported until July) is missing a number of patches: cf175dc315f90185128fb061dc05b6fbb211aa2f powerpc/64: Disable the speculation barrier from the command line 6453b532f2c8856a80381e6b9a1f5ea2f12294df powerpc/64: Make stf barrier PPC_BOOK3S_64 specific. 179ab1cbf883575c3a585bcfc0f2160f1d22a149 powerpc/64: Add CONFIG_PPC_BARRIER_NOSPEC af375eefbfb27cbb5b831984e66d724a40d26b5c powerpc/64: Call setup_barrier_nospec() from setup_arch() 406d2b6ae3420f5bb2b3db6986dc6f0b6dbb637b powerpc/64: Make meltdown reporting Book3S 64 specific 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions dc8c6cce9a26a51fc19961accb978217a3ba8c75 powerpc/64s: Add new security feature flags for count cache flush ee13cb249fabdff8b90aaff61add347749280087 powerpc/64s: Add support for software count cache flush ba72dc171954b782a79d25e0f4b3ed91090c3b1e powerpc/pseries: Query hypervisor for count cache flush settings 99d54754d3d5f896a8f616b0b6520662bc99d66b powerpc/powernv: Query firmware for count cache flush settings 7d8bad99ba5a22892f0cad6881289fdc3875a930 powerpc/fsl: Fix spectre_v2 mitigations reporting 92edf8df0ff2ae86cc632eeca0e651fd8431d40d powerpc/security: Fix spectre_v2 reporting This appears to already be in -next. For the bionic 18.04.1 (4.15) kernel only this patch is already part of master-next: a6b3964ad71a61bb7c61d80a60bea7d42187b2eb powerpc/64s: Add barrier_nospec The others are ported, there were only 3 that were not clean. Those are: 2eea7f067f495e33b8b116b35b5988ab2b8aec55 powerpc/64s: Add support for ori barrier_nospec patching This failed because commit a048a07d7f4535baa4cbad6bc024f175317ab938 is missing, but it does not look like that is required here. cb3d6759a93c6d0aea1c10deb6d00e111c29c19c powerpc/64s: Enable barrier_nospec based on firmware settings This failed because debugfs was already included, I can see that previously added, I didn't see where it was previously removed. 06d0bbc6d0f56dacac3a79900e9a9a0d5972d818 powerpc/asm: Add a patch_site macro & helpers for patching instructions This failed because 8183d99f4a22c is not included - but doesn't seem necessary. All other patches applied with, at most, some fuzz. Has had a little testing - boots, check debugfs, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1822870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837223] Re: shiftfs: add O_DIRECT support
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837223 Title: shiftfs: add O_DIRECT support Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: Currently shiftfs does not handle O_DIRECT if the underlay supports it. This is blocking dqlite - an essential part of LXD - from profiting from the performance benefits of O_DIRECT on suitable filesystems when used with async io such as aio or io_uring. Regression Potential: Limited to shiftfs and virtually none since we have not supported this feature before. Test Case: Run LXD with dqlite on a kernel that has support for shiftfs with O_DIRECT. Target Kernels: All LTS kernels with shiftfs support. Patches: https://github.com/brauner/ubuntu-disco/tree/shiftfs_direct_io To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1790595] Re: Line 6 POD HD500 driver fault
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790595 Title: Line 6 POD HD500 driver fault Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: Release: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic uname: Linux GSLM 4.15.0-33-lowlatency #36-Ubuntu SMP PREEMPT Wed Aug 15 17:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux lspci -vnvn https://pastebin.com/7KM9bybk dmesg: usb 1-5: new high-speed USB device number 6 using xhci_hcd [ 44.208541] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 44.208548] usb 1-5: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 44.209063] usb 1-5: New USB device found, idVendor=0e41, idProduct=414d [ 44.209068] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 44.209072] usb 1-5: Product: POD HD500 [ 44.209076] usb 1-5: Manufacturer: Line 6 [ 44.209992] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 found [ 44.210969] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now attached [ 44.211283] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 found [ 44.211289] usb 1-5: selecting invalid altsetting 1 [ 44.211292] snd_usb_podhd 1-5:1.1: set_interface failed [ 44.211304] snd_usb_podhd 1-5:1.1: Line 6 POD HD500 now disconnected [ 44.211317] snd_usb_podhd: probe of 1-5:1.1 failed with error -22 [ 69.605987] nvidia-modeset: Allocated GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 69.606386] nvidia-modeset: Freed GPU:0 (GPU-a23356f9-937a-4843-a3cc-da12769e0681) @ PCI::01:00.0 [ 153.206595] usb 1-5: USB disconnect, device number 6 [ 153.207101] snd_usb_podhd 1-5:1.0: Line 6 POD HD500 now disconnected [ 165.694350] usb 1-1: new high-speed USB device number 7 using xhci_hcd [ 165.842687] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64 [ 165.842693] usb 1-1: config 1 interface 1 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64 [ 165.843146] usb 1-1: New USB device found, idVendor=0e41, idProduct=414d [ 165.843147] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 165.843149] usb 1-1: Product: POD HD500 [ 165.843150] usb 1-1: Manufacturer: Line 6 [ 165.843800] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 found [ 165.844514] snd_usb_podhd 1-1:1.0: Line 6 POD HD500 now attached [ 165.844740] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 found [ 165.844742] usb 1-1: selecting invalid altsetting 1 [ 165.844743] snd_usb_podhd 1-1:1.1: set_interface failed [ 165.844747] snd_usb_podhd 1-1:1.1: Line 6 POD HD500 now disconnected [ 165.844752] snd_usb_podhd: probe of 1-1:1.1 failed with error -22 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-03 (63 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. N501VW NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-lowlatency root=UUID=d7f11886-eed1-4644-ac54-ada42c063889 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-lowlatency N/A linux-backports-modules-4.15.0-33-lowlatency N/A linux-firmware1.173.1 Tags: bionic Uname: Linux 4.15.0-33-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare
[Kernel-packages] [Bug 1826716] Re: Include Sunix serial/parallel driver
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- 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/1826716 Title: Include Sunix serial/parallel driver Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] We shipped several platform with sunix device, which is enabled by sunix DKMS driver. We should use in-tree driver instead. [Fix] Backport in-tree Sunix driver. [Test] Sunix test it on all their devices and they confirmed it works. [Regression Potential] Low. It's a new driver so the regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1826716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834465] Re: ipv6: fix neighbour resolution with raw socket
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834465 Title: ipv6: fix neighbour resolution with raw socket Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Bug description: [SRU Justification] == Impact == IPv6 packets may be dropped during the neighbor resolution when a userspace program uses IPv6 raw sockets. The commit that introduces this bug has not been identified, but it's here at least from Xenial (4.4). This was fixed in the requested backport (from 5.2). == Fix == Backport the requested patches to Disco (5.0), Bionic (4.15) and Xenial (4.4). == Risk of Regregression == The change slightly modifies the target IPv6 address in neighbor resolution engine. Risk should be low and limited to ipv6. --- With an IPv6 raw socket, packets may be dropped during the neighbour resolution. It is fixed upstream by these patches: 9b1c1ef13b35 ipv6: constify rt6_nexthop() 2c6b55f45d53 ipv6: fix neighbour resolution with raw socket https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=9b1c1ef13b35fa35051b635ca9fbda39fe6bbc70 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=2c6b55f45d53420d8310d41310e0e2cd41fe073f The detail of the bug is explained in the second patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836912] Re: ipv4: enable route flushing in network namespaces
See https://lists.ubuntu.com/archives/kernel-team/2019-September/103670.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836912 Title: ipv4: enable route flushing in network namespaces Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification Impact: Tools such as vpnc try to flush routes when run inside network namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This currently does not work because flush is not enabled in non-initial network namespaces. Users have complained about this at various times (cf. Link: https://github.com/lxc/lxd/issues/4257). Fix: Enable /proc/sys/net/ipv4/route/flush inside non-initial network namespaces. Regression Potential: None, since this didn't use to work before. Since routes are per network namespace it is safe to enable /proc/sys/net/ipv4/route/flush in there. Test Case: Tested with LXD on a kernel with the patch applied and by running vpnc successfully. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5cdda5f1d6adde02da591ca2196f20289977dc56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825718] Re: Touchpad not detecting in Linux
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825718 Title: Touchpad not detecting in Linux Status in linux package in Ubuntu: Confirmed Bug description: This issue was observed in laptop -"iBall-Aer3" which has a touch-pad with integrated fingerprint scanner. Both works very well in Windows 10, but not in Linux. Please Check. Any help is highly appreciated. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dipin 1204 F pulseaudio /dev/snd/controlC1: dipin 1204 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 18:12:35 2019 InstallationDate: Installed on 2019-04-21 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: iBall Aer3 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=53642f8a-ea5c-46e8-bde2-b1744102311b ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YZ-BI-13.3-S133AR110-A55H-040-G dmi.board.asset.tag: Default string dmi.board.name: Aer3 dmi.board.vendor: iBall dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 9 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-13.3-S133AR110-A55H-040-G:bd07/26/2017:svniBall:pnAer3:pvrDefaultstring:rvniBall:rnAer3:rvrDefaultstring:cvnDefaultstring:ct9:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Aer3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: iBall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825718/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837231] Re: UBUNTU: SAUCE: shiftfs: pass correct point down
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837231 Title: UBUNTU: SAUCE: shiftfs: pass correct point down Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: shiftfs is currently passing down an unsigned long to copy_from_user() which expects a void __user * pointer. This will cause the compiler to complain because of mismatching types and in general is rather ugly. Regression Potential: Limited to shiftfs. Test Case: Compile kernel with patch and see that compiler does not complain anymore. Target Kernels: All LTS kernels with shiftfs support. Patches: https://github.com/brauner/ubuntu-disco/tree/shiftfs_direct_io To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837231/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841722] Re: [SRU][B/OEM-B/OEM-OSP1/D] UBUNTU: SAUCE: enable middle button for one more ThinkPad
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841722 Title: [SRU][B/OEM-B/OEM-OSP1/D] UBUNTU: SAUCE: enable middle button for one more ThinkPad Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: SRU justification: [Impact] The touchpads of some ThinkPad had a tap middle button. But current 5.2- kernel doesn't support it. [Fix] Add device pnpid to support the middle button on these ThinkPads. [Test] Verified on 2 hardware. Tests result are good. [Regression Potential] low, change is limited to speific hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1841722/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841490] Re: ACPI support for the ARMv8.2 Statistical Profiling Extension
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841490 Title: ACPI support for the ARMv8.2 Statistical Profiling Extension Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] perf support for the ARMv8.2 Statistical Profiling Extension does not work on ACPI platforms. [Test Case] ubuntu@d06-2:~$ sudo perf record -e arm_spe/ts_enable=1,pa_enable=1/ dd if=/dev/zero of=/dev/null count=1 1+0 records in 1+0 records out 512 bytes (5.1 MB, 4.9 MiB) copied, 0.0201586 s, 254 MB/s [ perf record: Woken up 1 times to write data ] [ perf record: Captured and wrote 1.354 MB perf.data ] ubuntu@d06-2:~$ sudo perf report --dump-raw-trace [...] 0 0 0x4a90 [0x30]: PERF_RECORD_AUXTRACE size: 0x155fd0 offset: 0 ref: 0x226974 . . ... ARM SPE data: size 1400784 bytes . : b0 28 31 25 10 00 00 ff c0 PC 0xff1025312 . 0009: 99 07 00 LAT 7 ISSUE . 000c: 98 09 00 LAT 9 TOT . 000f: 52 16 00 EV RETIRED L1D-ACC [...] [Fix] d482e575fbf0f perf: arm_spe: Enable ACPI/Platform automatic module loading d24a0c7099b32 arm_pmu: acpi: spe: Add initial MADT/SPE probing 56855a99f3d0d ACPI/PPTT: Add function to return ACPI 6.3 Identical tokens ed2b664fcc807 ACPI/PPTT: Modify node flag detection to find last IDENTICAL [Regression Risk] The functional changes are all ARM specific (while ACPI PPTT is generic, it is only enabled under arch/arm64 currently). There are new macros and an updated structure in generic code, but all pretty innocuous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841490/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841483] Re: Additional regression in CMA allocation rework
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841483 Title: Additional regression in CMA allocation rework Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: Introduced by the fixes for bug 1823753. Also related - bug 1839395. [Impact] There is an upstream report that the CMA allocation rework we backported to disco is breaking the ath10k wireless driver - and possibly other drivers - in certain configs. It is not clear if Ubuntu users have been impacted by this regression, I just noticed that it has a Fixes: reference in the git commit. [Test Case] Regression tested only. [Fix] 90ae409f9eb3b dma-direct: fix zone selection after an unaddressable CMA allocation [Regression Risk] Regressions in this code generally cause drivers to fail due to unavailable memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839693] Re: p54usb module in linux-modules-extra-5.0.0-23-generic does not work
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1839693 Title: p54usb module in linux-modules-extra-5.0.0-23-generic does not work Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == User report that the p54usb driver will crash when trying to load it on 5.0 kernel for a Dell Wireless 1450 Dual-band (802.11a/b/g) USB 2.0 adapter. This was caused by commit e3554197 (p54: Use skb_peek_tail() instead of direct head pointer accesses.) == Fix == * 1645ab93 (p54: fix crash during initialization) This patch added a check for target_skb to determine where to queue the buffer. It can be cherry-picked into Disco. Eoan got this patch from v5.2.1 upstream stable release update. == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1839693-p54usb/ This issue was reported against Bionic HWE 5.0 kernel, user confirmed that the patched B-hwe kernel can fix this issue. == Regression Potential == Low, change limited to p54usb driver, patch tested with positive test result. == Original Bug Report == I am using the Product: Dell Wireless 1450 Dual-band (802.11a/b/g) USB 2.0 Adapter This relies on the p54usb driver. It works great on kernel 4.18. I upgraded to 5.0.0-3 and the device fails to start. On the older kernel, things seem good: [ 1255.546620] usb 3-1: new high-speed USB device number 3 using xhci_hcd [ 1255.704106] usb 3-1: New USB device found, idVendor=413c, idProduct=8104, bcdDevice=10.50 [ 1255.704110] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1255.704112] usb 3-1: Product: Dell Wireless 1450 Dual-band (802.11a/b/g) USB 2.0 Adapter [ 1255.704115] usb 3-1: Manufacturer: DELL [ 1255.830808] usb 3-1: reset high-speed USB device number 3 using xhci_hcd [ 1255.979753] usb 3-1: Loading firmware file isl3887usb [ 1255.980055] ieee80211 phy1: p54 detected a LM87 firmware [ 1255.980058] p54: rx_mtu reduced from 3240 to 2384 [ 1255.980060] ieee80211 phy1: FW rev 2.13.25.0 - Softmac protocol 5.9 [ 1255.980063] ieee80211 phy1: cryptographic accelerator WEP:YES, TKIP:YES, CCMP:YES [ 1256.974586] ieee80211 phy1: hwaddr 00:14:a5:c6:56:ca, MAC:isl3892 RF:Xbow [ 1256.976368] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [ 1256.976974] usb 3-1: is registered as 'phy1' [ 1256.981866] p54usb 3-1:1.0 wlx0014a5c656ca: renamed from wlan0 I'm using: Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: === SRU Justification === [Impact] Realtek Wifi stops working after the driver changed from rtlwifi to rtw88. [Fix] Sync rtw88 to upstream version, and use MSI on the device. [Test] User confirmed the backport fixes the issue. [Regression Potential] Low. Currently only 8822be uses rtw88. === Original Bug Report === On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840028] Re: NULL pointer dereference when Inserting the VIMC module
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840028 Title: NULL pointer dereference when Inserting the VIMC module Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == When trying to insert a vimc module on a system has other devices being registered in the component framework, if the device is not necessarily a platform_device, nor have a platform_data it will trigger a NULL pointer deference issue. Issue found on a bare metal node with config vimc enabled. ubuntu@amaura:~$ sudo modprobe vimc Killed dmesg output: [ 2855.340272] media: Linux media interface: v0.10 [ 2855.344927] Linux video capture interface: v2.00 [ 2855.346146] BUG: unable to handle kernel NULL pointer dereference at [ 2855.346172] IP: strcmp+0xe/0x30 [ 2855.346181] PGD 0 P4D 0 [ 2855.346189] Oops: [#1] SMP PTI [ 2855.346198] Modules linked in: vimc(+) videodev media ppdev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel binfmt_misc kvm irqbypass intel_cstate intel_rapl_perf ipmi_si joydev ipmi_devintf ipmi_msghandler intel_pch_thermal input_leds parport_pc lpc_ich shpchp parport mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 mgag200 ttm drm_kms_helper aesni_intel syscopyarea aes_x86_64 sysfillrect crypto_simd igb sysimgblt glue_helper fb_sys_fops cryptd dca drm i2c_algo_bit [ 2855.346366] ahci ptp libahci pps_core video [ 2855.346379] CPU: 4 PID: 1505 Comm: modprobe Not tainted 4.15.0-58-generic #64 [ 2855.346395] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [ 2855.346418] RIP: 0010:strcmp+0xe/0x30 [ 2855.346428] RSP: 0018:b63501f93a00 EFLAGS: 00010202 [ 2855.346440] RAX: c0c860f0 RBX: RCX: [ 2855.346456] RDX: a097d85ec440 RSI: c0c8723f RDI: 0001 [ 2855.346473] RBP: b63501f93a00 R08: a097e09270a0 R09: a097d265ca80 [ 2855.346489] R10: e84b51559600 R11: 0200 R12: a097dcdbf718 [ 2855.346505] R13: a097d265ca80 R14: a097d2f2b380 R15: [ 2855.346521] FS: 7fd7f4e4b540() GS:a097e090() knlGS: [ 2855.346539] CS: 0010 DS: ES: CR0: 80050033 [ 2855.346553] CR2: CR3: 0004580fc001 CR4: 003606e0 [ 2855.346569] DR0: DR1: DR2: [ 2855.346585] DR3: DR6: fffe0ff0 DR7: 0400 [ 2855.346601] Call Trace: [ 2855.346611] vimc_comp_compare+0x15/0x20 [vimc] [ 2855.346624] try_to_bring_up_master+0xa3/0x260 [ 2855.346635] ? vimc_remove+0x90/0x90 [vimc] [ 2855.346646] component_master_add_with_match+0x8b/0xd0 [ 2855.346659] vimc_probe+0x325/0x3c9 [vimc] [ 2855.346672] ? acpi_dev_pm_attach+0x25/0xd0 [ 2855.346683] platform_drv_probe+0x3e/0xa0 [ 2855.346693] driver_probe_device+0x30c/0x490 [ 2855.346704] __driver_attach+0xa7/0xf0 [ 2855.346714] ? driver_probe_device+0x490/0x490 [ 2855.346725] bus_for_each_dev+0x70/0xc0 [ 2855.346735] driver_attach+0x1e/0x20 [ 2855.346744] bus_add_driver+0x1c7/0x270 [ 2855.346754] ? 0xc0c8b000 [ 2855.346763] driver_register+0x60/0xe0 [ 2855.346772] ? 0xc0c8b000 [ 2855.346781] __platform_driver_register+0x36/0x40 [ 2855.346793] vimc_init+0x46/0x1000 [vimc] [ 2855.347306] do_one_initcall+0x52/0x19f [ 2855.347810] ? __vunmap+0x8e/0xc0 [ 2855.348322] ? _cond_resched+0x19/0x40 [ 2855.348811] ? kmem_cache_alloc_trace+0x14e/0x1b0 [ 2855.349290] ? do_init_module+0x27/0x209 [ 2855.349768] do_init_module+0x5f/0x209 [ 2855.350
[Kernel-packages] [Bug 1842554] Re: disco/linux-kvm: 5.0.0-1016.17 -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: 1842561 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Packaging - phase-changed: Friday, 06. September 2019 05:38 UTC + phase: Packaging + phase-changed: Friday, 06. September 2019 13:04 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- 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/1842554 Title: disco/linux-kvm: 5.0.0-1016.17 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1842561 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Friday, 06. September 2019 13:04 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1842554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840075] Re: Goodix touchpad may drop first input event
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840075 Title: Goodix touchpad may drop first input event Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Bug description: [Impact] If a touchpad is connected to Intel LPSS PCI device, sometimes the first tap event can be dropped. Goodix touchpad has a rather small buffer so the time its parent devices spend in resuming need to be small. [Fix] Remove Intel LPSS D3cold delay, which is the bottleneck of the situation. [Test] Intel had tested the patch and the result is positive. [Regression Potential] Low. Intel internally tested this so it should be rather safe. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840882] Re: [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses shared power resources
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1840882 Title: [SRU][B-OEM-OSP1/D/E] reduce s2idle power consumption when BIOS uses shared power resources Status in HWE Next: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Bug description: SRU justification: [Impact] When system goes to suspend-to idle, it's power consumption is around 4+ w. [Fix] Some TBT and other ACPI devices share the same power resource, when system goes to s2idle. PME polling thread continue bringing up devices to D0 mode. Use cached ACPI device power state will avoid this issue. [Test] Verified on 2 hardware. Tests result are good. [Regression Potential] Medium, upstream patches cherry-picked. Since these hareware is only supported by 5.0+ kernel, I set B-OEM- OSP1 and disco+ kernel tag. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1840882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840394] Re: Intel HDMI audio print "Unable to sync register" errors
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- 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/1840394 Title: Intel HDMI audio print "Unable to sync register" errors Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Bug description: This fix is in the v5.3-rc3, and EAON already has this patch by backporting stable, so this patch is only for B/D. [Impact] After S3, the intel hdmi audio on a dell laptop print the error like below: [ 2052.030247] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 And the hdmi audio can't work anymore after this. [Fix] For Intel hdmi audio codec, it doesn't need to resume forcibly, because the i915 side probably is not ready to let hdmi codec work, since the intel hdmi audio uses component framework, let i915 control the hdmi codec. [Test Case] Tested on that dell laptops, the hdmi audio doesn't have any issues anymore after applying this patch. [Regression Risk] Low. We tested this patch on a couple of machines (dell and lenovo). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1840394/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840395] Re: reboot will introduce an alarm 'beep ...' during BIOS phase
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-disco -- 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/1840395 Title: reboot will introduce an alarm 'beep ...' during BIOS phase Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-oem source package in Disco: Invalid Status in linux source package in Eoan: Fix Released Status in linux-oem source package in Eoan: Invalid Bug description: Since this fix is still in the maintainer's tree, I add the UBUNTU: SAUCE: prefix in the patch title. And this patchset is fixing a bug in the oem project, so please merge the patchset to OEM-B asap. [Impact] We often hear the Beep noise when a couple of LENOVO laptops reboot, the reproduce rate is about 3/10. [Fix] make the codec enter D3 before rebooting or poweroff, this can fix the issue. [Test Case] Tested on those LENOVO latpops, reboot 50 times, didn't reproduce the noise issue. [Regression Risk] Low. We tested this patch on different lenovo and dell laptops, they all worked well as bfore. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1840395/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp