Thank you very much for the reply. Another question is try_get_page
returns -ENOMEM but kvm warning is bad address which should be EFAULT.
Why qemu prints error log says bad address?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
OK that didn't work. We can't usually handle crash files as
attachments... Please report the crash file again by running:
ubuntu-bug _usr_bin_gnome-shell.1002.crash
or
apport-cli _usr_bin_gnome-shell.1002.crash
from the machine.
** Changed in: gnome-shell (Ubuntu)
Status: New => In
This bug is solved. The above comments probably belong in bug 2006370,
not here.
--
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/1965882
Title:
[nouveau] External monitor plugged into (se
Three observations:
- Crashing in nouveau_dri.so which shouldn't be used at all when the
proper Nvidia driver is installed.
- Unexplained crashes in cogl_blit_framebuffer() is something I've seen
before when working on Nvidia multi-GPU support. So that sounds
relevant; https://gitlab.gnome.org/GN
You have been subscribed to a public bug:
When logged into a desktop session, I created a new user account and
then tried to "switch to" it. A new gnome session started for that user
(test1), but after a few seconds, gnome-shell appears to have crashed.
This only seems to happen on the first attem
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1009.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-jammy' to 'verification-done-jammy'. If the
problem still exists,
** Also affects: linux-kvm (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: linux-kvm (Ubuntu)
Status: New => Fix Released
** Changed in: linux-kvm (Ubuntu Bionic)
Status: New
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/2015836
Title:
package linux-image-unsigned-6.2.0-19-generic (not installed) failed
to install/upgra
All autopkgtests for the newly accepted
linux-restricted-modules-lowlatency-hwe-5.15 (5.15.0-70.77~20.04.1) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit
[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
Public bug reported:
Cannot log in (no keyboard input on login screen) with 6.2.0-19 but can
with 6.2.0.18.
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-image-unsigned-6.2.0-19-generic (not installed)
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-
Same problem...
I have an Aspire A515-57 and i am running into the same issue :/
I have tried replicating the steps from #19, but didn't manage to fix it.
Probably due to my lack of experience using Linux. Mine is the 0408:4033
BTW could any of you gentlemen do a more detailed step-by-step or vid
** Tags added: sru-20230320
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1848004
Title:
test_maps from ubuntu_bpf failed with sockmap creation on B/D-KVM
Status in ubuntu-kernel-t
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15
(5.15.0-70.77~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit the excuses
All autopkgtests for the newly accepted linux-restricted-modules-hwe-5.15
(5.15.0-70.77~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit the excuses
This bug is awaiting verification that the linux-kvm/5.19.0-1021.22
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-kinetic' to 'verification-done-kinetic'. If the
problem still exists
Hi @krglosse,
We have opened a bug to address the performance issue related to NFS.
You can find more details about the bug at this link:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015827.
We have also sent a proposal to upstream for their consideration, but
unfortunately, we have no
This bug is awaiting verification that the linux-gke/5.15.0-1031.36
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, ch
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-70.77~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem stil
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-70.77~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem stil
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => ChengEn, Du (chengendu)
** Changed in: linux (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
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 2015827
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
The performance issue that has been observed may be attributed to an increase
in NFS ACCESS operations, possibly due to a new mechanism introduced in the
Linux 6.2-rc3 NFS client side.
This mechanism clears the access cache as soon as the cache timestamp becomes
older than
hey @xijunli ! Could you please test that the driver now works as
expected? I have placed the files here
https://kernel.ubuntu.com/~lukenow/lp2012335/ , but you should only need
to install the modules. Let me know if that works for you
Thanks,
- Luke
--
You received this bug notification becaus
This bug is awaiting verification that the linux-
allwinner/5.19.0-1010.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-kinetic' to 'verification-
done-kinetic'. If the problem stil
This bug is awaiting verification that the linux-starfive/5.19.0-1015.17
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-kinetic' to 'verification-done-kinetic'. If the
problem still e
This bug is awaiting verification that the linux-riscv/5.19.0-1016.17
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-kinetic' to 'verification-done-kinetic'. If the
problem still exis
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Assignee: (unassigned) => Kamal Mostafa (kamal
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
This bug is awaiting verification that the linux-
snapdragon/4.15.0-1148.158 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-bionic' to
'verification-done-bionic'. If the problem still
Additional logs:
- Before executing above mv command:
[ 18.502463] Intel(R) Wireless WiFi driver for Linux
[ 18.502891] iwlwifi 0004:41:00.0: enabling device ( -> 0002)
[ 18.543590] iwlwifi 0004:41:00.0: api flags index 2 larger than supported by
driver
[ 18.543628] iwlwifi 0004:41:00
Hello, I have the same problem, with a lot of linux-firmware versions.
I have found this issue also with
linux-firmware-20220329.git681281e4-0ubuntu3.12.
After upgrading linux-firmware lib, I always have to use this command
`sudo mv /usr/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
/usr/lib/firmware/iwl
System is not booting so I'm not able to run the script.
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/2015794
Title:
Hi ChengEn, Du,
Do we have another issue opened to address the NFS mechanism and the
performance impacts it has on the kernel? We cannot move to the new
kernel currently because of these issues so I just want to make sure we
are continuing to push a solution forward. Thank you!
--
You received t
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 2015794
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Regression started from linux kernel 6.2
[57.794591] atomisp-isp2 :00:03.0: atomisp: Error -2 while requesting
firmware shisp_2401a0_v21.bin
^ this line was present in dmesg on the old kernels too
[57.851197] atomisp-isp2 :00:03.0: IUNIT power-off timeout.
[57.85308
The proposed fix is to include those above two symlink in linux-headers
package for compatibility
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2015776
Title:
5.17.0-102
Public bug reported:
The VMWare kernel modules required to use VMWare Workstation(the specific
version is 16.2.5 build-20904516) used to work in past by 3rd party script
automatically compiling modules with DKMS. Since some time it's broken due to
the DKMS triggered scripts looking for files:
`
Just updated to:
5.19.0-38-generic #39~22.04.1-Ubuntu
The same issue persists.
--
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/2012366
Title:
NMI: IOCK error on HP MicroServer Gen8 afte
** Package changed: ubuntu-release-upgrader (Ubuntu) => bluez (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2009910
Title:
After updrade (apt), my bluetooth headset microphone
You have been subscribed to a public bug:
Stop working after that upgrade.
Start-Date: 2023-03-09 19:39:40
Commandline: packagekit role='update-packages'
Requested-By: kea (1000)
Upgrade: udev:amd64 (251.4-1ubuntu7, 251.4-1ubuntu7.1),
xscreensaver-screensaver-bsod:amd64 (6.02+dfsg1-2ubuntu1,
6
Apparently, the check for (non-ignored) modules might be inexact? as both
'mstflint_access' and 'nvidia-fs' are in the linux-modules-*-nvidia deb package.
(Note: this is just a su-guess-tion :) I haven't looked at it.)
$ dpkg-deb -c linux-modules-5.15.0-1017-nvidia_5.15.0-1017.17_amd64.deb | grep
Public bug reported:
II: Checking modules for nvidia...
read 12 modules.
reading new modules...read 6315 modules.
reading old modules...
MISS: icp (ignored)
MISS: mstflint_access
MISS: nvidia-fs
MISS: spl (ignored)
MISS: v4l2loopback (ignored)
MISS: zavl (
Public bug reported:
[Impact]
This patch set is intended to address
https://bugs.launchpad.net/riverside/+bug/2011636
** Affects: linux-nvidia (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which i
Hello, I have the same problem, with a lot of linux-firmware versions.
I have found this issue also with
linux-firmware-20220329.git681281e4-0ubuntu3.12.
After upgrading linux-firmware lib, I always have to use this command
`sudo mv /usr/lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm
/usr/lib/firmware/iw
I just removed my WF-1000XM4 from my device list and paired them again.
Now I have "High Fidelity Playback (A2DP Sink, codec LDAC)" and it was selected
by default.
I have no idea what changed. bluez is still 5.64 since 2022-08-28. Maybe
it's related to the blueman update from 2.3.4 to 2.3.5 on 20
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.19 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
https://b
Hello everyone,
I have been following this thread for a while now, but have not yet seen
others report the same thing I am experiencing. I am using an LG Gram
14Z90Q-G.AA76B and have experienced high CPU usage from kworker threads
on every distro I have tried (Fedora, ArchLinux, VanillaOS, Ubuntu)
I just noticed that we have this hint for Lunar as well, I will revert
the bug status to incomplete to verify it.
** Changed in: ubuntu-kernel-tests
Status: Fix Released => Incomplete
** Changed in: linux (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification
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 2015741
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
Issue found on 6.2.0-20.20 ARM64 instances.
Looks like the memfd:run_fuse_test.sh will never finish properly and the
whole test will be interrupted abnormally.
Test log:
Running 'make run_tests -C memfd TEST_PROGS=run_fuse_test.sh TEST_GEN_PROGS=''
TEST_CUSTOM_PROGS='''
m
It still happens with 5.19.0-38-generic. alsa-info says:
!!Soundcards recognised by ALSA
!!-
0 [NVidia ]: HDA-Intel - HDA NVidia
HDA NVidia at 0xa308 irq 17
!!PCI Soundcards installed in the system
!!
Checked with K-5.19, K-lowlatency-5.19, J-hwe-5.19 and J-hwe-
lowlatency-5.19. This issue does not exist anymore, therefore I am
closing this bug.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => Fix Released
I see that if I disable "Automatic screen lock", it does not happen any
more, even if the screen goes blank for a long time.
--
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/1978980
Title:
This issue seems to be fixed with 5.19.0-40 this cycle (sru-20230320)
--
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/2000778
Title:
pmtu.sh in net from ubunut_kernel_selftests crash SUT
65 matches
Mail list logo
