So, it looks like there are multiple issues here. The NULL pointer
dereference bug that I see in comment #25 seems to be fixed by
458ec0c8f359 ("drm/i915: fix null pointer dereference"), but this can
happen only when i915 is used.
For the other problem(s) do you happen to have a kernel oops / trac
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
** This bug has been marked a duplicate of bug 1991704
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
--
You received this bug notification because you are a member of Kernel
Pac
*** This bug is a duplicate of bug 1991704 ***
https://bugs.launchpad.net/bugs/1991704
** This bug has been marked a duplicate of bug 1991704
Kinetic kernels 5.19.0-18/19-generic won't boot on Intel 11th/12th gen
--
You received this bug notification because you are a member of Kernel
Pac
I noticed that we're missing some i915 fixes from stable updates, so
I've applied a bunch of patches from stable and produced this test
kernel:
https://kernel.ubuntu.com/~arighi/lp-1993818/
It'd be great if someone affected by this bug could give it a try and
verify if the problem is still happen
Thanks for testing and good to know that the kernel doesn't seem to
crash (so far). All the i915 fixes that I applied will be available in
the next official Kinetic kernel, so we should be good. Let me know if
the problem happens again.
About the color distortions I'll investigate a bit. I may ask
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Committed
--
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/1993818
Title:
Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Ca
** Also affects: linux (Ubuntu Lunar)
Importance: Medium
Status: Triaged
** Also affects: lava (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
** Also affects: bpfcc (Ubuntu Lunar)
Importance: Undecided
Status: Triaged
** Also affects: bpftrace (Ubuntu Lunar)
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
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/1993818
Title:
Linux kernel crash on Ubuntu 22.10 on Th
Public bug reported:
[Impact]
sysdig-dkms fails to build on arm64 with the latest impish kernel
(5.13):
/var/lib/dkms/sysdig/0.27.1/build/main.c:1942:28: error: ‘SYSCALL_TABLE_ID0’
undeclared (first use in this function); did you mean ‘SYSCALL_TABLE_SIZE’?
1942 | table_index = id - SYS
** Patch added: "sysdig-fix-arm64-build.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1945757/+attachment/5529832/+files/sysdig-fix-arm64-build.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5
** Patch added: "sysdig-fix-arm64-build.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.6/+bug/1945757/+attachment/5529831/+files/sysdig-fix-arm64-build.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5
Public bug reported:
Found this when running the systemd autopkgtest on linux-aws
5.13.0-1004.5 (apparently it seems to affect nested kvm only):
systemd-testsuite login: [ 70.235559] int3: [#1] SMP NOPTI
[ 70.237824] CPU: 0 PID: 326 Comm: systemd-journal Not tainted
5.13.0-1004-aws #5-U
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: 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/1836694
Title:
memcg_test_3 from controllers in LT
Update: disabling CONFIG_KFENCE_STATIC_KEYS prevents this problem from
happening, so we may consider to disable this option as a temporary
workaround, or even disable KFENCE entirely, since it's more like a
debugging feature (low-overhead out-of-bounds / use-after-free /
invalid-free memory detecto
@Pietro, thanks for reporting this.
Can you do a test with the kernel that is currently in impish-proposed
(5.13.0-18.18)? See https://wiki.ubuntu.com/Testing/EnableProposed on
how to enable proposed (for this you need to upgrade from 21.04, then
enable proposed, install 5.13.0-18.18, then reboot)
ok, another interesting test to do would be to see what happens with a
mainline kernel (just to see if the problem is a mainline issue or if
it's limited to the Ubuntu kernel).
Can you try to do a test with this kernel?
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13.19/
^ This is basically
Update: apparently CONFIG_KFENCE can only reduce the probability to
trigger the bug, so it's not a reliable fix. According to all the traces
that we got the soft lockup is always happening to any SLUB allocation
function (__kmalloc, kmem_cache_alloc, and similar), and the instruction
pointer is on
Maybe disable secure boot from the BIOS? Test kernels can't be signed,
so I guess that's the only way...
--
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/1945590
Title:
Thinkpad E14 Gen2:
OK, so at least we know that it's a mainline issue. I'll investigate a
bit and will keep you informed. Thank you so much for all the tests!
--
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/19
Looking at the oops it seems that the stack gets corrupted inside
elantech_change_report_id(), that is defined in
drivers/input/mouse/elantech.c.
According to Stephan it seems that 5.11 is the last kernel that seems to
work.
If we look at the changes between 5.11 and 5.13 that are touching
driver
Hm.. it's not trivial to revert that commit, because it depends on other
subsystem changes. I was thinking that we may actually corrupt the stack
because elantech_create_smbus() is using too much stack. How about
allocating that i2c_props array in the heap. See the patch in attach.
** Patch added:
Hm.. it's not trivial to revert that commit, because it depends on other
subsystem changes. I was thinking that we may actually corrupt the stack
because elantech_create_smbus() is using too much stack. How about
allocating that i2c_props array in the heap. See the patch in attach.
** Patch added:
Test kernel is available here, if you want to give it a try:
https://kernel.ubuntu.com/~arighi/lp1945590/
Thanks!
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Andrea Righi (arighi)
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => High
--
You re
You just need to install linux and linux-modules (sorry I wasn't very
clear). But it looks like my patch didn't make any difference.
I'll investigate a bit more. Thanks for testing!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Also affects: linux-restricted-modules (Ubuntu Impish)
Importance: High
Assignee: dann frazier (dannf)
Status: In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.l
** Description changed:
+ [Impact]
+
+ Impish is missing the nvidia server drivers.
+
+ [Test case]
+
$ apt showsrc linux-restricted-modules | grep -e ^Version: -e server
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
- Version: 5.13.0-16.16
Versio
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
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
Fix for the 5.4 kernel in bionic reported in attach.
** Patch added: "lttng-support-kernel-5.4-without-random-tracepoints.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1986921/+attachment/5614597/+files/lttng-support-kernel-5.4-without-random-tracepoints.debdiff
--
Yo
Hi Brian, we have also experienced this issue during our tests, but it's
really hard to reproduce it on our side.
It seems to be a regression in virtio-rng and I've prepared a test
kernel, but we still haven't found a way to reproduce it systematically,
so I couldn't verify if this test kernel is
Public bug reported:
[Impact]
Align with the latest apparmor and LSM stacking versions.
To do so we need to:
- revert sauce to get back to upstream apparmor, and drop old LSM stacking
- pull in needed patches from upstream 6.0
- pull in needed patches from apparmor-next 6.1
This is required
@zhanglei-mao have you tried to update the kernel? Does it still happen
also with a more recent 5.4?
--
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/1976511
Title:
kernel taint ( warning
Public bug reported:
[Impact]
nvidia-dkms-470 fails to build on kinetic with the new (upcoming) kernel
5.19.
[Test case]
sudo apt install nvidia-dkms-470
[Fix]
Change driver to support the new 5.19 ABI.
[Regression potential]
We may see build issues / regressions in kernels >= 5.19, since t
debdiff in attach fixes all the build failures with kernels >= 5.19.
** Patch added: "support-linux-5.19-nvidia-470.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597189/+files/support-linux-5.19-nvidia-470.debdiff
--
You received thi
same fixes for nvidia-dkms-510.
** Patch added: "support-linux-5.19-nvidia-510.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597215/+files/support-linux-5.19-nvidia-510.debdiff
--
You received this bug notification because you are a
same fixes for nvidia-dkms-470-server
** Patch added: "support-linux-5.19-nvidia-470-server.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597370/+files/support-linux-5.19-nvidia-470-server.debdiff
--
You received this bug notificatio
Fixes for nvidia-dkms-510-server.
** Patch added: "support-linux-5.19-nvidia-510-server.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1978539/+attachment/5597442/+files/support-linux-5.19-nvidia-510-server.debdiff
--
You received this bug notification be
Public bug reported:
[Impact]
bcmwl fails to build on kernel 5.19 with the following errors:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:603:14:
error: implicit declaration of function ‘pci_alloc_consistent’; did you mean
‘osl_dma_alloc_consistent’? [-Werror=implicit-fu
Fix to properly support kernels >= 5.18 in attach.
** Patch added: "bcmwl-support-linux-5.18.debdiff"
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1981968/+attachment/5603690/+files/bcmwl-support-linux-5.18.debdiff
--
You received this bug notification because you are a member of Ker
I think this might be fixed by `55573f3a3f352 tcp: make sure
treq->af_specific is initialized` that is currently applied to
5.4.0-123.139 in focal-proposed.
It'd be great if someone that is able to reproduce the problem could try
to install this new kernel from -proposed and verify if it's still
h
@squirrelsc the next Azure kernel in Focal that will have this fix is
going to be 5.4.0-1087.92, but I don't see it in proposed yet. If it
helps I can upload to a ppa an "unofficial" Azure kernel with the fix.
--
You received this bug notification because you are a member of Kernel
Packages, whic
...or if it's easier, I've just uploaded some debs here:
https://kernel.ubuntu.com/~arighi/lp-1981658/
This kernel (5.4.0-1087.92+arighi) is probably going to be the Azure
kernel in proposed and it includes the fix that I mentioned above.
--
You received this bug notification because you are a m
Also my HP Pavilion 15 Notebook PC (L3S64EA#ABZ) was affected by this
problem, no longer saved the BIOS settings after installing this version
of Ubuntu, I solved as described above, I downloaded and installed the
kernel and carried out the procedure Described with a single reboot.
--
You receive
Same problem for me. I've tried evething but nothing seems work. Only
bluetooth speakers are working fine
--
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/1850439
Title:
No sound on ASUS
I tried to run the 4 commands but nothing seems change. After that I used the
script and now both speaker and microphone works fine on my UX534FTC.
Thank you guys!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
Gosh, I cannot do it. :(
--
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/1299738
Title:
digikam does not start in trusty beta 2amd64
Status in “linux” package in Ubuntu:
Incomplete
Bu
This bug affects quasselclient-qt4 as well. I will perform apport-
collect, hopefully it helps.
--
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/1299738
Title:
digikam does not start in tr
I find it quite *outrageous* that the bug is not considered "confirmed"
anymore. I am confirming it again since it affects multiple users.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
We were talking about a bug which affects >100 users of Ubuntu Saucy
(using the same Samsung hardware), and you decided to mark it as
regarding Quantal in order to say it's invalid. Well, your abuse of
power is quite remarkable, if not offensive.
If this is how you (I mean you, not the Ubuntu team
«Thanks juanmanuel for writing the fix and being so patient with
Ubuntu's ridiculous bug policies»
I think it's more of a one-man trolling issue than a policy problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Public bug reported:
when i check cat /proc/bus/input/devices there is no touchpad device.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.4.0-90-generic 5.4.0-90.101~18.04.1
ProcVersionSignature: Ubuntu 5.4.0-90.101~18.04.1-generic 5.4.148
Uname: Linux 5.4.0-90-generic x86_64
801 - 851 of 851 matches
Mail list logo
