apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1991703/+attachment/5621178/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1991703/+attachment/5621170/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
After today's Kinetic update my Framework laptop won't boot.
The boot hangs after this output:
[0.813802] pci :00:07.0: DPC: RP PIO log size 8 is invalid 0.814786] pci
:00:07.1: DPC: RP PIO log size 8 is invalid
[0.815754] pci :00:07.2: DPC: RP PIO log size 8 is
One difference between my Framework laptop (where the problem is
happening) and my ThinkPad is that the Framework laptop has a separate
Windows boot partition. Don't know if that's relevant, but thought it
worth mentioning just in case.
--
You received this bug notification because you are a memb
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/1991704
Title:
New Kinetic kernel (5.19.0-18-
Thanks Kai-Heng Feng, I have just tried to use 5.15.0.43-generic and the
issue isn't there: no need to modprobe -r xhci_pci, as there isn't any
kworker pegging a CPU.
So indeed a git bisect or similar approach between kernels .43 and .46
could reveal something. I can't find binaries for kernels in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/
Could this be a problem with the Nvidia DKMS driver? On a laptop using
the Radeon driver I have no problem.
** Also affects: nvidia-graphics-drivers-515 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which i
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1005.5
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1005.5
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1005.5
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1005.5
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1005.5
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
Unload the module, then suspend succeeds Dmesg.
Reloading the module results in.
[ 308.882904] i2c i2c-0: Failed to register i2c client dummy at 0x48 (-16)
[ 308.882977] cm32181: probe of i2c-CPLM3218:00 failed with error -16
** Attachment added: "kernel_lp1988346-3_dmesg_03_unload_module_susp
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1005.5
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
Suspend Fail Dmesg
** Attachment added: "kernel_lp1988346-3_dmesg_02_suspend_fail_with_module"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988346/+attachment/5621234/+files/kernel_lp1988346-3_dmesg_02_suspend_fail_with_module
--
You received this bug notification because you are a
This bug is awaiting verification that the linux-oem-6.0/6.0.0-1005.5
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-jammy' to 'verification-done-jammy'. If the
problem still exists,
Boot Dmesg
** Attachment added: "kernel_lp1988346-3_dmesg_01_boot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988346/+attachment/5621233/+files/kernel_lp1988346-3_dmesg_01_boot
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
All autopkgtests for the newly accepted linux-meta-oem-6.0 (6.0.0.1005.5) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/249.11-0ubuntu3.6 (amd64)
Please visit the excuses page listed below and investigate the failures,
** Description changed:
- On an HP x360 Spectre (i7-8565U WhiskeyLake-U GT2 [UHD Graphics 620]),
- after upgrading to 22.04 from 21.10, the display goes to some flickering
- lines in black and grey or colors (remember the artifacts on Amstrad CPC
- or C64 when loading from a tape? Same here...).
+
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1990945
Title:
i915: Add GuC v70.1.1 for all platforms
Status in HWE N
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1973676
and then change the status of the bug to 'Confirmed'.
If, due to the nature
I have the same issue with 5.19.0-18-generic on:
* Microsoft Surface Laptop 4
* Intel NUC 12 desktop
Although the last seen kernel log messages are a bit different for each
machine so I'm not sure how relevant they are.
** Summary changed:
- New Kinetic kernel (5.19.0-18-generic) won't boot
All affected machines seem to mention:
Dev loop[02]: unable to read RDB block 8
I can still ssh into the machine but there is no /dev/dri/, so that's
one reason why we wouldn't see any graphical startup.
--
You received this bug notification because you are a member of Kernel
Packages, which
Is the problem only Intel 11th/12th gen?
--
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/1991704
Title:
New Kinetic kernel (5.19.0-18-generic) won't boot
Status in linux package in Ubunt
Public bug reported:
Expected on kinetic: dkms will sign built modules with MOK key if
requested.
What happens:
dkms outputs "Binary kmod-sign not found, modules won't be signed"
Fix:
update dkms to 3.0.7: https://github.com/dell/dkms/pull/242
** Affects: dkms (Ubuntu)
Importance: Undeci
All autopkgtests for the newly accepted linux-meta-oracle-5.4
(5.4.0.1084.92~18.04.61) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
linux-oracle-5.4/unknown (arm64)
kpatch/0.5.0-0ubuntu1.1 (amd
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
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
You have been subscribed to a public bug:
I have the shell configured to lock the screen when I close the lid and
go to sleep after 20 idle minutes on battery power.
Immediately before I opened my laptop and unlocked it to submit this
bug, the laptop was unplugged from battery power and sitting w
** Changed in: ubuntu
Status: Incomplete => New
** Package changed: ubuntu => linux (Ubuntu)
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Does the issue still happen on v6.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/1975444
Title:
mt7921e wifi fails to resume after suspend
Status in linux package in Ubuntu:
Incomp
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1991598
and then change the status of the bug to 'Confirmed'.
If, due to the nature
This issue has gone in s390x zVM host kernel01 / LPAR host s2lp3
Running
'/home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/tests/skey'
BUILD_HEAD=16647354
timeout -k 1s --foreground 90s /usr/bin/qemu-system-s390x -nodefaults
-nographic -machine s390-ccw-virtio,accel=k
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990161
Title:
Fix RPL-S support on powercap/intel_rapl
Status in HWE Next:
New
Status i
download latest software 2023
https://millioncrack.com/anytrans-v8-9-2-crack/
https://zcracked.com/fontcreator-crack/
https://canarydata.io/vmix-crack-registration-key/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
OK the patch set here is broken, we gotta do this from scratch properly.
So I'm going to start cherry picking the rhboot patches for memory
management. I have applied so far from bug 1989446 the backport of "Try
to pick better locations for kernel and initrd" and cherry-picked from
rhboot the "x86-
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
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/bugs/1991403
Title:
mlxbf_gige: fix devm_ioremap error handling
should end up in 6.1
** Changed in: linux-oem-5.17 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux-oem-6.0 (Ubuntu Kinetic)
Status: New => Invalid
** No longer affects: linux (Ubuntu Kinetic)
** No longer affects: linux-oem-5.17 (Ubuntu Kinetic)
** No longer affects:
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
** Changed in: ubuntu-power-systems
Status: Triaged => Incomplete
** Tags removed: kk-release
--
You received this bug notification because you are a member of Kernel
Packages, whic
Private bug reported:
Missing:
iwlwifi-so-a0-gf-a0-74.ucode
iwlwifi-so-a0-gf4-a0-74.ucode
Sorry I don't have more details, only that we need to ship them for the
Kivu project. Eventually that means jammy too.
** Affects: linux-firmware (Ubuntu)
Importance: Wishlist
Status: New
Sorry, but I won't do this. It's quite old post (2013), I'm afraid it's
outdated, I need computer to work, I can't afford whole system to crash.
--
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
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug was fixed in the package linux - 5.19.0-18.18
---
linux (5.19.0-18.18) kinetic; urgency=medium
* kinetic/linux: 5.19.0-18.18 -proposed tracker (LP: #1990366)
* 5.19.0-17.17: kernel NULL pointer dereference, address: 0084
(LP: #1990236)
- Revert "UBUNT
This bug is awaiting verification that the linux-
bluefield/5.15.0-1008.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-jammy' to 'verification-
done-jammy'. If the problem still ex
This bug is awaiting verification that the linux-
bluefield/5.15.0-1008.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-jammy' to 'verification-
done-jammy'. If the problem still ex
This bug is awaiting verification that the linux-
bluefield/5.15.0-1008.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-jammy' to 'verification-
done-jammy'. If the problem still ex
This bug is awaiting verification that the linux-
bluefield/5.15.0-1008.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-jammy' to 'verification-
done-jammy'. If the problem still ex
This bug is awaiting verification that the linux-
bluefield/5.15.0-1008.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-jammy' to 'verification-
done-jammy'. If the problem still ex
This bug is awaiting verification that the linux-
bluefield/5.15.0-1008.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-jammy' to 'verification-
done-jammy'. If the problem still ex
This bug is awaiting verification that the linux-
bluefield/5.15.0-1008.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-jammy' to 'verification-
done-jammy'. If the problem still ex
Public bug reported:
irdma Kernel module will use > 5GB as soon as is loaded. This bug is
present from kernel 5.14.
# free -m
total used free shared buff/cache available
Mem: 15663 5998 8936 155 728 9213
Swap: 0 0 0
Using ps the sum of RSS memory does not adds up: it shows less th
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1959940
Title:
[22.10 FEAT] KVM: Secure Execution guest dump e
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853306
Title:
[22.04 FEAT] Enhanced Interpretation for PCI Fu
** Changed in: ubuntu-z-systems
Status: Triaged => In Progress
--
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/1639924
Title:
Kernel livepatch support for for s390x
Status in Ubun
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1959542
Title:
[22.10 FEAT] [IO2201] Independent Usage of Seco
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/1991656
Title:
irdma Kernel module huge memor
Yes. I have included a tarball of everything under that directory.
Thank you for looking into this!
** Attachment added: "pstore.tgz"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990697/+attachment/5621018/+files/pstore.tgz
--
You received this bug notification because you are a me
** Tags added: verification-done-jammy
--
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/bugs/1989172
Title:
mlxbf-pmc: error when reading unprogrammed events
Status in linux-bluefiel
Public bug reported:
[ Impact ]
* hwe-5.19 kernel has to be compiled with gcc-12+ for the new security
kernel config options that have been enabled in that kernel (init zero
structs).
* dkms needs to be patched to attempt to use the same compiler as was
used to build the kernel, specifically u
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
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/1
I can confirm that the (naive) patch sidesteps the issue, but that it is
otherwise present on all our 5.15/ZFS installs.
--
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/1980848
Title:
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: dkms (Ubuntu)
Status: Fix Released => Triaged
** Also affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kerne
Public bug reported:
This is a scripted bug report about ADT failures while running linux-
hwe-5.4 tests for linux-hwe-5.4/5.4.0-128.144~18.04.1 on bionic. Whether
this is caused by the dep8 tests of the tested source or the kernel has
yet to be determined.
Testing failed on:
amd64:
https://
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1991664
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Description changed:
- This is a scripted bug report about ADT failures while running linux-
- hwe-5.4 tests for linux-hwe-5.4/5.4.0-128.144~18.04.1 on bionic. Whether
- this is caused by the dep8 tests of the tested source or the kernel has
- yet to be determined.
+ The ADT tests for arm64 ker
Could this be the same issue as reported in bug 1936857?
** Also affects: grub2-unsigned (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Package grub-efi-arm64-signed 1.173.2~18.04.1+2.04-1ubuntu47.4 from
bionic-proposed fails to install/upgrade
+ Package grub-efi-arm
** Tags added: bionic regression-proposed
** No longer affects: grub2-unsigned (Ubuntu)
** No longer affects: grub2-unsigned (Ubuntu Bionic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.
Public bug reported:
Since the last kernel update today my system stops in the middle of the boot
process and does not reach KDE.
---
ProblemType: Bug
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DistroRelease: Ubuntu 22.10
InstallationDate: I
apport information
** Attachment added: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1991703/+attachment/5621162/+files/AlsaInfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1991703/+attachment/5621165/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launch
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1991703/+attachment/5621164/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1991
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1991703/+attachment/5621176/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.la
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1991703/+attachment/5621173/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpa
1 - 100 of 112 matches
Mail list logo
