Public bug reported:
I use Huawei Mate Book e 2022，the Intel graphics devices is Intel Iris
Xe （Intel Corporation Device [8086:9a40]）. But the kernel didn't
support, I have to use the params with nomodeset, i can't change
brightness. Also /sys/class/backlight/ is empty.
** Affects:
*** This bug is a duplicate of bug 1958283 ***
https://bugs.launchpad.net/bugs/1958283
** This bug has been marked a duplicate of bug 1958283
linux-firmware missing renoir_ta
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
sometimes the problem gets fixed on restart. Sometimes not. Touchpad
stops working in the middle of regular operation
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1
ProcVersionSignature: Ubuntu
*** This bug is a duplicate of bug 1893956 ***
https://bugs.launchpad.net/bugs/1893956
@thomas955 - the i40 driver in 4.15 will not be updated. You may want to
try the 5.4 HWE kernel for 18.04 which I think should include the
patches to enable the x710-T2L. We only pulled the support back as
** Tags added: servcert-187
--
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/1956982
Title:
Update Broadcom Emulex FC HBA lpfc driver to 14.0.0.4 for Ubuntu 22.04
Status in linux package
This bug is awaiting verification that the linux-azure/5.4.0-1070.73
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 still exists,
This bug is awaiting verification that the linux-azure/5.4.0-1070.73
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 still exists,
Public bug reported:
nil
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-dkms-450 450.102.04-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
Thanks for the bug report. Please run these commands:
lspci -k > lspci.txt
lsusb > lsusb.txt
journalctl -b0 > journal.txt
and attach the resulting text files here.
** Summary changed:
- Bluetooth headset not detected by bluetoth
+ Sony WF-XB700 Bluetooth headset not detected
** Also
Harry,
I'm still working to reproduce this, without success. I have set
the .autoconf sysctl to 0 (which controls creation of local addresses in
response to received Router Advertisements), as well as setting
.addr_gen_mode to 1 (to disable SLAAC (fe80::) addresses).
In any
Hi Wouter,
Thanks for helping test Jammy.
Looking at your lsusb, it seems you do have the affected 8087:0a2a bluetooth
device.
$ lsusb
...
Bus 001 Device 007: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
...
The mailing list thread [1] mentions it is fixed by the following
commit:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-hwe-5.13 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
Hi Juerg,
Installing the new firmware fixes it.Got some error messages but now I am on
5-13.0-28
Thank you for the support.
** Attachment added: "Screenshot_2022-02-09_22-51-01.png"
** Description changed:
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
** 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
+
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Impish)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu)
Status: Confirmed
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
Just did a fresh install of 20.04.3 LTS, updated & installed linux-
generic-hwe-20.04 and it booted up just fine. Only difference is
/etc/default/grub on a client's appliance, this is the default/grub on
the machine that freezes:
# If you change this file, run 'update-grub' afterwards to update
#
Hi Tim,
i also can confirm that 5.4.0-99.112 fixes the bug. Testscript runs for
more than a hour with this kernel without freezing the machine.
Thanks!
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a
Public bug reported:
I had multiple failed installs back to back.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-kernel-source-470 470.103.01-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-28-generic x86_64
ApportVersion:
** Changed in: linux (Ubuntu)
Assignee: Krzysztof Kozlowski (krzk) => Joseph Salisbury (jsalisbury)
--
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/1938918
Title:
5.13 RT kernel
** Changed in: linux (Ubuntu)
Assignee: Krzysztof Kozlowski (krzk) => Joseph Salisbury (jsalisbury)
--
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/1938048
Title:
5.13 RT kernel
This is the result of pulling the lxc test sources from the git repo,
but using the lxc from the archive. Currently, the archive has version
4.0.6 and the git repo has been updated to 4.0.12 as an upload is in
progress (it's in the unapproved queue as this comment is being
written).
The result is
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560023/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560022/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Applied the "apport-collect 1960344" command as requested. Note that
this is while using the 5.4.0-94 kernel, because I cannot successfully
log in with the 5.4.0-99 kernel.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560021/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560024/+files/acpidump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560016/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560013/+files/Lsusb.txt
--
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/1960344
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560017/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560020/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560011/+files/Lspci.txt
--
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/1960344
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560015/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560018/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560012/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560009/+files/CRDA.txt
--
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/1960344
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560019/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560014/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1960344/+attachment/5560010/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected una
** Description changed:
When I boot with kernel 5.4.0-94 my Linux system properly asks me for
the passphrase to my encrypted drive (full disk encryption) and then
after that successfully gets me to the user login screen. But when I
P.S. The reason this is a security issue is-- there is now an address on
the host that the guest also 'knows' and it sits on the bridge giving
access to all the other guests on the bridge. Most admins will not
'just know' they need rules to block fe80 traffic generated by host
interfaces--
I need to repeat: in sysctl.d put this line in a file, then reboot,
then your test setup will show the failure:
net.ipv6.conf.all.autoconf = 0
Otherwise, in your test setup the tables are populated, then you delete
the addresses, but the L3/4 code engaged by even a little time with the
fe80:...
Has there been any other followup on this?
** Tags added: hwcert-server
--
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/1950778
Title:
Ubuntu 20.04.3 generates IO error message during
Sent fix upstream:
https://lore.kernel.org/linux-rt-users/20220209162430.286578-1-krzysztof.kozlow...@canonical.com/T/#u
Discussions on-going.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: linux (Ubuntu)
Status: Incomplete => In
Public bug reported:
* Explain the bug(s)
The inner_ipproto saves the inner IP protocol of the plain
text packet. This allows vendor's IPsec feature making offload
decision at skb's features_check and configuring hardware at
ndo_start_xmit.
For example, ConnectX6-DX IPsec device needs the
Public bug reported:
* Explain the bug(s)
current code implementation did not handle the case where IPsec is used in
tunnel mode.
* Brief explanation of fixes
As in case of IPsec tunnel mode the skb->encapsulation bit is not set in case
of non-encapsulated
packet (As TCP and UDP), then inner
After upgrading to linux-image-5.13.0-28-generic this bug seems to be
fixed.
--
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/1953048
Title:
Laptop won't properly shutdown after kernel
*** This bug is a duplicate of bug 1958283 ***
https://bugs.launchpad.net/bugs/1958283
Thanks for the confirmation. No need to uninstall the package, it will
migrate to updates soon.
** This bug has been marked a duplicate of bug 1958283
linux-firmware missing renoir_ta
--
You received
--- Comment From wint...@de.ibm.com 2022-02-09 09:45 EDT---
Did a quick test of HiperSockets and OSA with
add-apt-repository ppa:krzk/linux-testing
apt install linux-image-unsigned-5.4.0-100-generic/focal
Looks good to me.
I did not exercise any memory pressure though. So it makes sense
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
** Changed in: linux (Ubuntu Focal)
** Changed in: linux (Ubuntu Focal)
Assignee: Krzysztof Kozlowski (krzk) => (unassigned)
** No longer affects: linux (Ubuntu Focal)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux-aws (Ubuntu Focal)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification
That solved the issue i am currently running 5.13.0-28-generic with no
random noise on the laptop screen.
Regarding the package i installed, should i uninstall it so it doesn't cause
issues in the future or will a future update replace it? (I will surely forget
about this custom install in a
Ondrej, I built the module using rtl8821ce-dkms package.
This is how I built the kernel snap:
https://paste.ubuntu.com/p/4KzY8qM6gm/
--
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/1954564
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1023.25
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 still
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1023.25
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 still
OK this would mean that kernel modules in the linux-modules-extra packages are
not signed.
kernel enforces kernel module signature check if SB is enabled.
But our modules should be signed.
@Renat, can you confirm exact versions of all the stage packages?
As those need to be aligned for signing
We've successfully built the kernel snap with the rtl8821ce-5.5.2.1 module.
I can confirm that it boots loads and enables the WiFi interface. I disabled
Secure Boot to make it work.
The problem is in Secure Boot, it doesn't allow us to load the module when
enabled.
Is there any chance that
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Krzysztof Kozlowski (krzk)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Repro same stack traces on 510 after some trial and error at:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-510/+bug/1953674
Key discovery there: it reproduces almost every time when my laptop is
on battery power with the power cord unplugged, otherwise it generally
only
*** This bug is a duplicate of bug 1946303 ***
https://bugs.launchpad.net/bugs/1946303
OK, now noticed that my error lines are exactly the same as:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-470/+bug/1946303 it's just I wasn't getting the logs
consistently before I had
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1946303
Title:
No
Fail to run the command "apport-collect 1960392".
Please check if the sosreport of #1 is enough, thanks.
--
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/1960392
Title:
Ubuntu server
*** This bug is a duplicate of bug 1946303 ***
https://bugs.launchpad.net/bugs/1946303
Then, re-enabled Wayland with NVIDIA purged, and suspend works there.
Then, re-installed and reenabled NVIDIA 510 (which blakclists Wayland
and puts me in X11 since no Wayland support yet), and boom
*** This bug is a duplicate of bug 1893956 ***
https://bugs.launchpad.net/bugs/1893956
This appears to still be an issue on the latest 5.4.0-99-generic kernel.
I'm using a 2 port 10GSFP+ card. The PCI driver isn't bound according to
lspci, and the interfaces don't show up in dmesg or "ip
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 1960392
and then change the status of the bug to 'Confirmed'.
If, due to the
** Attachment added: "sosreport and screenshot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960392/+attachment/5559923/+files/1960392.zip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Reproduce steps:
1.Setup raid 0 with 2 sata disks and intel VROC SATA controller.
2.Install Ubuntu server 22.04 with the latest image.
3.It crash with error "devices or container for raid must be specified"
** Affects: linux (Ubuntu)
Importance: Undecided
FYI: If you want/need a test - builds of the qemu that have that are in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4753
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Fail to run command "apport-collect ".
Please check if the sosreport is enough for you
** Attachment added: "sosreport 22.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950306/+attachment/5559922/+files/sosreport-ubuntu-server-1950306-2022-02-09-qxnqhqc.tar.xz
--
You received
Dumping a bit more debug log before I forget:
I disabled NVIDIA from the software & updates. If I try to suspend:
- it immediately wakes up into lock screen
- I can't login anymore: after password, goes into black kernel log screen as
in boot
That was in Wayland, the new default. So I
So just for the records:
with first picking:
277c8389386e ("390/kexec_file: move kernel image size check")
before
5ecb2da660ab ("s390: support command lines longer than 896 bytes")
I get the code into jammy's master-next.
--
You received this bug notification because you are a member of Kernel
73 matches
Mail list logo
