[Kernel-packages] [Bug 1856813] Re: Touchpad on X1 Carbon G6 is slow and sloppy
Found the fix in focal-proposed linux_5.4.0-9.12.diff.gz ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: rls-ee-incoming ** Summary changed: - Touchpad on X1 Carbon G6 is slow and sloppy + Touchpad on X1 Carbon G6 (LEN0091) is slow and sloppy -- 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/1856813 Title: Touchpad on X1 Carbon G6 (LEN0091) is slow and sloppy Status in linux package in Ubuntu: Fix Committed Bug description: Touchpad on X1 Carbon G6 is slow and sloppy Because: [2.101906] psmouse serio1: synaptics: Your touchpad (PNP: LEN0091 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. Adding kernel parameter psmouse.synaptics_intertouch=1 indeed fixes it. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Dec 18 14:09:51 2019 InstallationDate: Installed on 2019-12-18 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20KGS4XY00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=204dc145-c221-45e3-99f4-45107dc1b8d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS4XY00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KGS4XY00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS4XY00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS4XY00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856949] Re: cifs: kernel NULL pointer dereference, address: 0000000000000038
** Description changed:
- [598428.945633] BUG: kernel NULL pointer dereference, address:
0038
- ...
- [598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
- [598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
- ...
- [598428.945834] Call Trace:
- [598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
- [598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
- [598428.945909] process_one_work+0x1db/0x380
- [598428.945914] worker_thread+0x4d/0x400
- [598428.945921] kthread+0x104/0x140
- [598428.945925] ? process_one_work+0x380/0x380
- [598428.945931] ? kthread_park+0x80/0x80
- [598428.945937] ret_from_fork+0x35/0x40
+ [Impact]
+
+ Currently when the client creates a cifsFileInfo structure for
+ a newly opened file, it allocates a list of byte-range locks
+ with a pointer to the new cfile and attaches this list to the
+ inode's lock list. The latter happens before initializing all
+ other fields, e.g. cfile->tlink. Thus a partially initialized
+ cifsFileInfo structure becomes available to other threads that
+ walk through the inode's lock list. One example of such a thread
+ may be an oplock break worker thread that tries to push all
+ cached byte-range locks. This causes NULL-pointer dereference
+ in smb2_push_mandatory_locks() when accessing cfile->tlink:
+
+ [598428.945633] BUG: kernel NULL pointer dereference, address:
0038
+ ...
+ [598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
+ [598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
+ ...
+ [598428.945834] Call Trace:
+ [598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
+ [598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
+ [598428.945909] process_one_work+0x1db/0x380
+ [598428.945914] worker_thread+0x4d/0x400
+ [598428.945921] kthread+0x104/0x140
+ [598428.945925] ? process_one_work+0x380/0x380
+ [598428.945931] ? kthread_park+0x80/0x80
+ [598428.945937] ret_from_fork+0x35/0x40
+
+
+ [Test Case]
+
+ TBD.
+
+
+ [Fix]
+
+ Backport commit 6f582b273ec23332074d970a7fb25bef835df71f ("CIFS: Fix
+ NULL-pointer dereference in smb2_push_mandatory_locks")
+
+ [Regression Potential]
+
+ Low. The patch is fairly simple and it's tagged for stable kernels. In
+ fact it is already in some of the released upstream stable kernels.
** No longer affects: linux (Ubuntu Focal)
--
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/1856949
Title:
cifs: kernel NULL pointer dereference, address: 0038
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Status in linux source package in Bionic:
Incomplete
Status in linux source package in Disco:
Incomplete
Status in linux source package in Eoan:
Incomplete
Bug description:
[Impact]
Currently when the client creates a cifsFileInfo structure for
a newly opened file, it allocates a list of byte-range locks
with a pointer to the new cfile and attaches this list to the
inode's lock list. The latter happens before initializing all
other fields, e.g. cfile->tlink. Thus a partially initialized
cifsFileInfo structure becomes available to other threads that
walk through the inode's lock list. One example of such a thread
may be an oplock break worker thread that tries to push all
cached byte-range locks. This causes NULL-pointer dereference
in smb2_push_mandatory_locks() when accessing cfile->tlink:
[598428.945633] BUG: kernel NULL pointer dereference, address:
0038
...
[598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
[598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
...
[598428.945834] Call Trace:
[598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
[598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
[598428.945909] process_one_work+0x1db/0x380
[598428.945914] worker_thread+0x4d/0x400
[598428.945921] kthread+0x104/0x140
[598428.945925] ? process_one_work+0x380/0x380
[598428.945931] ? kthread_park+0x80/0x80
[598428.945937] ret_from_fork+0x35/0x40
[Test Case]
TBD.
[Fix]
Backport commit 6f582b273ec23332074d970a7fb25bef835df71f ("CIFS: Fix
NULL-pointer dereference in smb2_push_mandatory_locks")
[Regression Potential]
Low. The patch is fairly simple and it's tagged for stable kernels. In
fact it is already in some of the released upstream stable kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856949/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856949] 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 1856949
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
** Changed in: linux (Ubuntu Disco)
Status: New => Incomplete
** Changed in: linux (Ubuntu Eoan)
Status: New => Incomplete
** Changed in: linux (Ubuntu Xenial)
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/1856949
Title:
cifs: kernel NULL pointer dereference, address: 0038
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Status in linux source package in Bionic:
Incomplete
Status in linux source package in Disco:
Incomplete
Status in linux source package in Eoan:
Incomplete
Bug description:
[Impact]
Currently when the client creates a cifsFileInfo structure for
a newly opened file, it allocates a list of byte-range locks
with a pointer to the new cfile and attaches this list to the
inode's lock list. The latter happens before initializing all
other fields, e.g. cfile->tlink. Thus a partially initialized
cifsFileInfo structure becomes available to other threads that
walk through the inode's lock list. One example of such a thread
may be an oplock break worker thread that tries to push all
cached byte-range locks. This causes NULL-pointer dereference
in smb2_push_mandatory_locks() when accessing cfile->tlink:
[598428.945633] BUG: kernel NULL pointer dereference, address:
0038
...
[598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
[598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
...
[598428.945834] Call Trace:
[598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
[598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
[598428.945909] process_one_work+0x1db/0x380
[598428.945914] worker_thread+0x4d/0x400
[598428.945921] kthread+0x104/0x140
[598428.945925] ? process_one_work+0x380/0x380
[598428.945931] ? kthread_park+0x80/0x80
[598428.945937] ret_from_fork+0x35/0x40
[Test Case]
TBD.
[Fix]
Backport commit 6f582b273ec23332074d970a7fb25bef835df71f ("CIFS: Fix
NULL-pointer dereference in smb2_push_mandatory_locks")
[Regression Potential]
Low. The patch is fairly simple and it's tagged for stable kernels. In
fact it is already in some of the released upstream stable kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856949/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856949] [NEW] cifs: kernel NULL pointer dereference, address: 0000000000000038
Public bug reported:
[Impact]
Currently when the client creates a cifsFileInfo structure for
a newly opened file, it allocates a list of byte-range locks
with a pointer to the new cfile and attaches this list to the
inode's lock list. The latter happens before initializing all
other fields, e.g. cfile->tlink. Thus a partially initialized
cifsFileInfo structure becomes available to other threads that
walk through the inode's lock list. One example of such a thread
may be an oplock break worker thread that tries to push all
cached byte-range locks. This causes NULL-pointer dereference
in smb2_push_mandatory_locks() when accessing cfile->tlink:
[598428.945633] BUG: kernel NULL pointer dereference, address: 0038
...
[598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
[598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
...
[598428.945834] Call Trace:
[598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
[598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
[598428.945909] process_one_work+0x1db/0x380
[598428.945914] worker_thread+0x4d/0x400
[598428.945921] kthread+0x104/0x140
[598428.945925] ? process_one_work+0x380/0x380
[598428.945931] ? kthread_park+0x80/0x80
[598428.945937] ret_from_fork+0x35/0x40
[Test Case]
TBD.
[Fix]
Backport commit 6f582b273ec23332074d970a7fb25bef835df71f ("CIFS: Fix
NULL-pointer dereference in smb2_push_mandatory_locks")
[Regression Potential]
Low. The patch is fairly simple and it's tagged for stable kernels. In
fact it is already in some of the released upstream stable kernels.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
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/1856949
Title:
cifs: kernel NULL pointer dereference, address: 0038
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Xenial:
Incomplete
Status in linux source package in Bionic:
Incomplete
Status in linux source package in Disco:
Incomplete
Status in linux source package in Eoan:
Incomplete
Bug description:
[Impact]
Currently when the client creates a cifsFileInfo structure for
a newly opened file, it allocates a list of byte-range locks
with a pointer to the new cfile and attaches this list to the
inode's lock list. The latter happens before initializing all
other fields, e.g. cfile->tlink. Thus a partially initialized
cifsFileInfo structure becomes available to other threads that
walk through the inode's lock list. One example of such a thread
may be an oplock break worker thread that tries to push all
cached byte-range locks. This causes NULL-pointer dereference
in smb2_push_mandatory_locks() when accessing cfile->tlink:
[598428.945633] BUG: kernel NULL pointer dereference, address:
0038
...
[598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
[598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
...
[598428.945834] Call Trace:
[598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
[598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
[598428.945909] process_one_work+0x1db/0x380
[598428.945914] worker_thread+0x4d/0x400
[598428.945921] kthread+0x104/0x140
[598428.945925] ? process_one_work+0x380/0x380
[598428.945931] ? kthread_park+0x80/0x80
[598428.945937] ret_from_fork+0x35/0x40
[Test Case]
TBD.
[Fix]
Backport commit 6f582b273ec23332074d970a7fb25bef835df71f ("CIFS: Fix
NULL-pointer dereference in smb2_push_mandatory_locks")
[Regression Potential]
Low. The patch is fairly simple and it's tagged for stable kernels. In
fact it is already in some of the released upstream stable kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856949/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: - bionic/linux-hwe: bug 1856210, bug 1856849 + bionic/linux-hwe: bug 1856849 eoan/linux-oracle: bug 1854755 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-hwe: bug 1856849 eoan/linux-oracle: bug 1854755 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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)
Thank Lucas. -- 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 root=UUID=0ca062da-7e8f-425a-88b1-1f784fb40346 ro quiet splash
[Kernel-packages] [Bug 1848898] Re: /home/user/lspci-vnvn.log
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848898 Title: /home/user/lspci-vnvn.log Status in linux package in Ubuntu: Expired Bug description: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 03) Subsystem: Acer Incorporated [ALI] Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [1025:008f] 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: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 915GM/GMS/910GML Express Graphics Controller [1025:008f] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] 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- Kernel driver in use: i915 Kernel modules: i915, intelfb 00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 03) Subsystem: Acer Incorporated [ALI] Mobile 915GM/GMS/910GML Express Graphics Controller [1025:008f] 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- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag+ RBE- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 2.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, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #2, PowerLimit 6.500W; 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- Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: Data: Capabilities: [90] Subsystem: Acer Incorporated [ALI] 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [1025:008f] Capabilities: [a0] 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] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed+ WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- VC1:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00 Status:
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
non nvme SSDs are pretty slow, like 8 times slower. Stick with NVME and if nothing works install Qubes -- 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 1746340] Re: Samsung SSD corruption (fsck needed)
Thank you. My SSD is LITEON CA3-8D512, not Samsung. So, would i buy another type of SSD? non nvme? -- 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 1856872] Re: Realtek btusb dongle vanishes after resume from suspend
In case you happen to have 'tlp' installed, please uninstall that. -- 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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.01 Cls=ef(misc ) Sub=02 Prot=01
[Kernel-packages] [Bug 1856872] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313749/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=02
[Kernel-packages] [Bug 1856872] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313747/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#=
[Kernel-packages] [Bug 1856872] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313757/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01
[Kernel-packages] [Bug 1856872] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313754/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01
[Kernel-packages] [Bug 1856872] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313752/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01
[Kernel-packages] [Bug 1856872] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313750/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01
[Kernel-packages] [Bug 1856872] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313748/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01
[Kernel-packages] [Bug 1856872] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313755/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01
[Kernel-packages] [Bug 1856872] Re: Realtek btusb dongle vanishes after resume from suspend
apport information ** Tags added: apport-collected ** Description changed: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.01 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0408 ProdID=5365 Rev=00.02 S: Manufacturer=SunplusIT Inc S: Product=HP TrueVision HD Camera C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo I: If#=0x1
[Kernel-packages] [Bug 1856872] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313751/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01
[Kernel-packages] [Bug 1856872] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313753/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01
[Kernel-packages] [Bug 1856872] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313758/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1
[Kernel-packages] [Bug 1856872] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1856872/+attachment/5313756/+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/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=02
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
The other 2 good brands I know are Corsair and WD Black. Don't buy Samsung, the majority of people with this problem have Samsung -- 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 1746340] Re: Samsung SSD corruption (fsck needed)
Thank Lucas, i think i will buy another type of SSD. Do you have any suggestion? -- 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 1856749] Re: bionic/linux: 4.15.0-74.84 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 18. December 2019 22:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: + bionic/linux-raspi2: bug 1854793 bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 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/1856749 Title: bionic/linux: 4.15.0-74.84 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 18. December 2019 22:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux-raspi2: bug 1854793 bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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)
Hu trong lu. I indeed bought a new SSD because I thought mine was faulty. However I bought one of the same brand (Samsung). I didn't have the idea of buying another brand. Anyways, the brand new SSD also has the problem. For my case it definitely is not a hardware problem. With Linux the problem happens every day, sometimes more than once per day. With Windows the error never happened and with Qubes I'm running for more than 2 months without any problems. So it's not hardware, definitely is something wrong with Linux kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: USER
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi Lucas, do you have tried with new SSD? I don't think this is the hw issue. My SSD Power Cycles is only 807. Eventually, if not having any other solution, i think i will buy new SSD, do you know which type of SSD would work properly with linux? Smartctl output: sudo smartctl -t long -a /dev/nvme0n1p2 smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.0.0-37-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: LITEON CA3-8D512 Serial Number: 0028104000DN Firmware Version: C49640A PCI Vendor ID: 0x14a4 PCI Vendor Subsystem ID:0x1b4b IEEE OUI Identifier:0x002303 Total NVM Capacity: 512,110,190,592 [512 GB] Unallocated NVM Capacity: 0 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 512,110,190,592 [512 GB] Namespace 1 Formatted LBA Size: 512 Local Time is: Thu Dec 19 08:54:28 2019 +07 Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x001f): Security Format Frmw_DL NS_Mngmt *Other* Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Maximum Data Transfer Size: 32 Pages Warning Comp. Temp. Threshold: 83 Celsius Critical Comp. Temp. Threshold: 85 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 8.00W --0 0 0 00 0 1 + 4.50W --1 1 1 15 5 2 + 3.00W --2 2 2 25 5 3 - 0.0700W --3 3 3 3 10005000 4 - 0.0100W --4 4 4 4 5000 45000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 - 512 0 1 1 -4096 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02, NSID 0x1) Critical Warning: 0x00 Temperature:47 Celsius Available Spare:100% Available Spare Threshold: 0% Percentage Used:0% Data Units Read:5,773,150 [2.95 TB] Data Units Written: 6,405,757 [3.27 TB] Host Read Commands: 78,674,228 Host Write Commands:91,754,035 Controller Busy Time: 10,405 Power Cycles: 807 Power On Hours: 312 Unsafe Shutdowns: 104 Media and Data Integrity Errors:0 Error Information Log Entries: 0 Warning Comp. Temperature Time:0 Critical Comp. Temperature Time:0 Temperature Sensor 1: 47 Celsius Error Information (NVMe Log 0x01, max 64 entries) No Errors Logged -- 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
[Kernel-packages] [Bug 1854793] Re: bionic/linux-raspi2: 4.15.0-1053.57 -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: 1854819 + kernel-stable-master-bug: '1856749' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 03. December 2019 23:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854792 unknown/unknown: bug 1854792 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/1854793 Title: bionic/linux-raspi2: 4.15.0-1053.57 -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: In Progress 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: '1856749' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 03. December 2019 23:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854792 unknown/unknown: bug 1854792 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856872] 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 1856872 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard
[Kernel-packages] [Bug 1856908] Re: [80SY, Realtek ALC236, Speaker, Internal] Playback problem
Looks like the Intel graphics kernel driver crashing. ** Summary changed: - [80SY, Realtek ALC236, Speaker, Internal] Playback problem + Sometimes my Lenovo v310 freezes completely while playing music ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856908 Title: Sometimes my Lenovo v310 freezes completely while playing music Status in linux package in Ubuntu: Incomplete Bug description: $lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $uname -a Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux audacious: 3.6.2-2 What happened: Sometimes my Lenovo v310 freezes completely while playing music (Audacious). This is something i found in syslog. Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here ] Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active) Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: 14771 at /build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek snd_hda_codec_generic arc4 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_soc_skl intel_cstate intel_rapl_perf snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_midi snd_seq_midi_event videobuf2_core joydev snd_rawmidi input_leds videodev serio_raw snd_seq media wmi_bmof snd_seq_device Dec 19 03:01:53 localhost kernel: [12615.594456] intel_wmi_thunderbolt snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me mei btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci libahci wmi video Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: kworker/u8:0 Tainted: G OE4.15.0-73-generic #82~16.04.1-Ubuntu Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO 80SY/, BIOS 0ZCN30WW 12/08/2016 Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: events_unbound intel_atomic_commit_work [i915] Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: 0010:intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: 0018:c23fc1367cb0 EFLAGS: 00010286 Dec 19 03:01:53 localhost kernel: [12615.594969] RAX: RBX: a06e2a00 RCX: 97e63a28 Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 RSI: 0082 RDI: 0202 Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 R08: fffa734938d0 R09: Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 R11: 0367 R12: a06c56299000 Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 R14: a06c5629f000 R15: a06e2a00 Dec 19 03:01:53 localhost kernel: [12615.594997] FS: () GS:a06e3ec0() knlGS: Dec 19 03:01:53 localhost kernel: [12615.595003] CS: 0010 DS: ES: CR0: 80050033 Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 CR3: 000210a0a001 CR4: 003626f0 Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace: Dec 19 03:01:53 localhost kernel: [12615.595197] ? intel_pre_plane_update+0x12f/0x190 [i915] Dec 19 03:01:53 localhost kernel: [12615.595371] intel_update_crtc+0x75/0xa0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595526] skl_update_crtcs+0x1a9/0x1f0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595663] intel_atomic_commit_tail+0x3c8/0xe00 [i915] Dec 19 03:01:53 localhost kernel: [12615.595676] ? __switch_to+0x9b/0x4e0 Dec 19 03:01:53 localhost kernel: [12615.595687] ? __switch_to_asm+0x35/0x70 Dec 19 03:01:53 localhost kernel: [12615.595819] intel_atomic_commit_work+0x12/0x20 [i915] Dec 19 03:01:53 localhost kernel: [12615.595830] process_one_work+0x14d/0x410 Dec 19 03:01:53 localhost kernel: [12615.595839] worker_thread+0x4b/0x460 Dec 19 03:01:53 localhost kernel:
[Kernel-packages] [Bug 1854829] Re: xenial/linux-raspi2: 4.4.0-1127.136 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- 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/1854829 Title: xenial/linux-raspi2: 4.4.0-1127.136 -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: In Progress 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 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: 1854835 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 04. December 2019 15:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1854828 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854793] Re: bionic/linux-raspi2: 4.15.0-1053.57 -proposed tracker
Hardware Certification have begun testing this -proposed kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- 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/1854793 Title: bionic/linux-raspi2: 4.15.0-1053.57 -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: In Progress 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: '1856749' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 03. December 2019 23:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-raspi2/pi-kernel: bug 1854792 unknown/unknown: bug 1854792 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856908] 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 1856908 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856908 Title: Sometimes my Lenovo v310 freezes completely while playing music Status in linux package in Ubuntu: Incomplete Bug description: $lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $uname -a Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux audacious: 3.6.2-2 What happened: Sometimes my Lenovo v310 freezes completely while playing music (Audacious). This is something i found in syslog. Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here ] Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active) Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: 14771 at /build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek snd_hda_codec_generic arc4 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_soc_skl intel_cstate intel_rapl_perf snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_midi snd_seq_midi_event videobuf2_core joydev snd_rawmidi input_leds videodev serio_raw snd_seq media wmi_bmof snd_seq_device Dec 19 03:01:53 localhost kernel: [12615.594456] intel_wmi_thunderbolt snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me mei btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci libahci wmi video Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: kworker/u8:0 Tainted: G OE4.15.0-73-generic #82~16.04.1-Ubuntu Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO 80SY/, BIOS 0ZCN30WW 12/08/2016 Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: events_unbound intel_atomic_commit_work [i915] Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: 0010:intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: 0018:c23fc1367cb0 EFLAGS: 00010286 Dec 19 03:01:53 localhost kernel: [12615.594969] RAX: RBX: a06e2a00 RCX: 97e63a28 Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 RSI: 0082 RDI: 0202 Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 R08: fffa734938d0 R09: Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 R11: 0367 R12: a06c56299000 Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 R14: a06c5629f000 R15: a06e2a00 Dec 19 03:01:53 localhost kernel: [12615.594997] FS: () GS:a06e3ec0() knlGS: Dec 19 03:01:53 localhost kernel: [12615.595003] CS: 0010 DS: ES: CR0: 80050033 Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 CR3: 000210a0a001 CR4: 003626f0 Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace: Dec 19 03:01:53 localhost kernel: [12615.595197] ? intel_pre_plane_update+0x12f/0x190 [i915] Dec 19 03:01:53 localhost kernel: [12615.595371] intel_update_crtc+0x75/0xa0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595526] skl_update_crtcs+0x1a9/0x1f0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595663] intel_atomic_commit_tail+0x3c8/0xe00 [i915] Dec 19 03:01:53 localhost kernel: [12615.595676] ? __switch_to+0x9b/0x4e0 Dec 19 03:01:53 localhost
[Kernel-packages] [Bug 1856908] [NEW] Sometimes my Lenovo v310 freezes completely while playing music
You have been subscribed to a public bug: $lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 $uname -a Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux audacious: 3.6.2-2 What happened: Sometimes my Lenovo v310 freezes completely while playing music (Audacious). This is something i found in syslog. Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here ] Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active) Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: 14771 at /build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek snd_hda_codec_generic arc4 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_soc_skl intel_cstate intel_rapl_perf snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_midi snd_seq_midi_event videobuf2_core joydev snd_rawmidi input_leds videodev serio_raw snd_seq media wmi_bmof snd_seq_device Dec 19 03:01:53 localhost kernel: [12615.594456] intel_wmi_thunderbolt snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me mei btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci libahci wmi video Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: kworker/u8:0 Tainted: G OE4.15.0-73-generic #82~16.04.1-Ubuntu Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO 80SY/, BIOS 0ZCN30WW 12/08/2016 Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: events_unbound intel_atomic_commit_work [i915] Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: 0010:intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: 0018:c23fc1367cb0 EFLAGS: 00010286 Dec 19 03:01:53 localhost kernel: [12615.594969] RAX: RBX: a06e2a00 RCX: 97e63a28 Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 RSI: 0082 RDI: 0202 Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 R08: fffa734938d0 R09: Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 R11: 0367 R12: a06c56299000 Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 R14: a06c5629f000 R15: a06e2a00 Dec 19 03:01:53 localhost kernel: [12615.594997] FS: () GS:a06e3ec0() knlGS: Dec 19 03:01:53 localhost kernel: [12615.595003] CS: 0010 DS: ES: CR0: 80050033 Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 CR3: 000210a0a001 CR4: 003626f0 Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace: Dec 19 03:01:53 localhost kernel: [12615.595197] ? intel_pre_plane_update+0x12f/0x190 [i915] Dec 19 03:01:53 localhost kernel: [12615.595371] intel_update_crtc+0x75/0xa0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595526] skl_update_crtcs+0x1a9/0x1f0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595663] intel_atomic_commit_tail+0x3c8/0xe00 [i915] Dec 19 03:01:53 localhost kernel: [12615.595676] ? __switch_to+0x9b/0x4e0 Dec 19 03:01:53 localhost kernel: [12615.595687] ? __switch_to_asm+0x35/0x70 Dec 19 03:01:53 localhost kernel: [12615.595819] intel_atomic_commit_work+0x12/0x20 [i915] Dec 19 03:01:53 localhost kernel: [12615.595830] process_one_work+0x14d/0x410 Dec 19 03:01:53 localhost kernel: [12615.595839] worker_thread+0x4b/0x460 Dec 19 03:01:53 localhost kernel: [12615.595853] kthread+0x105/0x140 Dec 19 03:01:53 localhost kernel: [12615.595861] ? process_one_work+0x410/0x410 Dec 19 03:01:53 localhost kernel: [12615.595867] ? kthread_bind+0x40/0x40 Dec 19 03:01:53 localhost kernel: [12615.595878] ret_from_fork+0x35/0x40 Dec 19 03:01:53 localhost kernel: [12615.595885] Code: 4a 03 00 00 00 0f 84 55 01 00 00 80 bb ca 2c 00 00 00 0f 84 1c ff ff ff 48 c7 c6 5e 54 5e c0 48 c7 c7 44 54 5e c0 e8 a3 f0 52 d6 <0f> 0b e9 02 ff ff ff 3d 00 08 00 00 ba 00 08 00 00 0f 4f c2 e9 Dec 19 03:01:53 localhost kernel: [12615.596031] ---[ end trace 4627cd6bd9d494bf ]---
[Kernel-packages] [Bug 1856872] Re: bluez regression: Bluetooth fails after resume
** Tags added: eoan ** Summary changed: - bluez regression: Bluetooth fails after resume + Realtek btusb dongle vanishes after resume from suspend ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1856872 Title: Realtek btusb dongle vanishes after resume from suspend Status in linux package in Ubuntu: New Bug description: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
I think more likely it was a kernel bug and we just haven't bisected it clearly yet. Try going back to a v5.3 kernel like Ubuntu is shipping and see if it happens there? -- 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/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Incomplete Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. 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 19.2.1-1ubuntu1
[Kernel-packages] [Bug 1855685] Re: change kconfig of the soundwire bus driver from y to m
** Also affects: linux (Ubuntu Focal) Importance: Medium Assignee: Hui Wang (hui.wang) Status: Confirmed ** Also affects: linux-oem-osp1 (Ubuntu Focal) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855685 Title: change kconfig of the soundwire bus driver from y to m Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] We just got a Dell laptop which has soundwire codec on it, and let us change the soundwire bus from y to m, then the kernel image size will be reduced and it is easy for us to use dkms to replace this driver. And Intel released a sound wire audio driver to us, but it is based on the 5.4-rc7, we couldn't backport 150+ patches to our oem-osp1 kernel, and we plan to use dkms on this machine. To use dkms, we need to change this driver to a kernel module. [Fix] Change the kernel config from y to m. [Test Case] We tested this patch on osp1 kernel, it worked very well with soundwire audio dkms. [Regression Risk] Low, just change a driver from y to m. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855685/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:building + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: - bionic/linux-hwe: bug 1856849, bug 1856210 + bionic/linux-hwe: bug 1856210, bug 1856849 eoan/linux-oracle: bug 1854755 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-hwe: bug 1856210, bug 1856849 eoan/linux-oracle: bug 1854755 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Ongoing -- package copied to Proposed signed:building trackers: - bionic/linux-hwe: bug 1856210, bug 1856849 + bionic/linux-hwe: bug 1856849, bug 1856210 + eoan/linux-oracle: bug 1854755 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-hwe: bug 1856210, bug 1856849 eoan/linux-oracle: bug 1854755 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854755] Re: eoan/linux-oracle: 5.3.0-1008.9 -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: '1856807' packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 11. December 2019 11:16 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-oracle-5.3: bug 1854754 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/1854755 Title: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: 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 Eoan: 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: '1856807' packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 11. December 2019 11:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854829] Re: xenial/linux-raspi2: 4.4.0-1127.136 -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: 1854835 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 04. December 2019 15:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1854828 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/1854829 Title: xenial/linux-raspi2: 4.4.0-1127.136 -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 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: 1854835 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 04. December 2019 15:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1854828 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854829/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854831] Re: xenial/linux-snapdragon: 4.4.0-1131.139 -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: 1854835 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 04. December 2019 15:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1854830 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/1854831 Title: xenial/linux-snapdragon: 4.4.0-1131.139 -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: In Progress 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 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: 1854835 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 04. December 2019 15:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1854830 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854755] Re: eoan/linux-oracle: 5.3.0-1008.9 -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: 1854762 + kernel-stable-master-bug: '1856807' packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 11. December 2019 11:16 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-oracle-5.3: bug 1854754 variant: debs ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- 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/1854755 Title: eoan/linux-oracle: 5.3.0-1008.9 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: 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 Eoan: 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: '1856807' packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Wednesday, 11. December 2019 11:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1854754 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854755/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: - bionic/linux-hwe: bug 1856849 + bionic/linux-hwe: bug 1856210, bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-hwe: bug 1856210, bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854824] Re: xenial/linux-aws: 4.4.0-1100.111 -proposed tracker
** Tags added: passed regression-testing- -- 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/1854824 Title: xenial/linux-aws: 4.4.0-1100.111 -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-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Wednesday, 04. December 2019 16:11 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-aws/aws-kernel: bug 1854823 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854744 packages: main: linux-raspi2-5.3 meta: linux-meta-raspi2-5.3 - phase: Promote to Proposed - phase-changed: Wednesday, 18. December 2019 09:13 UTC + phase: Testing + phase-changed: Wednesday, 18. December 2019 23:01 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856235 Title: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854744 packages: main: linux-raspi2-5.3 meta: linux-meta-raspi2-5.3 phase: Testing phase-changed: Wednesday, 18. December 2019 23:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 18. December 2019 22:32 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:46 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.84 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => New ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => New ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => New ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => New ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => New ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Andy Whitcroft (apw) => Ubuntu Stable Release Updates Team (ubuntu-sru) -- 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/1856749 Title: bionic/linux: 4.15.0-74.84 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 18. December 2019 22:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854762] Re: eoan/linux: 5.3.0-25.27 -proposed tracker
*** This bug is a duplicate of bug 1856807 *** https://bugs.launchpad.net/bugs/1856807 ** This bug has been marked a duplicate of bug 1856807 eoan/linux: 5.3.0-26.28 -proposed tracker -- 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/1854762 Title: eoan/linux: 5.3.0-25.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: 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 Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1856210 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-eoan ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Wednesday, 18. December 2019 16:51 UTC + phase: Ready for Promote to Proposed + phase-changed: Wednesday, 18. December 2019 22:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:failed - replaces: bug 1854762 + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Wednesday, 18. December 2019 22:32 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.84 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging - phase-changed: Wednesday, 18. December 2019 22:21 UTC + phase-changed: Wednesday, 18. December 2019 22:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded - promote-to-proposed: Alert -- packages no longer available trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 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/1856749 Title: bionic/linux: 4.15.0-74.84 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 18. December 2019 22:32 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856900] 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 1856900 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- 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/1856900 Title: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12 Status in linux package in Ubuntu: Incomplete Bug description: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu 16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c000c25ffce0 LR: c063f058 CTR: c000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c00109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic) 16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 800010009033 CR: 88002440 XER: 2000 16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c063f054 IRQMASK: 0 16:20:39 DEBUG| [stdout]GPR00: c063f034 c00109703aa0 c1a4bb00 c0007cef3000 16:20:39 DEBUG| [stdout]GPR04: c000c25ffc18 16:20:39 DEBUG| [stdout]GPR08: 16:20:39 DEBUG| [stdout]GPR12: c000c25ffce0 c0003fffee00 79b6987b4410 16:20:39 DEBUG| [stdout]GPR16: 79b698b3 79b6987b0320 79b69771f240 79b6987b4420 16:20:39 DEBUG| [stdout]GPR20: 79b6880010a0 79b698a4d3a0 16:20:39 DEBUG| [stdout]GPR24: c00109d56cc0 c001fde0cd8c c000c25ffce0 c00109d56ca0 16:20:39 DEBUG| [stdout]GPR28: c00109d56cc0 c0007cef3000 c00109d56c90 16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c000c25ffce0] 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c063f058]
[Kernel-packages] [Bug 1856900] Re: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
I believe this is because a FUSE based file system is being used in the prior ADT testing and sysinfo is breaking on the FUSE filesystem, so it may be a problem with with the fuse fs itself or the fuse file system that is using the kernel fuse core. -- 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/1856900 Title: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12 Status in linux package in Ubuntu: Incomplete Bug description: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu 16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c000c25ffce0 LR: c063f058 CTR: c000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c00109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic) 16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 800010009033 CR: 88002440 XER: 2000 16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c063f054 IRQMASK: 0 16:20:39 DEBUG| [stdout]GPR00: c063f034 c00109703aa0 c1a4bb00 c0007cef3000 16:20:39 DEBUG| [stdout]GPR04: c000c25ffc18 16:20:39 DEBUG| [stdout]GPR08: 16:20:39 DEBUG| [stdout]GPR12: c000c25ffce0 c0003fffee00 79b6987b4410 16:20:39 DEBUG| [stdout]GPR16: 79b698b3 79b6987b0320 79b69771f240 79b6987b4420 16:20:39 DEBUG| [stdout]GPR20: 79b6880010a0 79b698a4d3a0 16:20:39 DEBUG| [stdout]GPR24: c00109d56cc0 c001fde0cd8c c000c25ffce0 c00109d56ca0 16:20:39 DEBUG| [stdout]GPR28: c00109d56cc0 c0007cef3000 c00109d56c90 16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c000c25ffce0] 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c063f058] fuse_request_end+0x128/0x2f0 16:20:39 DEBUG| [stdout] [ 6521.210423] Call Trace: 16:20:39 DEBUG| [stdout] [ 6521.210448] [c00109703aa0] [c063f034] fuse_request_end+0x104/0x2f0 (unreliable) 16:20:39 DEBUG| [stdout] [ 6521.210520] [c00109703af0] [c0642ebc] fuse_dev_do_write+0x2cc/0x5c0 16:20:39 DEBUG| [stdout] [ 6521.210591] [c00109703b70] [c0643654]
[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.84 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Promote to Proposed - phase-changed: Wednesday, 18. December 2019 21:31 UTC + phase: Packaging + phase-changed: Wednesday, 18. December 2019 22:21 UTC reason: - promote-to-proposed: Stalled -- review in progress + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Alert -- packages no longer available trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 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/1856749 Title: bionic/linux: 4.15.0-74.84 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 18. December 2019 22:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded promote-to-proposed: Alert -- packages no longer available trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.84 -proposed tracker
** Summary changed: - bionic/linux: 4.15.0-74.83 -proposed tracker + bionic/linux: 4.15.0-74.84 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Released => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856749 Title: bionic/linux: 4.15.0-74.84 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Wednesday, 18. December 2019 22:21 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded promote-to-proposed: Alert -- packages no longer available trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856900] Re: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
I've seen something very similar to this on this platform and I believe it's a combination of previous regressions tests and the stress-ng sysinfo test that triggers this. Running the stress-ng stressor after a clean boot won't trigger this issue. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1856900 Title: stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12 Status in linux package in Ubuntu: Incomplete Bug description: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu 16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c000c25ffce0 LR: c063f058 CTR: c000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c00109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic) 16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 800010009033 CR: 88002440 XER: 2000 16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c063f054 IRQMASK: 0 16:20:39 DEBUG| [stdout]GPR00: c063f034 c00109703aa0 c1a4bb00 c0007cef3000 16:20:39 DEBUG| [stdout]GPR04: c000c25ffc18 16:20:39 DEBUG| [stdout]GPR08: 16:20:39 DEBUG| [stdout]GPR12: c000c25ffce0 c0003fffee00 79b6987b4410 16:20:39 DEBUG| [stdout]GPR16: 79b698b3 79b6987b0320 79b69771f240 79b6987b4420 16:20:39 DEBUG| [stdout]GPR20: 79b6880010a0 79b698a4d3a0 16:20:39 DEBUG| [stdout]GPR24: c00109d56cc0 c001fde0cd8c c000c25ffce0 c00109d56ca0 16:20:39 DEBUG| [stdout]GPR28: c00109d56cc0 c0007cef3000 c00109d56c90 16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c000c25ffce0] 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c063f058] fuse_request_end+0x128/0x2f0 16:20:39 DEBUG| [stdout] [ 6521.210423] Call Trace: 16:20:39 DEBUG| [stdout] [ 6521.210448] [c00109703aa0] [c063f034] fuse_request_end+0x104/0x2f0 (unreliable) 16:20:39 DEBUG| [stdout] [
[Kernel-packages] [Bug 1856900] [NEW] stress-ng sysinfo stressor fails on ppc64el with linux 5.4.0-9.12
Public bug reported: During autopkgtest testing the sysinfo stressor failed, causing the kernel to oops. 16:20:34 DEBUG| [stdout] sysinfo STARTING 16:20:39 DEBUG| [stdout] sysinfo RETURNED 0 16:20:39 DEBUG| [stdout] sysinfo FAILED (kernel oopsed) 16:20:39 DEBUG| [stdout] [ 6521.203448] kernel tried to execute exec-protected page (c000c25ffce0) - exploit attempt? (uid: 0) 16:20:39 DEBUG| [stdout] [ 6521.207260] BUG: Unable to handle kernel instruction fetch 16:20:39 DEBUG| [stdout] [ 6521.207307] Faulting instruction address: 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.207367] Oops: Kernel access of bad area, sig: 11 [#1] 16:20:39 DEBUG| [stdout] [ 6521.207416] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries 16:20:39 DEBUG| [stdout] [ 6521.207481] Modules linked in: unix_diag sctp vhost_vsock vmw_vsock_virtio_transport_common vsock zfs(PO) zunicode(PO) zavl(PO) icp(PO) zlua(PO) userio zcommon(PO) znvpair(PO) cuse spl(O) kvm_pr kvm snd_seq snd_seq_device snd_timer snd soundcore hci_vhci bluetooth ecdh_generic ecc uhid hid vhost_net vhost tap atm algif_rng aegis128 algif_aead anubis fcrypt khazad seed sm4_generic tea crc32_generic md4 michael_mic nhpoly1305 poly1305_generic rmd128 rmd160 rmd256 rmd320 sha3_generic sm3_generic streebog_generic tgr192 wp512 xxhash_generic blowfish_generic blowfish_common cast5_generic des_generic libdes salsa20_generic chacha_generic camellia_generic cast6_generic cast_common serpent_generic twofish_generic twofish_common algif_skcipher aufs sch_etf sch_fq dccp_ipv6 dccp_ipv4 dccp ip6table_nat ip6_tables iptable_nat xt_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 algif_hash af_alg ip_vti ip6_vti fou6 sit ipip tunnel4 fou geneve act_mirred cls_basic esp6 authenc echainiv 16:20:39 DEBUG| [stdout] [ 6521.208045] iptable_filter xt_policy veth esp4_offload esp4 xfrm_user xfrm_algo macsec vxlan ip6_udp_tunnel udp_tunnel vrf 8021q garp mrp bridge stp llc ip6_gre ip6_tunnel tunnel6 ip_gre ip_tunnel gre cls_u32 sch_htb dummy tls binfmt_misc af_packet_diag tcp_diag udp_diag raw_diag inet_diag iptable_mangle xt_TCPMSS xt_tcpudp bpfilter dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto crct10dif_vpmsum sch_fq_codel ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c crc32c_vpmsum virtio_blk virtio_net net_failover failover [last unloaded: trace_printk] 16:20:39 DEBUG| [stdout] [ 6521.209360] CPU: 1 PID: 2647099 Comm: fuse_mnt Tainted: P OE 5.4.0-9-generic #12-Ubuntu 16:20:39 DEBUG| [stdout] [ 6521.209457] NIP: c000c25ffce0 LR: c063f058 CTR: c000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.209528] REGS: c00109703810 TRAP: 0400 Tainted: P OE (5.4.0-9-generic) 16:20:39 DEBUG| [stdout] [ 6521.209608] MSR: 800010009033 CR: 88002440 XER: 2000 16:20:39 DEBUG| [stdout] [ 6521.209681] CFAR: c063f054 IRQMASK: 0 16:20:39 DEBUG| [stdout]GPR00: c063f034 c00109703aa0 c1a4bb00 c0007cef3000 16:20:39 DEBUG| [stdout]GPR04: c000c25ffc18 16:20:39 DEBUG| [stdout]GPR08: 16:20:39 DEBUG| [stdout]GPR12: c000c25ffce0 c0003fffee00 79b6987b4410 16:20:39 DEBUG| [stdout]GPR16: 79b698b3 79b6987b0320 79b69771f240 79b6987b4420 16:20:39 DEBUG| [stdout]GPR20: 79b6880010a0 79b698a4d3a0 16:20:39 DEBUG| [stdout]GPR24: c00109d56cc0 c001fde0cd8c c000c25ffce0 c00109d56ca0 16:20:39 DEBUG| [stdout]GPR28: c00109d56cc0 c0007cef3000 c00109d56c90 16:20:39 DEBUG| [stdout] [ 6521.210276] NIP [c000c25ffce0] 0xc000c25ffce0 16:20:39 DEBUG| [stdout] [ 6521.210355] LR [c063f058] fuse_request_end+0x128/0x2f0 16:20:39 DEBUG| [stdout] [ 6521.210423] Call Trace: 16:20:39 DEBUG| [stdout] [ 6521.210448] [c00109703aa0] [c063f034] fuse_request_end+0x104/0x2f0 (unreliable) 16:20:39 DEBUG| [stdout] [ 6521.210520] [c00109703af0] [c0642ebc] fuse_dev_do_write+0x2cc/0x5c0 16:20:39 DEBUG| [stdout] [ 6521.210591] [c00109703b70] [c0643654] fuse_dev_write+0x74/0xd0 16:20:39 DEBUG| [stdout] [ 6521.210660] [c00109703c00] [c04707c0] do_iter_readv_writev+0x240/0x290 16:20:39 DEBUG| [stdout] [ 6521.210735] [c00109703c70] [c04730d8] do_iter_write+0xc8/0x280 16:20:39 DEBUG| [stdout] [ 6521.210794] [c00109703cc0] [c04733a0] vfs_writev+0xe0/0x180 16:20:39 DEBUG| [stdout] [ 6521.210854] [c00109703dc0] [c04734dc] do_writev+0x9c/0x1a0 16:20:39 DEBUG| [stdout] [ 6521.210915] [c00109703e20] [c000b278] system_call+0x5c/0x68 16:20:39 DEBUG| [stdout] [ 6521.210973] Instruction
[Kernel-packages] [Bug 1823037] Re: amd_iommu possible data corruption
seems I finally found the real issue in the bios of my Gigabyte x570 UD , when I have 4G encode option enabled I have silent data corruption ( or at least if its enabled along side with IOMMU ) I need to make another array that I can kill to keep testing with , but I can literally go into the bios enable 4G reboot then start a zfs scrub and instantly have crc errors pop up everywhere , reboot disable do a scrub and it's all good , seems to only kick in when multiple disks are in use In the past ~2012 with my Gigabyte F2A85x-UP4 AMD A10 5800k I also had data issues with IOMMU enabled ... never had issues with my intel i7 4790k build , so it could very well just be AMD IOMMU that is causing it for me -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range in the hardware to the last page which is _in_ the range. [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain 3c677d206210f53a4be972211066c0f1cd47fe12 iommu/amd: Set exclusion range correctly These can be picked from my branches here: Bionic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/bionic 1823037-amd_iommu-cherrypick b7abdb585d0ae4193add1f7038476cd8d6dd7f41 iommu/amd: Reserve exclusion range in iova-domain ee4a87e6b7fe7e039c1f02c50c53da63e4270732 iommu/amd: Set exclusion range correctly Cosmic: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/cosmic 1823037-amd_iommu-cherrypick 0acc8c0e862b46b12c233abd76593420f4a20e0c iommu/amd: Reserve exclusion range in iova-domain fbead5d71bfc2a49ffca8d181e2708fd616e9a7f iommu/amd: Set exclusion range correctly Disco: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/disco 1823037-amd_iommu-cherrypick 6ddc207ca0d442b413ea7f059937ba90e5139753 iommu/amd: Set exclusion range correctly Note Disco only required f1cd47fe12 as the first patch was already picked in LP: #1830934 Not necessary for Eoan as these are already upstream in 5.2-rc1 [Regression Risk] Low,this adds memory protection to the driver and has already been applied upstream and tested by Dell for 24 hours with no failures noted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856235] Re: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854744 packages: main: linux-raspi2-5.3 meta: linux-meta-raspi2-5.3 phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 09:13 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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/1856235 Title: bionic/linux-raspi2-5.3: 5.3.0-1015.17~18.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854744 packages: main: linux-raspi2-5.3 meta: linux-meta-raspi2-5.3 phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 09:13 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.83 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 18. December 2019 12:42 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 18. December 2019 21:31 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 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/1856749 Title: bionic/linux: 4.15.0-74.83 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 21:31 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.83 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856749 Title: bionic/linux: 4.15.0-74.83 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Wednesday, 18. December 2019 21:31 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 18. December 2019 16:51 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:failed,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa meta:failed replaces: bug 1854762 trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 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/1856807 Title: eoan/linux: 5.3.0-26.28 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Wednesday, 18. December 2019 16:51 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:failed replaces: bug 1854762 trackers: bionic/linux-hwe: bug 1856849 eoan/linux/pc-kernel: bug 1856805 eoan/linux/pc-lowlatency-kernel: bug 1856806 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855178] Re: pstate
Please notice I incorrectly stated the System 76 model as the Galago Pro. This is the ORYX PRO with the Core i7-8750H. This is the first slim model (not sure the version). I also have the 4-core prior version, however I haven't yet had a chance to test. -- 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/1855178 Title: pstate Status in linux package in Ubuntu: Confirmed Bug description: LSB Release: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic Hardware: System76 Galago Pro v4 (i7-8750H), Clevo-960rd (i7-9750H) Expected results: CPU should be governed by Intel P-State and should normally idle between 400 and 800 MHz when not loaded. Actual results: After update, CPU frequency remains pegged at maximum at all times. This sucks battery life and overheats the laptop. Steps to reproduce: 1. Install Ubuntu 19.10 from official media. Kernel installed will be 5.3.0-18-generic 2. Check CPU frequencies. They will typically idle around 800MHz. Loading the system will spike to max frequencies (4.5 for 9750H, 4.2 for 8750H). 3. Upgrade system. Kernel will update to 5.3.0-23-generic 4. Reboot. 5. Monitor CPU frequencies again. This time, all core will remain at max frequencies. Additional information: 1. Geekbench v4 multi-core scores are cut in half (26K vs 13K) after update. Single-core scores drop around 20%. This does not occur in 19.04 or 18.04. Confirmed on multiple 960rd systems. 2. linux-image-5.3.0-19-generic is also confirmed 3. We suspect that all kernels images after 5.3.0-18 have this bug 4. We are not sure how much hardware is affected. At present, only the 8750/9750H CPUs are confirmed. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu2017 F pulseaudio /dev/snd/controlC1: kubuntu2017 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-18 (16 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Notebook P95_96_97Ex,Rx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13NS1 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.13NS1:bd10/01/2019:svnNotebook:pnP95_96_97Ex,Rx:pvrNotApplicable:rvnNotebook:rnP95_96_97Ex,Rx:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P95_96_97Ex,Rx dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kubuntu1949 F pulseaudio /dev/snd/controlC1: kubuntu1949 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-18 (16 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Notebook P95_96_97Ex,Rx NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgkubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/01/2019 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.13NS1 dmi.board.asset.tag: Tag 12345 dmi.board.name: P95_96_97Ex,Rx dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No
[Kernel-packages] [Bug 1849751] Re: [i915] doesn't boot after 19.10 upgrade
OK! Confirmed this was a hardware failure, thanks for helping me look into it! ** 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 in Ubuntu. https://bugs.launchpad.net/bugs/1849751 Title: [i915] doesn't boot after 19.10 upgrade Status in linux package in Ubuntu: Invalid Bug description: after upgrading to ubuntu 19.10, vulkan support when using the intel card in my laptop is broken. running any of my example vulkan apps shows the following error: $ vkcube vkcube: /build/vulkan-tools-IZAxVX/vulkan-tools-1.1.114.0+dfsg1/cube/cube.c:3175: demo_init_vk: Assertion `!err' failed. Aborted (core dumped) note that since the update I can no longer boot my system at all without adding "nomodeset" the kernel params, something is broken in the intel modeset driver since 19.04. so this may very well be related. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mesa-vulkan-drivers 19.2.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 24 20:04:54 2019 DistUpgraded: 2019-10-23 18:54:04,373 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: zfs, 0.8.1, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer HD Graphics 630 [1558:65a1] NVIDIA Corporation GP104BM [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104BM [GeForce GTX 1070 Mobile] [1558:65a3] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd Chicony USB 2.0 Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. EgisTec_ES603 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Oryx Pro ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=ZFS=rpool/root ro root=ZFS=rpool/root quiet nomodeset SourcePackage: mesa UpgradeStatus: Upgraded to eoan on 2019-10-23 (1 days ago) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 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 19.2.1-1ubuntu1 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/linux/+bug/1849751/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
git bisect reports: 0b6a70743beacb15516ef9572b40c93b8b3892d3 is the first bad commit commit 0b6a70743beacb15516ef9572b40c93b8b3892d3 Author: Jan-Marek Glogowski Date: Fri Feb 1 13:52:31 2019 +0100 usb: handle warm-reset port requests on hub resume -- 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856869] Re: Eoan update: 5.3.17 upstream stable release
Please note I: * Reverted the UBUNTU SAUCE version of "ovl: fix lookup failure on multi lower squashfs" in favor of the upstream stable version * Reverted the UBUNTU SAUCE version of "seccomp: avoid overflow in implicit constant conversion" in favor of the upstream stable version * Reverted the UBUNTU SAUCE version of "mfd: rk808: Fix RK818 ID template" in favor of the upstream stable version -- 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/1856869 Title: Eoan update: 5.3.17 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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: * usb: gadget: configfs: Fix missing spin_lock_init() * usb: gadget: pch_udc: fix use after free * Revert "nvme: Add quirk for Kingston NVME SSD running FW E8FK11.T" * scsi: zfcp: trace channel log even for FCP command responses * scsi: qla2xxx: Fix driver unload hang * scsi: qla2xxx: Fix memory leak when sending I/O fails * media: venus: remove invalid compat_ioctl32 handler * USB: uas: honor flag to avoid CAPACITY16 * USB: uas: heed CAPACITY_HEURISTICS * USB: documentation: flags on usb-storage versus UAS * usb: Allow USB device to be warm reset in suspended state * usb: host: xhci-tegra: Correct phy enable sequence * binder: fix incorrect calculation for num_valid * staging: rtl8188eu: fix interface sanity check * staging: rtl8712: fix interface sanity check * staging: vchiq: call unregister_chrdev_region() when driver registration fails * staging: gigaset: fix general protection fault on probe * staging: gigaset: fix illegal free on probe errors * staging: gigaset: add endpoint-type sanity check * usb: xhci: only set D3hot for pci device * xhci: Fix memory leak in xhci_add_in_port() * xhci: fix USB3 device initiated resume race with roothub autosuspend * xhci: Increase STS_HALT timeout in xhci_suspend() * xhci: handle some XHCI_TRUST_TX_LENGTH quirks cases as default behaviour. * xhci: make sure interrupts are restored to correct state * interconnect: qcom: sdm845: Walk the list safely on node removal * ARM: dts: pandora-common: define wl1251 as child node of mmc3 * iio: adis16480: Add debugfs_reg_access entry * iio: adis16480: Fix scales factors * iio: humidity: hdc100x: fix IIO_HUMIDITYRELATIVE channel reporting * iio: imu: inv_mpu6050: fix temperature reporting using bad unit * iio: adc: ad7606: fix reading unnecessary data from device * iio: adc: ad7124: Enable internal reference * USB: atm: ueagle-atm: add missing endpoint check * USB: idmouse: fix interface sanity checks * USB: serial: io_edgeport: fix epic endpoint lookup * usb: roles: fix a potential use after free * USB: adutux: fix interface sanity check * usb: core: urb: fix URB structure initialization function * usb: mon: Fix a deadlock in usbmon between mmap and read * tpm: add check after commands attribs tab allocation * EDAC/altera: Use fast register IO for S10 IRQs * brcmfmac: disable PCIe interrupts before bus reset * mtd: spear_smi: Fix Write Burst mode * mtd: rawnand: Change calculating of position page containing BBM * virt_wifi: fix use-after-free in virt_wifi_newlink() * virtio-balloon: fix managed page counts when migrating pages between zones * usb: dwc3: pci: add ID for the Intel Comet Lake -H variant * usb: dwc3: gadget: Fix logical condition * usb: dwc3: gadget: Clear started flag for non-IOC * usb: dwc3: ep0: Clear started flag on completion * phy: renesas: rcar-gen3-usb2: Fix sysfs interface of "role" * usb: typec: fix use after free in typec_register_port() * iwlwifi: pcie: fix support for transmitting SKBs with fraglist * btrfs: check page->mapping when loading free space cache * btrfs: use refcount_inc_not_zero in kill_all_nodes * Btrfs: fix metadata space leak on fixup worker failure to set range as delalloc * Btrfs: fix negative subv_writers counter and data space leak after buffered write * btrfs: Avoid getting stuck during cyclic writebacks * btrfs: Remove btrfs_bio::flags member * Btrfs: send, skip backreference walking for extents with many references * btrfs: record all roots for rename exchange on a subvol * rtlwifi: rtl8192de: Fix missing
[Kernel-packages] [Bug 1856870] Re: Eoan update: 5.3.18 upstream stable release
** 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:
+ * inet: protect against too small mtu values.
+ * mqprio: Fix out-of-bounds access in mqprio_dump
+ * net: bridge: deny dev_set_mac_address() when unregistering
+ * net: dsa: fix flow dissection on Tx path
+ * net: ethernet: ti: cpsw: fix extra rx interrupt
+ * net: sched: fix dump qlen for sch_mq/sch_mqprio with NOLOCK subqueues
+ * net: thunderx: start phy before starting autonegotiation
+ * net/tls: Fix return values to avoid ENOTSUPP
+ * openvswitch: support asymmetric conntrack
+ * tcp: md5: fix potential overestimation of TCP option space
+ * tipc: fix ordering of tipc module init and exit routine
+ * net/mlx5e: Query global pause state before setting prio2buffer
+ * net: ipv6: add net argument to ip6_dst_lookup_flow
+ * net: ipv6_stub: use ip6_dst_lookup_flow instead of ip6_dst_lookup
+ * tcp: fix rejected syncookies due to stale timestamps
+ * tcp: tighten acceptance of ACKs not matching a child socket
+ * tcp: Protect accesses to .ts_recent_stamp with {READ,WRITE}_ONCE()
+ * gre: refetch erspan header from skb->data after pskb_may_pull()
+ * Fixed updating of ethertype in function skb_mpls_pop
+ * hsr: fix a NULL pointer dereference in hsr_dev_xmit()
+ * net: Fixed updating of ethertype in skb_mpls_push()
+ * net/mlx5e: Fix TXQ indices to be sequential
+ * page_pool: do not release pool until inflight == 0.
+ * xdp: obtain the mem_id mutex before trying to remove an entry.
+ * Linux 5.3.18
+ * UBUNTU: upstream stable to v5.3.18
-5.3.18 upstream stable release
-from git://git.kernel.org/
+ 5.3.18 upstream stable release
+ from git://git.kernel.org/
--
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/1856870
Title:
Eoan update: 5.3.18 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Eoan:
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:
* inet: protect against too small mtu values.
* mqprio: Fix out-of-bounds access in mqprio_dump
* net: bridge: deny dev_set_mac_address() when unregistering
* net: dsa: fix flow dissection on Tx path
* net: ethernet: ti: cpsw: fix extra rx interrupt
* net: sched: fix dump qlen for sch_mq/sch_mqprio with NOLOCK subqueues
* net: thunderx: start phy before starting autonegotiation
* net/tls: Fix return values to avoid ENOTSUPP
* openvswitch: support asymmetric conntrack
* tcp: md5: fix potential overestimation of TCP option space
* tipc: fix ordering of tipc module init and exit routine
* net/mlx5e: Query global pause state before setting prio2buffer
* net: ipv6: add net argument to ip6_dst_lookup_flow
* net: ipv6_stub: use ip6_dst_lookup_flow instead of ip6_dst_lookup
* tcp: fix rejected syncookies due to stale timestamps
* tcp: tighten acceptance of ACKs not matching a child socket
* tcp: Protect accesses to .ts_recent_stamp with {READ,WRITE}_ONCE()
* gre: refetch erspan header from skb->data after pskb_may_pull()
* Fixed updating of ethertype in function skb_mpls_pop
* hsr: fix a NULL pointer dereference in hsr_dev_xmit()
* net: Fixed updating of ethertype in skb_mpls_push()
* net/mlx5e: Fix TXQ indices to be sequential
* page_pool: do not release pool until inflight == 0.
* xdp: obtain the mem_id mutex before trying to remove an entry.
* Linux 5.3.18
* UBUNTU: upstream stable to v5.3.18
5.3.18 upstream stable release
from git://git.kernel.org/
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1856869] Re: Eoan update: 5.3.17 upstream stable release
** 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: + * mlxsw: spectrum_router: Fix determining underlay for a GRE tunnel + * net/mlx4_en: fix mlx4 ethtool -N insertion + * net/mlx4_en: Fix wrong limitation for number of TX rings + * net: rtnetlink: prevent underflows in do_setvfinfo() + * net/sched: act_pedit: fix WARN() in the traffic path + * net: sched: ensure opts_len <= IP_TUNNEL_OPTS_MAX in act_tunnel_key + * sfc: Only cancel the PPS workqueue if it exists + * net/mlxfw: Verify FSM error code translation doesn't exceed array size + * net/mlx5e: Fix set vf link state error flow + * net/mlx5: Fix auto group size calculation + * net/tls: enable sk_msg redirect to tls socket egress + * ipv6/route: return if there is no fib_nh_gw_family + * taprio: don't reject same mqprio settings + * net/ipv4: fix sysctl max for fib_multipath_hash_policy + * net/mlx5e: Fix error flow cleanup in mlx5e_tc_tun_create_header_ipv4/6 + * net/mlx5e: Do not use non-EXT link modes in EXT mode + * net/mlx5: Update the list of the PCI supported devices + * vhost/vsock: split packets to send using multiple buffers + * gpio: max77620: Fixup debounce delays + * gpio: bd70528: Use correct unit for debounce times + * tools: gpio: Correctly add make dependencies for gpio_utils + * fork: fix pidfd_poll()'s return type + * nbd:fix memory leak in nbd_get_socket() + * virtio_console: allocate inbufs in add_port() only if it is needed + * virtio_ring: fix return code on DMA mapping fails + * virtio_balloon: fix shrinker count + * Revert "fs: ocfs2: fix possible null-pointer dereferences in ocfs2_xa_prepare_entry()" + * mm/memory_hotplug: don't access uninitialized memmaps in shrink_zone_span() + * mm/ksm.c: don't WARN if page is still mapped in remove_stable_node() + * drm/amdgpu: disable gfxoff when using register read interface + * drm/amdgpu: disable gfxoff on original raven + * drm/amd/powerplay: issue no PPSMC_MSG_GetCurrPkgPwr on unsupported ASICs + * drm/i915: Don't oops in dumb_create ioctl if we have no crtcs + * drm/i915/pmu: "Frequency" is reported as accumulated cycles + * drm/i915/userptr: Try to acquire the page lock around set_page_dirty() + * Bluetooth: Fix invalid-free in bcsp_close() + * ath10k: restore QCA9880-AR1A (v1) detection + * ath10k: Fix HOST capability QMI incompatibility + * ath10k: Fix a NULL-ptr-deref bug in ath10k_usb_alloc_urb_from_pipe + * ath9k_hw: fix uninitialized variable data + * Revert "Bluetooth: hci_ll: set operational frequency earlier" + * Revert "dm crypt: use WQ_HIGHPRI for the IO and crypt workqueues" + * md/raid10: prevent access of uninitialized resync_pages offset + * mdio_bus: Fix init if CONFIG_RESET_CONTROLLER=n + * ARM: 8904/1: skip nomap memblocks while finding the lowmem/highmem boundary + * x86/insn: Fix awk regexp warnings + * x86/speculation: Fix incorrect MDS/TAA mitigation status + * x86/speculation: Fix redundant MDS mitigation message + * nbd: prevent memory leak + * gve: fix dma sync bug where not all pages synced + * x86/stackframe/32: Repair 32-bit Xen PV + * x86/xen/32: Make xen_iret_crit_fixup() independent of frame layout + * x86/xen/32: Simplify ring check in xen_iret_crit_fixup() + * x86/doublefault/32: Fix stack canaries in the double fault handler + * x86/pti/32: Size initial_page_table correctly + * x86/cpu_entry_area: Add guard page for entry stack on 32bit + * x86/entry/32: Fix IRET exception + * x86/entry/32: Use %ss segment where required + * x86/entry/32: Move FIXUP_FRAME after pushing %fs in SAVE_ALL + * x86/entry/32: Unwind the ESPFIX stack earlier on exception entry + * x86/entry/32: Fix NMI vs ESPFIX + * selftests/x86/mov_ss_trap: Fix the SYSENTER test + * selftests/x86/sigreturn/32: Invalidate DS and ES when abusing the kernel + * x86/pti/32: Calculate the various PTI cpu_entry_area sizes correctly, make the CPU_ENTRY_AREA_PAGES assert precise + * x86/entry/32: Fix FIXUP_ESPFIX_STACK with user CR3 + * futex: Prevent robust futex exit race + * ALSA: usb-audio: Fix NULL dereference at parsing BADD + * nfc: port100: handle command failure cleanly + * media: vivid: Set
[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load
SRU submitted today:
https://lists.ubuntu.com/archives/kernel-team/2019-December/106479.html
Cheers,
Guilherme
--
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/1855409
Title:
qede driver causes 100% CPU load
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
[Impact]
* The PTP feature in qede driver is implemented in a way that if the
NIC firmware takes some time to perform the timestamping then the PTP
worker function will reschedule itself indefinitely until the value
read from a device register is meaningful. With that behavior, if an
userspace tool requests a bad configured TX/RX filter (or if NIC
firmware has any other issue in timestamping), the function
qede_ptp_task() will reschedule itself forever and cause an unbound
resource consumption. This manifests as a kworker thread consuming
100% of CPU.
* The dmesg log will show a message like this:
"qede_ptp_tx_ts:533(eno3)]Timestamping in progress"
Also, by using perf user can observe a stack like the following:
- 44.76% 0.00% kworker/16:5 [kernel.kallsyms]
ret_from_fork
- kthread
- 44.74% worker_thread
- 44.57% process_one_work
- 42.67% qede_ptp_task
- 38.86% qed_ptp_hw_read_tx_ts
qed_rd
- 3.03% queue_work_on
- 2.06% __queue_work
- 0.68% get_work_pool
- 0.61% radix_tree_lookup
__radix_tree_lookup
0.50% set_work_pool_and_clear_pending
* The patch proposed in this SRU request refactors the PTP worked in
qede by adding a time limit, after which the task doesn't reschedule
itself anymore, failing the timestamp procedure: 9adebac37e7d ("qede:
Handle infinite driver spinning for Tx timestamp.")
http://git.kernel.org/linus/9adebac37e7d
Besides fixing the issue, it also adds an ethtool statistics for
accounting the PTP errors.
[Test case]
By using chrony in Bionic, the following steps will reproduce the
issue:
a) Install chrony on Bionic in a system with working NIC managed by qede;
b) Edit chrony configuration and add: "hwtimestamp *" to the top of its conf
file;
c) Restart chrony service
Check dmesg for the "[...]Timestamping in progress" message and the
overall CPU workload using a tool like "top" to observe a kthread
consuming 100% of CPU.
[Regression potential]
The patch scope is restricted to qede PTP handler, and is upstream for
more than 7 months. If there's any possibility of regressions, the
worst would be an issue affecting the packet timestamping, not messing
with the regular xmit path of the driver.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855409/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856701] Re: focal/linux: 5.4.0-9.12 -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 -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 17. December 2019 21:07 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 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/1856701 Title: focal/linux: 5.4.0-9.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-release series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 17. December 2019 21:07 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load
** Description changed:
- This bug is similar to #1832082 (bnx2x driver causes 100% CPU load) but
- applies for qede driver instead of bnx2x. The symptoms are the same:
+ [Impact]
- With chrony installed, and configured with "hwtimestamp *", I observe
- 100% CPU load on 2 CPU cores.
+ * The PTP feature in qede driver is implemented in a way that if the NIC
+ firmware takes some time to perform the timestamping then the PTP worker
+ function will reschedule itself indefinitely until the value read from a
+ device register is meaningful. With that behavior, if an userspace tool
+ requests a bad configured TX/RX filter (or if NIC firmware has any other
+ issue in timestamping), the function qede_ptp_task() will reschedule
+ itself forever and cause an unbound resource consumption. This manifests
+ as a kworker thread consuming 100% of CPU.
- Running perf report shows that kernel is busy executing qede_ptp_task
- function in qede driver.
+ * The dmesg log will show a message like this:
+ "qede_ptp_tx_ts:533(eno3)]Timestamping in progress"
- A workaround is to disable "hwtimestamp *" in chrony configuration.
-
- ---
-
- $ modinfo qede
- filename:
/lib/modules/4.15.0-72-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko
- version:8.10.10.21
- license:GPL
- description:QLogic FastLinQ 4 Ethernet Driver
- srcversion: D5EC89D815FC81B973EE9F0
- alias: pci:v1077d8090sv*sd*bc*sc*i*
- alias: pci:v1077d8070sv*sd*bc*sc*i*
- alias: pci:v1077d1664sv*sd*bc*sc*i*
- alias: pci:v1077d1656sv*sd*bc*sc*i*
- alias: pci:v1077d1654sv*sd*bc*sc*i*
- alias: pci:v1077d1644sv*sd*bc*sc*i*
- alias: pci:v1077d1636sv*sd*bc*sc*i*
- alias: pci:v1077d1666sv*sd*bc*sc*i*
- alias: pci:v1077d1634sv*sd*bc*sc*i*
- depends:ptp,qed
- retpoline: Y
- intree: Y
- name: qede
- vermagic: 4.15.0-72-generic SMP mod_unload
- signat: PKCS#7
- signer:
- sig_key:
- sig_hashalgo: md4
- parm: debug: Default debug msglevel (uint)
-
-
- $ uname -a
- Linux dcn1-clm-inf-1 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
-
-
- $ lspci | grep -i ether
- 19:00.0 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series
10/25/40/50GbE Controller (rev 02)
- 19:00.1 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series
10/25/40/50GbE Controller (rev 02)
- 19:00.2 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series
10/25/40/50GbE Controller (rev 02)
- 19:00.3 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series
10/25/40/50GbE Controller (rev 02)
-
-
- # perf report snippet:
-
- Children Self Command Shared Object
- - 44.76% 0.00% kworker/16:5 [kernel.kallsyms]
+ Also, by using perf user can observe a stack like the following:
+ - 44.76% 0.00% kworker/16:5 [kernel.kallsyms]
ret_from_fork
- kthread
- 44.74% worker_thread
- 44.57% process_one_work
- 42.67% qede_ptp_task
- 38.86% qed_ptp_hw_read_tx_ts
qed_rd
- 3.03% queue_work_on
- 2.06% __queue_work
- 0.68% get_work_pool
- 0.61% radix_tree_lookup
__radix_tree_lookup
0.50% set_work_pool_and_clear_pending
+
+ * The patch proposed in this SRU request refactors the PTP worked in
+ qede by adding a time limit, after which the task doesn't reschedule
+ itself anymore, failing the timestamp procedure: 9adebac37e7d ("qede:
+ Handle infinite driver spinning for Tx timestamp.")
+ http://git.kernel.org/linus/9adebac37e7d
+
+ Besides fixing the issue, it also adds an ethtool statistics for
+ accounting the PTP errors.
+
+ [Test case]
+
+ By using chrony in Bionic, the following steps will reproduce the issue:
+
+ a) Install chrony on Bionic in a system with working NIC managed by qede;
+ b) Edit chrony configuration and add: "hwtimestamp *" to the top of its conf
file;
+ c) Restart chrony service
+
+ Check dmesg for the "[...]Timestamping in progress" message and the
+ overall CPU workload using a tool like "top" to observe a kthread
+ consuming 100% of CPU.
+
+ [Regression potential]
+
+ The patch scope is restricted to qede PTP handler, and is upstream for
+ more than 7 months. If there's any possibility of regressions, the worst
+ would be an issue affecting the packet timestamping, not messing with
+ the regular xmit path of the driver.
--
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/1855409
Title:
qede driver causes 100% CPU load
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Hi trong luu, I didn't test it, but I think that it depends on the way VMware virtualizes access to the disk. There may be multiple ways, one of which will work. -- 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
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Testing phase-changed: Wednesday, 11. December 2019 17:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress 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 in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Testing phase-changed: Wednesday, 11. December 2019 17:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854800] Re: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854800 Title: bionic/linux-aws-fips: 4.15.0-2006.6 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854802 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Testing phase-changed: Wednesday, 11. December 2019 17:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854800/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856875] 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/1856875 Title: touchpad freeze after long suspention Status in linux package in Ubuntu: Confirmed Bug description: Mouse works but not the touchpad. Need to restart laptop to restore touchpad ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-25-generic 5.3.0-25.27 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user-meir 14256 F pulseaudio /dev/snd/controlC0: user-meir 14256 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Dec 18 09:16:47 2019 InstallationDate: Installed on 2019-10-18 (60 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3180 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-25-generic root=UUID=8b17e198-3430-4a53-9e4a-1da7d792458b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-25-generic N/A linux-backports-modules-5.3.0-25-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1748103] Re: apic test in kvm-unit-test failed
affects 4.15.0-1052.52 linux-kvm ** Changed in: ubuntu-kernel-tests Status: Confirmed => Triaged -- 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/1748103 Title: apic test in kvm-unit-test failed Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux-azure-edge source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in linux-azure-edge source package in Bionic: New Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test apic will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the apic test as root: # TESTNAME=apic TIMEOUT=30 ACCEL= ./x86/run x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline timeout -k 1s --foreground 30 /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/apic.flat -smp 2 -cpu qemu64,+x2apic,+tsc-deadline # -initrd /tmp/tmp.onXtr5JVp7 enabling apic enabling apic paging enabled cr0 = 80010011 cr3 = 459000 cr4 = 20 apic version: 1050014 PASS: apic existence PASS: xapic id matches cpuid PASS: writeable xapic id PASS: non-writeable x2apic id PASS: sane x2apic id FAIL: x2apic id matches cpuid PASS: correct xapic id after reset PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set PASS: apic_disable: Local apic disabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is clear PASS: apic_disable: Local apic enabled PASS: apic_disable: CPUID.1H:EDX.APIC[bit 9] is set x2apic enabled PASS: x2apic enabled to invalid state PASS: x2apic enabled to apic enabled PASS: disabled to invalid state PASS: disabled to x2apic enabled PASS: apic enabled to invalid state PASS: apicbase: relocate apic PASS: apicbase: reserved physaddr bits PASS: apicbase: reserved low bits PASS: self ipi starting broadcast (x2apic) PASS: APIC physical broadcast address PASS: APIC physical broadcast shorthand PASS: nmi-after-sti qemu-system-x86_64: terminating on signal 15 from pid 7246 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:00:55 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DistroRelease: Ubuntu 16.04 Package: linux-azure-edge PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 4.13.0-1009.12-username 4.13.13 Tags: xenial uec-images Uname: Linux 4.13.0-1009-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy libvirtd lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748103/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856875] [NEW] touchpad freeze after long suspention
Public bug reported: Mouse works but not the touchpad. Need to restart laptop to restore touchpad ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-25-generic 5.3.0-25.27 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user-meir 14256 F pulseaudio /dev/snd/controlC0: user-meir 14256 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Dec 18 09:16:47 2019 InstallationDate: Installed on 2019-10-18 (60 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3180 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-25-generic root=UUID=8b17e198-3430-4a53-9e4a-1da7d792458b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-25-generic N/A linux-backports-modules-5.3.0-25-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan package-from-proposed -- 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/1856875 Title: touchpad freeze after long suspention Status in linux package in Ubuntu: New Bug description: Mouse works but not the touchpad. Need to restart laptop to restore touchpad ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-25-generic 5.3.0-25.27 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user-meir 14256 F pulseaudio /dev/snd/controlC0: user-meir 14256 F pulseaudio CurrentDesktop: X-Cinnamon Date: Wed Dec 18 09:16:47 2019 InstallationDate: Installed on 2019-10-18 (60 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3180 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-25-generic root=UUID=8b17e198-3430-4a53-9e4a-1da7d792458b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-25-generic N/A linux-backports-modules-5.3.0-25-generic N/A linux-firmware1.183.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856872] [NEW] bluez regression: Bluetooth fails after resume
Public bug reported: New laptop that is running Ubuntu Mate 19.10, most everything works out of the box even bluetooth but bluetooth does not resume after suspend. In fact I am unable to restart it and get it to work after a suspend. Wireless resumes and continues to work, just bluetooth fails. After suspend the controller and adapter are not found, restarting bluetooth.service nor restarting network manger solve the issue. After a resume the adapter is not found at all, I have tried to remove the module before a suspend and add it back to no avail, the only way to get it working is to reboot which is a pain. Please let me know what additional data you may need, posting information below: Chipset is Realtek RTL8822CE, combined wireless and Bluetooth module Running Bluez 5.50 package... Working on intial Boot: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 10: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. |__ Port 10: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M ID 0bda:b00c Realtek Semiconductor Corp. rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=01 Dev#= 3 Spd=12 MxCh= 0 D: Ver= 1.00 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0bda ProdID=b00c Rev=00.00 S: Manufacturer=Realtek S: Product=Bluetooth Radio S: SerialNumber=00e04c01 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb I: If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 003: ID 0bda:b00c Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep Blue [1.192743] usb 1-10: Product: Bluetooth Radio [ 11.706607] Bluetooth: Core ver 2.22 [ 11.706620] Bluetooth: HCI device and connection manager initialized [ 11.706624] Bluetooth: HCI socket layer initialized [ 11.706626] Bluetooth: L2CAP socket layer initialized [ 11.706628] Bluetooth: SCO socket layer initialized [ 11.720229] Bluetooth: hci0: RTL: rtl: examining hci_ver=0a hci_rev=000c lmp_ver=0a lmp_subver=8822 [ 11.721252] Bluetooth: hci0: RTL: rom_version status=0 version=3 [ 11.721254] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_fw.bin [ 11.722558] Bluetooth: hci0: RTL: rtl: loading rtl_bt/rtl8822cu_config.bin [ 11.722879] Bluetooth: hci0: RTL: cfg_sz 6, total sz 24866 [ 15.466810] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 15.466812] Bluetooth: BNEP filters: protocol multicast [ 15.466816] Bluetooth: BNEP socket layer initialized [ 18.070246] Bluetooth: RFCOMM TTY layer initialized [ 18.070250] Bluetooth: RFCOMM socket layer initialized [ 18.070253] Bluetooth: RFCOMM ver 1.11 After resume: lsusb -tv /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M ID 1d6b:0003 Linux Foundation 3.0 root hub /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 3: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. |__ Port 3: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M ID 0408:5365 Quanta Computer, Inc. rfkill list 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no usb-devices T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh=12 D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=1d6b ProdID=0002 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S: Product=xHCI Host Controller S: SerialNumber=:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub T: Bus=01 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 D: Ver= 2.01 Cls=ef(misc ) Sub=02 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0408 ProdID=5365 Rev=00.02 S: Manufacturer=SunplusIT Inc S: Product=HP TrueVision HD Camera C: #Ifs= 2 Cfg#= 1 Atr=80 MxPwr=500mA I: If#=0x0 Alt= 0 #EPs= 1 Cls=0e(video) Sub=01 Prot=00 Driver=uvcvideo I: If#=0x1 Alt= 0 #EPs= 0 Cls=0e(video) Sub=02 Prot=00 Driver=uvcvideo T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=1 MxCh= 6 D: Ver= 3.10 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev=05.03 S: Manufacturer=Linux 5.3.0-24-generic xhci-hcd S:
[Kernel-packages] [Bug 1856749] Re: bionic/linux: 4.15.0-74.83 -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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Wednesday, 18. December 2019 12:42 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 + xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 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/1856749 Title: bionic/linux: 4.15.0-74.83 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Wednesday, 18. December 2019 12:42 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux/pc-kernel: bug 1856747 bionic/linux/pc-lowlatency-kernel: bug 1856748 xenial/linux-azure: bug 1856203 xenial/linux-hwe: bug 1856804 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856749/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856807] Re: eoan/linux: 5.3.0-26.28 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
- phase: Packaging
- phase-changed: Wednesday, 18. December 2019 05:08 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Wednesday, 18. December 2019 16:51 UTC
reason:
- prepare-package: Ongoing -- {} package not yet fully built
- promote-to-proposed: Pending -- builds not complete in ppa
main:building,meta:failed,signed:depwait
+ promote-to-proposed: Pending -- builds not complete in ppa
meta:failed,signed:depwait
replaces: bug 1854762
trackers:
bionic/linux-hwe: bug 1856849
eoan/linux/pc-kernel: bug 1856805
eoan/linux/pc-lowlatency-kernel: bug 1856806
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/1856807
Title:
eoan/linux: 5.3.0-26.28 -proposed tracker
Status in Kernel SRU Workflow:
In Progress
Status in Kernel SRU Workflow automated-testing series:
New
Status in Kernel SRU Workflow certification-testing series:
New
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
New
Status in Kernel SRU Workflow promote-to-security series:
New
Status in Kernel SRU Workflow promote-to-updates series:
New
Status in Kernel SRU Workflow regression-testing series:
New
Status in Kernel SRU Workflow security-signoff series:
New
Status in Kernel SRU Workflow verification-testing series:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Eoan:
Confirmed
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Holding before Promote to Proposed
phase-changed: Wednesday, 18. December 2019 16:51 UTC
reason:
promote-to-proposed: Pending -- builds not complete in ppa
meta:failed,signed:depwait
replaces: bug 1854762
trackers:
bionic/linux-hwe: bug 1856849
eoan/linux/pc-kernel: bug 1856805
eoan/linux/pc-lowlatency-kernel: bug 1856806
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856807/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856869] [NEW] Eoan update: 5.3.17 upstream stable release
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: 5.3.17 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Connor Kuehl (connork) 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 Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856869 Title: Eoan update: 5.3.17 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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: 5.3.17 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856869/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856867] [NEW] When i update my linux kernel my touch pad doesn't work
Public bug reported: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=06cb Product=78f1 Version=0100 N: Name="Synaptics TM3096-001" P: Phys=i2c-DLL06B0:00 S: Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-DLL06B0:00/0018:06CB:78F1.0001/input/input7 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=6f38103 I: Bus=0019 Vendor= Product= Version= N: Name="DELL Wireless hotkeys" P: Phys=dellabce/input0 S: Sysfs=/devices/virtual/input/input8 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0003 Vendor=0c45 Product=6710 Version=5504 N: Name="Integrated_Webcam_HD: Integrate" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-5/2-5:1.0/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys= S: Sysfs=/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input10 U: Uniq= H: Handlers=rfkill kbd event8 B: PROP=0 B: EV=13 B: KEY=8000 0 0 101500b0c00 20030 e 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input15 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input16 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input17 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=1c4f Product=0034 Version=0110 N: Name="SIGMACHIP Usb Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/0003:1C4F:0034.0003/input/input23 U: Uniq= H: Handlers=mouse1 event16 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hermes 3066 F pulseaudio /dev/snd/controlC1: hermes 3066 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 11:45:58 2019 HibernationDevice: RESUME=UUID=8ebd4080-f73f-4eee-8e6b-5d3837e0f977 InstallationDate: Installed on 2018-12-27 (356 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" -
[Kernel-packages] [Bug 1856867] 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/1856867 Title: When i update my linux kernel my touch pad doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event4 leds B: PROP=0 B: EV=120013 B: KEY=1100f02902000 8380307cf910f001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=06cb Product=78f1 Version=0100 N: Name="Synaptics TM3096-001" P: Phys=i2c-DLL06B0:00 S: Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-DLL06B0:00/0018:06CB:78F1.0001/input/input7 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=6f38103 I: Bus=0019 Vendor= Product= Version= N: Name="DELL Wireless hotkeys" P: Phys=dellabce/input0 S: Sysfs=/devices/virtual/input/input8 U: Uniq= H: Handlers=rfkill kbd event6 B: PROP=0 B: EV=3 B: KEY=80 0 0 0 I: Bus=0003 Vendor=0c45 Product=6710 Version=5504 N: Name="Integrated_Webcam_HD: Integrate" P: Phys=usb-:00:14.0-5/button S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-5/2-5:1.0/input/input9 U: Uniq= H: Handlers=kbd event7 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Dell WMI hotkeys" P: Phys= S: Sysfs=/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/9DBB5994-A997-11DA-B012-B622A1EF5492/input/input10 U: Uniq= H: Handlers=rfkill kbd event8 B: PROP=0 B: EV=13 B: KEY=8000 0 0 101500b0c00 20030 e 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12 U: Uniq= H: Handlers=kbd event10 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input14 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input15 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input16 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input17 U: Uniq= H: Handlers=event15 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=1c4f Product=0034 Version=0110 N: Name="SIGMACHIP Usb Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb2/2-2/2-2:1.0/0003:1C4F:0034.0003/input/input23 U: Uniq= H: Handlers=mouse1 event16 B: PROP=0 B: EV=17 B: KEY=7
[Kernel-packages] [Bug 1856870] [NEW] Eoan update: 5.3.18 upstream stable release
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: 5.3.18 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Connor Kuehl (connork) 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 Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856870 Title: Eoan update: 5.3.18 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: 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: 5.3.18 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
I still see this message on a fully up-to-date Kubuntu 19.10 system. However the system boots fine and everything seems to be working ok. This is apparently a non-fatal error message? It sounds pretty bad but it still seems to have been able to load the initramfs image fine. What does this really mean then? -- 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/1835660 Title: initramfs unpacking failed Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853485] Re: Bionic kernel panic on Cavium ThunderX CN88XX
Confirmed fixed with Bionic 4.15.0-74.83 15:58:28 DEBUG| [stdout] Linux wright-kernel 4.15.0-74-generic #83-Ubuntu SMP Wed Dec 18 04:32:55 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853485 Title: Bionic kernel panic on Cavium ThunderX CN88XX Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Bug description: Description: kernel panic while trying to deploy Bionic 18.04.3 Linux version 4.15.0-70-generic on Cavium ThunderX CN88XX (arm64) System: Board Model: gbt-mt30 Board name: MT30-GS0 System name:MT30-GS0 SKU: CN8890-2000BG2601-AAP-Y22-G To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
I also just saw this during a forced XHCI reset (after the USB bus failed to connect): 8< [ 247.130032] usb 3-1.6.2.4: new low-speed USB device number 9 using xhci_hcd [ 247.388286] usb 3-1.6.2.4: New USB device found, idVendor=04d9, idProduct=2013, bcdDevice= 1.03 [ 247.388287] usb 3-1.6.2.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 247.388288] usb 3-1.6.2.4: Product: USB Keyboard [ 247.388289] usb 3-1.6.2.4: Manufacturer: [ 247.454042] usb 3-1.6.5: new high-speed USB device number 10 using xhci_hcd [ 247.511444] input: USB Keyboard as /devices/pci:00/:00:1d.6/:06:00.0/:07:01.0/:09:00.0/:0a:04.0/:0c:00.0/:0d:01.0/:0e:00.0/usb3/3-1/3-1.6/3-1.6.2/3-1.6.2.4/3-1.6.2.4:1.0/0003:04D9:2013.0014/input/input44 [ 247.570426] hid-generic 0003:04D9:2013.0014: input,hidraw4: USB HID v1.00 Keyboard [ USB Keyboard] on usb-:0e:00.0-1.6.2.4/input0 [ 247.583572] input: USB Keyboard System Control as /devices/pci:00/:00:1d.6/:06:00.0/:07:01.0/:09:00.0/:0a:04.0/:0c:00.0/:0d:01.0/:0e:00.0/usb3/3-1/3-1.6/3-1.6.2/3-1.6.2.4/3-1.6.2.4:1.1/0003:04D9:2013.0015/input/input45 [ 247.613793] usb 3-1.6.5: New USB device found, idVendor=0424, idProduct=274c, bcdDevice= 2.00 [ 247.613796] usb 3-1.6.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 247.613797] usb 3-1.6.5: Product: Hub Controller [ 247.613799] usb 3-1.6.5: Manufacturer: Microchip Tech [ 247.642290] input: USB Keyboard Consumer Control as /devices/pci:00/:00:1d.6/:06:00.0/:07:01.0/:09:00.0/:0a:04.0/:0c:00.0/:0d:01.0/:0e:00.0/usb3/3-1/3-1.6/3-1.6.2/3-1.6.2.4/3-1.6.2.4:1.1/0003:04D9:2013.0015/input/input46 [ 247.642466] hid-generic 0003:04D9:2013.0015: input,hidraw5: USB HID v1.00 Device [ USB Keyboard] on usb-:0e:00.0-1.6.2.4/input1 [ 247.703468] hid-generic 0003:0424:274C.0016: hiddev2,hidraw6: USB HID v1.10 Device [Microchip Tech Hub Controller] on usb-:0e:00.0-1.6.5/input0 [ 249.085573] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.085576] xhci_hcd :0e:00.0: Looking for event-dma fffa2040 trb-start fffa2020 trb-end fffa2020 seg-start fffa2000 seg-end fffa2ff0 [ 249.086506] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.086509] xhci_hcd :0e:00.0: Looking for event-dma fffa2050 trb-start fffa2020 trb-end fffa2020 seg-start fffa2000 seg-end fffa2ff0 [ 249.087505] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.087509] xhci_hcd :0e:00.0: Looking for event-dma fffa2060 trb-start fffa2020 trb-end fffa2020 seg-start fffa2000 seg-end fffa2ff0 [ 249.088504] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.088506] xhci_hcd :0e:00.0: Looking for event-dma fffa2070 trb-start fffa2020 trb-end fffa2020 seg-start fffa2000 seg-end fffa2ff0 [ 249.089505] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.089506] xhci_hcd :0e:00.0: Looking for event-dma fffa2080 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.090504] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.090507] xhci_hcd :0e:00.0: Looking for event-dma fffa2090 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.091507] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.091511] xhci_hcd :0e:00.0: Looking for event-dma fffa20a0 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.092507] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.092510] xhci_hcd :0e:00.0: Looking for event-dma fffa20b0 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.093505] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.093509] xhci_hcd :0e:00.0: Looking for event-dma fffa20c0 trb-start fffa2030 trb-end fffa2030 seg-start fffa2000 seg-end fffa2ff0 [ 249.094507] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 6 comp_code 13 [ 249.094512] xhci_hcd :0e:00.0: Looking for event-dma fffa20d0 trb-start fffa2030 trb-end
[Kernel-packages] [Bug 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 05. December 2019 22:51 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 -- 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/1854807 Title: xenial/linux-oracle: 4.15.0-1031.34~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: 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-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: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 05. December 2019 22:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1854807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -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: 1854819 + kernel-stable-master-bug: '1856749' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 13. December 2019 15:48 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 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs ** Changed in: kernel-sru-workflow/regression-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: '1856749' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 13. December 2019 15:48 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 1856202 xenial/linux-azure/azure-kernel: bug 1856199 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/1856203 Title: xenial/linux-azure: 4.15.0-1066.71 -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: '1856749' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 13. December 2019 15:48 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 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854832] Re: xenial/linux-fips: 4.4.0-1027.32 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854832 Title: xenial/linux-fips: 4.4.0-1027.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 05. December 2019 17:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -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/1856203 Title: xenial/linux-azure: 4.15.0-1066.71 -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: '1856749' packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 13. December 2019 15:48 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 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854832] Re: xenial/linux-fips: 4.4.0-1027.32 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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: 1854835 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 05. December 2019 17:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress 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 in Ubuntu. https://bugs.launchpad.net/bugs/1854832 Title: xenial/linux-fips: 4.4.0-1027.32 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Testing phase-changed: Thursday, 05. December 2019 17:55 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
Haven't had a problem for over a week now with kernel 5.4.1-050401-generic. Strange, as a comment above says it happened with this kernel as well. So it probably was fixed by the Firefox update? updates since Dec 8th contain: - Firefox from 69.0.3 to 71.0 - Thunderbird - samba, git, wine, ssh, makemkv -- 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/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Incomplete Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2
[Kernel-packages] [Bug 1854833] Re: trusty/linux-aws: 4.4.0-1060.64 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854833 Title: trusty/linux-aws: 4.4.0-1060.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid 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 Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 05. December 2019 13:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854807] Re: xenial/linux-oracle: 4.15.0-1031.34~16.04.1 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1854807 Title: xenial/linux-oracle: 4.15.0-1031.34~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: 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-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: 1854808 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Thursday, 05. December 2019 22:51 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: 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/1854807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854833] Re: trusty/linux-aws: 4.4.0-1060.64 -proposed tracker
** Changed in: kernel-sru-workflow/regression-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: 1854835 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 05. December 2019 13:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress 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-aws in Ubuntu. https://bugs.launchpad.net/bugs/1854833 Title: trusty/linux-aws: 4.4.0-1060.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid 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 Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854835 packages: main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Thursday, 05. December 2019 13:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855409] Re: qede driver causes 100% CPU load
Hi Przemyslaw, thank you for the great report and debug! I'll proceed with the SRU proposal. Cheers, Guilherme ** Tags added: disco sts -- 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/1855409 Title: qede driver causes 100% CPU load Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: This bug is similar to #1832082 (bnx2x driver causes 100% CPU load) but applies for qede driver instead of bnx2x. The symptoms are the same: With chrony installed, and configured with "hwtimestamp *", I observe 100% CPU load on 2 CPU cores. Running perf report shows that kernel is busy executing qede_ptp_task function in qede driver. A workaround is to disable "hwtimestamp *" in chrony configuration. --- $ modinfo qede filename: /lib/modules/4.15.0-72-generic/kernel/drivers/net/ethernet/qlogic/qede/qede.ko version:8.10.10.21 license:GPL description:QLogic FastLinQ 4 Ethernet Driver srcversion: D5EC89D815FC81B973EE9F0 alias: pci:v1077d8090sv*sd*bc*sc*i* alias: pci:v1077d8070sv*sd*bc*sc*i* alias: pci:v1077d1664sv*sd*bc*sc*i* alias: pci:v1077d1656sv*sd*bc*sc*i* alias: pci:v1077d1654sv*sd*bc*sc*i* alias: pci:v1077d1644sv*sd*bc*sc*i* alias: pci:v1077d1636sv*sd*bc*sc*i* alias: pci:v1077d1666sv*sd*bc*sc*i* alias: pci:v1077d1634sv*sd*bc*sc*i* depends:ptp,qed retpoline: Y intree: Y name: qede vermagic: 4.15.0-72-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: debug: Default debug msglevel (uint) $ uname -a Linux dcn1-clm-inf-1 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ lspci | grep -i ether 19:00.0 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.1 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.2 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) 19:00.3 Ethernet controller: QLogic Corp. FastLinQ QL41000 Series 10/25/40/50GbE Controller (rev 02) # perf report snippet: Children Self Command Shared Object - 44.76% 0.00% kworker/16:5 [kernel.kallsyms] ret_from_fork - kthread - 44.74% worker_thread - 44.57% process_one_work - 42.67% qede_ptp_task - 38.86% qed_ptp_hw_read_tx_ts qed_rd - 3.03% queue_work_on - 2.06% __queue_work - 0.68% get_work_pool - 0.61% radix_tree_lookup __radix_tree_lookup 0.50% set_work_pool_and_clear_pending To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
