** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Mehmet Basaran (mehmetbasaran)
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Mehmet Basaran (mehmetbasaran)
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: linux (Ubuntu)
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812116/+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/20
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812114/+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/2077405
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812115/+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/bug
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812109/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812113/+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/2077405
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812111/+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/b
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812112/+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/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812095/+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
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812110/+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
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812108/+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.l
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812106/+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/2077405
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812107/+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/b
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812105/+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/2077
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812103/+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/2077405
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812104/+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/2077
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812097/+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/2077405
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812098/+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/20
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2077405/+attachment/5812096/+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/20
apport information
** Tags added: apport-collected
** Description changed:
With Kernel 6.8.0-40 (upgraded yesterday)
a) the external screen connected to my Lenovo T14 ThinkPad randomly turns
black for a few seconds and then recovers,
b) the laptop cannot be used after the lid has been cl
Public bug reported:
[Impact]
io_commit_cqring() writes the CQ ring tail to make it visible and also triggers
any deferred work.
When a ring is set up with IOPOLL, it doesn't require locking around the CQ
ring updates.
However, if there is deferred work that needs processing, io_queue_deferred()
User is running and was testing Noble. We also backport this to Jammy
for the 6.8 HWE kernel. Unable to test this on Jammy so assuming
success.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-f
The issue should be fixed in 6.8.0-44.44 by below commit
commit 27e70aa72937bcfd08ffc10727ad315f9763e6ac
Author: Hui Wang
Date: Thu Jul 18 16:57:16 2024 +0800
e1000e: move force SMBUS near the end of enable_ulp function
BugLink: https://bugs.launchpad.net/bugs/2073358
The
There is no change for this firmware in this re-upload, so re-adding the
tag verification-done-jammy.
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.
This was verified by Xilinx in a test PPA.
** Tags removed: verification-needed-jammy-linux-xilinx-zynqmp
** Tags added: verification-done-jammy-linux-xilinx-zynqmp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ub
** Also affects: linux-xilinx-zynqmp (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux-xilinx-zynqmp (Ubuntu)
Status: In Progress => Confirmed
** Changed in: linux-xilinx-zynqmp (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux-xilinx-zynq
Public bug reported:
[Summary]
During the SRU testing, I found at least 2 DUTs always timeout after
suspend test, after checking I found that both of them only detect 10
Mbps speed on their NIC and can't get IP from DHCP.
Part of journal log as follows:
Sep 02 10:55:00 ubuntu kernel: PM: suspend
This is still a problem and quite important one because any performance
investigations on Noble are complicated.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2019247
Title:
perf should
Public bug reported:
[Impact]
[Fix]
[Test]
[Where problems could occur]
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In Progress
** Affects: linux-oem-6.11 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects:
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
Hi Bozsoki,
>From the schedule, 2024.08.05 cycle will release 6.8.0-44 kernel.
So, the optimise schedule will be at the end of Oct, which is 8 weeks later.
https://kernel.ubuntu.com/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-h
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
I believe this is related to the issue:
[15868.339701] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[15868.340230] [drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU
ID 0x0100] Failed to grab modeset ownership
[158
** Summary changed:
- Noble update: upstream stable patchset 2024-08-29
+ Noble update: upstream stable patchset 2024-09-02
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scop
>From just a cursory look it seems like maybe one of the two drivers (the
memory temp driver or underlying EDAC driver) isn't handling some dimm
configurations correctly. my dimm configuration looks like:
/sys/devices/system/edac/mc/mc0/dimm0/dimm_location:branch 0 channel 0 slot 0
/sys/devices/s
Ok, can confirm after having disabled Gnome's 'screen lock' entirely,
that this is triggered merely by the 'Screen blanking' being invoked.
For now will workaround by disabling that, but in case it's useful
here's the dmesg output from when this happened just now when the screen
blanked. Leaving ou
`prevjournal.txt` (looks like I can't attach multiple files to a single
post)
If it helps, current system with the issue is an i7-12700F with an NVIDIA
GeForce RTX 4070 SUPER (pci-id 10de:2783).
I also have a suspicion that problematic behaviour only ensues after playing
Steam games full screen,
I'm having the same issue right now. I've just applied latest updates,
but not sure whether they're relevant - seems more relevant that I've
just moved to using HDMI audio based on the content of this crash, but
either could be involved.
Attaching requested diagnostic files - please let me know if
I also have this problem with an Acer Nitro 17
AMD Ryzen 7 8845HS w/ Radeon 780M Graphics
6.8.0-41-generic
Nvidia 4060
32GB
Ubuntu 24.04.1 LTS
I can sometimes trigger it by using OrcaSlicer and manipulating 3D objects I'm
going to print.
--
You received this bug notification because you are a
Our top priority is the safety and well-being of our community, and we are
committed to offering comprehensive support to those who have experienced
damage from Eat-and-Run incidents.
https://www.toto-system.com/
--
You received this bug notification because you are a member of Kernel
Packages
Upgraded successfully to 24.04 and the 6.8. kernel is working as it did
for Fedoras 40:
$ sudo dmesg | grep ath11k
[ 18.787935] ath11k_pci :72:00.0: BAR 0 [mem 0xa250-0xa25f
64bit]: assigned
[ 18.787959] ath11k_pci :72:00.0: enabling device ( -> 0002)
[ 18.788346] ath11k
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: opa-ff (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/1215411
I'll be off for the next week.
I'll investigate and respond as soon as I'm back.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2077265
Title:
Screen freezes with kernel 6.8 (als
The same problem in Ubuntu 24.04.1
Details:
- clean install of Ubuntu 24.04.1 (no dual boot, no other OS)
- external hard drive with NTFS
I plug in the USB cable and I get the error message: "error mounting /dev/sdb1".
If I plug the cable to a machine with Ubuntu 22.04.4 it mounts O.K.
Any help ple
Still affects jammy on a ThinkPad X260 with kernel 6.8.0-40-generic.
I haven't tried the workaround yet but a `rmmod btusb; modprobe btsub`
makes Bluetooth work on this notebook.
Actually, I am pretty sure it worked before and this is a more recent
regression, maybe when the LTS kernel was update
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.ne
The machine is getting more and more inresponsive the longer the machine is
running. There are lots of "Application x" is not responding" - windows.
I only run Chrome and Chrome Remote Desktop.
Top cpu eaters are "chrome --type =renderer --crashpad-handler-pid",
20%, gnome-shell 10-20%
If I look
The out-of-tree mali400 driver for the GPU does not build against the
6.8 kernel, as the register_shrinker apis it depends on is removed in
the 6.7 kernel [1].
[1]:
https://lore.kernel.org/all/2023091109.68966-7-zhengqi.a...@bytedance.com/
--
You received this bug notification because you ar
I am having the same issue with Focal. Will this be fixed in the focal
kernel, too?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076576
Title:
5.15.0-118: NFS causes suspend to fail
52 matches
Mail list logo
