Public bug reported:
trying to update wireless regdb via sudo apt upgrade
Preparing to unpack .../0-wireless-regdb_2024.07.04-0ubuntu1~24.04.1_all.deb ...
Unpacking wireless-regdb (2024.07.04-0ubuntu1~24.04.1) over
(2022.06.06-0ubuntu2) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-J
Hello Fabio,
Just wanted to check to see if after reproducing the behavior you were
able to identify any temporary fixes, or if any fixes are in the
pipeline.
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
ht
** Description changed:
Description
When SEV-SNP is enabled on Ubuntu 24.04, RSA operations experience a
significant performance degradation (approximately 66% slower) compared
to when SEV-SNP is disabled. This appears to be caused by the loss of
crucial CPU instruction sets when SEV-
.flags;
ap->ops->qc_fill_rtf(qc);
+ qc->flags |= ATA_QCFLAG_RTF_FILLED;
}
static void ata_verify_xfer(struct ata_queued_cmd *qc)
All the best,
Jon Ivar
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-52-generic 6.8.0-52.53
ProcVersionSigna
without a bit of know-how and
remote logging, they might not be able to find neither the culprit nor
the workaround.
Cheers, and thanks for following up on the issue!
Jon Ivar
> 9. feb. 2025 kl. 22:51 skrev Matthew Ruffell <2097...@bugs.launchpad.net>:
>
> Yeah, looks like powe
sible and the system keeps
throwing I/O errors until I force a reboot.
All the best,
Jon Ivar
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-52-generic 6.8.0-52.53
ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
Uname: Linux 6.8.0-52-generic x86_64
ApportVersio
Hello Fabio,
Thank you for the quick response and for confirming the behavior.
You're right - the missing CPU flags (AVX, AVX2, VAES, etc.) when SEV-
SNP is enabled is expected behavior and occurs on both Ubuntu 24.04 and
AL2023. I apologize for the oversight.
I guess we are just puzzled on the
Public bug reported:
Description
When SEV-SNP is enabled on Ubuntu 24.04, RSA operations experience a
significant performance degradation (approximately 66% slower) compared
to when SEV-SNP is disabled. This appears to be caused by the loss of
crucial CPU instruction sets when SEV-SNP is enabled.
I'm also seeing this on linux-image-6.8.0-50-generic package for Ubuntu
24.04, if I downgrade to linux-image-6.8.0-49-generic its fine.
The LUKS prompt shows up and the keyboard works for a split second, then
the display blinks off for a moment (like its changing video modes), and
when it comes ba
Ok gotcha. Perhaps someone from Ubuntu side can help illuminate when
that would be available, I'm not familiar with the release cadence here.
We're certainly open to back-n-forth discussions here if this commit
doesn't fix the issue, or other issues remain, but given what we went
through on other
@Hans - thanks - our messages crossed in flight. I've cross posted the
tags where the fixing commit should live, as well as the bug ID that
brought in the fixing commit. It looks like it was brought in as normal
fit-n-finish backports, so this regression should find it self-solving
(knock on wood!)
Builds with the suspect commit as mentioned above:
jon@C02F13YVQ05N jammy % git tag --contains 34192ba1338f
Ubuntu-5.15.0-125.135
Ubuntu-5.15.0-126.136
Ubuntu-5.15.0-127.137
Ubuntu-lowlatency-5.15.0-125.135
Ubuntu-lowlatency-5.15.0-126.136
Ubuntu-lowlatency-5.15.0-127.137
Builds with what should
Checked out the jammy source
jon@C02F13YVQ05N jammy % git clone
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
jon@C02F13YVQ05N jammy % git checkout Ubuntu-5.15.0-126.136
jon@C02F13YVQ05N jammy % git log --oneline -n 1 HEAD
87cad896a075 (HEAD, tag: Ubuntu-5.15.0-126.136
Hey Jon from Nutanix AHV R&D here - We also see this issue on RHEL,
SLE15, and vanilla kernels. In all three of those cases, the problem
wasn't with AHV, but with a problematic set of backport that was tagged
as a CVE, but caused a GSO-based performance regression. This can be
reproduc
Hey Jon from Nutanix AHV R&D here - We also see this issue on RHEL,
SLE15, and vanilla kernels. In all three of those cases, the problem
wasn't with AHV, but with a problematic set of backport that was tagged
as a CVE, but caused a GSO-based performance regression. This can be
reproduc
Hey! Thank you for the quick turnaround - confirmed that I was able to
start a 22.04 LTS VM on LXD, then install the linux-image and linux-
modules debs and both Cilium and Parca Agent functioned correctly wrt to
the BPF subsystem!
--
You received this bug notification because you are a member of
ling them all didn't prevent the computer
waking up immediately.
Any help greatly appreciated!
Thanks,
Jon
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-14-generic 6.5.0-14.14
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linu
pi/wakeup as in
https://askubuntu.com/questions/598236/ubuntu-wakes-up-after-few-
seconds-of-sleep, but disabling them all didn't prevent the computer
waking up immediately.
Any help greatly appreciated!
Thanks,
Jon
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-14
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease:
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRel
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
Dist
ng-symbolic'
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
Cu
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease:
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
D
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
D
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease:
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop:
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
D
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRel
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRel
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease:
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRel
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease:
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRel
ng-symbolic'
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop:
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
DistroRelease: Lin
#x27;
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jon1403 F wireplumber
/dev/snd/seq:jon1401 F pipewire
CasperMD5json: {
CurrentDesktop: MATE
D
icon-name: 'battery-full-charging-symbolic'
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: jon1403 F wireplumber
+ /dev/snd/seq:jon1401 F pipewire
+ C
Public bug reported:
Description:Linux Mint 21
Release:21 (21.1)
Power Manager 1.26.0 Power management daemon
cat /proc/version_signature > version.log = Ubuntu
5.15.0-83.92-generic 5.15.116
On Thinkpad Yoga 370, with kernel 5.15.0-83-generic, power management
applet (Power Mana
2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jon2489 F pulseaudio
/dev/snd/controlC0: jon2489 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri
this is still an issue in 2023
--
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/1752772
Title:
r8169 ethernet card don't work after returning from suspension
Status in Linux:
New
Status
I'm seeing this as well. Some information that may help. I found the
problem with 5.4.0-137. I found that when looking at tcpdump on the
guest and the bridge I can see ARP requests on both interfaces. On the
guest I can see it responding to the ARP request, however I don't see
the ARP response on t
Same/Related bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996539
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-iotg in Ubuntu.
https://bugs.launchpad.net/bugs/1998588
Title:
package linux-intel-iotg-tools-com
--
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/1996539
Title:
Problem linux-tools-common (5.15.0-52.58)
Status in linux package in Ubuntu:
Incomplete
Bug description:
dpkg: error pr
I've hit this (or a very similar problem) on 2 different digital ocean
droplets running 20.04 LTS . Unfortunately, what I could see of the
console contained only the end of the panic report, but I've transcribed
it by hand below (I have screenshots if the missing numbers are wanted).
The RIP was e
Adding MUTTER_DEBUG_DISABLE_HW_CURSORS=1 to /etc/environment and
rebooting had no effect on the issue. White square "mouse pointer" is
present on gdm login screen if /usr/share/icons/adwaita/cursors is
missing (renamed).
If instead I install a symbolic link .../Adwaita/cursors -> .../Yaru/cursors
The reported problem is during login, not after successful login.
I don't think mutter configuration has any effect before graphical login.
Ubuntu's cursor theme may come from 'yaru-theme-icon', but does gdm's?
Two files affect the observed condition:
/usr/share/icons/Adwaita/cursors/left_ptr
/u
I tried Fedora 35, and found the exact same behaviour (ie the boot
program recognises the keyboard, but the final linux image does not).
Jon Thackray
j...@pobox.com
0044 1223 276500 (home)
0044 7803 017991 (mobile)
0033 423354068 (France)
-- Original Message --
From: "Jon Tha
* log2 (180) hours, ie about 4 hours.
Jon Thackray
j...@pobox.com
0044 1223 276500 (home)
0044 7803 017991 (mobile)
0033 423354068 (France)
-- Original Message --
From: "Daniel van Vugt" <1930...@bugs.launchpad.net>
To: j...@pobox.com
Sent: 22/04/2022 03:00:03
Subject:
time next year, there will be no Ubuntu (or Debian I think,
given that Rapsbian doesn't work with the KVM either) distribution I can
use, as at that point 18.04 will be end of support. I shall then start
having to try and learn other distros to see if any of them have
fixed/failed to create
I'm using Ubuntu 20.04.4 LTS and GNOME 3.36.8
Still having this problem. Very surprised it has lasted this long. In
any case, if it is fixed, will this change make it to the next LTS
update?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Adding dmesg output from computer
** Attachment added: "Output from dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+attachment/5540411/+files/dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubun
I am also adding the output from boltctl, if you need any other info
please advise.
** Attachment added: "Boltctl output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+attachment/5540412/+files/boltctl.txt
--
You received this bug notification because you are a member of Kern
Public bug reported:
I have a Lenovo Thunderbolt 3 Gen 2 dock and wanted to use this with
Ubuntu 21.10. When booting an unmodified version the usb ports do not
work. After an inspection with journalctl I find the error message "No
bus number available for hot-added bridge" and a google search led
Confirmed! Finally. With the latest HWE:
$ apt show linux-image-5.11.0-37-generic
Package: linux-image-5.11.0-37-generic
Version: 5.11.0-37.41~20.04.2
...
No errors or warnings in dmesg or journalctl -b seen on my statem
anymore.
Motherboard: ASUS PRIME X570-PRO (latest BIOS v 4021)
CPU: Ryzen
Confirmed. Just updated and same.
Can you backport the fix to the 20.04 HWE kernel? I mean that's the one
Canonical recommends has as first choice if downloading Ubuntu from
ubuntu.com, for years now. And they've become more stable in my
experience than the ones between LTS versions, which is good
And will that kernel come to the Ubuntu 20.04 LTS HWE stack, say in
20.04.4? Kinda need to use LTS versions, us that need that stability at
least.
Not really interested in fixes for 21.10 or something... Focal.
--
You received this bug notification because you are a member of Kernel
Packages, wh
To be clear this issue started with Kernel 5.8.0-63 NOT 5.11 (on Focal /
20.04 HWE LTS)
Well Ubuntu Kernel Bot, that's exactly what I did in comment #14
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/comments/14
Latest 5.13 kernel in -prosed on Focal (20.04.3) gets the same gpio
err
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
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/1937897
Title:
GPIO error logs in start and dmesg after
Added tag 'verification-failed-hirsute'. Enabled proposed and installed
package 'linux-image-5.13.0-14-generic' version '5.13.0-14.14~20.04.4'
on my 20.04.3 LTS, and still get in dmesg:
[1.228729] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with
zero lines
[1.228732] gpiochi
--
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/1929504
Title:
Add support for IO functions of AAEON devices
Status in linux package in Ubuntu:
Fix Released
Status in linux source packa
OK, but don't try to load the gpio-aaeon module on PCs that, if simply
one tries to load it manually, it simply says that no such device
exists... It shows twice in the boot log (dmesg + journalctl -b) but
even worse also on the monitors, although GRUB has "quiet" specified (no
splash).
Worst of a
Well OK there is a module with that name, however I did blacklist it and
same error still occurs. It happens very early in the boot process. Now
maybe it tries to load gpio-aaeon, but still early to load modules I
would say, it's still doing say GRUB kernel parameters like fsck ones.
Now I have co
No, I can't, because there isn't a single module loaded with even the
name "gpio" in it.
So running: $ lsmod|grep gpio == No result
It's in the kernel, not a module. I reverted to the GA kernel and
although with that I've had some issue with on headless *Intel* NUC
running Virtual Machines that u
EDIT: To clarify both times these lines come they refer to "gpiochip1"
(so not 2 different ones).
I started getting the same 3 lines of errors TWICE at boot, with the now
latest official 5.8 HWE kernel. Without "splash", just "quiet" set for
GRUB it also shows on my monitors when booting. Honestly
I don't have a "Unifying receiver". That's just the name which appears
and/or disappears when I plug in the KVM to the PC. The KVM in all cases
is directly connected to the keyboard/mouse/screen at one end, and USB
ports/HDMI at the PC end.
-- Original Message --
From: "Hui Wang" <1930.
0 GHz
Installed RAM16.0 GB
Device ID86452CEC-D6C1-46A6-9970-7FE2338F4B02
Product ID00326-1-0-AA334
System type64-bit operating system, x64-based processor
Pen and touchNo pen or touch input is available for this display
Here's the motherboard info
C:\Users\Jon>w
I can deterministically reproduce this crash with Wireguard on the RPI3
running 20.10 and hence using the lan78xx driver on eth0. A few minutes
of browsing public web sites on a client connected through Wireguard to
the RPI3 crashes the RPI. Changing nothing except for running
Wireguard's forward
Public bug reported:
Ubuntu 18.04.5
iproute2 4.15.0-2ubuntu1.2
iproute2-doc 4.15.0-2ubuntu1.2
Most of the subcommands for /sbin/ip are documented in a manpage with a name of
the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at
"ip-address(8)".
However, ip tuntap seems to be
Changing the status of this bug from 'expired' to 'confirmed', since all
the way up here in Ubuntu 20 land (in 2020), I have found this bug when
development testing my research OS. Random lockups and segfaults, after
which the CPU usage of the qemu-system-x86 process sticks at over 100%.
** Chang
It turns out the MOK key installed previously was removed during a BIOS
update. Upon the next kernel update from Ubuntu I was prompted to
install the MOK key, after which OpenCL works even when kernel lockdown
is enabled.
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: New => In
** Description changed:
When booting with secure boot and kernel lockdown is enabled, OpenCL is
unable to use my GPU (GeForce RTX 2080 SUPER). Running "clinfo" shows
- "Number of platforms 0". If I disable secure boot in my UFEI BIOS,
+ "Number of platforms 0". If I disable secure boot in
Public bug reported:
When booting with secure boot and kernel lockdown is enabled, OpenCL is
unable to use my GPU (GeForce RTX 2080 SUPER). Running "clinfo" shows
"Number of platforms 0". If I disable secure boot in my UFEI BIOS,
clinfo shows the details of my GPU as expected.
ProblemType: Bug
Public bug reported:
Release 20.04 LTS with MATE desktop on RPi 4 with 4GB.
Running with root on SSD and /boot on SD.
Following "sudo apt update && sudo apt full-upgrade", I get a series of
errors starting with:
Setting up linux-image-5.4.0-1013-raspi (5.4.0-1013.13) ...
Failed to create symlink
i am also seeing this same issue on Mint 19.2 Tina on a dell XPS13.
only after a recent (today) apt update.
i can ssh in and tail the kern.log and watch it happen, same kind of
sporadic usage, like switching between slack-desktop and chrome etc.
# Apr 18 22:09:59 fig kernel: [ 1138.173506] i915 0
All 3 test kernels look good. Tested on internal ryzen development
boards that were showing this symptom previously.
--
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/1796443
Title:
HP Eli
Hardware: Thinkpad T440s
OS/Kernel: Kubuntu 18.04/4.15.0-52-generic
Driver: mtrack
Also experienced this bug. The temporary fix (modprobe) worked, but
commenting out the "blacklist i2c_i801" line resulted in the machine not
finding the touchpad on reboot.
I was able to successfully fix this iss
Thank you! Will do.
--
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/1796443
Title:
HP EliteBook 745 G5 (Ryzen 2500U) fails to boot unless `mce=off` is
set on command line
Status in Lin
Adding dmesg/serial from failing system (AMD test board) as another
example of failing system besides the original reporter.
** Attachment added: "kernel log from failing system (AMD)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796443/+attachment/5268815/+files/dmesg-panic.log
--
Just ran across this bug in LP.
Note: 60c8144afc28 is only masking what the real issue is; it's a real
bug, but the reason it's getting hit at all in this specific instance is
because of an AMD CPU erratum which is causing spurious MCEs early
enough to hit the bug this commit fixes.
However, whil
*** This bug is a duplicate of bug 1813663 ***
https://bugs.launchpad.net/bugs/1813663
This bug is affecting several of my coworkers!!
--
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/18
Is there any chance you can find a page in your bios like the one I've
attached and post it? For me I hit f12 (boot device select), device
configuration, amd pbs, and firmware version. I'm having an identical
issue with my dell Inspiron 7375 and an Intel 7260 and am curious if I
can expect a fix f
Something to try, run system monitor. If I have it open I don't have any
issues playing videos. Strange but true.
--
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/1777238
Title:
video lag
Thanks for the suggestion @kaihengfeng. I installed linux-generic-
hwe-16.04-edge, which gave me a working 4.15.0-23-generic after a
reboot.
The log from 4.13.0-45 failed at this point:
[2.444002] DMAR-IR: IOAPIC id 10 under DRHD base 0xdfffe000 IOMMU 0
[2.52] DMAR-IR: IOAPIC id 9 un
Another data point, 4.13.0-45 crashes on boot even with acpi=off. It
looks like a different call trace though, which I can transcribe on
request if anyone thinks it will help.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Attached is a transcription of the latest kernel boot panic.
This is the Oops:
[2.62] BUG: unable to handle kernel NULL pointer dereference at (null)
[2.62] IP: __bitmap_intersects+0x10/0x70
[2.62] PGD 0
[2.62] P4D 0
[2.62]
[2.62] Oops: [#1] S
I am still experiencing the same bug. I regularly pull down the latest
updates with apt update and apt dist-upgrade, and if a kernel update is
included then I always test it.
This morning my system got updated with both linux-
image-4.13.0-45-generic and linux-image-4.4.0-128-generic. I have
modif
If it helps I am using Kernalcare so it pushes me to the latest version
which I am seeing might not be a good idea.
--
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/1746806
Title:
sssd app
I am having the same issue. I tested the C5 instance when it first came
out and it would randomly lock up at 100% CPU. I contacted AWS support
and they could not figure it out. They sent a message to the devs to see
if they could. So I switched back to c4 instances. I decided to try it
again yester
I updated again this morning and installed the latest 4.13.0-36-generic
kernel. Unfortunately it still panics on boot. I've attached another
slo-mo video.
** Attachment added: "Slo-mo video of failing boot of 4.13.0-36-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+atta
sudo apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following packages were automatically installed and are no longer required:
linux-headers-4.4.0-108 linux-headers-4.4.0-108-generic
linux-headers-4
Public bug reported:
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
linux-image-extra-4.4.0-108-generic : Depends: linux-image-4.4.0-108-generic
but it is not going to be installed
linux-image-generic : Depends: linux-image-4.4.0-109
** Attachment added: "Slo-mo video of failing boot (3s)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+attachment/5039509/+files/Failed%204.13.0-26-generic%20boot.mp4
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
It still fails for me with acpi=off.
A bit of background, this PC has been running fine for the past 12
months or so, with regular updates including kernel updates. It's only
started failing since 4.13.0-26-generic.
** Attachment added: "grub command line"
https://bugs.launchpad.net/ubuntu/+s
** Attachment added: "Kernel panic from 4.13.0-30-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675/+attachment/5038840/+files/IMG_0803.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
@jsalisbury
Thanks, I followed the instructions and tried booting 4.13.0-30-generic.
I still get a kernel panic. I've attached a screenshot from grub with
the kernel version visible, and a screenshot of the panic.
Thanks
** Attachment added: "grub screenshot"
https://bugs.launchpad.net/ubunt
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934
It is indeed not happening after upgrading to 4.4.0-109. Many thanks for
the lightning-quick response!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
The kernel version in the report is the previous, working version which
I booted into to file the report. The broken version is linux-
image-4.4.0-108-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Public bug reported:
After an unattended upgrade today my system would no longer boot.
Presumably the kernel panic and stack trace info is attached. This is on
an HP ProLiant MicroServer Gen8
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-104-generic 4.4.0-104.127
ProcVer
upgraded kernel to 4.12.13 and the problem is not happening.
--
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/1697132
Title:
CPU Cores Stalls/Lock
Status in linux package in Ubuntu:
Inc
1 - 100 of 246 matches
Mail list logo
