@aaron,
Tried the 5.11.0-26.28-lp1938999-generic kernel, it works fine. You
could check more about it from this log. Thanks!
** Attachment added: "journalctl.l15.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+attachment/5518358/+files/journalctl.l15.log
--
You
** Tags removed: verification-needed-hirsute
** Tags added: 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/1938149
Title:
To support AMD W6600 and
** Description changed:
[Impact]
- With AMDGPU and don't use it as a display output,
- After multiple Suspend, system would hang.
+ With AMD-GPU and don't use it as a display output,
+ After multiple Suspend, system would hang.
[Fix]
Disable BACO for polaris12 series.
+ BACO allow the
Thanks for the bug report. That's a kernel crash in the nouveau driver.
But that driver is not well supported so we would usually recommend the
official Nvidia driver instead. Unfortunately:
1. Your GeForce 310M GPU requires the Nvidia 340 driver only. Newer
drivers don't support that GPU; and
Public bug reported:
[Impact]
With AMDGPU and don't use it as a display output,
After multiple Suspend, system would hang.
[Fix]
Disable BACO for polaris12 series.
[Test Case]
1. Must plug AMD GPU and don't use it as display output
2. Plug DP/hdmi on igpu.
3. Suspend machine.
4. check if system
You have been subscribed to a public bug:
Since upgrading to Ubuntu 21.04 yesterday, I've noticed several hangs
during full-screen video playback (watching Youtube videos in Chromium).
Often, it happens just after or during the switch to full-screen.
The system stays running and I can connect
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux-hwe-5.8 (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.8 in Ubuntu.
I have created a test kernel for 21.10 at the following link:
https://people.canonical.com/~mreed/lp_1935034_mpt3sas_update_38_100/impish/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750
This bug is closed as a duplicate of bug 1869750 which is also closed.
For any ongoing issues, please open new bugs.
--
You received this bug notification because you are a member of Kernel
Packages,
Seeing i915 GPU HANG in 5.11.0-7620-generic.
Aug 14 23:46:50 topper kernel: [88920.160585] i915 :00:02.0: [drm]
Resetting rcs0 for preemption time out
Aug 14 23:46:50 topper kernel: [88920.161300] i915 :00:02.0: [drm] *ERROR*
rcs0 reset request timed out: {request: 0001, RESET_CTL:
Thanks
On 8/16/21 8:18 PM, Hui Wang wrote:
> @Michael,
>
> The patch for 5.11.0-31-generic was rejected because it introduced a
> build failure (https://lists.ubuntu.com/archives/kernel-
> team/2021-August/123162.html), the fix patch will be in the -32 kernel,
> and once the -32 kernel merges
@Michael,
The patch for 5.11.0-31-generic was rejected because it introduced a
build failure (https://lists.ubuntu.com/archives/kernel-
team/2021-August/123162.html), the fix patch will be in the -32 kernel,
and once the -32 kernel merges this patch and is ready to test, the
status will be
You guys mocking around trying to hack headers and wotnot, just build
the bloody kernel and you'll have a full kernel without wondering if you
broke something by hacking stuff! You could have built the kernel a
100x by now!
1) Just build dwarves from hirsute
2) build libbpf from hirsute
3)
** 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/1940107
Title:
libvirtd fails to create VM
Status in
** Also affects: zfs-linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1939177
Title:
Ubuntu 20.04.2 LTS kernel
On Mon, Aug 16, 2021 at 02:05:07AM -, Kai-Heng Feng wrote:
> Is there any log in `/var/lib/systemd/pstore`?
No.
--
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/1939349
Title:
On Mon, Aug 16, 2021 at 02:15:25AM -, AaronMa wrote:
> Could you try disabling Secure Boot in BIOS?
Would you expect disabling Secure Boot to have an effect here? It should be
out of the way after the kernel has booted.
I have disabled Secure Boot, and the hang is still reproducible.
--
This bug is not limited to just Kubuntu. I am chiming in as a Xubuntu
20.04.2 user. The driver I attempt to install from Driver Manager is
340.108. The results are identical to what is being reported here. And
this bug affects ALL of my machines running v20.04. My Asus laptop with
hybrid Nvidia
@tlk this is similar/same workaround, info posted in #57 is in principles:
1. install problematic package without configuring
2. replace binary files in unpacked package path
3. configure package (this also do dkms modules build)
4. fake libc depend version in status file
this (details in #57)
Upstream has been working with me to try to determine what is going on
here. The conclusion is that we believe that firmware is piggy-backing
on the ARM_SMCCC_ARCH_WORKAROUND calls, and is clobbering some of the
registers in the x4-x17 range. The patch series mentioned in Comment #9
happens to
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This bug was fixed in the package linux-oem-5.13 - 5.13.0-1010.11
---
linux-oem-5.13 (5.13.0-1010.11) focal; urgency=medium
* focal/linux-oem-5.13: 5.13.0-1010.11 -proposed tracker (LP:
#1937217)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf, follow
This appears to be fixed in the current beta kernel for 18-pi -
5.4.0-1042.46~18.04.3 r337
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1938912
Title:
Bad Linux ARM64 Image
This bug affects me too.
Ubuntu 20.04 with Gnome. The bug appears when using Firefox in my case.
Downgrading the kernel to 5.4 series solves the issue. I have to downgrade from
5.11, the last version of the Hardware Enablement Stack. The bug is present on
5.11 and 5.8 versions.
Intel(R)
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
This bug was fixed in the package linux - 4.15.0-154.161
---
linux (4.15.0-154.161) bionic; urgency=medium
* bionic/linux: 4.15.0-154.161 -proposed tracker (LP: #1938411)
* Potential reverts of 4.19.y stable changes in 18.04 (LP: #1938537)
- SAUCE: Revert "locking/mutex:
*** This bug is a duplicate of bug 1869750 ***
https://bugs.launchpad.net/bugs/1869750
I'm having a similar issue on Ubuntu 20.04. Currently, every time that I
reboot I'm unable to login. I just get a black screen after logging in.
I have noticed that if I first delete the contents of .config
Public bug reported:
When building with a non-primary variant - such as the unstable tree[*],
do_libc_dev gets set to false:
debian/rules.d/0-common-vars.mk
# linux-libc-dev may not be needed, default to building it only for the
# primary variant
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
Just updated Linux xps17 5.11.0-31-generic #33
System is still showing Dummy Output for sound.
But, there are no errors in dmesg now.
[2.787880] snd_hda_intel :00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040100
[2.787895] snd_hda_intel :00:1f.3: SoundWire
OOps, this this isn't the same kernel!? Ignore my comment then!
--
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/1937897
Title:
GPIO error logs in start and dmesg after update of kernel
** Description changed:
== SRU Justification Focal ==
[Impact]
https://github.com/openzfs/zfs/issues/12462
Ubuntu 20.04.2 LTS
Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu
zfs-0.8.3-1ubuntu12.12
zfs-kmod-2.0.2-1ubuntu5
Trying to run zfs send | receive and getting an
** Changed in: linux (Ubuntu Hirsute)
Status: New => Invalid
--
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/1940134
Title:
fails to launch linux L2 guests on AMD
Status in linux
** Description changed:
+ == SRU Justification Focal ==
+
+ [Impact]
+
https://github.com/openzfs/zfs/issues/12462
Ubuntu 20.04.2 LTS
Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu
zfs-0.8.3-1ubuntu12.12
zfs-kmod-2.0.2-1ubuntu5
Trying to run zfs send | receive and getting an
can confirm this (simpler) workaround works https://askubuntu.com/a/1335849
tested with 5.13.0
force-install the newer headers (edit out the libc6 2.33 dep in the dpkg
status file)
Then just dpkg -x linux-headers-5.11.16-051116-generic_5.11.16 and
replace fixdep and modpost
--
You received
Adding linux-hwe-5.8 as invalid to document that the test case has been
run there, and the bug has not shown up.
Cascardo.
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: linux (Ubuntu
Public bug reported:
[Impact]
Users won't be able to run a Linux inside a Linux guest.
[Test case]
Launch an L1 guest with libvirt, then launch an L2 guest using qemu inside that
first/L1 guest.
[Potential regression]
There might be reduced performance due to vmexits for interrupt handling.
No it unfortunately did not work. With the new HWE kernel Ubuntu
5.11.0-27.29~20.04.1-generic (same as above?).
The failing lines are at two places in the log. Boot is very quick
though but it is annoying seeing the red lines.
--
You received this bug notification because you are a member of
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
I'm now using Ubuntu 21.04 hirsute, and this bug can no longer be
reproduced :) Kernel 5.11.0-25-generic.
I've done 3 tests. No crashes so far.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.8 in Ubuntu.
Info provided by Intel for EHL:
https://bugs.launchpad.net/intel/+bug/1929902/comments/12
--
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/1929892
Title:
[TGL] enable USB-dw3
I built the two parents of commit 900db15: 8685217 and e9bdf7e
They both booted fine. I built 900db15 again just in case, and it does
not boot. So it does indeed seem to be the first bad commit, unless I'm
doing something wrong on my end.
Any suggestions?
Thanks!
--
You received this bug
I was not able to use the suggested kernel due to UEFI/SecureBoot.
However, after edit "/etc/default/grub" and change
GRUB_CMDLINE_LINUX_DEFAULT to GRUB_CMDLINE_LINUX_DEFAULT="quiet
i8042.nopnp=1 pci=nocrs", touchpad started to work.
OBS: Suggestion taken from:
** Summary changed:
- libvirtd failes to create VM
+ libvirtd fails to create VM
--
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/1940107
Title:
libvirtd fails to create VM
Status in
Hello, I added those options to the boot menu (via esc -> e -> adding it to
the end of the linux line in the boot config -> f10) and the trackpad is
still entirely unresponsive. The function key for enable/disable trackpad
did not make a difference. The device also doesn't appear in the xinput
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518147/+files/IwConfig.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 focal
** Description changed:
Hello,
My laptop run well with last 5.4 linux kernel even if I connect my
thunderbolt dock.
When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock
and 2 monitors connected, the
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518148/+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/1940113
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518159/+files/UdevDb.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/1940113/+attachment/5518161/+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: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518151/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => 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/1940121
Title:
Impish update: v5.13.11 upstream stable
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518152/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518146/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux-gcp - 5.11.0-1017.19
---
linux-gcp (5.11.0-1017.19) hirsute; urgency=medium
* hirsute/linux-gcp: 5.11.0-1017.19 -proposed tracker (LP: #1939549)
[ Ubuntu: 5.11.0-31.33 ]
* hirsute/linux: 5.11.0-31.33 -proposed tracker (LP: #1939553)
*
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518149/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518153/+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/1940113/+attachment/5518150/+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/1940113
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518145/+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/1940113
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518155/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518160/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518158/+files/RfKill.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/1940113/+attachment/5518156/+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: "PulseList.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518157/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1940113/+attachment/5518154/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package linux-azure - 5.11.0-1013.14
---
linux-azure (5.11.0-1013.14) hirsute; urgency=medium
* hirsute/linux-azure: 5.11.0-1013.14 -proposed tracker (LP: #1936485)
* linux-azure: Ensure the latest linux-image-sgx is installed with the 5.11
kernels
This bug was fixed in the package linux - 5.11.0-31.33
---
linux (5.11.0-31.33) hirsute; urgency=medium
* hirsute/linux: 5.11.0-31.33 -proposed tracker (LP: #1939553)
* REGRESSION: shiftfs lets sendfile fail with EINVAL (LP: #1939301)
- SAUCE: shiftfs: fix sendfile()
This bug was fixed in the package linux - 5.11.0-31.33
---
linux (5.11.0-31.33) hirsute; urgency=medium
* hirsute/linux: 5.11.0-31.33 -proposed tracker (LP: #1939553)
* REGRESSION: shiftfs lets sendfile fail with EINVAL (LP: #1939301)
- SAUCE: shiftfs: fix sendfile()
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1044.46
---
linux-oem-5.10 (5.10.0-1044.46) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1044.46 -proposed tracker (LP:
#1939533)
* mute/micmute LEDs no function on HP ProBook 650 G8 (LP: #1939473)
- SAUCE:
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1044.46
---
linux-oem-5.10 (5.10.0-1044.46) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1044.46 -proposed tracker (LP:
#1939533)
* mute/micmute LEDs no function on HP ProBook 650 G8 (LP: #1939473)
- SAUCE:
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1044.46
---
linux-oem-5.10 (5.10.0-1044.46) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1044.46 -proposed tracker (LP:
#1939533)
* mute/micmute LEDs no function on HP ProBook 650 G8 (LP: #1939473)
- SAUCE:
This bug was fixed in the package linux - 5.11.0-31.33
---
linux (5.11.0-31.33) hirsute; urgency=medium
* hirsute/linux: 5.11.0-31.33 -proposed tracker (LP: #1939553)
* REGRESSION: shiftfs lets sendfile fail with EINVAL (LP: #1939301)
- SAUCE: shiftfs: fix sendfile()
This bug was fixed in the package linux-azure-5.11 -
5.11.0-1013.14~20.04.1
---
linux-azure-5.11 (5.11.0-1013.14~20.04.1) focal; urgency=medium
* focal/linux-azure-5.11: 5.11.0-1013.14~20.04.1 -proposed tracker
(LP: #1936484)
* linux-azure: Ensure the latest linux-image-sgx
This bug was fixed in the package linux-raspi - 5.11.0-1016.17
---
linux-raspi (5.11.0-1016.17) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1016.17 -proposed tracker (LP: #1936496)
* HUGETLBFS is disabled (LP: #1933627)
- [Config] raspi: Set HUGETLBFS=y
[
This bug was fixed in the package linux-gcp - 5.11.0-1017.19
---
linux-gcp (5.11.0-1017.19) hirsute; urgency=medium
* hirsute/linux-gcp: 5.11.0-1017.19 -proposed tracker (LP: #1939549)
[ Ubuntu: 5.11.0-31.33 ]
* hirsute/linux: 5.11.0-31.33 -proposed tracker (LP: #1939553)
*
This bug was fixed in the package linux-riscv - 5.11.0-1017.18
---
linux-riscv (5.11.0-1017.18) hirsute; urgency=medium
* hirsute/linux-riscv: 5.11.0-1017.18 -proposed tracker (LP: #1939589)
* RISC-V: Illegal instruction (LP: #1934548)
- SAUCE: RISC-V: prevent
This bug was fixed in the package linux-riscv-5.11 -
5.11.0-1017.18~20.04.1
---
linux-riscv-5.11 (5.11.0-1017.18~20.04.1) focal; urgency=medium
* focal/linux-riscv-5.11: 5.11.0-1017.18~20.04.1 -proposed tracker
(LP: #1939588)
* Packaging resync (LP: #1786013)
-
This bug was fixed in the package linux - 5.11.0-31.33
---
linux (5.11.0-31.33) hirsute; urgency=medium
* hirsute/linux: 5.11.0-31.33 -proposed tracker (LP: #1939553)
* REGRESSION: shiftfs lets sendfile fail with EINVAL (LP: #1939301)
- SAUCE: shiftfs: fix sendfile()
This bug was fixed in the package linux - 5.11.0-31.33
---
linux (5.11.0-31.33) hirsute; urgency=medium
* hirsute/linux: 5.11.0-31.33 -proposed tracker (LP: #1939553)
* REGRESSION: shiftfs lets sendfile fail with EINVAL (LP: #1939301)
- SAUCE: shiftfs: fix sendfile()
1 - 100 of 177 matches
Mail list logo
