Are you trying to report a kernel problem? If so, what is it?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/2084789
Title:
* dkms: running auto installation service for kernel 6.8.0-47-generic
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/nvidia-fs/2.22.3/source/dkms.conf)
Deprecated feature: REMAKE_INITRD
(/var/lib/dkms/nvidia-fs/2.22.3/source/dkms.conf)
nvidia-fs/2.22.3 autoinstall failed due to missing dependen
** Tags removed: need-duplicate-check
--
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/2084836
Title:
package linux-headers-6.8.0-47-generic 6.8.0-47.47 failed to
install/upgrade: instal
Hi Paolo,
Thanks for your quick respond, I will test new one next Monday.
--
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/2081685
Title:
[Ubuntu 24.04-generic Kernel-6.8]Hard lockup on 8
** Summary changed:
- [i915] ThinkPad X201 (Arrandale) screen freezes
+ [i915] ThinkPad X201 (Arrandale) screen freezes in kernels >= 6.9.0
--
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/2
Hi Michael,
This fixed the issue in 24.04. and 22.04.5 which has the 6.8 kernel.
[shangsong]: 1. When the fix will release or which release already contain the
fix on 24.04?
2. Is it necessary to open a issue for Ubuntu 22.04.5 HWE kernel(6.8.0-40)
--
You received this bug notification becaus
** Description changed:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
1. Fresh install of Ubuntu server 24.04 on the Server with Intel VMD
- 2. Upgrade the
V2 change and built kernel image.
Heiner Kallweit 2024-10-17 21:25:46 UTC
I found that the proposed patch causes issues under heavy load. Reason isn't
clear yet. Could you please test whether the following fixes the issue for you
as well?
This change should have no side effects.
diff --git a/
** Description changed:
[Impact]
Failed to locate the LED of nvme device behing Intel VMD via below command
# ledctl locate=/dev/nvme0n1 or ledctl locate=/dev/nvme0n1 --listed-only
[Test Plan]
- 1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
- 2. Upgrade kernel
Hi Shangsong,
What is the regression risk of this patch?
** Description changed:
+ [Impact]
1. Fresh install Ubuntu server 24.04 on the Server with Intel VMD
2. Upgrade kernel to 6.8.0-40 and install ledmon package
3. Fail to locate the LED of nvme device behing Intel VMD via below command
Hi Shangsong,
This fixed the issue in 24.04. and 22.04.5 which has the 6.8 kernel.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a mem
Public bug reported:
The track pad on this laptop is not detected by Ubuntu at all. its a
ipason laptop. I am running Ubuntu version: 24.04.1 LTS the software
center appears to be version: 1.0.0
this is a fresh install of Ubuntu on a new laptop i got for a
cybersecurity school. it would be nice t
Patch submitted: https://lists.ubuntu.com/archives/kernel-
team/2024-October/154680.html
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu.
https://bugs.launchp
Hi Matthew,
If you look at https://launchpad.net/~ubuntu-
toolchain-r/+archive/ubuntu/ppa/?field.series_filter=noble
it indeed shows that 6.8.0-45-generic is in there, and not -47, but
soon, Matthias Klose will probably build 6.8.0-47-generic and break you
again too.
emacs 29.4 is in oracular, y
Hi Pedro,
Great to hear that this helped you.
Hmm, we should probably try figure out why the modules weren't pulled in
when the image was installed.
Any chanced you could have a look through /var/log/apt/history.log, and
see when 6.8.0-47-generic was first installed, and what packages were
insta
Public bug reported:
encountered during an update
ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: linux-headers-6.8.0-47-generic 6.8.0-47.47
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVer
** Description changed:
This is a public version of: https://bugs.launchpad.net/bugs/2078894
[Impact]
- In Emerald Rapids VMs, a stack trace is printed during boot on 6.8 based
- kernels. The stack traces look like:
+ In Emerald Rapids VMs with OOB P-states enabled, a stack trace is
+ pr
** Tags removed: verification-needed-oracular-linux
** Tags added: verification-done-oracular-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to iproute2 in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/206450
** Tags removed: verification-needed-oracular-linux
** Tags added: verification-done-oracular-linux
--
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/2083845
Title:
Setting I/O scheduler to
** Tags removed: verification-needed-oracular-linux
** Tags added: verification-done-oracular-linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
Matching subscriptions: iproute2
https://bugs.launchpad.net/bugs/1470
Public bug reported:
This is a public version of: https://bugs.launchpad.net/bugs/2078894
[Impact]
In Emerald Rapids VMs, a stack trace is printed during boot on 6.8 based
kernels. The stack traces look like:
[ 1.206658] intel_pstate: Intel P-state driver initializing
[ 1.207453] unchecked MSR
here is some info https://perfectglazing.uk/
--
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/1628204
Title:
linux: 4.4.0-41.61 -proposed tracker
Status in Kernel SRU Workflow:
Fix Rele
Ah, the toolchain thing is ringing a bell. I believe I had to install
that in order to get a different version of gcc because I was trying to
build a newer version of emacs than I could get from the repositories.
In any case, ubuntu has now updated to 6.8.0-47.47-generic and that
doesn't seem to h
if you need more reliable information here is the
https://homeimprovmentideas.uk/
--
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/1628204
Title:
linux: 4.4.0-41.61 -proposed tracker
Stat
** Changed in: systemd (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Jammy)
Importance: High => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Hi Juerg, I actually rolled back to the snapshot I had from the previous
day. Seems to be working fine again. Planning on holding off on running
updates for a week to be safe.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid =
Many thanks Anushree for this double verification, now also with macvtap
- that's great and gives confidence.
--
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/2076406
Title:
L2 Guest migra
Fixed already part of https://bugs.launchpad.net/bugs/2083488
--
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/2083923
Title:
[VROC][Ub 24.04.1] LEDs are not changed correctly
Status in l
Committed as 5560a612c20d3 upstream.
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to li
bisect shows
# first bad commit: [9c901808b3affa5b21bb146148ae2c39dfd732ee] drivers:
core: synchronize really_probe() and dev_uevent()
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/b
Based on google, the ntfs driver is now the kernel default, but it
provides read only access only, its web page says the people supporting
it are part time only, there are reports about file system corruption, a
notice about linux 6.9 maybe dropping it.
Maybe ubunutu should just blacklist ntfs by
After ckeck drivers ubuntu-drivers autoinstall and after updating the
packages the problem has been solved
--
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/2084493
Title:
thinkpad having i
Well that was really painful to find. After hours of bisecting and
building kernel manually I've found it: Kernel (and Ubuntu Devs) enabled
Intel IOMMU by default:
* https://github.com/torvalds/linux/commit/792fb43ce2c9
* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440
Ubuntu Devs we
Public bug reported:
I upgraded releases from 24.04 to 24.10 and found that my sound was not
working anymore. My previous sound outputs go away and all I see is
Dummy Output. After a long time debugging I tracked it to the package
alsa-ucm-conf. By installing an older version of the package my sou
--- Comment From anushree.math...@ibm.com 2024-10-17 11:13 EDT---
Hi fheimes,
I have tried with macvtap network and it is working fine in this scenario too!
ANALYSIS
HOST[SOURCE](Non-MDC):
OS : ubuntu
Kernel: 6.8.0-48-generic
qemu : QEMU emulator version 8.2.2 (Debian 1:8.2.2+ds-0ubuntu1.2
** Description changed:
- [Summary]
+ [Impact]
During the SRU testing, I found many laptops displayed a black screen after
booting. Those machines are still alive and able to access via ssh, just
nothing displayed on the screen.
After a brief check, those affected machines that I inspecte
Hello!
where are you doing
--
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/2084808
Title:
Dell Alienware sysytem reports errors of dell_wmi_sysman and
dell_smbios in demsg
Status in li
So can we log this somewhere for the ntfs developers as 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/2062972
Title:
ntfs partition does not mount with linux 6.8 and
CONFIG_BLK_D
I am using Linux kernel 6.8.0-47-generic and when trying to mount clean
ntfs drives, I also get "wrong fs type, bad option, bad superblock".
Morbius1's solution:
echo 'blacklist ntfs3' | sudo tee /etc/modprobe.d/disable-ntfs3.conf
And a reboot worked for me as well. Thank you Morbius.
--
You re
@Luca, @Portia I assume this verification action item is on us. Please
confirm.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/2083466
Title:
xilinx-tsn: fix ptp sync failu
** Changed in: linux-nvidia (Ubuntu Noble)
Status: In Progress => Fix Committed
** Changed in: linux-nvidia-6.8 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-nvidia-lowlatency (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received thi
No, no need for further verification, that was already done, see:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070329/comments/10
and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2070329/comments/11
(just this tag 'verification-needed-noble-linux' is the relevant one for
us here -
*** This bug is a duplicate of bug 2084251 ***
https://bugs.launchpad.net/bugs/2084251
Hi Paolo,
I say bug feels like the same because while booting LUKS is not asking
for password.
I upgraded from 24.04 to 24.10 and also did a fresh install without any
success.
I managed to solve the prob
Great Anushree! Thanks for your verification on this - that gives
confidence to roll out the kernel!
--
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/2076866
Title:
Guest crashes post migr
*** This bug is a duplicate of bug 2084251 ***
https://bugs.launchpad.net/bugs/2084251
** This bug has been marked a duplicate of bug 2084251
LUKS not detected or prompted for on boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
I can't verify because I installed 24.10. I experience no flickering with
kernel 6.11.0-8.
On Thu, Oct 17, 2024, 5:42 AM Ubuntu Kernel Bot <2062...@bugs.launchpad.net>
wrote:
> This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
> kernel in -proposed solves the problem. Please t
** Changed in: linux-gke (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gke in Ubuntu.
https://bugs.launchpad.net/bugs/2084716
Title:
Disable Multi-Gen LRU in the 6.8 ker
*** This bug is a duplicate of bug 2084251 ***
https://bugs.launchpad.net/bugs/2084251
Hi Jose,
when you say your situation is exactly the same, does it mean (quoting
bug here 1998266): "After the initial start screens, when LUKS is
expected to appear, the monitor instead says "no signal" and
--- Comment From anushree.math...@ibm.com 2024-10-17 09:30 EDT---
Hi fheimes!
I have done the testing with macvtap bridge and this scenario is also
working fine!
HOST[SOURCE](MDC):
OS : ubuntu
Kernel: 6.8.0-48-generic
qemu : QEMU emulator version 8.2.2 (Debian 1:8.2.2+ds-0ubuntu1.2)
libvi
Hello Mathew,
It seems you were correct, and I must have been missing linux-modules or
linux-modules-extra packages. Running the commands:
$ sudo apt install linux-image-6.8.0-47-generic linux-modules-6.8.0-47-generic
linux-modules-extra-6.8.0-47-generic linux-headers-6.8.0-47-generic
$ sudo apt
@bktan1 It's not there in proposed, it's committed for next SRU cycle.
--
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/2083701
Title:
[SRU] GPU: support additional device ids for DG2 driv
Sure, but there is plenty of space at /boot and / (and I would have
noticed some "insufficient disk space" if that happened during initrd
creation).
nwildner@host:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 3.2G 3.2M 3.1G 1% /
--- Comment From sthou...@in.ibm.com 2024-10-17 09:21 EDT---
(In reply to comment #12)
> Man thanks Gautam for the successful verification!
> (I'm updating the tags accordingly ...)
--- Comment From ubuntu-kernel-bot 2024-10-17 17:37:45 UTC---
This bug is awaiting verification that the
** Changed in: dracut (Ubuntu)
Milestone: None => ubuntu-25.04
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2070066
Title:
dracut does not support booting from an encrypted ZFS
Public bug reported:
[Impact]
A Dell Alienware system reports some error messages in dmesg after booting up:
1. dell_wmi_sysman: Unable to run on non-Dell system
2. dell_smbios: Unable to run on non-Dell system
[Fix]
Applying the following patch from linux-next fixes the issue:
a561509b4187 platf
** Changed in: linux-intel (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/2071628
Title:
Fix QEMU/KVM support for EPT pa
** Tags added: verification-done verification-done-jammy
--
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/2074380
Title:
[UBUNTU 22.04] s390/cpum_cf: make crypto counters upward compatible
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
This bug is awaiting verification that the linux-xilinx/6.8.0-1009.10
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-noble-linux-xilinx' to 'verification-done-
noble-linux-xilinx'. If
Public bug reported:
This bug feels like the same of this one:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998266 but for
24.10.
Someone have already asked for this here:
https://askubuntu.com/questions/1529983/the-luks-passphrase-screen-
doesnt-show-up-after-24-10-installation
My situ
Per your request: switched back up to kernel 5.4.0-198 and repeated same
actions that generated errors. This time I could NOT duplicate the
errors. Perhaps simply rebooting resolved my prior issues.
I installed apport system, and will use it to document errors if they
recur.
--
You received th
So far, I've tracked that down to the 6.9 branch. I haven't got any
freeze on 6.8.0, 6.8.12, nor Noble's kernel (6.8.0-31), but got them on
6.9.0 and 6.10.1 downloaded from your link. Are there pre-built packages
somewhere to help bisect the commit, or is it a completely manual
process? I'm not ver
Thanks Amy,
here's another kernel for you to test:
https://people.canonical.com/~ppisati/lp2081685/f6f633918771/
As for the previous one, you probably just need to update linux-image-
unsigned, linux-modules and linux-modules-extra packages.
--
You received this bug notification because you are
This bug is awaiting verification that the linux/6.11.0-9.9 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-oracular-linux' to 'verification-done-oracular-
linux'. If the problem still
This bug is awaiting verification that the linux/6.11.0-9.9 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-oracular-linux' to 'verification-done-oracular-
linux'. If the problem still
This bug is awaiting verification that the linux/6.11.0-9.9 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-oracular-linux' to 'verification-done-oracular-
linux'. If the problem still
Public bug reported:
mark-herzog@marks-win10-ubtu20:~$ ubuntu-bug linux
mark-herzog@marks-win10-ubtu20:~$ Gtk-Message: 12:11:29.023: Not loading module
"atk-bridge": The functionality is provided by GTK natively. Please try to not
load it.
[128091, Main Thread] WARNING: GTK+ module
/snap/firefo
Any updates or idea @kowshik?
Do we need to pull the commit again from the kernel?
--
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/2060039
Title:
[Ubuntu-24.04] FADump with recommended cr
noble works with -48
** Changed in: linux (Ubuntu Noble)
Status: New => Invalid
** Also affects: linux-firmware (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
** Changed in: linux-firmware (Ubuntu Noble)
St
Hi Nicolas,
can you show us the output of 'ls -la /boot/'?
And 'df -h' too.
--
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/2084695
Title:
Kernel update through apt leaves the system wit
Hi Paolo, I just installed new 6.8.0-32.32 kernel that you provided, but
seems same with comment #20, it occurred 3 times out of 6 reboots.
--
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/20
** Attachment added: "dmesg_new_32.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2081685/+attachment/5828907/+files/dmesg_new_32.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
** Also affects: linux-nvidia-tegra-igx (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-nvidia-tegra (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lo
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Ghadi Rahme (ghadi-rahme)
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Ghadi Rahme (ghadi-rahme)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
note that I was able to reproduce this with MTL-M SDP, and updating the
GuC firmware helped
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2084766
Title:
Most Meteor Lake machine
1 - 100 of 106 matches
Mail list logo
