This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
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-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the
This bug is awaiting verification that the linux-
gcp-6.2/6.2.0-1021.23~22.04.1 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-jammy-linux-
gcp-6.2' to
This bug is awaiting verification that the linux-
bluefield/5.15.0-1033.35 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-jammy-linux-bluefield' to
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.1~22.04.1 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-jammy-linux-
lowlatency-hwe-6.5' to
This bug is awaiting verification that the linux-nvidia-
tegra-5.15/5.15.0-1020.20~20.04.1 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-focal-linux-
nvidia-tegra-5.15' to
This bug is awaiting verification that the linux-intel-
iotg-5.15/5.15.0-1046.52~20.04.1 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-focal-linux-
intel-iotg-5.15' to
This bug is awaiting verification that the linux-nvidia-tegra-
igx/5.15.0-1007.7 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-jammy-linux-nvidia-tegra-
igx' to
This bug is awaiting verification that the linux-nvidia-6.5/6.5.0-1007.7
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-jammy-linux-nvidia-6.5' to 'verification-done-
This bug is awaiting verification that the linux-nvidia-
tegra/5.15.0-1020.20 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-jammy-linux-nvidia-tegra' to
This bug is awaiting verification that the linux-
gcp-5.15/5.15.0-1048.56~20.04.1 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-focal-linux-
gcp-5.15' to
This bug is awaiting verification that the linux-
lowlatency/5.15.0-91.101 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-jammy-linux-lowlatency' to
This bug is awaiting verification that the linux-intel-
iotg/5.15.0-1046.52 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-jammy-linux-intel-iotg' to
This bug is awaiting verification that the linux-gkeop/5.15.0-1034.40
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-jammy-linux-gkeop' to 'verification-done-jammy-
linux-gkeop'. If
This bug was fixed in the package linux - 5.15.0-91.101
---
linux (5.15.0-91.101) jammy; urgency=medium
* jammy/linux: 5.15.0-91.101 -proposed tracker (LP: #2043452)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix
I have successfully upgraded from Lunar to Mantic with kernel
6.5.0.14.16 so the fix for this must've been merged on a recent release
to ubuntu's main repo:
```
~ apt policy linux-image-generic
linux-image-generic:
Installed: 6.5.0.14.16
Candidate: 6.5.0.14.16
Version table:
***
This bug is awaiting verification that the linux-
hwe-6.5/6.5.0-14.14~22.04.1 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-jammy-linux-
hwe-6.5' to
This bug is awaiting verification that the linux-azure/6.5.0-1010.10
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-mantic-linux-azure' to 'verification-done-
mantic-linux-azure'. If
This bug is awaiting verification that the linux-gcp/6.5.0-1010.10
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-mantic-linux-gcp' to 'verification-done-mantic-
linux-gcp'. If the
This bug is awaiting verification that the linux-laptop/6.5.0-1007.10
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-mantic-linux-laptop' to 'verification-done-
mantic-linux-laptop'.
This bug is awaiting verification that the linux-
lowlatency/6.5.0-14.14.1 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-mantic-linux-lowlatency' to
This bug is awaiting verification that the linux-azure-
fips/5.15.0-1053.61+fips1 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-jammy-linux-azure-fips' to
I don't believe so, I'm on one of the affected laptops on
6.2.0-37-generic / 23.04 with no issues. It's 23.10's kernel 6.5 that
triggers the issue for me. The bug is also about 23.10, which wouldn't
have kernel 6.2 anyway.
--
You received this bug notification because you are a member of Kernel
@copong
> I'm not sure why kernel 6.2 keeps getting suggested by the ubuntu bot, it's
> never been affected by this bug, at least not on any kernel packaged for
> ubuntu 23.04.
Maybe the bug had been backported?
--
You received this bug notification because you are a member of Kernel
This bug is awaiting verification that the linux-riscv/6.2.0-39.40.1
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-lunar-linux-riscv' to 'verification-done-lunar-
linux-riscv'. If
I'm not sure why kernel 6.2 keeps getting suggested by the ubuntu bot,
it's never been affected by this bug, at least not on any kernel
packaged for ubuntu 23.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug is awaiting verification that the linux-
hwe-6.2/6.2.0-39.40~22.04.1 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-jammy-linux-
hwe-6.2' to
This bug is awaiting verification that the linux-starfive/6.2.0-1010.11
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-lunar-linux-starfive' to 'verification-done-
This bug is awaiting verification that the linux-aws/6.2.0-1017.17
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-lunar-linux-aws' to 'verification-done-lunar-
linux-aws'. If the
This bug is awaiting verification that the linux-lowlatency-
hwe-6.2/6.2.0-1018.18~22.04.1 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-jammy-linux-
lowlatency-hwe-6.2' to
This bug is awaiting verification that the linux-azure/6.2.0-1018.18
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-lunar-linux-azure' to 'verification-done-lunar-
linux-azure'. If
This bug is awaiting verification that the linux-gcp/6.2.0-1020.22
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-lunar-linux-gcp' to 'verification-done-lunar-
linux-gcp'. If the
This bug is awaiting verification that the linux-kvm/6.2.0-1018.18
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-lunar-linux-kvm' to 'verification-done-lunar-
linux-kvm'. If the
This bug was fixed in the package linux - 6.2.0-39.40
---
linux (6.2.0-39.40) lunar; urgency=medium
* lunar/linux: 6.2.0-39.40 -proposed tracker (LP: #2043451)
* USB bus error after upgrading to proposed kernel on lunar and jammy
(LP: #2043197)
- USB: core: Fix oversight
This bug is awaiting verification that the linux-gcp-tcpx/5.15.0-1003.3
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-focal-linux-gcp-tcpx' to 'verification-done-
The new 6.5 kernel contains other changes beside the fix for NVME, so
the new issues may or may not be related. Please file a new bug and try
to provide some log of the failed boot (you can do a boot into 6.5 and
then reboot back into 6.2. Then "sudo journalctl -b-1" might contain
useful info to
@copong This bug does not represent the entire latest 6.5 update,
therefore if you have a different issue, please create another bug
report and we can take action from there.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Just to clarify, on mantic and kernel 6.5.0-12 the nvme issue is there,
but not the graphical issue with Plymouth or GDM hanging - I can boot up
the NVME drive from a usb-c adaptor and the problems aren't there.
--
You received this bug notification because you are a member of Kernel
Packages,
@Eric, those issues are introduced with this kernel as well, either as a
result of the patch or something else.
Also, ubuntu lunar's current kernel (6.2.0-36-generic) does not suffer from the
nvme issue. I'm writing this from there.
--
You received this bug notification because you are a
@copong , This bug tracks the issue with NVMe in the kernel, if you have
other issues please submit another bug.
** Tags removed: verification-failed-mantic-linux
** Tags added: verification-done-mantic-linux
--
You received this bug notification because you are a member of Kernel
Packages,
** Tags removed: verification-needed-mantic-linux
** Tags added: verification-failed-mantic-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/2040157
Title:
Unable to use nvme drive
I have tested linux/6.5.0-12 and it's been a mixed bag:
* The nvme fix seems to work, I can see my services loading and whatnot on the
boot log
* The Plymouth theme displays at half the size than with other kernels (I have
a 4k display with intel integrated graphics and nvidia gtx 1050
This bug is awaiting verification that the linux/6.5.0-12.12 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still
This bug is awaiting verification that the linux/6.2.0-38.39 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-lunar-linux' to 'verification-done-lunar-linux'. If
the problem still
This bug is awaiting verification that the linux/5.15.0-90.100 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-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
** Changed in: linux (Ubuntu Lunar)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu)
Status: Confirmed =>
The upstream fix for this is:
commit 0e4cac557531a4c93de108d9ff11329fcad482ff
[PATCH] misc: rtsx: Fix some platforms can not boot and move the l1ss
judgment to probe
commit 101bd907b424 ("misc: rtsx: judge ASPM Mode to set PETXCFG Reg")
some readers no longer force #CLKREQ to low
when the
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Additional note: the comment about blacklisting in the bug report was
somewhat mangled:
> I can confirm that blacklisting the drivers (rtsx_pci_and sdmmc and
rtsx_pci) and rebuilding the initramfs...
I found there is a rtsx_pci_sdmmc module, so potentially the complete
kernel argument is:
The upstream bug report ends in bisecting to:
commit 69304c8d285b77c9a56d68f5ddb2558f27abf406
Author: Ricky WU
Date: Tue Jul 25 09:10:54 2023 +
misc: rtsx: judge ASPM Mode to set PETXCFG Reg
commit 101bd907b4244a726980ee67f95ed9cafab6ff7a upstream.
ASPM Mode is
49 matches
Mail list logo
