Public bug reported:
I could not find an existing report on this.
When Ubuntu 20.04 does powersaving, the audio card powers down.
When the card powers up again, it emits a short annoying popping/crackling
noise, then audio plays just fine.
The workaround is to disable power-saving for the audio
The system is largely unresponsive. I got this though:
ubuntu@myserver:~$ free
totalusedfree shared buff/cache available
Mem: 6568594848896836 803588 4691721598552415572340
Swap: 1996796 51712 1945084
I got the same bug again. Here are the kernel messages:
[ 1450.993972] INFO: task systemd:1 blocked for more than 120 seconds.
[ 1451.000279] Tainted: P O 4.15.0-36-generic #39-Ubuntu
[ 1451.007094] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[
I tried the following command:
ubuntu@myserver:~$ lxd-benchmark launch --count 900 --parallel 24 ubuntu:18.04
Test environment:
Server backend: lxd
Server version: 3.0.2
Kernel: Linux
Kernel architecture: x86_64
Kernel version: 4.15.0-36-generic
Storage backend: zfs
Storage
@Vasiliy: Indeed.
The version in -proposed is "4.15.0-29.31" (source:
https://launchpad.net/ubuntu/bionic/+queue?queue_state=3_text
=linux-image)
The page for that version at
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782173
does not have a reference to this bug number #1781364.
--
I have been doing stress-testing on LXD at a freshly installed 18.04.
The Linux kernel was the standard 18.04 kernel.
LXD though was compiled from master, ZFS was also compile from master.
I performed the stress-testing by running the command
lxd-benchmark --count 384 --parallel 24
This
zfsutils-linux (zfs-linux, zfs-linux_0.7.5-1ubuntu16.3) is already in proposed,
https://launchpad.net/ubuntu/bionic/+queue?queue_state=3_text=zfs-linux
Please report when linux-image gets into -proposed,
https://launchpad.net/ubuntu/bionic/+queue?queue_state=3_text=linux-image
--
You received
Public bug reported:
I have been stress-testing LXD and managed to cause the following kernel
hung:
[10271.564074] INFO: task systemd:1 blocked for more than 120 seconds.
[10271.570397] Tainted: P OE4.15.0-20-generic #21-Ubuntu
[10271.577212] "echo 0 >
** Bug watch added: Github Issue Tracker for ZFS #7659
https://github.com/zfsonlinux/zfs/issues/7659
** Changed in: linux
Status: Fix Released => Unknown
** Changed in: linux
Remote watch: Github Issue Tracker for ZFS #7691 => Github Issue Tracker for
ZFS #7659
--
You received this
This might be related to #1773392.
On the other hand, the issue in #1773392 appears to have been introduced
in more recent kernels (16.04 not affected).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Upstream bug report and pull request to try:
"Kernel error "task zfs:pid blocked for more than 120 seconds" #7691"
https://github.com/zfsonlinux/zfs/issues/7691
"Fix zpl_mount() deadlock #7693"
https://github.com/zfsonlinux/zfs/pull/7693
** Bug watch added: Github Issue Tracker for ZFS #7691
I get this message and I do not even run a Kabylake system ("kbl").
According to https://01.org/linuxgraphics/downloads/firmware
"2. Q: I am seeing the following error message, what do they mean and what
should I do in response?
W:Possible missing firmware
It's great that it has been fixed upstream.
To backport to 14.04, see instructions at
https://help.ubuntu.com/community/UbuntuBackports
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also occurred on an ASRock Z87 Pro4, after several suspend/resume
cycles. It might be a race condition.
Linux desktop 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages,
Christopher, the motherboard is from a LoCo member and I do not have access to
it at the moment.
What is common between the two cases, is the motherboard being ASRock.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Apparently this is a regression in the xhci code (USB3). If you connect
the device to a USB2 port (if you have one) or disable xHCI in the BIOS,
the problem is gone. Of course you get USB2 speeds as well.
Relevant bug reports:
Bug#741989: linux: 3.13.5: known regression: xHCI xhci_drop_endpoint
16 matches
Mail list logo
