[Kernel-packages] [Bug 1854315] [NEW] IPSec / xfrm memory leak found
Public bug reported: Hi everybody. there is a memory leak in the current kernels since 4.15 (maybe olders as well) in combination with IPSec. I verified it with kernel linux-meta 4.15.0.70.72 on Ubuntu 18.04. As Strongswan is used and users login / logout, being connected and doing traffic memory gets lost. After a while no memory is left over and OOM killer starts it work. After some debugging and asking in the Strongswan irc channel I was informed that there was a memory leak found in net/xfrm/xfrm_state.c which might be related. Here is the commit to this fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86c6739eda7d2a03f2db30cbee67a5fb81afa8ba I applied this patch against the linux-meta 4.15.0.70.72 and it fixes the issue. Tested and verified on and with: Ubuntu 18.04.3 LTS strongswan-5.6.2-1ubuntu2.4 linux-image-generic-4.15.0.70.72 Here are some additional information: https://lore.kernel.org/netdev/2019062832.gp13...@gauss3.secunet.de/ https://marc.info/?l=linux-netdev=157405892918311=2 it also is reproducible with hwe and hwe-edge kernel as well as with other strongswan version. I also backported latest Ubuntu version of strongswan to 18.04 which has same behavior. On a completely different system (Gentoo) it also is the case. So I'm really sure that this is related to the reported kernel thing which is already solve in current mainline ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854315 Title: IPSec / xfrm memory leak found Status in linux-meta package in Ubuntu: New Bug description: Hi everybody. there is a memory leak in the current kernels since 4.15 (maybe olders as well) in combination with IPSec. I verified it with kernel linux- meta 4.15.0.70.72 on Ubuntu 18.04. As Strongswan is used and users login / logout, being connected and doing traffic memory gets lost. After a while no memory is left over and OOM killer starts it work. After some debugging and asking in the Strongswan irc channel I was informed that there was a memory leak found in net/xfrm/xfrm_state.c which might be related. Here is the commit to this fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86c6739eda7d2a03f2db30cbee67a5fb81afa8ba I applied this patch against the linux-meta 4.15.0.70.72 and it fixes the issue. Tested and verified on and with: Ubuntu 18.04.3 LTS strongswan-5.6.2-1ubuntu2.4 linux-image-generic-4.15.0.70.72 Here are some additional information: https://lore.kernel.org/netdev/2019062832.gp13...@gauss3.secunet.de/ https://marc.info/?l=linux-netdev=157405892918311=2 it also is reproducible with hwe and hwe-edge kernel as well as with other strongswan version. I also backported latest Ubuntu version of strongswan to 18.04 which has same behavior. On a completely different system (Gentoo) it also is the case. So I'm really sure that this is related to the reported kernel thing which is already solve in current mainline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1854315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851623] Re: Enable framebuffer fonts auto selection for HighDPI screen
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851623 Title: Enable framebuffer fonts auto selection for HighDPI screen Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: == Justification == After bug 1819881 - [CONFIG] please enable highdpi font FONT_TER16x32, our kernels now support TER16x32 font for high resolution screen. With Takashi Iwai's patch: dfd19a50 (fonts: Prefer a bigger font for high resolution screens) The framebuffer can now decide which font to use base on the screen resolution. It will be great to have this feature in older kernels as well. == Fixes == * aa1d19f1 (fonts: Fix coding style) * dfd19a50 (fonts: Prefer a bigger font for high resolution screens) First patch just changes the coding style, no actual changes were made. The second patch added an extra check to see if we can use highDPI font. These two patches can be cherry-picked into X/B/D For Eoan and onward, they already have these patches. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1851623-fb-font-detect/ Patch tested on a Dell G7 UHD laptop and it works as expected, the font displayed in the early boot stage (before switching to color frame buffer device) will be set to a more readable one. Screenshots can be found in the attachment of the bug report. == Regression Potential == Low, this only affects the frame buffer, changing the way to decide which font to use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851623/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -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: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854315] Re: IPSec / xfrm memory leak found
package was not taken correctly ** Package changed: linux (Ubuntu) => linux-meta (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1854315 Title: IPSec / xfrm memory leak found Status in linux-meta package in Ubuntu: New Bug description: Hi everybody. there is a memory leak in the current kernels since 4.15 (maybe olders as well) in combination with IPSec. I verified it with kernel linux- meta 4.15.0.70.72 on Ubuntu 18.04. As Strongswan is used and users login / logout, being connected and doing traffic memory gets lost. After a while no memory is left over and OOM killer starts it work. After some debugging and asking in the Strongswan irc channel I was informed that there was a memory leak found in net/xfrm/xfrm_state.c which might be related. Here is the commit to this fix: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=86c6739eda7d2a03f2db30cbee67a5fb81afa8ba I applied this patch against the linux-meta 4.15.0.70.72 and it fixes the issue. Tested and verified on and with: Ubuntu 18.04.3 LTS strongswan-5.6.2-1ubuntu2.4 linux-image-generic-4.15.0.70.72 Here are some additional information: https://lore.kernel.org/netdev/2019062832.gp13...@gauss3.secunet.de/ https://marc.info/?l=linux-netdev=157405892918311=2 it also is reproducible with hwe and hwe-edge kernel as well as with other strongswan version. I also backported latest Ubuntu version of strongswan to 18.04 which has same behavior. On a completely different system (Gentoo) it also is the case. So I'm really sure that this is related to the reported kernel thing which is already solve in current mainline To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1854315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852432] Re: i40e: Setting VF MAC address causes General Protection Fault
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852432 Title: i40e: Setting VF MAC address causes General Protection Fault Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Confirmed Bug description: [Impact] * Creating SR-IOV enabled VMs in Openstack can sometimes trigger the GPF and leave system unusable [Test Case] * Continuously spin up VFs and set MAC address with e.g. ifconfig [Fix] * The fix updates the VSI pointer passed down to i40e_set_vf_mac function() if the adapter is still in reset, preventing the GPF. [Regression Potential] * Regression potential should be low, as we're now updating the VSI using the ID stored in the VF pointer * Regressions could arise from issues in VF creation or reset, as that would corrupt the new VSI pointer * Patch was validated and tested in a production environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852216] Re: Disable unreliable HPET on CFL-H system
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852216 Title: Disable unreliable HPET on CFL-H system Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: [Impact] TSC marked unstable by skewed HPET after Intel CFL-H SoC reached PC10 state. [Fix] Disable HPET on CFL-H SoC. [Test] I can confirm disabling HPET can workaround this issue. [Regression Potential] Low. TSC on recent Intel SoC is now an invariant clocksource, so it's harmless to disable HPET on these platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1852216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -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: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
4.15.0-1064.69 - azure Regression test CMPL, RTB. Issue to note in x86_64 (azure): ubuntu_kernel_selftests - cpu-hotplug (bug 1831543) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) port80 (bug 1748105) vmx (bug 1821394) failed on Standard_D16s_v3, Standard_D2_v3, Standard_D2s_v3, Standard_D48_v3, Standard_E2s_v3, Standard_F2s_v2, Standard_F32s_v2 ubuntu_ltp_syscalls - move_pages12 on some instances(bug 1831043) quotactl04 (bug 1854153) statx05 (bug 1798524) ubunut_qrt_apparmor - timed out on Standard-B1ms, Standard_DS15_v2, Standard_E2s_v3, Standard-F1s, Standard_F32s_v2 (bug 1783922) Skipped / blacklisted: * ubuntu_ltp ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- 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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -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: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853326] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
Tried 4.15.0-72.81 kernel on 1 socket and 2 sockets ThunderX machine and all boot ok. Thanks. ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1853326 Title: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] 4.15.0-71-generic can not boot on ThunderX Here are console logs https://pastebin.ubuntu.com/p/xcRk7VRrzF/ https://pastebin.ubuntu.com/p/DkdBqbBqqD/ [Test Case] Boot kernel with earlycon. See if kernel oops while booting. [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851607] Re: tsc failed on B-aws-5.0 / D-aws amd64 bare metal
Issue found on X-4.15 AWS (4.15.0-1056.58~16.04.1) with instance c5.metal (passed with i3.metal and r5.metal) ** Tags added: 4.15 xenial -- 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/1851607 Title: tsc failed on B-aws-5.0 / D-aws amd64 bare metal Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Bug description: Issue found on AWS i3.metal bare metal node Running 'make ' cc -O -Wall -Wpedantic -Werror -c -o checktsc.o checktsc.c cc -o checktsc checktsc.o -lpthread Running '/home/ubuntu/autotest/client/tmp/tsc/src/checktsc -t 650' Program checktsc exit status is 1 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/tsc/tsc.py", line 74, in run_once raise error.TestFail(reason) TestFail: Latency CPU 63 - CPU 50 = 746 exceeds threshold 650 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851607/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854298] Re: ubuntu_unionmount_ovlfs failed on X with latest update in upstream testsuite
It looks like this is OK with X-4.15 but not X-4.4 / T-4.4. Maybe something in the kernel has to do with this as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854298 Title: ubuntu_unionmount_ovlfs failed on X with latest update in upstream testsuite Status in ubuntu-kernel-tests: New Status in linux-signed package in Ubuntu: New Bug description: A bisect shows this test is failing since commit 2104e51db38 (Simplify initialization of __upper ) The test will fail with: /mnt/a/foo100: File unexpectedly on upper layer For the complete test log, please refer the attachment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-169-generic 4.4.0-169.198 ProcVersionSignature: User Name 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Nov 28 04:21:52 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853666] Re: Battery will not charge on Toshiba Satellite Pro A50-C-119
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853666
Title:
Battery will not charge on Toshiba Satellite Pro A50-C-119
Status in linux package in Ubuntu:
Confirmed
Bug description:
Since I have switched from Windows 10 to Ubuntu, my battery will no
longer charge. The battery shows 0% charge and says Estimating. Ubuntu
appears to detect removing the battery as the battery indicator
disappears and reappears upon replacing the battery. Unplugging the AC
adaptor with the battery plugged in causes the computer to lose power
immediately. When the computer is off with battery connected and AC
adaptor removed, the computer will not switch on. I have bought a new
battery but that produces the same problem. In Power Settings, the
battery status is shown as Charging 0%. I believe this to be an ACPI
issue. I have followed the instructions on these websites:
https://ubuntu.com/blog/debug-dsdt-ssdt-with-acpica-utilities
https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips
The acpi driver loaded is toshiba_acpi. I have extracted some
information using acpidump and acpiexec which is in the attached file
acpiexec.log.
I have delved deeper in to the issue. A search of the DSDT files
unveiled the following:
dsdt.dsl:Name (_HID, EisaId ("TOS6208")) // _HID: Hardware ID
dsdt.dsl:Name (_HID, EisaId ("TOS620A")) // _HID: Hardware ID
dsdt.dsl:Name (_HID, EisaId ("TOS6205")) // _HID: Hardware ID
dsdt.dsl:Name (_HID, "ACPI0003" /* Power Source Device */) //
_HID: Hardware ID
dsdt.dsl:Name (_HID, EisaId ("PNP0C0A") /* Control Method Battery
*/) // _HID: Hardware ID
dsdt.dsl:Name (_HID, EisaId ("TOS620D")) // _HID: Hardware ID
A search of toshiba_acpi.c shows that TOS6208 is listed as a supported
device but none of the others are. Please could someone look in to
this and add the devices to the toshiba_acpi driver if required. Many
thanks.
Linux image
linux-image-5.3.0-23-generic
cat /proc/version_signature
Ubuntu 5.3.0-23.25-generic 5.3.7
lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10
sudo lspci -vnvn
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI
[8086:1604] (rev 09)
Subsystem: Toshiba America Info Systems Broadwell-U Host Bridge -OPI
[1179:0001]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: bdw_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500
[8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:000d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
LnkCap: Port #6, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s
<1us, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (downgraded), Width x0 (downgraded)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE#
ARIFwd-
AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
ARIFwd-
AtomicOpsCtl: ReqEn- EgressBlck-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal
[Kernel-packages] [Bug 1854216] Re: Bionic update: upstream stable patchset 2019-11-27
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854216 Title: Bionic update: upstream stable patchset 2019-11-27 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-11-27 Ported from the following upstream stable releases: v4.14.156, v4.19.86 from git://git.kernel.org/ spi: mediatek: use correct mata->xfer_len when in fifo transfer tee: optee: add missing of_node_put after of_device_is_available net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size() idr: Fix idr_get_next race with idr_remove mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span() mm/memory_hotplug: fix updating the node span arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault fbdev: Ditch fb_edid_add_monspecs net: ovs: fix return type of ndo_start_xmit function net: xen-netback: fix return type of ndo_start_xmit function ARM: dts: dra7: Enable workaround for errata i870 in PCIe host mode ARM: dts: omap5: enable OTG role for DWC3 controller f2fs: return correct errno in f2fs_gc ARM: dts: sun8i: h3-h5: ir register size should be the whole memory block SUNRPC: Fix priority queue fairness IB/hfi1: Ensure ucast_dlid access doesnt exceed bounds kvm: arm/arm64: Fix stage2_flush_memslot for 4 level page table arm64/numa: Report correct memblock range for the dummy node ath10k: fix vdev-start timeout on error ata: ahci_brcm: Allow using driver or DSL SoCs ath9k: fix reporting calculated new FFT upper max usb: gadget: udc: fotg210-udc: Fix a sleep-in-atomic-context bug in fotg210_get_status() usb: dwc3: gadget: Check ENBLSLPM before sending ep command nl80211: Fix a GET_KEY reply attribute irqchip/irq-mvebu-icu: Fix wrong private data retrieval watchdog: w83627hf_wdt: Support NCT6796D, NCT6797D, NCT6798D KVM: PPC: Inform the userspace about TCE update failures dmaengine: ep93xx: Return proper enum in ep93xx_dma_chan_direction dmaengine: timb_dma: Use proper enum in td_prep_slave_sg ext4: fix build error when DX_DEBUG is defined clk: keystone: Enable TISCI clocks if K3_ARCH sunrpc: Fix connect metrics mei: samples: fix a signedness bug in amt_host_if_call() cxgb4: Use proper enum in cxgb4_dcb_handle_fw_update cxgb4: Use proper enum in IEEE_FAUX_SYNC powerpc/pseries: Fix DTL buffer registration powerpc/pseries: Fix how we iterate over the DTL entries powerpc/xive: Move a dereference below a NULL test ARM: dts: at91: sama5d4_xplained: fix addressable nand flash size ARM: dts: at91: at91sam9x5cm: fix addressable nand flash size mtd: rawnand: sh_flctl: Use proper enum for flctl_dma_fifo0_transfer PM / hibernate: Check the success of generating md5 digest before hibernation tools: PCI: Fix compilation warnings clocksource/drivers/sh_cmt: Fixup for 64-bit machines clocksource/drivers/sh_cmt: Fix clocksource width for 32-bit machines md: allow metadata updates while suspending an array - fix ixgbe: Fix ixgbe TX hangs with XDP_TX beyond queue limit i40e: Use proper enum in i40e_ndo_set_vf_link_state ixgbe: Fix crash with VFs and flow director on interface flap IB/mthca: Fix error return code in __mthca_init_one() IB/mlx4: Avoid implicit enumerated type conversion ACPICA: Never run _REG on system_memory and system_IO powerpc/time: Use clockevents_register_device(), fixing an issue with large decrementer ata: ep93xx: Use proper enums for directions media: rc: ir-rc6-decoder: enable toggle bit for Kathrein RCU-676 remote media: pxa_camera: Fix check for pdev->dev.of_node media: i2c: adv748x: Support probing a single output ALSA: hda/sigmatel - Disable automute for Elo VuPoint KVM: PPC: Book3S PR: Exiting split hack mode needs to fixup both PC and LR USB: serial: cypress_m8: fix interrupt-out transfer length mtd: physmap_of: Release resources on error cpu/SMT: State SMT is disabled even with nosmt and without "=force" brcmfmac: reduce timeout for action frame scan brcmfmac: fix full timeout waiting for action frame on-channel tx qtnfmac: pass sgi rate info flag to wireless core qtnfmac: drop error reports for out-of-bounds key indexes clk: samsung: exynos5420: Define CLK_SECKEY
[Kernel-packages] [Bug 1854229] Re: Disco update: upstream stable patchset 2019-11-27
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854229
Title:
Disco update: upstream stable patchset 2019-11-27
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-11-27
Ported from the following upstream stable releases:
v4.19.86, v5.3.13
from git://git.kernel.org/
i2c: mediatek: modify threshold passed to i2c_get_dma_safe_msg_buf()
Revert "OPP: Protect dev_list with opp_table lock"
net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size()
mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span()
mm/memory_hotplug: fix updating the node span
arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault
fbdev: Ditch fb_edid_add_monspecs
bpf, x32: Fix bug for BPF_ALU64 | BPF_NEG
bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_X shift by 0
bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_K shift by 0
bpf, x32: Fix bug for BPF_JMP | {BPF_JSGT, BPF_JSLE, BPF_JSLT, BPF_JSGE}
bpf: btf: Fix a missing check bug
UBUNTU: upstream stable to v4.19.86, v5.3.13
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854229/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853659] Re: Disco update: upstream stable patchset 2019-11-22
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853659 Title: Disco update: upstream stable patchset 2019-11-22 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-11-22 Ported from the following upstream stable releases: v4.19.84, v5.3.11 from git://git.kernel.org/ bonding: fix state transition issue in link monitoring CDC-NCM: handle incomplete transfer of MTU ipv4: Fix table id reference in fib_sync_down_addr net: ethernet: octeon_mgmt: Account for second possible VLAN header net: fix data-race in neigh_event_send() net: qualcomm: rmnet: Fix potential UAF when unregistering net: usb: qmi_wwan: add support for DW5821e with eSIM support NFC: fdp: fix incorrect free object nfc: netlink: fix double device reference drop NFC: st21nfca: fix double free qede: fix NULL pointer deref in __qede_remove() net: mscc: ocelot: don't handle netdev events for other netdevs net: mscc: ocelot: fix NULL pointer on LAG slave removal ipv6: fixes rt6_probe() and fib6_nh->last_probe init net: hns: Fix the stray netpoll locks causing deadlock in NAPI path ALSA: timer: Fix incorrectly assigned timer instance ALSA: bebob: fix to detect configured source of sampling clock for Focusrite Saffire Pro i/o series ALSA: hda/ca0132 - Fix possible workqueue stall mm: memcontrol: fix network errors from failing __GFP_ATOMIC charges mm, meminit: recalculate pcpu batch and high limits after init completes mm: thp: handle page cache THP correctly in PageTransCompoundMap mm, vmstat: hide /proc/pagetypeinfo from normal users dump_stack: avoid the livelock of the dump_lock tools: gpio: Use !building_out_of_srctree to determine srctree perf tools: Fix time sorting drm/radeon: fix si_enable_smc_cac() failed issue HID: wacom: generic: Treat serial number and related fields as unsigned soundwire: depend on ACPI soundwire: bus: set initial value to port_status arm64: Do not mask out PTE_RDONLY in pte_same() ceph: fix use-after-free in __ceph_remove_cap() ceph: add missing check in d_revalidate snapdir handling iio: adc: stm32-adc: fix stopping dma iio: imu: adis16480: make sure provided frequency is positive iio: srf04: fix wrong limitation in distance measuring ARM: sunxi: Fix CPU powerdown on A83T netfilter: nf_tables: Align nft_expr private data to 64-bit netfilter: ipset: Fix an error code in ip_set_sockfn_get() intel_th: pci: Add Comet Lake PCH support intel_th: pci: Add Jasper Lake PCH support x86/apic/32: Avoid bogus LDR warnings SMB3: Fix persistent handles reconnect can: usb_8dev: fix use-after-free on disconnect can: flexcan: disable completely the ECC mechanism can: c_can: c_can_poll(): only read status register after status IRQ can: peak_usb: fix a potential out-of-sync while decoding packets can: rx-offload: can_rx_offload_queue_sorted(): fix error handling, avoid skb mem leak can: gs_usb: gs_can_open(): prevent memory leak can: dev: add missing of_node_put() after calling of_get_child_by_name() can: mcba_usb: fix use-after-free on disconnect can: peak_usb: fix slab info leak configfs: stash the data we need into configfs_buffer at open time configfs_register_group() shouldn't be (and isn't) called in rmdirable parts configfs: new object reprsenting tree fragments configfs: provide exclusion between IO and removals configfs: fix a deadlock in configfs_symlink() ALSA: usb-audio: More validations of descriptor units ALSA: usb-audio: Simplify parse_audio_unit() ALSA: usb-audio: Unify the release of usb_mixer_elem_info objects ALSA: usb-audio: Remove superfluous bLength checks ALSA: usb-audio: Clean up check_input_term() ALSA: usb-audio: Fix possible NULL dereference at create_yamaha_midi_quirk() ALSA: usb-audio: remove some dead code ALSA: usb-audio: Fix copy error in the validator usbip: Fix vhci_urb_enqueue() URB null transfer buffer error path usbip: Implement SG support to vhci-hcd and stub driver PCI: tegra: Enable Relaxed Ordering only for Tegra20 & Tegra30 HID: google: add magnemite/masterball USB ids dmaengine: xilinx_dma: Fix control reg update in vdma_channel_set_config dmaengine:
[Kernel-packages] [Bug 1854094] Re: Disco update: upstream stable patchset 2019-11-26
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854094 Title: Disco update: upstream stable patchset 2019-11-26 Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-11-26 Ported from the following upstream stable releases: v4.19.85, v5.3.12 from git://git.kernel.org/ KVM: x86: introduce is_pae_paging scsi: core: Handle drivers which set sg_tablesize to zero ax88172a: fix information leak on short answers ipmr: Fix skb headroom in ipmr_get_route(). net: gemini: add missed free_netdev net: usb: qmi_wwan: add support for Foxconn T77W968 LTE modules slip: Fix memory leak in slip_open error path ALSA: usb-audio: Fix missing error check at mixer resolution test ALSA: usb-audio: not submit urb for stopped endpoint ALSA: usb-audio: Fix incorrect NULL check in create_yamaha_midi_quirk() ALSA: usb-audio: Fix incorrect size check for processing/extension units Btrfs: fix log context list corruption after rename exchange operation Input: ff-memless - kill timer in destroy() Input: synaptics-rmi4 - fix video buffer size Input: synaptics-rmi4 - disable the relative position IRQ in the F12 driver Input: synaptics-rmi4 - do not consume more data than we have (F11, F12) Input: synaptics-rmi4 - clear IRQ enables for F54 Input: synaptics-rmi4 - destroy F54 poller workqueue when removing IB/hfi1: Ensure full Gen3 speed in a Gen4 system IB/hfi1: Use a common pad buffer for 9B and 16B packets i2c: acpi: Force bus speed to 400KHz if a Silead touchscreen is present ecryptfs_lookup_interpose(): lower_dentry->d_inode is not stable ecryptfs_lookup_interpose(): lower_dentry->d_parent is not stable either net: ethernet: dwmac-sun8i: Use the correct function in exit path iommu/vt-d: Fix QI_DEV_IOTLB_PFSID and QI_DEV_EIOTLB_PFSID macros mm: mempolicy: fix the wrong return value and potential pages leak of mbind mm: memcg: switch to css_tryget() in get_mem_cgroup_from_mm() mm: hugetlb: switch to css_tryget() in hugetlb_cgroup_charge_cgroup() mmc: sdhci-of-at91: fix quirk2 overwrite dmaengine: at_xdmac: remove a stray bottom half unlock slcan: Fix memory leak in error path tcp: remove redundant new line from tcp_event_sk_skb dpaa2-eth: free already allocated channels on probe defer KVM: MMU: Do not treat ZONE_DEVICE pages as being reserved drm/i915: update rawclk also on resume ntp/y2038: Remove incorrect time_t truncation mm/page_io.c: do not free shared swap slots UBUNTU: upstream stable to v4.19.85, v5.3.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
Reply to comment #3, it's a regression in the kernel side, not the DKMS as 4.4.0-169 works just fine. Bisecting. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852306 Title: xenial/linux: 4.4.0-170.199 -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: Incomplete 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 verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854298] [NEW] ubuntu_unionmount_ovlfs failed on X with latest update in upstream testsuite
Public bug reported: A bisect shows this test is failing since commit 2104e51db38 (Simplify initialization of __upper ) The test will fail with: /mnt/a/foo100: File unexpectedly on upper layer For the complete test log, please refer the attachment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-169-generic 4.4.0-169.198 ProcVersionSignature: User Name 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Nov 28 04:21:52 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug sru-2019 ubuntu-unionmount-ovlfs uec-images xenial ** Attachment added: "ubuntu_unionmount_ovlfs.log" https://bugs.launchpad.net/bugs/1854298/+attachment/5308322/+files/ubuntu_unionmount_ovlfs.log ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: sru-2019 ** Tags added: ubuntu-unionmount-ovlfs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854298 Title: ubuntu_unionmount_ovlfs failed on X with latest update in upstream testsuite Status in ubuntu-kernel-tests: New Status in linux-signed package in Ubuntu: New Bug description: A bisect shows this test is failing since commit 2104e51db38 (Simplify initialization of __upper ) The test will fail with: /mnt/a/foo100: File unexpectedly on upper layer For the complete test log, please refer the attachment. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-169-generic 4.4.0-169.198 ProcVersionSignature: User Name 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Nov 28 04:21:52 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
Also tried removal of that dkms, wifi is still good on both 169 and 170. No hang found on both. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497457] ---[ end trace
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
Not reproducible on 4.4.0-169-generic, so it's a kernel regression. By the way, amdgpu-pro DKMS 16.60-377537 doesn't compile on at least 4.4.0-169-generic and newer, should file a separate bug later. ** No longer affects: linux-signed (Ubuntu) ** No longer affects: linux-signed (Ubuntu Xenial) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ?
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Thank Lucas, It just happened to my laptop. I will try find out the solution. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
For X-Azure 4.15, it's not happening on all the instances, spotted on * Standard_DS15_v2 * Standard_D48_v3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: New Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
** Tags added: sru-2019 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: New Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831543] Re: Standard_A2_v2 Azure instance will have CPU in offline state
** Tags added: amd64 -- 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/1831543 Title: Standard_A2_v2 Azure instance will have CPU in offline state Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Bug description: This needs to be investigated to see if it's been disabled intentionally. The cpu-hot-plug test shows there are 126 offlined CPUs. selftests: cpu-on-off-test.sh pid 9824's current affinity mask: 3 pid 9824's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 2-127 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831543] Re: Standard_A2_v2 Azure instance will have CPU in offline state
** Tags added: sru-2019 -- 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/1831543 Title: Standard_A2_v2 Azure instance will have CPU in offline state Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Bug description: This needs to be investigated to see if it's been disabled intentionally. The cpu-hot-plug test shows there are 126 offlined CPUs. selftests: cpu-on-off-test.sh pid 9824's current affinity mask: 3 pid 9824's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 2-127 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852857] Re: Use more modern Raven Ridge firmware in linux-firmware package
Yes, git bisecting. You may want to bisect commits related to those raven2_* blobs, which should be much less work to do. It's also possible the fix is actually consisted of multiple commits, so when you locate the first good commit, please cherry-pick it onto Bionic HEAD and make sure if that alone fixes this issue. If not, then we'd need to locate the second one, and so on. Thank you. :) -- 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/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package Status in linux-firmware package in Ubuntu: New Bug description: I own a: CPU: AMD Ryzen 5 2500U GPU: AMD Raven Ridge (Vega 8) Laptop model: Lenovo IdeaPad 330S (330S-15ARR) Description: Ubuntu 18.04.3 LTS Release: 18.04 linux-firmware: Installed: 1.173.12 Candidate: 1.173.12 Version table: *** 1.173.12 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 1.173 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The firmware provided by Ubuntu 18.04 is too old and causes frequent system freezes, particularly when using the web browser. When it freezes, the mouse is the only thing that works, but the GPU gets completely locked up. Keyboard also gets locked up (even Num Lock doesn't respond). There are no crash reports automatically generated. The logs get corrupted so it's impossible to know what happened. Updating it to a new firmware version fixes all freezes and system stability becomes rock solid. I'm not sure which exactly is the relevant firmware file, but I'm using these: fe5ec673b44d95c686a240a8d138f499 raven2_asd.bin a671f876b7ea6ff9f93dc56e0e147157 raven2_ce.bin be6c5c565ec341ee69f6d99a0ecb109d raven2_gpu_info.bin 5d7b9b404c424c692342cc1408553025 raven2_me.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec2.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec.bin 4d7651ab7fc4dba1abcfaf4a88f40686 raven2_pfp.bin 4ac07f88b9c4aa4fe026be87cb16ceda raven2_rlc.bin ac3a488f651921bc5a21b5a443ee7c23 raven2_sdma.bin 2372175130589c169afc4bc0e0435705 raven2_vcn.bin fe5ec673b44d95c686a240a8d138f499 raven_asd.bin 3e4aeb199a9e1c56a398d5b4ff6a7166 raven_ce.bin b5387b400b0ee4b04565a5179aebb9cd raven_dmcu.bin 052cdc264b228656dff12b95def55c54 raven_gpu_info.bin b16a081785f2f75a6f326ca5ca92113d raven_me.bin 4390c8485f4d4583ae878aa227968a48 raven_mec2.bin 4390c8485f4d4583ae878aa227968a48 raven_mec.bin f69ef2e297e66eb68eecb02540780f4c raven_pfp.bin 0e5fff019103b4cdc5a0366e29411fdd raven_rlc.bin df5f1ef96feade475a9c83451d840bb3 raven_sdma.bin 7e22527c2ef5e9b6e4e871d6ec546848 raven_vcn.bin There's the possibility that I'm wrong and the actually firmware file is not related to Raven Ridge (I doubt it, my usage when it freezes points to being a GPU problem) More specifically I'm using these https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tag/?h=20190815 I have been working with these new firmware files for months and no crashes. Yesterday linux-firmware was updated reverting my changes, and it started locking up again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi tronglx, I didn't try Arch but I THINK I tried Manjaro which is based on it. If I did it didn't work. I remember trying lots of linux and all of them failed. Qubes OS works because it doesn't use linux kernels directly because it uses Xen microkernel, so somehow it excludes the bug. You can install Arch as a Qubes VM, there's a script for it, you just run it and then it generates an image that you can install. They also provide Ubuntu, Kali and others. Since this bug is rare I don't think they'll try to fix, the guy that was helping here gave up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Shih-Yuan Lee (fourdollars) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-signed source package in Xenial: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] []
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Thank Lucas, do you have tried with arch linux? Qubes OS is very strange with me. I'm developer and os community is very importance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
@Askshay, This is the new image you could have a try with. http://cdimage.ubuntu.com/ubuntu-server/eoan/daily- preinstalled/20191126.2/ And "100% happen" means it will freeze every time you reboot and input the password to login. Thanks. -- 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/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847389] Re: Prevent bpool (or pools with /BOOT/) to be upgraded
If the pool has an _active_ (and not "read-only compatible") feature that GRUB does not understand, then GRUB will (correctly) refuse to load the pool. Accordingly, you will be unable to boot. Some features go active immediately, and others need you to enable some filesystem-level feature or take some other action to go from enabled to active. The features that are left disabled in the upstream Root-on-ZFS HOWTO (that I manage) are disabled because GRUB does not support them. At best, you never use them and it's fine. At worst, you make one active and then you can't boot. Since you can't use them without breaking booting, there is no point in having them enabled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1847389 Title: Prevent bpool (or pools with /BOOT/) to be upgraded Status in zfs-linux package in Ubuntu: New Bug description: The bpool status is confusing. Should I upgrade the pool or is it on purpose that the bpool is like this. I do no like to see this warning after installing the system on ZFS from scratch. See screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809206]
I've recently hit this seem issue, this is caused by the hp-wmi driver passing a buffer which is not big enough when making WMI related ACPI calls. I've submitted a patch-series which fixes this upstream: https://lore.kernel.org/patchwork/project/lkml/list/?series=419906 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809206 Title: Amd ACPI Error Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Hi Hp Laptop Amd A10 9600p Ubuntu 18.10 Kernel: all kernel acpi error mesg | grep Error [3.546921] RAS: Correctable Errors collector initialized. [9.979321] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.979438] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.979484] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.979764] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.979872] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.988903] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.989220] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.989318] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.989358] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990180] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.990274] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990312] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990557] ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20180531/dsopcode-201) [9.990646] ACPI Error: Method parse/execution failed \HWMC, AE_AML_BUFFER_LIMIT (20180531/psparse-516) [9.990682] ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20180531/psparse-516) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1809206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852266] Re: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852266 Title: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Thanks for this sultan, this is useful information. Forgot to mention that I was able to get help in fixing the bug, turns out I needed a newer version of alsa-lib, had to switch to Fedora to get a packaged version but I can confirm audio on my laptop is working now... https://bugzilla.redhat.com/show_bug.cgi?id=1775732 ** Bug watch added: Red Hat Bugzilla #1775732 https://bugzilla.redhat.com/show_bug.cgi?id=1775732 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
Hui Wang - Does it 100% happen? --> I'm not sure what you meant by this, it happened on repeated attempts, till the point I just formatted my SD card. Did you login through keyboard/ssh connection/usb-serial console? --> I logged in using a keyboard. Last could you please try the Image of #36. --> Your next comments asks us not to try this, so is there a fresh install I can try that fixes this ? -- 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/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854229] [NEW] Disco update: upstream stable patchset 2019-11-27
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-11-27
Ported from the following upstream stable releases:
v4.19.86, v5.3.13
from git://git.kernel.org/
i2c: mediatek: modify threshold passed to i2c_get_dma_safe_msg_buf()
Revert "OPP: Protect dev_list with opp_table lock"
net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size()
mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span()
mm/memory_hotplug: fix updating the node span
arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault
fbdev: Ditch fb_edid_add_monspecs
bpf, x32: Fix bug for BPF_ALU64 | BPF_NEG
bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_X shift by 0
bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_K shift by 0
bpf, x32: Fix bug for BPF_JMP | {BPF_JSGT, BPF_JSLE, BPF_JSLT, BPF_JSGE}
bpf: btf: Fix a missing check bug
UBUNTU: upstream stable to v4.19.86, v5.3.13
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2019-11-27
-upstream stable patchset 2019-11-27
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.19.86, v5.3.13
+
+ from git://git.kernel.org/
+
+ i2c: mediatek: modify threshold passed to i2c_get_dma_safe_msg_buf()
+ Revert "OPP: Protect dev_list with opp_table lock"
+ net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size()
+ mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span()
+ mm/memory_hotplug: fix updating the node span
+ arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault
+ fbdev: Ditch fb_edid_add_monspecs
+ bpf, x32: Fix bug for BPF_ALU64 | BPF_NEG
+ bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_X shift by 0
+ bpf, x32: Fix bug with ALU64 {LSH, RSH, ARSH} BPF_K shift by 0
+ bpf, x32: Fix bug for BPF_JMP | {BPF_JSGT, BPF_JSLE, BPF_JSLT, BPF_JSGE}
+ bpf: btf: Fix a missing check bug
+ UBUNTU: upstream stable to v4.19.86, v5.3.13
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1854229
Title:
Disco update: upstream stable patchset 2019-11-27
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Disco:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
upstream stable patchset 2019-11-27
Ported from the following upstream stable releases:
v4.19.86, v5.3.13
from git://git.kernel.org/
[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Looks like you are missing UCM config files (due to an outdated ALSA UCM package that's not in sync with the kernel). This is what causes the "Audio Port: ASoC: no backend DAIs enabled for Audio Port" messages. See this thread: https://bugzilla.kernel.org/show_bug.cgi?id=115531#c43 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853666] Re: Battery will not charge on Toshiba Satellite Pro A50-C-119
** Description changed:
Since I have switched from Windows 10 to Ubuntu, my battery will no
longer charge. The battery shows 0% charge and says Estimating. Ubuntu
appears to detect removing the battery as the battery indicator
disappears and reappears upon replacing the battery. Unplugging the AC
adaptor with the battery plugged in causes the computer to lose power
immediately. When the computer is off with battery connected and AC
adaptor removed, the computer will not switch on. I have bought a new
battery but that produces the same problem. In Power Settings, the
battery status is shown as Charging 0%. I believe this to be an ACPI
issue. I have followed the instructions on these websites:
https://ubuntu.com/blog/debug-dsdt-ssdt-with-acpica-utilities
https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips
The acpi driver loaded is toshiba_acpi. I have extracted some
information using acpidump and acpiexec which is in the attached file
acpiexec.log.
+
+ I have delved deeper in to the issue. A search of the DSDT files
+ unveiled the following:
+
+ dsdt.dsl:Name (_HID, EisaId ("TOS6208")) // _HID: Hardware ID
+ dsdt.dsl:Name (_HID, EisaId ("TOS620A")) // _HID: Hardware ID
+ dsdt.dsl:Name (_HID, EisaId ("TOS6205")) // _HID: Hardware ID
+ dsdt.dsl:Name (_HID, "ACPI0003" /* Power Source Device */) //
_HID: Hardware ID
+ dsdt.dsl:Name (_HID, EisaId ("PNP0C0A") /* Control Method Battery
*/) // _HID: Hardware ID
+ dsdt.dsl:Name (_HID, EisaId ("TOS620D")) // _HID: Hardware ID
+
+ A search of toshiba_acpi.c shows that TOS6208 is listed as a supported
+ device but none of the others are. Please could someone look in to this
+ and add the devices to the toshiba_acpi driver if required. Many thanks.
Linux image
linux-image-5.3.0-23-generic
cat /proc/version_signature
Ubuntu 5.3.0-23.25-generic 5.3.7
lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10
sudo lspci -vnvn
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI
[8086:1604] (rev 09)
Subsystem: Toshiba America Info Systems Broadwell-U Host Bridge -OPI
[1179:0001]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-
Kernel driver in use: bdw_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 5500
[8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:000d]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr+ TransPend-
LnkCap: Port #6, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s
<1us, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (downgraded), Width x0 (downgraded)
TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+
Slot #0, PowerLimit 0.000W; Interlock- NoCompl+
SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+
Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock-
SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock-
Changed: MRL- PresDet- LinkState-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID , PMEStatus- PMEPending-
DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE#
ARIFwd-
AtomicOpsCap: Routing- 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled
ARIFwd-
AtomicOpsCtl: ReqEn- EgressBlck-
LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
Transmit Margin: Normal Operating Range, EnterModifiedCompliance-
ComplianceSOS-
Compliance De-emphasis: -6dB
LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-,
EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee01004
[Kernel-packages] [Bug 1848739] Re: [linux-azure] Patch to prevent possible data corruption
https://lists.ubuntu.com/archives/kernel-team/2019-November/105876.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/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
Status in linux-azure package in Ubuntu:
Confirmed
Status in linux-azure source package in Xenial:
In Progress
Bug description:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852266] Re: bionic/linux-oem: 4.15.0-1065.75 -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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1852266 Title: bionic/linux-oem: 4.15.0-1065.75 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1854027 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Thursday, 21. November 2019 15:15 UTC reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852275] Re: xenial/linux-oracle: 4.15.0-1030.33~16.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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852275 Title: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 09:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852277] Re: bionic/linux-oracle: 4.15.0-1030.33 -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-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852277 Title: bionic/linux-oracle: 4.15.0-1030.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 19:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1852275 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -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: In Progress 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: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 25. November 2019 12:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852273] Re: bionic/linux-kvm: 4.15.0-1051.51 -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-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1852273 Title: bionic/linux-kvm: 4.15.0-1051.51 -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: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854027] Re: bionic/linux: 4.15.0-72.81 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854027 Title: bionic/linux: 4.15.0-72.81 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: 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: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 27. November 2019 02:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854029 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1854012 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1854010 bionic/linux-snapdragon: bug 1854013 bionic/linux/pc-kernel: bug 1854024 bionic/linux/pc-lowlatency-kernel: bug 1854025 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1854026 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852285] Re: xenial/linux-gcp: 4.15.0-1050.53 -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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1852285 Title: xenial/linux-gcp: 4.15.0-1050.53 -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 verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Thursday, 14. November 2019 22:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1852283 xenial/linux-gcp/gke-kernel: bug 1852284 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852285/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854013] Re: bionic/linux-snapdragon: 4.15.0-1069.76 -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-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1854013 Title: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 27. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1854011 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854010] Re: bionic/linux-raspi2: 4.15.0-1052.56 -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-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1854010 Title: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1854027 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 27. November 2019 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854009 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854029] Re: bionic/linux-aws: 4.15.0-1056.58 -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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854029 Title: bionic/linux-aws: 4.15.0-1056.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 27. November 2019 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1854028 xenial/linux-aws-hwe: bug 1854030 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848739] Re: [linux-azure] Patch to prevent possible data corruption
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Xenial)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
--
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/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
Status in linux-azure package in Ubuntu:
Confirmed
Status in linux-azure source package in Xenial:
In Progress
Bug description:
There are three patches that prevent possible data corruption. The
three commits are:
aef1897cd36d ("blk-mq: insert rq with DONTPREP to hctx dispatch list when
requeue")
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
923218f6166a ("blk-mq: don't allocate driver tag upfront for flush rq")
18.04 has all three of these patches. 16.04 has two out of the three,
but it is missing commit c616cbee97ae.
We would like to request commit c616cbee97ae be included in the 16.04 kernel:
c616cbee97ae ("blk-mq: punt failed direct issue to dispatch list")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1848739/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852277] Re: bionic/linux-oracle: 4.15.0-1030.33 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 19:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1852275 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/1852277 Title: bionic/linux-oracle: 4.15.0-1030.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 20. November 2019 19:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-oracle: bug 1852275 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854216] [NEW] Bionic update: upstream stable patchset 2019-11-27
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-11-27 Ported from the following upstream stable releases: v4.14.156, v4.19.86 from git://git.kernel.org/ spi: mediatek: use correct mata->xfer_len when in fifo transfer tee: optee: add missing of_node_put after of_device_is_available net: cdc_ncm: Signedness bug in cdc_ncm_set_dgram_size() idr: Fix idr_get_next race with idr_remove mm/memory_hotplug: don't access uninitialized memmaps in shrink_pgdat_span() mm/memory_hotplug: fix updating the node span arm64: uaccess: Ensure PAN is re-enabled after unhandled uaccess fault fbdev: Ditch fb_edid_add_monspecs net: ovs: fix return type of ndo_start_xmit function net: xen-netback: fix return type of ndo_start_xmit function ARM: dts: dra7: Enable workaround for errata i870 in PCIe host mode ARM: dts: omap5: enable OTG role for DWC3 controller f2fs: return correct errno in f2fs_gc ARM: dts: sun8i: h3-h5: ir register size should be the whole memory block SUNRPC: Fix priority queue fairness IB/hfi1: Ensure ucast_dlid access doesnt exceed bounds kvm: arm/arm64: Fix stage2_flush_memslot for 4 level page table arm64/numa: Report correct memblock range for the dummy node ath10k: fix vdev-start timeout on error ata: ahci_brcm: Allow using driver or DSL SoCs ath9k: fix reporting calculated new FFT upper max usb: gadget: udc: fotg210-udc: Fix a sleep-in-atomic-context bug in fotg210_get_status() usb: dwc3: gadget: Check ENBLSLPM before sending ep command nl80211: Fix a GET_KEY reply attribute irqchip/irq-mvebu-icu: Fix wrong private data retrieval watchdog: w83627hf_wdt: Support NCT6796D, NCT6797D, NCT6798D KVM: PPC: Inform the userspace about TCE update failures dmaengine: ep93xx: Return proper enum in ep93xx_dma_chan_direction dmaengine: timb_dma: Use proper enum in td_prep_slave_sg ext4: fix build error when DX_DEBUG is defined clk: keystone: Enable TISCI clocks if K3_ARCH sunrpc: Fix connect metrics mei: samples: fix a signedness bug in amt_host_if_call() cxgb4: Use proper enum in cxgb4_dcb_handle_fw_update cxgb4: Use proper enum in IEEE_FAUX_SYNC powerpc/pseries: Fix DTL buffer registration powerpc/pseries: Fix how we iterate over the DTL entries powerpc/xive: Move a dereference below a NULL test ARM: dts: at91: sama5d4_xplained: fix addressable nand flash size ARM: dts: at91: at91sam9x5cm: fix addressable nand flash size mtd: rawnand: sh_flctl: Use proper enum for flctl_dma_fifo0_transfer PM / hibernate: Check the success of generating md5 digest before hibernation tools: PCI: Fix compilation warnings clocksource/drivers/sh_cmt: Fixup for 64-bit machines clocksource/drivers/sh_cmt: Fix clocksource width for 32-bit machines md: allow metadata updates while suspending an array - fix ixgbe: Fix ixgbe TX hangs with XDP_TX beyond queue limit i40e: Use proper enum in i40e_ndo_set_vf_link_state ixgbe: Fix crash with VFs and flow director on interface flap IB/mthca: Fix error return code in __mthca_init_one() IB/mlx4: Avoid implicit enumerated type conversion ACPICA: Never run _REG on system_memory and system_IO powerpc/time: Use clockevents_register_device(), fixing an issue with large decrementer ata: ep93xx: Use proper enums for directions media: rc: ir-rc6-decoder: enable toggle bit for Kathrein RCU-676 remote media: pxa_camera: Fix check for pdev->dev.of_node media: i2c: adv748x: Support probing a single output ALSA: hda/sigmatel - Disable automute for Elo VuPoint KVM: PPC: Book3S PR: Exiting split hack mode needs to fixup both PC and LR USB: serial: cypress_m8: fix interrupt-out transfer length mtd: physmap_of: Release resources on error cpu/SMT: State SMT is disabled even with nosmt and without "=force" brcmfmac: reduce timeout for action frame scan brcmfmac: fix full timeout waiting for action frame on-channel tx qtnfmac: pass sgi rate info flag to wireless core qtnfmac: drop error reports for out-of-bounds key indexes clk: samsung: exynos5420: Define CLK_SECKEY gate clock only or Exynos5420 clk: samsung: Use clk_hw API for calling clk framework from clk notifiers i2c: brcmstb: Allow enabling the driver on DSL SoCs NFSv4.x: fix lock recovery during delegation recall dmaengine: ioat: fix prototype of ioat_enumerate_channels media: cec-gpio: select correct Signal Free Time Input: st1232 - set INPUT_PROP_DIRECT property Input: silead - try firmware reload after unsuccessful resume remoteproc: Check for NULL firmwares in sysfs interface kexec: Allocate decrypted control pages for kdump if SME is enabled x86/olpc: Fix build
[Kernel-packages] [Bug 1854013] Re: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 27. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1854011 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/1854013 Title: bionic/linux-snapdragon: 4.15.0-1069.76 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 27. November 2019 10:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1854011 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854207] 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 1854207 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) 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/1854207 Title: Unrevert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: We reverted a couple changes in 4.15.0-72.81 because they were causing a regression (bug 1853326) that was not understood at press time: b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hvc_*" 5f395b984282e Revert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" This bug is to track the reapplication of these patches, once we've figured out the underlying issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832151] Re: Unexpected CFS throttling
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => Fix Committed ** Changed in: linux-azure (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1832151 Title: Unexpected CFS throttling Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in linux-azure source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux-azure source package in Eoan: Invalid Bug description: Basically, this issue: https://bugzilla.kernel.org/show_bug.cgi?id=198197 ..is affecting a cloud provider on a 4.15 kernel. Customer testing with a kernel that is patched with the fix (upstream: de53fd7aedb100f03e5d2231cfce0e4993282425 ) confirms that it resolves the issue. More details in the SalesForce ticket: https://canonical.my.salesforce.com/5003z1yUmC1 [Impact] * Aggressive throttling by CFS causes severe performance degradation in some cases. [Test Case] * This reproducer clearly shows the problem before the fix and shows no problem after the fix: https://gist.github.com/bobrik/2030ff040fad360327a5fab7a09c4ff1 [Regression Potential] * It touches core scheduler code so regression could be bad - but risk is low as the patch is accepted in mainline and tested separately by myself, the cloud provider, and at least 2 others. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852241] Re: bionic/linux-gcp: 5.0.0-1026.27~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 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/1852241 Title: bionic/linux-gcp: 5.0.0-1026.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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852244 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Friday, 15. November 2019 23:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1852240 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852241/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1853116 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1853901 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 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/1852253 Title: disco/linux: 5.0.0-37.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: 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: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-bluefield: bug 1852252 bionic/linux-hwe: bug 1852250 bionic/linux-oem-osp1: bug 1853116 disco/linux-aws: bug 1852236 disco/linux-azure: bug 1853901 disco/linux-gcp: bug 1852244 disco/linux-kvm: bug 1852245 disco/linux-oracle: bug 1852248 disco/linux-raspi2: bug 1852233 disco/linux-snapdragon: bug 1852249 unknown/unknown: bug 1852245 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853712] Re: linux-cloud-tools-*-azure package is not installed when installing linux-azure-edge
** Also affects: linux-azure-5.3 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Invalid ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure-5.3 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-azure-5.3 (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-azure-5.3 (Ubuntu Bionic) Assignee: (unassigned) => Marcelo Cerri (mhcerri) ** Changed in: linux-azure-5.3 (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1853712 Title: linux-cloud-tools-*-azure package is not installed when installing linux-azure-edge Status in linux-azure package in Ubuntu: Invalid Status in linux-azure-5.3 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-5.3 source package in Bionic: Fix Committed Bug description: While installing linux-azure package, it installs linux-cloud-tools- azure Bionic + linux-azure The following NEW packages will be installed: linux-azure linux-azure-cloud-tools-5.0.0-1024 linux-azure-headers-5.0.0-1024 linux-azure-tools-5.0.0-1024 linux-cloud-tools-5.0.0-1024-azure linux-cloud-tools-azure linux-headers-5.0.0-1024-azure linux-headers-azure linux-image-5.0.0-1024-azure linux-image-azure linux-modules-5.0.0-1024-azure linux-tools-5.0.0-1024-azure linux-tools-azure 0 upgraded, 13 newly installed, 0 to remove and 280 not upgraded. But during linux-azure-edge package installation, it does not install linux-cloud-tools-azure Bionic + linux-azure-edge The following NEW packages will be installed: crda iw libnl-genl-3-200 linux-azure-5.3-headers-5.3.0-1006 linux-azure-edge linux-headers-5.3.0-1006-azure linux-headers-azure-edge linux-image-5.3.0-1006-azure linux-image-azure-edge linux-modules-5.3.0-1006-azure linux-modules-extra-5.3.0-1006-azure wireless-regdb 0 upgraded, 12 newly installed, 0 to remove and 280 not upgraded. Can we have linux-cloud-tools-azure package included as well. Let me know, if you have any questions. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1853712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854207] [NEW] Unrevert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2"
Public bug reported: We reverted a couple changes in 4.15.0-72.81 because they were causing a regression (bug 1853326) that was not understood at press time: b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hvc_*" 5f395b984282e Revert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" This bug is to track the reapplication of these patches, once we've figured out the underlying issue. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854207 Title: Unrevert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: We reverted a couple changes in 4.15.0-72.81 because they were causing a regression (bug 1853326) that was not understood at press time: b042ff6848684 Revert "arm64: Get rid of __smccc_workaround_1_hvc_*" 5f395b984282e Revert "arm64: Use firmware to detect CPUs that are not affected by Spectre-v2" This bug is to track the reapplication of these patches, once we've figured out the underlying issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854207/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853326] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX
Tracking the reapplication of the reverted patches in bug 1854207. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853326 Title: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] 4.15.0-71-generic can not boot on ThunderX Here are console logs https://pastebin.ubuntu.com/p/xcRk7VRrzF/ https://pastebin.ubuntu.com/p/DkdBqbBqqD/ [Test Case] Boot kernel with earlycon. See if kernel oops while booting. [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851947] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308272/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308267/+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/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308271/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308263/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308261/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308270/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308262/+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/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308265/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308266/+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/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308268/+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/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308269/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1851947/+attachment/5308264/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851947 Title: nvidia Status in linux package in Ubuntu: Incomplete Bug description: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1851947] Re: nvidia
apport information ** Description changed: I have a bug which affects me every day. Gnome 3.28.2 shakespeare@RYZEN:~$ uname -r 5.0.0-33-generic I have a 4K display with a ROG 1060 using NVIDIA driver metapackage from nvidia-driver-435 (proprietary, tested). I have no other additional drivers. My CPU is an AMD Ryzen 7 1700X Eight-Core Processor. family(23) model(1) stepping(1) I have 32GB RAM and 15GB swap total. My lsb_release is shakespeare@RYZEN:~$ lsb_release -rd Description: Ubuntu 18.04.3 Release:18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 5127 F pulseaudio /dev/snd/controlC1: shakespeare 5127 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (45 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-33.35~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.173.11 RfKill: Tags: bionic Uname: Linux 5.0.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shakespeare 2093 F pulseaudio /dev/snd/controlC1: shakespeare 2093 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-09-25 (57 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=d54a3591-810b-4e60-bc6b-a70fcda75a38 ro scsi_mod.scan=sync quiet splash nouveau.modeset=0 vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.12 RfKill: Tags: bionic Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B350-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB350-FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.10 + Architecture: amd64 +
[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 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/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress 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: In Progress 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852857] Re: Use more modern Raven Ridge firmware in linux-firmware package
You mean bisecting the git commits from mainline linux-firmware; compare it against https://kernel.ubuntu.com/git/ubuntu/linux- firmware.git/log/?h=bionic until I isolate the culprit(s)? Yes I can do that. It will take a while though (laptop needs to reboot with every attempt, it may take a while to crash, etc) Does anyone know if: service lightdm stop rmmod amdgpu modprobe amdgpu service lightdm start will reupload the firmware blob? That would speed up the testing process tremendously. -- 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/1852857 Title: Use more modern Raven Ridge firmware in linux-firmware package Status in linux-firmware package in Ubuntu: New Bug description: I own a: CPU: AMD Ryzen 5 2500U GPU: AMD Raven Ridge (Vega 8) Laptop model: Lenovo IdeaPad 330S (330S-15ARR) Description: Ubuntu 18.04.3 LTS Release: 18.04 linux-firmware: Installed: 1.173.12 Candidate: 1.173.12 Version table: *** 1.173.12 500 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ar.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status 1.173 500 500 http://ar.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The firmware provided by Ubuntu 18.04 is too old and causes frequent system freezes, particularly when using the web browser. When it freezes, the mouse is the only thing that works, but the GPU gets completely locked up. Keyboard also gets locked up (even Num Lock doesn't respond). There are no crash reports automatically generated. The logs get corrupted so it's impossible to know what happened. Updating it to a new firmware version fixes all freezes and system stability becomes rock solid. I'm not sure which exactly is the relevant firmware file, but I'm using these: fe5ec673b44d95c686a240a8d138f499 raven2_asd.bin a671f876b7ea6ff9f93dc56e0e147157 raven2_ce.bin be6c5c565ec341ee69f6d99a0ecb109d raven2_gpu_info.bin 5d7b9b404c424c692342cc1408553025 raven2_me.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec2.bin 81f2957c4512ec2595bb1dbdc37f52ca raven2_mec.bin 4d7651ab7fc4dba1abcfaf4a88f40686 raven2_pfp.bin 4ac07f88b9c4aa4fe026be87cb16ceda raven2_rlc.bin ac3a488f651921bc5a21b5a443ee7c23 raven2_sdma.bin 2372175130589c169afc4bc0e0435705 raven2_vcn.bin fe5ec673b44d95c686a240a8d138f499 raven_asd.bin 3e4aeb199a9e1c56a398d5b4ff6a7166 raven_ce.bin b5387b400b0ee4b04565a5179aebb9cd raven_dmcu.bin 052cdc264b228656dff12b95def55c54 raven_gpu_info.bin b16a081785f2f75a6f326ca5ca92113d raven_me.bin 4390c8485f4d4583ae878aa227968a48 raven_mec2.bin 4390c8485f4d4583ae878aa227968a48 raven_mec.bin f69ef2e297e66eb68eecb02540780f4c raven_pfp.bin 0e5fff019103b4cdc5a0366e29411fdd raven_rlc.bin df5f1ef96feade475a9c83451d840bb3 raven_sdma.bin 7e22527c2ef5e9b6e4e871d6ec546848 raven_vcn.bin There's the possibility that I'm wrong and the actually firmware file is not related to Raven Ridge (I doubt it, my usage when it freezes points to being a GPU problem) More specifically I'm using these https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/tag/?h=20190815 I have been working with these new firmware files for months and no crashes. Yesterday linux-firmware was updated reverting my changes, and it started locking up again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 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/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress 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: In Progress 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854027] Re: bionic/linux: 4.15.0-72.81 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 27. November 2019 02:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED + automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854029 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1854012 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1854010 bionic/linux-snapdragon: bug 1854013 bionic/linux/pc-kernel: bug 1854024 bionic/linux/pc-lowlatency-kernel: bug 1854025 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1854026 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/1854027 Title: bionic/linux: 4.15.0-72.81 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: 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: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 27. November 2019 02:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854029 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1854012 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1854010 bionic/linux-snapdragon: bug 1854013 bionic/linux/pc-kernel: bug 1854024 bionic/linux/pc-lowlatency-kernel: bug 1854025 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1854026 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854146] Re: Kernel oops on 5.3.0-18
Maybe try 5.3.0.24.28? $ rmadison linux-generic linux-generic | 5.3.0.24.28| eoan-proposed| amd64, arm64, armhf, ppc64el, s390x linux-generic | 5.3.0.24.28| focal-proposed | amd64, arm64, armhf, ppc64el, s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854146 Title: Kernel oops on 5.3.0-18 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date @ 27/11/2019 2 kernel oops occured https://errors.ubuntu.com/oops/bae189ae-1070-11ea-a61f-fa163ee63de6 https://errors.ubuntu.com/oops/75853dda-0b73-11ea-b03e-fa163e983629 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 2871 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 27 11:14:16 2019 InstallationDate: Installed on 2019-10-25 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=b5dfba6b-1ac7-4113-8538-36b84cb54969 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854146/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854177] 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/1854177 Title: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2 Status in linux package in Ubuntu: Confirmed Bug description: Present testing has focused on closing the laptop lid and reopening it. The laptop suspends as expected and resumes as expected (existing ssh sessions start working again) except that the display remains black and calls such as `xset -display :0 dpms force on` hang. The screen remains blank sSometimes for a few minutes, sometimes for many. In the example log it was 10 minutes and a few seconds before the display turned back on. One time trying to capture a log of the recovery I gave up after 70 minutes. While the display is black `/var/log/Xorg.0.log` repeats the following lines once per second. [ 119.384] (WW) modeset(0): hotplug event: connector 86's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails... [ 119.386] (II) modeset(0): EDID vendor "SDC", prod id 16705 [ 119.386] (II) modeset(0): Printing DDC gathered Modelines: [ 119.386] (II) modeset(0): Modeline "3840x2160"x0.0 545.12 3840 3888 3920 4160 2160 2164 2168 2184 +hsync -vsync (131.0 kHz eP) This stops when the display turns on and no other messages are logged. The journalctl log has a much longer repeated sequence of messages. I haven't confirmed exact matching of the whole repeated block but here's a snippet reporting a failure. Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Max Voltage Swing reached Nov 27 00:02:32 p1 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:86:eDP-1] Link Training failed at link rate = 54, lane count = 4 When the display turned back on I instead get the following success message. Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] clock recovery OK Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS3 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_start_link_train [i915]] Channel EQ done. DP Training successful I tested the mainline .deb package for 5.3.13 and it did not exhibit this issue. When I open the laptop lid after suspending by closing it the cursor reliably displays within about 1 second and the lock screen is shown within about another second. I further checked versions and the last mainline .deb to exhibit the issue is 5.3.11. 5.3.12 works well. Looking at the changelog for 5.3.12 showed the following two commits
[Kernel-packages] [Bug 1852586] Re: Boot hangs after "Loading initial ramdisk ..."
Oh, and run dpkg as root, or use sudo dpkg -i linux*tpmrevert*deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852586 Title: Boot hangs after "Loading initial ramdisk ..." Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Kernel 5.3.0.-23-generic and Kernel 5.3.0.-22-generic don't boot, I get the "Loading initial ramdisk ..." on purple background, nothing happens, Notebook need to get shutoff to resume Kernels: 5.3.0-19 and 5.3.0-18 do work It's a Lenovo L580 Running Ubuntu 19.10 output of version signature: Ubuntu 5.3.0-19.20-generic 5.3.1 output of lscpi: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e34] (rev 0c) Subsystem: Lenovo Device [17aa:5075] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5075] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [17aa:5075] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [17aa:5075] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd 00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] (rev 30) Subsystem: Lenovo Cannon Point-LP Shared SRAM [17aa:5075] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.2 Serial bus controller [0c80]: Intel Corporation Device [8086:9dea] (rev 30) Subsystem: Lenovo Device [17aa:5075] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
[Kernel-packages] [Bug 1852586] Re: Boot hangs after "Loading initial ramdisk ..."
Just download the linux-image, linux-modules and linux-modules-extra deb files, and dpkg -i linux*tpmrevert*deb. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852586 Title: Boot hangs after "Loading initial ramdisk ..." Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Kernel 5.3.0.-23-generic and Kernel 5.3.0.-22-generic don't boot, I get the "Loading initial ramdisk ..." on purple background, nothing happens, Notebook need to get shutoff to resume Kernels: 5.3.0-19 and 5.3.0-18 do work It's a Lenovo L580 Running Ubuntu 19.10 output of version signature: Ubuntu 5.3.0-19.20-generic 5.3.1 output of lscpi: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e34] (rev 0c) Subsystem: Lenovo Device [17aa:5075] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5075] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [17aa:5075] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [17aa:5075] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd 00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] (rev 30) Subsystem: Lenovo Cannon Point-LP Shared SRAM [17aa:5075] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.2 Serial bus controller [0c80]: Intel Corporation Device [8086:9dea] (rev 30) Subsystem: Lenovo Device [17aa:5075] Control: I/O-
[Kernel-packages] [Bug 1853900] Re: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 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/1853900 Title: bionic/linux-azure: 5.0.0-1027.29~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress 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: In Progress 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1853901 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure/azure-kernel: bug 1853899 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854029] Re: bionic/linux-aws: 4.15.0-1056.58 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 27. November 2019 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1854028 xenial/linux-aws-hwe: bug 1854030 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/1854029 Title: bionic/linux-aws: 4.15.0-1056.58 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 27. November 2019 11:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1854028 xenial/linux-aws-hwe: bug 1854030 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854029/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854177] [NEW] Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2
Public bug reported: Present testing has focused on closing the laptop lid and reopening it. The laptop suspends as expected and resumes as expected (existing ssh sessions start working again) except that the display remains black and calls such as `xset -display :0 dpms force on` hang. The screen remains blank sSometimes for a few minutes, sometimes for many. In the example log it was 10 minutes and a few seconds before the display turned back on. One time trying to capture a log of the recovery I gave up after 70 minutes. While the display is black `/var/log/Xorg.0.log` repeats the following lines once per second. [ 119.384] (WW) modeset(0): hotplug event: connector 86's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails... [ 119.386] (II) modeset(0): EDID vendor "SDC", prod id 16705 [ 119.386] (II) modeset(0): Printing DDC gathered Modelines: [ 119.386] (II) modeset(0): Modeline "3840x2160"x0.0 545.12 3840 3888 3920 4160 2160 2164 2168 2184 +hsync -vsync (131.0 kHz eP) This stops when the display turns on and no other messages are logged. The journalctl log has a much longer repeated sequence of messages. I haven't confirmed exact matching of the whole repeated block but here's a snippet reporting a failure. Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Max Voltage Swing reached Nov 27 00:02:32 p1 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:86:eDP-1] Link Training failed at link rate = 54, lane count = 4 When the display turned back on I instead get the following success message. Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] clock recovery OK Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS3 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_start_link_train [i915]] Channel EQ done. DP Training successful I tested the mainline .deb package for 5.3.13 and it did not exhibit this issue. When I open the laptop lid after suspending by closing it the cursor reliably displays within about 1 second and the lock screen is shown within about another second. I further checked versions and the last mainline .deb to exhibit the issue is 5.3.11. 5.3.12 works well. Looking at the changelog for 5.3.12 showed the following two commits referencing i915 (don't let me mislead you here of course, just trying to provide as much info as possible). The first one strikes me as relevant but I haven't applied that patch to the Ubuntu 5.3.0-23 kernel and built it for testing. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2f216a8507153578efc309c821528a6b81628cd2 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ed77d88752aea56b33731aee42e7146379b90769 ProblemType: Bug
[Kernel-packages] [Bug 1854010] Re: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854027 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 27. November 2019 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854009 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/1854010 Title: bionic/linux-raspi2: 4.15.0-1052.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1854027 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 27. November 2019 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854009 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854177] Re: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2
** Attachment added: "xorg-2019-11-26T23_56_26-05_00.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854177/+attachment/5308164/+files/xorg-2019-11-26T23_56_26-05_00.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/1854177 Title: Black screen after resume from suspend on Lenovo ThinkPad P1 Gen 2 Status in linux package in Ubuntu: New Bug description: Present testing has focused on closing the laptop lid and reopening it. The laptop suspends as expected and resumes as expected (existing ssh sessions start working again) except that the display remains black and calls such as `xset -display :0 dpms force on` hang. The screen remains blank sSometimes for a few minutes, sometimes for many. In the example log it was 10 minutes and a few seconds before the display turned back on. One time trying to capture a log of the recovery I gave up after 70 minutes. While the display is black `/var/log/Xorg.0.log` repeats the following lines once per second. [ 119.384] (WW) modeset(0): hotplug event: connector 86's link-state is BAD, tried resetting the current mode. You may be leftwith a black screen if this fails... [ 119.386] (II) modeset(0): EDID vendor "SDC", prod id 16705 [ 119.386] (II) modeset(0): Printing DDC gathered Modelines: [ 119.386] (II) modeset(0): Modeline "3840x2160"x0.0 545.12 3840 3888 3920 4160 2160 2164 2168 2184 +hsync -vsync (131.0 kHz eP) This stops when the display turns on and no other messages are logged. The journalctl log has a much longer repeated sequence of messages. I haven't confirmed exact matching of the whole repeated block but here's a snippet reporting a failure. Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:02:32 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Max Voltage Swing reached Nov 27 00:02:32 p1 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:86:eDP-1] Link Training failed at link rate = 54, lane count = 4 When the display turned back on I instead get the following success message. Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] Using LINK_RATE_SET value 02 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0400 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 1 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using signal levels 0700 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using vswing level 2 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis level 0 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_link_training_clock_recovery [i915]] clock recovery OK Nov 27 00:07:22 p1 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP training pattern TPS3 Nov 27 00:07:22 p1 kernel: [drm:intel_dp_start_link_train [i915]] Channel EQ done. DP Training successful I tested the mainline .deb package for 5.3.13 and it did not exhibit this issue. When I open the laptop lid after suspending by closing it the cursor reliably displays within about 1 second and the lock screen is shown within about another second. I further checked versions and the last mainline .deb to exhibit the issue is 5.3.11. 5.3.12 works
[Kernel-packages] [Bug 1853901] Re: disco/linux-azure: 5.0.0-1027.29 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1853900 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/1853901 Title: disco/linux-azure: 5.0.0-1027.29 -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: In Progress 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: In Progress 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852253 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Tuesday, 26. November 2019 11:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-azure: bug 1853900 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1853901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854027] Re: bionic/linux: 4.15.0-72.81 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 27. November 2019 02:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854029 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1854012 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1854010 bionic/linux-snapdragon: bug 1854013 bionic/linux/pc-kernel: bug 1854024 bionic/linux/pc-lowlatency-kernel: bug 1854025 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1854026 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/1854027 Title: bionic/linux: 4.15.0-72.81 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: 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: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Wednesday, 27. November 2019 02:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854029 bionic/linux-fips: bug 1852278 bionic/linux-gke-4.15: bug 1852272 bionic/linux-ibm-gt: bug 1854012 bionic/linux-kvm: bug 1852273 bionic/linux-oem: bug 1852266 bionic/linux-oracle: bug 1852277 bionic/linux-raspi2: bug 1854010 bionic/linux-snapdragon: bug 1854013 bionic/linux/pc-kernel: bug 1854024 bionic/linux/pc-lowlatency-kernel: bug 1854025 xenial/linux-azure: bug 1852282 xenial/linux-gcp: bug 1852285 xenial/linux-hwe: bug 1854026 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854027/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi tronglx, the only way I found was to install Qubes OS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi lucas, i have the same problem. My laptop is matebook x pro 2018 and nvme LITEON CA3-8D512. My working is on linux and it is an unpleasant experience. Currently, when issue occurs, i power off/on my laptop (one times or more) and it can work normally in a few hours. Do you have any another suggest about linux distributions? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago)
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
@Rex, is it possible to get a list of platforms has oem-wifi-intel- iwlwifi-*-dkms installed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-signed source package in Xenial: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
The following tests were perform: - tested with 4.4.0-169 (Pass) - re-install the system, dist-upgrade, tested with 4.4.0-170 (Fail, still reproducible) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-signed source package in Xenial: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-signed source package in Xenial: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497452] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497454] [] ret_from_fork+0x55/0x80 Nov 27 18:40:01 201701-25364 kernel: [ 600.497456] [] ? kthread_create_on_node+0x1e0/0x1e0 Nov 27
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress + certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 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/1852306 Title: xenial/linux: 4.4.0-170.199 -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: Incomplete 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 verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854114] Re: My 4K display goes black screen when I updated my NVIDIA driver from 340 to 435
RE: #2 I think so, just to add: pretty much every available driver I tried that was more recent than the v340, the same thing happened. So there must be something that happens for nvidia drivers 340+. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1854114 Title: My 4K display goes black screen when I updated my NVIDIA driver from 340 to 435 Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: Here's what happened: I have Ubuntu 19.10 installed + NVIDIA driver 340 + 4K screen. Everything works file. I upgraded my NVIDIA driver to 435 and then everything is still fine until the login screen. When I enter my password, the screen goes black. So, I connected my old HD monitor, rebooted, and it worked! Funny thing is that, when I'm logged in the OS, if I reconnect my 4K monitor, it works! But if I restart my system, the problem persists. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:03:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Nov 26 19:21:07 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-23-generic, x86_64: installed openrazer-driver, 2.6.0, 5.3.0-22-generic, x86_64: installed openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM107GL [Quadro K2200] [10de:13ba] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM107GL [Quadro K2200] [10de:1097] InstallationDate: Installed on 2019-10-18 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Precision Tower 5810 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=ab778d32-5ce1-4c38-a14e-2024d96eb5d3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/24/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A32 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA32:bd09/24/2019:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA02:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.product.sku: 0617 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-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.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 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-435/+bug/1854114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852306] Re: xenial/linux: 4.4.0-170.199 -proposed tracker
A potential regression was found https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854156 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852306 Title: xenial/linux: 4.4.0-170.199 -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: Incomplete 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 verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 14. November 2019 18:50 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1852304 trusty/linux-lts-xenial: bug 1852305 xenial/linux-aws: bug 1852296 xenial/linux-cascade: bug 1852297 xenial/linux-fips: bug 1852303 xenial/linux-kvm: bug 1852298 xenial/linux-raspi2: bug 1852300 xenial/linux-snapdragon: bug 1852302 xenial/linux/caracalla-kernel: bug 1852291 xenial/linux/pc-kernel: bug 1852292 xenial/linux/stlouis-kernel: bug 1852293 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
** Summary changed: - [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-genericproposed kernel + [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-signed (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-signed source package in Xenial: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] [] dump_stack+0x63/0x82 Nov 27 18:40:01 201701-25364 kernel: [ 600.497433] [] warn_slowpath_common+0x82/0xc0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497435] [] warn_slowpath_null+0x1a/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497436] [] __blk_mq_run_hw_queue+0x305/0x3a0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497439] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497440] [] ? __schedule+0x30d/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497441] [] ? __schedule+0x301/0x810 Nov 27 18:40:01 201701-25364 kernel: [ 600.497443] [] blk_mq_run_work_fn+0x12/0x20 Nov 27 18:40:01 201701-25364 kernel: [ 600.497445] [] process_one_work+0x16b/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497446] [] worker_thread+0x4e/0x590 Nov 27 18:40:01 201701-25364 kernel: [ 600.497447] [] ? process_one_work+0x4e0/0x4e0 Nov 27 18:40:01 201701-25364 kernel: [ 600.497449] [] kthread+0xe7/0x100 Nov 27 18:40:01 201701-25364 kernel: [ 600.497450] [] ?
[Kernel-packages] [Bug 1854156] Re: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel
The dkms was updated at 29 Mar 2019 ubuntu@201701-25364:/tmp$ dkms status amdgpu-pro, 16.60-377537, 4.4.0-127-generic, x86_64: installed amdgpu-pro, 16.60-377537, 4.4.0-49-generic, x86_64: installed oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-127-generic, x86_64: installed oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-170-generic, x86_64: installed oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms, 2.0, 4.4.0-170-generic, x86_64: installed ubuntu@201701-25364:/tmp$ apt -o Debug::Acquire::http=true download oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms 0% [Working]GET /updates/pool/public/o/oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms/oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms_2.0_all.deb HTTP/1.1 Host: dell.archive.canonical.com User-Agent: Debian APT-HTTP/1.3 (1.2.32) 0% [Waiting for headers]Answer for: http://dell.archive.canonical.com/updates/pool/public/o/oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms/oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms_2.0_all.deb HTTP/1.1 200 OK Date: Wed, 27 Nov 2019 14:24:39 GMT Server: Apache/2.4.7 (Ubuntu) Last-Modified: Fri, 29 Mar 2019 10:56:31 GMT ETag: "6f5c20-5853985faf5c0" Accept-Ranges: bytes Content-Length: 7298080 Content-Type: application/x-debian-package Get:1 http://dell.archive.canonical.com/updates xenial-dell/public amd64 oem-wifi-intel-iwlwifi-lp1757035-4.4-dkms-dkms all 2.0 [7298 kB] Fetched 7298 kB in 3s (1978 kB/s) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854156 Title: [8086:24f3] intel Corporation Wireless 8260 regression of 4.4.0-170-generic proposed kernel Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-signed source package in Xenial: New Bug description: When connecting bg-open wifi, the system will freeze. Hardware: Dell Precision 5720 AIO (CID 201701-25364) Kernel: 4.4.0-170-generic #199-Ubuntu SMP Thu Nov 14 01:45:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Image: pre-installed image (xenial 4.4 based) [Steps to Reproduce] 1. install the target image 2. when the system is ready, connect to wifi(bg-open channel) over network-manager applet. [Expected Result] Connection established [Actual Result] System freezed [Reproducing Rate] 100% (5 out of 5) [Additional Info] I was sometimes able to catch the following kernel oops Nov 27 18:40:01 201701-25364 kernel: [ 600.497340] [ cut here ] Nov 27 18:40:01 201701-25364 kernel: [ 600.497345] WARNING: CPU: 0 PID: 30 at /build/linux-AweC5P/linux-4.4.0/block/blk-mq.c:794 __blk_mq_run_hw_queue+0x305/0x3a0() Nov 27 18:40:01 201701-25364 kernel: [ 600.497346] Modules linked in: nvram msr rfcomm cmac bnep uvcvideo videobuf2_vmalloc videobuf2_memops btusb videobuf2_v4l2 videobuf2_core btrtl v4l2_common btbcm btintel videodev bluetooth m edia ecdh_generic input_leds joydev hid_multitouch arc4 dell_led i2c_designware_platform i2c_designware_core dell_wmi snd_hda_codec_realtek(OE) sparse_keymap snd_hda_codec_generic(OE) i915_bpo dcdbas dell_smm_hwmon intel_ips drm_k ms_helper intel_rapl x86_pkg_temp_thermal iwlmvm(OE) intel_powerclamp coretemp drm kvm_intel mac80211(OE) i2c_algo_bit fb_sys_fops syscopyarea kvm sysfillrect sysimgblt snd_hda_intel(OE) snd_hda_codec(OE) irqbypass snd_hda_core(OE ) crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel aesni_intel aes_x86_64 lrw snd_pcm gf128mul iwlwifi(OE) glue_helper ablk_helper cryptd snd_seq_midi snd_seq_midi_event cfg80211(OE) snd_rawmidi snd_seq serio_raw snd_se q_device snd_timer rtsx_pci_ms compat(OE) snd memstick idma64 soundcore virt_dma mei_me intel_lpss_pci mei shpchp intel_lpss 8250_fintek mac_hid acpi_pad parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror dm_region_h ash dm_log hid_generic usbhid hid mmc_block uas usb_storage rtsx_pci_sdmmc psmouse e1000e ptp pps_core rtsx_pci ahci nvme libahci wmi video fjes Nov 27 18:40:01 201701-25364 kernel: [ 600.497418] CPU: 0 PID: 30 Comm: kworker/4:0H Tainted: G OE 4.4.0-170-generic #199-Ubuntu Nov 27 18:40:01 201701-25364 kernel: [ 600.497419] Hardware name: Dell Inc. Precision 5720 AIO/, BIOS 2.3.6 01/31/2018 Nov 27 18:40:01 201701-25364 kernel: [ 600.497421] Workqueue: kblockd blk_mq_run_work_fn Nov 27 18:40:01 201701-25364 kernel: [ 600.497422] 0286 3b6f2186023dc8e9 8808394dbd30 8140cde1 Nov 27 18:40:01 201701-25364 kernel: [ 600.497424] 81d07a88 8808394dbd68 81086492 Nov 27 18:40:01 201701-25364 kernel: [ 600.497425] 880831d52400 8808394dbda0 88085dd15f80 88085dd1b400 Nov 27 18:40:01 201701-25364 kernel: [ 600.497427] Call Trace: Nov 27 18:40:01 201701-25364 kernel: [ 600.497430] []
[Kernel-packages] [Bug 1852586] Re: Boot hangs after "Loading initial ramdisk ..."
Hi, can you post a brief howto? I didn't install kernels outside of apt for some time -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852586 Title: Boot hangs after "Loading initial ramdisk ..." Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Kernel 5.3.0.-23-generic and Kernel 5.3.0.-22-generic don't boot, I get the "Loading initial ramdisk ..." on purple background, nothing happens, Notebook need to get shutoff to resume Kernels: 5.3.0-19 and 5.3.0-18 do work It's a Lenovo L580 Running Ubuntu 19.10 output of version signature: Ubuntu 5.3.0-19.20-generic 5.3.1 output of lscpi: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e34] (rev 0c) Subsystem: Lenovo Device [17aa:5075] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5075] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [17aa:5075] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [17aa:5075] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd 00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] (rev 30) Subsystem: Lenovo Cannon Point-LP Shared SRAM [17aa:5075] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.2 Serial bus controller [0c80]: Intel Corporation Device [8086:9dea] (rev 30) Subsystem: Lenovo Device [17aa:5075] Control: I/O- Mem+ BusMaster+ SpecCycle-
[Kernel-packages] [Bug 1852586] Re: Boot hangs after "Loading initial ramdisk ..."
Can you try the test package at [1]? [1] https://people.canonical.com/~cascardo/tpmrevert1/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852586 Title: Boot hangs after "Loading initial ramdisk ..." Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Kernel 5.3.0.-23-generic and Kernel 5.3.0.-22-generic don't boot, I get the "Loading initial ramdisk ..." on purple background, nothing happens, Notebook need to get shutoff to resume Kernels: 5.3.0-19 and 5.3.0-18 do work It's a Lenovo L580 Running Ubuntu 19.10 output of version signature: Ubuntu 5.3.0-19.20-generic 5.3.1 output of lscpi: 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e34] (rev 0c) Subsystem: Lenovo Device [17aa:5075] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5075] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, OBFF Not Supported AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [17aa:5075] Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [17aa:5075] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd 00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] (rev 30) Subsystem: Lenovo Cannon Point-LP Shared SRAM [17aa:5075] Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.2 Serial bus controller [0c80]: Intel Corporation Device [8086:9dea] (rev 30) Subsystem: Lenovo Device [17aa:5075] Control: I/O- Mem+ BusMaster+
