As mentioned in the description these are reverts to the state before
based on code review. Verified that those are included in the kernel.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of
It looks like there was an issue with the bots. This fix is released and
no longer requires verification.
** Tags removed: verification-needed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
See https://partnerissuetracker.corp.google.com/issues/194431474 for
more information
[Impact]
aufs.ko to be removed
[Fix]
Set CONFIG_AUFS_FS to N.
[Test]
Confirm that aufs.ko no longer being built.
[Regression Potential]
No expected regression (aufs functionality will be
** Also affects: linux-oem-5.10 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.10 (Ubuntu
Chris, the fix is here and I'll do the SRU:
https://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/intel.git/commit/?h=fixes=2f658f7a3953f6d70bab90e117aff8d0ad44e200
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
All autopkgtests for the newly accepted linux-meta (4.15.0.154.143) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
linux/4.15.0-154.161 (ppc64el, i386)
network-manager/1.10.6-2ubuntu1.4 (i386)
Please visit the excuses page
Yes the live image is fine so long as it is Ubuntu 21.10:
http://cdimage.ubuntu.com/daily-live/current/
--
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/1919250
Title:
[ASUS TUF Gaming
> seems like this bug has not been patched for the vast majority of us,
> given that this is a critical bug i say it should be reopened
Judging by the above comments, it's 2 people out of 51. Comments #30 and
#33 are definitely not this bug because that's the wrong hardware
generation. So it
*** This bug is a duplicate of bug 1926808 ***
https://bugs.launchpad.net/bugs/1926808
** This bug has been marked a duplicate of bug 1926808
Bionic update: upstream stable patchset 2021-04-30
--
You received this bug notification because you are a member of Kernel
Packages, which is
This commit has been merge in focal master-next branch as following.
https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-
intel/+git/focal/commit/?h=master-
next=cb8e4e3fc893ad3e77b98168df29fca03f1d46ea
Anything else should I check?
--
You received this bug notification because
I will, give me time. I will use dvd-live, is that ok?
On Mon, Aug 2, 2021, 3:45 AM Daniel van Vugt <1919...@bugs.launchpad.net>
wrote:
> Please try a newer kernel:
>
> https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
>
> or just try live booting the latest preview of 21.10 from USB:
>
Hi Chao. May you please verify the Focal kernel in proposed resolves
this bug?
If the problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem still exists, change the tag
'verification-needed-focal' to 'verification-failed-focal'.
Thank you!
--
All autopkgtests for the newly accepted linux-meta-aws (4.15.0.1110.113) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
Please visit the excuses page listed below and investigate the failures,
All autopkgtests for the newly accepted linux-meta-kvm (4.15.0.1098.94) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
glibc/2.27-3ubuntu1.4 (amd64)
ddcci-driver-linux/0.3.1-2ubuntu0.1 (amd64)
This bug is awaiting verification that the 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 exists,
change the tag
This bug is awaiting verification that the 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 exists,
change the tag
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0..114)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
lxd/3.0.3-0ubuntu1~18.04.1 (arm64)
Please visit the excuses page listed below and investigate the
This patch fixes the problem:
>From 57ca81245f4db4a0222d545f8f5d4709544c26cf Mon Sep 17 00:00:00 2001
From: Shukun Tan
Date: Thu, 5 Mar 2020 10:06:21 +0800
Subject: [PATCH] crypto: hisilicon - Use one workqueue per qm instead of per
qp
Since SEC need not so many workqueues as our test, we just
This appears to already be in 21.10 devel
https://code.launchpad.net/~usd-import-
team/ubuntu/+source/hwdata/+git/hwdata/+ref/applied/ubuntu/impish-devel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to hwdata in Ubuntu.
** Patch removed: "chmod-reference.patch"
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1938886/+attachment/5515876/+files/chmod-reference.patch
** Patch added: "chmod-reference.patch"
** Tags added: patch
--
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/1938886
Title:
rrr:no dh_strip or strip loose setuid bit
Status in bash package in Ubuntu:
Invalid
Status in
I've switched to a new flash drive, updated firmware (again), and turned
back on optimized OS defaults. One of the three (or a combination of
them) resulted in a succeeded 20.04.02 LTS installation. This issue can
be closed. Thanks everyone!
--
You received this bug notification because you are
seems like this bug has not been patched for the vast majority of us,
given that this is a critical bug i say it should be reopened
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-hwe-5.8 in Ubuntu.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance:
** Information type changed from Private Security to Public Security
--
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/1937107
Title:
Kernel Oops - unable to handle kernel paging request
I need atleast 5.12 for wifi to work. But I will try once I have a BIOS
upgrade.
--
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/1937056
Title:
Touchpad not working with ASUS TUF F15
Public bug reported:
== Comment: #0 - Ingo Franzki - 2021-08-02 08:08:41 ==
A problem has been identified in the the libkmipclient component of s390-tools
2.17.0.
Please include the following commit on top of v2.17.0:
You have been subscribed to a public bug:
== Comment: #0 - Ingo Franzki - 2021-08-02 08:08:41 ==
A problem has been identified in the the libkmipclient component of s390-tools
2.17.0.
Please include the following commit on top of v2.17.0:
Appears to be an ELAN:
acpidump | grep ELAN
439E0: 31 00 5F 48 49 44 70 0D 45 4C 41 4E 30 30 30 31 1._HIDp.ELAN0001
Add this ID to include/linux/input/elan-i2c-ids.h did not work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Patch added: "chmod-reference.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938886/+attachment/5515876/+files/chmod-reference.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: bash (Ubuntu)
Status: New => Invalid
** Changed in: dash (Ubuntu)
Status: New => Invalid
** Changed in: debhelper (Ubuntu)
Status: New => Triaged
** Changed in: debugedit (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: New
stock 5.13 + same config + RT patches work fine, so this is something
todo with the sauce patches methinks.
--
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
Based on https://elixir.bootlin.com/linux/latest/source/fs/inode.c#L1928
it seems that setuid and capabilities will be stipped, thus currently
our implementation of dh_strip causes to loose setuid and capabilities.
No idea why this is working with fakeroot when Rules-Requires-Root is set to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-470 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in
separately I'm not sure who/what/why stips setuid bits on file creation
through redirect.
is it like some kind of a CVE in bash/dash? kernel protection?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
- objcopy/strip changed in 2.36.1, not keeping file attributes of the
original file. Work around that in dh_strip to write to a temporary
file and cat'ing this to the original file to keep the original
attributes.
which is broken for setuid files.
** Also affects: dash (Ubuntu)
Public bug reported:
I’m trying to revive a slightly old Lenovo Z70-80. I haven’t used it for
a month or so. Then, I downloaded all the latest updates a couple of
weeks ago and something broke. The screen looks as if it's tearing many
times per second and some of the middle pixels are repeated on
I've done some more testing and built tags v5.7 and v5.7-rc2 from
source.
v5.7-rc2 seems to consistently boot without any special kernel flags
v5.7 gives me rather odd behaviour:
- When I'm first powering on the machine, v5.7 does not boot without any
special kernel flags
- If I set
Thanks for the information. So it means the ownership of the pin is incorrectly
configured by the BIOS. I can force the host_own bit to different value, please
try to install the customized kernel and give me the dmesg output.
https://people.canonical.com/~mschiu77/lp1937056/
However, even it
Hello,
For some reason, in the past week or so this bug has been freezing my
machine every couple of days or so (I’m surprised that AMD wasn’t able
to reproduce the problem yet¹). You can imagine how “pleasant” it makes
using this computer.
Today I got an interesting error in dmesg, perhaps
stress-ng --af-alg 0 -t 60 (a few rounds) produces:
[ 99.445636] BUG: scheduling while atomic: kthreadd/2/0x0002
[ 99.445647] Modules linked in: chacha_generic chacha_x86_64 libchacha
xxhash_generic wp512 streebog_generic sm3_generic sha3_generic rmd160
poly1305_generic poly1305_x86_64
** Description changed:
[Impact]
On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the failed boot from one of those
devices:
Hit any key to stop autoboot:
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
stress-ng --daemon -t 60 produces:
[ 68.860977] BUG: scheduling while atomic: stress-ng/91343/0x0002
[ 68.860981] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac
scsi_dh_emc scsi_dh_alua intel_rapl_msr joydev intel_rapl_common kvm_intel kvm
rapl input_leds serio_raw
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
and stress-ng --dup 0 produces:
[ 506.394685] BUG: scheduling while atomic: stress-ng/35875/0x0002
[ 506.394819] CPU: 0 PID: 35855 Comm: stress-ng Tainted: GW
5.13.0-1003-realtime #3-Ubuntu
[ 506.394821] i2c_i801 net_failover libahci
[ 506.394822] Hardware name: QEMU
** Description changed:
- on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
+ [Impact]
+
+ On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the
Public bug reported:
stress-ng --enosys 0 -t 60 causes:
[ 513.783315] BUG: scheduling while atomic: stress-ng/42082/0x0002
[ 513.783319] Modules linked in: cuse snd_seq snd_seq_device dccp_ipv4 dccp
atm chacha_generic chacha_x86_64 libchacha xxhash_generic wp512
streebog_generic
I also noticed just now that this kernel from the 20 track does seem to work
fine on uc20 systems:
pi-kernel5.4.0-1042.46 33120/beta
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi-5.4 in Ubuntu.
I had been running with a USB GPS for years and recently purchased a GOOD GNSS
device, so I have not had anything on this machine that accesses the pps_api
until a few days ago.
FYI I have a Raspberry Pi with Ubuntu where the pps_api works with
raspberrypi-kernel 1:1.2010727-1 if that is of any
Public bug reported:
on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the failed boot from one of those
devices:
Hit any key to stop autoboot: 0
WARNING at
= focal kernel verification =
ubuntu@aurorus:~$ apt show linux-image-5.4.0-81-generic | grep Recommends
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Recommends: flash-kernel | grub-efi-arm64, initramfs-tools |
linux-initramfs-tool
ubuntu@aurorus:~$ apt show
Confirmed with hirsute/linux 5.11.0-26.28 that icmp_redirect.sh results
are as expected:
# selftests: net: icmp_redirect.sh
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
Confirmed with focal/linux 5.4.0-81.91 that icmp_redirect.sh results are
as expected:
# selftests: net: icmp_redirect.sh
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
#
Confirmed with focal/linux 5.4.0-81.91 that the following testcases from
kernel selftests net are now being run:
fib_nexthop_multiprefix.sh
fib_nexthops.sh
icmp_redirect.sh
ip6_gre_headroom.sh
route_localnet.sh
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
I can confirm the issue is now fixed on the 5.4 kernels.
Results with bionic/linux-oracle-5.4 5.4.0-1053.57~18.04.1:
# selftests: net: pmtu.sh
# TEST: ipv4: PMTU exceptions [ OK ]
# TEST: ipv6: PMTU exceptions [ OK ]
Issue resolved with a patched kernel. Patch is here
https://bugzilla.kernel.org/show_bug.cgi?id=213579#c56.
** Bug watch added: Linux Kernel Bug Tracker #213579
https://bugzilla.kernel.org/show_bug.cgi?id=213579
--
You received this bug notification because you are a member of Kernel
Hello Jim,
Did it work before with your system and got broken after a kernel
update? If yes, would you be able to identify the kernel version which
was working before? If you didn't run this use case before, would you be
able to boot with an older kernel version and check whether it works?
SRU request submitted to the Ubuntu kernel team mailing list for hirsute and
focal:
https://lists.ubuntu.com/archives/kernel-team/2021-August/thread.html#122959
Changing status to 'In Progress' for hirsute and focal.
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
**
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hirsute)
Status: New => Confirmed
** Changed in: linux (Ubuntu Focal)
Status: New =>
Public bug reported:
After updating the kernel to the version 5.11.0.22 all network
peripherals stopped working. It appears they are not detected on lshw or
lsusb. I've tried with the ethernet port on the motherboard and an
external wifi board and also using USB tethering from a phone. None was
** Summary changed:
- vrf_route_leaking in net from ubuntu_kernel_selftests linux ADT test failure
with linux/5.11.0-18.19 (Ping received ICMP Packet too big)
+ vrf_route_leaking.sh in net from ubuntu_kernel_selftests linux ADT test
failure with linux/5.11.0-18.19 (Ping received ICMP Packet too
** Description changed:
+ SRU Justification:
+ ==
+
+ [Impact]
+
+ * It is difficult for customers to identify if a KVM guest on s390x runs
+ in secure execution more or not. Hence several requests came up that
+ asked about providing a better indication.
+
+ * If the mode is
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => 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/1938824
Title:
Bionic update: upstream stable patchset
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => 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/1936960
Title:
Bionic update: upstream stable patchset
** Tags added: verification-done-focal verification-done-hirsute
--
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/1936452
Title:
[SRU][F/H/I] Add MT7921 wifi fw
Status in HWE
verified linux-oem-5.13 version 5.13.0-1010.11 from focal-proposed.
** Tags removed: verification-needed-focal
** 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.
verified linux-oem-5.13 version 5.13.0-1010.11 from focal-proposed.
** Tags removed: verification-needed-focal
** 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.
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => 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/1936231
Title:
Bionic update: upstream stable patchset
** Changed in: linux (Ubuntu Focal)
Status: In Progress => 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/1938713
Title:
Focal update: v5.4.133 upstream stable
** Changed in: linux (Ubuntu Focal)
Status: In Progress => 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/1938199
Title:
Focal update: v5.4.132 upstream stable
A fix for this bug is now staged as part of v5.4.132 to be included in a
kernel update soon (it will be in a 5.11 update around the same time but
not separately tracked there). For 5.13 it should already be included.
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
**
verified linux-oem-5.13 version 5.13.0-1010.11 from focal-proposed.
** Tags removed: verification-needed-focal
** 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.
** Changed in: linux (Ubuntu Focal)
Status: In Progress => 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/1936244
Title:
Focal update: v5.4.130 upstream stable
** Changed in: linux (Ubuntu Focal)
Status: In Progress => 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/1936245
Title:
Focal update: v5.4.131 upstream stable
Patched kernel for further testing are being built are are soon available here:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1933173/+packages
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Focal)
Status: In Progress => 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/1936242
Title:
Focal update: v5.4.129 upstream stable
I still get the issue with the latest version of ubuntu/focal64 (several
versions checked: 20210803.0.0, 20210802.1.0, 20210624.0.0):
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/focal64'...
==> default: Matching MAC address for
Actually I made a mistake. I filed these with iotg-focal-
desktop-20210706.img
This is the only image I've used on the EHL board. I got confused with
the TGL-H board which I've used both Desktop and Core.
So, What is the old kernel you want me to use?
--
You received this bug notification
Which is the Old Kernel you want me to try?
All these bugs were filed using
iotg-focal-core-20210722.img (5.11.0-1011-intel)
I then used the patch you gave me on this kernel and retested.
I have managed to have the system hang on booting after a shutdown
twice, but after another 10 shutdowns, it
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => 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/1938340
Title:
Hirsute update: upstream stable patchset
** Changed in: linux-oem-5.6 (Ubuntu Focal)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1856010
Title:
xfrm_policy.sh / pmtu.sh /
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => 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/1936969
Title:
Hirsute update: upstream stable patchset
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => 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/1936863
Title:
Hirsute update: upstream stable patchset
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => 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/1936688
Title:
Hirsute update: upstream stable patchset
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1929452
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Hirsute)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Groovy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I had the same problem with that driver and fixed it in the driver.
Feel free to use my patch for that:
https://github.com/enlyze/xr-usb-serial/commit/6515173a8b2681fd52cc2747d7282f4e47bdd254
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
This bug was fixed in the package linux - 4.15.0-153.160
---
linux (4.15.0-153.160) bionic; urgency=medium
* bionic/linux: 4.15.0-153.160 -proposed tracker (LP: #1938319)
* 4.15.0-151 is freezing various CPUs (LP: #1938013)
- mac80211: fix memory corruption in EAPOL handling
This bug was fixed in the package linux-restricted-modules -
4.15.0-153.160
---
linux-restricted-modules (4.15.0-153.160) bionic; urgency=medium
* Master version: 4.15.0-153.160
* LRMv5: switch primary version handling to kernel-versions data set
(LP: #1928921)
-
I seem to have very similar issues. Using a Lenovo ThinkPad X1 Carbon
7th gen and ThinkPad USB-C Dock Gen 2. But I also see this on a
different docking station. I'm pretty sure they are both using USB-C DP-
alt mode.
When I boot my laptop connected to the docking stations, I can see BIOS
POST
** Changed in: linux (Ubuntu Hirsute)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
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/1935846
Title:
Sony Dualshock 4 usb dongle crashes the whole system
Hi @Doug,
Regarding this issue and bug 1938408, could you try to use the old
kernel to see if this patch caused the system hang issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
Here it is:
GPIO ranges handled:
0: INT34C6:00 GPIOS [81 - 105] PINS [0 - 24]
128: INT34C6:00 GPIOS [209 - 228] PINS [25 - 44]
32: INT34C6:00 GPIOS [113 - 138] PINS [45 - 70]
96: INT34C6:00 GPIOS [177 - 202] PINS [79 - 104]
64: INT34C6:00 GPIOS [145 - 168] PINS [105 - 128]
160: INT34C6:00 GPIOS
I spoke too soon.
If you continually shutdown/boot the system, it will hang, about 20% of
the time, at the splash screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1938413
SRU: https://lists.ubuntu.com/archives/kernel-
team/2021-August/122937.html (impish)
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 112 matches
Mail list logo
