This bug was fixed in the package alsa-lib - 1.2.4-1.1ubuntu4
---
alsa-lib (1.2.4-1.1ubuntu4) jammy; urgency=medium
* d/p/0001-ucm-fix-regexec-REG_NOMATCH-state-handling-for-defin.patch
- ucm: Fix a Regex parser bug, when there is no match, need to
set err to 0, otherwise,
** Changed in: linux (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1920674
Title:
AMD A8-7680 (amdgpu): broken Xor
Public bug reported:
[Description]
Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade to kernel
5.11.0-1022.23-raspi
[Steps to reproduce]
1. Flash image (see additional information)
2. Boot into system
3. apt dist-upgrade all packages and reboot
4. Enable proposed repository
5. Up
** Tags added: kernel-bug kernel-therm
** Tags removed: kernel-bug
--
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/1947614
Title:
Laptop fans spin at ~50% w/o CPU load with kernel 5.13
To check the theory about the Ubuntu-specific patches, I tried to boot
another Linux distro (Fedora Live 35) in order to see if the problem
would exist: it did not.
The kernel used was: 5.14.10-300.fc35.x86_64.
Which is more recent that the kernel 5.13.0-20, currently used by Ubuntu
21.10. Theref
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/1950062
Title:
Unable to access CPU i2c inter
Results of i2cdetect showing i2c-0 to i2c-2 are the pixx4 interfaces
from the CPU:
i2cdetect -l
i2c-3 i2c AMDGPU DM i2c hw bus 0 I2C adapter
i2c-1 smbus SMBus PIIX4 adapter port 2 at ff00 SMBus adapter
i2c-6 i2c AMDGPU DM i2c hw bus 3
Public bug reported:
OpenRGB uses the CPU SMBus/i2c interfaces to talk to the motherboard RGB
controller and the DRAM RGB controllers and after updating my system to
a 5700G from a 2400G I see error messages in dmesg for each read and
write attempt to the interfaces. If I swap the CPU back on the
** Description changed:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.
+
+ Warning: 32bit iso on sourceforge for boot-repair-disk
** Description changed:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.
Symptoms:
* BIOS settings cannot be saved
* USB B
This seems to be NVIDIA related (I'm using nvidia-driver-470).
Downgrading the libnvidia-egl-wayland1 package to the version used in
impish fixes the issue; hence it's a 1.1.9 regression.
Setting GDK_BACKEND=x11, as mentioned in the upstream issue, works
around the problem.
** Bug watch added: g
Given that the problem exist with kernel 5.13.0-19 and newer but not
with kernel 5.11.0-37, I tried to find which the change triggered this
weird behavior using git bisect. I used bisect in the range [v5.11,
v5.13] (official tags) and I've built the standard non-ubuntu kernel(s)
using:
make -j
> I believe we can close this bug.
The change to the wiki is welcome, since it now reflects the current
situation.
However, in my opinion, the real problem uncovered here has not been
addressed:
Ubuntu should provide mainline kernels built with the latest LTS
toolchain alongside the current one
Public bug reported:
OS: Ubuntu 21.10
Package: pi-bluetooth 0.1.15ubuntu2 arm64
Affected HW: Raspberry Pi 4B
Here's my problem:
bthelper unit fails to start
# systemctl status bthelper@hci0.service
× bthelper@hci0.service - Raspberry Pi bluetooth helper
Loaded: loaded (/lib/systemd/system/b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-firmware (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.
https://bugs.launchpad.
This bug was fixed in the package bluez - 5.62-0ubuntu1
---
bluez (5.62-0ubuntu1) jammy; urgency=medium
* New upstream release 5.62 (LP: #1941708):
- Fix issue with handling truncation when loading LTKs.
- Fix issue with accepting Exchange MTU on EATT bearer.
- Fix issue
This bug was fixed in the package bluez - 5.62-0ubuntu1
---
bluez (5.62-0ubuntu1) jammy; urgency=medium
* New upstream release 5.62 (LP: #1941708):
- Fix issue with handling truncation when loading LTKs.
- Fix issue with accepting Exchange MTU on EATT bearer.
- Fix issue
On my affected machine I tested a live iso of EndeavourOS (latest
release) with kernel 5.13+ and I observed no freezes. So the problem
looks specific to Ubuntu on my laptop (Dell Latitude 7390).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
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 1950046
and then change the status of the bug to 'Confirmed'.
If, due to the nature
I have observed that if I choose to boot in recovery mode from GRUB menu
and then select to resume boot, the system does not freeze. Of course,
in that case the graphics drivers are not loaded properly so it's
probably not a particularly viable workaround.
--
You received this bug notification be
Example 2:
Nov 06 15:34:38 kernel: [ cut here ]
Nov 06 15:34:38 kernel: NETDEV WATCHDOG: eno1 (tg3): transmit queue
0 timed out
Nov 06 15:34:38 kernel: WARNING: CPU: 1 PID: 0 at
net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260
Nov 06 15:34:38 kernel: Modules linked
Public bug reported:
Hi,
since earlier this year (sorry, I don't have an exact date) I started to
encounter regular network hangs on multiple HPE servers that I manage.
The hangs occur on high network load and are followed by a message like
"tg3 :02:00.0 eno1: transmit timed out, resetting".
Example 1:
Nov 04 17:34:59 kernel: [ cut here ]
Nov 04 17:34:59 kernel: NETDEV WATCHDOG: eno1 (tg3): transmit queue
0 timed out
Nov 04 17:34:59 kernel: WARNING: CPU: 3 PID: 0 at
net/sched/sch_generic.c:467 dev_watchdog+0x24f/0x260
Nov 04 17:34:59 kernel: Modules linked
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 1950042
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Impact]
NVMe with HMB may still do DMA during suspend, so there was a commit
that put the NVMe to PCI D3 during suspend to prevent DMA activities.
However, this makes them consumes much more power because modern NVMe
requires to stay at PCI D0 to make its natve power control w
To be clear, the last dmesg is from after I rebooted the "frozen"
computer (which wouldn't respond to Control-Alt-F1/F8/etc or any other
keys). Since it shows kernel version, etc.
I pushed some keys, the backlight came on like it was going to boot, and
then it just stopped there. But I think the p
NOPE, NEVERMIND. The issue is still happening. I thought I did a full
reboot, with [deep], and came back. But I just came back after an hour
or two and the BACKLIGHT turned on, but it still wouldn't come back from
suspend.
This seems like it attempted to come back online:
$ journalctl -o short-pr
** Description changed:
I have an HP Pavilion 15-eh0050wm laptop running Kubuntu 21.10 and when
I wake it up from sleep, the screen flashes rainbow colours, and the
laptop freezes. It doesn't matter if I suspend it with 'systemctl
suspend', close the lid or through the desktop. The problem
Okay, so I added to my GRUB kernel parameters string:
acpi_sleep=s3_bios,s3_mode
per here:
- http://powersave.sourceforge.net/powersave/Suspend2Ram.html
- https://wiki.ubuntu.com/Kernel/KernelBootParameters
and ran GRUB config. And set myself back to:
echo deep | sudo tee /sys/power/mem_sleep
I JUST got the "you have a new version available" and clicked update
last night. From ~21.xx to 21.10 and it won't come back from deep sleep.
Acer C740P laptop with Ubuntu desktop.
Switching to:
echo shallow | sudo tee /sys/power/mem_sleep
from the previous comment allows me to come back. Howev
I have the same problem on Hirsute Hippo. I am on a Lenovo Yoga 730,
connecting to a Coms projector from usb-c through a lenovo usb-c to hdmi
adapter that was included with the laptop.
I have had no trouble before connecting from the same laptop through the
included usb-c to VGA adapter.
I canno
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/1950036
Title:
cant adjust brightness
Status
Public bug reported:
cant adjust brightness and not that stable when i try to fix it
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-20-generic 5.13.0-20.20
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20
33 matches
Mail list logo
