** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1990920
Title:
Fix resume on AMD platforms when TBT monitor is plugged
Status in HWE
Hints removed, marked as fix-released.
** Changed in: ubuntu-kernel-tests
Status: New => 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/1990124
Title:
** Also affects: linux-xilinx-zynqmp (Ubuntu)
Importance: Undecided
Status: New
** Tags added: 5.4 focal
--
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/1992912
Passed with F-gkeop-5.15.0-1005
** Tags added: verification-done-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/1990124
Title:
icmp_redirect.sh in ubuntu_kernel_selftests failed
** Tags removed: stress-smoke-test
** Tags added: ubuntu-stress-smoke-test
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1992641
Title:
stress ng seal regression
Status in
For J-gkeop 5.15.0-1005.7
The failed test case number has reduced to 3:
#27, #30, #150
#27/u atomic compare-and-exchange smoketest - 32bit FAIL
Unexpected success to load!
verification time 32 usec
stack depth 4
processed 23 insns (limit 100) max_states_per_insn 0 total_states 2
There is no flickering in that screen recording.
Please take a video using a phone or a camera.
--
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/1992474
Title:
Flickering started right
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1973676
Title:
flickering and black screen after grub after 22.04
NVIDIA says the fix is coming in driver 525:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2233#note_1575235
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: Confirmed => Won't Fix
**
https://github.com/strace/strace/commit/aeb29a3238ef3cc7f191f98743678d3b4ec949b9
and
https://github.com/strace/strace/commit/a30e5defe41b5b806c223865e92b20d8c9b08f4b
look relevant.
In general, does strace get a release for each kernel release? Should it
be updated in parallel?
** Tags added:
Due to the nature of the issue, I am unable to run the command "apport-
collect 1993078"
** 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.
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 1993078
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
Immediate crash upon entering boot with linux-image-5.4.0-128-generic on
HP Omnibook XE3-GF
Prior versions up to linux-image-5.4.0-126-generic work fine
I 8.3938581 Hardware name: Hewlett-Packard HP OmniBook PC GF M1 14 11/27/2002
[ 8.3931371 EIP: switch_to_asm+0x44/0x54
So the issue is that I am only able to boot via CTRL + ALT + DEL from the
splash screen with Gigabyte motherboard logo and from there via recovery mode
only.
With Kernel 5.19.0-15 up to 5.19.0-19 after recovery mode a 'Resume normal
boot' screen appears and from there a normal boot occurs.
Which was already the issue reported in the present Bug.
But since Kernel 5.19.0-21 was installed yesterday, then even selecting
recovery mode does not work at all any longer. After the 'Resume normal boot'
screen by hitting OK, the next screen is a white blinking cursor.
Typing CTRL + ALT +
Absolutely.
** Attachment added: "Ubuntu desktop from live system (downloaded Oct 16th
2022)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990750/+attachment/5624410/+files/IMG_20221016_220018.jpg
--
You received this bug notification because you are a member of Kernel
Packages,
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/1993071
Title:
dmesg -l err iwlwifi Intel(R)
** Summary changed:
- iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430
+ dmesg -l err iwlwifi Intel(R) Wireless-AC 9560 160MHz, REV=0x430
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
lots of iwlwifi errors in dmesg.
loaded firmware version 73.35c0a2c6.0 so-a0-jf-b0-73.ucode op_mode
iwlmvm
firmware didn't ACK the reset - continue anyway
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-modules-iwlwifi-generic 5.15.0.50.50
ProcVersionSignature:
50 and 48 out of order, no workaround works. My pc is dead, i'm writing
from my phone.
--
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/1992679
Title:
Can not login after new kernel
I can replicate this on my Dell XPS13 9380 (no encryption). Occurs as well with
Ubuntu 20.04 LTS, but not with 18.04 LTS, so not sure if it is related to the
same reason?
-> Disabling Secure Boot and SGX did not resolve the issue
--
You received this bug notification because you are a member
Public bug reported:
I had to revert back to 515.65 via GRUB history or something on 22.10
because all I'm seeing is black screen. I originally stumbled onto this
exact issue with KDE Neon Unstable 22.04.
It appears that it affects both nvidia-driver-515 & nvidia-
driver-515-open 515.76
Now that the kernel is fixed, we can see a different error:
gcc -DHAVE_CONFIG_H -I./linux/x86_64 -I../../src/linux/x86_64
-I./linux/generic -I../../src/linux/generic -I. -I../../src -DIN_STRACE=1
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Wno-missing-field-initializers
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/1993052
Title:
iwlwifi Not valid error log
Hi Christopher,
I came across this bug on 5.10.124 ( Amazon Linux 2 on AWS ECS ).
Perhaps it was fixed on a later version?
--
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/1924298
Title:
Public bug reported:
For some reason, Ubuntu gets glitched where the Bluetooth works but WiFi
does not even show up. If I reboot into Windows, it is a similar issue
(wifi does not show up, but device manager shows Code 10. If I disable
and enable the adaptor Intel Wireless AC 9560, it sometimes
26 matches
Mail list logo
