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/1983815
Title:
[ThinkPad T16 Gen 1] No
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 1990342
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
Configuration:
-
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
- CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
- BMC Version 0.48 (Build ID: ESX303K)
- UEFI Version 0.62 (Build ID: ESE105G)
-
root@jam:~# lspci -s 00:19.0 -vvvnn
00:19.0 RAID bus controller [0104]: Intel Corporation Device [8086:282f] (rev
11)
DeviceName: PCH Integrated SATA Controller 2
Subsystem: Lenovo Device [1d49:0116]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+
Public bug reported:
Configuration:
OS:ubuntu-20.04.5-live-server-amd64.iso,ubuntu-22.04-live-server-amd64.iso,ubuntu-22.04.1-live-server-amd64.iso
CPU:SPR-SP XCC D-0 48c 270w ES2 99AL8V/QYFN
BMC Version0.48 (Build ID: ESX303K)
UEFI Version 0.62 (Build ID: ESE105G)
Drive 1
** Bug watch removed: gitlab.freedesktop.org/drm/intel/-/issues #6401
https://gitlab.freedesktop.org/drm/intel/-/issues/6401
** Summary changed:
- no detection of the hdmi display moinitor
+ [ThinkPad T16 Gen 1] No detection of the HDMI monitor
** Changed in: linux (Ubuntu)
Status:
HDMI port is detected.
https://forums.lenovo.com/t5/Other-Linux-Discussions/Thinkpad-T16-can-t-
resume-from-suspend/m-p/5160642?page=7
$ fwupdmgr refresh
$ fwupdmgr update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
[Impact]
+ It hangs while doing S3 test on the platform with CPU Intel(R) Pentium(R)
Silver N6005 @ 2.00GHz
[Fix]
+ Can't reproduce this issue with v5.18-rc1 kernel, so bisecting the kernel and
found this below commit
+ 567511462387 mm/memcg: protect memcg_stock
Public bug reported:
[Impact]
[Fix]
[Test]
[Where problems could occur]
** Affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux-oem-5.17 (Ubuntu Jammy)
Importance: Undecided
Assignee: AceLan Kao (acelankao)
Status: In
Thanks for the fix!
Tests restarted.
** Changed in: ubuntu-kernel-tests
Status: New => 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/1990090
Title:
** 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/1990236
Title:
5.19.0-17.17: kernel NULL pointer dereference,
We've worked around this in the autopackage test environment by
blacklisting the virtio_rng module, so I'm setting this task to Fix
Released.
** Changed in: auto-package-testing
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages,
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/1990318
Title:
iwlwifi causes kernel panic
Applied Luke's patch to the qa-regression-testing repo:
https://git.launchpad.net/qa-regression-
testing/commit/?id=7fb27c11cc22f99ed39ebb7c04e62b3eccf3ab64 (with added
references to this bug report), thanks!
(We happily take merge requests via the above, but can take patches
however people
@alexmurray Submited merge request :) 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/1990090
Title:
test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
on
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990318/+attachment/5617540/+files/dmesg.202209201802
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
After I suspend and resume my laptop, everything works fine for about 60
seconds. From there, my system locks up and the kernel panics. I have
narrowed down the kernel panic happen only when iwlwifi is loaded.
Unloading iwlwifi prevents the kernel panic. I have tried
Also in 22.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1918085
Title:
Package linux-crashdump in 20.04 configures kernel cmdline crashkernel
incorrectly causing lock-up on
@lukenow could you please submit it as a merge request for the QA
Regression Testing project in Launchpad? https://code.launchpad.net/qa-
regression-testing
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: patch
--
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/1990090
Title:
test_520_config_random_trust_cpu in ubuntu_qrt_kernel_security failed
on Bionic 4.15
Status in QA
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
I attached a patch that updates the test case in qa-regression-testing,
do you know where I would submit this patch or who I would talk to?
** Patch added:
"0001-test-kernel-security.py-Update-RANDOM_TRUST_CPU-test.patch"
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 1990292
and then change the status of the bug to 'Confirmed'.
If, due to the
All autopkgtests for the newly accepted linux-meta (4.15.0.194.179) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
linux/4.15.0-194.205 (i386, amd64, s390x, ppc64el)
Please visit the excuses page listed below and investigate
** Package changed: 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/1990292
Title:
Mistery memory usage in linux Kernel >= 5.14
Status in linux package in
You have been subscribed to a public bug:
My hardware is SuperMicro X11SDV-8C-TP8F with Intel D-2146NT.
I've tested this issue with:
* Ubuntu 22.04 Kernel 5.15
* Ubuntu 22.04 Kernel 5.17
* Ubuntu 20.04 Kernel 5.15
* Ubuntu 20.04 Kernel 5.14
Using Ubuntu 20.04 with kernel 5.13 or lower will NOT
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 1990294
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
ramiro@HP-s151nr:~$ lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
ramiro@HP-s151nr:~$
ramiro@HP-s151nr:~$ sudo apt update
[sudo] password for ramiro:
Hit:1 http://co.archive.ubuntu.com/ubuntu focal InRelease
Hit:2
** Also affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
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/1990296
Title:
package linux-tools-5.15.0-48
** Tags removed: need-duplicate-check
--
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/1990296
Title:
package linux-tools-5.15.0-48 (not installed) failed to
install/upgrade: trying to
Never happened in previous versions of Ubuntu. Only in current 22.04.1
--
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/1990296
Title:
package linux-tools-5.15.0-48 (not installed) failed
Public bug reported:
having issues installing linux-tools-lowlatency beside linux-tools-
generic. Never had this issue before.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-tools-5.15.0-48 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-47.53-lowlatency 5.15.46
Uname: Linux
** Changed in: linux (Ubuntu)
Status: Fix Committed => 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/1981554
Title:
[Ubuntu-22.04] Video mode is not working with
Managed to capture the kernel crash during LiveUSB boot
** Attachment added: "USB 22.04 boot crash"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+attachment/5617448/+files/image20220811_223937394.jpg
--
You received this bug notification because you are a member of Kernel
Hi Sreekanth,
Have you had an opportunity to test the test kernel in comment #8?
--
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
I just noticed, why is the importance marked as "wishlist"?
it is confirmed bug as,
A function (wake on touchpad interaction) was working in several past version
of Ubuntu
(atleast 18.04 to 21.04), but stopped working with Ubuntu 21.10 (Kernel 5.15).
Kernel: 5.13 -> bug -> 5.14
Last when I
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/1990286
Title:
X display crash
Status in
** Summary changed:
- PolarFire Icicle Kit: enable PCIe support
+ [FFe] PolarFire Icicle Kit: enable PCIe support
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1989566
Title:
Public bug reported:
Display frequently crashes when running windows 10 pro in KVM Virtual
Machine. When the system is in too much pressure in memory consumption
and workload then also display crashes.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-47-generic
Since kinetic/22.10 is based on 5.19 and all patches got upstream
accepted with at least v5.18 (one 5.17), everything needed is included
in kinetic/22.10.
For jammy/22.04 I checked master-next and found all patches in
Ubuntu-5.15.0-41 or later, so jammy/22.04 incl. all the fixes and is not
(or
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-z-systems
Importance: Undecided => Medium
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners
Public bug reported:
== Comment: #0 - KISHORE KUMAR G - 2022-09-19 04:39:42
==
---Problem Description---
On a Ubuntu/s390 system that houses a Mellanox CX5 Adapter with two ports
connected to the a pair of TOR switches , act as entry point to cluster of
compute nodes to access public
You have been subscribed to a public bug:
== Comment: #0 - KISHORE KUMAR G - 2022-09-19 04:39:42
==
---Problem Description---
On a Ubuntu/s390 system that houses a Mellanox CX5 Adapter with two ports
connected to the a pair of TOR switches , act as entry point to cluster of
compute nodes
Thanks, this workaround is a great idea and works flawlessly!
--
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/1908916
Title:
brcmfmac bug while going to sleep
Status in linux package in
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/1990272
Title:
PCIe Bus Error: Uncorrected,
If you don't find it's bug 1958191 which was fixed in mainline kernel
5.17.7 then please also try other mainline kernels to see if a fix for
this does exist in some newer version:
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
--
You received this bug notification because you are a
Moved to the kernel because flickering like that is always the kernel's
fault/responsibility. There's nothing mutter can do to make sub-frame
flickers.
Please check bug 1958191 to see if it's the same issue fixed in 5.17.7
and later or by i915.enable_dc=0 intel_idle.max_cstate=2
If that's not
Public bug reported:
My dmesg is getting spammed by these AER errors. The laptop (Lenovo X1
Extreme Gen 5, Intel Core i7-12700H) is otherwise working fine.
The errors come in random waves of 60..160 back-to-back errors with an
interval of 130..140 microseconds.
Device [8086:51b0] is the
You have been subscribed to a public bug:
[Summary]
The monitor occurs the flicker problem while moving the mouse if the external
monitor is connected to type-c port via type-c-to-DP/HDMI dongle.
[Steps to reproduce]
1. Boot into OS with DP/HDMI Monitor via type-c-to-DP/HDMI dongle to
Please use one of these commands to provide a full log.
If you have not rebooted since the freeze:
journalctl -b0 > journal.txt
Or after you have rebooted:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Changed in: linux (Ubuntu)
Status: Confirmed =>
Based on comments in
https://gitlab.gnome.org/GNOME/mutter/-/issues/2384, a new fix might be
coming in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2482
** Changed in: linux (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassigned)
** Package changed: linux (Ubuntu) => mutter
Public bug reported:
Non-default GPUs (vboxvideo) in VirtualBox freeze at the login screen.
This is a regression of what was previously fixed in
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2360 but then
broken again upstream.
Sep 20 18:09:42 vjam gnome-shell[903]: Failed to post KMS
The same bug is reproducible on AWS EKS 1.23
--
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/1924298
Title:
accept returns duplicate endpoints under load
Status in Linux:
New
Status
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: Triaged => Fix Committed
** Changed in: linux (Ubuntu Jammy)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
** Description changed:
[Impact]
+ The TBT ID[8086:1134] the new project uses is not listed in the driver.
[Fix]
-
- [Test]
+ Intel submits this as we requested which is still in linux-next
+ https://lore.kernel.org/linux-usb/20220908104320.3409720-1-gil.f...@intel.com/
[Where
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1052.59
---
linux-oem-5.14 (5.14.0-1052.59) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1052.59 -proposed tracker (LP:
#1987820)
* Additional fix for TGL + AUO panel flickering (LP: #1983297)
- Revert
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
I'm experiencing the same issue.
I am running Ubuntu 20.04 with kernel 5.19.7-051907-generic
--
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/1983519
Title:
[linux 5.19] rcu_preempt
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.15.0-48.54
---
linux (5.15.0-48.54) jammy; urgency=medium
* jammy/linux: 5.15.0-48.54 -proposed tracker (LP: #1987775)
* System freeze after resuming from suspend due to PCI ASPM settings
(LP: #1980829)
- SAUCE: PCI/ASPM:
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux - 5.4.0-126.142
---
linux (5.4.0-126.142) focal; urgency=medium
* focal/linux: 5.4.0-126.142 -proposed tracker (LP: #1987819)
* [SRU] fnic driver on needs to be updated to 1.6.0.53 on Focal (LP: #1984011)
- scsi: fnic: Change
This bug was fixed in the package linux-azure - 5.15.0-1020.25
---
linux-azure (5.15.0-1020.25) jammy; urgency=medium
* jammy/linux-azure: 5.15.0-1020.25 -proposed tracker (LP: #1987744)
* Jammy update: v5.15.49 upstream stable release (LP: #1983149)
- [Config] azure:
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** 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.
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 1990236
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1990240
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
[Impact]
Got blank screen after entered desktop
[Fix]
Below commit in linux-next fixes the issue.
6215a7c8f552 drm/i915: Add new ADL-S pci id
[Test]
Verified on the target machine.
[Where problems could occur]
It only adds an ID to the list, should be pretty safe.
**
Public bug reported:
[Impact]
[Fix]
[Test]
[Where problems could occur]
** Affects: hwe-next
Importance: Undecided
Status: New
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: oem-priority originate-from-1988945 somerville
** Tags
Note: the bot wants me to run apport on this bug, however I can not run
apport on the broken kernel and running it on the working kernel is
likely to produce wrong logs.
Please look at the boot log that I attached manually instead.
--
You received this bug notification because you are a member
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1990236/+attachment/5617328/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Tags added: apport-collected kinetic
** Description changed:
After upgrading to 5.19.0-17.17 from 5.19.0-16.16, system began to lock up
unexpectedly.
Log inspection showed this:
Sep 20 09:05:20 zeus kernel: BUG: kernel NULL pointer dereference, address:
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 1990236
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
After upgrading to 5.19.0-17.17 from 5.19.0-16.16, system began to lock up
unexpectedly.
Log inspection showed this:
Sep 20 09:05:20 zeus kernel: BUG: kernel NULL pointer dereference, address:
0084
Sep 20 09:05:20 zeus kernel: #PF: supervisor read access in
confirmed but I didn't see 'verification-needed-jammy' be tagged.
** Tags added: verification-done-jammy
--
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/1982716
Title:
Audio
doing the last part of #2 does not make RPL-S load intel_pmc_core
note that it doesn't load even on my ADL-S
--
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/1988461
Title:
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 1979633
and then change the status of the bug to 'Confirmed'.
If, due to the
Hints removed, thanks!
** Changed in: ubuntu-kernel-tests
Status: New => 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/1986921
Title:
lttng-modules/2.13.1-1 ADT
OK, it appears that a simple way to trigger this bug is to run
sudo losetup -f /var/lib/snapd/snaps/bare_5.snap
Every time this command is run, the error is reported. If you add the
"-P" option, which should be used to force a partition scan, then you
get an additional warning line:
Sep 20
The correct fix should in kernel driver or GPU firmware.
Please track on drm-intel#6851.
** Changed in: oem-priority
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Verified with:
J-5.17.0-9.9~22.04.8:
* howzit-kernel (GOOD, tested with generic kernel)
J-5.15.0-49.55:
* helo-kernel (GOOD, tested with generic kernel)
* howzit-kernel (GOOD, tested with generic-64k kernel)
F-hwe-5.15.0-48.54~20.04.1
* howzit-kernel (GOOD, tested with generic-64k kernel)
just to be clear, the diff between upstream v5.19..v5.19.7 is this:
b431cffb4883b9e drm/i915/ttm: don't leak the ccs state
17c3edc70ff3eaf drm/i915: pass a pointer for tlb seqno at vma_invalidate_tlb()
26d7e3fcf0af9d5 drm/i915/gt: Batch TLB invalidations
99a4dbc0328d917 drm/i915/gt: Skip TLB
I don't have ADL-P myself
--
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/1990212
Title:
[ADL-P-IOTG graphics cause Ubuntu 22.10 hang
Status in intel:
New
Status in linux package in
Which Ubuntu kernel revision is bad, and which upstream version is good? We've
merged changes from 5.19.7 already, so if it's just v5.19 you've tested, please
test 5.19.7 too.
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You
1 - 100 of 103 matches
Mail list logo
