Public bug reported:
Hello, I can not umount a cifs share with umount /media/share.
I alwas have to use umount -f -l /media/share.
We have round about 260 installations with Automatic software
distribution which need to unmount the share or it get stuck.
ProblemType: Bug
DistroRelease: Ubuntu
*** This bug is a duplicate of bug 2009136 ***
https://bugs.launchpad.net/bugs/2009136
** This bug has been marked a duplicate of bug 2009136
No HDMI audio under 5.19.0-35 (regression from -32)
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
After the recent update to the 5.19.35 kernel (installed on 4th March
2023), the HDMI audio (out) of my AMD RX6700 XT doesn't work anymore. I
don't see any devices in Gnome or when listing the devices with `aplay
-a`
In the ACPI error message on startup I see:
kernel:
Public bug reported:
I'm exporting a logical volume via nbd-server to a raspberry pi which
uses the nbd device as a physical volume for its own LVM stack. Some
operations such as running mkfs.ext2 on a logical volume inside the
raspberry pi crash the exporting server. I have seen various messages
Seems like this issue was caused by nvidia driver remainders, which
caused an instant wake-up after suspend or hibernate.
** Changed in: linux-oem-6.0 (Ubuntu)
Status: New => Incomplete
** Changed in: linux-oem-6.0 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
It seems like there is no more force-probe required for oem-6.1, works
fine out-of-the-box now.
When is the 22.2 mesa from ppa:canonical-x/x-staging going to be
released, currently using the linux-oem-6.1 kernel together with the
23.0 mesa from the Intel Arc package sources.
--
You received
Is this not going to happen?
> kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
--
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/1971712
Title:
Add support for Intel
The new firmware package works fine with the 6.0 kernel, it loads the GuC and
HuC Firmware, as seen below:
[4.691687] i915 :03:00.0: [drm] Finished loading DMC firmware
i915/dg2_dmc_ver2_06.bin (v2.6)
[4.702309] i915 :03:00.0: [drm] GuC firmware i915/dg2_guc_70.1.2.bin
version
Private bug reported:
When using the latest Linux 6.0.0-1006-oem Kernel, Firefox and Chromium
won't open anymore.
** Affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: Invalid
** Changed in: linux-oem-6.0 (Ubuntu)
Status: New => Invalid
** Information type
Public bug reported:
The computer is unable to suspend or hibernate, when a DG2 graphics card
is installed and in-use in the system.
When attempting to suspend or hibernate the system will turn off its
screens for a few seconds after which they will light up again.
I am using the latest
Hi Timo,
Upgrading to Mesa 22.2 seems to resolve this issue. Using the packages
from the intel repository (https://dgpu-docs.intel.com/installation-
guides/ubuntu/ubuntu-jammy-arc.html) works as well.
Is it planned to release the updated mesa 22.2 packages to Ubuntu 22.04?
--
You received this
I've managed to reproduce this bug on an Arc A380 and Arc A770 GPU. I've
attached the requested lspci output for the A770.
Ubuntu 22.04 has already received a mesa update with backported patches
for DG2 support:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1971712
I haven't tried 22.10
Looking forward to linux-oem-6.0 support. Got an A380 and A770 here for
testing purposes.
It seems like the current proposed build of the linux-oem-6.0 kernel
still has some issues in this regard.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
When using GNOME Shell with Wayland, all application windows become
invisible from time to time. This usually happens right after starting
GNOME Shell for the first time or after having a VRAM intensive
application open, such as a game.
I have installed the latest
Public bug reported:
DG2 graphics support should be enabled by default, dmesg outputs the
following:
i915 :67:00.0: Your graphics device 56a5 is not properly supported by the
driver in this
kernel version. To force driver probe anyway, use
i915.force_probe=56a5
Are there any plans for providing an i915 DKMS Module with DG2 Support
for oem-5.17?
--
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/1971712
Title:
Add support for Intel DG2
Public bug reported:
After installing a USB to Serial Adapter on a Raspberry Pi 4 running
Ubuntu Server 22.04 LTS, no tty device is created under /dev/ttyUSB...
dmesg:
[3.793123] usb 1-1.2.1: New USB device found, idVendor=0403,
idProduct=6001, bcdDevice= 6.00
[3.793142] usb 1-1.2.1:
Okay, I updated to the latest kernel 5.13.0-1031-aws and the problem
doesn't seem to be present anymore:
sudo apt update
apt list --upgradable
apt-transport-https/focal-updates 2.0.9 all [upgradable from: 2.0.8]
apt-utils/focal-updates 2.0.9 amd64 [upgradable from: 2.0.8]
apt/focal-updates 2.0.9
I'm currently on a conference so I won't be able to look into this
further until Thursday. I should be able to provide more information by
the end of the week.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
This issue did not exist on Kernels lower than: 5.13.0-1028-aws
5.13.0-1028-aws broke Docker completely and 5.13.0-1029-aws breaks Docker
partially
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws-5.13 in Ubuntu.
Created a new bug report:
https://bugs.launchpad.net/ubuntu/+source/linux-aws-5.13/+bug/1978475
Hopefully @electricdaemon and other affected users can help to provide a
reproducible test.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I can confirm that the problem is indeed not fully fixed.
@electricdaemon said:
> Test kernel posted fixes crash but has another bug with unkillable
stuck defunct docker-proxy service causing more issues. Bug is not
solved. Tested on Linux AWS Lightsail instance.
And that's the problem that I'm
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
ith kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
If i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastia
ith kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
ith kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
0
0
If i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastia
ith kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
ith kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
nel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: X-Cinnamon
DistroRelease: Linux Mint 20.3
InstallationDate: Installed
i boot up with kernel 5.13.0-40 everything works fine.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 4875 F pulseaudio
/dev/snd/controlC0: sebastian 4875 F
.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastian 1568 F
mint 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastia
mint 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastia
If i boot up with kernel 5.13.0-41 i become an
error.
I use Linux mint 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebas
r.
I use Linux mint 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0:
nt 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastian 1568 F
Linux mint 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastia
use Linux mint 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastia
Linux mint 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastia
nt 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastian 1568 F
.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastian 1568 F
nt 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastia
Linux mint 20.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastia
.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastian 1568 F
.3. i have this error with two different computers
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: sebastian 1568 F pulseaudio
/dev/snd/controlC0: sebastian 1568 F
different computers
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27.24
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: sebastian 1568 F pulseaudio
+ /dev/snd/controlC0: sebastian 1568 F pulseaudio
+ CasperMD5CheckResult: skip
Public bug reported:
I mount my nfs share with nfs4 in fstab. When i Boot up with kernel 5.13.0-40,
there is no problem. If i boot up with kernel 5.13.0-41 i become an error.
I use Linux mint 20.3. i have this error with two different computers
** Affects: linux (Ubuntu)
Importance:
Try nvidia.NVreg_PreserveVideoMemoryAllocations=1 as suggested by
@vanvugt
You may wanna change the file path of the temporary file thought for
better performance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I'm using a RTX 3080 Ti on a Z690 Desktop motherboard and enabling the
S0ix option fixed the problem for me.
I've added the following option
"nvidia.NVreg_EnableS0ixPowerManagement=1" to
GRUB_CMDLINE_LINUX_DEFAULT.
--
You received this bug notification because you are a member of Kernel
Eh... so on a fresh 22.04 installation (dell xps 13) my internet connection
drops rougly every minute or so. It all worked fine on 21.04, the wifi hasn't
changed.
This is horrible I have to say not sure if this is the right bug report for
it. Any terminal output I should present?
--
You
Seems fixed in linux-image-5.13.0-39-generic
5.13.0-39.44~20.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958494
Title:
After upgrade to
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Was able to reproduce this bug on two of my machines aswell. Both were
using Nvidia 3000 Series graphics. Booting the 5.15.0-18 Kernel or 5.16
Mainline Kernels didn't have this issue.
Seems like only 5.15.0-22 is affected by this bug.
--
You received this bug notification because you are a
Was able to reproduce this issue on two of my machines aswell. Both were
installed in EFI Mode.
Booting the older 5.15.0-18 kernel or 5.16 mainline kernels work around
this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Today a new linux image was available (update from 5.15.12 to 5.15.19).
After installation the problems with AlderLake/z690 network module IGC
are solved.
```
phoenix@dev:~$ cat /proc/version_signature
Ubuntu 5.15.0-22.22-generic 5.15.19
```
I can now happily reboot and shutdown my box :) Can
** Summary changed:
- Known bug in IGC causes shutdown bug in z690 environments
+ Known bug in IGC kernel module causes shutdown bug in z690 environments
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
When I unload the **igc** module while system is running it triggers a reboot,
just like described here:
-
https://lore.kernel.org/all/924175a188159f4e03bd69908a91e606b574139b.ca...@gmx.de/
The 5.15.12 kernel seems to fix the issue for **igb** kernel module but not for
**igc**. According to
Found this related kernel patch for igb and igc:
- https://bugzilla.kernel.org/show_bug.cgi?id=215129
The post states that for igb kernel module a fix is included in 5.15.12.
I tested with kernel 5.15.12 (Ubuntu 5.15.0-18.18-generic 5.15.12) and
the bug remains in my case using igc kernel
Public bug reported:
Suspend/Resume and don't seem to work with the shipped 5.15 Kernel.
When rebooting or shutting down the system gets stuck at "Reached
Target: System Poweroff" or "Reboot".
Installing the mainline kernel 5.16.11 fixes this issue and the system
is able to properly
Seems like it is fixed in kernel 5.14:
https://gitlab.freedesktop.org/drm/amd/-/issues/1783
Any chance to get the fix backported to 20.04?
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1783
https://gitlab.freedesktop.org/drm/amd/-/issues/1783
--
You received this bug
Public bug reported:
I own a Asus z690 Apex board, and shutdown hangs because of a bug in IGC
driver. I cannot provide any logs because this happens after filesystem
driver has been shut down and display/graphics have been turned of. The
PC simply never turns off.
I can disable the network
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: 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/1960460
Title:
Fails to
Hi Tim,
I can confirm that 5.4.0-99.112 fixes the cifs issue.
Testing in our environment does not show any freezes accessing cifs
shares while using 5.4.0-99.112.
Best Regards,
Sebastian
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Problem can be reproduced with 5.13.0-28.31~20.04.1 as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958494
Title:
After upgrade to
Just a quick heads up on my tests with different kernel versions. I have
installed all available Updates for Ubuntu 20.04 (including samba-*=
2:4.13.17~dfsg-0ubuntu0.21.04.1; CVE-2022-0336). These are the results:
GA:
5.4.0-98.111~lp1959665.1 -> no freezes in 3 hours of testing
5.4.0-97.110 ->
the latest cifs patches from kernel 5.4.0-97.110 seems to fix
our issue.
I will keep testing on 5.4.0-98-generic #111~lp1959665.1.
Best regards,
Sebastian
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Summary changed:
- linux-image-9.4.0-97.110 freezes by accessing cifs shares
+ linux-image-5.4.0-97.110 freezes by accessing cifs shares
** Description changed:
- Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we
+ Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly
Public bug reported:
Ubuntu 20.04 with kernel image 9.4.0-97.110 randomly freezes when we
access cifs shares. The system needs a hard reset after the freeze.
The previous kernel image (5.4.0-96.109) does not show this behavior.
Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110
** Summary changed:
- After upgrade to linux-image-5.13.0-27-generic, screen doesn't recovere from
blanking
+ After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from
blanking
--
You received this bug notification because you are a member of Kernel
Packages, which is
According to my logs in the past few days, these versions have worked
fine:
5.10.0-1045.47-oem
5.11.0-37.41~20.04.2-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
Public bug reported:
After screen was blanked (meta-L; lid closed) it wakes up with an
erratic pattern, it can't recover from (except power off, power on).
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
ProcVersionSignature: Ubuntu
** Attachment added: "IMG_20220120_073821207.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+attachment/771/+files/IMG_20220120_073821207.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 1949790 ***
https://bugs.launchpad.net/bugs/1949790
** This bug has been marked a duplicate of bug 1949790
Thunderbolt 3 NIC driver is loaded too early and won't establish connection
--
You received this bug notification because you are a member of
Public bug reported:
I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T
NIC (atlantic).
The issue is that during boot it only detects the interface as 5 GBe, as seen
in dmesg:
enp11s0: atlantic: link change old 0 new 5000
This prevents the interface from establishing a
Public bug reported:
I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T
NIC (atlantic).
The issue is that during boot it only detects the interface as 5 GBe, as seen
in dmesg:
enp11s0: atlantic: link change old 0 new 5000
This prevents the interface from establishing a
The latest Ubuntu 21.10 install still comes with zfs-kmod-2.0.3, which
prevents the system from booting in the first place.
Installing zfs-dkms via the recovery mode, which updates the zfs-kmod to
version 2.0.6, fixed the issue for me.
I hope that the release image of Ubuntu 21.10 will ship with
5.10.0-1049.51 works for me too, many thanks indeed.
--
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/1930754
Title:
e1000e extremly slow
Status in HWE Next:
New
Status in OEM
I also experienced this bug on Ubuntu 21.10 Beta during boot on a fresh
ZFS Install with Encryption.
The only way to boot into GNOME without crashing was booting through
recovery mode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Have tested the linux-image-5.11.0-33-generic:amd64 5.11.0-33.35 from
proposed and I can verify it fixed the issue for me.
Switched back to the non-proposed 5.11.0-31 kernel and am looking
forward to the new update.
** Tags removed: verification-needed-hirsute
** Tags added:
93A45D1668FCC
vermagic: 5.10.0-1038-oem SMP mod_unload modversions
But it didn't help.
I am currently using the wireless adapter until a find a solution.
Sadly, the only solution provided by technical support was to re-install
Ubuntu, which I will do when I find free time.
Many than
Thanks @Yuan-Chen.
Yes, I did try but it didn't work for me.
--
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/1930754
Title:
e1000e extremly slow
Status in OEM Priority
-04/m-p/7889980
After the "sudo ethtool -C rx-usecs 6000" command I keep seeing
rx_errors and rx_crc_errors with:
sudo ethtool -S | grep -i err
Do you know why?
Many thanks,
Sebastian
--
You received this bug notification because you are a member of Kernel
Packages, which is
Sure thing Chris, here's the dmesg log.
Before I forget: thank you for helping me out here, I really appreciate it.
** Attachment added: "5.11.0-24-generic.dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+attachment/5510164/+files/5.11.0-24-generic.dmesg.txt
--
You
this went horribly wrong, since suspend itself did not work at all ;-)
( freezing of tasks failed after 20.010 seconds )
** Attachment added: "5.13.0-051300-generic.dmesg.txt"
Did you change anything else in this kernel? Because it seemed to work
correctly.
** Attachment added: "5.11.0-24-generic.dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931301/+attachment/5509673/+files/5.11.0-24-generic.dmesg.txt
--
You received this bug notification
Public bug reported:
package linux-image-5.11.0-22-generic 5.11.0-22.23 failed to
install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/53-linux-
image-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht zugegriffen
werden: Datei oder Verzeichnis nicht gefunden
ProblemType: Package
Public bug reported:
package linux-modules-extra-5.11.0-22-generic 5.11.0-22.23 failed to
install/upgrade: Auf das Archiv »/tmp/apt-dpkg-install-NSQLwt/54-linux-
modules-extra-5.11.0-22-generic_5.11.0-22.23_amd64.deb« kann nicht
zugegriffen werden: Datei oder Verzeichnis nicht gefunden
If started a live session with Ubuntu 21.04 and the problem exists also (as
described in "my" bug 1929456).
I run
grep . /sys/class/drm/*/modes > modes.txt
and will attach the output file (renamed).
The workaround (as described in "my" bug 1929456) helped there also.
I wasn't able to follow
** Changed in: linux (Ubuntu Focal)
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/1923670
Title:
CIFS DFS entries not accessible with
Public bug reported:
New to linux. Have no idea why the system crashed.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion:
1 - 100 of 344 matches
Mail list logo
