[Kernel-packages] [Bug 1993041] Re: nvidia-driver-515 (515.76-0ubuntu0.22.04.1): blank screen after boot, can't log in
This bug was fixed in the package nvidia-graphics-drivers-515 - 515.76+really.515.65.01-0ubuntu1 --- nvidia-graphics-drivers-515 (515.76+really.515.65.01-0ubuntu1) kinetic; urgency=medium * Revert to the 515.65.01 version (LP: #1993041). * Revert "debian/templates/dkms_nvidia.conf.in: drop buildfix_kernel_6.0.patch" * debian/rules: Make sure that debian_version variable includes the full version, so that we depend on the correct libraries in case of release rollbacks. -- Alberto Milone Wed, 19 Oct 2022 16:18:24 + ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1993041 Title: nvidia-driver-515 (515.76-0ubuntu0.22.04.1): blank screen after boot, can't log in Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Bug description: System: Ubuntu 22.04.1 LTS (x86-64) Kernel: 5.15.0-50-generic NVIDIA card: NVIDIA Corporation GA102 [GeForce RTX 3080 Lite Hash Rate] (rev a1) Problem summary: Just updated "nvidia-driver-515" package from "515.65.01-0ubuntu0.22.04.1" to newest "515.76-0ubuntu0.22.04.1". It results in a blank screen after boot and before showing graphical login (gdm) so can't log in. Seems that keyboard doesn't work in this situation so I can't change to a text session. Instead, I used a remote ssh session to get some info: journalctl.txt, dmesg.txt, lspci.txt and nvidia-smi.txt files attached. Card is connected to monitor using HDMI output. Notes: - Previous "nvidia-driver-515" version, "515.65.01-0ubuntu0.22.04.1", worked as expected. Unfortunately I can't install that version again because it seems to be deleted from the repository. - Previous "nvidia-driver-510" version, "510.85.02-0ubuntu0.22.04.1", works as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1993041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992474] Re: [Lenovo ThinkPad P1 Gen2] Flickering started right after install
In that case please try selecting the 'Ubuntu' login option and then look at Settings > About to confirm that Wayland is being used. Does the flicker still occur 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/1992474 Title: [Lenovo ThinkPad P1 Gen2] Flickering started right after install Status in linux package in Ubuntu: Incomplete Bug description: My computer is a Lenovo Thinkpad p-Series Gen 2 with Intel Core i9. I've tried updating my grub file as is suggested in Bugs #1970426, #1958191, and #1973676. That is, I've tried GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" And, I've tried cstate=4. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon 2093 F pulseaudio /dev/snd/controlC1: moon 2093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 08:05:20 2022 InstallationDate: Installed on 2020-03-29 (926 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=39110848-f164-47a5-bf96-fda0216c46fb ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (51 days ago) dmi.bios.date: 05/07/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:br1.31:efr1.23:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QT_BU_Think_FM_ThinkPadP1Gen2: dmi.product.family: ThinkPad P1 Gen2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen2 dmi.product.version: ThinkPad P1 Gen2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992474] Re: [Lenovo ThinkPad P1 Gen2] Flickering started right after install
I don't get that option. I do get 'Ubuntu on xorg' and the flickering still occurs when I select it. Also, the flickering starts as soon as the Ubuntu logo appears before login. I just noticed that as I was waiting to try your 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/1992474 Title: [Lenovo ThinkPad P1 Gen2] Flickering started right after install Status in linux package in Ubuntu: Incomplete Bug description: My computer is a Lenovo Thinkpad p-Series Gen 2 with Intel Core i9. I've tried updating my grub file as is suggested in Bugs #1970426, #1958191, and #1973676. That is, I've tried GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" And, I've tried cstate=4. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon 2093 F pulseaudio /dev/snd/controlC1: moon 2093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 08:05:20 2022 InstallationDate: Installed on 2020-03-29 (926 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=39110848-f164-47a5-bf96-fda0216c46fb ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (51 days ago) dmi.bios.date: 05/07/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:br1.31:efr1.23:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QT_BU_Think_FM_ThinkPadP1Gen2: dmi.product.family: ThinkPad P1 Gen2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen2 dmi.product.version: ThinkPad P1 Gen2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991774] Re: Memory leak while using NFQUEUE to delegate the decision on TCP packets to userspace processes
I have used the linux/4.15.0-195.206 kernel in -proposed for testing.
The issue no longer exists by testing with the same test plan.
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991774
Title:
Memory leak while using NFQUEUE to delegate the decision on TCP
packets to userspace processes
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Environment: v4.15.0-177-generic Xenial ESM
Using NFQUEUE to delegate the decision on TCP packets to userspace processes
will cause memory leak.
The symptom is that TCP slab objects will accumulate and eventually cause OOM.
[Fix]
There is a discrepancy between backport and upstream commit.
[Upstream Commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1]
diff --git a/include/net/netfilter/nf_queue.h
b/include/net/netfilter/nf_queue.h
index 9eed51e920e8..980daa6e1e3a 100644
--- a/include/net/netfilter/nf_queue.h
+++ b/include/net/netfilter/nf_queue.h
@@ -37,7 +37,7 @@ void nf_register_queue_handler(const struct
nf_queue_handler *qh);
void nf_unregister_queue_handler(void);
void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
void nf_queue_entry_free(struct nf_queue_entry *entry);
static inline void init_hashrandom(u32 *jhash_initval)
diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
index 5ab0680db445..e39549c55945 100644
--- a/net/netfilter/nf_queue.c
+++ b/net/netfilter/nf_queue.c
@@ -96,19 +96,21 @@ static void __nf_queue_entry_init_physdevs(struct
nf_queue_entry *entry)
}
/* Bump dev refs so they don't vanish while packet is out */
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
{
struct nf_hook_state *state = >state;
+ if (state->sk && !refcount_inc_not_zero(>sk->sk_refcnt))
+ return false;
+
dev_hold(state->in);
dev_hold(state->out);
- if (state->sk)
- sock_hold(state->sk);
#if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
dev_hold(entry->physin);
dev_hold(entry->physout);
#endif
+ return true;
}
EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);
@@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const
struct nf_hook_state *state,
__nf_queue_entry_init_physdevs(entry);
- nf_queue_entry_get_refs(entry);
+ if (!nf_queue_entry_get_refs(entry)) {
+ kfree(entry);
+ return -ENOTCONN;
+ }
switch (entry->state.pf) {
case AF_INET:
diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
index ea2d9c2a44cf..64a6acb6aeae 100644
--- a/net/netfilter/nfnetlink_queue.c
+++ b/net/netfilter/nfnetlink_queue.c
@@ -710,9 +710,15 @@ static struct nf_queue_entry *
nf_queue_entry_dup(struct nf_queue_entry *e)
{
struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
- if (entry)
- nf_queue_entry_get_refs(entry);
- return entry;
+
+ if (!entry)
+ return NULL;
+
+ if (nf_queue_entry_get_refs(entry))
+ return entry;
+
+ kfree(entry);
+ return NULL;
}
#if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
[Backport Commit 4d032d60432327f068f03b516f5b6c51ceb17d15]
diff --git a/include/net/netfilter/nf_queue.h
b/include/net/netfilter/nf_queue.h
index 814058d0f167..f38cc6092c5a 100644
--- a/include/net/netfilter/nf_queue.h
+++ b/include/net/netfilter/nf_queue.h
@@ -32,7 +32,7 @@ void nf_register_queue_handler(struct net *net, const
struct nf_queue_handler *q
void nf_unregister_queue_handler(struct net *net);
void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
void nf_queue_entry_release_refs(struct nf_queue_entry *entry);
static inline void init_hashrandom(u32 *jhash_initval)
diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
index 59340b3ef7ef..dbc45165c533 100644
--- a/net/netfilter/nf_queue.c
+++ b/net/netfilter/nf_queue.c
@@ -80,10 +80,13 @@ void nf_queue_entry_release_refs(struct nf_queue_entry
*entry)
EXPORT_SYMBOL_GPL(nf_queue_entry_release_refs);
/* Bump dev refs so they don't vanish while packet is out */
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
{
struct nf_hook_state *state = >state;
+ if (state->sk && !refcount_inc_not_zero(>sk->sk_refcnt))
+ return false;
+
if (state->in)
[Kernel-packages] [Bug 1993609] Re: linux-firmware: add sdio firmware for qca9377 wifi module
** Description changed: - This is for tracking purpose. + This firmware is already in the linux-firmware of upstream and jammy + + [Impact] + We have a UC20 project to enable the qca9377 sdio wifi on a imx6ull + board, without this firmware the ath10k-sdio wifi driver will fail to + initialize and the wifi can't work. + + [Fix] + Backport 1 patch from upstream linux-firmware. + + [Test] + Install the patched linux-firmware and boot the kernel on that board, + the ath10k-sdio.ko could find and load the firmware successfully and + the wifi function worked well. + + + [Where problems could occur] + The patch is from upstream and Jammy already has this patch, this patch + just adds new files to existing firmware, the regression possibility is + very low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1993609 Title: linux-firmware: add sdio firmware for qca9377 wifi module Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Focal: In Progress Bug description: This firmware is already in the linux-firmware of upstream and jammy [Impact] We have a UC20 project to enable the qca9377 sdio wifi on a imx6ull board, without this firmware the ath10k-sdio wifi driver will fail to initialize and the wifi can't work. [Fix] Backport 1 patch from upstream linux-firmware. [Test] Install the patched linux-firmware and boot the kernel on that board, the ath10k-sdio.ko could find and load the firmware successfully and the wifi function worked well. [Where problems could occur] The patch is from upstream and Jammy already has this patch, this patch just adds new files to existing firmware, the regression possibility is very low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993609] [NEW] linux-firmware: add sdio firmware for qca9377 wifi module
Public bug reported: This is for tracking purpose. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: High Status: In Progress ** Affects: linux-firmware (Ubuntu Focal) Importance: High Assignee: Hui Wang (hui.wang) Status: In Progress ** Tags: oem-priority originate-from-1990944 tillamook ** Changed in: linux-firmware (Ubuntu) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu) Status: New => In Progress ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: oem-priority originate-from-1990944 tillamook -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1993609 Title: linux-firmware: add sdio firmware for qca9377 wifi module Status in HWE Next: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Focal: In Progress Bug description: This is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
I suspect the same cause as the bug report I filled: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993217 that is commit: 72cd3810e52c606595f9e1a2d442a4cc6e6a3551 is the first bad commit commit 72cd3810e52c606595f9e1a2d442a4cc6e6a3551 Author: Hui Wang Date: Mon May 6 22:09:32 2019 +0800 ALSA: hda/hdmi - Consider eld_valid when reporting jack event -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993217] Re: old commit make HDMI audio not available if not eld_valid
This might be the same problem as:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993217
Title:
old commit make HDMI audio not available if not eld_valid
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is on my friend laptop with his TV.
HDMI audio not available in pavucontrol (profile say unplugged, unavailable)
in kernel versions with bugs.
It is just shown as an audio output (HDMI audio) on kernels where it is
working.
When not working, I can play with aplay -D HDMI ...
When working... I select HDMI audio in output, and test sound ok, Youtube
videos ok, etc.
4.9.177 working.
4.9.178 not working.
I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
is between those versions, and is related to audio (realtek in part).
More info at:
https://forums.linuxmint.com/viewtopic.php?f=49=383607=2246352#p2246352
although the laptop now runs ... 17.10 I think (a version with a not broken
kernel).
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: client 1023 F pulseaudio
/dev/snd/pcmC0D0p: client 1023 F...m pulseaudio
/dev/snd/controlC1: client 1023 F pulseaudio
CasperMD5json: {
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: SAMSUNG ELECTRONICS CO., LTD. R425D/R525D
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
LANGUAGE=fr_CA:fr
TERM=xterm-256color
PATH=(custom, no user)
LANG=fr_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic
root=UUID=2db14083-ebb6-4a5a-b0b1-4a65e79069d7 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.15.0-50-generic N/A
linux-backports-modules-5.15.0-50-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.5
Tags: vanessa apport-hook-error
Uname: Linux 5.15.0-50-generic x86_64
UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 10/16/2010
dmi.bios.release: 2.0
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02UF
dmi.board.name: R425D/R525D
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr02UF:bd10/16/2010:br2.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnR425D/R525D:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR425D/R525D:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:sku:
dmi.product.name: R425D/R525D
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993217/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993532] Re: Unable to see second monitor
Thanks for the bug report. I am slightly concerned the attached kernel log mentions "evdi" which is used for USB-connected displays (via DisplayLink chips inside dongles). So long as you have USB-C ports, evdi/DisplayLink should not be necessary. So I suggest either: (a) Get some native USB-C to monitor cables that don't have built-in dongles; or (b) Install the manufacturer's driver (https://www.synaptics.com/products/displaylink- graphics/downloads/ubuntu), which I know from previous experience with DisplayLink is more reliable than the default built-in driver. Please also run this command to check what monitors are connected: grep connect /sys/class/drm/*/status ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Incomplete Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993560] 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/1993560 Title: iwlwifi errors Status in linux package in Ubuntu: Confirmed Bug description: I do experience intermittent WLAN problems, with connections getting lost after a few seconds, and continuous (unsuccessful) reconnection attempts. Unfortunately, I am unable to provide a specific error description, but in dmesg I see lines related to iwlwifi which suggest some microcode does not execute as it should. I add these as attachment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Oct 19 17:34:47 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22e7] InstallationDate: Installed on 2022-10-15 (4 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CCS3HD00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=9f272456-a6f0-404d-b699-e1e936418b0c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CCS3HD00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CCS3HD00:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CCS3HD00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CC_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CCS3HD00 dmi.product.sku: LENOVO_MT_21CC_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Re: unable to boot kernel 5.15.0.50
*** This bug is a duplicate of bug 1992679 *** https://bugs.launchpad.net/bugs/1992679 This sounds like bug 1992679. ** This bug has been marked a duplicate of bug 1992679 Can not login after new kernel installed (nvidia driver crashed) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Confirmed Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993567] Re: devices buf
Thanks for the bug report. > touch mouse donesnt work and the heat of video card unavailable on sensor extenstion Those are two unrelated issues. Please choose one of them to discuss here. ** Package changed: linux (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Confirmed => 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/1993567 Title: devices buf Status in Ubuntu: Incomplete Bug description: touch mouse donesnt work and the heat of video card unavailable on sensor extenstion ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ahmad 1899 F pulseaudio /dev/snd/pcmC0D0p: ahmad 1899 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 20:08:00 2022 InstallationDate: Installed on 2022-10-11 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 13d3:3490 IMC Networks Bus 001 Device 003: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 18f8:1486 [Maxxter] X5s ZEUS Macro Pro Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540UBR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=67ffb376-9c2a-4fc6-a9d2-aa844b3f17da ro quiet splash acpi=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 08/13/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540UBR.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540UBR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540UBR.301:bd08/13/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540UBR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UBR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X540UBR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1993567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
something like "nvidia-driver-515-open" and which should be fixed by commit a36807ad1c738abe7980dd09d001549a224b71b3 Author: Alberto Milone Date: Tue Aug 23 17:03:01 2022 +0200 UbuntuDrivers/detect.py: fix driver series detection in nvidia_desktop_pre_installation_hook Seems like u-d-c from -proposed should fix comment#35. root cause could be n-g-d-515 shouldn't be landed in -updates before u-d-c. please see https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-515/+bug/1988836 If someone can enable -proposed and then upgrading u-d-c then try comment#33, then it'll help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version:
[Kernel-packages] [Bug 1993516] Re: bluetooth input freezes for a few second after brief inactivity
There certainly are Bluetooth errors in the log, and some are kernel related. I suggest the best thing to do here is to try a newer Ubuntu release like 22.04.1. Because there's a good chance this was a bug in the kernel, Intel firmware, or BlueZ that has already been fixed. ** Summary changed: - bluetooth input freezes for a few second after brief inactivity + [focal] [Intel 8260] bluetooth input freezes for a few second after brief inactivity -- 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/1993516 Title: [focal] [Intel 8260] bluetooth input freezes for a few second after brief inactivity Status in bluez package in Ubuntu: New Bug description: I have a Logitech bluetooth mouse (M650) and keyboard (K380, details in the attached log). I almost never power down the laptop: I suspend and resume it. Sometimes when I resume from suspend everything works flawlessly. Other times, there's a 2-3s "freeze" after just several seconds of input inactivity, during which moving the mouse or pressing keyboard keys gives no response. After 2-3s, all the keys pressed during the freeze suddenly appear on screen. Restarting the bluetooth service, going to airplane mode and back or turning the mouse and keyboard on and off does not help at all. The delay makes using these input devices barely usable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 11:25:13 2022 InstallationDate: Installed on 2017-02-18 (2068 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=2b559de5-44d4-4f98-a211-a39edbb31bc8 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2022-08-02 (77 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 03MCRF dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd10/02/2019:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn03MCRF:rvrA09:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E5570 dmi.product.sku: 06DF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: B8:8A:60:C5:C9:BF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:34304 acl:977 sco:0 events:2580 errors:0 TX bytes:603917 acl:73 sco:0 commands:2473 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2022-10-19T11:24:40.907104 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1993516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993560] Re: iwlwifi errors
** Summary changed: - wlan errors + iwlwifi errors ** Package changed: xorg (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/1993560 Title: iwlwifi errors Status in linux package in Ubuntu: Confirmed Bug description: I do experience intermittent WLAN problems, with connections getting lost after a few seconds, and continuous (unsuccessful) reconnection attempts. Unfortunately, I am unable to provide a specific error description, but in dmesg I see lines related to iwlwifi which suggest some microcode does not execute as it should. I add these as attachment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Oct 19 17:34:47 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22e7] InstallationDate: Installed on 2022-10-15 (4 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CCS3HD00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=9f272456-a6f0-404d-b699-e1e936418b0c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CCS3HD00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CCS3HD00:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CCS3HD00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CC_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CCS3HD00 dmi.product.sku: LENOVO_MT_21CC_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993560/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993560] [NEW] iwlwifi errors
You have been subscribed to a public bug: I do experience intermittent WLAN problems, with connections getting lost after a few seconds, and continuous (unsuccessful) reconnection attempts. Unfortunately, I am unable to provide a specific error description, but in dmesg I see lines related to iwlwifi which suggest some microcode does not execute as it should. I add these as attachment. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Oct 19 17:34:47 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22e7] InstallationDate: Installed on 2022-10-15 (4 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 21CCS3HD00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=9f272456-a6f0-404d-b699-e1e936418b0c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2022 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: N3AET65W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 21CCS3HD00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN3AET65W(1.30):bd08/02/2022:br1.30:efr1.14:svnLENOVO:pn21CCS3HD00:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CCS3HD00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CC_BU_Think_FM_ThinkPadX1CarbonGen10: dmi.product.family: ThinkPad X1 Carbon Gen 10 dmi.product.name: 21CCS3HD00 dmi.product.sku: LENOVO_MT_21CC_BU_Think_FM_ThinkPad X1 Carbon Gen 10 dmi.product.version: ThinkPad X1 Carbon Gen 10 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu ubuntu -- iwlwifi errors https://bugs.launchpad.net/bugs/1993560 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992474] Re: [Lenovo ThinkPad P1 Gen2] Flickering started right after install
If you select 'Ubuntu on Wayland' on the login screen, does the flickering still occur? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992474 Title: [Lenovo ThinkPad P1 Gen2] Flickering started right after install Status in linux package in Ubuntu: Incomplete Bug description: My computer is a Lenovo Thinkpad p-Series Gen 2 with Intel Core i9. I've tried updating my grub file as is suggested in Bugs #1970426, #1958191, and #1973676. That is, I've tried GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" And, I've tried cstate=4. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon 2093 F pulseaudio /dev/snd/controlC1: moon 2093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 08:05:20 2022 InstallationDate: Installed on 2020-03-29 (926 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=39110848-f164-47a5-bf96-fda0216c46fb ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (51 days ago) dmi.bios.date: 05/07/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:br1.31:efr1.23:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QT_BU_Think_FM_ThinkPadP1Gen2: dmi.product.family: ThinkPad P1 Gen2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen2 dmi.product.version: ThinkPad P1 Gen2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990294] Re: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..."
Tried to reproduce this issue on Ampere Altra SoC (not AltraMax) with focal grub and 5.15.0-43-generic kernel but can not reproduce. It reboot 222 times successfully. I will try to reproduce on an altramax machine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990294 Title: Ampere AltraMax sometimes hangs after "EFI stub: Exiting boot services..." Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When kernel test rebooted onto the 5.15.0-43-generic HWE kernel, no output appeared on the console after the EFI stub: Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint A0 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint 92 Checkpoint AD EFI stub: Booting Linux Kernel... EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: Using DTB from configuration table EFI stub: Exiting boot services... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1990294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993217] Re: old commit make HDMI audio not available if not eld_valid
** Summary changed:
- HDMI audio not available RS880 between 4.9.177 and 4.9.178
+ old commit make HDMI audio not available if not eld_valid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993217
Title:
old commit make HDMI audio not available if not eld_valid
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is on my friend laptop with his TV.
HDMI audio not available in pavucontrol (profile say unplugged, unavailable)
in kernel versions with bugs.
It is just shown as an audio output (HDMI audio) on kernels where it is
working.
When not working, I can play with aplay -D HDMI ...
When working... I select HDMI audio in output, and test sound ok, Youtube
videos ok, etc.
4.9.177 working.
4.9.178 not working.
I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
is between those versions, and is related to audio (realtek in part).
More info at:
https://forums.linuxmint.com/viewtopic.php?f=49=383607=2246352#p2246352
although the laptop now runs ... 17.10 I think (a version with a not broken
kernel).
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: client 1023 F pulseaudio
/dev/snd/pcmC0D0p: client 1023 F...m pulseaudio
/dev/snd/controlC1: client 1023 F pulseaudio
CasperMD5json: {
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: SAMSUNG ELECTRONICS CO., LTD. R425D/R525D
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
LANGUAGE=fr_CA:fr
TERM=xterm-256color
PATH=(custom, no user)
LANG=fr_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic
root=UUID=2db14083-ebb6-4a5a-b0b1-4a65e79069d7 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.15.0-50-generic N/A
linux-backports-modules-5.15.0-50-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.5
Tags: vanessa apport-hook-error
Uname: Linux 5.15.0-50-generic x86_64
UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 10/16/2010
dmi.bios.release: 2.0
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02UF
dmi.board.name: R425D/R525D
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr02UF:bd10/16/2010:br2.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnR425D/R525D:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR425D/R525D:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:sku:
dmi.product.name: R425D/R525D
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993217/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989144] Re: unprivileged users may trigger page cache invalidation WARN
This bug is awaiting verification that the linux/4.15.0-195.206 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989144 Title: unprivileged users may trigger page cache invalidation WARN Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Unprivileged users may trigger a page cache invalidation failure when doing parallel direct I/O and buffered I/O. On some kernels, that may lead to a WARN. [ 22.415082] WARNING: CPU: 3 PID: 3404 at /build/linux-GtMq7R/linux-4.15.0/fs/iomap.c:903 iomap_dio_actor+0xbd/0x460 [ 22.415083] Modules linked in: xfs isofs kvm_intel kvm irqbypass joydev input_leds serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse ahci libahci virtio_blk virtio_net [ 22.415099] CPU: 3 PID: 3404 Comm: xfs_io Not tainted 4.15.0-192-generic #203-Ubuntu [ 22.415100] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 22.415103] RIP: 0010:iomap_dio_actor+0xbd/0x460 [ 22.415104] RSP: 0018:b7c782fe7bf0 EFLAGS: 00010202 [ 22.415104] RAX: 0002 RBX: RCX: 0009 [ 22.415105] RDX: 01ff RSI: RDI: b7c782fe7e20 [ 22.415105] RBP: b7c782fe7c68 R08: b7c782fe7c88 R09: 9bbc9f48fba0 [ 22.415106] R10: 0001 R11: R12: 0009 [ 22.415106] R13: 9bbc9f48fba0 R14: b7c782fe7c88 R15: 1000 [ 22.415107] FS: 7f2b802ed700() GS:9bbcbfd8() knlGS: [ 22.415107] CS: 0010 DS: ES: CR0: 80050033 [ 22.415108] CR2: 01639000 CR3: 1e6b0003 CR4: 00760ee0 [ 22.415110] PKRU: 5554 [ 22.415110] Call Trace: [ 22.415122] ? iomap_dio_zero+0x130/0x130 [ 22.415123] iomap_apply+0xa5/0x120 [ 22.415124] ? iomap_dio_zero+0x130/0x130 [ 22.415125] iomap_dio_rw+0x2f3/0x430 [ 22.415126] ? iomap_dio_zero+0x130/0x130 [ 22.415148] xfs_file_dio_aio_read+0x68/0xf0 [xfs] [ 22.415157] ? xfs_file_dio_aio_read+0x68/0xf0 [xfs] [ 22.415165] xfs_file_read_iter+0xbf/0xe0 [xfs] [ 22.415170] new_sync_read+0xe4/0x130 [ 22.415171] __vfs_read+0x29/0x40 [ 22.415172] vfs_read+0x8e/0x130 [ 22.415173] SyS_pread64+0x95/0xb0 [ 22.415176] do_syscall_64+0x73/0x130 [ 22.415183] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 22.415184] RIP: 0033:0x7f2b7fbc0b73 [ 22.415185] RSP: 002b:7ffc134e1a58 EFLAGS: 0246 ORIG_RAX: 0011 [ 22.415186] RAX: ffda RBX: RCX: 7f2b7fbc0b73 [ 22.415186] RDX: 1000 RSI: 01639000 RDI: 0003 [ 22.415186] RBP: R08: R09: [ 22.415187] R10: R11: 0246 R12: 7ffc134e1b00 [ 22.415187] R13: 0002 R14: R15: [ 22.415188] Code: 21 d0 48 89 45 a0 0f 85 aa 03 00 00 41 0f b7 46 18 66 83 f8 03 0f 84 7e 02 00 00 66 83 f8 04 74 52 66 83 f8 01 0f 84 c8 02 00 00 <0f> 0b 48 c7 45 a0 fb ff ff ff 48 8b 5d d0 65 48 33 1c 25 28 00 [Test case] Run xfstests generic/446 test. [Potential regressions] Data corruption could be caused, though it is expected to be caused in such scenarions anyway. That should affecte direct I/O. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989144/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
This bug is awaiting verification that the linux/4.15.0-195.206 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: In Progress Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990690] Re: Users belonging to video group may trigger a deadlock WARN
This bug is awaiting verification that the linux/4.15.0-195.206 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990690
Title:
Users belonging to video group may trigger a deadlock WARN
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
("fbcon: Prevent that screen size is smaller than font size") introduced
an extraneous lock_fb_info line into the ioctl flow in fbmem.c.
This line only exists in bionic tree.
Users belonging to video group may trigger a deadlock and potentially
lock the system.
WARNING: possible recursive locking detected
4.15.0-195-generic #206 Not tainted
refresh/1248 is trying to acquire lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
but task is already holding lock:
(_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
lock(_info->lock);
lock(_info->lock);
*** DEADLOCK ***
May be due to missing lock nesting notation
2 locks held by refresh/1248:
#0: (console_lock){+.+.}, at: [<8000aa2b>] do_fb_ioctl+0x435/0x5e0
#1: (_info->lock){+.+.}, at: [<4c154cfe>] lock_fb_info+0x1d/0x40
stack backtrace:
CPU: 0 PID: 1248 Comm: refresh Not tainted 4.15.0-195-generic #206
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014
Call Trace:
dump_stack+0x98/0xd2
__lock_acquire+0x736/0x1480
? sched_clock_local+0x17/0x90
? sched_clock+0x9/0x10
? sched_clock_local+0x17/0x90
lock_acquire+0xa3/0x1e0
? lock_acquire+0xa3/0x1e0
? lock_fb_info+0x1d/0x40
? lock_fb_info+0x1d/0x40
__mutex_lock+0x65/0x970
? lock_fb_info+0x1d/0x40
? sched_clock_local+0x17/0x90
? lock_acquire+0xa3/0x1e0
mutex_lock_nested+0x1b/0x20
? mutex_lock_nested+0x1b/0x20
lock_fb_info+0x1d/0x40
do_fb_ioctl+0x57a/0x5e0
? __fd_install+0x5/0x250
fb_ioctl+0x33/0x40
? fb_ioctl+0x33/0x40
do_vfs_ioctl+0xa9/0x6d0
? putname+0x4c/0x60
? do_sys_open+0x13d/0x370
SyS_ioctl+0x79/0x90
do_syscall_64+0x7b/0x1e0
entry_SYSCALL_64_after_hwframe+0x46/0xbb
RIP: 0033:0x7f22acca7217
RSP: 002b:7ffe2a930b48 EFLAGS: 0213 ORIG_RAX: 0010
RAX: ffda RBX: RCX: 7f22acca7217
RDX: 7ffe2a930c30 RSI: 4601 RDI: 0003
RBP: 7ffe2a930d40 R08: R09:
R10: R11: 0213 R12: 5624ac8fc7c0
R13: 7ffe2a930e20 R14: R15:
[Test case]
Run a sample framebuffer userspace test to call FBIOPUT_VSCREENINFO
and verified with LOCKDEP.
[Potential regressions]
There are no new potential regressions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990690/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991774] Re: Memory leak while using NFQUEUE to delegate the decision on TCP packets to userspace processes
This bug is awaiting verification that the linux/4.15.0-195.206 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-bionic' to 'verification-done-bionic'. If the
problem still exists, change the tag 'verification-needed-bionic' to
'verification-failed-bionic'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991774
Title:
Memory leak while using NFQUEUE to delegate the decision on TCP
packets to userspace processes
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Bug description:
[Impact]
Environment: v4.15.0-177-generic Xenial ESM
Using NFQUEUE to delegate the decision on TCP packets to userspace processes
will cause memory leak.
The symptom is that TCP slab objects will accumulate and eventually cause OOM.
[Fix]
There is a discrepancy between backport and upstream commit.
[Upstream Commit c3873070247d9e3c7a6b0cf9bf9b45e8018427b1]
diff --git a/include/net/netfilter/nf_queue.h
b/include/net/netfilter/nf_queue.h
index 9eed51e920e8..980daa6e1e3a 100644
--- a/include/net/netfilter/nf_queue.h
+++ b/include/net/netfilter/nf_queue.h
@@ -37,7 +37,7 @@ void nf_register_queue_handler(const struct
nf_queue_handler *qh);
void nf_unregister_queue_handler(void);
void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
void nf_queue_entry_free(struct nf_queue_entry *entry);
static inline void init_hashrandom(u32 *jhash_initval)
diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
index 5ab0680db445..e39549c55945 100644
--- a/net/netfilter/nf_queue.c
+++ b/net/netfilter/nf_queue.c
@@ -96,19 +96,21 @@ static void __nf_queue_entry_init_physdevs(struct
nf_queue_entry *entry)
}
/* Bump dev refs so they don't vanish while packet is out */
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry)
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry)
{
struct nf_hook_state *state = >state;
+ if (state->sk && !refcount_inc_not_zero(>sk->sk_refcnt))
+ return false;
+
dev_hold(state->in);
dev_hold(state->out);
- if (state->sk)
- sock_hold(state->sk);
#if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
dev_hold(entry->physin);
dev_hold(entry->physout);
#endif
+ return true;
}
EXPORT_SYMBOL_GPL(nf_queue_entry_get_refs);
@@ -196,7 +198,10 @@ static int __nf_queue(struct sk_buff *skb, const
struct nf_hook_state *state,
__nf_queue_entry_init_physdevs(entry);
- nf_queue_entry_get_refs(entry);
+ if (!nf_queue_entry_get_refs(entry)) {
+ kfree(entry);
+ return -ENOTCONN;
+ }
switch (entry->state.pf) {
case AF_INET:
diff --git a/net/netfilter/nfnetlink_queue.c b/net/netfilter/nfnetlink_queue.c
index ea2d9c2a44cf..64a6acb6aeae 100644
--- a/net/netfilter/nfnetlink_queue.c
+++ b/net/netfilter/nfnetlink_queue.c
@@ -710,9 +710,15 @@ static struct nf_queue_entry *
nf_queue_entry_dup(struct nf_queue_entry *e)
{
struct nf_queue_entry *entry = kmemdup(e, e->size, GFP_ATOMIC);
- if (entry)
- nf_queue_entry_get_refs(entry);
- return entry;
+
+ if (!entry)
+ return NULL;
+
+ if (nf_queue_entry_get_refs(entry))
+ return entry;
+
+ kfree(entry);
+ return NULL;
}
#if IS_ENABLED(CONFIG_BRIDGE_NETFILTER)
[Backport Commit 4d032d60432327f068f03b516f5b6c51ceb17d15]
diff --git a/include/net/netfilter/nf_queue.h
b/include/net/netfilter/nf_queue.h
index 814058d0f167..f38cc6092c5a 100644
--- a/include/net/netfilter/nf_queue.h
+++ b/include/net/netfilter/nf_queue.h
@@ -32,7 +32,7 @@ void nf_register_queue_handler(struct net *net, const
struct nf_queue_handler *q
void nf_unregister_queue_handler(struct net *net);
void nf_reinject(struct nf_queue_entry *entry, unsigned int verdict);
-void nf_queue_entry_get_refs(struct nf_queue_entry *entry);
+bool nf_queue_entry_get_refs(struct nf_queue_entry *entry);
void nf_queue_entry_release_refs(struct nf_queue_entry *entry);
static inline void init_hashrandom(u32 *jhash_initval)
diff --git a/net/netfilter/nf_queue.c b/net/netfilter/nf_queue.c
index 59340b3ef7ef..dbc45165c533 100644
--- a/net/netfilter/nf_queue.c
+++ b/net/netfilter/nf_queue.c
@@ -80,10 +80,13 @@ void
[Kernel-packages] [Bug 1993217] Re: HDMI audio not available RS880 between 4.9.177 and 4.9.178
I believe this is the situation discussed in:
https://gitlab.freedesktop.org/drm/amd/-/issues/1569
Also, I tested master head this morning (showing 6.0.0-rc6, and it was
broken.
I had tried a reverse of this commit and previous one, but it was broken
too (I probably did not made the right choices when seeing conflicts).
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1569
https://gitlab.freedesktop.org/drm/amd/-/issues/1569
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993217
Title:
HDMI audio not available RS880 between 4.9.177 and 4.9.178
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is on my friend laptop with his TV.
HDMI audio not available in pavucontrol (profile say unplugged, unavailable)
in kernel versions with bugs.
It is just shown as an audio output (HDMI audio) on kernels where it is
working.
When not working, I can play with aplay -D HDMI ...
When working... I select HDMI audio in output, and test sound ok, Youtube
videos ok, etc.
4.9.177 working.
4.9.178 not working.
I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
is between those versions, and is related to audio (realtek in part).
More info at:
https://forums.linuxmint.com/viewtopic.php?f=49=383607=2246352#p2246352
although the laptop now runs ... 17.10 I think (a version with a not broken
kernel).
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: client 1023 F pulseaudio
/dev/snd/pcmC0D0p: client 1023 F...m pulseaudio
/dev/snd/controlC1: client 1023 F pulseaudio
CasperMD5json: {
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: SAMSUNG ELECTRONICS CO., LTD. R425D/R525D
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
LANGUAGE=fr_CA:fr
TERM=xterm-256color
PATH=(custom, no user)
LANG=fr_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic
root=UUID=2db14083-ebb6-4a5a-b0b1-4a65e79069d7 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.15.0-50-generic N/A
linux-backports-modules-5.15.0-50-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.5
Tags: vanessa apport-hook-error
Uname: Linux 5.15.0-50-generic x86_64
UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 10/16/2010
dmi.bios.release: 2.0
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02UF
dmi.board.name: R425D/R525D
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr02UF:bd10/16/2010:br2.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnR425D/R525D:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR425D/R525D:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:sku:
dmi.product.name: R425D/R525D
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993217/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993217] Re: HDMI audio not available RS880 between 4.9.177 and 4.9.178
Found the offending commit:
Did not verify this, but I suspect this is the case:
After this change, the driver will not report Jack_is_plugged event
through hdmi_present_sense_via_verbs() if monitor_present is 1 and
eld_valid is 0.
paul@rabachi:~/colinKernels/new4.9.180/my4.9.180$ LANG=en git bisect replay
bisect.log
Already on 'master'
Your branch is ahead of 'origin/master' by 4 commits.
(use "git push" to publish your local commits)
72cd3810e52c606595f9e1a2d442a4cc6e6a3551 is the first bad commit
commit 72cd3810e52c606595f9e1a2d442a4cc6e6a3551
Author: Hui Wang
Date: Mon May 6 22:09:32 2019 +0800
ALSA: hda/hdmi - Consider eld_valid when reporting jack event
commit 7f641e26a6df9269cb25dd7a4b0a91d6586ed441 upstream.
On the machines with AMD GPU or Nvidia GPU, we often meet this issue:
after s3, there are 4 HDMI/DP audio devices in the gnome-sound-setting
even there is no any monitors plugged.
When this problem happens, we check the /proc/asound/cardX/eld#N.M, we
will find the monitor_present=1, eld_valid=0.
The root cause is BIOS or GPU driver makes the PRESENCE valid even no
monitor plugged, and of course the driver will not get the valid
eld_data subsequently.
In this situation, we should not report the jack_plugged event, to do
so, let us change the function hdmi_present_sense_via_verbs(). In this
function, it reads the pin_sense via snd_hda_pin_sense(), after
calling this function, the jack_dirty is 0, and before exiting
via_verbs(), we change the shadow pin_sense according to both
monitor_present and eld_valid, then in the snd_hda_jack_report_sync(),
since the jack_dirty is still 0, it will report jack event according
to this modified shadow pin_sense.
After this change, the driver will not report Jack_is_plugged event
through hdmi_present_sense_via_verbs() if monitor_present is 1 and
eld_valid is 0.
Signed-off-by: Hui Wang
Cc:
Signed-off-by: Takashi Iwai
Signed-off-by: Greg Kroah-Hartman
:04 04 0280e65d8aca2561b6ed8ee27383d1cd0e3cc022
ebe57ab9f50fdb2851d074f5d2c95f5e74beb541 M sound
paul@rabachi:~/colinKernels/new4.9.180/my4.9.180$
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993217
Title:
HDMI audio not available RS880 between 4.9.177 and 4.9.178
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is on my friend laptop with his TV.
HDMI audio not available in pavucontrol (profile say unplugged, unavailable)
in kernel versions with bugs.
It is just shown as an audio output (HDMI audio) on kernels where it is
working.
When not working, I can play with aplay -D HDMI ...
When working... I select HDMI audio in output, and test sound ok, Youtube
videos ok, etc.
4.9.177 working.
4.9.178 not working.
I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
is between those versions, and is related to audio (realtek in part).
More info at:
https://forums.linuxmint.com/viewtopic.php?f=49=383607=2246352#p2246352
although the laptop now runs ... 17.10 I think (a version with a not broken
kernel).
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: client 1023 F pulseaudio
/dev/snd/pcmC0D0p: client 1023 F...m pulseaudio
/dev/snd/controlC1: client 1023 F pulseaudio
CasperMD5json: {
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: SAMSUNG ELECTRONICS CO., LTD. R425D/R525D
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
LANGUAGE=fr_CA:fr
TERM=xterm-256color
PATH=(custom, no user)
LANG=fr_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic
root=UUID=2db14083-ebb6-4a5a-b0b1-4a65e79069d7 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.15.0-50-generic N/A
linux-backports-modules-5.15.0-50-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.5
Tags: vanessa apport-hook-error
Uname: Linux 5.15.0-50-generic x86_64
UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 10/16/2010
dmi.bios.release: 2.0
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02UF
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
There is no test case for this in the ubuntu-manual-tests code which contains the test cases which are listed in the ISO tracker. If this is a supported installation method then we should have a test case for it. ** Also affects: ubuntu-manual-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: New Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993587] [NEW] No HDMI output on pi4 8Gb
Public bug reported: Hardware is an rpi 4 8Gb I installed the latest ubuntu desktop image onto an sd card. I used this image: http://cdimage.ubuntu.com/ubuntu/daily-preinstalled/20221018.1/kinetic- preinstalled-desktop-arm64+raspi.img.xz I verified that the sha256sum matches. After unxz'ing it, I made a bootable sd card with: dd if=kinetic-preinstalled-desktop-arm64+raspi.img of=/dev/sda When I boot, I see the BIOS boot screen, then the color palette screen, then just blackness. I've tried with two different known working monitors and two different known working cables. I also tried installing Raspbery Pi OS the same way to the same 32Gb sd card and it booted just fine. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Description changed: Hardware is an rpi 4 8Gb I installed the latest ubuntu desktop image onto an sd card. I used this image: http://cdimage.ubuntu.com/ubuntu/daily-preinstalled/20221018.1/kinetic- preinstalled-desktop-arm64+raspi.img.xz I verified that the sha256sum matches. After unxz'ing it, I made a bootable sd card with: dd if=kinetic-preinstalled-desktop-arm64+raspi.img of=/dev/sda When I boot, I see the BIOS boot screen, then the color palette screen, then just blackness. I've tried with two different known working monitors and two different known working cables. - I also tried installing Raspbery Pi OS the same way to the same sd card - and it booted just fine. + I also tried installing Raspbery Pi OS the same way to the same 32Gb sd + card and it booted just fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1993587 Title: No HDMI output on pi4 8Gb Status in linux-raspi package in Ubuntu: New Bug description: Hardware is an rpi 4 8Gb I installed the latest ubuntu desktop image onto an sd card. I used this image: http://cdimage.ubuntu.com/ubuntu/daily- preinstalled/20221018.1/kinetic-preinstalled-desktop- arm64+raspi.img.xz I verified that the sha256sum matches. After unxz'ing it, I made a bootable sd card with: dd if=kinetic-preinstalled-desktop-arm64+raspi.img of=/dev/sda When I boot, I see the BIOS boot screen, then the color palette screen, then just blackness. I've tried with two different known working monitors and two different known working cables. I also tried installing Raspbery Pi OS the same way to the same 32Gb sd card and it booted just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1993587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991254] Re: No HDMI sound output from alsa in server (no KMS)
** Changed in: ubuntu-release-notes Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1991254 Title: No HDMI sound output from alsa in server (no KMS) Status in Release Notes for Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Kinetic: Fix Released Bug description: During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi image, on a Raspberry Pi 4B and 3B, I noted that the HDMI "sound card" no longer appears in /proc/asound/cards; only the Headphones output (from the AUX socket on the board) appears. I checked with the current linux-raspi in the release pocket (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi), and both exhibit the same issue. On Kinetic: $ cat /proc/asound/cards 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones On Jammy: $ cat /proc/asound/cards 0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1 bcm2835 HDMI 1 1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811254] Re: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function
Hello I would like to give a positive feedback. The upgrade to LM21Cin. fixed all hotkey LED problems. System: Host: LM21-Test Kernel: 5.15.0-52-generic arch: x86_64 bits: 64 Desktop: Cinnamon v: 5.4.12 Distro: Linux Mint 21 Vanessa. Thanks a lot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1811254 Title: HP ProBook 470 G5, LED's in Hotkeys f5, f8 and f11 without function Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: Notebook: HP ProBook 470 G5 (3KZ03EA) Distro: Linux Mint 19.1 Tessa Desktop: Cinnamon 4.0.8 Kernel: 4.15.0-43-generic x86_64 bits: 64 The functions of all hotkeys are given, but the LED's in the [f5] Speaker-mute, [f8] Micro-mute and [f11] Wireless on/off Buttons do not show the status. Disturbing is also the LED in [f11] permanently lit. This is my first bug report to launchpad and I ask for leniency and troubleshooting support. I created 12 logs, unfortunately the upload did not work at once: acpi_listen.txt apt-cache-policy dmesg.log lsb_release lsinput.log lspci-vnvn.log rfkill_list.txt udev-db.txt version.log xev keypress test.txt xkbcomp.txt xkbmap.txt Previous attempts: My on-board search for other HP ProBook Hotkey LED-issues led me to this bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705586 but the solution to the file: /etc/modprobe.d/alsa-base.conf to supplement the entry: options snd-hda-intel mode = mute-led-gpio did not lead to the solution here. Presumably, the failure results from a different ubuntu-version and/or a another kernel. Information: This problem was previously discussed on linuxmintusers.de: https://www.linuxmintusers.de/index.php?topic=51737.msg710376#msg710376 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992474] Re: [Lenovo ThinkPad P1 Gen2] Flickering started right after install
Here's the text file ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992474/+attachment/5625338/+files/journal.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/1992474 Title: [Lenovo ThinkPad P1 Gen2] Flickering started right after install Status in linux package in Ubuntu: Incomplete Bug description: My computer is a Lenovo Thinkpad p-Series Gen 2 with Intel Core i9. I've tried updating my grub file as is suggested in Bugs #1970426, #1958191, and #1973676. That is, I've tried GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.enable_dc=0 intel_idle.max_cstate=2" And, I've tried cstate=4. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: moon 2093 F pulseaudio /dev/snd/controlC1: moon 2093 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Oct 11 08:05:20 2022 InstallationDate: Installed on 2020-03-29 (926 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QTCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=39110848-f164-47a5-bf96-fda0216c46fb ro quiet splash i915.enable_dc=0 intel_idle.max_cstate=2 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-08-20 (51 days ago) dmi.bios.date: 05/07/2020 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QTCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:br1.31:efr1.23:svnLENOVO:pn20QTCTO1WW:pvrThinkPadP1Gen2:rvnLENOVO:rn20QTCTO1WW:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QT_BU_Think_FM_ThinkPadP1Gen2: dmi.product.family: ThinkPad P1 Gen2 dmi.product.name: 20QTCTO1WW dmi.product.sku: LENOVO_MT_20QT_BU_Think_FM_ThinkPad P1 Gen2 dmi.product.version: ThinkPad P1 Gen2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** Tags added: foundations-triage-discuss ** Also affects: ubuntu-release-notes Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Release Notes for Ubuntu: New Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 787738]
Have a similar problem on t480 on kernel 6.0.2-arch1-1. The trackpoint works at first, then the input starts to get "mushy", then (after about 3 minutes of constant use) trackpoint freaks out (cursor teleports across the screen, random rmb/lmb/mmb presses). Disabling/Enabling both trackpad/trackpoint in bios has no effect on xinput cli output. Trackpoint is recognised as "PS/2 Generic Mouse". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/787738 Title: [Thinkpad X220/E220s/E420s] trackpoint/trackpoint displays odd behaviour Status in Linux: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Natty: Invalid Status in linux source package in Oneiric: Invalid Status in Fedora: New Bug description: Using the touchpad does not result in expected behavior. The touchpad has three "mouse" buttons on top, and none of these buttons currently function. Using xev does not show any output from these buttons. The touchpad itself works fine. There are two bottom buttons integrated with the touchpad, which do not work consistantly. The left button will sometimes act like a left-click and sometime like a right click, making it hard to move applications on the screen. The right button acts like a left click and only sometimes bring up menus. Trying to change from a left hand to a right hand mouse in mouse options does not change the behavior. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: linux-image-2.6.38-8-generic 2.6.38-8.42 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1235 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xd252 irq 44' Mixer name : 'Intel CougarPoint HDMI' Components : 'HDA:14f1506e,17aa21da,0010 HDA:80862805,80860101,0010' Controls : 20 Simple ctrls : 8 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw unknown' Mixer name : 'ThinkPad EC (unknown)' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Tue May 24 14:44:59 2011 HibernationDevice: RESUME=UUID=dd9d30b2-4950-42af-87e2-b304fc01e83d InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) MachineType: LENOVO 428623U ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=4985f74f-9e44-411f-8d41-73f9f68c057d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-2.6.38-8-generic N/A linux-backports-modules-2.6.38-8-generic N/A linux-firmware1.52 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET28WW (1.00 ) dmi.board.asset.tag: Not Available dmi.board.name: 428623U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET28WW(1.00):bd01/25/2011:svnLENOVO:pn428623U:pvrThinkPadX220:rvnLENOVO:rn428623U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 428623U dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/787738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993571] 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/1993571 Title: After 5.19.0-15, intel wifi 6 no longer available Status in linux package in Ubuntu: Confirmed Bug description: Since 5.19.0-16, which is also the kernel that broke booting on 11/12-gen Intel graphics, my Intel wifi is no longer working. This continues with the present release candidate kernel package -21. The wifi status reports simply that it is "unavailable" and no means to make it "available" is evident to me. On all prior kernels and Jammy it worked fine. % sudo iwconfig wlo1 wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on % sudo nmcli device show wlo1 GENERAL.DEVICE: wlo1 GENERAL.TYPE: wifi GENERAL.HWADDR: 38:87:D5:13:C1:30 GENERAL.MTU:1500 GENERAL.STATE: 20 (unavailable) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.GATEWAY:-- IP6.GATEWAY:-- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-21-generic 5.19.0-21.21 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwb1179 F wireplumber /dev/snd/seq:jwb1176 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Oct 19 10:24:26 2022 InstallationDate: Installed on 2021-12-31 (292 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=74e4f833-7902-4b06-9e40-e5b191272e08 ro quiet splash irqaffinity=0-15 isolcpus=16-19 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-21-generic N/A linux-backports-modules-5.19.0-21-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-06-07 (133 days ago) dmi.bios.date: 08/25/2022 dmi.bios.release: 20.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690-P WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd08/25/2022:br20.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981433] Re: [Asus Zenbook UX3402ZA] Sound doesn't work at all
Here are the output of the above hda-verb commands. arun@arunpc:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x40 [sudo] password for arun: nid = 0x20, verb = 0x500, param = 0x40 value = 0x0 arun@arunpc:~$ sudo hda-verb /dev/snd/hwC0D0 0x20 GET_PROC_COEF 0 nid = 0x20, verb = 0xc00, param = 0x0 value = 0x420 This didn't solve either. ** Attachment added: "alsa-info output file." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+attachment/5625330/+files/alsa-info.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/1981433 Title: [Asus Zenbook UX3402ZA] Sound doesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: Sound/speakers don't work at all on Asus Zenbook 14 OLED and other similar models with Realtek ALC294. No solution works. Audio is not muted, tried adding snd-hda arguments - no dice. This has been reported numerous times, when will a fix finally be rolled out?! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1730 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jul 12 13:57:05 2022 InstallationDate: Installed on 2022-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=40c924aa-99ad-4770-a66d-33d3359f6053 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-41-generic N/A linux-backports-modules-5.15.0-41-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981433/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993571] Re: After 5.19.0-15, intel wifi 6 no longer available
Possibly this is a NM bug. I have no idea. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993571 Title: After 5.19.0-15, intel wifi 6 no longer available Status in linux package in Ubuntu: New Bug description: Since 5.19.0-16, which is also the kernel that broke booting on 11/12-gen Intel graphics, my Intel wifi is no longer working. This continues with the present release candidate kernel package -21. The wifi status reports simply that it is "unavailable" and no means to make it "available" is evident to me. On all prior kernels and Jammy it worked fine. % sudo iwconfig wlo1 wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on % sudo nmcli device show wlo1 GENERAL.DEVICE: wlo1 GENERAL.TYPE: wifi GENERAL.HWADDR: 38:87:D5:13:C1:30 GENERAL.MTU:1500 GENERAL.STATE: 20 (unavailable) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.GATEWAY:-- IP6.GATEWAY:-- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-21-generic 5.19.0-21.21 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwb1179 F wireplumber /dev/snd/seq:jwb1176 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Oct 19 10:24:26 2022 InstallationDate: Installed on 2021-12-31 (292 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=74e4f833-7902-4b06-9e40-e5b191272e08 ro quiet splash irqaffinity=0-15 isolcpus=16-19 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-21-generic N/A linux-backports-modules-5.19.0-21-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-06-07 (133 days ago) dmi.bios.date: 08/25/2022 dmi.bios.release: 20.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690-P WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd08/25/2022:br20.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993567] 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/1993567 Title: devices buf Status in linux package in Ubuntu: Confirmed Bug description: touch mouse donesnt work and the heat of video card unavailable on sensor extenstion ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ahmad 1899 F pulseaudio /dev/snd/pcmC0D0p: ahmad 1899 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 20:08:00 2022 InstallationDate: Installed on 2022-10-11 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 13d3:3490 IMC Networks Bus 001 Device 003: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 18f8:1486 [Maxxter] X5s ZEUS Macro Pro Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540UBR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=67ffb376-9c2a-4fc6-a9d2-aa844b3f17da ro quiet splash acpi=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 08/13/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540UBR.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540UBR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540UBR.301:bd08/13/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540UBR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UBR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X540UBR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993571] [NEW] After 5.19.0-15, intel wifi 6 no longer available
Public bug reported: Since 5.19.0-16, which is also the kernel that broke booting on 11/12-gen Intel graphics, my Intel wifi is no longer working. This continues with the present release candidate kernel package -21. The wifi status reports simply that it is "unavailable" and no means to make it "available" is evident to me. On all prior kernels and Jammy it worked fine. % sudo iwconfig wlo1 wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on % sudo nmcli device show wlo1 GENERAL.DEVICE: wlo1 GENERAL.TYPE: wifi GENERAL.HWADDR: 38:87:D5:13:C1:30 GENERAL.MTU:1500 GENERAL.STATE: 20 (unavailable) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.GATEWAY:-- IP6.GATEWAY:-- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-21-generic 5.19.0-21.21 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jwb1179 F wireplumber /dev/snd/seq:jwb1176 F pipewire CRDA: N/A CasperMD5CheckResult: unknown Date: Wed Oct 19 10:24:26 2022 InstallationDate: Installed on 2021-12-31 (292 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=74e4f833-7902-4b06-9e40-e5b191272e08 ro quiet splash irqaffinity=0-15 isolcpus=16-19 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-21-generic N/A linux-backports-modules-5.19.0-21-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to kinetic on 2022-06-07 (133 days ago) dmi.bios.date: 08/25/2022 dmi.bios.release: 20.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2003 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z690-P WIFI D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2003:bd08/25/2022:br20.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ690-PWIFID4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993571 Title: After 5.19.0-15, intel wifi 6 no longer available Status in linux package in Ubuntu: New Bug description: Since 5.19.0-16, which is also the kernel that broke booting on 11/12-gen Intel graphics, my Intel wifi is no longer working. This continues with the present release candidate kernel package -21. The wifi status reports simply that it is "unavailable" and no means to make it "available" is evident to me. On all prior kernels and Jammy it worked fine. % sudo iwconfig wlo1 wlo1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=-2147483648 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on % sudo nmcli device show wlo1 GENERAL.DEVICE: wlo1 GENERAL.TYPE: wifi GENERAL.HWADDR: 38:87:D5:13:C1:30 GENERAL.MTU:1500 GENERAL.STATE: 20 (unavailable) GENERAL.CONNECTION: -- GENERAL.CON-PATH: -- IP4.GATEWAY:-- IP6.GATEWAY:-- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-21-generic 5.19.0-21.21 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 ApportVersion: 2.23.1-0ubuntu3
[Kernel-packages] [Bug 1993567] [NEW] devices buf
Public bug reported: touch mouse donesnt work and the heat of video card unavailable on sensor extenstion ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ahmad 1899 F pulseaudio /dev/snd/pcmC0D0p: ahmad 1899 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 20:08:00 2022 InstallationDate: Installed on 2022-10-11 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 13d3:3490 IMC Networks Bus 001 Device 003: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 18f8:1486 [Maxxter] X5s ZEUS Macro Pro Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540UBR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=67ffb376-9c2a-4fc6-a9d2-aa844b3f17da ro quiet splash acpi=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 08/13/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540UBR.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540UBR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540UBR.301:bd08/13/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540UBR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540UBR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: VivoBook dmi.product.name: VivoBook 15_ASUS Laptop X540UBR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993567 Title: devices buf Status in linux package in Ubuntu: New Bug description: touch mouse donesnt work and the heat of video card unavailable on sensor extenstion ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ahmad 1899 F pulseaudio /dev/snd/pcmC0D0p: ahmad 1899 F...m pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 20:08:00 2022 InstallationDate: Installed on 2022-10-11 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 13d3:3490 IMC Networks Bus 001 Device 003: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam Bus 001 Device 002: ID 18f8:1486 [Maxxter] X5s ZEUS Macro Pro Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540UBR ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=67ffb376-9c2a-4fc6-a9d2-aa844b3f17da ro quiet splash acpi=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: 08/13/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X540UBR.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X540UBR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file
The same problem exists in kinetic and this package version: Package: thermald Version: 2.5.1-1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1993566 Title: dbus-daemon: Unknown group "power" in message bus configuration file Status in thermald package in Ubuntu: New Bug description: Hi, I see the following error message in the logs: # journalctl | grep 'Unknown group "power"' Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file The problem comes from this file: # grep -r power /etc/dbus-1/ /etc/dbus-1/system.d/org.freedesktop.thermald.conf:
[Kernel-packages] [Bug 1993566] [NEW] dbus-daemon: Unknown group "power" in message bus configuration file
Public bug reported: Hi, I see the following error message in the logs: # journalctl | grep 'Unknown group "power"' Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file The problem comes from this file: # grep -r power /etc/dbus-1/ /etc/dbus-1/system.d/org.freedesktop.thermald.conf:
[Kernel-packages] [Bug 1993563] 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 1993563 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/1993563 Title: support for same series backports versioning numbers Status in linux package in Ubuntu: Incomplete Bug description: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993563] [NEW] support for same series backports versioning numbers
Public bug reported: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1993563 Title: support for same series backports versioning numbers Status in linux package in Ubuntu: Incomplete Bug description: packaging support for sameport versioning numbers Allow generating kernel packages, that use backports mechanism within the same series. For example linux-lowlatancy linux-riscv. Those kernels already have customized packaging to achieve the above, this is introducing standard support for this in the main kernels for jammy and kinetic series. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
** Summary changed: - Fix RPL: the Screen is shaking by onboard HDMI port in mirror mode + RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1993561 Title: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993561] [NEW] RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
Public bug reported: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: koba (kobako) Status: Incomplete ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: Incomplete ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Assignee: koba (kobako) Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Assignee: koba (kobako) Status: Incomplete ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1982590 somerville ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Description changed: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP on Display >= 12. + + Due to schedule, SRU for OEM kernels first. + After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => koba (kobako) ** Changed in: linux (Ubuntu Jammy) Status: New => Incomplete ** Changed in: linux (Ubuntu Kinetic) Status: New => Incomplete ** Tags added: oem-priority originate-from-1982590 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993561 Title: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: New Status in linux-oem-6.0 package in Ubuntu: New Status in linux source package in Jammy: Incomplete Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: New Status in linux-oem-6.0 source package in Kinetic: New Bug description: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port
[Kernel-packages] [Bug 1993558] [NEW] filter out "not supported" errors about dkms build failures
Public bug reported: I was looking at some nvidia crash reports in the Ubuntu Error Tracker (https://errors.ubuntu.com/?package=nvidia-graphics- drivers-515=month and more specifically https://errors.ubuntu.com/problem/2bd74bd6c63bbf70e53d9b7983c37368a1a5b630) and discovered a pattern of some with log files like: package:nvidia-dkms-515:515.65.01-0ubuntu0.22.04.1 Setting up nvidia-dkms-515 (515.65.01-0ubuntu0.22.04.1) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-515.65.01 DKMS files... Building for 6.0.0-06-generic Building for architecture x86_64 Building initial module for 6.0.0-06-generic ERROR (dkms apport): kernel package linux-headers-6.0.0-06-generic is not supported Error! Bad return status for module build on kernel: 6.0.0-06-generic (x86_64) Consult /var/lib/dkms/nvidia/515.65.01/build/make.log for more information. dpkg: error processing package nvidia-dkms-515 (--configure): installed nvidia-dkms-515 package post-installation script subprocess returned error exit status 10 I'm not certain its worth reporting errors when there are disconnects between the kernel version and the nvidia driver. ** Affects: errors Importance: Undecided Status: New ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ll-incoming ** Package changed: apport (Ubuntu) => dkms (Ubuntu) ** Summary changed: - filter out apport-package reports about dkms build failures + filter out "not supported" errors about dkms build failures ** Also affects: errors Importance: Undecided Status: New ** Tags added: rls-ll-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1993558 Title: filter out "not supported" errors about dkms build failures Status in Errors: New Status in dkms package in Ubuntu: New Bug description: I was looking at some nvidia crash reports in the Ubuntu Error Tracker (https://errors.ubuntu.com/?package=nvidia-graphics- drivers-515=month and more specifically https://errors.ubuntu.com/problem/2bd74bd6c63bbf70e53d9b7983c37368a1a5b630) and discovered a pattern of some with log files like: package:nvidia-dkms-515:515.65.01-0ubuntu0.22.04.1 Setting up nvidia-dkms-515 (515.65.01-0ubuntu0.22.04.1) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-515.65.01 DKMS files... Building for 6.0.0-06-generic Building for architecture x86_64 Building initial module for 6.0.0-06-generic ERROR (dkms apport): kernel package linux-headers-6.0.0-06-generic is not supported Error! Bad return status for module build on kernel: 6.0.0-06-generic (x86_64) Consult /var/lib/dkms/nvidia/515.65.01/build/make.log for more information. dpkg: error processing package nvidia-dkms-515 (--configure): installed nvidia-dkms-515 package post-installation script subprocess returned error exit status 10 I'm not certain its worth reporting errors when there are disconnects between the kernel version and the nvidia driver. To manage notifications about this bug go to: https://bugs.launchpad.net/errors/+bug/1993558/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993558] [NEW] filter out apport-package reports about dkms build failures
You have been subscribed to a public bug: I was looking at some nvidia crash reports in the Ubuntu Error Tracker (https://errors.ubuntu.com/?package=nvidia-graphics- drivers-515=month and more specifically https://errors.ubuntu.com/problem/2bd74bd6c63bbf70e53d9b7983c37368a1a5b630) and discovered a pattern of some with log files like: package:nvidia-dkms-515:515.65.01-0ubuntu0.22.04.1 Setting up nvidia-dkms-515 (515.65.01-0ubuntu0.22.04.1) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-515.65.01 DKMS files... Building for 6.0.0-06-generic Building for architecture x86_64 Building initial module for 6.0.0-06-generic ERROR (dkms apport): kernel package linux-headers-6.0.0-06-generic is not supported Error! Bad return status for module build on kernel: 6.0.0-06-generic (x86_64) Consult /var/lib/dkms/nvidia/515.65.01/build/make.log for more information. dpkg: error processing package nvidia-dkms-515 (--configure): installed nvidia-dkms-515 package post-installation script subprocess returned error exit status 10 I'm not certain its worth reporting errors when there are disconnects between the kernel version and the nvidia driver. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New -- filter out apport-package reports about dkms build failures https://bugs.launchpad.net/bugs/1993558 You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958770] Re: Aquantia GbE LAN driver causes UBSAN error during kernel boot
Still present in 5.15.0-52-lowlatency 10/19/22 7:59 AMkernel 10/19/22 7:59 AMkernel UBSAN: array-index-out-of-bounds in /build/linux-lowlatency-rWNFY0/linux-lowlatency-5.15.0/drivers/net/ethernet/aquantia/atlantic/aq_nic.c:1262:48 10/19/22 7:59 AMkernel index 8 is out of range for type 'aq_vec_s *[8]' 10/19/22 7:59 AMkernel CPU: 7 PID: 2084 Comm: daemon-init Not tainted 5.15.0-52-lowlatency #58-Ubuntu 10/19/22 7:59 AMkernel Hardware name: To Be Filled By O.E.M. X570 Creator/X570 Creator, BIOS P3.72 05/17/2022 10/19/22 7:59 AMkernel Call Trace: 10/19/22 7:59 AMkernel 10/19/22 7:59 AMkernel show_stack+0x52/0x5c 10/19/22 7:59 AMkernel dump_stack_lvl+0x4a/0x63 10/19/22 7:59 AMkernel dump_stack+0x10/0x16 10/19/22 7:59 AMkernel ubsan_epilogue+0x9/0x49 10/19/22 7:59 AMkernel __ubsan_handle_out_of_bounds.cold+0x44/0x49 10/19/22 7:59 AMkernel ? dev_fetch_sw_netstats+0x48/0x90 10/19/22 7:59 AMkernel ? aq_vec_stop+0x72/0x80 [atlantic] 10/19/22 7:59 AMkernel aq_nic_stop+0x1b6/0x1c0 [atlantic] 10/19/22 7:59 AMkernel aq_ndev_set_features+0x143/0x1a0 [atlantic] 10/19/22 7:59 AMkernel __netdev_update_features+0x184/0x820 10/19/22 7:59 AMkernel dev_disable_lro+0x34/0x150 10/19/22 7:59 AMkernel devinet_sysctl_forward+0x1fb/0x230 10/19/22 7:59 AMkernel proc_sys_call_handler+0x161/0x2d0 10/19/22 7:59 AMkernel proc_sys_write+0x13/0x20 10/19/22 7:59 AMkernel new_sync_write+0x114/0x1a0 10/19/22 7:59 AMkernel ? icl_set_topdown_event_period+0x70/0xe0 10/19/22 7:59 AMkernel vfs_write+0x1fb/0x290 10/19/22 7:59 AMkernel ksys_write+0x67/0xf0 10/19/22 7:59 AMkernel __x64_sys_write+0x19/0x20 10/19/22 7:59 AMkernel do_syscall_64+0x5c/0xc0 10/19/22 7:59 AMkernel ? syscall_exit_to_user_mode+0x27/0x50 10/19/22 7:59 AMkernel ? do_syscall_64+0x69/0xc0 10/19/22 7:59 AMkernel ? irqentry_exit_to_user_mode+0x9/0x20 10/19/22 7:59 AMkernel ? irqentry_exit+0x3b/0x50 10/19/22 7:59 AMkernel ? exc_page_fault+0x89/0x190 10/19/22 7:59 AMkernel entry_SYSCALL_64_after_hwframe+0x61/0xcb 10/19/22 7:59 AMkernel RIP: 0033:0x7f61c36a1a6f 10/19/22 7:59 AMkernel Code: 89 54 24 18 48 89 74 24 10 89 7c 24 08 e8 19 c0 f7 ff 48 8b 54 24 18 48 8b 74 24 10 41 89 c0 8b 7c 24 08 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 31 44 89 c7 48 89 44 24 08 e8 5c c0 f7 ff 48 10/19/22 7:59 AMkernel RSP: 002b:7f61837fd810 EFLAGS: 0293 ORIG_RAX: 0001 10/19/22 7:59 AMkernel RAX: ffda RBX: 0002 RCX: 7f61c36a1a6f 10/19/22 7:59 AMkernel RDX: 0002 RSI: 7f61c40265e5 RDI: 0013 10/19/22 7:59 AMkernel RBP: 7f61c40265e5 R08: R09: 0001 10/19/22 7:59 AMkernel R10: R11: 0293 R12: 0013 10/19/22 7:59 AMkernel R13: 0013 R14: R15: 7f6178031e10 10/19/22 7:59 AMkernel 10/19/22 7:59 AMkernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958770 Title: Aquantia GbE LAN driver causes UBSAN error during kernel boot Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: The undefined behaviour sanitiser picks up an array-index-out-of- bounds in the aquantia atlantic driver. The NIC is (I think) built into my gigabyte motherboard (https://www.gigabyte.com/uk/Motherboard/X399-AORUS-XTREME- rev-10/sp#sp). This wasn't an issue before I upgrading from 20.04 to 22.04 (or at least dmesg didn't previously complain). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 23 13:02:10 2022 InstallationDate: Installed on
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
https://code.launchpad.net/~xnox/ubiquity/+git/ubiquity/+merge/431831 should solve first boot post-install. However, I don't think that will solve booting snapshot, or whenever on- disk cached is missing/corrupted/out of date, and one tries to boot. Seems quite scary. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988346] Re: cm32181 module error blocking suspend
Thanks for your testing so far! Please give this kernel a try: https://people.canonical.com/~khfeng/lp1988346-5/ I made CM32181's suspend/resume routine dummy functions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Failed with result 'exit-code'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Failed to start System Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Dependency failed for Suspend. Aug 31 19:59:44 nmurphy-laptop systemd[1]: suspend.target: Job suspend.target/start failed with result 'dependency'. Aug 31 19:59:44 nmurphy-laptop systemd[1]: Stopped target Sleep. Aug 31 19:59:44 nmurphy-laptop
[Kernel-packages] [Bug 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** Merge proposal linked: https://code.launchpad.net/~xnox/ubiquity/+git/ubiquity/+merge/431831 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in snapd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: New Status in zsys package in Ubuntu: Invalid Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1993318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993539] [NEW] Nvidia GeForce GTX 560 M not recognized as an OpenCL platform with 5.15.0-50 kernel
Public bug reported: Hi, Before to update to Linux Mint 21, based on Ubuntu 22.04 LTS, I have tried 5.15.0-50 kernel with HWE. This was intended as a test of my hardware compatibility with the hardware stack of Ubuntu 22.04, before a possible update. At a first glance, all seemed OK; nut I noticed that LibreOffice was unable to use OpenCL. A simple "clinfo" command confirmed this: $ clinfo Number of platforms 0 I went back from 5.15.0-50 kernel to 5.4.0-128 one. Now, "clinfo" output is: $ clinfo Number of platforms 1 Platform Name NVIDIA CUDA Platform Vendor NVIDIA Corporation Platform VersionOpenCL 1.2 CUDA 9.1.84 Platform ProfileFULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_copy_opts cl_nv_create_buffer Platform Extensions function suffix NV Platform Name NVIDIA CUDA Number of devices 1 Device Name GeForce GTX 560M Device Vendor NVIDIA Corporation Device Vendor ID0x10de Device Version OpenCL 1.1 CUDA Driver Version 390.154 Device OpenCL C Version OpenCL C 1.1 Device Type GPU Device Topology (NV)PCI-E, 01:00.0 Device Profile FULL_PROFILE Device AvailableYes Compiler Available Yes Max compute units 4 Max clock frequency 1550MHz Compute Capability (NV) 2.1 Max work item dimensions3 Max work item sizes 1024x1024x64 Max work group size 1024 Preferred work group size multiple 32 Warp size (NV) 32 Preferred / native vector sizes char 1 / 1 short1 / 1 int 1 / 1 long 1 / 1 half 0 / 0(n/a) float1 / 1 double 1 / 1 (cl_khr_fp64) Half-precision Floating-point support (n/a) Single-precision Floating-point support (core) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Correctly-rounded divide and sqrt operations No Double-precision Floating-point support (cl_khr_fp64) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Address bits64, Little-Endian Global memory size 3150839808 (2.934GiB) Error Correction supportNo Max memory allocation 787709952 (751.2MiB) Unified memory for Host and Device No Integrated memory (NV) No Minimum alignment for any data type 128 bytes Alignment of base address 4096 bits (512 bytes) Global Memory cache typeRead/Write Global Memory cache size65536 (64KiB) Global Memory cache line size 128 bytes Image support Yes Max number of samplers per kernel 16 Max 2D image size
[Kernel-packages] [Bug 1993352] Re: unable to boot kernel 5.15.0.50
Changing status to 'Confirmed' as requested in comment #2. ** 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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Confirmed Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993532] 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/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Confirmed Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993532] [NEW] Unable to see second monitor
Public bug reported: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993532 Title: Unable to see second monitor Status in linux package in Ubuntu: Confirmed Bug description: I have a second monitor plugged into this laptop. Under 5.15.0-52-generic this monitor isn't seen by Ubuntu, whether via a thunderbolt dongle or directly into the HDMI port. When I boot it back into 5.15.0-50-generic it works just fine. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-52-generic 5.15.0-52.58 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robin 4304 F pulseaudio /dev/snd/controlC0: robin 4304 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 14:53:25 2022 InstallationDate: Installed on 2022-03-17 (216 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) MachineType: Dell Inc. Latitude 7320 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2022 dmi.bios.release: 1.17 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.17.2 dmi.board.name: 07MHG4 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.17.2:bd06/15/2022:br1.17:svnDellInc.:pnLatitude7320:pvr:rvnDellInc.:rn07MHG4:rvrA02:cvnDellInc.:ct10:cvr:sku0A34: dmi.product.family: Latitude dmi.product.name: Latitude 7320 dmi.product.sku: 0A34 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993532/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Re: unable to boot kernel 5.15.0.50
** Tags added: kernel-bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
@htaccess that looks like a bug in ubuntu-drivers. I wonder what the actual value of package_name was though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic
> In general, does strace get a release for each kernel release? Should it be updated in parallel? I tried to find an answer to this question and I would say yes. As is stated in [1], strace follows the same release cycle as the kernel. In addition, every strace release at least comes with a non-backward compatible change, which is the update of the ioctl commands list (for an example see [2]). So instead of cherry-picking the 2 commits mwhudson mentions, I'd rather update to 5.19 since the default kernel for kinetic is 5.19 (both commits belong to this version). [1] https://lists.strace.io/pipermail/strace-devel/2022-August/011094.html [2] https://github.com/strace/strace/commit/22f61979141fa5c9732d01ea69c23f46a3e2868a -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: Fix Released Status in strace package in Ubuntu: Triaged Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
@Alberto Milone (albertomilone): I went with `sudo apt install nvidia-driver-515` instead due to the `ubuntu-drivers` error above, this installed a bunch of stuff play this lot: ``` Loading new nvidia-515.76 DKMS files... Building for 5.15.0-52-generic Building for architecture x86_64 Building initial module for 5.15.0-52-generic ``` rebooted and everything worked. Looks like I'm back in action (although I assume the two older kernels wont work, hopefully I don't need them). Thanks for the help! BTW launchpad formatting is terrible! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
@Alberto Milone (albertomilone):
sudo apt-get --purge remove '*nvidia*'
removed a lot of packages except these:
```
$ dpkg -l | awk '/nvidia/{ print $2 }'
libnvidia-compute-515:i386
libnvidia-decode-515:i386
libnvidia-encode-515:i386
libnvidia-fbc1-515:i386
```
```
$ sudo ubuntu-drivers install
Traceback (most recent call last):
File "/usr/bin/ubuntu-drivers", line 513, in
greet()
File "/usr/lib/python3/dist-packages/click/core.py", line 1128, in __call__
return self.main(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/lib/python3/dist-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/lib/python3/dist-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/lib/python3/dist-packages/click/decorators.py", line 84, in
new_func
return ctx.invoke(f, obj, *args, **kwargs)
File "/usr/lib/python3/dist-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/bin/ubuntu-drivers", line 413, in install
command_install(config)
File "/usr/bin/ubuntu-drivers", line 187, in command_install
UbuntuDrivers.detect.nvidia_desktop_pre_installation_hook(to_install)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 839, in
nvidia_desktop_pre_installation_hook
with_nvidia_kms = version >= 470
UnboundLocalError: local variable 'version' referenced before assignment
```
looks like this try is failing with a ValueError so the version var is
not assigned:
```
$ grep 'Enable KMS if nvidia >= 470' -A 8
/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py
# Enable KMS if nvidia >= 470
for package_name in to_install:
if package_name.startswith('nvidia-driver-'):
try:
version = int(package_name.split('-')[-1])
except ValueError:
pass
finally:
with_nvidia_kms = version >= 470
```
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1992679
Title:
Can not login after new kernel installed (nvidia driver crashed)
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-515 package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
Confirmed
Status in nvidia-graphics-drivers-510 source package in Jammy:
Confirmed
Status in nvidia-graphics-drivers-515 source package in Jammy:
Confirmed
Bug description:
Hello. Today i have installed new kernel from. I installed 5.15.0-50
and after that i can not login to system... I see boot text, but after
booting i see black log screen and can not login. I able boot and
login with old kernel (5.15.0-48).
I updated these packages:
Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic),
linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic),
linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic),
linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic),
linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic),
linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic),
linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic),
linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic),
linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic)
Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50),
google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1),
linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64
(5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48,
5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50)
Updated logs see in attachement.
Logs from journalctl see in attachements.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-50-generic 5.15.0-50.56
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: vodka 1819 F pulseaudio
/dev/snd/controlC1: vodka 1819 F pulseaudio
CasperMD5CheckResult: unknown
Date: Wed Oct 12 19:56:43 2022
InstallationDate: Installed on 2018-05-02 (1623 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID
[Kernel-packages] [Bug 1981364] Re: ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop
that commit is upstream in 5.15.46 and up, jammy kernel already has changes up to and including 5.15.60, so there's nothing to do ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1981364 Title: ALSA: hda/realtek: Enable 4-speaker output for Dell XPS 15 9520 laptop Status in linux package in Ubuntu: Fix Released Bug description: This is cherry pick from a bug fix which was added to kernel 5.17.5. Bug: https://bugzilla.kernel.org/show_bug.cgi?id=216035 Commit: https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=15dad62f4bdb5dc0f0efde8181d680db9963544c With Ubuntu 22.05 coming with 5.15.x it would be really nice to have this in as well. Thanks for all hard work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981364/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992118] Re: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel
Hello Jian, or anyone else affected, Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- firmware/1.187.34 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1992118 Title: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-intel-iotg-5.15 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Summary] AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 Intel IoTG kernel. [Steps to reproduce] $ sudo apt update $ sudo apt upgrade $ reboot [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% [Other Info] [4.485407] iwlwifi :02:00.0: enabling device ( -> 0002) [4.512442] iwlwifi :02:00.0: api flags index 2 larger than supported by driver [4.512500] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.63.2.2 [4.514725] iwlwifi :02:00.0: loaded firmware version 66.f1c864e0.0 ty-a0-gf-a0-66.ucode op_mode iwlmvm [4.636133] iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [4.811565] iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000 [4.812366] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. [4.812478] iwlwifi :02:00.0: Start IWL Error Log Dump: [4.812484] iwlwifi :02:00.0: Transport status: 0x004A, valid: 6 [4.812489] iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [4.812499] iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0 [4.812503] iwlwifi :02:00.0: 0x | trm_hw_status1 [4.812507] iwlwifi :02:00.0: 0x004DA722 | branchlink2 [4.812510] iwlwifi :02:00.0: 0x004D0CCE | interruptlink1 [4.812514] iwlwifi :02:00.0: 0x004D0CCE | interruptlink2 [4.812517] iwlwifi :02:00.0: 0x004D94DA | data1 [4.812520] iwlwifi :02:00.0: 0x0010 | data2 [4.812523] iwlwifi :02:00.0: 0x | data3 [4.812527] iwlwifi :02:00.0: 0x | beacon time [4.812530] iwlwifi :02:00.0: 0x0001324E | tsf low [4.812533] iwlwifi :02:00.0: 0x | tsf hi [4.812536] iwlwifi :02:00.0: 0x | time gp1 [4.812540] iwlwifi :02:00.0: 0x000244E1 | time gp2 [4.812543] iwlwifi :02:00.0: 0x0001 | uCode revision type [4.812546] iwlwifi :02:00.0: 0x0042 | uCode version major [4.812550] iwlwifi :02:00.0: 0xF1C864E0 | uCode version minor [4.812553] iwlwifi :02:00.0: 0x0420 | hw version [4.812557] iwlwifi :02:00.0: 0x18C89002 | board version [4.812560] iwlwifi :02:00.0: 0x8008FF05 | hcmd [4.812563] iwlwifi :02:00.0: 0x0002 | isr0 [4.812566] iwlwifi :02:00.0: 0x6000 | isr1 [4.812569] iwlwifi :02:00.0: 0x48F2 | isr2 [4.812572] iwlwifi :02:00.0: 0x00C0001C | isr3 [4.812575] iwlwifi :02:00.0: 0x | isr4 [4.812578] iwlwifi :02:00.0: 0x | last cmd Id [4.812581] iwlwifi :02:00.0: 0x004D94DA | wait_event [4.812584] iwlwifi :02:00.0: 0x | l2p_control [4.812588] iwlwifi :02:00.0: 0x | l2p_duration [4.812591] iwlwifi :02:00.0: 0x | l2p_mhvalid [4.812594] iwlwifi :02:00.0: 0x | l2p_addr_match [4.812597]
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Same freeze for me with 515 nv driver. I'm actually sticking to 5.15.0.48 as a workaround -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993516] [NEW] bluetooth input freezes for a few second after brief inactivity
Public bug reported: I have a Logitech bluetooth mouse (M650) and keyboard (K380, details in the attached log). I almost never power down the laptop: I suspend and resume it. Sometimes when I resume from suspend everything works flawlessly. Other times, there's a 2-3s "freeze" after just several seconds of input inactivity, during which moving the mouse or pressing keyboard keys gives no response. After 2-3s, all the keys pressed during the freeze suddenly appear on screen. Restarting the bluetooth service, going to airplane mode and back or turning the mouse and keyboard on and off does not help at all. The delay makes using these input devices barely usable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 11:25:13 2022 InstallationDate: Installed on 2017-02-18 (2068 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=2b559de5-44d4-4f98-a211-a39edbb31bc8 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2022-08-02 (77 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 03MCRF dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd10/02/2019:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn03MCRF:rvrA09:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E5570 dmi.product.sku: 06DF dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: B8:8A:60:C5:C9:BF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:34304 acl:977 sco:0 events:2580 errors:0 TX bytes:603917 acl:73 sco:0 commands:2473 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2022-10-19T11:24:40.907104 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1993516 Title: bluetooth input freezes for a few second after brief inactivity Status in bluez package in Ubuntu: New Bug description: I have a Logitech bluetooth mouse (M650) and keyboard (K380, details in the attached log). I almost never power down the laptop: I suspend and resume it. Sometimes when I resume from suspend everything works flawlessly. Other times, there's a 2-3s "freeze" after just several seconds of input inactivity, during which moving the mouse or pressing keyboard keys gives no response. After 2-3s, all the keys pressed during the freeze suddenly appear on screen. Restarting the bluetooth service, going to airplane mode and back or turning the mouse and keyboard on and off does not help at all. The delay makes using these input devices barely usable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-126.142-generic 5.4.203 Uname: Linux 5.4.0-126-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 11:25:13 2022 InstallationDate: Installed on 2017-02-18 (2068 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude E5570 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-126-generic root=UUID=2b559de5-44d4-4f98-a211-a39edbb31bc8 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2022-08-02 (77 days ago) dmi.bios.date: 10/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.21.6 dmi.board.name: 03MCRF dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.21.6:bd10/02/2019:svnDellInc.:pnLatitudeE5570:pvr:rvnDellInc.:rn03MCRF:rvrA09:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E5570 dmi.product.sku: 06DF dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: B8:8A:60:C5:C9:BF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:34304 acl:977 sco:0 events:2580 errors:0 TX bytes:603917 acl:73 sco:0 commands:2473 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2022-10-19T11:24:40.907104 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Can you follow these steps, please? Remove any nvidia package left on your system: sudo apt-get --purge remove '*nvidia*' Finally, install the driver using the following command: sudo ubuntu-drivers install Finally, reboot, and see if you can reproduce the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
Apparently the options workaround doesn't completely eliminate the bug. It still occurs around five percent of the time when booting kinetic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581969] iwlwifi :05:00.0: value [iter 3]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581984] iwlwifi :05:00.0:
[Kernel-packages] [Bug 1975840] Re: WiFi not roaming to a much stronger/faster AP
** Also affects: wpasupplicant (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1975840 Title: WiFi not roaming to a much stronger/faster AP Status in linux package in Ubuntu: Confirmed Status in wpasupplicant package in Ubuntu: New Bug description: I have spotty WiFi reception around the house, and I've noticed that once I roam to a 2.4GHz because I've moved out of range, coming back I'm stuck at it with very low signal despite there being much more powerful and faster BSSIDs around. `nmcli d wifi` reports: $ nmcli d wifi IN-USE BSSID SSID MODE CHAN RATESIGNAL BARS SECURITY 74:83:C2:19:7E:BA wifi Infra 1 130 Mbit/s 82 ▂▄▆█ WPA2 * 74:83:C2:19:7E:BB wifi Infra 44540 Mbit/s 55 ▂▄__ WPA2 4C:E6:76:F9:5E:AF wifi Infra 52130 Mbit/s 39 ▂▄__ WPA2 If I didn't reconnect, I'd be stuck on the 4C: BSSID still. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-33-generic 5.15.0-33.34 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michal 6270 F pulseaudio /dev/snd/controlC1: michal 6270 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 17:12:34 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2022-04-29 (27 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Dell Inc. XPS 12-9Q33 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/zsh ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_6u8k7k@/vmlinuz-5.15.0-33-generic root=ZFS=rpool/ROOT/ubuntu_6u8k7k ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-33-generic N/A linux-backports-modules-5.15.0-33-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2015 dmi.bios.release: 0.8 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.ec.firmware.release: 0.8 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:br0.8:efr0.8:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:skuXPS12-9Q33: dmi.product.name: XPS 12-9Q33 dmi.product.sku: XPS 12-9Q33 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1975840/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993492] 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/1993492 Title: package linux-headers-5.15.0-52 5.15.0-52.58 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux- headers-5.15.0-52.list-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 5.15.0-52.58-generic 5.15.60 00:00.0 Host bridge [0600]: Intel Corporation Coffee Lake HOST and DRAM Controller [8086:3e34] (rev 0b) Subsystem: Lenovo Coffee Lake HOST and DRAM Controller [17aa:3808] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:39f4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0b) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [17aa:3829] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [17aa:385b] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] (rev 30) Subsystem: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO
[Kernel-packages] [Bug 1993352] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625134/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625135/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625136/+files/acpidump.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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625132/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625133/+files/RfKill.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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625130/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625127/+files/PaInfo.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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625123/+files/Lspci-vt.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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625131/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625122/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625125/+files/Lsusb-t.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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625128/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625126/+files/Lsusb-v.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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625124/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625129/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625120/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625121/+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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 Tags: jammy Uname: Linux 5.15.0-50-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: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Re: unable to boot kernel 5.15.0.50
apport information ** Tags added: apport-collected ** Description changed: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: gwendal1853 F pulseaudio + /dev/snd/controlC2: gwendal1853 F pulseaudio + /dev/snd/controlC1: gwendal1853 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-10-12 (6 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + MachineType: Alienware Alienware 15 R3 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=/dev/mapper/vgubuntu-root ro + ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-50-generic N/A + linux-backports-modules-5.15.0-50-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.5 + Tags: jammy + Uname: Linux 5.15.0-50-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: 07/21/2020 + dmi.bios.release: 1.10 + dmi.bios.vendor: Alienware + dmi.bios.version: 1.10.0 + dmi.board.name: Alienware 15 R3 + dmi.board.vendor: Alienware + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Alienware + dmi.chassis.version: Not Specified + dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: + dmi.product.family: Alienware + dmi.product.name: Alienware 15 R3 + dmi.product.sku: 0774 + dmi.product.version: 1.10.0 + dmi.sys.vendor: Alienware ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1993352/+attachment/5625119/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gwendal1853 F pulseaudio /dev/snd/controlC2: gwendal1853 F pulseaudio /dev/snd/controlC1: gwendal1853 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-10-12 (6 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8
[Kernel-packages] [Bug 1993492] [NEW] package linux-headers-5.15.0-52 5.15.0-52.58 failed to install/upgrade: unable to create new file '/var/lib/dpkg/info/linux-headers-5.15.0-52.list-new': Operation
Public bug reported: Ubuntu 5.15.0-52.58-generic 5.15.60 00:00.0 Host bridge [0600]: Intel Corporation Coffee Lake HOST and DRAM Controller [8086:3e34] (rev 0b) Subsystem: Lenovo Coffee Lake HOST and DRAM Controller [17aa:3808] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Lenovo WhiskeyLake-U GT2 [UHD Graphics 620] [17aa:39f4] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis- NROPrPrP- LTR- 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- OBFF Disabled, AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 Kernel modules: i915 00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0b) Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [17aa:3829] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device_pci_legacy 00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911] Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [17aa:385b] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] (rev 30) Subsystem: Intel Corporation Cannon Point-LP Shared SRAM [8086:9def] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi 00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #0 [8086:9de8] (rev 30) Subsystem: Lenovo Cannon Point-LP Serial IO I2C Controller [17aa:380b] 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: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP Serial IO I2C Controller #1 [8086:9de9] (rev 30)
[Kernel-packages] [Bug 1990876] Re: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module
Same problem with linux.image-5.10.0.52. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990876 Title: kworker high CPU usage: issue with xhci_hub_control from xhci_pci kernel module Status in linux package in Ubuntu: Incomplete Bug description: Using Ubuntu 22.04, as of yesterday night upon rebooting the framework laptop (which had not been rebooted for several weeks), the fans come on strong and I see, with top, a kworker process at nearly 100% CPU utilization, which makes the laptop unusable. I have an early Framework laptop with an 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz. I removed all USB-c expansion cards except for one with an USB-c pass through, to no avail. With perf I have been able to determine that the xhci_hub_control and perhaps xhci_bus_suspend are at fault. As a matter of fact, the laptop cannot suspend any more, when it was working flawlessly until the reboot. $ sudo apt install linux-tools-common linux-tools-$(uname -r) $ sudo -i # echo -1 > /proc/sys/kernel/perf_event_paranoid # perf record control-c # perf report Samples: 125K of event 'cycles', Event count (approx.): 142991820424 Overhead Command Shared Object Symbol 54.11% kworker/5:2+usb [kernel.kallsyms] [k] xhci_hub_control ◆ 7.94% kworker/5:2+usb [kernel.kallsyms] [k] xhci_bus_suspend ▒ 0.98% kworker/5:2+usb [kernel.kallsyms] [k] kfree ▒ 0.86% kworker/5:2+usb [kernel.kallsyms] [k] _raw_spin_lock_irqsave ... What can be done to address this issue with a kworker? I suspect perhaps the new kernel is at fault. I tried rebooting to the prior kernel 5.15.0-47-generic and 5.15.0-46-generic, but with the same result. What has changed? What can be done about this kworker and the xchi_hub_control? A temporary solution: $ sudo modprobe -r xhci_pci … which results in the kworker process disappearing from `top` (reduced CPU usage to near zero), the fans wind down, and unfortunately the ethernet expansion bay doesn’t work anymore but at least wifi does. Keyboard and touchpad also work. And suspend with deep also work well, just tested it. I assume other expansion bays will stop working too, but the laptop is at least charging: the USB-c pass-through works. See also: https://community.frame.work/t/kworker-stuck-at-near-100-cpu-usage-with-ubuntu-22-04/23053/2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: albert 4870 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 18:14:26 2022 InstallationDate: Installed on 2022-03-11 (199 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Framework Laptop ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_ezm1f9@/vmlinuz-5.15.0-48-generic root=ZFS=rpool/ROOT/ubuntu_ezm1f9 ro quiet splash nvme.noacpi=1 mem_sleep_default=deep vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (150 days ago) dmi.bios.date: 07/19/2022 dmi.bios.release: 3.16 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 03.10 dmi.board.asset.tag: * dmi.board.name: FRANBMCP0B dmi.board.vendor: Framework dmi.board.version: AB dmi.chassis.asset.tag: FRANBMCPAB1484011X dmi.chassis.type: 10 dmi.chassis.vendor: Framework dmi.chassis.version: AB dmi.modalias: dmi:bvnINSYDECorp.:bvr03.10:bd07/19/2022:br3.16:svnFramework:pnLaptop:pvrAB:rvnFramework:rnFRANBMCP0B:rvrAB:cvnFramework:ct10:cvrAB:skuFRANBMCP0B: dmi.product.family: FRANBMCP dmi.product.name: Laptop dmi.product.sku: FRANBMCP0B dmi.product.version: AB dmi.sys.vendor: Framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990876/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1993352] 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 1993352 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/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: Incomplete Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993223] Re: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04
** Tags added: kern-4658 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1993223 Title: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Kinetic: Fix Released Bug description: Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs firmware to be loaded by amdgpu. This firmware has been upstreamed by these commits, which are already part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1) db6db36a amdgpu: add firmware for VCN 3.1.2 IP block 3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block 639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block 76589464 amdgpu: add firmware for GC 10.3.6 IP block 427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block Matching kernel code for this processor is already upstreamed in 6.0 kernel, and so this should work with OEM-6.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] Re: unable to boot kernel 5.15.0.50
** Package changed: ubuntu => linux (Ubuntu) ** Tags removed: 22.40 ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993352 Title: unable to boot kernel 5.15.0.50 Status in linux package in Ubuntu: New Bug description: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993352/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993071] Re: dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430
** Tags added: kern-4657 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1993071 Title: dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430 Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: lots of iwlwifi errors in dmesg. loaded firmware version 73.35c0a2c6.0 so-a0-jf-b0-73.ucode op_mode iwlmvm firmware didn't ACK the reset - continue anyway ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-iwlwifi-generic 5.15.0.50.50 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kimathi1734 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 16 19:29:23 2022 InstallationDate: Installed on 2022-07-26 (82 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) IwConfig: lono wireless extensions. enp2s0no wireless extensions. wlo1 no wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1934:5168 Feature Integration Technology Inc. (Fintek) F71610A or F71612A Consumer Infrared Receiver/Transceiver Bus 001 Device 002: ID 045e:0800 Microsoft Corp. Wireless keyboard (All-in-One-Media) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUS System Product Name ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=ab6e73ff-42d6-40bd-b4e1-617afcbabcf8 ro quiet splash loglevel=3 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2022 dmi.bios.release: 16.20 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1620 dmi.board.asset.tag: Default string dmi.board.name: PRIME H610I-PLUS D4 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1620:bd08/12/2022:br16.20:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEH610I-PLUSD4:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993352] [NEW] unable to boot kernel 5.15.0.50
You have been subscribed to a public bug: Hi, After a fresh install of Ubuntu 22.04 I'm unable to boot with kernel 5.15.0.50 Normal boot on 5.15.0.50 : stuck at boot with the following message : INFO: task gpu-manager:749 blocked for more than XXX seconds I deactivated the silent splash screen on Grub to get more details about what's wrong : "a start job is running for Detect the available GPU..." Recovery mode on 5.15.0.50: I can boot but after login only integrated monitor is working Normal boot on 5.15.0.43: No issue Configuration: Alienware 15R3 Nvidia GTX 1080 Mobile + Integrated Intel GPU Nvidia drivers: 515 What I'v done so far : -Deactivated gpu-manager in grub: no effect -Uninstall intel-microcode or downgraded intel-microcode : no effect -Tried various nvidia drivers: no effect -Tried other external monitors: no effect ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 22.40 5.15.0.50 bot-comment intel-microcode nvidia -- unable to boot kernel 5.15.0.50 https://bugs.launchpad.net/bugs/1993352 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993052] Re: iwlwifi Not valid error log pointer 0x00000000 causes WiFi to not work but bluetooth works
** Tags added: kern-4656 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1993052 Title: iwlwifi Not valid error log pointer 0x causes WiFi to not work but bluetooth works Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: For some reason, Ubuntu gets glitched where the Bluetooth works but WiFi does not even show up. If I reboot into Windows, it is a similar issue (wifi does not show up, but device manager shows Code 10. If I disable and enable the adaptor Intel Wireless AC 9560, it sometimes works and most times does not). After a few days, the issue goes away. Relevent info: Laptop: Asus ROG Strig-G 531GT Using newest bios 308 WiFi Adaptor: Intel Wireless AC 9560 As for wifi connection, usually wifi icon does not even show and stays that way throughout the whole uptime. If I reboot a couple of times, this may change. However, the wifi I connect to usually is WiFi 5 on 5G channel running WPA2. If I use my laptop outside my home, it connects to enterprise WiFi Here is the Intel firmware version [5.088777] kernel: iwlwifi :00:14.3: loaded firmware version 46.fae53a8b.0 9000-pu-b0-jf-b0-46.ucode op_mode iwlmvm Here is the relevent Dmesg output [code] [ 10.661344] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x234c [ 10.661361] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 10.909316] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [ 10.909348] iwlwifi :00:14.3: IML/ROM dump: [ 10.909349] iwlwifi :00:14.3: 0x | IML/ROM error/state [ 10.909382] iwlwifi :00:14.3: 0x0003 | IML/ROM data1 [ 10.909397] iwlwifi :00:14.3: Fseq Registers: [ 10.909406] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE [ 10.909414] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [ 10.909422] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION [ 10.909431] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [ 10.909438] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION [ 10.909447] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN [ 10.909456] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID [ 10.909464] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID [ 10.909472] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [ 10.909483] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [ 10.909494] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 10.909535] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 10.909543] iwlwifi :00:14.3: Failed to start INIT ucode: -110 [ 10.909544] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 14.088686] iwlwifi :00:14.3: Failed to run INIT ucode: -110 [ 14.101296] iwlwifi :00:14.3: retry init count 1 [ 14.104445] iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560 160MHz, REV=0x318 [ 14.112168] thermal thermal_zone6: failed to read out thermal zone (-61) [ 15.141330] iwlwifi :00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x234c [ 15.141345] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [ 15.390252] iwlwifi :00:14.3: Not valid error log pointer 0x for Init uCode [ 15.390284] iwlwifi :00:14.3: IML/ROM dump: [ 15.390285] iwlwifi :00:14.3: 0x | IML/ROM error/state [ 15.390316] iwlwifi :00:14.3: 0x0003 | IML/ROM data1 [ 15.390332] iwlwifi :00:14.3: Fseq Registers: [ 15.390340] iwlwifi :00:14.3: 0x6F1F6FFD | FSEQ_ERROR_CODE [ 15.390348] iwlwifi :00:14.3: 0x | FSEQ_TOP_INIT_VERSION [ 15.390357] iwlwifi :00:14.3: 0xC5F8DD60 | FSEQ_CNVIO_INIT_VERSION [ 15.390365] iwlwifi :00:14.3: 0xA384 | FSEQ_OTP_VERSION [ 15.390373] iwlwifi :00:14.3: 0x5B3DBD40 | FSEQ_TOP_CONTENT_VERSION [ 15.390382] iwlwifi :00:14.3: 0x420E0021 | FSEQ_ALIVE_TOKEN [ 15.390390] iwlwifi :00:14.3: 0xDC0D7CE6 | FSEQ_CNVI_ID [ 15.390398] iwlwifi :00:14.3: 0x548306C4 | FSEQ_CNVR_ID [ 15.390407] iwlwifi :00:14.3: 0x01000100 | CNVI_AUX_MISC_CHIP [ 15.390417] iwlwifi :00:14.3: 0x01300202 | CNVR_AUX_MISC_CHIP [ 15.390428] iwlwifi :00:14.3: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [ 15.390469] iwlwifi :00:14.3: 0xA5A5A5A2 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [ 15.390477] iwlwifi :00:14.3: Failed to start INIT ucode: -110 [ 15.390480] iwlwifi :00:14.3: WRT: Collecting data: ini trigger 13 fired (delay=0ms). [/code] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56
[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU
@Chris, it's not easy to use one line of code but not too hard to implement.
Must clean up the existed table if the original policy is passive policy 2.
Then parse pp1 on thermald.
I thought it's better to follow the upstream code architecture.
~~~
#here's code sniplet of 82609c7
+void cthd_engine_adaptive::install_passive_default() {
+ if (passive_installed)
+ return;
+
+ thd_log_info("IETM_D0 processed\n");
+
+ for (unsigned int i = 0; i < zones.size(); ++i) {
+ cthd_zone *_zone = zones[i];
+ _zone->zone_reset(1);
+ _zone->trip_delete_all();
+
+ if (_zone->zone_active_status())
+ _zone->set_zone_inactive();
+ }
+
+ struct psvt *psvt = gddv.find_def_psvt();
+ if (!psvt)
+ return;
+
+ std::vector psvs = psvt->psvs;
+
+ thd_log_info("Name :%s\n", psvt->name.c_str());
+ for (unsigned int j = 0; j < psvs.size(); ++j) {
+ install_passive([j]);
+ }
+
+ psvt_consolidate();
+ thd_log_info("\n\n ZONE DUMP BEGIN\n");
+ for (unsigned int i = 0; i < zones.size(); ++i) {
+ zones[i]->zone_dump();
+ }
+ thd_log_info("\n\n ZONE DUMP END\n");
+ passive_installed = 1;
+}
+
~~~
I have did the way you said, the one is affected and the one is not affected.
e.g. TGL and ADL platform.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1981087
Title:
thermald prematurely throttling GPU
Status in thermald package in Ubuntu:
Fix Released
Status in thermald source package in Jammy:
In Progress
Bug description:
[Impact]
* thermald prematurely throttling GPU
[Test Plan]
* Run game on the target machine.
* the FPS must not be throttled below 20FPS.
[Where problems could occur]
* better support for Passive Policy. currently passive policy 1 is supported
and it should have a bug if the machine only enable pssive policy 2.
~~~
I got a new game and started playing it
It would run at over 100 FPS solidly some of the time and then cyclically dip
down to below 20 FPS for a few minutes
I determined that it was thermald trying to keep my GPU below 70°C
to determine this I sudo systemctl stop thermald
The game ran solidly and consistently with the GPU at 75°C
This is well below the specs set by the manufacturer and perhaps
unreasonably low for a laptop
But more importantly I was given no indication this was happening. I
had to sleuth it out myself.
Perhaps it is impossible to determine good defaults for all hardware,
I don't know. However without an indication that this is happening
there will be a lot of people with a mysteriously broken experience.
This was extremely difficult for me to find and I had several friend
who are experts on linux gaming and video drivers trying to track this
down. I discovered it by luck and perseverance.
This absolutely needs some sort of indication and hopefully a way to
remedy it from the GUI. ideally it would set thermal limits that are
more in line with what the device is designed for and not a
conservative default if at all possible.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thermald 2.4.9-1
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Fri Jul 8 16:08:55 2022
InstallationDate: Installed on 2020-10-19 (626 days ago)
InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64
(20200731)
SourcePackage: thermald
UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980517] Re: ubuntu_bpf build failed with "error: ‘struct bpf_test’ has no member named ‘fixup_kfunc_btf_id’" on J-5.15 / F-5.15
** Changed in: linux (Ubuntu Jammy)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-kernel-tests
Status: In Progress => 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/1980517
Title:
ubuntu_bpf build failed with "error: ‘struct bpf_test’ has no member
named ‘fixup_kfunc_btf_id’" on J-5.15 / F-5.15
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
Issue found on Jammy 5.15, the test build will fail with:
In file included from
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/verifier/tests.h:21,
from test_verifier.c:432:
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/verifier/calls.c:124:10:
error: ‘struct bpf_test’ has no member named ‘fixup_kfunc_btf_id’
124 | .fixup_kfunc_btf_id = {
| ^~
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/verifier/calls.c:124:9:
warning: braces around scalar initializer
124 | .fixup_kfunc_btf_id = {
| ^
This is because of commit 13c6a37d4 "selftests/bpf: Add test for
reg2btf_ids out of bounds access" upstream.
Issue reported to stable mailing list:
https://lore.kernel.org/stable/20220429104052.345760...@linuxfoundation.org/T/#m3ad9b4882ab3d98fc65feee95f5d78019461835f
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1980517/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993479] 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/1993479 Title: Dell G5 5500 touchpad and keyboard not detected Status in linux package in Ubuntu: Confirmed Bug description: After an upgrade to Ubuntu 22.04 LTS the on-boaard keyboard and touchpad on my Dell G5 5500 do not work and are not shown in /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 1696 F pulseaudio /dev/snd/pcmC1D0p: john 1696 F...m pulseaudio /dev/snd/controlC0: john 1696 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 08:43:47 2022 InstallationDate: Installed on 2021-04-21 (546 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. G5 5500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=00617001-053b-4da9-b627-ca8ee14453f5 ro quiet splash acpi=noirq vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-14 (4 days ago) dmi.bios.date: 09/08/2022 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 03GNH6 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd09/08/2022:br1.20:svnDellInc.:pnG55500:pvr:rvnDellInc.:rn03GNH6:rvrA02:cvnDellInc.:ct10:cvr:sku09E2: dmi.product.family: GSeries dmi.product.name: G5 5500 dmi.product.sku: 09E2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993479] [NEW] Dell G5 5500 touchpad and keyboard not detected
Public bug reported: After an upgrade to Ubuntu 22.04 LTS the on-boaard keyboard and touchpad on my Dell G5 5500 do not work and are not shown in /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 1696 F pulseaudio /dev/snd/pcmC1D0p: john 1696 F...m pulseaudio /dev/snd/controlC0: john 1696 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 08:43:47 2022 InstallationDate: Installed on 2021-04-21 (546 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. G5 5500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=00617001-053b-4da9-b627-ca8ee14453f5 ro quiet splash acpi=noirq vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-14 (4 days ago) dmi.bios.date: 09/08/2022 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 03GNH6 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd09/08/2022:br1.20:svnDellInc.:pnG55500:pvr:rvnDellInc.:rn03GNH6:rvrA02:cvnDellInc.:ct10:cvr:sku09E2: dmi.product.family: GSeries dmi.product.name: G5 5500 dmi.product.sku: 09E2 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993479 Title: Dell G5 5500 touchpad and keyboard not detected Status in linux package in Ubuntu: New Bug description: After an upgrade to Ubuntu 22.04 LTS the on-boaard keyboard and touchpad on my Dell G5 5500 do not work and are not shown in /proc/bus/input/devices ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 1696 F pulseaudio /dev/snd/pcmC1D0p: john 1696 F...m pulseaudio /dev/snd/controlC0: john 1696 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 19 08:43:47 2022 InstallationDate: Installed on 2021-04-21 (546 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. G5 5500 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic root=UUID=00617001-053b-4da9-b627-ca8ee14453f5 ro quiet splash acpi=noirq vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-50-generic N/A linux-backports-modules-5.15.0-50-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-14 (4 days ago) dmi.bios.date: 09/08/2022 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 03GNH6 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd09/08/2022:br1.20:svnDellInc.:pnG55500:pvr:rvnDellInc.:rn03GNH6:rvrA02:cvnDellInc.:ct10:cvr:sku09E2: dmi.product.family: GSeries dmi.product.name: G5 5500 dmi.product.sku: 09E2 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981087] Re: thermald prematurely throttling GPU
I'm just surprised that "make passive policy 1 default" isn't a cleanly cherry-pickable thing. That *sounds* like it should be one line of code :) Unless it first needs to implement support for "passive policy 1", which it may well need to! But I don't know that unless someone tells me :) Since the churn *is* necessary, then we should organise testing on a wide variety of laptops - both ones which are expected to have bugs fixed by this upload, and ones which aren't expected to be affected by this upload. The CI lab should have a reasonable selection; what sort of automated testing can be done for this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: In Progress Bug description: [Impact] * thermald prematurely throttling GPU [Test Plan] * Run game on the target machine. * the FPS must not be throttled below 20FPS. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
This issue is affecting me as well 5.15.0.50-generic and 5.15.0.52-generic are both broken. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: originate-from-1992116
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in Linux:
New
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in mutter package in Ubuntu:
Opinion
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
