** Tags added: kernel-fixed-upstream kernel-net
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039755
Title:
kernel crashes in CIFS code
Status in linux-signed-hwe-6.2 p
** Tags added: kernel-fs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2047042
Title:
BUG: kernel NULL pointer dereference, address: 0008
Status in linux-sig
Have you tried a newer kernel release to see if the same thing occurs?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2041851
Title:
mount of compressed erofs shows corrup
** Tags added: uec-images
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2046059
Title:
kernel cannot find lz4hc and z3fold modules on boot
Status in cloud-images:
New
Syslog shows a bunch of these repeated with the -40 kernel:
kernel: [ 21.617137] nvidia: disagrees about version of symbol sme_me_mask
kernel: [ 21.617149] nvidia: Unknown symbol sme_me_mask (err -22)
kernel: [ 21.617213] nvidia: disagrees about version of symbol
acpi_walk_namespace
kernel:
Public bug reported:
My system updated from linux-image-6.8.0-38-generic to linux-
image-6.8.0-40-generic and now the graphics do not work at all. I get a
completely black screen and don't know how to proceed.
-38 still works fine (I'm using it now).
I will do the usual upstream checks, if possi
Public bug reported:
I switched to the 550-open driver to test this out but the module fails
to load with secureboot enabled. The key is rejected.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nvidia-kernel-source-550-open 550.67-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic
Works fine on Debian Bookworm on GCP too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2046059
Title:
kernel cannot find lz4hc and z3fold modules on boot
Status in clou
** Changed in: linux (Ubuntu)
Status: Confirmed => New
** Project changed: ubuntu-ubuntu-server => 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/1626838
Title:
yakkety co
** Tags added: trusty
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/1727861
Title:
kernel BUG at /build/linux-hwe-IJy1zi/linux-
hwe-4.10.0/fs/cachefiles/namei.c:164!
Status
I've started seeing this for the Virtualbox modules. Could just be a
coincidence but thought I'd mention it.
** Tags added: jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bug
** Project changed: subiquity => ubuntu
** Package changed: ubuntu => linux-meta-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2051418
Title:
Error in rem
Noble on LXD works correctly too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2046059
Title:
kernel cannot find lz4hc and z3fold modules on boot
Status in cloud-images
I tried again in Qemu with 16.04, 20.04, 22.04 and 24.04 and none of
them see this issue.
So I tried with Jammy on LXD and the issue does present itself. So the
issue appears to be with the UEC images.
I also tried Mantic on LXD and it works fine. So something has been
fixed between Jammy and Man
I tried again in Qemu with 16.04, 20.04, 22.04 and 24.04 and none of
them see this issue.
So I tried with Jammy on LXD and the issue does present itself. So the
issue appears to be with the UEC images.
I also tried Mantic on LXD and it works fine. So something has been
fixed between Jammy and Man
New kernel, no change.
** Description changed:
I've been using zswap without any issues for a while, but fairly
recently (can't be certain when) the kernel became unable to find the
modules for lz4hc compression and the z3fold zpool.
- $ sudo dmesg | grep -E 'z3fold|lz4hc'
- [0.0
So I ran multiple btrfs scrubs and they all reported no error, but for
some reason my system now works. I still have the incorrect extent
counts but there's no lock-ups. Additional scrubs find nothing wrong.
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
Yet again my BTRFS root filesystem has failed. There is nothing wrong
with my hardware - it's been tested over and over.
I can boot fine (the gods know what damage is done when I do) but
processes eventually succumb to disk-wait and the whole system ends up
frozen. Trying to
oot. The segfault in GpuWatchdog
appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0
ip 7efc77192336 sp 7efc6b9fd370 error 6 in
libcef.so[7efc72cef000+776f000] likely on CPU
Please provide the dmesg log.
You may have better luck with the r8169 binary package.
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in U
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2036287
Title:
6.2.0-32 kernel doesn'
Which older kernels?
Also see https://wiki.ubuntu.com/Kernel/Bugs
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.
Have you tried the upstream kernel?
Also see https://wiki.ubuntu.com/Kernel/Bugs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039755
Title:
kernel crashes in CIFS code
What the hell is this supposed to be?
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: New => Invalid
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Assignee: AshimShaheer (ashimsha) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages,
ec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0
ip 7efc77192336 sp 7efc6b9fd370 error 6 in
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d
cf 00 79 09 48
** Summary changed:
- lernel crashes in CIFS code
+ kernel crashes in CIFS code
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2039755
Title:
kernel crashes in CIFS code
** Description changed:
- I've been using zswap without any issues for a while, but on upgrading
- from 18.04 to 22.04 (via 20.04) the kernel starting failing to find the
+ I've been using zswap without any issues for a while, but fairly
+ recently (can't be certain when) the kernel became unable
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2036271
Title:
Ubuntu 22.04.3 fails to
Public bug reported:
I've been using zswap without any issues for a while, but on upgrading
from 18.04 to 22.04 (via 20.04) the kernel starting failing to find the
modules for lz4hc compression and the z3fold zpool.
$ sudo dmesg | grep -E 'z3fold|lz4hc'
[0.00] Command line: BOOT_IMAGE=/bo
this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0
ip 7efc77192336 sp 7efc6b9fd370 error 6 in
libcef.so[7efc72cef000+776f000] likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 d
** Changed in: linux-signed-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2043136
Title:
Bluetooth prpblem
Status in li
e a reboot. The segfault in GpuWatchdog appears
immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0
ip 7efc77192336 sp 7efc6b9fd370 error 6 in
libcef.so[7efc72cef000+776f0
em becomes unresponsive. I can access the
machine over SSH and force a reboot. The segfault in GpuWatchdog
appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0
ip 7efc7
access the
machine over SSH and force a reboot. The segfault in GpuWatchdog
appears immediately on logging back in.
For me, this first appears to have occured on Dec 2.
Dec 2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0
ip 7efc77192336 sp 7efc6b9fd370 e
2 22:49:52 ken kernel: [191969.402923] GpuWatchdog[9387]: segfault at 0 ip
7efc77192336 sp 7efc6b9fd370 error 6 in libcef.so[7efc72cef000+776f000]
likely on CPU 3 (core 3, socket 0)
Dec 2 22:49:52 ken kernel: [191969.402960] Code: 89 de e8 3d ef 6e ff 80 7d cf
00 79 09 48 8b 7d b8 e8 b
** Package changed: syslog-ng (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/1903203
Title:
System becomes un-responsive due to gpu segfault
Status in linux p
Are you still having this issue?
** Tags added: amd64 bionic
--
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/1861294
Title:
Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7
rnelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ken8889 F pulseaudio
/dev/snd/controlC1: ken8889 F pulseaudio
/de
** Package changed: linux (Ubuntu) => firefox (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/2027667
Title:
Certain website floods syslog
Status in firefox package in Ubuntu:
Happens with 5.19.0-38-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/2009271
Title:
Too many BDL entries regression
Status in linux package in Ubuntu:
Confirmed
Status in li
I can confirm that 5.19.0-21-generic in kinetic-proposed does indeed fix
this issue for me.
--
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/1991691
Title:
cannot change mount namespace
S
Public bug reported:
Upon boot up the CD-ROM tray opens and closes. This happens on 5.4.0-86
and 5.4.0-84. Went back to 5.4.0-81 and things are normal.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ke
I've discovered that this behavior can also occur with the installer
(similar to bug 1900130) when the USB stick to which the installer ISO
was written is bad. (In this case, the error message is saying exactly
what it should be saying.)
--
You received this bug notification because you are a me
I started running a bisect but it takes hours for one step. It's not a
realistic option.
Adding snd_hda_intel to /etc/modules doesn't work, so a crappy workaround is to
add
@reboot /sbin/modprobe snd_hda_intel
to root's crontab, until I can be bothered to come back to this, but I just
don't have
Tested 5.12.0-051200rc4-generic and the problem still occurs.
Could this be an issue in another package? Would udev be involved?
Otherwise the next step is for me to file upstream.
** Tags added: kernel-bug-exists-upstream kernel-sound-hdmi
--
You received this bug notification because you are
Tested the mainline kernel 4.15.18-041518-generic and the problem still
occurs.
** Summary changed:
- AMD Trinity HDMI Audio Controller: no sound
+ AMD A4-5300: no sound
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Public bug reported:
Starting with linux-4.15.0-137-generic, there is no sound at all on a
system with an AMD A4-5300.
>From a working kernel:
Mar 22 05:00:29 richie kernel: [ 33.029621] snd_hda_intel :00:01.1: Force
to non-snoop mode
[...]
Mar 22 05:00:29 richie kernel: [ 33.589291] in
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1917245
Title:
HP and Canon support ubuntu LTS linux systems
Status in l
What makes you think that this is a Linux bug? Did you bother reporting
this to Steam?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
What makes you think that this is a Linux bug? Did you bother reporting
this to Steam?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
What debugging have you done to determine that this is a Linux bug,
because I very much doubt it is?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
htt
** Tags added: bionic focal regression-update
--
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/1920660
Title:
Missing Commit for 5.4-Kernel breaks xen Dom0
Status in linux package in Ubu
.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times:
[ src/main.c:parse_controller_config() Key file does not have group
Public bug reported:
dpkg: error processing package bcmwl-kernel-source (--configure):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 10
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu
You need to provide /var/lib/dkms/nvidia/390.141/build/make.log
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
ht
properly.
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09
Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken
s properly.
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 2
s properly.
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09
untu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
le MacBookPro 2,1 with kernel
5.8.0-31-generic works properly.
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_conf
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09
ing Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09
untu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
untu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09
ing Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
ing Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
booting Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09
u 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
ing Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
u 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
u 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-macbookpro21
ing Ubuntu 20.10 on Apple MacBookPro 2,1 with kernel
5.8.0-33-generic crashes with error indicating low memory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-ma
corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times:
[ src/main.c:parse_controller_config() Key file does not
ory corruption.
Release: 20.10
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]:
src/main.c:parse_controller_config() Key file does not have group “Controller”
Dec 20 09:08:36 ken-macbookpro21 bluetoothd[739]: message repeated 27 times:
[ src/main.c:parse_controller_config() Key file does
I am also affected by this bug, but I'm missing at least two firmware
files, not just one. I'm missing rtl8168fp-3.fw and rtl8125a-3.fw, I had
to download those two files manually
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmw
"Fix:
sudo apt install -y --reinstall gcc g++ gcc-7 g++-7"
How on Earth is that a fix? Does an updated package do this for you? I'm
doubting it very much.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubun
I've also seen this with kernel 5.3.0-40-generic (Default with 19.10 and
18.04.04 LTS). Lenovo X1 with Intel i7-10710u and AC 9560
[2.861512] iwlwifi :00:14.3: enabling device ( -> 0002)
[2.886678] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
43.2.23.17
[2.886992]
23.25
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ken1252 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date
All good here too with 390.116-0ubuntu0.18.04.3
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1851162
Title:
nvidia-drivers-390 fail to build with kernel 5.3
Stat
Updated Bionic with all the latest packages before adding -proposed.
Building module:
cleaning build area...
unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES=''
KERNEL_UNAME=5.3.0-26-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1
SYSSRC=/lib/modules/5.3.0-26-generic/build LD
Probably the same as Bug #1851162
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1843385
Title:
package nvidia-dkms-390 (not installed) failed to install/upgrade:
*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162
** This bug has been marked a duplicate of bug 1851162
nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
--
You received this bug notification because you are a member of Kernel
Packag
Did you build a custom kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1846995
Title:
package nvidia-dkms-390 390.129-0ubuntu1 failed to install/upgrade:
i
*** This bug is a duplicate of bug 1851162 ***
https://bugs.launchpad.net/bugs/1851162
** This bug has been marked a duplicate of bug 1851162
nvidia-drivers-390 fail to build with DKMS and linux-image-5.3.0-19
--
You received this bug notification because you are a member of Kernel
Packag
Or don't.
https://discourse.ubuntu.com/t/intel-32bit-packages-on-ubuntu-from-19-10-onwards/11263/90
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-g
The HWE package now force-upgrades to 5.3.0, rendering that entire
package useless.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1851162
Title:
nvidia-drivers-390
Nilesh's fix worked for me thanks ... Ubuntu 16.04 Dell Inspiron 15 3000
series kernel 4.15.0-72-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/1854798
Title:
Synaptics s3203 tou
PID ACCESS COMMAND
/dev/snd/controlC0: ken1252 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 3 01:09:07 2019
InstallationDate: Installed on 2019-04-27 (219 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Machine
5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ken1252 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 3 01:09:07 2019
InstallationDate: Installed on 2019-04
5.3.0-23.25
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ken1252 F pulseaudio
CurrentDesktop
Public bug reported:
With linux-image-5.0.0-23 I had no problems. Following an update linux-
image-5.3.0-19 was installed, the DKMS build failed, and the system
became unusable.
Removing 5.3.0 brings the system back.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-driver-390 390.116
Build log attached.
** Attachment added: "DKMS build log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1851162/+attachment/5302550/+files/make.log
** Description changed:
- With linux-image-5.0.0-23 I had no problems. Following an update 5.3.0
- was installed, t
I've marked this as affecting me but I've just realised that I'm using a
different kernel. In my case 5.0.x works fine, 5.3.0 fails in
(apparently) the same way:
DKMS make.log for nvidia-390.116 for kernel 5.3.0-19-generic (x86_64)
Sun 3 Nov 19:50:42 GMT 2019
make[1]: Entering directory '/usr/src
fixed links
User on lingon on raspberry pi forum posted the following:
The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the
issue seen earlier that using more RAM than 3072 MB breaks the USB:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=25[/u
Fixed links
User on lingon on raspberry pi forum posted the following:
The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the
issue seen earlier that using more RAM than 3072 MB breaks the USB:
[url]https://www.raspberrypi.org/forums/viewtopic.php?f=63&t=246766&start=25[/u
fixed links
User on lingon on raspberry pi forum posted the following:
The USB-problem concerning the Raspberry Pi 4GB RAM model might be due to the
issue seen earlier that using more RAM than 3072 MB breaks the USB:
https://www.raspberrypi.org/forums/v...46766&start=25
The issue was solved by
1 - 100 of 311 matches
Mail list logo
