Public bug reported:
Hi,
Legion laptop with Nvidia.
- Nouveau : no hdmi
- Nvidia 535 dynamic graphics : no HDMI (screen not detected)
- Nvidia 535 discrete graphics : HDMI is detected
So I suppose this bug to be linked to Intel GPU.
All was ok with previous 6.3 kernel.
** Affects: linux (Ubunt
The legacy flag only works when you also set a model, for me the model
dell-headset-multi works. You have to shutdown the system completely
after setting these options. When you have done that you should be able
to reboot without locking up. The logs will still contain errors though.
--
You recei
We are still seeing this issue on 5.15.0-82-generic for 22.04 (Jammy)
Since the (Ubuntu Jammy) is on Fix Committed and not Fix Released, I
would assume this is normal right? And the Fix Released status on
(Ubuntu) means the bug is not present on other Ubuntu versions?
--
You received this bug n
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2028746
Title:
Fix UBSAN in Intel EDAC driver
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2029199
Title:
NULL pointer dereference on CS35L41
*** This bug is a duplicate of bug 2031537 ***
https://bugs.launchpad.net/bugs/2031537
** This bug has been marked a duplicate of bug 2031537
Ethernet not stable 23.04 (RTL8168/8169)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2029199
Title:
NULL pointer dereference on CS35L41
i tried setting snd_intel_dspcfg.dsp_driver to 1 (legacy) as a
workaround without success but it did change the lockup output:
watchdog: BUG: soft lockup - CPU#7 stuck for 23s! [kworker/7:3:326]
Sep 01 13:03:32 jammy kernel: Modules linked in: bridge xt_pkttype xt_tcpudp
xt_state stp xt_conntrack
And you can also buy a new device, with SMB version 3 or newer, will this also
solve the problem?...
Maybe the developers will return the correct work with version 1.0?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
[25013.905943] INFO: task DOMCacheThread:17496 blocked for more than 120
seconds.
[25013.905945] Tainted: P OE4.15.0-54-generic #58-Ubuntu
[25013.905947] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[25013.905949] DOMCacheThread D0 17496 224
[25013.905943] INFO: task DOMCacheThread:17496 blocked for more than 120
seconds.
[25013.905945] Tainted: P OE4.15.0-54-generic #58-Ubuntu
[25013.905947] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[25013.905949] DOMCacheThread D0 17496 224
All autopkgtests for the newly accepted linux-meta-azure-6.2
(6.2.0.1011.11~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-azure-6.2/6.2.0-1011.11~22.04.1 (arm64)
Please visit the excuses page listed below and inve
Dear Team
My laptop up 41 hours without network issue, "pcie_aspm=off" is work
for me.
Waiting for future updates, too.
Many thanks.
--
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/
I have observed the same cifs issue upon using kernel 6.20-31. I was
able to resolve the issue via a method provided in cifs-utils bug report
2031246 https://bugs.launchpad.net/ubuntu/+source/cifs-
utils/+bug/2031246.
--
You received this bug notification because you are a member of Kernel
Packag
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/2033693
Title:
Kernel bug lead to unresponsiv
Public bug reported:
A server became unresponsive. After a hardware reset the server came
back up. /var/log/kern.log shows a stacktrace at Aug 31 19:42:36:
Aug 31 19:42:36 prod01 kernel: [1222010.240461] pcieport :00:1c.1: AER:
Multiple Corrected error received: :00:1c.1
Aug 31 19:42:36
I had to make a VM, but focal seems to work
** Tags removed: verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
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/201
PLease keep in mind that the test plan should be executed on the jammy
official kernels.
--
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/2028217
Title:
MTL: Add support for Meteor Lake
Hello koba, or anyone else affected,
Accepted thermald into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/thermald/2.4.9-1ubuntu0.4 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Public bug reported:
[issue]
This patch set addresses several CoreSight PMU issues. These are all
upstream patches.
Commit Summary
2940a5e perf: arm_cspmu: Fix variable dereference warning
06f6951 perf: arm_cspmu: Set irq affinitiy only if overflow interrupt is used
292771d perf/arm_cspmu: Fix
On Thu, 31 Aug 2023 at 14:22, Andreas Hasenack
<2028...@bugs.launchpad.net> wrote:
>
> I suppose it's possible that the particular dkms module that failed to
> build is essential for booting the system, so the new approach that
> hides this build failure could render the system unbootable without t
> I suppose it's possible that the particular dkms module that failed to build
> is essential for booting the
> system, so the new approach that hides this build failure could render the
> system unbootable without the
> user realizing it.
We still have the old kernel with the built DKMS around,
Found on bionic/linux-aws-5.4: 5.4.0-1109
--
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/1876687
Title:
func_traceonoff_triggers.tc from ubuntu_kselftests_ftrace flaky
(Tracing file is
** Also affects: ubuntu-z-systems
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/2029261
Title:
[UBUNTU 23.04] vlan interface lost after reboo
Hi Andreas,
Anbox dkms module is incomptible with kernel 6.2.0-27-generic.
Solution applied:
1- Anbox removed
2- Command applied:
$ dkms remove anbox-ashmem/1 --all
$ dkms remove anbox-binder/1 --all
System is now ok.
apt update : ok without error
apt upgrade : ok without error
Restart o
** Also affects: gdm (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: nvidia-graphics-drivers-470 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: gdm (Ubuntu M
all current nvidia releases support simpledrm since last March, except
390 which has been EOL for some time now
--
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/1965303
Title:
Migrate from
thanks for the heads-up, yeah that'd need to be fixed in jammy as well
(for gdm) when a hwe kernel supports simpledrm
I'm thinking if mantic 6.5 would be the first candidate
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: New => Fix Released
--
You received this bug notificat
I'm adding a task for gdm to this bug. The reason is that if simpledrm
is used, we've found race conditions that occur where the transition
from simpledrm to the proper KMS driver may race with gdm starting up
the login screen.
When gdm loses the race you end up with a black screen. So please ma
@Nerdopolis If everything goes well, it should be release next week.
Could you also verify if this change works as expected for focal? :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016
** Tags removed: verification-done-focal verification-needed-focal-linux
** Tags added: verification-done-focal-linux
--
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/2031022
Title:
Fix bo
Public bug reported:
[Impact]
Hard hangs in some cases on resume from suspend on AMD Phoenix
[Fix]
pick three commits from v6.5-rc7 (also in 6.1.47):
730d44e1fa306a2 drm/amd/pm: skip the RLC stop when S0i3 suspend for SMU
v13.0.4/11
f1740b1ab2703b2 drm/amdgpu: skip fence GFX interrupts disabl
mantic will have 6.5 soon enough
** Changed in: linux (Ubuntu Jammy)
Status: New => Won't Fix
** Changed in: linux-oem-6.1 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
S
The verification of the Stable Release Update for dkms has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a reg
This bug was fixed in the package dkms - 3.0.10-7ubuntu2.1
---
dkms (3.0.10-7ubuntu2.1) lunar; urgency=medium
* Unsupported DKMS modules break kernel header installation if compilation
fails. Handle this by ignoring autoinstall errors if a release upgrade is
in progress or i
I suppose it's possible that the particular dkms module that failed to
build is essential for booting the system, so the new approach that
hides this build failure could render the system unbootable without the
user realizing it. A bit less catastrophic, but still very serious,
would be for the mac
these are in 6.5
** 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-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2021572
Title:
dGPU cannot resume because
** Also affects: nvidia-graphics-drivers-535-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Status: New => In Progress
** Changed in: nvidia-graphics-drivers-535-server (Ubuntu)
Assignee: (unassigned) => Alberto M
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubu
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-jammy-linux-oem-6.5 verification-
needed-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 i
Actually I see an exit status 1 instead of 11:
E: linux-image-6.2.0-31-generic: installed linux-image-6.2.0-31-generic
package post-installation script subprocess returned error exit status 1
and is the /boot/initrd.img-6.2.0-31 CPIO archive missing afterwards.
Luckily I can fall back to kernel 6
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
** Tags added: verification-needed-jammy-linux-oem-6.5 verification-
needed-jammy-mantic-linux
--
You received this bug notifi
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.lau
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => Fix Committed
** Tags added: verification-done-jammy-linux-oem-6.5
--
You re
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.n
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2028746
Title:
Fix UBSAN in Intel EDAC driver
Stat
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
** Tags added: verification-needed-jammy-linux-oem-6.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.n
Tested again with Mantic daily-preinstall from 31-Aug: the problem is
still there.
Tested the 23.04 image (
https://cdimage.ubuntu.com/releases/23.04/release/ubuntu-23.04-preinstalled-
server-riscv64+visionfive2.img.xz ) using the same SD card and the same
VisionFive2 board. The image boots and th
Public bug reported:
After waking up from hibernation
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-6.2.0-31-generic 6.2.0-31.31
ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15
Uname: Linux 6.2.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportV
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a memb
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2028749
Title:
Make TTY switching possible fo
** Also affects: linux-oem-6.5 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Lunar)
Status: New => Invalid
--
You received this bug notification because you are a member of Ker
** Changed in: linux-oem-6.5 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-6.5 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of K
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2030872
Title:
Azure: hv_netvsc: add support for vlans in A
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Pac
Hello Team,
PC up and running for 48h straight. Looks like adding the
"pcie_aspm=off" does indeed work.
Waiting for a future update to remove such a line.
Thanks for the support.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Comm
Dear Juerg,
For me, after setting pcie_aspm=off already work over 25 hours.
But Ahmed report in #51, pcie_aspm=off still can't solve this
issue, that's why I ask him about current comment line and update-grub
or not.
Please check #51 and I will keep monitoring with my laptop.
@David @Giuliano
Same issue for me I updated kernal version 6.1 and run your compile.sh
again but showing me error same as @Marcos script do you have any solution for
that
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Keep `pcie_aspm=off` as a work-around until we fix this properly.
--
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/2031537
Title:
Ethernet not stable 23.04 (RTL8168/8169)
Status in linux
You should not go back to 5.19. That kernel is dead and receives no
longer any security or other updates.
--
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/2031537
Title:
Ethernet not stabl
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2032176
Title:
Crashing with CPU soft lock on GA kernel 5.1
63 matches
Mail list logo
