** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance:
Your drive seems to be dying:
[ 843.681582] sd 2:0:0:0: [sda] tag#16 FAILED Result: hostbyte=DID_TIME_OUT
driverbyte=DRIVER_OK cmd_age=35s
[ 843.681588] sd 2:0:0:0: [sda] tag#16 CDB: Write(10) 2a 00 03 7d 98 00 00 0a
00 00
[ 843.681590] I/O error, dev sda, sector 58562560 op 0x1:(WRITE)
is included in Ubuntu-6.1.0-13.13 and up, and in oem-6.1 -1007
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: linux (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux
included in Ubuntu-6.1.0-13.13 and up, and in oem-6.1 -1007
** Changed in: linux (Ubuntu Lunar)
Status: In Progress => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: In Progress => Fix Committed
**
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Assignee: (unassigned) => Chris Chiu (mschiu77)
--
You received this bug
Actually I might have seen artifacts like that before. It was when I was
swapping LCD panels and I didn't have a clean connection on the ribbon
cable between the LCD and the laptop's motherboard. If you don't know
how to check that then it's safest not to try.
--
You received this bug
** Changed in: linux (Ubuntu Kinetic)
Status: In Progress => Fix Released
--
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/2000110
Title:
Keeps rebooting with AMD W6400,
That's quite unusual. I would lean toward thinking that's a broken LCD
panel.
Just in case, please also remember to run:
sudo update-grub
after editing /etc/default/grub. And then reboot.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I have adjusted the kernel parameters by opening the grub file at
/etc/default/grub and changing the GRUB_CMDLINE_LINUX_DEFAULT from
"quiet splash" to "quiet splash i915.enable_psr=0". No significant
change to the issue has occurred.
** Attachment added: "blueLines.jpg"
Thanks for the bug report.
Please try adding a kernel parameter:
i915.enable_psr=0
Please also attach a photo of the problem.
** Summary changed:
- Many Cyan Lines Cover Computer Screen
+ [Dell Inspiron 5521] Many Cyan Lines Cover Computer Screen
** Package changed: xorg (Ubuntu) => linux
You have been subscribed to a public bug:
bunch of cyan lines appearing on my screen rapidly, pretty sure its a
hardware issue but want to make sure the graphics drivers are up to
date.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Lunar)
Importance: Undecided
Status: New
--
You received
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2002501
Title:
mlxbf-pmc support for
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2004235
Title:
mlxbf-pmc counters not
Note that this test is still failing on X-4.4 AWS and T-4.4 AWS.
INFO: Test start time: Wed Jan 4 12:03:51 UTC 2023
COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 24091 -n 24091 -f
/tmp/ltp-uU5zrx72XR/alltests -l /dev/null -C /dev/null -T /dev/null
LOG File: /dev/null
FAILED COMMAND
Hi Steve,
sorry this was fell off from our radar.
I can confirm that this issue does not exist with T-azure-4.15 /
B-azure-4.15 anymore.
INFO: Test start time: Thu Jan 12 03:57:05 UTC 2023
COMMAND:/opt/ltp/bin/ltp-pan -q -e -S -a 2011 -n 2011 -f
/tmp/ltp-ZOzvNj4f7j/alltests -l
** Description changed:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
These 3 commits fix the issue
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio
Thanks. It seems the kernel isn't waking from sleep.
Can you attach a copy of /proc/acpi/wakeup ?
** 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.
** Changed in: linux-oem-6.0 (Ubuntu Lunar)
Status: New => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Lunar)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
The locality to this apparmor denial suggests to me it's just the bluez
snap that needs to request some extra privileges.
Feb 07 23:50:34 ubuntu audit[1562]: AVC apparmor="DENIED" operation="create"
profile="snap.bluez.bluez" pid=1562 comm="bluetoothd" family="alg"
sock_type="seqpacket"
You have been subscribed to a public bug:
Hi,
After waking up from suspend to RAM, my computer actually wakes up but
can sometimes then hang on a black screen (no prompt, nothing displayed,
screen is active).
This issue happens quite frequently but seems rather random. I think
certain
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2002373
Title:
Mic Mute LED doesn't work on DMIC laptops
Status in HWE
** Description changed:
[Impact]
With AMD W6400, W6600, or W6800 graphic cards the system keeps rebooting
while entering graphics mode.
[Fix]
+ These 3 commits fix the issue
+ a8671493d207 drm/amdgpu: make sure to init common IP before gmc
+ e3163bc8ffdf drm/amdgpu: move nbio
The fix should contain below 3 commits and confirmed that doesn't introduce
regressions on Dell Inspiron 3585 with AMD GPU.
a8671493d207 drm/amdgpu: make sure to init common IP before gmc
e3163bc8ffdf drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for
vega
dc1d85cb790f
Yes there's a problem with the cable or the port here.
Looking at Dell's website they seem to confirm the built-in HDMI port on
the Optiplex 3000 only supports HDMI 1.4, so it can't do 4K60Hz. To get
HDMI 2.0 support on the Optiplex 3000 you need to be using the optional
add-on port which screws
there was a kernel update today (5.15.0-60-generic) but I still see the
overflow followed by a kernel crash. So no change.
--
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/1998285
Title:
** Tags added: kinetic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1949075
Title:
[Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not
autoconnecting on power-on on 22.04
Commit a8671493d207 ("drm/amdgpu: make sure to init common IP before
gmc") intorduce a regression in 5.17-oem kernel and has been reverted
since 5.17.0-1027.28
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: Fix Released => In Progress
--
You received this bug notification because
This bug was fixed in the package broadcom-sta - 6.30.223.271-23~22.04.1
---
broadcom-sta (6.30.223.271-23~22.04.1) jammy; urgency=medium
* Lunar import, remove dh-dkms from Build-dep (LP: #2002636).
-- Paolo Pisati Thu, 12 Jan 2023 09:59:55
+
** Changed in: broadcom-sta
The verification of the Stable Release Update for broadcom-sta 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
Hello Paolo, or anyone else affected,
Accepted broadcom-sta into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/broadcom-
sta/6.30.223.271-23~22.10.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
The verification of the Stable Release Update for ubiquity 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
This bug was fixed in the package ubiquity - 22.04.19
---
ubiquity (22.04.19) jammy; urgency=medium
* zsys-setup: generate correct zfs-list.cache for target (LP:
#1993318)
-- Dimitri John Ledkov Tue, 10 Jan 2023
16:26:48 +
** Changed in: ubiquity (Ubuntu Jammy)
All of these CVEs related to
https://xenbits.xen.org/xsa/advisory-396.html have been addressed in
every kernel except for
- Ubuntu 20.04's linux-oem-5.14
- CVE-2022-23041 has not been addressed in the 4.15 based kernels.
--
You received this bug notification because you are a member of Kernel
The API that was failing in this test was introduced in the 4.6 kernel
series (in b844f0ecbc56 ("vfs: define kernel_copy_file_from_fd()")), so
trusty's 4.4 kernel should not be affected. The linux-azure 4.15 kernels
in trusty and xenial have the needed fix applied, are they still
affected by this
** Bug watch added: Debian Bug tracker #1030898
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030898
** Also affects: libpcap (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030898
Importance: Unknown
Status: Unknown
** No longer affects: libpcap (Ubuntu
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: libpcap (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Summary changed:
- [focal, jammy]Enable rdma-sniffer for libpcap
+ Enable rdma-sniffer for libpcap
** Also affects: libpcap (Ubuntu Focal)
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/2001564
Title:
Kernel crash due to Bluefield
Patches committed. Due for release in the 2023.01.30 SRU cycle.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1990167
Title:
cma alloc failure in large 5.15 arm instances
Status
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in
Hey Don,
Everything has been accepted by the kernel team. I don't have an eta on
when it will be merged, but there's nothing more to do now but wait and
eventually this should be updated with a request to test a proposed
kernel in the next few weeks.
--
You received this bug notification
I have sent patches for both Kinetic and Lunar on the mailing list:
https://lists.ubuntu.com/archives/kernel-team/2023-February/136945.html
https://lists.ubuntu.com/archives/kernel-team/2023-February/136949.html
These now reenable the compilation of nat6to4 with CC support.
--
You received this
I have sent patches for both Kinetic and Lunar on the mailing list:
https://lists.ubuntu.com/archives/kernel-team/2023-February/136945.html
https://lists.ubuntu.com/archives/kernel-team/2023-February/136949.html
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
**
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/2006624
Title:
Multiple Kernel Ooopses with
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux-oem-5.17 - 5.17.0-1027.28
---
linux-oem-5.17 (5.17.0-1027.28) jammy; urgency=medium
* jammy/linux-oem-5.17: 5.17.0-1027.28 -proposed tracker (LP:
#2003451)
* CVE-2022-3545
- nfp: fix use-after-free in area_cache_get()
*
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux - 5.15.0-60.66
---
linux (5.15.0-60.66) jammy; urgency=medium
* jammy/linux: 5.15.0-60.66 -proposed tracker (LP: #2003450)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.4.0-139.156
---
linux (5.4.0-139.156) focal; urgency=medium
* focal/linux: 5.4.0-139.156 -proposed tracker (LP: #2003486)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 4.15.0-204.215
---
linux (4.15.0-204.215) bionic; urgency=medium
* bionic/linux: 4.15.0-204.215 -proposed tracker (LP: #2003522)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
This bug was fixed in the package linux - 5.19.0-31.32
---
linux (5.19.0-31.32) kinetic; urgency=medium
* kinetic/linux: 5.19.0-31.32 -proposed tracker (LP: #2003423)
* amdgpu: framebuffer is destroyed and the screen freezes with unsupported IP
blocks (LP: #2003524)
-
This bug was fixed in the package linux-signed - 4.15.0-204.215
---
linux-signed (4.15.0-204.215) bionic; urgency=medium
* Master version: 4.15.0-204.215
* SIGNEDv3: add a linux-generate ancillary package (LP: #1989705)
- [Packaging] add linux-generate* direct ancillary
*
This bug was fixed in the package linux - 4.15.0-204.215
---
linux (4.15.0-204.215) bionic; urgency=medium
* bionic/linux: 4.15.0-204.215 -proposed tracker (LP: #2003522)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
This bug was fixed in the package linux - 5.4.0-139.156
---
linux (5.4.0-139.156) focal; urgency=medium
* focal/linux: 5.4.0-139.156 -proposed tracker (LP: #2003486)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.4.0-139.156
---
linux (5.4.0-139.156) focal; urgency=medium
* focal/linux: 5.4.0-139.156 -proposed tracker (LP: #2003486)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.4.0-139.156
---
linux (5.4.0-139.156) focal; urgency=medium
* focal/linux: 5.4.0-139.156 -proposed tracker (LP: #2003486)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.4.0-139.156
---
linux (5.4.0-139.156) focal; urgency=medium
* focal/linux: 5.4.0-139.156 -proposed tracker (LP: #2003486)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 5.4.0-139.156
---
linux (5.4.0-139.156) focal; urgency=medium
* focal/linux: 5.4.0-139.156 -proposed tracker (LP: #2003486)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
This bug was fixed in the package linux - 4.15.0-204.215
---
linux (4.15.0-204.215) bionic; urgency=medium
* bionic/linux: 4.15.0-204.215 -proposed tracker (LP: #2003522)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
This bug was fixed in the package linux - 5.4.0-139.156
---
linux (5.4.0-139.156) focal; urgency=medium
* focal/linux: 5.4.0-139.156 -proposed tracker (LP: #2003486)
* Revoke & rotate to new signing key (LP: #2002812)
- [Packaging] Revoke and rotate to new signing key
linux
** Changed in: linux-azure (Ubuntu Kinetic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2003353
Title:
Azure: Fix race on per-CQ
Public bug reported:
I'm seeing frequent kernel crashes with my new computer. The crashes
tend to focus on the network device that I'm currently using (both the
built-in WiFi and 2.5G Ethernet). I've attached representative messages.
The most recent crash happened with the integrated GPU. That
Adding sysctl.kernel.watchdog_thresh=60 to the kernel command line
bypasses the problem.
--
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/2006588
Title:
5.19.0-1004.4-generic
FTR this is still happening on 22.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1949075
Title:
[Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not
autoconnecting on
I've updated to the 6.1.0-1004-oem kernel to see if that helped, and it
did not.
Here's the grep:
grep . /sys/class/drm/*/modes
/sys/class/drm/card0-HDMI-A-3/modes:1920x1080
/sys/class/drm/card0-HDMI-A-3/modes:1920x1080
/sys/class/drm/card0-HDMI-A-3/modes:1920x1080
Here is the full syslog from which the portion in the bug description
was extracted from.
** Attachment added: "c5.12xlarge-3-syslog.log"
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/2006620/+attachment/5645600/+files/c5.12xlarge-3-syslog.log
--
You received this bug
Public bug reported:
Hibernation on AWS instances with jammy/5.19.0-1019-aws sometimes fails
due to the following failure to freeze:
Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.247854] PM: hibernation:
hibernation entry
Feb 1 01:09:05 ip-172-31-54-178 kernel: [ 443.347353] TSC found
** Also affects: broadcom-sta (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: broadcom-sta (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-bluefield/5.4.0-1057.63
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' to 'verification-done-focal'. If the
problem still
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware. I recommend
performing a back up and then investigating the situation. Measures you
might take include
1 - 100 of 125 matches
Mail list logo
