** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-oem-5.17 (Ubuntu Focal)
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Public bug reported:
[Impact]
I219 may stop working after s2idle. The link is up but failed to get an
IP address from DHCP server.
[Fix]
Revert the workaround patch "e1000e: Fix possible HW unit hang after an
s0ix exit" so the new fix "e1000e: Enable GPT clock before sending
message to CSME" can
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
22.04.1 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
20220329.git681281e40ubuntu3.4
3) What you expected to happen
"nosplash" should just prevent the boot-up graphics from being
displayed, which are done by plymouthd. And if plymouthd is not running
then it can't get stuck on a nouveau kernel bug at boot time. Though
there's still a risk of hitting the same or other nouveau bugs later.
--
You received this
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
**
I did locate the second patch and I have created a test kernel, please
test
https://people.canonical.com/~mreed/misc/lp_1965927_mpt3sas/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 1986520
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
SRU Justification:
Impact:
Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is
part of the Ice Lake D platform which is otherwise supported in 5.4. One of
the hardware vendors has requested that we update Ice in 5.4 to support E823.
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1986520
Title:
There are libvirtd errors in /var/log/syslog when powering
** Changed in: amd64-microcode (Ubuntu)
Status: Confirmed => Fix Committed
--
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/1983409
Title:
Please merge amd64-microcode
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
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
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
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
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 1986717
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
SRU Justification:
Impact:
Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is
part of the Ice Lake D platform which is otherwise supported in 5.4. One of
the hardware vendors has requested that we update Ice in 5.4 to support E823.
Fix:
I think
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
Patch submitted: https://lists.ubuntu.com/archives/kernel-
team/2022-August/132630.html
--
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/1986713
Title:
azure: Replace hyperv_fb with
Public bug reported:
SRU Justification
[Impact]
Microsoft has asked to replace hyperv_fb with hyperv_drm in linux-
modules-azure.
[Test Plan]
Extract linux-modules and ensure hyperv_drm.ko exists and hyperv_fb.ko
does not.
[Where things could go wrong]
According to Microsoft, hyperv_drm is
Thanks for taking the time to report this bug an trying to make Ubuntu
better.
Is this the only relevant message you found in the syslog? Is this error
causing some unexpected behavior apart from this message in the syslog?
You mentioned the error in the log but did not mention what is the
impact
** 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/1965927
Title:
[Ubuntu 22.04] mpt3sas: Request to include latest bug
I am setting this to confirmed and assigning owning teams per
https://wiki.ubuntu.com/UbuntuDevelopment/Merging
Please let me know if I assigned teams incorrectly or if I can do more
work for this merge.
** Changed in: amd64-microcode (Ubuntu)
Status: In Progress => Confirmed
** Changed
The next step to resolve this issue is to capture a trace of the USB bus
with a logic analyzer.
Does anyone affected by this problem happen to have access to a logic analyzer?
If so, post a trace here and someone can see if it is the device, the cable,
or the computer misbehaving.
--
You
As I said, most of the times boot proceeds with no issues. (I have heard
that boot sequence is randomized to make it less easier to attack by
code injection, maybe it depends on the order of loading?)
What does the nosplash parameter do? For now, at least, I can live with
this bug, since it
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 1986623
and then change the status of the bug to 'Confirmed'.
If, due to the
@koba
I installed thermald_2.5.0-1_amd64 from Debian Sid (sha256
19840c0dffd4424996016293dcbd9402595cdb5c0b1c709f94f08a717a239b2e) just
by grabbing the .deb and installing it
Started the service and ran a quick test. My graphics card reached a
peak of 81°C with no in-game slowdown whatsoever
I
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided => Critical
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Kernel
Another option is to hope the issue is limited to plymouthd and just
disable plymouthd with a kernel parameter: nosplash
BTW newer Nvidia drivers (versions >= 510 at least) have fixed the text
mode framebuffer resolution problem.
--
You received this bug notification because you are a member of
** 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/1986668
Title:
[VROC] Kernel does not contain fixes for iostat for md
Installing version 20.04 would get me stuck with the previous version of apps
and libraries, and that would be more annoying that dealing with the bug (since
it usually doesn't occur, and when it occurs it usually just require a system
restart. Also, I replaced the Nvidia driver with nouveau
Ok, sorry, I didn't understand which kernel is used in Jammy correctly. I've
opened new bug for 22.04
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668 .
Verification for Kinetic in progress, I will let you know here if issue is
reproducible there.
--
You received this bug
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 1986668
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Hello,
I noticed that kernel which was used in ubuntu 22.04 does not contain
fixes for IO statistics for md devices. IO statistics for md devices
were added to kernel 5.10
Logs are added in description instead of attachment. Changing to
confirmed.
** 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.
Yeah there are positive test results in bug 1978067.
--
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/1983143
Title:
AMD Rembrandt: DP tunneling fails with Thunderbolt monitors
> that would break most of the software already installed and would
leave me exposed to security bugs
Incorrect. Apps generally don't know the difference between kernel
versions and even the "old" 5.4 focal kernel is still supported with
security updates (last one was 6 days ago):
Fixed with LTP fork update (bug 1982995)
With LTP fork updated, the ubuntu_ltp_controllers on Jammy is now failing with:
* LP: #1986636
cpuset_inherit|cpuset_base_ops|cpuset_exclusive|cpuset_hierarchy|
cpuset_syscall|cpuset_sched_domains|cpuset_load_balance|
1049 has been in proposed since Friday, have you been able to test it?
--
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/1983143
Title:
AMD Rembrandt: DP tunneling fails with
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
This issue does not exist on J-realtime anymore.
INFO: Test start time: Tue Aug 16 06:08:56 UTC 2022
COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 648348 -n 648348 -f
/tmp/ltp-qVqxKBH0Bi/alltests -l /dev/null -C /dev/null -T /dev/null
LOG File: /dev/null
FAILED COMMAND File:
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: linux (Ubuntu
42 matches
Mail list logo
