[Kernel-packages] [Bug 1781924] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1781924/+attachment/5278472/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in OEM Priority Project: New Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 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 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.
[Kernel-packages] [Bug 1781924] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1781924/+attachment/5278477/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in OEM Priority Project: New Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 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 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2017 dmi.bios.vendor: American Megatrends
[Kernel-packages] [Bug 1781924] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1781924/+attachment/5278479/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in OEM Priority Project: New Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 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 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2017 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1781924] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1781924/+attachment/5278478/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in OEM Priority Project: New Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 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 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bi
[Kernel-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
The missing properties seems to be caused by this error: $ sudo /lib/systemd/systemd-udevd --debug [...] IMPORT 'scsi_id --export --whitelisted -d /dev/sdb' /lib/udev/rules.d/60-persistent-storage.rules:44 starting 'scsi_id --export --whitelisted -d /dev/sdb' Process 'scsi_id --export --whitelisted -d /dev/sdb' failed with exit code 1. The above command was run while running 'modprobe scsi_debug' in another terminal. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1781924] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1781924/+attachment/5278470/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in OEM Priority Project: New Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 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 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.ver
[Kernel-packages] [Bug 1781924] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1781924/+attachment/5278483/+files/UdevDb.txt ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Assignee: (unassigned) => Alex Tu (alextu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1781924 Title: Kernel wrong temperature reporting Status in OEM Priority Project: New Status in linux package in Ubuntu: Expired Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 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 Tags: tara Uname: Linux 4.15.0-24-generic x86_64 UpgradeStatus: No upgra
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
Please try this commit: commit 855b5e01c0732d66c306cdd5215c3337e5311899 Author: Jaroslav Kysela Date: Thu Jun 13 15:09:01 2019 +0200 ALSA: hda/hdmi - consider eld_valid also in sync_eld_via_acomp() In the commit 7f641e26a6df9269cb25dd7a4b0a91d6586ed441 (ALSA: hda/hdmi - Consider eld_valid when reporting jack event) the eld_valid check was added for the jack event reports. Do the same in sync_eld_via_acomp() function. Apparently, it is required for the NVIDIA proprietary driver (monitor presence reported first, but ELD is available later). Let me know if you need a prebuilt kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
I think the quickest way is to do a kernel bisection. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834902] Re: disco/linux: 5.0.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Ready for Testing - phase-changed: Wednesday, 17. July 2019 14:12 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 17:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-hwe: bug 1835388 bionic/linux-oem-osp1: bug 1836856 disco/linux-aws: bug 1834886 disco/linux-azure: bug 1835434 disco/linux-gcp: bug 1834891 disco/linux-kvm: bug 1834892 disco/linux-raspi2: bug 1834884 disco/linux-snapdragon: bug 1834894 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/1834902 Title: disco/linux: 5.0.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Release phase-changed: Monday, 22. July 2019 17:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-hwe: bug 1835388 bionic/linux-oem-osp1: bug 1836856 disco/linux-aws: bug 1834886 disco/linux-azure: bug 1835434 disco/linux-gcp: bug 1834891 disco/linux-kvm: bug 1834892 disco/linux-raspi2: bug 1834884 disco/linux-snapdragon: bug 1834894 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837440] [NEW] linux firmware 1.178.3 seems to break WPA enterprise
Public bug reported: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1837440 Title: linux firmware 1.178.3 seems to break WPA enterprise Status in linux-firmware package in Ubuntu: New Bug description: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1837440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834902] Re: disco/linux: 5.0.0-21.22 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834902 Title: disco/linux: 5.0.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Release phase-changed: Monday, 22. July 2019 17:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-hwe: bug 1835388 bionic/linux-oem-osp1: bug 1836856 disco/linux-aws: bug 1834886 disco/linux-azure: bug 1835434 disco/linux-gcp: bug 1834891 disco/linux-kvm: bug 1834892 disco/linux-raspi2: bug 1834884 disco/linux-snapdragon: bug 1834894 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837397] Re: Make possible to load Mellanox OFED modules
https://lists.ubuntu.com/archives/kernel-team/2019-July/102478.html -- 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/1837397 Title: Make possible to load Mellanox OFED modules Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: In Progress Status in linux-azure source package in Cosmic: In Progress Status in linux-azure source package in Disco: In Progress Bug description: [Impact] Infiniband and Mellanox modules are currently built-in which makes impossible for users to build and load OFED drivers. [Test Case] Users should be able to build and load OFED drivers without conflicting with the built-in drivers. [Regression Potential] The major regression potential is related to the linux-modules or linux-modules-extra packages. The built-in modules should be build as loadable modules and placed at the linux-modules package, having then in the linux-modules-extra package will cause issues for current users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834891] Re: disco/linux-gcp: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge), bug 1836202 (bionic /linux-gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Holding before Release - phase-changed: Monday, 22. July 2019 14:17 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp-edge: bug 1835904 bionic/linux-gke-5.0: bug 1836202 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/1834891 Title: disco/linux-gcp: 5.0.0-1011.11 -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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge), bug 1836202 (bionic /linux-gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Release phase-changed: Monday, 22. July 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-gcp-edge: bug 1835904 bionic/linux-gke-5.0: bug 1836202 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834894] Re: disco/linux-snapdragon: 5.0.0-1017.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Holding before Release - phase-changed: Monday, 22. July 2019 08:57 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy 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/1834894 Title: disco/linux-snapdragon: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Release phase-changed: Monday, 22. July 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834892] Re: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Holding before Release - phase-changed: Monday, 22. July 2019 08:57 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy 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/1834892 Title: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Release phase-changed: Monday, 22. July 2019 17:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834884] Re: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Holding before Release - phase-changed: Monday, 22. July 2019 08:56 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy 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/1834884 Title: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Confirmed Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Release phase-changed: Monday, 22. July 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: disco/linux-aws: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Holding before Release - phase-changed: Monday, 22. July 2019 08:56 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- master bug not ready for release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws-edge: bug 1835782 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/1834886 Title: disco/linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Release phase-changed: Monday, 22. July 2019 17:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws-edge: bug 1835782 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782206] Re: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA)
** Description changed: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages - Upstream target linux 5.3/Qemu-3.10 + Upstream target linux 5.4/Qemu-3.10 Target Release: 19.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782206 Title: KVM enable SnowRidge Accelerator Interfacing Architecture (AIA) Status in linux package in Ubuntu: Incomplete Status in qemu package in Ubuntu: Fix Released Status in xen package in Ubuntu: Incomplete Bug description: CPU core (Tremont) includes Accelerator Interfacing Architecture (AIA) features including: - UMONITOR/UMWAIT: Ring-3 MONITOR/MWAIT with timeout. For memory-based synch with accelerators - TPAUSE: Monitor-less wait (with timeout). For wait-on-multiple or wait-for-interrupt usages - MOVDIRI: 8B streaming doorbell write capability. For streaming accelerator usages. - MOVDIR64B: Non-temporal write with 64B guaranteed write-atomicity. For latency critical accelerator usages Upstream target linux 5.4/Qemu-3.10 Target Release: 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834417] Re: EDAC driver support for Idaville
1dc78f1ffa3a386b986b659884952d816021f38f 5c5d3ac2064ae2466c81d40186bcc09b2d5b7892 c4a1dd9e83ceceef6ffba82b8b274ab9b929ea14 5.3-rc1 ** Changed in: intel Status: New => Fix Committed ** Description changed: Description: Provide detailed memory topology and configuration information as well as translating error addresses to physical DIMM addresses. Target Release: 19.10 - Target Kernel:5.2 + Target Kernel:5.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834417 Title: EDAC driver support for Idaville Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: Provide detailed memory topology and configuration information as well as translating error addresses to physical DIMM addresses. Target Release: 19.10 Target Kernel:5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1834417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835434] Re: disco/linux-azure: 5.0.0-1012.12 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835434 Title: disco/linux-azure: 5.0.0-1012.12 -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: Confirmed 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: Fix Released 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: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835882 (bionic/linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1834902 phase: Ready for Release phase-changed: Monday, 22. July 2019 18:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-azure-edge: bug 1835882 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835434] Re: disco/linux-azure: 5.0.0-1012.12 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835882 (bionic/linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1834902 - phase: Ready for Testing - phase-changed: Wednesday, 10. July 2019 23:36 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 18:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-azure-edge: bug 1835882 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/1835434 Title: disco/linux-azure: 5.0.0-1012.12 -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: Confirmed 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: Fix Released 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: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835882 (bionic/linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1834902 phase: Ready for Release phase-changed: Monday, 22. July 2019 18:09 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-azure-edge: bug 1835882 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835322] Re: [linux-azure] panic in ext4_resize_fs() found during storage testing
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1835322
Title:
[linux-azure] panic in ext4_resize_fs() found during storage testing
Status in linux-azure package in Ubuntu:
Confirmed
Status in linux-azure source package in Xenial:
Fix Committed
Status in linux-azure source package in Cosmic:
Fix Committed
Bug description:
A panic was observed during file system testing. The trace is the
following:
[ 8783.243586] kernel BUG at
/build/linux-azure-3iFJ9j/linux-azure-4.18.0/fs/ext4/resize.c:266!
[ 8783.252751] invalid opcode: [#1] SMP PTI
[ 8783.256735] CPU: 7 PID: 39476 Comm: resize2fs Not tainted
4.18.0-1023-azure #24~18.04.1-Ubuntu
[ 8783.256735] Hardware name: Microsoft Corporation Virtual Machine/Virtual
Machine, BIOS 090007 06/02/2017
[ 8783.256735] RIP: 0010:ext4_resize_fs+0x73b/0xf10
[ 8783.256735] Code: 50 ff ff ff 41 8b 75 10 4d 8b 65 00 85 f6 0f 94 c0 4d 85
e4 0f 94 c1 09 c8 83 bd 5c ff ff ff 01 7e 48 84 c0 0f 84 43 06 00 00 <0f> 0b 48
c7 c2 68 a7 8d 8f 48 c7 c6 00 fb 88 8f 4c 89 f7 e8 0d f8
[ 8783.256735] RSP: 0018:984e8dce7cb0 EFLAGS: 00010202
[ 8783.256735] RAX: 00205c01 RBX: 001f RCX:
[ 8783.256735] RDX: 8b1dbe1367d0 RSI: RDI:
[ 8783.256735] RBP: 984e8dce7d88 R08: 984e8dce7d4c R09:
984e8dce7d54
[ 8783.256735] R10: 0120 R11: 0001 R12:
8b1dbe136800
[ 8783.256735] R13: 8b1d74aefe80 R14: 8b1dbdeb9000 R15:
[ 8783.256735] FS: 7f213fed30c0() GS:8b1ded7c()
knlGS:
[ 8783.256735] CS: 0010 DS: ES: CR0: 80050033
[ 8783.256735] CR2: 556aa08ae9b8 CR3: 001b8e324005 CR4:
003606e0
[ 8783.256735] DR0: DR1: DR2:
[ 8783.256735] DR3: DR6: fffe0ff0 DR7:
0400
[ 8783.256735] Call Trace:
[ 8783.256735] ? security_capable+0x3c/0x60
[ 8783.256735] ext4_ioctl+0xf91/0x14d0
[ 8783.256735] ? audit_filter_rules.constprop.14+0x325/0xf90
[ 8783.256735] ? audit_filter_rules.constprop.14+0x24b/0xf90
[ 8783.256735] do_vfs_ioctl+0xa8/0x630
[ 8783.256735] ksys_ioctl+0x75/0x80
[ 8783.256735] __x64_sys_ioctl+0x1a/0x20
[ 8783.256735] do_syscall_64+0x6a/0x1a0
[ 8783.256735] entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 8783.256735] RIP: 0033:0x7f213f3825d7
[ 8783.256735] Code: b3 66 90 48 8b 05 b1 48 2d 00 64 c7 00 26 00 00 00 48 c7
c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01
f0 ff ff 73 01 c3 48 8b 0d 81 48 2d 00 f7 d8 64 89 01 48
[ 8783.256735] RSP: 002b:7ffe8effd688 EFLAGS: 0246 ORIG_RAX:
0010
[ 8783.256735] RAX: ffda RBX: 556aa08aa980 RCX:
7f213f3825d7
[ 8783.256735] RDX: 7ffe8effd7d0 RSI: 40086610 RDI:
0004
[ 8783.256735] RBP: 0004 R08: R09:
[ 8783.256735] R10: R11: 0246 R12:
556aa08ac980
[ 8783.256735] R13: 7ffe8effd7d0 R14: 556aa08a92d0 R15:
This issue is resolved by the following upstream commit:
f96c3ac8dfc2 ("ext4: fix crash during online resizing")
Commit f96c3ac8dfc2 is in mainline as of v5.1-rc1. This commit was requested
in the upstream stable kernels. However, the Ubuntu kernels are EOL upstream.
Please include this commit in the 16.04 and 18.04 linux-azure kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1835322/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: bionic/linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835436 Title: bionic/linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Confirmed Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Thursday, 18. July 2019 15:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: bionic/linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Thursday, 18. July 2019 15:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress 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/1835436 Title: bionic/linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Confirmed Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Thursday, 18. July 2019 15:08 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Release phase-changed: Monday, 22. July 2019 18:29 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834943] Re: bionic/linux-oracle: 4.15.0-1018.20 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834943 Title: bionic/linux-oracle: 4.15.0-1018.20 -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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Release phase-changed: Monday, 22. July 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-oracle: bug 1834942 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836857] Re: [18.04 FEAT] Enhanced hardware support
Kernel SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2019-July/thread.html#102485 ** Information type changed from Private to Public ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: ubuntu-z-systems Status: Incomplete => 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/1836857 Title: [18.04 FEAT] Enhanced hardware support Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: == [Impact] * Enhanced hardware support for upcoming machine and make sure it can report new CPU capabilities [Fix] * a8fd61688dfad6fdce95fa64cacd8a66595697b8 a8fd616 "s390: report new CPU capabilities" * 142c52d7bce45d335f48d53fdbf428bb15cf3924 142c52d "s390: add alignment hints to vector load and store" [Test Case] * check /proc/cpuinfo in bionic running on upcoming machine - currently only IBM can do that [Regression Potential] * The regression potential can be considered as very low since these changes are limited to arch/s390 * and mainly adds code for the capability to report new features in cpuinfo - in case of running on new hardware [Other Info] * a8fd616 got upstream accepted with 5.2; 142c52d with 5.1 - hence both are already in eoan __ Feature request to apply this to Ubuntu 18.04 in support of new machine. Summary: kernel: report new CPU capabilities Description: Add hardware capability bits and features tags to /proc/cpuinfo for 4 new CPU features: the "Vector-Enhancements Facility 2", the "Vector-Packed-Decimal-Enhancement Facility", the "Enhanced-Sort Facility" and the "Deflate-Conversion Facility" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1836857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Ready for Testing - phase-changed: Thursday, 18. July 2019 14:04 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 18:29 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy 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/1836925 Title: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Release phase-changed: Monday, 22. July 2019 18:29 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837447] [NEW] Backport BTRFS fixes to kernels 4.15 and 5.0
Public bug reported: [Description] In [1] two important fixes in BTRFS are listed: 8e928218780e2f1cf2f5891c7575e8f0b284fcce "btrfs: fix corruption reading shared and compressed extents after hole punching" 4ea748e1d2c9f8a27332b949e8210dbbf392987e "btrfs: fix deadlock between clone/dedupe and rename" Both of them were backported to stable kernels like 4.14.x and newer 5.0 releases, but both are missisng in Ubuntu's 4.15.0 and 5.0.0. [Impact] Possible data corruption. [Solution] Cherry-pick those commits to supported kernels. [1] https://github.com/Zygo/bees/blob/master/docs/btrfs-kernel.md ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco package-from-proposed ** Description changed: [Description] In [1] two important fixes in BTRFS are listed: 8e928218780e2f1cf2f5891c7575e8f0b284fcce "btrfs: fix corruption reading shared and compressed extents after hole punching" 4ea748e1d2c9f8a27332b949e8210dbbf392987e "btrfs: fix deadlock between clone/dedupe and rename" Both of them were backported to stable kernels like 4.14.x and newer 5.0 releases, but both are missisng in Ubuntu's 4.15.0 and 5.0.0. [Impact] Possible data corruption. [Solution] Cherry-pick those commits to supported kernels. [1] https://github.com/Zygo/bees/blob/master/docs/btrfs-kernel.md - - ProblemType: Bug - DistroRelease: Ubuntu 19.04 - Package: linux-image-generic 5.0.0.21.22 - ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 - Uname: Linux 5.0.0-21-generic x86_64 - ApportVersion: 2.20.10-0ubuntu27.1 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: user 2792 F pulseaudio - /dev/snd/controlC2: user 2792 F pulseaudio - /dev/snd/pcmC2D0p: user 2792 F...m pulseaudio - /dev/snd/controlC0: user 2792 F pulseaudio - CurrentDesktop: XFCE - Date: Mon Jul 22 21:27:47 2019 - HibernationDevice: #RESUME=UUID=0bc1a657-82ca-4015-971a-8c255c7889a9 - InstallationDate: Installed on 2017-08-28 (693 days ago) - InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) - MachineType: ASUS All Series - ProcFB: 0 radeondrmfb - ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-21-generic root=UUID=745b0c43-6a82-4bce-9821-7f5dd88a9246 ro rootflags=subvol=@ resume=UUID=133b8284-7ef8-4010-b2ea-b524bddea7e0 - RelatedPackageVersions: - linux-restricted-modules-5.0.0-21-generic N/A - linux-backports-modules-5.0.0-21-generic N/A - linux-firmware1.178.4 - RfKill: - - SourcePackage: linux - UpgradeStatus: Upgraded to disco on 2018-02-08 (529 days ago) - dmi.bios.date: 03/10/2016 - dmi.bios.vendor: American Megatrends Inc. - dmi.bios.version: 0801 - dmi.board.asset.tag: To be filled by O.E.M. - dmi.board.name: AM1I-A - dmi.board.vendor: ASUSTeK COMPUTER INC. - dmi.board.version: Rev X.0x - dmi.chassis.asset.tag: Asset-1234567890 - dmi.chassis.type: 3 - dmi.chassis.vendor: Chassis Manufacture - dmi.chassis.version: Chassis Version - dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd03/10/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1I-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: - dmi.product.family: ASUS MB - dmi.product.name: All Series - dmi.product.sku: All - dmi.product.version: System Version - dmi.sys.vendor: ASUS - modified.conffile..etc.default.apport: [modified] - mtime.conffile..etc.default.apport: 2018-07-03T12:21:32.224223 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837447 Title: Backport BTRFS fixes to kernels 4.15 and 5.0 Status in linux package in Ubuntu: New Bug description: [Description] In [1] two important fixes in BTRFS are listed: 8e928218780e2f1cf2f5891c7575e8f0b284fcce "btrfs: fix corruption reading shared and compressed extents after hole punching" 4ea748e1d2c9f8a27332b949e8210dbbf392987e "btrfs: fix deadlock between clone/dedupe and rename" Both of them were backported to stable kernels like 4.14.x and newer 5.0 releases, but both are missisng in Ubuntu's 4.15.0 and 5.0.0. [Impact] Possible data corruption. [Solution] Cherry-pick those commits to supported kernels. [1] https://github.com/Zygo/bees/blob/master/docs/btrfs-kernel.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834943] Re: bionic/linux-oracle: 4.15.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-bionic ** Tags removed: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Ready for Testing - phase-changed: Wednesday, 10. July 2019 23:42 UTC + phase: Ready for Release + phase-changed: Monday, 22. July 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Pending -- ready to copy trackers: xenial/linux-oracle: bug 1834942 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/1834943 Title: bionic/linux-oracle: 4.15.0-1018.20 -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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Release phase-changed: Monday, 22. July 2019 18:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-oracle: bug 1834942 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837440] Re: linux firmware 1.178.3 seems to break WPA enterprise
There haven't been any updates to the firmware for your wireless hardware since 1.178, so it seems unlikely that the linux-firmware update would be responsible. Let's see how your testing turns out though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1837440 Title: linux firmware 1.178.3 seems to break WPA enterprise Status in linux-firmware package in Ubuntu: New Bug description: Seen on intel Wireless-N 2230 BGN (rev c4). After the update to said linux firmware version I had issues in connecting to the WPA enterprise wifi networks EDUROAM and ALMAWIFI. EDUROAM is the European universities Wi-Fi network. Ability to connect to non enterprise network is unaffected. Downgrading to 1.178 seems to restore proper functionality. In the next days I'll try further checks to see if the firmware is really the sole trigger for the issue. In the meantime, I am tentatively opening the bug in case others have my same issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-firmware 1.178 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jul 22 19:27:16 2019 Dependencies: EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-12 (2047 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to disco on 2019-06-12 (40 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1837440/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837447] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837447 Title: Backport BTRFS fixes to kernels 4.15 and 5.0 Status in linux package in Ubuntu: Confirmed Bug description: [Description] In [1] two important fixes in BTRFS are listed: 8e928218780e2f1cf2f5891c7575e8f0b284fcce "btrfs: fix corruption reading shared and compressed extents after hole punching" 4ea748e1d2c9f8a27332b949e8210dbbf392987e "btrfs: fix deadlock between clone/dedupe and rename" Both of them were backported to stable kernels like 4.14.x and newer 5.0 releases, but both are missisng in Ubuntu's 4.15.0 and 5.0.0. [Impact] Possible data corruption. [Solution] Cherry-pick those commits to supported kernels. [1] https://github.com/Zygo/bees/blob/master/docs/btrfs-kernel.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
How to do that? I would need a guide. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash
Oh https://wiki.ubuntu.com/Kernel/KernelBisection You mean I should install a specific previous version? Which version do you want to get tested? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1818974 Title: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE. Since kernel 4.18 sometimes while waking up from standby my user session crash. I assume that my attached external USB to SATA HDD could be cause this kernel bug. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin27966 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a InstallationDate: Installed on 2018-07-21 (228 days ago) InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626 MachineType: LENOVO 20FXS05500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs noibpb l1tf=off vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-16-generic N/A linux-backports-modules-4.18.0-16-generic N/A linux-firmware 1.173.3 Tags: tessa Uname: Linux 4.18.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo _MarkForUpload: True dmi.bios.date: 09/27/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET87W (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FXS05500 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FXS05500 dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827790] Re: Dell XPS 13 9380 - Screen brightness flashes
So it seems that it does away with the following kernel option: i915.enable_psr=0 It seems from some Dell user forum that some have had the same issues on Windows and disabling the panel self refresh worked for them so I was searching along these lines. I'm certain it's not a "clean" fix however to deactivate a measure that's suppose to save battery. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1827790 Title: Dell XPS 13 9380 - Screen brightness flashes Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have a new 2019 Dell XPS 13 (9380). I ordered the official Ubuntu edition from Dell which came with 18.04, but I've since wiped it and installed 19.04 from a fresh ISO download. This is the non-touch non- 4K version (13-inch 1080p). Every so often (maybe a couple of times per minute), the screen flashes brighter, as if the brightness has been turned up momentarily and then back down again. I previously had an issue with the brightness / colours changing slightly when I opened menus or if the screen content changed slightly, but I fixed that by disabling Dynamic Brightness in the BIOS. It is definitely a better experience with that turned off. However the screen flashing still persists. I booted a live image of Fedora 30 now that it has been released, and so far I have not seen the screen flashing, so I do not think the hardware is faulty. I ran apport-bug, so hopefully the collected information has been attached. Thank you. 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 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 5 15:59:45 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-28 (6 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=fcb75d61-4e46-4391-8800-ccef7ff04f70 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 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/gnome-settings-daemon/+bug/1827790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806343] Re: FN+F3/F4 does not modify keyboard backlight brightness.
Hi, for me all fn combs work except keyboard backlight, I'm on an Asus ROG. For me there are both 'kbd_backlight' and 'kbd_backlight_1' in sys/class/leds/asus::<...>. I can also manually adjust 'sys/class/leds/asus::kbd_backlight_1/brightness' which effectively toggles the light. The Fn combinations do show a successful animation and appear to succesfully toggle the value in 'sys/class/leds/asus::kbd_backlight/brightness'. It seems like the '_1' addition is not uniformly anticipated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806343 Title: FN+F3/F4 does not modify keyboard backlight brightness. Status in linux package in Ubuntu: Confirmed Bug description: acpi_listen does not output anything to terminal when pressing key combination. Keyboard backlight has worked on older versions (I believe 18.04 or earlier.) I can manually toggle with: echo 0 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 1 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 2 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness echo 3 | sudo tee --append /sys/class/leds/asus\:\:kbd_backlight_1/brightness for varying degrees of brightness. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Tags: disco Uname: Linux 4.19.6-041906-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: duck 3632 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2018-11-28 (22 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181128) MachineType: ASUSTeK COMPUTER INC. GL502VMK NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/vg0-root ro quiet splash acpi_osi= acpi_backlight=native vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 Tags: disco Uname: Linux 4.18.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL502VMK.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL502VMK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL502VMK.305:bd07/03/2017:svnASUSTeKCOMPUTERINC.:pnGL502VMK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL502VMK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL502VMK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806343/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: bionic/linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Ready for Testing - phase-changed: Thursday, 18. July 2019 15:08 UTC + phase: Signoff + phase-changed: Monday, 22. July 2019 19:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835436 Title: bionic/linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Monday, 22. July 2019 19:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: bionic/linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835436 Title: bionic/linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Monday, 22. July 2019 19:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
I still need to verify this for the SRUs. There are no - up to now - regressions being showed in excuses for Disco and/or Bionic. Will provide verification soon. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
** Package changed: linux-signed (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15:13:31 Lappy kernel: [ 85.320173] iwlwifi :3b:00.0: 0x1000 | data2 Jul 17 15:13:31 Lappy kernel: [ 85.320174] iwlwifi :3b:00.0: 0xE008 | data3 Jul 17 15:13
[Kernel-packages] [Bug 1834902] Re: disco/linux: 5.0.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834902 Title: disco/linux: 5.0.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Release phase-changed: Monday, 22. July 2019 20:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-hwe: bug 1835388 bionic/linux-oem-osp1: bug 1836856 disco/linux-aws: bug 1834886 disco/linux-azure: bug 1835434 disco/linux-gcp: bug 1834891 disco/linux-kvm: bug 1834892 disco/linux-raspi2: bug 1834884 disco/linux-snapdragon: bug 1834894 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836910] Re: br_netfilter: namespace sysctl operations
** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Connor Kuehl (connork) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Connor Kuehl (connork) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836910 Title: br_netfilter: namespace sysctl operations Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Bug description: SRU Justification Impact: Currently, the /proc/sys/net/bridge folder is only created in the initial network namespace. This blocks use-cases where users would like to e.g. not do bridge filtering for bridges in a specific network namespace while doing so for bridges located in another network namespace. Fix: The patches linked below ensure that the /proc/sys/net/bridge folder is available in each network namespace if the module is loaded and disappears from all network namespaces when the module is unloaded. In doing so the patch makes the sysctls: bridge-nf-call-arptables bridge-nf-call-ip6tables bridge-nf-call-iptables bridge-nf-filter-pppoe-tagged bridge-nf-filter-vlan-tagged bridge-nf-pass-vlan-input-dev apply per network namespace. Regression Potential: None, since this didn't use to work before. Otherwise limited to the br_netfilter module. The netfilter rules are afaict already per network namespace so it should be safe for users to specify whether bridge devices inside a network namespace are supposed to go through iptables et al. or not. Also, this can already be done per-bridge by setting an option for each individual bridge via Netlink. It should also be possible to do this for all bridges in a network namespace via sysctls. Test Case: Tested with LXD on a kernel with the patches applied and per-network namespace iptables. Target Kernels: All LTS kernels starting from 4.15. Kernel 5.3 has the patchset upstream. Patches: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff6d090d0db41425aef0cfe5dc58bb3cc12514a2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=22567590b2e634247931b3d2351384ba45720ebe https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7e6daf50e1f4ea0ecd56406beb64ffc66e1e94db To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: disco/linux-aws: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834886 Title: disco/linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:25 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-aws-edge: bug 1835782 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: disco/linux-aws: 5.0.0-1011.12 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Ready for Release - phase-changed: Monday, 22. July 2019 17:41 UTC + phase: Release + phase-changed: Monday, 22. July 2019 20:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-aws-edge: bug 1835782 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/1834886 Title: disco/linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:25 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-aws-edge: bug 1835782 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: disco/linux-aws: 5.0.0-1011.12 -proposed tracker
This bug was fixed in the package linux-aws - 5.0.0-1011.12 --- linux-aws (5.0.0-1011.12) disco; urgency=medium * linux-aws: 5.0.0-1011.12 -proposed tracker (LP: #1834886) * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - [Config] aws: update configs for ASIX rename [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when offsets are used - platform/x86: pmc_atom: Drop __initconst on dmi table - NFSv4.1 fix incorrect return value in copy_file_range - perf/core: Fix perf_event_disable_inatomic() race - genirq: Prevent use-after-free and work list corruption - usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON - usb: dwc3: Fix default lpm_nyet_threshold value - USB: serial: f81232: fix int
[Kernel-packages] [Bug 1834891] Re: disco/linux-gcp: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834891 Title: disco/linux-gcp: 5.0.0-1011.11 -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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge), bug 1836202 (bionic /linux-gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:30 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp-edge: bug 1835904 bionic/linux-gke-5.0: bug 1836202 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834902] Re: disco/linux: 5.0.0-21.22 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Ready for Release - phase-changed: Monday, 22. July 2019 17:38 UTC + phase: Release + phase-changed: Monday, 22. July 2019 20:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-hwe: bug 1835388 bionic/linux-oem-osp1: bug 1836856 disco/linux-aws: bug 1834886 disco/linux-azure: bug 1835434 disco/linux-gcp: bug 1834891 disco/linux-kvm: bug 1834892 disco/linux-raspi2: bug 1834884 disco/linux-snapdragon: bug 1834894 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/1834902 Title: disco/linux: 5.0.0-21.22 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835388 (bionic/linux-hwe), bug 1836856 (bionic/linux-oem-osp1) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Release phase-changed: Monday, 22. July 2019 20:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-hwe: bug 1835388 bionic/linux-oem-osp1: bug 1836856 disco/linux-aws: bug 1834886 disco/linux-azure: bug 1835434 disco/linux-gcp: bug 1834891 disco/linux-kvm: bug 1834892 disco/linux-raspi2: bug 1834884 disco/linux-snapdragon: bug 1834894 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834884] Re: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834884 Title: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in 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: 1834902 phase: Release phase-changed: Monday, 22. July 2019 20:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834908] Re: xenial/linux-aws: 4.4.0-1088.99 -proposed tracker
** Tags added: regression-testing-passed -- 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/1834908 Title: xenial/linux-aws: 4.4.0-1088.99 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834907 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Release phase-changed: Monday, 22. July 2019 20:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834908] Re: xenial/linux-aws: 4.4.0-1088.99 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834907 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 - phase: Ready for Testing - phase-changed: Wednesday, 10. July 2019 23:38 UTC + phase: Holding before Release + phase-changed: Monday, 22. July 2019 20:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- master bug not ready for release 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/1834908 Title: xenial/linux-aws: 4.4.0-1088.99 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834907 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1836880 phase: Holding before Release phase-changed: Monday, 22. July 2019 20:19 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834884] Re: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Ready for Release - phase-changed: Monday, 22. July 2019 17:41 UTC + phase: Release + phase-changed: Monday, 22. July 2019 20:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published 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/1834884 Title: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: In Progress Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in 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: 1834902 phase: Release phase-changed: Monday, 22. July 2019 20:20 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi
This bug was fixed in the package linux-raspi2 - 5.0.0-1013.13 --- linux-raspi2 (5.0.0-1013.13) disco; urgency=medium * linux-raspi2: 5.0.0-1013.13 -proposed tracker (LP: #1834884) * [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88 (LP: #1831828) - raspi2: [Config] Add realtek wifi RTW88 support * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - raspi2: [Config] Rename ASIX module * Load average inexplicably high with 5.0 kernel on rpi (LP: #1825235) // Refresh RaspberryPi BSP (LP: #1831219) - raspberrypi: remove the old RaspberryPi BSP - arm: partially revert 702b94bff3c50542a6e4ab9a4f4cef093262fe65 - Revert "rtc: pcf8523: properly handle oscillator stop bit" - smsx95xx: fix crimes against truesize - smsc95xx: Experimental: Enable turbo_mode and packetsize=2560 by default - Allow mac address to be set in smsc95xx - Protect __release_resource against resources without parents - irq-bcm2836: Prevent spurious interrupts, and trap them early - irq-bcm2836: Avoid "Invalid trigger warning" - irqchip: bcm2835: Add FIQ support - irqchip: irq-bcm2835: Add 2836 FIQ support - spi: spidev: Completely disable the spidev warning - dmaengine: bcm2835: Load driver early and support legacy API - firmware: Updated mailbox header - rtc: Add SPI alias for pcf2123 driver - watchdog: bcm2835: Support setting reboot partition - reboot: Use power off rather than busy spinning when halt is requested - bcm: Make RASPBERRYPI_POWER depend on PM - Register the clocks early during the boot process, so that special/critical clocks can get enabled early on in the boot process avoiding the risk of disabling a clock, pll_divider or pll when a claiming driver fails to install propperly - maybe it needs to defer. - bcm2835-rng: Avoid initialising if already enabled - clk-bcm2835: Mark used PLLs and dividers CRITICAL - clk-bcm2835: Add claim-clocks property - clk-bcm2835: Read max core clock from firmware - clk: bcm2835: Mark GPIO clocks enabled at boot as critical. - sound: Demote deferral errors to INFO level - Update vfpmodule.c - i2c: bcm2835: Add debug support - mm: Remove the PFN busy warning - ASoC: Add prompt for ICS43432 codec - irqchip: irq-bcm2836: Remove regmap and syscon use - lan78xx: Enable LEDs and auto-negotiation - amba_pl011: Don't use DT aliases for numbering - amba_pl011: Round input clock up - amba_pl011: Insert mb() for correct FIFO handling - amba_pl011: Add cts-event-workaround DT property - pinctrl-bcm2835: Set base to 0 give expected gpio numbering - Main bcm2708/bcm2709 linux port - Add dwc_otg driver - bcm2708 framebuffer driver - fbdev: add FBIOCOPYAREA ioctl - Speed up console framebuffer imageblit function - dmaengine: Add support for BCM2708 - MMC: added alternative MMC driver - Adding bcm2835-sdhost driver, and an overlay to enable it - vc_mem: Add vc_mem driver for querying firmware memory addresses - vcsm: VideoCore shared memory service for BCM2835 - Add /dev/gpiomem device for rootless user GPIO access - Add SMI driver - MISC: bcm2835: smi: use clock manager and fix reload issues - Add SMI NAND driver - Revert "Add SMI NAND driver" - Add cpufreq driver - Add Chris Boot's i2c driver - char: broadcom: Add vcio module - firmware: bcm2835: Support ARCH_BCM270x - scripts: Add mkknlimg and knlinfo scripts from tools repo - BCM2708: Add core Device Tree support - BCM270x_DT: Add pwr_led, and the required "input" trigger - Added Device IDs for August DVB-T 205 - Improve __copy_to_user and __copy_from_user performance - gpio-poweroff: Allow it to work on Raspberry Pi - mfd: Add Raspberry Pi Sense HAT core driver - ASoC: pcm512x: implement set_tdm_slot interface - ASoC: Add support for Rpi-DAC - Add IQaudIO Sound Card support for Raspberry Pi - Added support for HiFiBerry DAC+ - Added driver for HiFiBerry Amp amplifier add-on board - Add driver for rpi-proto - Add Support for JustBoom Audio boards - New AudioInjector.net Pi soundcard with low jitter audio in and out. - New driver for RRA DigiDAC1 soundcard using WM8741 + WM8804 - Add support for Dion Audio LOCO DAC-AMP HAT - Allo Piano DAC boards: Initial 2 channel (stereo) support (#1645 - Add support for Allo Piano DAC 2.1 plus add-on board for Raspberry Pi. - Add support for Allo Boss DAC add-on board for Raspberry Pi. (#1924 - Support for Blokas Labs pisound board - ASoC: Add driver for Cirrus Logic Audio Card - sound: Support for Dion Audio LOCO-V2 DAC-AMP HAT - Add support for Fe-Pi audio sound card. (#1867 - Add support for the AudioInjector.net Octo sound card - Driver support for Google voiceHAT soundcard. - Driver and overlay for Allo Katana DAC - ASoC
[Kernel-packages] [Bug 1834476] Re: Add nvidia-418 dkms build support to disco
This bug was fixed in the package linux-restricted-modules - 5.0.0-21.22 --- linux-restricted-modules (5.0.0-21.22) disco; urgency=medium * Master version: 5.0.0-21.22 * Add nvidia-418 dkms build support to disco (LP: #1834476) - add support for nvidia-418 * Miscellaneous Ubuntu changes - debian/dkms-versions -- update from master - debian/scripts/dkms-build--nvidia-N -- update from master -- Stefan Bader Tue, 02 Jul 2019 15:11:36 +0200 ** Changed in: linux-restricted-modules (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1834476 Title: Add nvidia-418 dkms build support to disco Status in linux package in Ubuntu: Fix Committed Status in linux-restricted-modules package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-restricted-modules source package in Disco: Fix Released Bug description: SRU Justification Impact: The nvidia-graphics-drivers-418 package landed in disco shortly before release and was not included in linux-restricted- modules, though it is wanted there. Fix: Update the linux and linux-restricted-modules packages to include nvidia-graphics-drivers-418. Test Case: Confirm that binary packages for nvidia-418 are built and function as expected, and confirm that nvidia-390 continue to work as before. A test build is available in ppa:sforshee/test-builds. Regression Potential: The nvidia-418 packages are new binary packages which must be installed by the user, so they cannot cause regressions. There is a risk of inadvertent errors affecting the nvidia-390 packages, however regression testing has turned up no such regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834884] Re: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker
This bug was fixed in the package linux-raspi2 - 5.0.0-1013.13 --- linux-raspi2 (5.0.0-1013.13) disco; urgency=medium * linux-raspi2: 5.0.0-1013.13 -proposed tracker (LP: #1834884) * [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88 (LP: #1831828) - raspi2: [Config] Add realtek wifi RTW88 support * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - raspi2: [Config] Rename ASIX module * Load average inexplicably high with 5.0 kernel on rpi (LP: #1825235) // Refresh RaspberryPi BSP (LP: #1831219) - raspberrypi: remove the old RaspberryPi BSP - arm: partially revert 702b94bff3c50542a6e4ab9a4f4cef093262fe65 - Revert "rtc: pcf8523: properly handle oscillator stop bit" - smsx95xx: fix crimes against truesize - smsc95xx: Experimental: Enable turbo_mode and packetsize=2560 by default - Allow mac address to be set in smsc95xx - Protect __release_resource against resources without parents - irq-bcm2836: Prevent spurious interrupts, and trap them early - irq-bcm2836: Avoid "Invalid trigger warning" - irqchip: bcm2835: Add FIQ support - irqchip: irq-bcm2835: Add 2836 FIQ support - spi: spidev: Completely disable the spidev warning - dmaengine: bcm2835: Load driver early and support legacy API - firmware: Updated mailbox header - rtc: Add SPI alias for pcf2123 driver - watchdog: bcm2835: Support setting reboot partition - reboot: Use power off rather than busy spinning when halt is requested - bcm: Make RASPBERRYPI_POWER depend on PM - Register the clocks early during the boot process, so that special/critical clocks can get enabled early on in the boot process avoiding the risk of disabling a clock, pll_divider or pll when a claiming driver fails to install propperly - maybe it needs to defer. - bcm2835-rng: Avoid initialising if already enabled - clk-bcm2835: Mark used PLLs and dividers CRITICAL - clk-bcm2835: Add claim-clocks property - clk-bcm2835: Read max core clock from firmware - clk: bcm2835: Mark GPIO clocks enabled at boot as critical. - sound: Demote deferral errors to INFO level - Update vfpmodule.c - i2c: bcm2835: Add debug support - mm: Remove the PFN busy warning - ASoC: Add prompt for ICS43432 codec - irqchip: irq-bcm2836: Remove regmap and syscon use - lan78xx: Enable LEDs and auto-negotiation - amba_pl011: Don't use DT aliases for numbering - amba_pl011: Round input clock up - amba_pl011: Insert mb() for correct FIFO handling - amba_pl011: Add cts-event-workaround DT property - pinctrl-bcm2835: Set base to 0 give expected gpio numbering - Main bcm2708/bcm2709 linux port - Add dwc_otg driver - bcm2708 framebuffer driver - fbdev: add FBIOCOPYAREA ioctl - Speed up console framebuffer imageblit function - dmaengine: Add support for BCM2708 - MMC: added alternative MMC driver - Adding bcm2835-sdhost driver, and an overlay to enable it - vc_mem: Add vc_mem driver for querying firmware memory addresses - vcsm: VideoCore shared memory service for BCM2835 - Add /dev/gpiomem device for rootless user GPIO access - Add SMI driver - MISC: bcm2835: smi: use clock manager and fix reload issues - Add SMI NAND driver - Revert "Add SMI NAND driver" - Add cpufreq driver - Add Chris Boot's i2c driver - char: broadcom: Add vcio module - firmware: bcm2835: Support ARCH_BCM270x - scripts: Add mkknlimg and knlinfo scripts from tools repo - BCM2708: Add core Device Tree support - BCM270x_DT: Add pwr_led, and the required "input" trigger - Added Device IDs for August DVB-T 205 - Improve __copy_to_user and __copy_from_user performance - gpio-poweroff: Allow it to work on Raspberry Pi - mfd: Add Raspberry Pi Sense HAT core driver - ASoC: pcm512x: implement set_tdm_slot interface - ASoC: Add support for Rpi-DAC - Add IQaudIO Sound Card support for Raspberry Pi - Added support for HiFiBerry DAC+ - Added driver for HiFiBerry Amp amplifier add-on board - Add driver for rpi-proto - Add Support for JustBoom Audio boards - New AudioInjector.net Pi soundcard with low jitter audio in and out. - New driver for RRA DigiDAC1 soundcard using WM8741 + WM8804 - Add support for Dion Audio LOCO DAC-AMP HAT - Allo Piano DAC boards: Initial 2 channel (stereo) support (#1645 - Add support for Allo Piano DAC 2.1 plus add-on board for Raspberry Pi. - Add support for Allo Boss DAC add-on board for Raspberry Pi. (#1924 - Support for Blokas Labs pisound board - ASoC: Add driver for Cirrus Logic Audio Card - sound: Support for Dion Audio LOCO-V2 DAC-AMP HAT - Add support for Fe-Pi audio sound card. (#1867 - Add support for the AudioInjector.net Octo sound card - Driver support for Google voiceHAT soundcard. - Driver and overlay for Allo Katana DAC - ASoC
[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to build on disco
This bug was fixed in the package linux-aws - 5.0.0-1011.12 --- linux-aws (5.0.0-1011.12) disco; urgency=medium * linux-aws: 5.0.0-1011.12 -proposed tracker (LP: #1834886) * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - [Config] aws: update configs for ASIX rename [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when offsets are used - platform/x86: pmc_atom: Drop __initconst on dmi table - NFSv4.1 fix incorrect return value in copy_file_range - perf/core: Fix perf_event_disable_inatomic() race - genirq: Prevent use-after-free and work list corruption - usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON - usb: dwc3: Fix default lpm_nyet_threshold value - USB: serial: f81232: fix int
[Kernel-packages] [Bug 1827750] Re: Not boot with EFI
This bug was fixed in the package linux-raspi2 - 5.0.0-1013.13 --- linux-raspi2 (5.0.0-1013.13) disco; urgency=medium * linux-raspi2: 5.0.0-1013.13 -proposed tracker (LP: #1834884) * [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88 (LP: #1831828) - raspi2: [Config] Add realtek wifi RTW88 support * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - raspi2: [Config] Rename ASIX module * Load average inexplicably high with 5.0 kernel on rpi (LP: #1825235) // Refresh RaspberryPi BSP (LP: #1831219) - raspberrypi: remove the old RaspberryPi BSP - arm: partially revert 702b94bff3c50542a6e4ab9a4f4cef093262fe65 - Revert "rtc: pcf8523: properly handle oscillator stop bit" - smsx95xx: fix crimes against truesize - smsc95xx: Experimental: Enable turbo_mode and packetsize=2560 by default - Allow mac address to be set in smsc95xx - Protect __release_resource against resources without parents - irq-bcm2836: Prevent spurious interrupts, and trap them early - irq-bcm2836: Avoid "Invalid trigger warning" - irqchip: bcm2835: Add FIQ support - irqchip: irq-bcm2835: Add 2836 FIQ support - spi: spidev: Completely disable the spidev warning - dmaengine: bcm2835: Load driver early and support legacy API - firmware: Updated mailbox header - rtc: Add SPI alias for pcf2123 driver - watchdog: bcm2835: Support setting reboot partition - reboot: Use power off rather than busy spinning when halt is requested - bcm: Make RASPBERRYPI_POWER depend on PM - Register the clocks early during the boot process, so that special/critical clocks can get enabled early on in the boot process avoiding the risk of disabling a clock, pll_divider or pll when a claiming driver fails to install propperly - maybe it needs to defer. - bcm2835-rng: Avoid initialising if already enabled - clk-bcm2835: Mark used PLLs and dividers CRITICAL - clk-bcm2835: Add claim-clocks property - clk-bcm2835: Read max core clock from firmware - clk: bcm2835: Mark GPIO clocks enabled at boot as critical. - sound: Demote deferral errors to INFO level - Update vfpmodule.c - i2c: bcm2835: Add debug support - mm: Remove the PFN busy warning - ASoC: Add prompt for ICS43432 codec - irqchip: irq-bcm2836: Remove regmap and syscon use - lan78xx: Enable LEDs and auto-negotiation - amba_pl011: Don't use DT aliases for numbering - amba_pl011: Round input clock up - amba_pl011: Insert mb() for correct FIFO handling - amba_pl011: Add cts-event-workaround DT property - pinctrl-bcm2835: Set base to 0 give expected gpio numbering - Main bcm2708/bcm2709 linux port - Add dwc_otg driver - bcm2708 framebuffer driver - fbdev: add FBIOCOPYAREA ioctl - Speed up console framebuffer imageblit function - dmaengine: Add support for BCM2708 - MMC: added alternative MMC driver - Adding bcm2835-sdhost driver, and an overlay to enable it - vc_mem: Add vc_mem driver for querying firmware memory addresses - vcsm: VideoCore shared memory service for BCM2835 - Add /dev/gpiomem device for rootless user GPIO access - Add SMI driver - MISC: bcm2835: smi: use clock manager and fix reload issues - Add SMI NAND driver - Revert "Add SMI NAND driver" - Add cpufreq driver - Add Chris Boot's i2c driver - char: broadcom: Add vcio module - firmware: bcm2835: Support ARCH_BCM270x - scripts: Add mkknlimg and knlinfo scripts from tools repo - BCM2708: Add core Device Tree support - BCM270x_DT: Add pwr_led, and the required "input" trigger - Added Device IDs for August DVB-T 205 - Improve __copy_to_user and __copy_from_user performance - gpio-poweroff: Allow it to work on Raspberry Pi - mfd: Add Raspberry Pi Sense HAT core driver - ASoC: pcm512x: implement set_tdm_slot interface - ASoC: Add support for Rpi-DAC - Add IQaudIO Sound Card support for Raspberry Pi - Added support for HiFiBerry DAC+ - Added driver for HiFiBerry Amp amplifier add-on board - Add driver for rpi-proto - Add Support for JustBoom Audio boards - New AudioInjector.net Pi soundcard with low jitter audio in and out. - New driver for RRA DigiDAC1 soundcard using WM8741 + WM8804 - Add support for Dion Audio LOCO DAC-AMP HAT - Allo Piano DAC boards: Initial 2 channel (stereo) support (#1645 - Add support for Allo Piano DAC 2.1 plus add-on board for Raspberry Pi. - Add support for Allo Boss DAC add-on board for Raspberry Pi. (#1924 - Support for Blokas Labs pisound board - ASoC: Add driver for Cirrus Logic Audio Card - sound: Support for Dion Audio LOCO-V2 DAC-AMP HAT - Add support for Fe-Pi audio sound card. (#1867 - Add support for the AudioInjector.net Octo sound card - Driver support for Google voiceHAT soundcard. - Driver and overlay for Allo Katana DAC - ASoC
[Kernel-packages] [Bug 1831219] Re: Refresh RaspberryPi BSP
This bug was fixed in the package linux-raspi2 - 5.0.0-1013.13 --- linux-raspi2 (5.0.0-1013.13) disco; urgency=medium * linux-raspi2: 5.0.0-1013.13 -proposed tracker (LP: #1834884) * [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88 (LP: #1831828) - raspi2: [Config] Add realtek wifi RTW88 support * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - raspi2: [Config] Rename ASIX module * Load average inexplicably high with 5.0 kernel on rpi (LP: #1825235) // Refresh RaspberryPi BSP (LP: #1831219) - raspberrypi: remove the old RaspberryPi BSP - arm: partially revert 702b94bff3c50542a6e4ab9a4f4cef093262fe65 - Revert "rtc: pcf8523: properly handle oscillator stop bit" - smsx95xx: fix crimes against truesize - smsc95xx: Experimental: Enable turbo_mode and packetsize=2560 by default - Allow mac address to be set in smsc95xx - Protect __release_resource against resources without parents - irq-bcm2836: Prevent spurious interrupts, and trap them early - irq-bcm2836: Avoid "Invalid trigger warning" - irqchip: bcm2835: Add FIQ support - irqchip: irq-bcm2835: Add 2836 FIQ support - spi: spidev: Completely disable the spidev warning - dmaengine: bcm2835: Load driver early and support legacy API - firmware: Updated mailbox header - rtc: Add SPI alias for pcf2123 driver - watchdog: bcm2835: Support setting reboot partition - reboot: Use power off rather than busy spinning when halt is requested - bcm: Make RASPBERRYPI_POWER depend on PM - Register the clocks early during the boot process, so that special/critical clocks can get enabled early on in the boot process avoiding the risk of disabling a clock, pll_divider or pll when a claiming driver fails to install propperly - maybe it needs to defer. - bcm2835-rng: Avoid initialising if already enabled - clk-bcm2835: Mark used PLLs and dividers CRITICAL - clk-bcm2835: Add claim-clocks property - clk-bcm2835: Read max core clock from firmware - clk: bcm2835: Mark GPIO clocks enabled at boot as critical. - sound: Demote deferral errors to INFO level - Update vfpmodule.c - i2c: bcm2835: Add debug support - mm: Remove the PFN busy warning - ASoC: Add prompt for ICS43432 codec - irqchip: irq-bcm2836: Remove regmap and syscon use - lan78xx: Enable LEDs and auto-negotiation - amba_pl011: Don't use DT aliases for numbering - amba_pl011: Round input clock up - amba_pl011: Insert mb() for correct FIFO handling - amba_pl011: Add cts-event-workaround DT property - pinctrl-bcm2835: Set base to 0 give expected gpio numbering - Main bcm2708/bcm2709 linux port - Add dwc_otg driver - bcm2708 framebuffer driver - fbdev: add FBIOCOPYAREA ioctl - Speed up console framebuffer imageblit function - dmaengine: Add support for BCM2708 - MMC: added alternative MMC driver - Adding bcm2835-sdhost driver, and an overlay to enable it - vc_mem: Add vc_mem driver for querying firmware memory addresses - vcsm: VideoCore shared memory service for BCM2835 - Add /dev/gpiomem device for rootless user GPIO access - Add SMI driver - MISC: bcm2835: smi: use clock manager and fix reload issues - Add SMI NAND driver - Revert "Add SMI NAND driver" - Add cpufreq driver - Add Chris Boot's i2c driver - char: broadcom: Add vcio module - firmware: bcm2835: Support ARCH_BCM270x - scripts: Add mkknlimg and knlinfo scripts from tools repo - BCM2708: Add core Device Tree support - BCM270x_DT: Add pwr_led, and the required "input" trigger - Added Device IDs for August DVB-T 205 - Improve __copy_to_user and __copy_from_user performance - gpio-poweroff: Allow it to work on Raspberry Pi - mfd: Add Raspberry Pi Sense HAT core driver - ASoC: pcm512x: implement set_tdm_slot interface - ASoC: Add support for Rpi-DAC - Add IQaudIO Sound Card support for Raspberry Pi - Added support for HiFiBerry DAC+ - Added driver for HiFiBerry Amp amplifier add-on board - Add driver for rpi-proto - Add Support for JustBoom Audio boards - New AudioInjector.net Pi soundcard with low jitter audio in and out. - New driver for RRA DigiDAC1 soundcard using WM8741 + WM8804 - Add support for Dion Audio LOCO DAC-AMP HAT - Allo Piano DAC boards: Initial 2 channel (stereo) support (#1645 - Add support for Allo Piano DAC 2.1 plus add-on board for Raspberry Pi. - Add support for Allo Boss DAC add-on board for Raspberry Pi. (#1924 - Support for Blokas Labs pisound board - ASoC: Add driver for Cirrus Logic Audio Card - sound: Support for Dion Audio LOCO-V2 DAC-AMP HAT - Add support for Fe-Pi audio sound card. (#1867 - Add support for the AudioInjector.net Octo sound card - Driver support for Google voiceHAT soundcard. - Driver and overlay for Allo Katana DAC - ASoC
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
Since this seems like a bug in the firmware, you should report this issue to Intel as described here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging Please post a link to the bug here so I can keep track of the status. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15
[Kernel-packages] [Bug 1834894] Re: disco/linux-snapdragon: 5.0.0-1017.18 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834894 Title: disco/linux-snapdragon: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:35 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Complete phase-changed: Monday, 22. July 2019 20:36 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834943] Re: bionic/linux-oracle: 4.15.0-1018.20 -proposed tracker
This bug was fixed in the package linux-oracle - 4.15.0-1018.20 --- linux-oracle (4.15.0-1018.20) bionic; urgency=medium * linux-oracle: 4.15.0-1018.20 -proposed tracker (LP: #1834943) [ Ubuntu: 4.15.0-55.60 ] * linux: 4.15.0-55.60 -proposed tracker (LP: #1834954) * Request backport of ceph commits into bionic (LP: #1834235) - ceph: use atomic_t for ceph_inode_info::i_shared_gen - ceph: define argument structure for handle_cap_grant - ceph: flush pending works before shutdown super - ceph: send cap releases more aggressively - ceph: single workqueue for inode related works - ceph: avoid dereferencing invalid pointer during cached readdir - ceph: quota: add initial infrastructure to support cephfs quotas - ceph: quota: support for ceph.quota.max_files - ceph: quota: don't allow cross-quota renames - ceph: fix root quota realm check - ceph: quota: support for ceph.quota.max_bytes - ceph: quota: update MDS when max_bytes is approaching - ceph: quota: add counter for snaprealms with quota - ceph: avoid iput_final() while holding mutex or in dispatch thread * QCA9377 isn't being recognized sometimes (LP: #1757218) - SAUCE: USB: Disable USB2 LPM at shutdown * hns: fix ICMP6 neighbor solicitation messages discard problem (LP: #1833140) - net: hns: fix ICMP6 neighbor solicitation messages discard problem - net: hns: fix unsigned comparison to less than zero * Fix occasional boot time crash in hns driver (LP: #1833138) - net: hns: Fix probabilistic memory overwrite when HNS driver initialized * use-after-free in hns_nic_net_xmit_hw (LP: #1833136) - net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() * hns: attempt to restart autoneg when disabled should report error (LP: #1833147) - net: hns: Restart autoneg need return failed when autoneg off * systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp) (LP: #1821625) - powerpc: sys_pkey_alloc() and sys_pkey_free() system calls - powerpc: sys_pkey_mprotect() system call * [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different (LP: #1832625) - pkey: Indicate old mkvp only if old and current mkvp are different * [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing (LP: #1832623) - s390/crypto: fix gcm-aes-s390 selftest failures * System crashes on hot adding a core with drmgr command (4.15.0-48-generic) (LP: #1833716) - powerpc/numa: improve control of topology updates - powerpc/numa: document topology_updates_enabled, disable by default * Kernel modules generated incorrectly when system is localized to a non- English language (LP: #1828084) - scripts: override locale from environment when running recordmcount.pl * [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs (LP: #1832624) - s390/zcrypt: Fix wrong dispatching for control domain CPRBs * CVE-2019-11815 - net: rds: force to destroy connection if t_sock is NULL in rds_tcp_kill_sock(). * Sound device not detected after resume from hibernate (LP: #1826868) - drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled - drm/i915: Save the old CDCLK atomic state - drm/i915: Remove redundant store of logical CDCLK state - drm/i915: Skip modeset for cdclk changes if possible * Handle overflow in proc_get_long of sysctl (LP: #1833935) - sysctl: handle overflow in proc_get_long * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle (LP: #1808957) - Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering D3 and being disabled" - Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when suspending" - Revert "UBUNTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3" - Revert "SAUCE: nvme: add quirk to not call disable function when suspending" - Revert "SAUCE: pci: prevent sk hynix nvme from entering D3" - PCI: PM: Avoid possible suspend-to-idle issue - PCI: PM: Skip devices in D0 for suspend-to-idle - nvme-pci: Sync queues on reset - nvme: Export get and set features - nvme-pci: Use host managed power state for suspend * linux v4.15 ftbfs on a newer host kernel (e.g. hwe) (LP: #1823429) - selinux: use kernel linux/socket.h for genheaders and mdp * 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all (LP: #1830433) - x86/mm/pat: Disable preemption around __flush_tlb_all() - x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init() - x86/mm: Disable ioremap free page handling on x86-PAE - ioremap: Update pgtable free interfaces with addr - x86/mm: Add TLB purge to free pmd/pte page interfaces - x86/init: fix build with CONFIG_SWAP=n - x86/mm: provide pmdp_establish() helper - x86/mm: Use WRITE_ONCE() when setting PT
[Kernel-packages] [Bug 1834943] Re: bionic/linux-oracle: 4.15.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834943 Title: bionic/linux-oracle: 4.15.0-1018.20 -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: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Release phase-changed: Monday, 22. July 2019 20:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published trackers: xenial/linux-oracle: bug 1834942 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835434] Re: disco/linux-azure: 5.0.0-1012.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1835434 Title: disco/linux-azure: 5.0.0-1012.12 -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: Fix Released 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: Fix Released 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: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835882 (bionic/linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:35 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure-edge: bug 1835882 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834891] Re: disco/linux-gcp: 5.0.0-1011.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge), bug 1836202 (bionic /linux-gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Ready for Release - phase-changed: Monday, 22. July 2019 17:41 UTC + phase: Release + phase-changed: Monday, 22. July 2019 20:25 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gcp-edge: bug 1835904 bionic/linux-gke-5.0: bug 1836202 variant: debs ** Changed in: kernel-sru-workflow/promote-to-updates 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 1835904 (bionic/linux-gcp-edge), bug 1836202 (bionic /linux-gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Release - phase-changed: Monday, 22. July 2019 20:25 UTC + phase: Holding before Security + phase-changed: Monday, 22. July 2019 20:30 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-gcp-edge: bug 1835904 bionic/linux-gke-5.0: bug 1836202 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/1834891 Title: disco/linux-gcp: 5.0.0-1011.11 -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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge), bug 1836202 (bionic /linux-gke-5.0) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:30 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-gcp-edge: bug 1835904 bionic/linux-gke-5.0: bug 1836202 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834894] Re: disco/linux-snapdragon: 5.0.0-1017.18 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Ready for Release - phase-changed: Monday, 22. July 2019 17:42 UTC + phase: Release + phase-changed: Monday, 22. July 2019 20:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published variant: debs ** Changed in: kernel-sru-workflow/promote-to-updates 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: 1834902 - phase: Release - phase-changed: Monday, 22. July 2019 20:31 UTC + phase: Holding before Security + phase-changed: Monday, 22. July 2019 20:35 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published 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/1834894 Title: disco/linux-snapdragon: 5.0.0-1017.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:35 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: disco/linux-aws: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Release - phase-changed: Monday, 22. July 2019 20:20 UTC + phase: Holding before Security + phase-changed: Monday, 22. July 2019 20:25 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published trackers: bionic/linux-aws-edge: bug 1835782 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/1834886 Title: disco/linux-aws: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:25 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-aws-edge: bug 1835782 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834892] Re: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1834892 Title: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1834902 phase: Release phase-changed: Monday, 22. July 2019 20:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834888] Re: linux-azure: 5.0.0-1012.12 -proposed tracker
*** This bug is a duplicate of bug 1835434 *** https://bugs.launchpad.net/bugs/1835434 This bug was fixed in the package linux-azure - 5.0.0-1012.12 --- linux-azure (5.0.0-1012.12) disco; urgency=medium * linux-azure: 5.0.0-1012.12 -proposed tracker (LP: #1834888) * Disco update: 5.0.12 upstream stable release (LP: #1830934) - [Config] Document drop of axis-fifo for amd64/i386 * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - [Config] update configs and annotations for ASIX renamed [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when offsets are used - platform/x86: pmc_atom: Drop __initconst on dmi table - NFSv4.1 fix incorrect return value in copy_file_range - perf/core: Fix perf_event_dis
[Kernel-packages] [Bug 1834891] Re: disco/linux-gcp: 5.0.0-1011.11 -proposed tracker
This bug was fixed in the package linux-gcp - 5.0.0-1011.11 --- linux-gcp (5.0.0-1011.11) disco; urgency=medium * linux-gcp: 5.0.0-1011.11 -proposed tracker (LP: #1834891) * Disco update: 5.0.12 upstream stable release (LP: #1830934) - gcp: [Config] Drop axis-fifo * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - gcp: [Config] Rename ASIX module [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when offsets are used - platform/x86: pmc_atom: Drop __initconst on dmi table - NFSv4.1 fix incorrect return value in copy_file_range - perf/core: Fix perf_event_disable_inatomic() race - genirq: Prevent use-after-free and work list corruption - usb: dwc3: Allow building USB_DWC3_QCOM without EXTCON
[Kernel-packages] [Bug 1834892] Re: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Ready for Release - phase-changed: Monday, 22. July 2019 17:42 UTC + phase: Release + phase-changed: Monday, 22. July 2019 20:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published 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/1834892 Title: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: In Progress Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1834902 phase: Release phase-changed: Monday, 22. July 2019 20:30 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834894] Re: disco/linux-snapdragon: 5.0.0-1017.18 -proposed tracker
This bug was fixed in the package linux-snapdragon - 5.0.0-1017.18 --- linux-snapdragon (5.0.0-1017.18) disco; urgency=medium * linux-snapdragon: 5.0.0-1017.18 -proposed tracker (LP: #1834894) * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - [Config] update configs and annotations for ASIX renamed * [SRU][B/B-OEM/C/D/OEM-OSP1] Add RTL8822 wifi driver rtw88 (LP: #1831828) - [Config] Add realtek wifi RTW88 support [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when offsets are used - platform/x86: pmc_atom: Drop __initconst on dmi table - NFSv4.1 fix incorrect return value in copy_file_range - perf/core: Fix perf_event_disable_inatomic() race - genirq: Prevent use-after-free and work list cor
[Kernel-packages] [Bug 1812624] Re: PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM
This bug was fixed in the package linux-kvm - 5.0.0-1011.12 --- linux-kvm (5.0.0-1011.12) disco; urgency=medium * linux-kvm: 5.0.0-1011.12 -proposed tracker (LP: #1834892) * q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels (LP: #1812159) - [Config]: enable SCHED_STACK_END_CHECK * PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM (LP: #1812624) - [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY, PAGE_POISONING_ZERO * test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM (LP: #1811981) - [Config]: enable CONFIG_LOCK_DOWN_KERNEL [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when o
[Kernel-packages] [Bug 1829812] Re: Regression for ubuntu_kernel_selftests [net] ubuntu_bpf test case fails to build on disco
This bug was fixed in the package linux-azure - 5.0.0-1012.12 --- linux-azure (5.0.0-1012.12) disco; urgency=medium * linux-azure: 5.0.0-1012.12 -proposed tracker (LP: #1834888) * Disco update: 5.0.12 upstream stable release (LP: #1830934) - [Config] Document drop of axis-fifo for amd64/i386 * AX88772A USB to Ethernet dongle doesn't work (LP: #1834114) - [Config] update configs and annotations for ASIX renamed [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when offsets are used - platform/x86: pmc_atom: Drop __initconst on dmi table - NFSv4.1 fix incorrect return value in copy_file_range - perf/core: Fix perf_event_disable_inatomic() race - genirq: Prevent use-after-free and work list corruption - usb
[Kernel-packages] [Bug 1834892] Re: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker
This bug was fixed in the package linux-kvm - 5.0.0-1011.12 --- linux-kvm (5.0.0-1011.12) disco; urgency=medium * linux-kvm: 5.0.0-1011.12 -proposed tracker (LP: #1834892) * q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels (LP: #1812159) - [Config]: enable SCHED_STACK_END_CHECK * PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM (LP: #1812624) - [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY, PAGE_POISONING_ZERO * test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM (LP: #1811981) - [Config]: enable CONFIG_LOCK_DOWN_KERNEL [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when o
[Kernel-packages] [Bug 1812159] Re: q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels
This bug was fixed in the package linux-kvm - 5.0.0-1011.12 --- linux-kvm (5.0.0-1011.12) disco; urgency=medium * linux-kvm: 5.0.0-1011.12 -proposed tracker (LP: #1834892) * q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels (LP: #1812159) - [Config]: enable SCHED_STACK_END_CHECK * PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM (LP: #1812624) - [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY, PAGE_POISONING_ZERO * test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM (LP: #1811981) - [Config]: enable CONFIG_LOCK_DOWN_KERNEL [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when o
[Kernel-packages] [Bug 1823429] Re: linux v4.15 ftbfs on a newer host kernel (e.g. hwe)
This bug was fixed in the package linux-oracle - 4.15.0-1018.20 --- linux-oracle (4.15.0-1018.20) bionic; urgency=medium * linux-oracle: 4.15.0-1018.20 -proposed tracker (LP: #1834943) [ Ubuntu: 4.15.0-55.60 ] * linux: 4.15.0-55.60 -proposed tracker (LP: #1834954) * Request backport of ceph commits into bionic (LP: #1834235) - ceph: use atomic_t for ceph_inode_info::i_shared_gen - ceph: define argument structure for handle_cap_grant - ceph: flush pending works before shutdown super - ceph: send cap releases more aggressively - ceph: single workqueue for inode related works - ceph: avoid dereferencing invalid pointer during cached readdir - ceph: quota: add initial infrastructure to support cephfs quotas - ceph: quota: support for ceph.quota.max_files - ceph: quota: don't allow cross-quota renames - ceph: fix root quota realm check - ceph: quota: support for ceph.quota.max_bytes - ceph: quota: update MDS when max_bytes is approaching - ceph: quota: add counter for snaprealms with quota - ceph: avoid iput_final() while holding mutex or in dispatch thread * QCA9377 isn't being recognized sometimes (LP: #1757218) - SAUCE: USB: Disable USB2 LPM at shutdown * hns: fix ICMP6 neighbor solicitation messages discard problem (LP: #1833140) - net: hns: fix ICMP6 neighbor solicitation messages discard problem - net: hns: fix unsigned comparison to less than zero * Fix occasional boot time crash in hns driver (LP: #1833138) - net: hns: Fix probabilistic memory overwrite when HNS driver initialized * use-after-free in hns_nic_net_xmit_hw (LP: #1833136) - net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() * hns: attempt to restart autoneg when disabled should report error (LP: #1833147) - net: hns: Restart autoneg need return failed when autoneg off * systemd 237-3ubuntu10.14 ADT test failure on Bionic ppc64el (test-seccomp) (LP: #1821625) - powerpc: sys_pkey_alloc() and sys_pkey_free() system calls - powerpc: sys_pkey_mprotect() system call * [UBUNTU] pkey: Indicate old mkvp only if old and curr. mkvp are different (LP: #1832625) - pkey: Indicate old mkvp only if old and current mkvp are different * [UBUNTU] kernel: Fix gcm-aes-s390 wrong scatter-gather list processing (LP: #1832623) - s390/crypto: fix gcm-aes-s390 selftest failures * System crashes on hot adding a core with drmgr command (4.15.0-48-generic) (LP: #1833716) - powerpc/numa: improve control of topology updates - powerpc/numa: document topology_updates_enabled, disable by default * Kernel modules generated incorrectly when system is localized to a non- English language (LP: #1828084) - scripts: override locale from environment when running recordmcount.pl * [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs (LP: #1832624) - s390/zcrypt: Fix wrong dispatching for control domain CPRBs * CVE-2019-11815 - net: rds: force to destroy connection if t_sock is NULL in rds_tcp_kill_sock(). * Sound device not detected after resume from hibernate (LP: #1826868) - drm/i915: Force 2*96 MHz cdclk on glk/cnl when audio power is enabled - drm/i915: Save the old CDCLK atomic state - drm/i915: Remove redundant store of logical CDCLK state - drm/i915: Skip modeset for cdclk changes if possible * Handle overflow in proc_get_long of sysctl (LP: #1833935) - sysctl: handle overflow in proc_get_long * Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle (LP: #1808957) - Revert "UBUNTU: SAUCE: pci/nvme: prevent WDC PC SN720 NVMe from entering D3 and being disabled" - Revert "UBUNTU: SAUCE: nvme: add quirk to not call disable function when suspending" - Revert "UBUNTU: SAUCE: pci: prevent Intel NVMe SSDPEKKF from entering D3" - Revert "SAUCE: nvme: add quirk to not call disable function when suspending" - Revert "SAUCE: pci: prevent sk hynix nvme from entering D3" - PCI: PM: Avoid possible suspend-to-idle issue - PCI: PM: Skip devices in D0 for suspend-to-idle - nvme-pci: Sync queues on reset - nvme: Export get and set features - nvme-pci: Use host managed power state for suspend * linux v4.15 ftbfs on a newer host kernel (e.g. hwe) (LP: #1823429) - selinux: use kernel linux/socket.h for genheaders and mdp * 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all (LP: #1830433) - x86/mm/pat: Disable preemption around __flush_tlb_all() - x86/mm: Drop usage of __flush_tlb_all() in kernel_physical_mapping_init() - x86/mm: Disable ioremap free page handling on x86-PAE - ioremap: Update pgtable free interfaces with addr - x86/mm: Add TLB purge to free pmd/pte page interfaces - x86/init: fix build with CONFIG_SWAP=n - x86/mm: provide pmdp_establish() helper - x86/mm: Use WRITE_ONCE() when setting PT
[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM
This bug was fixed in the package linux-kvm - 5.0.0-1011.12 --- linux-kvm (5.0.0-1011.12) disco; urgency=medium * linux-kvm: 5.0.0-1011.12 -proposed tracker (LP: #1834892) * q-r-t security test wants SCHED_STACK_END_CHECK to be enabled in KVM kernels (LP: #1812159) - [Config]: enable SCHED_STACK_END_CHECK * PAGE_POISONING / PAGE_POISONING_NO_SANITY / PAGE_POISONING_ZERO option was expected to be set in C-KVM (LP: #1812624) - [Config]: enable PAGE_POISONING, PAGE_POISONING_NO_SANITY, PAGE_POISONING_ZERO * test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM (LP: #1811981) - [Config]: enable CONFIG_LOCK_DOWN_KERNEL [ Ubuntu: 5.0.0-21.22 ] * linux: 5.0.0-21.22 -proposed tracker (LP: #1834902) * Disco update: 5.0.15 upstream stable release (LP: #1834529) - net: stmmac: Use bfsize1 in ndesc_init_rx_desc - Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup() - ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings - staging: greybus: power_supply: fix prop-descriptor request size - staging: wilc1000: Avoid GFP_KERNEL allocation from atomic context. - staging: most: cdev: fix chrdev_region leak in mod_exit - staging: most: sound: pass correct device when creating a sound card - ASoC: tlv320aic3x: fix reset gpio reference counting - ASoC: hdmi-codec: fix S/PDIF DAI - ASoC: stm32: sai: fix iec958 controls indexation - ASoC: stm32: sai: fix exposed capabilities in spdif mode - ASoC: stm32: sai: fix race condition in irq handler - ASoC:soc-pcm:fix a codec fixup issue in TDM case - ASoC:hdac_hda:use correct format to setup hda codec - ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform - ASoC: dpcm: prevent snd_soc_dpcm use after free - ASoC: nau8824: fix the issue of the widget with prefix name - ASoC: nau8810: fix the issue of widget with prefixed name - ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate - ASoC: rt5682: Check JD status when system resume - ASoC: rt5682: fix jack type detection issue - ASoC: rt5682: recording has no sound after booting - ASoC: wm_adsp: Add locking to wm_adsp2_bus_error - clk: meson-gxbb: round the vdec dividers to closest - ASoC: stm32: dfsdm: manage multiple prepare - ASoC: stm32: dfsdm: fix debugfs warnings on entry creation - ASoC: cs4270: Set auto-increment bit for register writes - ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol - drm/omap: hdmi4_cec: Fix CEC clock handling for PM - IB/hfi1: Clear the IOWAIT pending bits when QP is put into error state - IB/hfi1: Eliminate opcode tests on mr deref - IB/hfi1: Fix the allocation of RSM table - MIPS: KGDB: fix kgdb support for SMP platforms. - ASoC: tlv320aic32x4: Fix Common Pins - drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata() - perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS - perf/x86/intel: Initialize TFA MSR - linux/kernel.h: Use parentheses around argument in u64_to_user_ptr() - iov_iter: Fix build error without CONFIG_CRYPTO - xtensa: fix initialization of pt_regs::syscall in start_thread - ASoC: rockchip: pdm: fix regmap_ops hang issue - drm/amdkfd: Add picasso pci id - drm/amdgpu: Adjust IB test timeout for XGMI configuration - drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list - drm/amd/display: fix cursor black issue - ASoC: cs35l35: Disable regulators on driver removal - objtool: Add rewind_stack_do_exit() to the noreturn list - slab: fix a crash by reading /proc/slab_allocators - drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind - virtio_pci: fix a NULL pointer reference in vp_del_vqs - RDMA/vmw_pvrdma: Fix memory leak on pvrdma_pci_remove - RDMA/hns: Fix bug that caused srq creation to fail - KEYS: trusted: fix -Wvarags warning - scsi: csiostor: fix missing data copy in csio_scsi_err_handler() - drm/mediatek: fix possible object reference leak - drm/mediatek: fix the rate and divder of hdmi phy for MT2701 - drm/mediatek: make implementation of recalc_rate() for MT2701 hdmi phy - drm/mediatek: remove flag CLK_SET_RATE_PARENT for MT2701 hdmi phy - drm/mediatek: using new factor for tvdpll for MT2701 hdmi phy - drm/mediatek: no change parent rate in round_rate() for MT2701 hdmi phy - ASoC: Intel: kbl: fix wrong number of channels - ASoC: stm32: sai: fix master clock management - ALSA: hda: Fix racy display power access - virtio-blk: limit number of hw queues by nr_cpu_ids - blk-mq: introduce blk_mq_complete_request_sync() - nvme: cancel request synchronously - nvme-fc: correct csn initialization and increments on error - nvmet: fix discover log page when o
[Kernel-packages] [Bug 1836925] Re: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Ready for Release - phase-changed: Monday, 22. July 2019 18:29 UTC + phase: Complete + phase-changed: Monday, 22. July 2019 20:36 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Pending -- ready to copy 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/1836925 Title: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Complete phase-changed: Monday, 22. July 2019 20:36 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835434] Re: disco/linux-azure: 5.0.0-1012.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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 1835882 (bionic/linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1834902 - phase: Ready for Release - phase-changed: Monday, 22. July 2019 18:09 UTC + phase: Holding before Security + phase-changed: Monday, 22. July 2019 20:35 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Pending -- ready to copy trackers: bionic/linux-azure-edge: bug 1835882 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/1835434 Title: disco/linux-azure: 5.0.0-1012.12 -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: Fix Released 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: Fix Released 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: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835882 (bionic/linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:35 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: bionic/linux-azure-edge: bug 1835882 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834943] Re: bionic/linux-oracle: 4.15.0-1018.20 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Ready for Release - phase-changed: Monday, 22. July 2019 18:30 UTC + phase: Release + phase-changed: Monday, 22. July 2019 20:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published trackers: xenial/linux-oracle: bug 1834942 variant: debs ** Changed in: kernel-sru-workflow/promote-to-updates 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 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Release - phase-changed: Monday, 22. July 2019 20:36 UTC + phase: Holding before Security + phase-changed: Monday, 22. July 2019 20:41 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published trackers: xenial/linux-oracle: bug 1834942 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/1834943 Title: bionic/linux-oracle: 4.15.0-1018.20 -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: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Holding before Security phase-changed: Monday, 22. July 2019 20:41 UTC proposed-announcement-sent: true proposed-testing-requested: true trackers: xenial/linux-oracle: bug 1834942 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
@sforshee: Are you referring to me or someone on the ubuntu dev team? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15:13:31 Lappy kernel: [ 85.320173] iwlwifi :3b:00.0: 0x1000 | data2 Jul 17 15:13:31 Lappy kernel: [ 85.320174] iwlwifi :3b:00.0: 0xE008 | data3 Jul 17 15:1
[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
Hi, i also experience similar problems. Lately i use both vscode and intellij, and of course chrome, all hungry for cpu and ram. Since about 3-4 weeks my system hangs completely. Especially if i drag n drop things or to be precise attempt to, because i cant, it freezes. System-Information: === ➜ ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename: disco ➜ ~ uname -a 5.0.0-21-generic #22-Ubuntu SMP Tue Jul 2 13:27:33 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ➜ ~ nvidia-smi Mon Jul 22 22:46:58 2019 +-+ | NVIDIA-SMI 430.26 Driver Version: 430.26 CUDA Version: 10.2 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | |===+==+==| | 0 GeForce 940MX Off | :02:00.0 Off | N/A | | N/A 40CP0N/A / N/A |431MiB / 2004MiB | 0% Default | +---+--+--+ +-+ | Processes: GPU Memory | | GPU PID Type Process name Usage | |=| |0 3090 G /usr/lib/xorg/Xorg 193MiB | |0 3411 G /usr/bin/gnome-shell 140MiB | ➜ ~ hwinfo --short cpu: 8 * Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz, 1775 MHz monitor: AUO LCD Monitor BenQ V2400Eco graphics card: nVidia GM108M [GeForce 940MX] Intel HD Graphics 630 disk: /dev/nvme0n1 Toshiba America Info XG4 NVMe SSD Controller bios: BIOS bridge: Intel 100 Series/C230 Series Chipset Family PCI Express Root Port #1 Intel Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x4) Intel QM175 Chipset LPC/eSPI Controller Intel Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) Intel Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers Intel 100 Series/C230 Series Chipset Family PCI Express Root Port #9 Intel 100 Series/C230 Series Chipset Family PCI Express Root Port #5 hub: Lenovo ThinkPad Dock Lenovo ThinkPad Dock Linux Foundation 2.0 root hub Lenovo ThinkPad Dock Linux Foundation 3.0 root hub LOG OUTPUT === $ journalctl [...] gnome-software[4896]: hiding category graphics featured applications: found only 1 to show, need at least 9 [...] gnome-software[4896]: hiding category audio-video featured applications: found only 0 to show, need at least 9 [...] snapd[1118]: 2019/07/22 21:58:57 Unsolicited response received on idle HTTP channel starting with "HTTP/1.0 408 Request Time-out\r\nCache-Control: no-cache\r\nConnection: close\r\nContent-Type: text/html\r\n\r\n408 Request Time-out\nYour browser didn't send a complete request in time.\n\n"; err= [...] /usr/lib/gdm3/gdm-x-session[3088]: nvLock: client timed out, taking the lock MORE LOG OUTPUT === the logs above i saw earlier, but following came once after updating my kernel today (was hoping to fix freeze issue ^^) and also was about to try JDK 13 and 14, just did set JAVA_HOME and sourced, after that wanted to open vscode and my PC went crazy, 8 Cores running like on fire, than memory started to fill up, so i killed vscode and also intellij idea which was also running already: the logs produced while core burning: [...] Jul 22 21:44:01 ThinkPad-T470p kernel: mce: CPU4: Package temperature/speed normal Jul 22 21:44:15 ThinkPad-T470p kernel: Valid eCryptfs headers not found in file header region or xattr region, inode 26223225 Jul 22 21:44:26 ThinkPad-T470p kernel: ptrace attach of "/lib/systemd/systemd --user"[3060] was attempted by "/usr/share/code/resources/app/node_modules.asar.unpacked/vscode-ripgrep/bin/rg --hidden --ignore-case -g !**/.git -g !**/.svn -g !**/.hg -g !**/CVS -g !**/.DS_Store -g !**/.classpath -g !**/.project -g !**/.settings -g !**/.factorypath -g
[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
That's so bad formatted, please take a look here at this gist: https://gist.github.com/farukg/4980c14aba876342bea8c2124a8c6264 -- 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 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
This is a kernel bug, introduced by one of these patches applied to xenial: commit d823dfc03906fd278ae6f48219c4ed53faee6f9d Author: Al Viro Date: Thu Jun 27 20:16:00 2019 +0200 bio_copy_from_iter(): get rid of copying iov_iter commit aceb27a7de5fc65a3fc70ccac344f33099e8a4dc Author: Keith Busch Date: Thu Jun 27 20:16:00 2019 +0200 block: Clear kernel memory before copying to user commit a713ff5b13e8fd9e331fd84232806316aa9e9b2a Author: Keith Busch Date: Thu Jun 27 20:16:00 2019 +0200 block/bio: Do not zero user pages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834892] Re: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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: 1834902 - phase: Release - phase-changed: Monday, 22. July 2019 20:30 UTC + phase: Holding before Security + phase-changed: Monday, 22. July 2019 21:12 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published 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/1834892 Title: disco/linux-kvm: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 21:12 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834884] Re: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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: 1834902 - phase: Release - phase-changed: Monday, 22. July 2019 20:20 UTC + phase: Holding before Security + phase-changed: Monday, 22. July 2019 21:11 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published 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/1834884 Title: disco/linux-raspi2: 5.0.0-1013.13 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in 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: 1834902 phase: Holding before Security phase-changed: Monday, 22. July 2019 21:11 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
@sforshee upstream is aware of the issue: https://lore.kernel.org/linux- wireless/s5hr26m9gvc.wl-ti...@suse.de -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | data1 Jul 17 15:13:31 Lappy kernel: [ 85.320173] iwlwifi :3b:00.0: 0x1000 | data2 Jul 17 15:13:31 Lappy kernel: [ 85.320174] iwlwifi :3
[Kernel-packages] [Bug 1837465] [NEW] WARNING: CPU: 9 PID: 129 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277 generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
Public bug reported: Whenever I run a game that pushes my GPU harder than usual, my monitor loses signal from the GPU and I have to do a hard reboot (hold down the power button for a few seconds) of my computer. I'm able to reproduce the problem consistently by playing Cities Skylines at 4K. Please let me know if I can be of any assistance in helping to test. System info: Ubuntu Version: 18.04.2 LTS Kernel: 5.1.16-050116-generic Steps to reproduce: 1) Run Cities Skylines from Steam at 4k 2) Load a new map and start building a city Expected: The system should be stable Actual: Within 20 - 300 seconds, the monitor loses signal, and I have to perform a hard reboot. Notes: I've attached the last 1000 lines of my syslog after the moment of the crash until I rebooted. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1837465/+attachment/5278554/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837465 Title: WARNING: CPU: 9 PID: 129 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277 generic_reg_wait.cold.3+0x25/0x2c [amdgpu] Status in linux package in Ubuntu: Incomplete Bug description: Whenever I run a game that pushes my GPU harder than usual, my monitor loses signal from the GPU and I have to do a hard reboot (hold down the power button for a few seconds) of my computer. I'm able to reproduce the problem consistently by playing Cities Skylines at 4K. Please let me know if I can be of any assistance in helping to test. System info: Ubuntu Version: 18.04.2 LTS Kernel: 5.1.16-050116-generic Steps to reproduce: 1) Run Cities Skylines from Steam at 4k 2) Load a new map and start building a city Expected: The system should be stable Actual: Within 20 - 300 seconds, the monitor loses signal, and I have to perform a hard reboot. Notes: I've attached the last 1000 lines of my syslog after the moment of the crash until I rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
Those commits were applied for LP: #1834499. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834499] Re: [linux-azure] Block Layer Commits Requested in Azure Kernels
The patches applied to fix this issue are causing a regression in Xenial
(see bug #1837235), therefore I'm going to remove them.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1834499
Title:
[linux-azure] Block Layer Commits Requested in Azure Kernels
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Committed
Bug description:
We would like to request the following two commits in the 16.04 and
18.04 linux-azure kernels:
f3587d76da05 ("block: Clear kernel memory before copying to user")
f55adad601c6 ("block/bio: Do not zero user pages")
These commits are in mainline as of v4.20 and have been cc'd to
upstream stable.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834499/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837465] Re: WARNING: CPU: 9 PID: 129 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277 generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
** Attachment added: "Last 1000 lines of syslog, captured after crash" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837465/+attachment/5278555/+files/sys.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837465 Title: WARNING: CPU: 9 PID: 129 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277 generic_reg_wait.cold.3+0x25/0x2c [amdgpu] Status in linux package in Ubuntu: Incomplete Bug description: Whenever I run a game that pushes my GPU harder than usual, my monitor loses signal from the GPU and I have to do a hard reboot (hold down the power button for a few seconds) of my computer. I'm able to reproduce the problem consistently by playing Cities Skylines at 4K. Please let me know if I can be of any assistance in helping to test. System info: Ubuntu Version: 18.04.2 LTS Kernel: 5.1.16-050116-generic Steps to reproduce: 1) Run Cities Skylines from Steam at 4k 2) Load a new map and start building a city Expected: The system should be stable Actual: Within 20 - 300 seconds, the monitor loses signal, and I have to perform a hard reboot. Notes: I've attached the last 1000 lines of my syslog after the moment of the crash until I rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
How to easily reproduce the issue: $ sudo modprobe scsi_debug $ sudo /lib/udev/scsi_id --export --whitelisted -v -d /dev/sdb 8:16: ioctl failed: Invalid argument 8:16: Unable to get INQUIRY vpd 0 page 0x0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: In Progress Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: In Progress Status in linux source package in Disco: Invalid Status in systemd source package in Disco: In Progress Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: In Progress Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260
@thedarb: To you, since you have the hardware to work with them to diagnose the problem. @kerneltoast: Sometimes these firmware crashes look the same but have different underlying causes, so imo it's better to go ahead and report it and let the Intel devs sort out whether or not it's actually a duplicate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1836986 Title: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260 Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu version: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 System type: description: Notebook product: Precision 5530 (087D) vendor: Dell Inc. Hardware having issue: (wireless card info from previous working kernel) *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:3b:00.0 logical name: wlp59s0 version: 29 serial: 48:89:e7:d5:ab:b5 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:16 memory:ed40-ed403fff Grub config with settings for Dell laptop hardware set: /etc/default/grub # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=0 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" #GRUB_CMDLINE_LINUX_DEFAULT="nosplash" GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 nouveau.runpm=0 mem_sleep_default=deep" # Uncomment to enable BadRAM filtering, modify to suit your needs # This works with Linux (no patch required) and with any kernel that obtains # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...) #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef" # Uncomment to disable graphical terminal (grub-pc only) #GRUB_TERMINAL=console # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' #GRUB_GFXMODE=640x480 # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux #GRUB_DISABLE_LINUX_UUID=true # Uncomment to disable generation of recovery mode menu entries #GRUB_DISABLE_RECOVERY="true" # Uncomment to get a beep at grub start #GRUB_INIT_TUNE="480 440 1" Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it disabled. /etc/modprobe.d/iwlwifi.conf # /etc/modprobe.d/iwlwifi.conf # iwlwifi will dyamically load either iwldvm or iwlmvm depending on the # microcode file installed on the system. When removing iwlwifi, first # remove the iwl?vm module and then iwlwifi. remove iwlwifi \ (/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \ && /sbin/modprobe -r mac80211 options iwlwifi 11n_disable=1 Linux-Firmware package = 1.180 Nvidia Driver version = 430.34-0ubuntu2 Issue: Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load. Works with 5.0.0.-20-generic kernel. Syslog: Jul 17 15:13:31 Lappy kernel: [ 85.319088] iwlwifi :3b:00.0: Microcode SW error detected. Restarting 0x0. Jul 17 15:13:31 Lappy kernel: [ 85.320158] iwlwifi :3b:00.0: Start IWL Error Log Dump: Jul 17 15:13:31 Lappy kernel: [ 85.320161] iwlwifi :3b:00.0: Status: 0x0080, count: 6 Jul 17 15:13:31 Lappy kernel: [ 85.320162] iwlwifi :3b:00.0: Loaded firmware version: 46.a41adfe7.0 Jul 17 15:13:31 Lappy kernel: [ 85.320164] iwlwifi :3b:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL Jul 17 15:13:31 Lappy kernel: [ 85.320166] iwlwifi :3b:00.0: 0x00A022F0 | trm_hw_status0 Jul 17 15:13:31 Lappy kernel: [ 85.320167] iwlwifi :3b:00.0: 0x | trm_hw_status1 Jul 17 15:13:31 Lappy kernel: [ 85.320168] iwlwifi :3b:00.0: 0x004882F2 | branchlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320169] iwlwifi :3b:00.0: 0x004793A2 | interruptlink1 Jul 17 15:13:31 Lappy kernel: [ 85.320171] iwlwifi :3b:00.0: 0x00480EA2 | interruptlink2 Jul 17 15:13:31 Lappy kernel: [ 85.320
[Kernel-packages] [Bug 1837467] [NEW] segfault when CCD are present in two different HOG services
Public bug reported: Hello everyone, Test setup: ubuntu 19.04, bluez 5.50, kernel bug id 204201 We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1837467 Title: segfault when CCD are present in two different HOG services Status in bluez package in Ubuntu: New Bug description: Hello everyone, Test setup: ubuntu 19.04, bluez 5.50, kernel bug id 204201 We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1837467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837465] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1837465 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837465 Title: WARNING: CPU: 9 PID: 129 at drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:277 generic_reg_wait.cold.3+0x25/0x2c [amdgpu] Status in linux package in Ubuntu: Incomplete Bug description: Whenever I run a game that pushes my GPU harder than usual, my monitor loses signal from the GPU and I have to do a hard reboot (hold down the power button for a few seconds) of my computer. I'm able to reproduce the problem consistently by playing Cities Skylines at 4K. Please let me know if I can be of any assistance in helping to test. System info: Ubuntu Version: 18.04.2 LTS Kernel: 5.1.16-050116-generic Steps to reproduce: 1) Run Cities Skylines from Steam at 4k 2) Load a new map and start building a city Expected: The system should be stable Actual: Within 20 - 300 seconds, the monitor loses signal, and I have to perform a hard reboot. Notes: I've attached the last 1000 lines of my syslog after the moment of the crash until I rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837467] Re: segfault when CCD are present in two different HOG services
** Attachment added: "callstacks" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1837467/+attachment/5278556/+files/callstacks.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1837467 Title: segfault when CCD are present in two different HOG services Status in bluez package in Ubuntu: New Bug description: Hello everyone, Test setup: ubuntu 19.04, bluez 5.50, kernel bug id 204201 We are currently developing a device that contains two HID services. That device, as it is right now, is properly functioning on Windows & Android. However, when pairing the device on Linux running bluez 5.50 we do get segfaults (see attached files). Our bluetooth device has 4 services : 1 battery service, 2 HID Over Gatt services and 1 device information service. With trial and error, we managed to find that we wouldn't get any crash as long as only 1 HOG service was present. Here's the interesting part. The two HOG services are made as follows: - standard keyboard over gatt: protocole mode / report map / 1 INPUT report / boot INPUT + OUTPUT / HID information / HID Control point - raw HID over gatt : report map / 1 INPUT report / 1 OUTPUT report / HID information / HID control point Looking at the write_ccc in the call stacks we wondered if the callbacks subscribing to notifications for the INPUT reports were causing this issue. We therefore changed the raw HID over gatt (and its report map) to remove the INPUT report and change it into 1 OUTPUT report (leading to 2 OUTPUT reports): no crash. We therefore hypothesize that the segfault occurs when subscribing to notification on a second HOG service... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1837467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
it is still failing... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837469] [NEW] AWS hibernation failure with KASLR enabled
Public bug reported: Observed during development and testing of AWS hibernation on Ubuntu linux-aws-bionic (4.15.0-1044.46): There is a known issue when using On-Demand Hibernation related to KASLR (Kernel Address Space Layout Randomization). KASLR is a standard Linux kernel security feature which helps to mitigate exposure to and ramifications of yet-undiscovered memory access vulnerabilities by randomizing the base address value of the kernel. In a small percentage of tests, instances with KASLR enabled do not resume and become completely unusable after hibernation. Disabling KASLR, which is enabled by default, is known to avoid this issue. Please see (TBD AWS announcement) for additional details. - Users affected by this issue may consider disabling KASLR as a work- around, as follows: To disable KASLR on an instance, follow these steps to reboot with the 'nokaslr' kernel command line switch: 1. Edit the file /etc/default/grub.d/50-cloudimg-settings.cfg and add the word 'nokaslr' to the GRUB_CMDLINE_LINUX_DEFAULT string, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 nokaslr" 2. Run the command 'sudo update-grub'. 3. Reboot the instance. ** Affects: linux-aws (Ubuntu) Importance: High Status: Triaged -- 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/1837469 Title: AWS hibernation failure with KASLR enabled Status in linux-aws package in Ubuntu: Triaged Bug description: Observed during development and testing of AWS hibernation on Ubuntu linux-aws-bionic (4.15.0-1044.46): There is a known issue when using On-Demand Hibernation related to KASLR (Kernel Address Space Layout Randomization). KASLR is a standard Linux kernel security feature which helps to mitigate exposure to and ramifications of yet-undiscovered memory access vulnerabilities by randomizing the base address value of the kernel. In a small percentage of tests, instances with KASLR enabled do not resume and become completely unusable after hibernation. Disabling KASLR, which is enabled by default, is known to avoid this issue. Please see (TBD AWS announcement) for additional details. - Users affected by this issue may consider disabling KASLR as a work- around, as follows: To disable KASLR on an instance, follow these steps to reboot with the 'nokaslr' kernel command line switch: 1. Edit the file /etc/default/grub.d/50-cloudimg-settings.cfg and add the word 'nokaslr' to the GRUB_CMDLINE_LINUX_DEFAULT string, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 nokaslr" 2. Run the command 'sudo update-grub'. 3. Reboot the instance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1837469/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836925] Re: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836925 Title: bionic/linux-ibm-gt: 4.15.0-1028.30 -proposed tracker Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Complete phase-changed: Monday, 22. July 2019 20:36 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1836925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
