https://lists.ubuntu.com/archives/kernel-team/2021-September/123898.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1892213
Title:
psock_snd.sh in net from
** Description changed:
[Impact]
- The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always
failing with:
+ The expected to fail 'raw gso min size - 1' test in psock_snd.sh is
+ not failing as expected, and thus this test will fail with:
- raw gso min size - 1 (expected
** Description changed:
[Impact]
The expected to fail 'raw gso min size - 1' test in psock_snd.sh is always
failing with:
raw gso min size - 1 (expected to fail)
tx: 1524
rx: 1472
OK
This is because after commit 7c6d2ec ("net: be more gentle about silly
gso requests
I filed a new SRU tracker here: LP: #1942972.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1936708
Title:
Wobbly graphics on built-in display since linux-
Public bug reported:
[Impact]
There's a new fix for LP: #1936708, and it's more reliable than the
old approach. So replace it.
[Fix]
Use eDP as predicate to enable max params.
[Test]
Users confirmed the fix can resolve their issue.
[Where problems could occur]
This patch reverts to the old
** 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-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1940610
Title:
Fix mic noise on HP ProBook
** 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-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1936682
Title:
Fix kernel panic caused by
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Hirsute)
Status: Confirmed => In Progress
That's why the instructions in comment #29 say to install them together
(in a single command):
sudo dpkg -i linux*.deb
--
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/1939417
Title:
The previous branch in comment 4 is for impish, this branch is for focal.
https://code.launchpad.net/~mreed8855/ubuntu/+source/hwdata/+git/hwdata/+ref/hba11_focal_pci_ids
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to hwdata in Ubuntu.
This branch is for focal. The previous branch in comment #1 is for
impish
https://code.launchpad.net/~mreed8855/ubuntu/+source/hwdata/+git/hwdata/+ref/perc11_focal_pci_ids
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to hwdata in
** 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-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1942830
Title:
Fix sluggish r8169 by disaling
All autopkgtests for the newly accepted linux-meta (4.15.0.157.146) 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 (s390x)
linux/4.15.0-157.164 (ppc64el, i386)
Please visit the excuses page listed
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1942952
Title:
Kernel Call Trace on Secure
Public bug reported:
Could the call traces in dmesg be related to UEFI secure boot?
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-34-generic 5.11.0-34.36
ProcVersionSignature: Ubuntu 5.11.0-34.36-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
ApportVersion:
laura@livingroom:~$ pulseaudio --kill && pulseaudio --start -
--log-target=[file:~/pulseaudio.txt]file:~/pulseaudio.txt
E: [pulseaudio] log.c: Invalid log target.
E: [pulseaudio] cmdline.c: Invalid log target: use either 'syslog', 'journal',
'stderr' or 'auto' or a valid file name 'file:',
Public bug reported:
I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10 0
I: Bus=0019 Vendor=
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/192
Title:
test_utils_testsuite from ubuntu_qrt_apparmor linux ADT
All autopkgtests for the newly accepted linux-meta (5.4.0.85.89) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (ppc64el, arm64, amd64)
Please visit the excuses page listed below and
Hi Shengyao,
According to Lenovo, the issue can be reproduced on a failed system in Windows
environment. Would you please try? If you can see the same result, let's do
debug in Windows environment.
Please provide your system information for me to understand if it is vPro or
non-vPro system.
--
** Changed in: linux-firmware (Ubuntu)
Milestone: None => focal-updates
** Tags added: rls-ff-incoming
--
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/1939986
Title:
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
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
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
Retested with the latest kernels as of Sept 7, 2021. Now able to see
that ubuntu-drivers now lists the 470-server driver as an available
option. For both Focal and Hirsute, I first had to enable -proposed. For
Bionic, it worked with the 4.15.0-156.163 kernel that was released this
week.
Tested
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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
All autopkgtests for the newly accepted linux-meta (5.11.0.35.37) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/247.3-3ubuntu3.4 (amd64)
Please visit the excuses page listed below and investigate the failures,
I can confirm the same with proposed.
On 9/7/21 3:40 PM, Will G wrote:
> For the avoidance of doubt I've just booted up `5.11.0-35-generic` from
> -proposed (after previously running Hui's build) and audio is working
> fine on my 9710.
>
> ** Tags removed: hirsute verification-needed-hirsute
>
This bug was fixed in the package linux - 5.4.0-84.94
---
linux (5.4.0-84.94) focal; urgency=medium
* focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources: Add
** Attachment added: "screenlog.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1942935/+attachment/5523575/+files/screenlog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in
For the avoidance of doubt I've just booted up `5.11.0-35-generic` from
-proposed (after previously running Hui's build) and audio is working
fine on my 9710.
** Tags removed: hirsute verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification
@hashratez
right/official command (without adding any 3rd repository) is:
sudo apt install --install-recommends linux-generic-hwe-20.04
on officialy supported HW is done automatically, on other you must manualy run
for upgrade to latest HWE line, more info:
Public bug reported:
It seems to always occur during an mdcheck/resync, if I am logged in via
SSH it is still somewhat responsive and basic utilities like dmesg will
work. But it apppears any write I/O will hang the terminal and nothing
is written to syslog (presumably because it is blocked).
Public bug reported:
SRU Justification:
[Impact]
* The oob_net0 interface, managed by the mlxbf_gige driver, will be
up and enabled but can stop processing received packets if three
specific conditions occur:
1) driver has received more than (N * RxRingSize) packets but less
than (N+1
@hui your kernel works for me on my Dell XPS9710. Sound in and out.
Thanks!!
In other words, in response to the kernel bot:
This patch solves the problem. If I knew how, I would change this to
'verification-done-hirsute'
Thanks again!
--
You received this bug notification because you are a
Hey Jo,
Thanks for the debdiff!
...
So, it looks like the 2 commits for dmesg/printk are actually LP#1921403
that you handled previously?
For better tracking/documentation purposes, the right thing to do would be to
keep these 2 patches
associated with that bug (well, it requires an SRU
It seems the maintainer has concerns on the patch, and there is no reply
from the developer at the moment:
https://patchwork.kernel.org/project/linux-
input/patch/20210729010940.5752-1-phoe...@emc.com.tw/
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: makedumpfile (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: makedumpfile (Ubuntu Hirsute)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
** Also affects: makedumpfile (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Hirsute)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu
Public bug reported:
SRU Justification:
[Impact]
* The command "ethtool -S oob_net0" displays a set of statistics
related to mlxbf_gige driver. This set of statistics does not
include the driver's interrupt counts.
[Fix]
* The fix is to extend the statistics list supported by "ethtool -S"
** Also affects: makedumpfile (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Focal)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Focal)
Assignee: (unassigned) => Ioanna Alifieraki (joalif)
** Tags added:
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.10
---
alsa-ucm-conf (1.2.2-1ubuntu0.10) focal; urgency=medium
* d/p/0031-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch
The mixer name is changed in the codec driver rt1316-sdw.c, so need
to handle
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.10
---
alsa-ucm-conf (1.2.2-1ubuntu0.10) focal; urgency=medium
* d/p/0031-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch
The mixer name is changed in the codec driver rt1316-sdw.c, so need
to handle
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu1.3
---
alsa-ucm-conf (1.2.4-2ubuntu1.3) hirsute; urgency=medium
* d/p/0005-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch
The mixer name is changed in the codec driver rt1316-sdw.c, so need
to handle
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu1.3
---
alsa-ucm-conf (1.2.4-2ubuntu1.3) hirsute; urgency=medium
* d/p/0005-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch
The mixer name is changed in the codec driver rt1316-sdw.c, so need
to handle
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. 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-
hirsute' to 'verification-done-hirsute'. If the problem still exists,
change the tag
This bug was fixed in the package thermald - 2.4.3-1ubuntu2
---
thermald (2.4.3-1ubuntu2) hirsute; urgency=medium
* Support Jasper Lake. (LP: #1940629)
- 0014-Added-Jasper-Lake-CPU-model.patch
-- Andy Chi Fri, 20 Aug 2021 15:56:17 +0800
** Changed in: thermald (Ubuntu
The verification of the Stable Release Update for thermald has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
This bug was fixed in the package thermald - 1.9.1-1ubuntu0.6
---
thermald (1.9.1-1ubuntu0.6) focal; urgency=medium
[Andy Chi]
* Support Jasper Lake. (LP: #1940629)
- 0144-Added-Jasper-Lake-CPU-model.patch
[Colin Ian King]
* AlderLake CPU support (LP: #1942181)
-
This bug was fixed in the package thermald - 1.9.1-1ubuntu0.6
---
thermald (1.9.1-1ubuntu0.6) focal; urgency=medium
[Andy Chi]
* Support Jasper Lake. (LP: #1940629)
- 0144-Added-Jasper-Lake-CPU-model.patch
[Colin Ian King]
* AlderLake CPU support (LP: #1942181)
-
The verification of the Stable Release Update for thermald has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
Just a quick update to let you know that my local build is still working
fine on all 5 test machines.
--
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
It's not in the commit log for -34: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/hirsute/log/?h=Ubuntu-5.11.0-34.36
It's in the log for the next kernel cycle -35:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/hirsute/log/?h=Ubuntu-5.11.0-35.37
--
You
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
Tags: bionic
Uname: Linux 5.11.5-051105-generic x86_64
UnreportableReason: The running kernel
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1942500/+attachment/5523563/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1942500/+attachment/5523562/+files/ProcCpuinfoMinimal.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)
Status: Incomplete => 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/1942500
Title:
invalid symbol # in scripts/module.lds
Status in
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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. 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-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
Same issue here on ubuntu 21.04, i was wondering why my power emptied
overnight.
❯ sudo cat /sys/power/mem_sleep
[s2idle]
❯ sudo dmesg | grep "suspend entry"
[sudo] password for jeremy:
[ 2739.515120] PM: suspend entry (s2idle)
[22012.050938] PM: suspend entry (s2idle)
--
You received this
Hui
Was the 5.11.0-34-generic release suppose to have the patch in it?
Thanks
Michael
--
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/1935850
Title:
Dell XPS 17 (9710) PCI/internal sound
--- Comment From boris.m...@de.ibm.com 2021-09-07 11:34 EDT---
Fix released, landed in impish / 21.10, hence closing the bug.
IBM BZ status:->CLOSED
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Public bug reported:
Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
Description:
Fix of genprotimg allowing the tool to verify the validity of IBM Secure
Execution host key documents.
Without that, customers must verify the host key document by themselves,which
is error prone
You have been subscribed to a public bug:
Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
Description:
Fix of genprotimg allowing the tool to verify the validity of IBM Secure
Execution host key documents.
Without that, customers must verify the host key document by
commit was reverted in Focal due to regression. Setting from fix
released -> triaged
** Changed in: linux (Ubuntu Focal)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
** Tags added: bot-stop-nagging
--
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/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
Status
Public bug reported:
Since kernel update to 5.11.0-27, nfs is not mounted. I get "mount.nfs:
access denied by server while mounting perso-env.univ-
rennes1.fr:/homedir" error.
If I start with kernel 5.8.0-40 or 5.8.0-55 nfs works fine.
lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:
Since 5.13 already landed in impish:
linux-generic | 5.13.0.14.25 | impish
and the patches are also upstream with 5.13,
I'll update the "affects impish" entry as Fix Released
and with that the entire ticket is Fix Released.
** Changed in: linux (Ubuntu Impish)
Status: Fix Committed =>
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 1942902
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux-azure-4.15 - 4.15.0-1123.136
---
linux-azure-4.15 (4.15.0-1123.136) bionic; urgency=medium
* bionic/linux-azure-4.15: 4.15.0-1123.136 -proposed tracker (LP:
#1939816)
* VM enter into hung status after triggering a crash (LP: #1882623)
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux-azure-5.4 -
5.4.0-1058.60~18.04.1
---
linux-azure-5.4 (5.4.0-1058.60~18.04.1) bionic; urgency=medium
* bionic/linux-azure-5.4: 5.4.0-1058.60~18.04.1 -proposed tracker
(LP: #1942138)
[ Ubuntu: 5.4.0-1058.60 ]
* focal/linux-azure:
This bug was fixed in the package linux-dell300x - 4.15.0-1027.32
---
linux-dell300x (4.15.0-1027.32) bionic; urgency=medium
* bionic/linux-dell300x: 4.15.0-1027.32 -proposed tracker (LP:
#1939817)
* dell300x: rsi wifi and bluetooth crash after suspend and resume
(LP:
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
1 - 100 of 176 matches
Mail list logo
