To further add: Running my scripts in their entirety with a self
compiled vanilla kernel instead of Ubuntu's kernel, and I have 0 usages
of the overlay module when the script completes. On Ubuntu's kernel the
usage goes up and up and up, and never goes down, even though the
processes that start the
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/2016398
Title:
stacked overlay file system mo
Public bug reported:
Hi
BACKGROUND:
---
I have a set of scripts that debootstraps and builds vanilla Debian installs,
where the only modifications are what packages are installed. Then that becomes
the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and
then that b
This keeps happening in kernel 5.19.0-38-generic. I installed the 4 debs
from the link above
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1972140/comments/13
then with grub I booted the linux-image-
unsigned-5.18.0-4-generic_5.18.0-4.4 kernel. Result: It refuses to load
the athk5 module. Th
Same thing with BIOS 0090 and kernel 5.4.0-135
** Attachment added: "Photo of panic trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664317/+files/BIOS0090_5.4.0-135_20230415_103355.jpg
--
You received this bug notification because you are a member of Kernel
P
Confirmed on 121.
Another thing I realized is that I also updated the BIOS when I upgraded
the RAM. Updated to BE0092. I have no idea what the previous BIOS
version I was using (whatever shipped with the machine initially), but
this one sill seems the most up to date version.
I'll try downgrading
Same thing with 131. So I have no idea what's going on. I upgraded the
RAM in this machine around March 14th, which is why I know that was the
last time I rebooted and I believe I would have noticed a panic.
I also confirm it seems all reboots result in the same panic (e.g. "sudo
reboot" and also
hmm. The issue persists going back to 5.4.0-135 also...
Trying 5.4.0-131 next, but if that it's still happening the issue may be
else ware?
I don't reboot or shutdown this machine very often, the last time I can
confirm I shut down without a panic was around March 14th.
** Attachment added: "5.4
Figured out what made that one node different from the rest: its UEFI network
boot stack had both PXE and HTTP enabled, while the others were PXE only.
After i added the kernel boot parameters, MAAS started to truncate the HTTP URI
by a few characters (and now keeps doing that even if the kernel
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/2016388
Title:
Kernel Panic on powerdown on N
Photo of console showing panic trace using 5.4.0-144
** Attachment added: "Photo of panic trace"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+attachment/5664275/+files/5.4.0-144_20230415_091831.jpg
--
You received this bug notification because you are a member of Kernel
Pack
This issue seems to persist falling back to kernel 5.4.0-144
--
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/2016388
Title:
Kernel Panic on powerdown on NUC8I3BEH1
Status in linux packag
Public bug reported:
Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-146-generic 5.4.0-146.163
ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229
Uname: Linux 5.4.0-144-generic x86_64
ApportVersion: 2.20.
@Koba :
Important information :
lsb_release -rd
Description:Ubuntu 22.04.2 LTS
Release:22.04
Completely new installation of Ubuntu 22.04.02 (HDD deleted).
After installation and update all, installed 5.19.9000-37-generic, to have
audio via HDMI. also installed synaptic and SSH, no fu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/2016374
Title:
package nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1 fai
Public bug reported:
Installation stalled and didn't complete.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-common-470 470.182.03-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
ApportVersion: 2.20
Still a problem on _random_ supermicro hardware: i have 15 identical
nodes, set kernel parameters for `console=ttyS0 console=tty0` and now
_one_ node will not commission or therefore provision with this error.
Maas (snap) is at 3.2.7-12037-g.c688dd446
The maas UI doesn't update the parameters pass
Public bug reported:
Since about a month or so, I get many oopses from apparmor, such as this
one:
[ 14.620816] BUG: kernel NULL pointer dereference, address: 0130
[ 14.620822] #PF: supervisor read access in kernel mode
[ 14.620825] #PF: error_code(0x) - not-present page
[
This bug is awaiting verification that the linux-
riscv-5.15/5.15.0-1031.35~20.04.1 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
As a workaround you can try the ubuntu upstream kernels. I installed
6.2.11 from here: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v6.2.11/
And sound was working out of the box again (kinda, I still had to open
alasmixer and set to Headphones instead of Speakers).
--
You received this bug no
20 matches
Mail list logo
