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/1990716
Title:
No sound after Kernel upgrade
How to close this bug report?
--
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/1981809
Title:
DELL XPS 7590 with Ubuntu 22.04 LTS won't go into suspend mode
Status in linux package in Ubu
Not sure exactly what I did, but managed to restore Nvidia drivers,
restart the system, and after a while the system will go into suspend
mode, maybe through updates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
Public bug reported:
In Ubuntu 22.04 LTS Software & Updates I had the 'Pre-released updates
(jammy-proposed) checkbox checked. An 'important' software update was
installed and immediately thereafter, during boot sequence the PC is
hanging at the splash screen with the mainboard logo displayed. Onl
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1018.21 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
[Expired for linux-oem-5.17 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-oem-5.17 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
ht
[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.
https://bugs.launchpad.net/bu
** Tags added: verification-done-jammy
--
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/1981390
Title:
Mass Storage Gadget driver truncates device >2TB
Status in linux package in Ubuntu:
All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1021.21) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.1-1ubuntu0.22.04.1 (arm64, amd64)
Please visit the excuses page listed below and investigat
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1018.21 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
Was audio working previously on this hardware and then stopped after a
kernel (or other package) update? If so, we can try bisecting.
Note also that the 5.15.0-41.44 kernel has been out for a while now. The
most recent kernel is 5.15.0-48.54 so maybe that is worth trying as
well.
--
You received
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1076.73) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
sl-modem/2.9.11~20110321-16ubuntu1 (amd64)
evdi/1.9.1-1ubuntu4~20.04.2 (amd64)
v4l2loopback/0.12.3-1ubuntu0.4 (am
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 1990700
and then change the status of the bug to 'Confirmed'.
If, due to the nature
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1092.89) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
v4l2loopback/0.12.3-1ubuntu0.4 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64)
systemd/245.4-4ubuntu3.18 (
Public bug reported:
Hi,
I found a "little" problem with Fibocom WWAN FM350-GL 5G modem in module
mtk_t7xx . Power management for this modem is bad. When the notebook goes to
sleep/suspend, kernel module mtk_t7xx return an error:
mtk_t7xx :58:00.0: [PM] SAP suspend error: -110
mtk_t7xx 000
All autopkgtests for the newly accepted linux-meta-ibm-5.4 (5.4.0.1034.48) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/237-3ubuntu10.56 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-meta-ibm (5.4.0.1034.63) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.18 (amd64)
Please visit the excuses page listed below and investigate the failures,
pro
Model Name: ASUS ZenBook13 UX325J
BIOS Version: 311
CPU: Intel Core(TM) i7-10 65G7 CPU @ 1.30GHz
GPU: Intel Iris(R) Plus Graphics
OS: Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-48-generic x86_64) / Windows 11
I made 'sudo apt-get dist-upgrade' on 22-Sep-2022, followed by I lost an access
to Ubuntu GUI.
** Description changed:
-
- 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 originat
On using linux-oem-5.17 kernel, no sound yet. But I got the following
log in dmesg related to Cirrus driver, I assume.
[ 11.845962] cs35l41_hda: probe of spi0-CSC3551:00-cs35l41-hda.0 failed with
error -22
[ 11.846034] cs35l41_hda: probe of spi0-CSC3551:00-cs35l41-hda.1 failed with
error -22
All autopkgtests for the newly accepted linux-meta-azure-5.4 (5.4.0.1092.69)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64)
v4l2loopback/0.10.0-1ubunt
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 1990697
and then change the status of the bug to 'Confirmed'.
If, due to the nature
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:
I'm seeing this 2-3 times per week. My system is configured with "Linux
Suspend" in the BIOS (not the Windows/Modern setting). Furthermore,
when plugged in, my system does not sleep.
When I come up to my laptop after inactivity, the screens are dark (but
as noted above, it
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Cengiz Can (cengizcan)
** Changed in: linux (Ubuntu)
Assignee: Cengiz Can (cengizcan) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Public bug reported:
[Impact]
One of the fixing commits for CVE-2021-33655, commit 159a96b199b4
("fbcon: Prevent that screen size is smaller than font size") introduced
a redundant lock_fb_info line into the ioctl flow in fbmem.c.
This line only exists in bionic tree.
Users belonging to video g
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1047.46)
for focal have finished running.
The following regressions have been reported in tests triggered by the package:
mali-midgard/unknown (arm64)
lxc/unknown (arm64)
openrazer/unknown (arm64)
nat-rtsp/unknown (arm64)
langfor
On Fri, Sep 23, 2022 at 11:15 AM Kellen Renshaw
<1970...@bugs.launchpad.net> wrote:
>
> I have put up a draft SRU exception page at
> https://wiki.ubuntu.com/MakedumpfileUpdates. Comments/edits are welcome.
> I am working on finding an appropriate place for test vmcores to be
> stored.
Awesome! Th
This bug is awaiting verification that the linux-azure/5.4.0-1092.97
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 exists, c
This bug is awaiting verification that the linux-azure/5.4.0-1092.97
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 exists, c
I have put up a draft SRU exception page at
https://wiki.ubuntu.com/MakedumpfileUpdates. Comments/edits are welcome.
I am working on finding an appropriate place for test vmcores to be
stored.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1018.21 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-xilinx-
zynqmp/5.4.0-1018.21 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
** Tags added: verification-done-jammy
--
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/1987670
Title:
Add support for AMD PMF
Status in HWE Next:
New
Status in linux package in Ubuntu:
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1018.21 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-xilinx-
zynqmp/5.4.0-1018.21 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
The problem was (partly) solved.
After asking for help in the linux kernel development mailing list Niklas
Cassel (one of the developers) wrote:
- The commit 1527f69204fe ("ata: ahci: Add Green Sardine vendor ID as
board_ahci_mobile") added the - PCI vendor and device id to the list of
supporte
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1004.4
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1004.4
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1004.4
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-bluefield/5.4.0-1047.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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-bluefield/5.4.0-1047.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-focal' to 'verification-done-focal'. If the
problem still exist
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
Model Name: ASUS ZenBook13 UX325J
BIOS Version: 311
CPU: Intel Core(TM) i7-10 65G7 CPU @ 1.30GHz
GPU: Intel Iris(R) Plus Graphics
OS: Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-48-generic x86_64) / Windows 11
I made 'sudo apt-get dist-upgrade' on 22-Sep-2022, followed by I lost an access
to Ubuntu GUI.
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/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' to 'verification-done-jammy'. If the
problem still exists,
Following this:
https://askubuntu.com/questions/1264859/watchdog-bug-soft-lockup-cpu6-stuck-for-23s
I attempted a BIOS update and verifying my swap was working properly. Also
reseated my GPU and still no luck.
--
You received this bug notification because you are a member of Kernel
Packages, wh
Present in 5.15.0-50-lowlatency . Continues the trend where tainted in
the Generic version of the kernel, but not the lowlatency version.
9/22/22 1:41 PM kernel
9/22/22 1:41 PM kernel UBSAN: array-index-out-of-boun
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1021.20) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
digimend-dkms/10-4 (amd64, arm64)
lttng-modules/2.13.1-1ubuntu0.22.04.1 (amd64, arm64)
Please visit the excu
This bug is awaiting verification that the linux-azure/5.15.0-1021.26
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.15.0-1021.26
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' to 'verification-done-jammy'. If the
problem still exists,
** Tags added: originate-from-1976477 sutton
--
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/1988797
Title:
pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
Fa
I have added a tcpdump to the github issue, if anybody wants to have a
look.
--
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/1989470
Title:
BGP adjacency not established on linux-imag
** Package changed: ubuntu => linux-hwe-5.15 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1990587
Title:
13.3GB reserved by kernel sometimes on clean boot
Status in
You have been subscribed to a public bug:
Description:Ubuntu 22.04.1 LTS
Release:22.04
Kernel: linux-image-5.15.0-48-generic
Occasionally (twice today) a clean boot has left only 2GB of 16GB RAM usable.
Looking at syslog - its clear the memory is being reserved for some reason by
the
67 matches
Mail list logo
