--
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/1936678
Title:
Samsung Laptop support module doesn't load
Status in linux package in Ubuntu:
Won't Fix
Bug description:
This is
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_gige driver shutdown() is invoked during reboot
processing, but the stop() logic is not guaranteed to execute
on all distros. If stop() does not execute NAPI remains enabled
during system shutdown and can cause an exception if NAPI is
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_gige driver encounters a NULL pointer exception in
mlxbf_gige_open() when kdump is enabled. The exception happens
because there is a pending RX interrupt before the call to
request_irq(RX IRQ) executes. Then, the RX IRQ handler fires
Public bug reported:
SRU Justification:
[Impact]
The support for mlxbf_gige pause frame counters was added to Jammy
via a SAUCE patch. After upstream review, a small issue was fixed
that makes the SAUCE patch different from the upstream commit.
[Fix]
The fix is to replace the SAUCE patch in
Public bug reported:
SRU Justification:
[Impact]
The BlueField-2 and BlueField-3 silicon designs include a
provision for reporting pause frame counters, but the driver
(mlxbf_gige) does not have software support yet.
[Fix]
The fix is to update the mlxbf_gige driver to support the
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 2455 F wireplumber
/dev/snd/controlC1: david 2455 F wireplumber
/dev/snd/seq:david 2438 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
Dmesg log from OEM kernel
** Attachment added: "dmesg_out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+attachment/5748485/+files/dmesg_out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
lsusb output
** Attachment added: "lsusb_out"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049938/+attachment/5748486/+files/lsusb_out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
When you connect the headset which is based on Bluetooth LE it connects
and then almost immediately disconnects. This does not happen when
using the 6.5.0-1009-oem kernel Can you poirt whatever changes to
bluetooth from the oem kernel to the generic as the cutomer will not
Public bug reported:
SRU Justification:
[Impact]
A regression has been introduced in the latest 22.04 kernel by including
the following two commits:
revert "UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
addition of upstream "mlxbf_gige: fix receive packet race condition"
Public bug reported:
SRU Justification:
[Impact]
There is a SAUCE patch that addresses a mlxbf-gige RX race condition
"UBUNTU: SAUCE: Fix OOB handling RX packets in heavy traffic"
This SAUCE patch should be reverted and replaced with upstream content.
[Fix]
Bring in the following upstream
Public bug reported:
SRU Justification:
[Impact]
There is a gap in the mlxbf-bootctl driver logic, resulting in failure to
report when a secure boot enabled card is using development keys. The program
will instead report lifecycle state as "GA Secured" which is misleading.
[Fix]
Bring in the
I assume you mean to run this
journalctl -k > journal_good.txt
from the working journal?
--
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/2042075
Title:
Black screen at login after
** Attachment added: "journal_good.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716723/+files/journal_good.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hope these help!
** Attachment added: "journal_good.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716137/+files/journal_good.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "journal_bad.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2042075/+attachment/5716136/+files/journal_bad.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Dell Inspiron AMD A10 Laptop
Linux Mint Mate O/S
After updating the kernel I restarted the laptop. After entering my
password and logging in the screen goes black with occasional flashes
of, I guess i'd call it static.
The same thing happened with the previous kernel I
Just in case I should add the kernels that caused the problem for my
laptop are Linux kernel 5.15.0-88.98, and 5.15.0-87
--
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/2042075
Title:
I'm experiencing the same issue as well.
I'm using an Asus TUF A15 with an RTX 4050.
Gnome crashes when using multiple screens with Firefox and the file
explorer.
One tip is to debug 'the frozen screen' by changing the screen order in
Settings > Display.
Best regards,
--
You received this
** Changed in: linux-meta-oracle (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/2035135
Title:
Oracle Cloud systems not
This appears to have been resolved as of 5.15.0.1044.39:
apt-cache policy linux-oracle
linux-oracle:
Installed: 5.15.0.1044.39
Candidate: 5.15.0.1044.39
Version table:
*** 5.15.0.1044.39 500
500 http://iad-ad-3.clouds.archive.ubuntu.com/ubuntu jammy-updates/main
amd64 Packages
Public bug reported:
SRU Justification:
[Impact]
The Mellanox BlueField power driver (pwr-mlxbf) has a dependency
on either the BlueField-2 or BlueField-3 GPIO driver. The current
Kconfig does not have the BlueField-3 dependency.
[Fix]
There is an upstream commit that extends the Kconfig to
Public bug reported:
(Please forgive my ignorance of the kernel release process, maybe I've
gotten this all wrong.)
There have been several kernel releases for Jammy lately but the two
systems I have on Oracle Cloud (one amd64 and one arm64) have not been
receiving updates since kernel
Public bug reported:
When doing a kernel make in our Jammy repo we notice the follow error
being emitted:
./scripts/pahole-flags.sh: line 7: return: can only `return' from a
function or sourced script
It appears that while the Jammy baseline is 5.15.99 (as per the top-level
Makefile)
the file
Public bug reported:
SRU Justification:
[Impact]
The mlxbf_bootctl BlueField platform driver in the Jammy repo
consists of some SAUCE patches. These need to be replaced.
[Fix]
The fix is to revert the four SAUCE patches, replacing them with
upstream commits for the same functionality. One
@kleber-souza do you have any reference for which kind of bugs were
resolved between 5.15.0-73-generic and 5.15.0-76.83 that might have
addressed this? Our testing indicates that the newer kernel version is
stable. It would be good to know what specifically caused this issue
--
You received this
-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 4017 F wireplumber
/dev/snd/controlC1: david 4017 F wireplumber
/dev/snd/seq:david 4013 F pipewire
CRDA: N
Thanks, we are trying out the jammy kernel to confirm it resolves the
issue. Will report back
--
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/2026229
Title:
Crashing issue with 5.15
** Description changed:
We have been working on making self-hosted GitHub actions runners
available in Canonical and have encountered an issue which seems to be
- with the kernel. This is a doc with more details:
- https://docs.google.com/document/d/1E00rlT12Cu-h99do80Qge-
-
Public bug reported:
We have been working on making self-hosted GitHub actions runners
available in Canonical and have encountered an issue which seems to be
with the kernel. This is a doc with more details:
https://docs.google.com/document/d/1E00rlT12Cu-h99do80Qge-
@Samer Attrah (samerattrah)
I had exactly the same problem that you have, I solved it by disabling secure
boot from bios.
(to have permission to disable secure boot I also had to set a supervisory
password from bios as well).
--
You received this bug notification because you are a member of
: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 4450 F pulseaudio
CasperMD5CheckResult: unknown
Date: Tue Jun 13 09:45:54 2023
Dependencies:
DuplicateSignature:
package:linux-libc-dev:5.15.0-72.79
Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.2) over
I am experiencing a similar issue, but I'm not sure if it's the same or
not. What I experience is that *if I boot with the second monitor
attached*, once I unplug it, it will never be detected again. However,
if I boot with the second monitor unattached, and then plug it in, I can
consistently
Public bug reported:
Found after updating from 20.04 to 22.04
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: libnvidia-gl-390 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-72.79-generic 5.15.98
Uname: Linux 5.15.0-72-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
In Tomcat versions 9.0.56 to 9.0.58, this message was sometimes emitted
in error; this was fixed in 9.0.59. Since 9.0.63, the log message also
explicitly recommends to use Kernel 5.10 or later, but I am not seeing
that in any of the logs reported here, so these Tomcat versions must be
older than
I am seeing this same issue (static screen) on a fully updated Jammy
system. It is a Beelink Renoir system and I have two external monitors
plugged in via HDMI.
It seems to happen fairly randomly, but most often after the monitors go
to sleep and then are woken up. It resolves itself eventually
FWIW, the fix mentioned earlier is indeed in Kernel 5.10-RC6 and later:
https://github.com/torvalds/linux/commit/01770a166165738a6e05c3d911fb4609cc4eb416
But if people are hitting it with e.g. a 5.15 Kernel, then... that fix
didn't fix it ;)
--
You received this bug notification because you are
I believe I fixed this in my case by installing the latest DispayLink
drivers from https://www.synaptics.com/products/displaylink-
graphics/downloads/ubuntu. You may also find choosing the not-latest
kernel in the boot menu will help.
--
You received this bug notification because you are a
x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 3982 F wireplumber
/dev/snd/controlC1: david 3982 F wireplumber
/dev/snd/seq:david 3979 F pipewire
CRDA: N/A
CasperMD5CheckResult
Windows was installed but it’s removed now. I have seen suggestions to
create a bootable usb to disable the WiFi adapter but I’m not sure if
that would work
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
@Matthew No luck i'm afraid I removed the module and I'm still getting
the same issue. @Jeremy is there any other steps I can try ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
I have removed the backports and now i'm getting this:
sudo dmesg |grep -i wifi
[3.412202] Intel(R) Wireless WiFi driver for Linux
[3.412300] iwlwifi :00:14.3: enabling device ( -> 0002)
[3.525445] iwlwifi :00:14.3: CSR_RESET = 0x10
[3.525473] iwlwifi :00:14.3:
Alos seeing this:
[2.691388] iwlwifi_compat: loading out-of-tree module taints kernel.
[2.698204] Loading modules backported from iwlwifi
[2.698208] iwlwifi-stack-public:master:9904:0e80336f
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
After upgrading from 22.04 to 23.04 the intel wifi driver is not
loading, I am seeing the following in dmesg:
[ 215.024382] Loading of unsigned module is rejected
[ 262.051998] [ cut here ]
[ 262.052001] WARNING: CPU: 2 PID: 6946 at
In my case, they did not.
On Tue, Apr 25, 2023 at 4:01 AM homerlinux <1969...@bugs.launchpad.net>
wrote:
> May be, by any chance, that your zvols contain LVMs?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1969457
>
Users of our software (singularity) were affected by this issue.
https://github.com/sylabs/singularity/issues/1499
For historic reasons (old kernels without /dev/loop-control), we have
been creating /dev/loopXX devices directly via mknod, if needed, before
using them.
After the backport of
prl_fs prl_tg
ApportVersion: 2.26.0-0ubuntu2
Architecture: arm64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david-noble 1659 F wireplumber
/dev/snd/seq:david-noble 1656 F pipewire
CasperMD5CheckResult: pass
Date: Fri Mar 31 14:47:08 2023
I'm on the latest kernel for 22.04 and I still can't get the wifi driver
to load I keep seeing the following:
[ 3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="man_gr
off" pid=522 comm="apparmor_parser"
[ 3.960935]
Public bug reported:
sudo cat /sys/kernel/debug/usb/devices
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 2
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 5.19
S: Manufacturer=Linux
Public bug reported:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo contains SAUCE
patches that enable BlueField-3 support. This same functionality
is contained in upstream commits and Jammy repo should utilize them.
[Fix]
The BlueField-3 support will be provided
Thanks, I think I'm now using 5.19.0-35 with the new driver. I'll
monitor for crashes. Is there anything in particular I should look for
in "journalctl -k -b"?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
To the best of my knowledge, I followed the steps you outlined cloning
both repos and installing/cp'ing the files. I've double checked the
firmware files exist. When I run "update-grub" just to check, I see
Found linux image: /boot/vmlinuz-6.0.0-1012-oem
Found initrd image:
I attempted this and booted into kernel 5.19.0-32-generic however I then
had no wifi at all. The option to connect no longer existed in the top
right corner.
Prior to this, it failed in the same way, with Microcode SW error
detected, a second time today. It does seems like it happened less often
I see the exact same issue with spotify, Ubuntu 22.04 and kernel: Linux
atomic 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb
17 15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux and I have a Lenovo
P14s and CPU model name: AMD Ryzen 7 PRO 5850U with Radeon Graphics
--
You
Public bug reported:
Hi,
As of linux-azure-5.4.0.1104 in Ubuntu Bionic (Azure) we are seeing
Docker images fail to start / hang. These images mount NFS and CIFS
shares into them as volumes, which I suspect might be related. I see
many NFS-related changes in this new kernel version's changelog.
] ieee80211 phy0: Hardware restart was requested
[88202.645822] usb 3-1.2: USB disconnect, device number 21
[88856.851319] perf: interrupt took too long (3195 > 3173), lowering
kernel.perf_event_max_sample_rate to 62500
$ uname -a
Linux david-XPS-9320 5.19.0-32-generic #33~22.04.1-Ubuntu
Can we get a confirmation if this issue will be fixed at some point or
can we get a workaround ?
--
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/1874241
Title:
iwlwifi intel
This has been going on for a while but since the last linux firmware
update the ax201 card is not working at all.
--
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://bugs.launchpad.net/bugs/2008706
Public bug reported:
[3.837973] audit: type=1400 audit(1677506792.544:10): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="man_gr
off" pid=522 comm="apparmor_parser"
[3.960935] iwlwifi :00:14.3: CSR_RESET = 0x10
[3.960965] iwlwifi :00:14.3: Host monitor
@Erwin (erwin-gaubitzer-6)
Spot on - thank you.
--
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/1485246
Title:
Backlight issue - Samsung Chronos 7 (model - NP770Z5E)
Status in linux
k is more an
hardware problem triggered or a driver error.
Anyone have an idea of what it could be ?
Thanks in advance
Have a good day.
David
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007853/+subscriptions
--
Mailing list: https://
k is more an
hardware problem triggered or a driver error.
Anyone have an idea of what it could be ?
Thanks in advance
Have a good day.
David
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007853/+subscriptions
--
Mailing list: htt
g.
It surprising me to keep the problem in grub menu so I think is more an
hardware problem triggered or a driver error.
Anyone have an idea of what it could be ?
Thanks in advance
Have a good day.
David
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
for hardware decoding
I can see it on syslog nothing else.
Nothing in xorg log.
It surprising me to keep the problem in grub menu so I think is more an
hardware problem triggered or a driver error.
Anyone have an idea of what it could be ?
Thanks in advance
Have a good day.
Dav
em triggered or a driver error.
+ It surprising me to keep the problem in grub menu so I think is more an
hardware problem triggered or a driver error.
Anyone have an idea of what it could be ?
Thanks in advance
Have a good day.
David
--
You received this bug notification because you a
it could be ?
Thanks in advance
Have a good day.
David
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: i915 xorg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
Maybe the same as
https://lore.kernel.org/lkml/CANn89iJxiV_-g6n60aeA=mO=DYwGV9VdJswHP4pc-
vwq_ug...@mail.gmail.com/T/ ?
--
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/1962485
Title:
The log was attached
** Attachment added: "stress-ng_0.15.04-1~j_amd64_log.txt"
https://bugs.launchpad.net/ubuntu/+source/stress-ng/+bug/1999731/+attachment/5647719/+files/stress-ng_0.15.04-1~j_amd64_log.txt
--
You received this bug notification because you are a member of Kernel
Packages,
Test with stress-ng_0.15.04-1~j_amd64 + ubunut 22.04(5.15.0-58-generic)
+ Micron_7450_MTFDKCB3T8TFR -> Passed
--
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/1999731
Title:
disk stress
I've tested the patch on kernel 5.15.0-57.63 and it solves the issue for
me.
Aleksandr - Andrea asked you in your kernel-team thread to rebase the
patch on master-next, hopefully if you can do this it'll be accepted.
Keen to see this issue fixed in jammy as it's breaking Docker+Sysbox
containers
Public bug reported:
Since installing the latest kernel update on bionic (4.15.0-201), ls
prints an error message for every btrfs read-only file system in the
target directory.
How to reproduce:
On a btrfs file system in any directory, run:
- sudo btrfs su cr testsubvol
- sudo btrfs su sn -r
Test with stress-ng_0.13.12-2ubuntu1_amd64.deb -> Passed
27 Dec 03:53: Running stress-ng locka stressor for 240 seconds...
stress-ng: info: [3300189] setting to a 240 second (4 mins, 0.00 secs) run per
stressor
stress-ng: info: [3300189] dispatching hogs: 176 locka
stress-ng: info: [3300189]
FWIW I'm now running Ubuntu 22.04 in Legacy mode and finding the
workaround satisfactory.
ls -lh /boot/initrd*
lrwxrwxrwx 1 root root 28 Dec 1 13:56 /boot/initrd.img ->
initrd.img-5.15.0-56-generic
-rw-r--r-- 1 root root 107M Nov 30 11:46 /boot/initrd.img-5.15.0-53-generic
-rw-r--r-- 1 root
I have this issue after suspend/resume on Ubuntu 20.04 LTS, kernel
5.15.0, Dell Precision 5540 with an Intel Core i9-9980HK processor.
lsusb shows the device:
Bus 001 Device 025: ID 8087:0029 Intel Corp
Which is an Intel AX200 Bluetooth wireless chip.
Suspending and resuming my laptop once more
Similarly, I was in a video call (via Chromium snap), tried to switch to
slack to check messages that just came in, and GUI locked up (but audio
continued for several minutes).
journald had a ton of these messages:
Nov 18 10:41:11 tippin kernel: amdgpu :05:00.0: amdgpu: [mmhub0] no-retry
Running "Ubuntu 22.04.1". After updating today, was unable to fully
boot. Screen goes black, unable to get to a terminal. Booted into
5.15.0-52 to report/confirm issue. Please instruct.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo does not yet
support the BlueField-3 SoC. The "mlxbf_gige" driver which
supports BlueField-2 SoC currently will be extended to include
the BlueField-3 support.
[Fix]
The BlueField-3 support will
It seems only 5.15 was the problem. I can confirm it to work on most of
the next major versions: I tried the latest of each series, 5.17.x,
5.18.x, 5.19.x and finally 6.0.0 and 6.0.1 and it works on all of them.
--
You received this bug notification because you are a member of Kernel
Packages,
Maybe related to this https://github.com/mate-desktop/mate-
desktop/issues/519
** Bug watch added: github.com/mate-desktop/mate-desktop/issues #519
https://github.com/mate-desktop/mate-desktop/issues/519
--
You received this bug notification because you are a member of Kernel
Packages, which
** 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...).
Public bug reported:
SRU Justification:
[Impact]
The following upstream commit was recently added to Jammy:
3a1a274e933f mlxbf_gige: compute MDIO period based on i1clk
This patch added driver logic that includes a "devm_ioremap"
call, but the error handling logic pertaining to this call
is
Sorry as this has become confusing. This bug does still apply to Jammy
linux-bluefield,
and the fix is contained in a patch series that I sent in yesterday:
v3--cover-letter.patch
v3-0001-UBUNTU-SAUCE-Revert-UBUNTU-SAUCE-mlxbf_gige-clear.patch
This bug is within the Jammy repo of the BlueField project (22.04).
I sent in the patch with a subject line containing this prefix:
"[SRU][F:linux-bluefield]" Is that relevant for 22.04 patches,
or should the "F" be replaced with something to signify Jammy?
--
You received this bug
Public bug reported:
SRU Justification:
[Impact]
The Jammy repo contains the following SAUCE patch:
UBUNTU: SAUCE: mlxbf_gige: clear MDIO gateway lock after read
This patch is now in mainline Linux kernel, so the SAUCE patch
can be reverted and replaced with the upstream commit SHA.
[Fix]
Public bug reported:
SRU Justification:
[Impact]
The BlueField-2 GIGE logic accesses the MDIO device via reads/writes
to a gateway (GW) register. The MDIO GW lock is set after read. Make
sure to always clear to indicate that the GW register is not being used.
If the lock is mistakenly
Unfortunately I'm unable to access terminal
at this point when I boot I can only access the GNU GRUB menu is there
any other way I can get those files?
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: david 1396 F pulseaudio
/dev/snd/controlC1: david 1396 F pulseaudio
/dev/snd/pcmC1D0p: d
-5.15.0-46-generic 5.15.0-46.49
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/control
I upgraded via do-release-upgrade -d
With 5.15.0-41-generic the webcam works! At least in Chrome/Firefox.
However wifi becomes unreliable and disconnects after some time. I will
confirm that this is reproducible later. For now, it doesn't look like a
viable solution for me.
I had installed the
The XPS 13 Plus 9320 webcam does not work for me since upgrading to
22.04 from the original 20.04 OEM installation.
BIOS: 1.4.0
Kernel:5.17.0-1013-oem
libcamhal-ipu6ep0 is installed from the mentioned PPA
v4l2-ctl --list-devices
Intel MIPI Camera (platform:v4l2loopback-000):
/dev/video0
Independent confirmation from me, with the same symptoms:
updated from kernel 5.13 to 5.15 today. After rebooting the system hangs
at "Loading ramdisk". I reverted to 5.13 and it started properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Apologies in advance if I don't use the right syntax or formatting here;
I'm pretty new to Linux and this bug reporting process. I believe I am
seeing the same symptoms running 5.15.0-41-generic #44-Ubuntu SMP Wed
Jun 22 14:20:53 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux on Lubuntu
22.04. The sound
** Also affects: linux-signed-hwe-5.15 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1981590
Title:
Kernel 5.15
While experimenting with FreeDOS and Windows PE, I discovered that
disabling UEFI mode (switching to Legacy mode) means I can now boot into
kernel 5.15. Certainly not a solution, but at least a workaround.
--
You received this bug notification because you are a member of Kernel
Packages, which
Independent confirmation from me, with the same symptoms:
updated from kernel 5.13 to 5.15 today. After rebooting the system hangs
at "Loading ramdisk". I reverted to 5.13 and it started properly.
--
You received this bug notification because you are a member of Kernel
Packages, which is
$ ls -lh /boot/initrd*
lrwxrwxrwx 1 root root 28 Jul 13 07:55 /boot/initrd.img ->
initrd.img-5.15.0-41-generic
-rw-r--r-- 1 root root 108M Jul 13 07:54 /boot/initrd.img-5.13.0-52-generic
-rw-r--r-- 1 root root 117M Jul 13 07:55 /boot/initrd.img-5.15.0-41-generic
lrwxrwxrwx 1 root root 28 Jul
Tried removing modifying /etc/default/grub by setting
GRUB_CMDLINE_LINUX_DEFAULT to "" (was "quiet splash")
Results:
- 5.13: spews lots of logs, no splash screen when prompted for disk
encryption passphrase
- 5.15: still hangs at the same place, no logs
--
You received this bug notification
** Summary changed:
- Computer hangs at boot
+ Kernel 5.15 hangs at "Loading initial ramdisk"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1981590
Title:
Kernel 5.15
No extra info available, once I get the following message, no keys
respond (e.g. NumLock cannot switch state). The same happens for the
"recovery mode" option.
Loading Linux 5.15.0-41-generic ...
Loading initial ramdisk ...
_
--
You received this bug notification because you are a member of
Result of dpkg -l | grep '^ii linux':
```
ii linux-base 4.5ubuntu3.7
all Linux image base
package
ii linux-firmware 1.187.32
1 - 100 of 2664 matches
Mail list logo
