[Kernel-packages] [Bug 1832685] Re: ACPI BIOS Error (bug)
Please remove "acpi_osi=". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832685 Title: ACPI BIOS Error (bug) Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 18.04.2 Kernel linux-generic-hwe-18.04-edge - 5.0.0-16-generic I keep getting this error and I think is the main cause of my laptop discharging faster than it should. [5.873864] ACPI BIOS Error (bug): Could not resolve [\_SB.PAGD._STA._OSI], AE_NOT_FOUND (20181213/psargs-330) [5.873872] No Local Variables are initialized for Method [_STA] [5.873874] No Arguments are initialized for method [_STA] [5.873875] ACPI Error: Method parse/execution failed \_SB.PAGD._STA, AE_NOT_FOUND (20181213/psparse-531) [5.875511] ACPI BIOS Error (bug): Could not resolve [\_SB.PAGD._STA._OSI], AE_NOT_FOUND (20181213/psargs-330) [5.875518] No Local Variables are initialized for Method [_STA] [5.875520] No Arguments are initialized for method [_STA] [5.875522] ACPI Error: Method parse/execution failed \_SB.PAGD._STA, AE_NOT_FOUND (20181213/psparse-531) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gemini 1461 F pulseaudio CurrentDesktop: Pantheon DistroRelease: elementary OS 5.0 InstallationDate: Installed on 2019-05-25 (18 days ago) InstallationMedia: elementary OS 5.0 "Juno" - Stable amd64 (20181016) MachineType: Notebook N150ZU Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5386f0be-cffb-49a2-b278-4571443ace18 ro quiet splash acpi_osi= vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: juno Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/03/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.04 dmi.board.asset.tag: Tag 12345 dmi.board.name: N150ZU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.04:bd01/03/2019:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150ZU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832239] Re: cosmic kernel (and above) provides two /dev/videoX device but there should be only one video device physically
e.g. checkbox https://bugs.launchpad.net/plainbox-provider- checkbox/+bug/1830146 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832239 Title: cosmic kernel (and above) provides two /dev/videoX device but there should be only one video device physically Status in linux package in Ubuntu: Confirmed Bug description: Since cosmic kernel (4.18) and above, I am aware that there will be two /dev/videoX even there is only one device physically. This issue could be found in many hardware platforms[1] [Steps to Reproduce] 1. Install Ubuntu desktop image (cosmic or above) on one of the platforms[1] 2. Check /dev/video* [Expected Result] There is only /dev/video0 because there is only one video device (the default webcam). [Actual Result] Both of /dev/video0 and /dev/video1 are shown. [1] The platforms have this issue: Dell Vostro 5568 Dell OptiPlex 3011 All In One Dell Computer Corporation XPS 15 9550 Dell Latitude E5570 Dell Vostro 3459 Dell Vostro 3559 Lenovo ThinkCentre Edge 62z All In One - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-21-generic 4.18.0-21.22 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1388 F pulseaudio Date: Mon Jun 10 11:20:43 2019 InstallationDate: Installed on 2018-11-23 (199 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Vostro 5568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=89c301bf-b96d-44b3-890f-71987524c021 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-21-generic N/A linux-backports-modules-4.18.0-21-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd07/18/2016:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 5568 dmi.product.sku: 0786 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833018] Re: After Installing Updates, system fails to boot on first try
Ok, then a kernel bisection is required. What's the latest kernel that works and the first kernel that has this issue? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771206] Re: mouse left click registers as right click
[Expired for linux-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-signed (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1771206 Title: mouse left click registers as right click Status in linux-signed package in Ubuntu: Expired Bug description: Randomly a mouse left click will register as a mouse right click, and then return to normal function. This happens in any application during any activity. This behavior was not present prior to upgrade to 18.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 14 13:43:26 2018 InstallationDate: Installed on 2016-10-24 (566 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-12 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1771206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832624] Re: [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs
** Changed in: ubuntu-z-systems Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832624 Title: [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: New Bug description: Description: kernel: Fix wrong dispatching for control domain CPRBs Symptom: Unable to maintain control-only crypto domains Problem: LPARs may have control-only crypto domains assigned. Such a domain can be controlled (for example master keys can be set) but can't be used for regualar crypto load (usage). A crypto domain may be assigned for control-and-usage to only one active LPAR. But the very same domain may be assigned for control-only to one or more other LPARs. However, trying to communicate in any way with a control-only crypto domain did not work. So a simple query for the state of the master keys on a control-only domain failed and the TKE does not even show this domain. Even worse, when the lowest domain (in a numerically sense) is a control-only domain, the TKE does not even see the crypto cards at all. Solution: This fix introduces some code which checks if an CCA CPRB is addressing a control-only domain. If that's the case and there is a default control-and-usage domain available the CPRB is send to this other domain instead. The target domain field within the CPRB is untouched and the crypto card firmware code detects this working-as-designed mismatch and does the right job and addresses the control domain. Reproduction: 1. Add a control-only domain to the crypto configuration of an LPAR and re-activate the LPAR. 2. Connect the TKE the LPAR and try to visit the master key verification patterns of this control-only domain. 3. Will fail without the fix, will succeed with the fix. Component: kernel Upstream-ID: 7379e652797c0b9b5f6caea1576f2dff9ce6a708 This fix is requested for 19.10 but should also be applied to 18.04 and 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832624/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) Status in lightdm package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (boot timing issues implicated) Status in lightdm package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Invalid Bug description: Okay the has happened recently at least since march 18, 2019 iso and march 22, 2019 iso are both effected very similar to one of my previously reported bugs .. which was related to xorg not being installed .. back ground .. PC is lenovo sl 500 with evo860 SSD drive 3 partions contain installs of disco sda1 -- main working system -- I usually install grub from here as master .. sda6 and sda7 are test installs of disco daily iso's 03-18-2019, 03-22-2019 repectively on the test installs as long as the iso is using the grub boot loader installed from that install the system will boot normally .. the display manger tends to flicker on and off but does final start and login can proceed. but if another install re-installs grub as master the display manager fails to stay active or even come-up for sda6 or sda7 only if their own grubs are reinstalled will they work normally sda1 display manager/xorg login works always no matter which "grub- source" is in control. if I use rescue boot from any grub as master I can get the displays to work by running dpkg fix which does nothing .. and then resuming the boot .. then things work normally.. if the "non-rescue" boots are used the screen/computer locks and only a power down and reboot gives access. (sometime requiring radical depowering .. unpluging and removing battery) now the is a message that appears that RCs??? level is missing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu11 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Mar 25 11:25:58 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller [17aa:20e4] InstallationDate: Installed on 2019-03-23 (1 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322) MachineType: LENOVO 2746CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 2746CTO dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 2746CTO dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832661] Re: Xenial update: 4.4.181 upstream stable release
These 4 patches didn't apply cleanly and needed manual merging. Nothing too hairy though: synchronize sync(2) against cgroup writeback membership switches KVM: x86: Skip EFER vs. guest CPUID checks for host-initiated writes arm64: cpu_ops: fix a leaked reference by adding missing of_node_put crypto: vmx - ghash: do nosimd fallback manually -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832661 Title: Xenial update: 4.4.181 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.181 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832661] Re: Xenial update: 4.4.181 upstream stable release
The following patches were NOT applied since they were applied previously: tools include: Adopt linux/bits.h net: create skb_gso_validate_mac_len() bnx2x: disable GSO where gso_size is too big for hardware -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832661 Title: Xenial update: 4.4.181 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.181 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832661] Re: Xenial update: 4.4.181 upstream stable release
Applied patches: * x86/speculation/mds: Revert CPU buffer clear on double fault exit * x86/speculation/mds: Improve CPU buffer clear documentation * ARM: exynos: Fix a leaked reference by adding missing of_node_put * crypto: vmx - fix copy-paste error in CTR mode * crypto: crct10dif-generic - fix use via crypto_shash_digest() * crypto: x86/crct10dif-pcl - fix use via crypto_shash_digest() * ALSA: usb-audio: Fix a memory leak bug * ALSA: hda/hdmi - Consider eld_valid when reporting jack event * ALSA: hda/realtek - EAPD turn on later * ASoC: max98090: Fix restore of DAPM Muxes * ASoC: RT5677-SPI: Disable 16Bit SPI Transfers * mm/mincore.c: make mincore() more conservative * ocfs2: fix ocfs2 read inode data panic in ocfs2_iget * mfd: da9063: Fix OTP control register names to match datasheets for DA9063/63L * tty/vt: fix write/write race in ioctl(KDSKBSENT) handler * ext4: actually request zeroing of inode table after grow * ext4: fix ext4_show_options for file systems w/o journal * Btrfs: do not start a transaction at iterate_extent_inodes() * bcache: fix a race between cache register and cacheset unregister * bcache: never set KEY_PTRS of journal key to 0 in journal_reclaim() * ipmi:ssif: compare block number correctly for multi-part return messages * crypto: gcm - Fix error return code in crypto_gcm_create_common() * crypto: gcm - fix incompatibility between "gcm" and "gcm_base" * crypto: chacha20poly1305 - set cra_name correctly * crypto: salsa20 - don't access already-freed walk.iv * crypto: arm/aes-neonbs - don't access already-freed walk.iv * writeback: synchronize sync(2) against cgroup writeback membership switches * fs/writeback.c: use rcu_barrier() to wait for inflight wb switches going into workqueue when umount * ext4: zero out the unused memory region in the extent tree block * ALSA: hda/realtek - Fix for Lenovo B50-70 inverted internal microphone bug * KVM: x86: Skip EFER vs. guest CPUID checks for host-initiated writes * net: avoid weird emergency message * net/mlx4_core: Change the error print to info print * ppp: deflate: Fix possible crash in deflate_init * tipc: switch order of device registration to fix a crash * tipc: fix modprobe tipc failed after switch order of device registration * stm class: Fix channel free in stm output free path * md: add mddev->pers to avoid potential NULL pointer dereference * intel_th: msu: Fix single mode with IOMMU * of: fix clang -Wunsequenced for be32_to_cpu() * cifs: fix strcat buffer overflow and reduce raciness in smb21_set_oplock_level() * media: ov6650: Fix sensor possibly not detected on probe * NFS4: Fix v4.0 client state corruption when mount * clk: tegra: Fix PLLM programming on Tegra124+ when PMC overrides divider * fuse: fix writepages on 32bit * fuse: honor RLIMIT_FSIZE in fuse_file_fallocate * iommu/tegra-smmu: Fix invalid ASID bits on Tegra30/114 * ceph: flush dirty inodes before proceeding with remount * tracing: Fix partial reading of trace event's id file * memory: tegra: Fix integer overflow on tick value calculation * perf intel-pt: Fix instructions sampling rate * perf intel-pt: Fix improved sample timestamp * perf intel-pt: Fix sample timestamp wrt non-taken branches * fbdev: sm712fb: fix brightness control on reboot, don't set SR30 * fbdev: sm712fb: fix VRAM detection, don't set SR70/71/74/75 * fbdev: sm712fb: fix white screen of death on reboot, don't set CR3B-CR3F * fbdev: sm712fb: fix boot screen glitch when sm712fb replaces VGA * fbdev: sm712fb: fix crashes during framebuffer writes by correctly mapping VRAM * fbdev: sm712fb: fix support for 1024x768-16 mode * fbdev: sm712fb: use 1024x768 by default on non-MIPS, fix garbled display * fbdev: sm712fb: fix crashes and garbled display during DPMS modesetting * PCI: Mark Atheros AR9462 to avoid bus reset * dm delay: fix a crash when invalid device is specified * xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink * xfrm6_tunnel: Fix potential panic when unloading xfrm6_tunnel module * vti4: ipip tunnel deregistration fixes. * xfrm4: Fix uninitialized memory read in _decode_session4 * KVM: arm/arm64: Ensure vcpu target is unset on reset failure * power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG * ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour * perf bench numa: Add define for RUSAGE_THREAD if not present * Revert "Don't jump to compute_result state from check_result state" * md/raid: raid5 preserve the writeback action after the parity check * btrfs: Honour FITRIM range constraints during free space trim * fbdev: sm712fb: fix memory frequency by avoiding a switch/case fallthrough * ext4: do not delete unlinked inode from orphan list on failed truncate * KVM: x86: fix return value for reserved EFER * bio: fix improper use of smp_mb__before_atomic() * Revert "scsi: sd: Keep disk read-only when re-reading partition" * crypto: vmx - CTR: always increment IV as quadword * gfs2: Fix sign extension bug in gfs2_update_stats
[Kernel-packages] [Bug 1832472] Re: cdc_ncm floods syslog unneccessarily
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832472 Title: cdc_ncm floods syslog unneccessarily Status in linux package in Ubuntu: Confirmed Bug description: Upon plugging in a USB adapter for NBase-T ethernet with an Realtek chip RTL8156 the kernel module cdc_ncm starts flooding /var/log/syslog with unneccessary status info. The status lines either say that there's no ethernet link or show the interface as connected and state the link speed. The relevant parts from /var/log/syslog after attaching the adapter without ethernet link read like this: [...] Jun 12 10:48:58 resdz-v13 kernel: [ 4240.398485] usb 2-3: new SuperSpeed Gen 1 USB device number 5 using xhci_hcd Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419463] usb 2-3: New USB device found, idVendor=0bda, idProduct=8156, bcdDevice=30.00 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419469] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419472] usb 2-3: Product: USB 10/100/1G/2.5G LAN Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419475] usb 2-3: Manufacturer: Realtek Jun 12 10:48:58 resdz-v13 kernel: [ 4240.419477] usb 2-3: SerialNumber: 1 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447769] cdc_ncm 2-3:2.0: MAC-Address: 00:13:3b:68:00:e9 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447775] cdc_ncm 2-3:2.0: setting rx_max = 16384 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.447929] cdc_ncm 2-3:2.0: setting tx_max = 16384 Jun 12 10:48:58 resdz-v13 kernel: [ 4240.448901] cdc_ncm 2-3:2.0 usb0: register 'cdc_ncm' at usb-:00:14.0-3, CDC NCM, 00:13:3b:68:00:e9 Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.1872] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/8) Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:14.0/usb2/2-3" Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Using default interface naming scheme 'v240'. Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Jun 12 10:48:58 resdz-v13 kernel: [ 4240.466476] cdc_ncm 2-3:2.0 enx00133b6800e9: renamed from usb0 Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.2315] device (usb0): interface index 7 renamed iface from 'usb0' to 'enx00133b6800e9' Jun 12 10:48:58 resdz-v13 systemd-udevd[4299]: Process 'vlan-network-interface UDEV' failed with exit code 1. Jun 12 10:48:58 resdz-v13 NetworkManager[916]: [1560329338.2431] device (enx00133b6800e9): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Jun 12 10:48:58 resdz-v13 charon: 12[KNL] interface enx00133b6800e9 activated Jun 12 10:48:58 resdz-v13 mtp-probe: checking bus 2, device 5: "/sys/devices/pci:00/:00:14.0/usb2/2-3" Jun 12 10:48:58 resdz-v13 mtp-probe: bus: 2, device: 5 was not an MTP device Jun 12 10:48:58 resdz-v13 kernel: [ 4240.524052] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.556109] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.588054] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.620383] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected Jun 12 10:48:58 resdz-v13 kernel: [ 4240.652415] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: disconnected [...] Upon plugging in the ethernet cable I see [...] Jun 12 10:49:01 resdz-v13 kernel: [ 4243.372273] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink Jun 12 10:49:01 resdz-v13 kernel: [ 4243.404278] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected [...] and Network Manager starts its work. After the interface is up the flooding continues: [...] Jun 12 10:49:01 resdz-v13 kernel: [ 4243.564056] cdc_ncm 2-3:2.0 enx00133b6800e9: 1000 mbit/s downlink 1000 mbit/s uplink Jun 12 10:49:01 resdz-v13 kernel: [ 4243.596051] cdc_ncm 2-3:2.0 enx00133b6800e9: network connection: connected Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/4 Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/4 Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/4 Jun 12 10:49:01 resdz-v13 whoopsie[1530]: [10:49:01] online Jun 12 10:49:01 resdz-v13 kernel: [ 4243.628055]
[Kernel-packages] [Bug 1832087] Re: Bluetooth not work on INTEL WIRELESS-AC 9260
Hmm, please attach dmesg under Linux 5.2. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832087 Title: Bluetooth not work on INTEL WIRELESS-AC 9260 Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.0.0-16 > Bluetooth on INTEL WIRELESS-AC 9260 NOT WORK !!?? I can not use my mouse, my keyboard and external speakers that all need bluetooth. My laptop has few usb ports, I am dependent on bluetooth with him... Unsolved problem from Kernel 5.0.0-15 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829497 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philippe 1646 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2018-11-13 (206 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=1c90898a-7750-4a75-967f-b653a0db22aa ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-16.17~18.04.1-generic 5.0.8 RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.173.6 Tags: tessa Uname: Linux 5.0.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0D0T05 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832087/+subscriptions -- Mailing list: https://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 1833018] Re: After Installing Updates, system fails to boot on first try
On 6/17/19 8:50 PM, Kai-Heng Feng wrote: > This is a quite good reference on how you do it: > https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter > Okay, that information was helpful. I'm quite sure I did it right this time. I assume the text I add (after a space at the end of the command) is: nopti I hit F10 to boot with the command applied (an alternative to cntrl-x). I needed that alternative because GRUB dumps you in qwerty layout, and I DO NOT use qwerty. With the parameter applied, it crashed (on the initial try). So I don't think the nopti parameter makes any difference. Again, after that, and specifying the old kernel (with no boot parameter), it worked. -- Sincerely, Aere -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1832715] Re: Black screen after reopening lid.
Please attach `journalctl -b -1 -k` to collect last kernel message. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832715 Title: Black screen after reopening lid. Status in linux package in Ubuntu: Confirmed Bug description: Black screen after reopening lid. Configuration : laptop TOSHIBA is running with lid closed but when it is re-opened, the screen still black. Unlocking is impossible. Last OK (operational) nucleus 4.15.0-46. Problem with 4.15.0-47 to 4.15.0-51. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833018] Re: After Installing Updates, system fails to boot on first try
This is a quite good reference on how you do it: https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832239] Re: cosmic kernel (and above) provides two /dev/videoX device but there should be only one video device physically
Can you list some affected apps? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832239 Title: cosmic kernel (and above) provides two /dev/videoX device but there should be only one video device physically Status in linux package in Ubuntu: Confirmed Bug description: Since cosmic kernel (4.18) and above, I am aware that there will be two /dev/videoX even there is only one device physically. This issue could be found in many hardware platforms[1] [Steps to Reproduce] 1. Install Ubuntu desktop image (cosmic or above) on one of the platforms[1] 2. Check /dev/video* [Expected Result] There is only /dev/video0 because there is only one video device (the default webcam). [Actual Result] Both of /dev/video0 and /dev/video1 are shown. [1] The platforms have this issue: Dell Vostro 5568 Dell OptiPlex 3011 All In One Dell Computer Corporation XPS 15 9550 Dell Latitude E5570 Dell Vostro 3459 Dell Vostro 3559 Lenovo ThinkCentre Edge 62z All In One - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-21-generic 4.18.0-21.22 ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1388 F pulseaudio Date: Mon Jun 10 11:20:43 2019 InstallationDate: Installed on 2018-11-23 (199 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Vostro 5568 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=89c301bf-b96d-44b3-890f-71987524c021 ro RelatedPackageVersions: linux-restricted-modules-4.18.0-21-generic N/A linux-backports-modules-4.18.0-21-generic N/A linux-firmware 1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.1:bd07/18/2016:svnDellInc.:pnVostro5568:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 5568 dmi.product.sku: 0786 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832239/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832048] Re: hinic: fix oops due to race in set_rx_mode
** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832048 Title: hinic: fix oops due to race in set_rx_mode Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] It is possible for the hinic driver to oops after the module is removed and reinserted. [Test Case] while :; do sudo modprobe -r hinic; modprobe hinic; done [Fix] From linux-next: 66350023d5756 hinic: fix a bug in set rx mode [Regression Risk] Patch is local to the hinic driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1751268]
Alec, any updates here? Did you get any chance to bisect the results? Priority is updated as the issue isn't in drmtip. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751268 Title: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crtc 1 Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu Desktop Bionic up to date System doesn't boot with an external monitor attached. There is this message in the journal (full journal attached for this boot) fbcon: inteldrmfb (fb0) is primary device [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck vblank wait timed out on crtc 1 [ cut here ] WARNING: CPU: 3 PID: 201 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 drm_wait_one_vblank+0x19b/0x1b0 [drm] Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U 4.13.0-32-generic #35-Ubuntu Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013 Workqueue: events_unbound async_run_entry_fn task: 9760d81cae80 task.stack: b01dc1fb8000 RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm] RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282 RAX: 001f RBX: 9760d708 RCX: RDX: RSI: 0002 RDI: 0246 RBP: b01dc1fbb828 R08: 001f R09: 0002af84 R10: b01dc1fbb7c8 R11: 041b R12: 0001 R13: 0170 R14: 0001 R15: FS: () GS:9760eef8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0 Call Trace: ? wait_woken+0x80/0x80 ironlake_crtc_enable+0x477/0xc00 [i915] ? gen6_write8+0x190/0x190 [i915] intel_update_crtc+0x4b/0xe0 [i915] intel_update_crtcs+0x5b/0x80 [i915] intel_atomic_commit_tail+0x254/0xf90 [i915] ? __schedule+0x293/0x880 intel_atomic_commit+0x3d5/0x490 [i915] ? drm_atomic_check_only+0x37b/0x540 [drm] drm_atomic_commit+0x4b/0x50 [drm] restore_fbdev_mode+0x15e/0x270 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] intel_fbdev_set_par+0x1a/0x70 [i915] fbcon_init+0x484/0x650 visual_init+0xd6/0x130 do_bind_con_driver+0x1fc/0x410 do_take_over_console+0x82/0x1a0 do_fbcon_takeover+0x5c/0xb0 fbcon_event_notify+0x587/0x780 notifier_call_chain+0x4a/0x70 blocking_notifier_call_chain+0x43/0x60 fb_notifier_call_chain+0x1b/0x20 register_framebuffer+0x24d/0x360 drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper] intel_fbdev_initial_config+0x18/0x30 [i915] async_run_entry_fn+0x36/0x150 process_one_work+0x1e7/0x410 worker_thread+0x4b/0x420 kthread+0x125/0x140 ? process_one_work+0x410/0x410 ? kthread_create_on_node+0x70/0x70 ret_from_fork+0x1f/0x30 Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 ---[ end trace a1db7ccd0b5e4dfc ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: j-lallement 3671 F pulseaudio /dev/snd/controlC0: j-lallement 3671 F pulseaudio /dev/snd/controlC1: j-lallement 3671 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 13:58:39 2018 InstallationDate: Installed on 2013-09-03 (1633 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) MachineType: ASUSTeK COMPUTER INC. UX32VD ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware
[Kernel-packages] [Bug 1751268]
Bisecting is a manual process, since it's some option (or combination thereof) enabled in Fedora's .config that's the problem rather than a bad commit which git can help with. You're right in that it's not drm-tip itself. In fact, while the original weirdness manifested itself in drm, it also trashed the disk controller. In the last couple stock fedora kernels (5.1.6 and 5.1.8), the problem has shifted to the keyboard controller (or maye it's usb, haven't disentabled it). So something in there is stomping on things it shouldn't, and for the longest time, that was the video driver. Since I'm now pretty certain it's not your bug, closing this one is fine: I'll keep poking at it till I solve it, or until I finally upgrade this T430, whichever comes first :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751268 Title: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crtc 1 Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: Ubuntu Desktop Bionic up to date System doesn't boot with an external monitor attached. There is this message in the journal (full journal attached for this boot) fbcon: inteldrmfb (fb0) is primary device [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck vblank wait timed out on crtc 1 [ cut here ] WARNING: CPU: 3 PID: 201 at /build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 drm_wait_one_vblank+0x19b/0x1b0 [drm] Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U 4.13.0-32-generic #35-Ubuntu Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013 Workqueue: events_unbound async_run_entry_fn task: 9760d81cae80 task.stack: b01dc1fb8000 RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm] RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282 RAX: 001f RBX: 9760d708 RCX: RDX: RSI: 0002 RDI: 0246 RBP: b01dc1fbb828 R08: 001f R09: 0002af84 R10: b01dc1fbb7c8 R11: 041b R12: 0001 R13: 0170 R14: 0001 R15: FS: () GS:9760eef8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0 Call Trace: ? wait_woken+0x80/0x80 ironlake_crtc_enable+0x477/0xc00 [i915] ? gen6_write8+0x190/0x190 [i915] intel_update_crtc+0x4b/0xe0 [i915] intel_update_crtcs+0x5b/0x80 [i915] intel_atomic_commit_tail+0x254/0xf90 [i915] ? __schedule+0x293/0x880 intel_atomic_commit+0x3d5/0x490 [i915] ? drm_atomic_check_only+0x37b/0x540 [drm] drm_atomic_commit+0x4b/0x50 [drm] restore_fbdev_mode+0x15e/0x270 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] intel_fbdev_set_par+0x1a/0x70 [i915] fbcon_init+0x484/0x650 visual_init+0xd6/0x130 do_bind_con_driver+0x1fc/0x410 do_take_over_console+0x82/0x1a0 do_fbcon_takeover+0x5c/0xb0 fbcon_event_notify+0x587/0x780 notifier_call_chain+0x4a/0x70 blocking_notifier_call_chain+0x43/0x60 fb_notifier_call_chain+0x1b/0x20 register_framebuffer+0x24d/0x360 drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper] intel_fbdev_initial_config+0x18/0x30 [i915] async_run_entry_fn+0x36/0x150 process_one_work+0x1e7/0x410 worker_thread+0x4b/0x420 kthread+0x125/0x140 ? process_one_work+0x410/0x410 ? kthread_create_on_node+0x70/0x70 ret_from_fork+0x1f/0x30 Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 ---[ end trace a1db7ccd0b5e4dfc ]--- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: j-lallement 3671 F pulseaudio /dev/snd/controlC0: j-lallement 3671 F pulseaudio /dev/snd/controlC1: j-lallement 3671 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Feb 23 13:58:39 2018 InstallationDate: Installed
[Kernel-packages] [Bug 1833147] [NEW] hns: attempt to restart autoneg when disabled should report error
Public bug reported: [Impact] Asking the driver to restart autonegotiation silently fails when autonegotation has been disabled. It should report an error. [Test Case] sudo ethtool -s ethX autoneg off sudo ethtool -r ethX [Fix] ed29ca8b95925 net: hns: Restart autoneg need return failed when autoneg off [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu) Assignee: dann frazier (dannf) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833147 Title: hns: attempt to restart autoneg when disabled should report error Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Bug description: [Impact] Asking the driver to restart autonegotiation silently fails when autonegotation has been disabled. It should report an error. [Test Case] sudo ethtool -s ethX autoneg off sudo ethtool -r ethX [Fix] ed29ca8b95925 net: hns: Restart autoneg need return failed when autoneg off [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
I'll do my best to provide a test kernel by tomorrow, for impacted user to test, and confirm it works before I submit it to the Ubuntu kernel team. Stay tuned. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832299] Re: Add new sound card PCIID into the alsa driver
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1832299 Title: Add new sound card PCIID into the alsa driver Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1832299 The 0001-xxx.patch is for adding the ICL pciid, it is not in the bionic kernel, so bionic kernel needs two patches. The 0002-xxx.patch is in the upstream from v5.2-rc1, it is needed for b/c/d/e. [Impact] We have some cometlake machines, after installing the bionic kernel, the sound can't work at all, we found the sound driver didn't load into the kernel. [Fix] After add the pciid in the pci_driver, the sound driver can be loaded and sound worked well. [Test Case] Boot the system and play sound or record sound, they all worked well [Regression Risk] Low. Adding new pciid, will not change existing functions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1832299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826868] Re: Sound device not detected after resume from hibernate
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Bug description: The patch is already in the v5.2-rc1, so don't send the patch to unstable. In the V2, I added 3 more patches. The 0001-xxx.patch is for fixing the issue of "audio doesn't work after s3/s4 on cln and glk machines", but it introduces a new issue of "screen flickering when CDCLK changes", So I added 0002/3/4-xxx.patch to fix the new issue. [Impact] After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi monitor is not plugged before s3 or s4, the re-probe will fail on cnl and glk machines. [Fix] Keep the cdclk alive when re-probing [Test Case] I applied the patches to bionic kernel and disco kernel, and tested them on Whiskeylake, cannonlake, kabylake, skylake and geminilake machines, before s3, I verified analogue audio, hdmi audio and screen dispaly all worked well, then let the system enter s3 and resume, recheck the analogue audio, hdmi audio and screen display, all worked well too. And repeated the test 5 times. [Regression Risk] Low. I have tested the patched kernel on different Dell and Lenovo machines, they include Whiskeylake, cannonlake, kabylake, skylake and geminilake. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 -- 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/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563 InstallationDate: Installed on 2017-06-13 (279 days ago) InstallationMedia: Xubuntu 17.04
[Kernel-packages] [Bug 1831978] Re: linux-oem: 4.15.0-1040.45 -proposed tracker
*** This bug is a duplicate of bug 1832468 *** https://bugs.launchpad.net/bugs/1832468 This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1831978 Title: linux-oem: 4.15.0-1040.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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Sunday, 09. June 2019 11:32 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/1831978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831828] Re: [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 -- 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/1831828 Title: [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Fix Released Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Invalid Bug description: SRU justification: [Impact] RTL8822BE/RTL8822CE need new driver rtw88 supports. [Fix] This is a new mac80211 driver for Realtek 802.11ac wireless network chips. And it needs new firmware too. [Test] Verified on hardware. Tests result are good. [Regression Potential] Low, it introducs the new driver to enable new wifi chips supports. 2 more upstream commits are introduced: e7d4a95da bitfield: fix *_encode_bits() 00b0c9b82 Add primitives for manipulating bitfields both in host- and fixed-endian. These 2 commits add "le32p_replace_bits" functions that rtw88 uses. They introduced new operator of bitfields since 4.16 kernel, don't change exsit funtions. C/D/OEM-OSP-1 don't need these 2 patches. These firmwares are already in disco. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757422] Re: Fix Runtime PM for r8169
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1757422 Title: Fix Runtime PM for r8169 Status in HWE Next: New Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Status in linux-oem source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] r8169 stays in D0 even when no ethernet cable is plugged in. This drains lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0, 1.8W when r8169 is in D3. The power saved is substantial. [Fix] Improved rumtime PM logic to let the device gets suspended (D3) when the port is not in used and the link is down. [Test Case] The chip version is 8168h/8111h. Test when no ethernet gets plugged. Powertop shows power consumption is roughly 5.5W. lspci shows the device is in D0. With the patch, The power consumption is reduced to 1.8W. lspci shows the device is in D3, PME# is correctly enabled. Plug ethernet cable can corretly wake up the device. Unplug the cable, the device gets suspended to D3 correctly. [Regression Potential] Medium. - r8169 is so ubiquitous, with lots of different chip versions. It's hard to test all of them. - PCI D3 needs system firmware (ACPI) support, this might hit some plaform bugs. - the code is still in v4.16-rc*, so it's not well tested by end users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1757422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831840] Re: Support new ums-realtek device
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 -- 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/1831840 Title: Support new ums-realtek device Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Incomplete Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Incomplete Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] Realtek storage device uses usb-storage by default. It works but we should use ums-realtek to bring more functionality, e.g. enabling/disabling MMC card detection. [Fix] Add its device ID to the driver. [Test] After this patch applied, we can use enable_mmc module option to control MMC detection. [Regression Potential] Low. The scope is limited to one device, and the driver is quite stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831065] Re: does not detect headphone when there is no other output devices
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Cosmic) Status: Invalid => Fix Released ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1831065 Title: does not detect headphone when there is no other output devices Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Fix Released Bug description: These two patches are already in the kernel-v5.0, so only B and C need these two patches. [Impact] On a Dell machine, there is no other output devices but a headphone on it, when plugging headset, the headset-mic can't work. [Fix] The headphone detection method is buggy, the driver can't detect the headphone, then the driver will not initialize for headset-mic, after applying these patches, the problem is fixed. [Test Case] Plug headset and record the sound from headset-mic, it works well. [Regression Risk] Low. the patch just change the headphone detection function, and the function is already in the kernel from 5.0-rc, no bug is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker
*** This bug is a duplicate of bug 1832468 *** https://bugs.launchpad.net/bugs/1832468 This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1832206 Title: linux-oem: 4.15.0-1041.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Testing phase-changed: Tuesday, 11. June 2019 12:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831065] Re: does not detect headphone when there is no other output devices
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 -- 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/1831065 Title: does not detect headphone when there is no other output devices Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Fix Released Bug description: These two patches are already in the kernel-v5.0, so only B and C need these two patches. [Impact] On a Dell machine, there is no other output devices but a headphone on it, when plugging headset, the headset-mic can't work. [Fix] The headphone detection method is buggy, the driver can't detect the headphone, then the driver will not initialize for headset-mic, after applying these patches, the problem is fixed. [Test Case] Plug headset and record the sound from headset-mic, it works well. [Regression Risk] Low. the patch just change the headphone detection function, and the function is already in the kernel from 5.0-rc, no bug is reported. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] r8169 failed to establish connection after the fix for LP: #1752772 landed. [Fix] Accepts BIOS WoL settings again, and disables MSI-X for certain chip revisions. [Test] Users confirmed the fix worked for them. [Regression Potential] Low. This brings back the old behavior for both WoL and MSI. ===Original Bug Report=== When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T 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.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832468] Re: linux-oem: 4.15.0-1042.47 -proposed tracker
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1832468 Title: linux-oem: 4.15.0-1042.47 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829219 phase: Ready for Testing phase-changed: Monday, 17. June 2019 18:01 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831828] Re: [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Cosmic) Status: Invalid => Fix Released ** Changed in: linux-oem (Ubuntu Disco) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1831828 Title: [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Fix Released Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Invalid Bug description: SRU justification: [Impact] RTL8822BE/RTL8822CE need new driver rtw88 supports. [Fix] This is a new mac80211 driver for Realtek 802.11ac wireless network chips. And it needs new firmware too. [Test] Verified on hardware. Tests result are good. [Regression Potential] Low, it introducs the new driver to enable new wifi chips supports. 2 more upstream commits are introduced: e7d4a95da bitfield: fix *_encode_bits() 00b0c9b82 Add primitives for manipulating bitfields both in host- and fixed-endian. These 2 commits add "le32p_replace_bits" functions that rtw88 uses. They introduced new operator of bitfields since 4.16 kernel, don't change exsit funtions. C/D/OEM-OSP-1 don't need these 2 patches. These firmwares are already in disco. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831840] Re: Support new ums-realtek device
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Cosmic) Status: Won't Fix => Fix Released ** Changed in: linux-oem (Ubuntu Disco) Status: Won't Fix => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1831840 Title: Support new ums-realtek device Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Incomplete Status in linux-oem source package in Cosmic: Fix Released Status in linux source package in Disco: Incomplete Status in linux-oem source package in Disco: Fix Released Bug description: [Impact] Realtek storage device uses usb-storage by default. It works but we should use ums-realtek to bring more functionality, e.g. enabling/disabling MMC card detection. [Fix] Add its device ID to the driver. [Test] After this patch applied, we can use enable_mmc module option to control MMC detection. [Regression Potential] Low. The scope is limited to one device, and the driver is quite stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832569] Re: linux-oracle: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832567 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:35 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:38 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832569 Title: linux-oracle: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832567 (xenial/linux-oracle) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:38 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832569/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832561] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832560 (xenial/linux-gcp) derivatives: bug 1832556 (gcp-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:35 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:37 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832561 Title: linux-gcp: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832560 (xenial/linux-gcp) derivatives: bug 1832556 (gcp-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:37 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832544] Re: linux-snapdragon: 4.15.0-1056.60 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832543 (dragonboard-kernel) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1832578 - phase: Packaging - phase-changed: Friday, 14. June 2019 17:33 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:37 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Holding -- master bug not ready for proposed 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/1832544 Title: linux-snapdragon: 4.15.0-1056.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832543 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1832578 phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:37 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832544/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832503] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832502 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1832508 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 11:32 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:35 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832503 Title: linux-azure: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832502 (bionic/linux-azure) -- swm properties -- kernel-stable-master-bug: 1832508 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:35 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832503/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832570] Re: linux-fips: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:35 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:38 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832570 Title: linux-fips: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832578 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:38 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832565] Re: linux-ibm-gt: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:35 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:38 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832565 Title: linux-ibm-gt: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832578 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:38 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832565/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832505] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832504 (bionic/linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1832508 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 11:32 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:36 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832505 Title: linux-gcp: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832504 (bionic/linux-gcp-edge) -- swm properties -- kernel-stable-master-bug: 1832508 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:36 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832499] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832497 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1832508 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 11:32 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:35 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832499 Title: linux-aws: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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 Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832497 (bionic/linux-aws-edge) -- swm properties -- kernel-stable-master-bug: 1832508 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:35 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832499/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832552] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832547 (xenial/linux-aws-hwe) derivatives: bug 1832546 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:34 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:37 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832552 Title: linux-aws: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832547 (xenial/linux-aws-hwe) derivatives: bug 1832546 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:37 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832552/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832545] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:34 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:37 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- 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/1832545 Title: linux-oem: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832578 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:37 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832542] Re: linux-raspi2: 4.15.0-1039.41 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832541 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Packaging phase-changed: Friday, 14. June 2019 16:04 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + prepare-package: Pending -- package tag not yet published + promote-to-proposed: Pending -- source package tags missing variant: debs -- 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/1832542 Title: linux-raspi2: 4.15.0-1039.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832541 (pi-kernel) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Packaging phase-changed: Friday, 14. June 2019 16:04 UTC reason: prepare-package: Pending -- package tag not yet published promote-to-proposed: Pending -- source package tags missing variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832506] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832508 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 11:32 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:36 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832506 Title: linux-kvm: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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 Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832508 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:36 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832506/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832564] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:35 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:38 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832564 Title: linux-kvm: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832578 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:38 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832583] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832593 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:37 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:39 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832583 Title: linux-kvm: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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 Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832593 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:39 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832575] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832573 (trusty/linux-azure) derivatives: bug 1832571 (azure-kernel), bug 1832572 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1832578 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:36 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:38 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832575 Title: linux-azure: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832573 (trusty/linux-azure) derivatives: bug 1832571 (azure-kernel), bug 1832572 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1832578 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:38 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832589] Re: linux-snapdragon: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832587 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1832593 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:37 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:39 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832589 Title: linux-snapdragon: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832587 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1832593 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:39 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832585] Re: linux-raspi2: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832584 (pi2-kernel) -- swm properties -- kernel-stable-master-bug: 1832593 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:37 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:39 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- 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/1832585 Title: linux-raspi2: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832584 (pi2-kernel) -- swm properties -- kernel-stable-master-bug: 1832593 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:39 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832582] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832581 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1832593 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:36 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:39 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832582 Title: linux-aws: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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 Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1832581 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1832593 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:39 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832582/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832590] Re: linux-fips: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832593 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:37 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:40 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832590 Title: linux-fips: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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: 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832593 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:40 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832591] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832593 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 14:38 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:40 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832591 Title: linux-aws: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832593 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:40 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832486] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 10:31 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:34 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832486 Title: linux-gcp: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:34 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832485] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 10:31 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:33 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832485 Title: linux-azure: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New 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 stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:33 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832488] Re: linux-snapdragon: 5.0.0-1015.15 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1832492 - phase: Packaging - phase-changed: Friday, 14. June 2019 13:32 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:34 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Holding -- master bug not ready for proposed 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/1832488 Title: linux-snapdragon: 5.0.0-1015.15 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1832492 phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:34 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832483] Re: linux-raspi2: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1832492 - phase: Packaging - phase-changed: Friday, 14. June 2019 13:01 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:33 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Holding -- master bug not ready for proposed variant: debs -- 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/1832483 Title: linux-raspi2: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1832492 phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:33 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832484] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 10:31 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:33 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832484 Title: linux-aws: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:33 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832484/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832487] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 - phase: Holding before Packaging - phase-changed: Wednesday, 12. June 2019 10:31 UTC + phase: Ready for Packaging + phase-changed: Monday, 17. June 2019 22:34 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified 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/1832487 Title: linux-kvm: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1832492 phase: Ready for Packaging phase-changed: Monday, 17. June 2019 22:34 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832593] Re: linux: 4.4.0-152.179 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832591 (trusty/linux-aws), bug 1832592 (trusty/linux-lts-xenial) derivatives: bug 1832580 (pc-kernel), bug 1832582 (linux-aws), bug 1832583 (linux-kvm), bug 1832585 (linux-raspi2), bug 1832589 (linux-snapdragon), bug 1832590 (linux-fips) -- swm properties -- - phase: Packaging - phase-changed: Thursday, 13. June 2019 10:00 UTC + boot-testing-requested: true + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:32 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present 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/1832593 Title: linux: 4.4.0-152.179 -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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832591 (trusty/linux-aws), bug 1832592 (trusty/linux-lts-xenial) derivatives: bug 1832580 (pc-kernel), bug 1832582 (linux-aws), bug 1832583 (linux-kvm), bug 1832585 (linux-raspi2), bug 1832589 (linux-snapdragon), bug 1832590 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:32 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832593/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832492] Re: linux: 5.0.0-18.19 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832489 (bionic/linux-hwe-edge), bug 1832491 (bionic/linux-oem-osp1) derivatives: bug 1832483 (linux-raspi2), bug 1832484 (linux-aws), bug 1832485 (linux-azure), bug 1832486 (linux-gcp), bug 1832487 (linux-kvm), bug 1832488 (linux-snapdragon) -- swm properties -- - phase: Packaging - phase-changed: Wednesday, 12. June 2019 17:30 UTC + boot-testing-requested: true + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:31 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 - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present 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/1832492 Title: linux: 5.0.0-18.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: 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 Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832489 (bionic/linux-hwe-edge), bug 1832491 (bionic/linux-oem-osp1) derivatives: bug 1832483 (linux-raspi2), bug 1832484 (linux-aws), bug 1832485 (linux-azure), bug 1832486 (linux-gcp), bug 1832487 (linux-kvm), bug 1832488 (linux-snapdragon) -- swm properties -- boot-testing-requested: true phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:31 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832492/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832508] Re: linux: 4.18.0-23.24 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832507 (bionic/linux-hwe) derivatives: bug 1832496 (linux-raspi2), bug 1832499 (linux-aws), bug 1832503 (linux-azure), bug 1832505 (linux-gcp), bug 1832506 (linux-kvm) -- swm properties -- - phase: Packaging - phase-changed: Wednesday, 12. June 2019 18:00 UTC + boot-testing-requested: true + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:31 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present 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/1832508 Title: linux: 4.18.0-23.24 -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 Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832507 (bionic/linux-hwe) derivatives: bug 1832496 (linux-raspi2), bug 1832499 (linux-aws), bug 1832503 (linux-azure), bug 1832505 (linux-gcp), bug 1832506 (linux-kvm) -- swm properties -- boot-testing-requested: true phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:31 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832508/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832496] Re: linux-raspi2: 4.18.0-1017.19 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1832508 - phase: Packaging - phase-changed: Friday, 14. June 2019 14:02 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:35 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Holding -- master bug not ready for proposed variant: debs -- 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/1832496 Title: linux-raspi2: 4.18.0-1017.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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Cosmic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1832508 phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:35 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832496/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832578] Re: linux: 4.15.0-53.57 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832575 (xenial/linux-azure), bug 1832577 (xenial/linux-hwe) derivatives: bug 1832539 (pc-kernel), bug 1832540 (pc-lowlatency-kernel), bug 1832542 (linux-raspi2), bug 1832544 (linux-snapdragon), bug 1832545 (linux-oem), bug 1832552 (linux-aws), bug 1832561 (linux-gcp), bug 1832563 (linux-gke-4.15), bug 1832564 (linux-kvm), bug 1832565 (linux-ibm-gt), bug 1832569 (linux-oracle), bug 1832570 (linux-fips) -- swm properties -- - phase: Packaging - phase-changed: Thursday, 13. June 2019 08:30 UTC + boot-testing-requested: true + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:32 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present 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/1832578 Title: linux: 4.15.0-53.57 -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 Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1832575 (xenial/linux-azure), bug 1832577 (xenial/linux-hwe) derivatives: bug 1832539 (pc-kernel), bug 1832540 (pc-lowlatency-kernel), bug 1832542 (linux-raspi2), bug 1832544 (linux-snapdragon), bug 1832545 (linux-oem), bug 1832552 (linux-aws), bug 1832561 (linux-gcp), bug 1832563 (linux-gke-4.15), bug 1832564 (linux-kvm), bug 1832565 (linux-ibm-gt), bug 1832569 (linux-oracle), bug 1832570 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:32 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833141] [NEW] hns: Fix WARNING when remove HNS driver with SMMU enabled
Public bug reported: [Impact] When the SMMU is enabled, removal of the hns_enet_drv module will trip a WARNING. [Test Case] sudo modprobe -r hns_enet_drv [Fix] 8601a99d7c025 net: hns: Fix WARNING when remove HNS driver with SMMU enabled [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833141 Title: hns: Fix WARNING when remove HNS driver with SMMU enabled Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] When the SMMU is enabled, removal of the hns_enet_drv module will trip a WARNING. [Test Case] sudo modprobe -r hns_enet_drv [Fix] 8601a99d7c025 net: hns: Fix WARNING when remove HNS driver with SMMU enabled [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833140] [NEW] hns: fix ICMP6 neighbor solicitation messages discard problem
Public bug reported: [Impact] ICMP6 neighbor solicitation messages are discarded. [Test Case] Regression tested only [Fix] ea401685a20b5 net: hns: fix unsigned comparison to less than zero f058e46855dcb net: hns: fix ICMP6 neighbor solicitation messages discard problem [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833140 Title: hns: fix ICMP6 neighbor solicitation messages discard problem Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] ICMP6 neighbor solicitation messages are discarded. [Test Case] Regression tested only [Fix] ea401685a20b5 net: hns: fix unsigned comparison to less than zero f058e46855dcb net: hns: fix ICMP6 neighbor solicitation messages discard problem [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833132] Re: net: hns: Fix loopback test failed at copper ports
** Description changed: [Impact] The ethtool offline test always fails on HNS devices w/ copper ports. [Test Case] sudo ethtool -t enahisic2i1 offline [Fix] - 01be367eef9d0 net: hns: Fix loopback test failed at copper ports + 2e1f164861e50 net: hns: Fix loopback test failed at copper ports [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833132 Title: net: hns: Fix loopback test failed at copper ports Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] The ethtool offline test always fails on HNS devices w/ copper ports. [Test Case] sudo ethtool -t enahisic2i1 offline [Fix] 2e1f164861e50 net: hns: Fix loopback test failed at copper ports [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833136] Re: use-after-free in hns_nic_net_xmit_hw
** Description changed: [Impact] KASAN detected a use-after-free condition, which could lead to memory corruption or a crash. [Test Case] Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg. [Fix] - 7848b9e26cab9 net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw( - + 3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. ** Description changed: [Impact] KASAN detected a use-after-free condition, which could lead to memory corruption or a crash. [Test Case] Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg. [Fix] 3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() + [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833136 Title: use-after-free in hns_nic_net_xmit_hw Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] KASAN detected a use-after-free condition, which could lead to memory corruption or a crash. [Test Case] Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg. [Fix] 3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833138] [NEW] Fix occasional boot time crash in hns driver
Public bug reported: [Impact] On rare occasions, the hns driver will oops on start-up [Test Case] Reboot, watch for oops [Fix] c0b0984426814 net: hns: Fix probabilistic memory overwrite when HNS driver initialized [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Cosmic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Cosmic) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833138 Title: Fix occasional boot time crash in hns driver Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] On rare occasions, the hns driver will oops on start-up [Test Case] Reboot, watch for oops [Fix] c0b0984426814 net: hns: Fix probabilistic memory overwrite when HNS driver initialized [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but 904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't. So the kernel bisection is completed and found the right good commit which is: https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but ac3069e67f5659131d7ac5f54d966005bbc40af8 doesn't. So the kernel bisection is completed and found the right good commit which is: https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833136] [NEW] use-after-free in hns_nic_net_xmit_hw
Public bug reported: [Impact] KASAN detected a use-after-free condition, which could lead to memory corruption or a crash. [Test Case] Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg. [Fix] 3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833136 Title: use-after-free in hns_nic_net_xmit_hw Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Bug description: [Impact] KASAN detected a use-after-free condition, which could lead to memory corruption or a crash. [Test Case] Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg. [Fix] 3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832286] Re: Remote denial of service (resource exhaustion) caused by low Maximum Segment Size values
This bug report represents CVE-2019-11479 ** Summary changed: - placeholder bug + Remote denial of service (resource exhaustion) caused by low Maximum Segment Size values ** Description changed: - placeholder bug + Jonathan Looney discovered that a remote attacker could cause a denial + of service (resource exhaustion) via a maliciously crafted TCP session. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11479 ** Changed in: linux (Ubuntu) Status: New => Fix Committed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Tyler Hicks (tyhicks) ** Information type changed from Private Security to Public Security ** Description changed: Jonathan Looney discovered that a remote attacker could cause a denial - of service (resource exhaustion) via a maliciously crafted TCP session. + of service (resource exhaustion) via a maliciously crafted TCP session + that utilizes a low MSS value. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832286 Title: Remote denial of service (resource exhaustion) caused by low Maximum Segment Size values Status in linux package in Ubuntu: Fix Committed Bug description: Jonathan Looney discovered that a remote attacker could cause a denial of service (resource exhaustion) via a maliciously crafted TCP session that utilizes a low MSS value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831637] Re: Remote denial of service (system crash) caused by integer overflow in TCP SACK handling
This bug report represents CVE-2019-11477 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11477 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831637 Title: Remote denial of service (system crash) caused by integer overflow in TCP SACK handling Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: New Status in linux source package in Trusty: New Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Jonathan Looney discovered that a remote attacker could cause a denial of service (system crash) via a maliciously crafted TCP session and a certain sequence of SACKs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831638] Re: Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation
This bug report represents CVE-2019-11478 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11478 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831638 Title: Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: New Status in linux source package in Trusty: New Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Jonathan Looney discovered that a remote attacker could cause a denial of service (resource exhaustion) via a maliciously crafted sequence of TCP SACKs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833132] Re: hns bug fixes
** Description changed: [Impact] Several bugs for the hns driver have recently been fixed, including a number of crashes and a memory corruption issue. [Test Case] Boot on D05. Verify that the hns modules can be removed w/o error. Verify that the loopback test succeeds on a copper port: sudo ethtool -t enahisic2i1 offline [Fix] 01be367eef9d0 net: hns: Fix loopback test failed at copper ports - f6136d021dc81 net: hns: fix unsigned comparison to less than zero f0bad645b691b net: hns: Fix sparse: some warnings in HNS drivers 0e51eda72399c net: hns: Fix WARNING when remove HNS driver with SMMU enabled - 3881c4420229d net: hns: fix ICMP6 neighbor solicitation messages discard problem ff5d4e1544dfc net: hns: Fix probabilistic memory overwrite when HNS driver initialized 7848b9e26cab9 net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fixes are restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. ** Summary changed: - hns bug fixes + net: hns: Fix loopback test failed at copper ports ** Description changed: [Impact] - Several bugs for the hns driver have recently been fixed, including a number of crashes and a memory corruption issue. + The ethtool offline test always fails on HNS devices w/ copper ports. [Test Case] - Boot on D05. - Verify that the hns modules can be removed w/o error. - Verify that the loopback test succeeds on a copper port: sudo ethtool -t enahisic2i1 offline + sudo ethtool -t enahisic2i1 offline [Fix] 01be367eef9d0 net: hns: Fix loopback test failed at copper ports - f0bad645b691b net: hns: Fix sparse: some warnings in HNS drivers - 0e51eda72399c net: hns: Fix WARNING when remove HNS driver with SMMU enabled - ff5d4e1544dfc net: hns: Fix probabilistic memory overwrite when HNS driver initialized - 7848b9e26cab9 net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] - Fixes are restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. + Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833132 Title: net: hns: Fix loopback test failed at copper ports Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] The ethtool offline test always fails on HNS devices w/ copper ports. [Test Case] sudo ethtool -t enahisic2i1 offline [Fix] 01be367eef9d0 net: hns: Fix loopback test failed at copper ports [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
I spoke too soon, it's back again this morning when I accidentally clicked and dragged a hyperlink in Chrome: Jun 18 07:43:22 bxps /usr/lib/gdm3/gdm-x-session[3594]: nvLock: client timed out, taking the lock Jun 18 07:43:27 bxps /usr/lib/gdm3/gdm-x-session[3594]: nvLock: client timed out, taking the lock -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1825626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833132] Re: hns bug fixes
** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833132 Title: hns bug fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] Several bugs for the hns driver have recently been fixed, including a number of crashes and a memory corruption issue. [Test Case] Boot on D05. Verify that the hns modules can be removed w/o error. Verify that the loopback test succeeds on a copper port: sudo ethtool -t enahisic2i1 offline [Fix] 01be367eef9d0 net: hns: Fix loopback test failed at copper ports f0bad645b691b net: hns: Fix sparse: some warnings in HNS drivers 0e51eda72399c net: hns: Fix WARNING when remove HNS driver with SMMU enabled ff5d4e1544dfc net: hns: Fix probabilistic memory overwrite when HNS driver initialized 7848b9e26cab9 net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fixes are restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833132] [NEW] hns bug fixes
Public bug reported: [Impact] Several bugs for the hns driver have recently been fixed, including a number of crashes and a memory corruption issue. [Test Case] Boot on D05. Verify that the hns modules can be removed w/o error. Verify that the loopback test succeeds on a copper port: sudo ethtool -t enahisic2i1 offline [Fix] 01be367eef9d0 net: hns: Fix loopback test failed at copper ports f6136d021dc81 net: hns: fix unsigned comparison to less than zero f0bad645b691b net: hns: Fix sparse: some warnings in HNS drivers 0e51eda72399c net: hns: Fix WARNING when remove HNS driver with SMMU enabled 3881c4420229d net: hns: fix ICMP6 neighbor solicitation messages discard problem ff5d4e1544dfc net: hns: Fix probabilistic memory overwrite when HNS driver initialized 7848b9e26cab9 net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fixes are restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: In Progress ** Affects: linux (Ubuntu Disco) Importance: Undecided Status: In Progress ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833132 Title: hns bug fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: In Progress Bug description: [Impact] Several bugs for the hns driver have recently been fixed, including a number of crashes and a memory corruption issue. [Test Case] Boot on D05. Verify that the hns modules can be removed w/o error. Verify that the loopback test succeeds on a copper port: sudo ethtool -t enahisic2i1 offline [Fix] 01be367eef9d0 net: hns: Fix loopback test failed at copper ports f6136d021dc81 net: hns: fix unsigned comparison to less than zero f0bad645b691b net: hns: Fix sparse: some warnings in HNS drivers 0e51eda72399c net: hns: Fix WARNING when remove HNS driver with SMMU enabled 3881c4420229d net: hns: fix ICMP6 neighbor solicitation messages discard problem ff5d4e1544dfc net: hns: Fix probabilistic memory overwrite when HNS driver initialized 7848b9e26cab9 net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fixes are restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
wbug: With Bug wnbug: With No Bug git bisect start '--term-old=wbug' '--term-new=wnbug' '--' 'drivers/gpu/drm/vmwgfx' # wbug: [62e9ccfaaedffd057e921fca976f9f7f71c9b254] Linux 4.16.18 git bisect wbug 62e9ccfaaedffd057e921fca976f9f7f71c9b254 # wnbug: [37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a] drm/vmwgfx: use monotonic event timestamps git bisect wnbug 37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a # wbug: [7928b2cbe55b2a410a0f5c1f154610059c57b1b2] Linux 4.16-rc1 git bisect wbug 7928b2cbe55b2a410a0f5c1f154610059c57b1b2 # wbug: [aa64b3f18aeb2cc4b74e69115df434147f1ed96c] drm/vmwgfx: Move screen object page flip to atomic function git bisect wbug aa64b3f18aeb2cc4b74e69115df434147f1ed96c # wnbug: [dc366364c4ef809dccd063919314301f8ba01ac2] drm/vmwgfx: Fix multiple command buffer context use git bisect wnbug dc366364c4ef809dccd063919314301f8ba01ac2 # wnbug: [25db875401c8aaac31a6650cb80a56cc78852694] drm/vmwgfx: Cursor update fixes git bisect wnbug 25db875401c8aaac31a6650cb80a56cc78852694 # wnbug: [904efd9e3f4c8f288b1279a316eed8e177190c8f] drm/vmwgfx: Send the correct nonblock option for atomic_commit git bisect wnbug 904efd9e3f4c8f288b1279a316eed8e177190c8f # wbug: [ac3069e67f5659131d7ac5f54d966005bbc40af8] drm/vmwgfx: Move the stdu vblank event to atomic function git bisect wbug ac3069e67f5659131d7ac5f54d966005bbc40af8 # first wnbug commit: [904efd9e3f4c8f288b1279a316eed8e177190c8f] drm/vmwgfx: Send the correct nonblock option for atomic_commit -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name:
[Kernel-packages] [Bug 1829166] Re: linux-azure: 5.0.0-1007.7 -proposed tracker
This bug was fixed in the package linux-azure - 5.0.0-1008.8 --- linux-azure (5.0.0-1008.8) disco; urgency=medium [ Ubuntu: 5.0.0-17.18 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Marcelo Henrique Cerri Tue, 04 Jun 2019 22:43:16 -0300 ** Changed in: linux-azure (Ubuntu Disco) Status: Confirmed => Fix Released -- 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/1829166 Title: linux-azure: 5.0.0-1007.7 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1829173 phase: Ready for Signoff phase-changed: Friday, 31. May 2019 16:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: stakeholder-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832138] Re: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832138 Title: Login screen never appears on vmwgfx but installing kernel >= v4.17-rc1 (or using WaylandEnable=false) fixes it Status in linux package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in mutter source package in Bionic: Incomplete Status in linux source package in Eoan: Invalid Status in mutter source package in Eoan: Invalid Bug description: I'm running Ubuntu 18.04.2 desktop in a virtual machine under VMWare Fusion Pro V11.1.0 on MacOS Mojave 10.14.5, all on a 15inch 2018 Macbook Pro. I've been running this Ubuntu 18.04.2 VM without problem for many months without problem. Yesterday, I did 'sudo apt update; sudo apt upgrade'. Upon rebooting, the system hangs immediately after displaying the splash screen. I never see a login screen. And I can't use Ctrl+Alt+F2 to navigate to a console/tty login. I can SSH into the system however. I've found that I can work around the hang/freeze if I uncomment the following line in /etc/gdm3/custom.conf; #WaylandEnable=false After uncommenting the WaylandEnable=false line and rebooting, then I see the login prompt as expected and I can then log in and use the system normally again. After the 'apt upgrade' my system is running linux kernel 4.15.0-51, as shown in this 'uname -a' output; Linux ubuntuvm1 4.15.0-51-generic #55-Ubuntu SMP Wed May 15 14:27:21 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a output; No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Sun Jun 9 12:38:37 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-05-06 (399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=/dev/mapper/ubuntu--vg-root ro splash net.ifnames=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831638] Re: Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831638 Title: Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: New Status in linux source package in Trusty: New Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Jonathan Looney discovered that a remote attacker could cause a denial of service (resource exhaustion) via a maliciously crafted sequence of TCP SACKs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831638/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831637] Re: Remote denial of service (system crash) caused by integer overflow in TCP SACK handling
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831637 Title: Remote denial of service (system crash) caused by integer overflow in TCP SACK handling Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: New Status in linux source package in Trusty: New Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Fix Released Bug description: Jonathan Looney discovered that a remote attacker could cause a denial of service (system crash) via a maliciously crafted TCP session and a certain sequence of SACKs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831637/+subscriptions -- Mailing list: https://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 1833018] Re: After Installing Updates, system fails to boot on first try
On 6/16/19 10:08 PM, Kai-Heng Feng wrote: > Does kernel parameter "nopti" help? > If, in the GRUB menu, instead of selecting "Ubuntu" (the default at the top of the list), I instead select "advanced options for Ubuntu", and then specify the prior kernel, it works fine, in several tries, without specifying any kernel options. It worked once for the most current kernel that way too, but on trying it again, it failed the same way as before. I tried to figure out how to specify kernel options, and I think I specified it right (nopti at the end of the GRUB menu kernel entry, preceded by a space), but I have no experience doing that, so I can't say for sure I did it right. But in the one attempt to specify the nopti option I did, it crashed during boot. -- Sincerely, Aere -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833018 Title: After Installing Updates, system fails to boot on first try Status in linux package in Ubuntu: Confirmed Bug description: I installed Lubuntu 18.04 LTS on an i386 machine (Dell GX-270). After installation, it rebooted with no problems. I installed all updates, and on rebooting it failed to boot. The screen had unreadable graphics in the top third of it. On rebooting again, it booted okay, saying it recovered the journal. Sometimes, it takes 3 tries to get it to boot. Often, it gets most of the way into the boot process, then suddenly goes into the GRUB menu. I installed this system because my primary partition on the same machine started failing to boot much of the time. This failure started happening after applying updates. I was thinking something in the system files might be corrupted. But the newly-installed system has the same symptoms. After applying updates, I expected the system to boot successfully every time. Instead, it always crashes during the boot, or hangs, on the first try to boot. On the 2nd or 3rd try, it will boot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-51-generic 4.15.0-51.55 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-51-generic. ApportVersion: 2.20.9-0ubuntu7.6 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere805 F pulseaudio /dev/snd/controlC0: aere805 F pulseaudio Card0.Amixer.info: Card hw:0 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card1.Amixer.info: Card hw:1 'MPD218'/'Akai MPD218 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card2.Amixer.values: Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sun Jun 16 18:09:10 2019 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2019-06-16 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic root=UUID=01278e7e-143f-479d-8842-aa15ad6ff5a8 ro quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-51-generic N/A linux-backports-modules-4.15.0-51-generic N/A linux-firmware 1.173.6 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1824474] Re: Is Vcs-Git line correct?
This bug was fixed in the package linux-meta-raspi2 - 4.4.0..111 --- linux-meta-raspi2 (4.4.0..111) xenial; urgency=medium * Bump ABI 4.4.0- * Is Vcs-Git line correct? (LP: #1824474) - Vcs-Git: Fix raspi2 branch checkout -- Stefan Bader Thu, 06 Jun 2019 17:41:11 +0200 ** Changed in: linux-meta-raspi2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1824474 Title: Is Vcs-Git line correct? Status in linux-meta-raspi2 package in Ubuntu: In Progress Status in linux-meta-raspi2 source package in Xenial: Fix Released Status in linux-meta-raspi2 source package in Bionic: Fix Released Status in linux-meta-raspi2 source package in Cosmic: Fix Committed Status in linux-meta-raspi2 source package in Disco: Fix Committed Status in linux-meta-raspi2 source package in Eoan: In Progress Bug description: Impact: apt-get source suggets the wrong instructions when inquiring for linux-meta-raspi2: $ apt-get source linux-meta-raspi2 ... NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. which, if executed, result in a checkout of the master branch in a raspi2 subdirectory (instead of a checkout of the raspi2 branch). Fix: Fix the Vcs-Git line in linux-meta-raspi2/debian/control.common. How to test: Check the output of `apt-get source linux-meta-raspi2`, a fixed version will suggest: ... git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic -b raspi2 ... Regression potential: Very low, trivial modification. -- The control file for the latest version of this package contains: Vcs-Git: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux- meta/+git/disco raspi2 This cauases `apt-get source` to suggest: NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. ...which checks out the sources to the raspi2 subdirectory, instead of checking out the raspi2 branch. Is this supposed to be "-b raspi2" instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi2/+bug/1824474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1757218] Re: QCA9377 isn't being recognized sometimes
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1757218 Title: QCA9377 isn't being recognized sometimes Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Bug description: === SRU Justification === [Impact] Qualcomm WiFi/Bluetooth may disappear after boot. [Fix] Disable USB2 LPM at shutdown phase, to prevent it from lingering in LPM L1. Pull back the device to full power before shutdown imitates the behavior on Windows. [Test] The affected user confimed it fixes the issue. I can also confirm that a) The power drain in S5 is much lower, b) Both WiFi and Bluetooth are always present during reboot stress test. [Regression Potential] Low. Only a limited number of USB2 devices that support LPM. === Original Bug Report === Sometimes, the Wireless Network Card QCA9377 is not recognized on boot. This caused, on prior versions, a kernel panic at boot. With Bionic, the system boots but is unable to use wireless network. On dmesg there are messages like: [2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd [2.808640] usb 1-7: device descriptor read/64, error -71 [3.044337] usb 1-7: device descriptor read/64, error -71 [3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd [3.408245] usb 1-7: device descriptor read/64, error -71 [3.644244] usb 1-7: device descriptor read/64, error -71 [3.752193] usb usb1-port7: attempt power cycle [4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd [4.404904] usb 1-7: Device not responding to setup address. [4.612478] usb 1-7: Device not responding to setup address. [4.820588] usb 1-7: device not accepting address 9, error -71 [4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd [4.949109] usb 1-7: Device not responding to setup address. [5.156893] usb 1-7: Device not responding to setup address. [5.364589] usb 1-7: device not accepting address 10, error -71 [5.364655] usb usb1-port7: unable to enumerate USB device And lspci and lsusb don't show the wireless network card. The alternative is to turn the system off. Reboot don't work and reboot to Windows 10 also don't. The system must be powered off to restore functionality. Then, on the next boot, it works properly. However, after the system is turned off, it may cause the issue again. This is not 100% consistent, but mostly it cycles between powering off and powering on the notebook as: Work -> Don't work -> Work -> Don't work On Windows 10 this doesn't happen but when happens on Ubuntu, it's possible to reboot and see the status on Windows 10 too: on Device Manager it's shown a unidentified USB device at 1-7. Sometimes, on Windows 10's Network Devices it's shown, instead of the QCA9377, from four to six different devices with generic names and Bluetooth and/or Wireless don't work. When turning Ubuntu off, there are messages that appears a few instants before the system is turned off: Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388] ath10k_pci :02:00.0: failed to install key for vdev 0 peer xx:xx:xx:xx:xx:xx: -110 Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399] wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110) Generally, only the second message appears (but both are recorded on kern.log). The MAC adress is the one from the router, not from the wireless card. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-12-generic 4.15.0-12.13 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1364 F pulseaudio /dev/snd/seq:usuario1258 F timidity CurrentDesktop: XFCE Date: Tue Mar 20 14:43:42 2018 HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
[Kernel-packages] [Bug 1757422] Re: Fix Runtime PM for r8169
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1757422 Title: Fix Runtime PM for r8169 Status in HWE Next: New Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Status in linux-oem source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] r8169 stays in D0 even when no ethernet cable is plugged in. This drains lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0, 1.8W when r8169 is in D3. The power saved is substantial. [Fix] Improved rumtime PM logic to let the device gets suspended (D3) when the port is not in used and the link is down. [Test Case] The chip version is 8168h/8111h. Test when no ethernet gets plugged. Powertop shows power consumption is roughly 5.5W. lspci shows the device is in D0. With the patch, The power consumption is reduced to 1.8W. lspci shows the device is in D3, PME# is correctly enabled. Plug ethernet cable can corretly wake up the device. Unplug the cable, the device gets suspended to D3 correctly. [Regression Potential] Medium. - r8169 is so ubiquitous, with lots of different chip versions. It's hard to test all of them. - PCI D3 needs system firmware (ACPI) support, this might hit some plaform bugs. - the code is still in v4.16-rc*, so it's not well tested by end users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1757422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1779817] Re: r8169 no internet after suspending
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1779817 Title: r8169 no internet after suspending Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] r8169 failed to establish connection after the fix for LP: #1752772 landed. [Fix] Accepts BIOS WoL settings again, and disables MSI-X for certain chip revisions. [Test] Users confirmed the fix worked for them. [Regression Potential] Low. This brings back the old behavior for both WoL and MSI. ===Original Bug Report=== When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T 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.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824474] Re: Is Vcs-Git line correct?
This bug was fixed in the package linux-meta-raspi2 - 4.15.0.1038.36 --- linux-meta-raspi2 (4.15.0.1038.36) bionic; urgency=medium * Bump ABI 4.15.0-1038 * Is Vcs-Git line correct? (LP: #1824474) - Vcs-Git: Fix raspi2 branch checkout -- Thadeu Lima de Souza Cascardo Wed, 05 Jun 2019 15:51:57 -0300 ** Changed in: linux-meta-raspi2 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1824474 Title: Is Vcs-Git line correct? Status in linux-meta-raspi2 package in Ubuntu: In Progress Status in linux-meta-raspi2 source package in Xenial: Fix Committed Status in linux-meta-raspi2 source package in Bionic: Fix Released Status in linux-meta-raspi2 source package in Cosmic: Fix Committed Status in linux-meta-raspi2 source package in Disco: Fix Committed Status in linux-meta-raspi2 source package in Eoan: In Progress Bug description: Impact: apt-get source suggets the wrong instructions when inquiring for linux-meta-raspi2: $ apt-get source linux-meta-raspi2 ... NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. which, if executed, result in a checkout of the master branch in a raspi2 subdirectory (instead of a checkout of the raspi2 branch). Fix: Fix the Vcs-Git line in linux-meta-raspi2/debian/control.common. How to test: Check the output of `apt-get source linux-meta-raspi2`, a fixed version will suggest: ... git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic -b raspi2 ... Regression potential: Very low, trivial modification. -- The control file for the latest version of this package contains: Vcs-Git: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux- meta/+git/disco raspi2 This cauases `apt-get source` to suggest: NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. ...which checks out the sources to the raspi2 subdirectory, instead of checking out the raspi2 branch. Is this supposed to be "-b raspi2" instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi2/+bug/1824474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831828] Re: [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1831828 Title: [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88 Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Cosmic: New Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: New Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Bug description: SRU justification: [Impact] RTL8822BE/RTL8822CE need new driver rtw88 supports. [Fix] This is a new mac80211 driver for Realtek 802.11ac wireless network chips. And it needs new firmware too. [Test] Verified on hardware. Tests result are good. [Regression Potential] Low, it introducs the new driver to enable new wifi chips supports. 2 more upstream commits are introduced: e7d4a95da bitfield: fix *_encode_bits() 00b0c9b82 Add primitives for manipulating bitfields both in host- and fixed-endian. These 2 commits add "le32p_replace_bits" functions that rtw88 uses. They introduced new operator of bitfields since 4.16 kernel, don't change exsit funtions. C/D/OEM-OSP-1 don't need these 2 patches. These firmwares are already in disco. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826868] Re: Sound device not detected after resume from hibernate
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1826868 Title: Sound device not detected after resume from hibernate Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Bug description: The patch is already in the v5.2-rc1, so don't send the patch to unstable. In the V2, I added 3 more patches. The 0001-xxx.patch is for fixing the issue of "audio doesn't work after s3/s4 on cln and glk machines", but it introduces a new issue of "screen flickering when CDCLK changes", So I added 0002/3/4-xxx.patch to fix the new issue. [Impact] After s3 or s4, the hdmi audio driver will re-probe the hw, if the hdmi monitor is not plugged before s3 or s4, the re-probe will fail on cnl and glk machines. [Fix] Keep the cdclk alive when re-probing [Test Case] I applied the patches to bionic kernel and disco kernel, and tested them on Whiskeylake, cannonlake, kabylake, skylake and geminilake machines, before s3, I verified analogue audio, hdmi audio and screen dispaly all worked well, then let the system enter s3 and resume, recheck the analogue audio, hdmi audio and screen display, all worked well too. And repeated the test 5 times. [Regression Risk] Low. I have tested the patched kernel on different Dell and Lenovo machines, they include Whiskeylake, cannonlake, kabylake, skylake and geminilake. dmesg -w shows the following: snd_hda_codec_realtek hdaudioC0D0: out of range cmd 0:20:400: snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1551 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 21:22:18 2019 InstallationDate: Installed on 2019-04-24 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 0bda:b00b Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Stream x360 Convertible 11-ag1XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=e0182eac-9bb3-45c5-b4e9-3b21715dbc95 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 SourcePackage: linux StagingDrivers: r8822be UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8501 dmi.board.vendor: HP dmi.board.version: 05.21 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.10:bd05/22/2018:svnHP:pnHPStreamx360Convertible11-ag1XX:pvrType1ProductConfigId:rvnHP:rn8501:rvr05.21:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Stream x360 Convertible 11-ag1XX dmi.product.sku: 4RV86PA#ABG dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832206] Re: linux-oem: 4.15.0-1041.46 -proposed tracker
*** This bug is a duplicate of bug 1832468 *** https://bugs.launchpad.net/bugs/1832468 This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1832206 Title: linux-oem: 4.15.0-1041.46 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Testing phase-changed: Tuesday, 11. June 2019 12:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831840] Re: Support new ums-realtek device
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1831840 Title: Support new ums-realtek device Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Cosmic: Incomplete Status in linux-oem source package in Cosmic: Won't Fix Status in linux source package in Disco: Incomplete Status in linux-oem source package in Disco: Won't Fix Bug description: [Impact] Realtek storage device uses usb-storage by default. It works but we should use ums-realtek to bring more functionality, e.g. enabling/disabling MMC card detection. [Fix] Add its device ID to the driver. [Test] After this patch applied, we can use enable_mmc module option to control MMC detection. [Regression Potential] Low. The scope is limited to one device, and the driver is quite stable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1831840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831978] Re: linux-oem: 4.15.0-1040.45 -proposed tracker
*** This bug is a duplicate of bug 1832468 *** https://bugs.launchpad.net/bugs/1832468 This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1831978 Title: linux-oem: 4.15.0-1040.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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Ready for Promote to Proposed phase-changed: Sunday, 09. June 2019 11:32 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/1831978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832299] Re: Add new sound card PCIID into the alsa driver
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1832299 Title: Add new sound card PCIID into the alsa driver Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem source package in Bionic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1832299 The 0001-xxx.patch is for adding the ICL pciid, it is not in the bionic kernel, so bionic kernel needs two patches. The 0002-xxx.patch is in the upstream from v5.2-rc1, it is needed for b/c/d/e. [Impact] We have some cometlake machines, after installing the bionic kernel, the sound can't work at all, we found the sound driver didn't load into the kernel. [Fix] After add the pciid in the pci_driver, the sound driver can be loaded and sound worked well. [Test Case] Boot the system and play sound or record sound, they all worked well [Regression Risk] Low. Adding new pciid, will not change existing functions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1832299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
