This can be reproduced with the following python code on Bionic, with
the autotest framework cloned:
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
sudo apt-get install -y python-minimal
python
from autotest.clientimport test, utils
import os
proxysets =
--- Comment From indira.pr...@in.ibm.com 2018-04-10 07:24 EDT---
Hi Jose,
Is this fix available in official ubutnu1804 build
Regards,
Indira
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kernel-sru-workflow/snap-release-to-beta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/snap-release-to-candidate
Status: New => Confirmed
** Changed in: kernel-sru-workflow/snap-release-to-edge
Status: Confirmed => Fix Released
--
You
--- Comment From bssrika...@in.ibm.com 2018-04-10 06:53 EDT---
We have got the qemu build with htm-on today [April 10th]. Now we are able to
start compat mode guests with htm-on.. apart from bug 166570 things look good.
We can close this one.
--
You received this bug notification
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 1762709
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug have popped up again in Bionic.
nafallo@wendigo:~$ nvidia-detector
Traceback (most recent call last):
File "/usr/bin/nvidia-detector", line 8, in
a = NvidiaDetection(printonly=True, verbose=False)
File "/usr/lib/python3/dist-packages/NvidiaDetector/nvidiadetector.py", line
68,
Hope this helps, I think I found a workaround for my bluetooth tethering
issue with Android.
NOTE: This assumes that you're using tlp power manager.
Find your bluetooth device like so:
tlp-usblist | grep btusb
Bus 002 Device 011 ID : control = on, autosuspend_delay_ms =
2000 -- Intel
--- Comment From iranna.an...@in.ibm.com 2018-04-10 06:42 EDT---
I think we are good to close this tracker bugzilla, given that all requested
KVM fixes are now available with 4.15.0-15.16 and above.
Thank you.
--
You received this bug notification because you are a member of Kernel
Tested with an older kernel on the same s390x node (kernel02), this
issue still exists.
Must be something else.
--
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/1762709
Title:
Unable to
Public bug reported:
All the tests that need to fetch a git repo for testing failed with error
message like:
CmdError: Command https://github.com/tytso/xfstests-bld> failed,
rc=128, Command returned non-zero exit status
* Command:
git clone
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1759188
Title:
[8086:3e92] display becomes blank after
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1758800
Title:
hda driver initialization takes too
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1757584
Title:
Let headset-mode initialization be
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1755804
Title:
IMA policy parsing is broken in 4.13
** Tags removed: verification-needed-artful
** Tags added: verification-done-artful
--
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/1758829
Title:
speaker can't output sound anymore
I tested the new kernel in artful-proposed on a system which failed with
the newest kernel + intel-microcode in normal artful repository.
Thus I confirm that the kernel in artful-proposed fixes this issue for
me.
$ apt policy linux-image-4.13.0-39-generic
linux-image-4.13.0-39-generic:
Public bug reported:
===SRU Justification===
[Impact]
Currently we need to recompile the entire kernel if we want try quirks
in usbcore.
[Test]
Use kernel parameter "usbcore.quirks=" in conjunction with dynamic debug
for usbcore, we can see that usb quirks successfully enabled for USB
devices
Partial solution found !
After three months of research, I came by chance on this website :
https://hive.blasux.ru/u/Stiletto/G752
# cd /sys/bus/hid/drivers/hid-multitouch
# ls
0018:04F3:3043.0007 bind module new_id uevent unbind
# echo "0018:04F3:3043.0007" > unbind
# echo 0018 04F3 3043 0013 >
Due to time constraints and because we would deviate further and further
away from Debian, we are not planning to update the Xen version for
Bionic.
** Changed in: xen (Ubuntu Bionic)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
I've followed the step linked to in
https://bugs.freedesktop.org/show_bug.cgi?id=104990 and have found that
using 'libinput measure touchpad-pressure --touch-thresholds=105:60
--palm-threshold=230' seemed to work well.
I was not able to format it into the hwdb file, however, so couldn't
actually
Patch to blacklist these on GCP / AWS has been applied.
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=40916a0680295d860c09d4c884d4aa86e3853d18
http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=81862bb97d80bf48f6349e21e259475462663f0d
We can close
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 1762695
and then change the status of the bug to 'Confirmed'.
If, due to the
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/1762693
Title:
No network with e1000e driver
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-
artful' to 'verification-done-artful'. If the problem still exists,
change the tag
Public bug reported:
When my computer boots with the most recent kernel 4.13.0-38-generic, I
don't have a working network connection. ethtool reports that my network
interface doesn't have a connection:
martin@dogmeat ~ % cat ethtool.txt
Settings for eth0:
Supported ports: [ TP ]
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-
artful' to 'verification-done-artful'. 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-
xenial' to 'verification-done-xenial'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
xenial' to 'verification-done-xenial'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
xenial' to 'verification-done-xenial'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
*** This bug is a duplicate of bug 1751202 ***
https://bugs.launchpad.net/bugs/1751202
The error message has been addressed in bug 1758242, which is also a dup
of bug 1751202
** This bug has been marked a duplicate of bug 1751202
test_095_kernel_symbols_missing in
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 1762652
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1761439
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-
xenial' to 'verification-done-xenial'. 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-
artful' to 'verification-done-artful'. 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-
artful' to 'verification-done-artful'. 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-
xenial' to 'verification-done-xenial'. If the problem still exists,
change the tag
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1761459
The update has some new features and it's a bit late in the cycle now,
that sounds rather SRU material at this point ... Daniel, Konrad, what
do you think?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
** Package changed: ubuntu => linux (Ubuntu)
--
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/1762652
Title:
perf DWARF unwind failed
Status in linux package in Ubuntu:
Incomplete
Bug
You have been subscribed to a public bug:
Ubuntu 17.10. To reproduce:
$ perf test
[...]
57: DWARF unwind : FAILED!
[...]
It seems perf is somehow mis-configured.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: bot-comment
--
4.4.0-1017.17 - aws
Regression test CMPL.
Issue to note in x86_64 (aws):
libhugetlbfs - 1 failed (alloc-instantiate-race shared), bad config 3, only
spotted on t2.small, passed on the rest
ubuntu_kvm_unit_tests - test skipped, KVM not supported
Skipped / blacklisted:
*
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/1762672
Title:
TPM on Dell XPS 13 stopped
Public bug reported:
[0.801334] tpm_tis MSFT0101:00: 2.0 TPM (device-id 0xFE, rev-id 4)
[0.812132] tpm tpm0: A TPM error (2314) occurred continue selftest
[0.843629] tpm tpm0: A TPM error (2314) occurred continue selftest
[0.895424] tpm tpm0: A TPM error (2314) occurred
Hey Bib, I have not filed a bug for the backlight OSD yet - I was too
lazy ;) I'll "me too" one if you open it though.
--
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/1746740
Title:
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
** Tags added: kernel-da-key
--
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/1762353
Title:
[Ubuntu 18.04] cryptsetup: 'device-mapper: reload ioctl on failed'
when setting up a second
** Summary changed:
- Unable to deploy Xenial image on ARM64 nodes
+ Unable to deploy Xenial image on ARM64 nodes with MaaS 2.3.0
--
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/1762655
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 1762655
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
It looks like that the deployment of Xenial on all of our ARM64 nodes are not
working (Moonshots and ThunderX)
The deployment process will drop into initramfs in the end, please find the
complete log obtained from the console here:
https://pastebin.ubuntu.com/p/BZvydzJb4v/
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Fix Released
--
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/1575921
Title:
Cannot create zpool using links in
** Changed in: zfs-linux (Ubuntu)
Status: Triaged => Incomplete
--
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/1733802
Title:
zfs destroy, dataset is busy; zpool export tank,
Would an immediate return with some error/warning message be more
appropriate that a 10 second delay?
--
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/1760173
Title:
zfs, zpool
as above, "that" -> "than"
** Changed in: zfs-linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: zfs-linux (Ubuntu)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
*** This bug is a duplicate of bug 1742698 ***
https://bugs.launchpad.net/bugs/1742698
** This bug has been marked a duplicate of bug 1742698
zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
--
You received this bug notification because you are a member of Kernel
Packages,
*** This bug is a duplicate of bug 1742698 ***
https://bugs.launchpad.net/bugs/1742698
On Ubuntu 16.04 LTS and newer, there's no need to use the zfs DKMS
packages.
** This bug has been marked a duplicate of bug 1742698
zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
--
You
*** This bug is a duplicate of bug 1742698 ***
https://bugs.launchpad.net/bugs/1742698
On Ubuntu 16.04 LTS and newer, there's no need to use the zfs DKMS
packages.
** This bug has been marked a duplicate of bug 1742698
zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel module failed to build
--
You
On Ubuntu 16.04 LTS and newer, there's no need to use the zfs DKMS
packages.
--
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/1742698
Title:
zfs-dkms 0.6.5.6-0ubuntu18: zfs kernel
There wasn't a xen commit listed (and we didn't bump the xen version so we
haven't picked it up by accident).
I'd assume this is a Won't Fix for 18.04 and might appear sometime later.
Is there any xen change to consider (later on) or was xen just
optionally listed but doesn't come to life?
**
Issue fixed in bug 1757939
** Changed in: zfs-linux (Ubuntu)
Status: New => Fix Released
--
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/1713375
Title:
zed failed because of
** 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 either directly
I didn't need but suddenly I installed some updates and it broke.
However I don't think the kernel got upgraded with that update.
--
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/1746340
The quirk is not included.
I asked this because looks like you didn't need to fsck under Debian
with Linux v4.9.
--
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/1746340
Title:
Samsung
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1752310
Title:
What is the zfs support policy wrt. LTS
You may possibly get some benefit from setting spl_kmem_cache_slab_limit
to zero as a module parameter for the spl ZoL kernel module. This avoids
SLUB slab merging entirely and maybe helpful from anecdotal evidence
I've seen.
--
You received this bug notification because you are a member of
Thanks for the great work.
Will you patch the ubuntu kernel in advance or do we need to wait until the
patch is in the mainline kernel?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => AceLan Kao (acelankao)
--
You received this bug notification because you are a member of Kernel
The system can get woken up by USB keyboard in -1023.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Seems to be fixed now, ie after i run
$ sudo dpkg --configure -a
everything seems to fall in place again. Found even a newer kernel (38)
and installed it.
So, from my side this case can be closed.
--
You received this bug notification because you are a member of Kernel
Packages, which is
It worked with xubuntu 16.04.
--
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/1761128
Title:
[TOSHIBA Satellite Pro L350] hibernate/resume failure
Status in linux package in Ubuntu:
Hello Canonical,
There are two problems here
1. Hang when CPUs don't respond to IPI. This can be resolved by setting a
non-zero panic timeout.
That fix is now available in Ubuntu releases.
2. But dump capture is still not successful with case1 fix as the system is
reseting, if some CPUs
are
I did not try to install with disable APST. I tried to put a custom
kernel in the live CD but it wouldn't boot. My current ubuntu was
installed with trial and error until it installed without any errors.
The installation process is not so important for me, I can try 5 or 7
times before getting it
4.4.0-1055.64 - aws
Regression test CMPL.
Issue to note in x86_64 (aws):
libhugetlbfs - 1 failed (brk_near_huge), Killed by signal 1, bad config 3,
only spotted on t2.small, passed on the rest
ubuntu_kvm_unit_tests - test disabled
ubuntu_lxc - lxc-test-ubunut failed (Failed to start
So do you see the same issue with mainline v4.9 kernel [1]?
>From what I can understand, disable APST can let you fully install
Ubuntu/Debian, but after some usage, you still have to fsck the disk?
[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.93/
--
You received this bug notification
Sounds possibly like bug 1738838(?). I'm not sure the upstream fix for
that has been released yet, or if it works sufficiently.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1762603
201 - 293 of 293 matches
Mail list logo
