Thanks Joseph.
I tested the kernel with OpenBSD and FreeBSD virtual machines and this
patch seems to fix the timing issues.
--
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/1778486
Title:
** Changed in: ubuntu-power-systems
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/1768431
Title:
Request to revert SAUCE patches in the 18.04
Apparently not, but this was the only mentioning of this bug and the it
can be reproduced just the same way (bonding + vlan)
But after trying the mainline 4.18rc2 kernel, the bug is still present
their. So it needs to be fixed upstream first (again).
For reference:
# uname -a
Linux hostname 4.18
** Changed in: ubuntu-power-systems
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/1770095
Title:
Need fix to aacraid driver to prevent panic
FWIW mine appears to have hung during a hidden (invisible to me) step
where it was attempting to set a MOK. I had to first kill the existing
dpkg, then edit /usr/sbin/update-secureboot-policy to change #!/bin/sh
to #!/bin/bash (I was getting a local variable error), then manually run
/usr/bin/perl
I don't see "xhci_hcd :00:14.0: xHCI host controller not responding,
assume dead" in the logs you attached, so it's quite possibly another
issue.
Please file a new bug for that, thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hey folks, just piping in that I am also having this problem. I am on
an encrypted disk, and the build of the kernel modules just hangs.
Please let me know if there is anything I can provide to assist in
debugging.
Note that there appear to be two other related / duplicate bugs: 1769327
and 17756
@Denis,
Have you looked at the RFC patch submitted to linux-serial (see bug
Description)?
The driver provided as fix for this issue will only attach if the BIOS on your
HW describes virtual serial devices with HID's INT3511/INT3512.
--
You received this bug notification because you are a membe
Bionic kernel has the fix already.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: linux (Ubuntu Artful)
Status: New => Won't Fix
--
You received this bug notification because you are a memb
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20180618_150357_00839@/log.gz
i386:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a7
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/1779007
Title:
BUG - vboxdrv.sh - failed: mod
Public bug reported:
romulorafa@romulorafa:~$ virtualbox virtualbox/delete-old-modules boolean true
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (4.15.0-23-generic) or it failed to
load. Please recompile the kernel m
Same issue with Gateway LT20 Netbook (Intel 945GM chipset and 1024x600 display)
running Xubuntu 16.04
Problem began with latest update to Linux 4.13.0-45-generic kernel.
Using recovery mode barely usable but stretches 800x600 across the display.
Booting with 4.10.0-42-generic eliminates the proble
It's an issue for my server too. LXD hangs when I try to restart
containers at times. I'm switching to libvirt until this is resolved.
--
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/1773392
I guess it caused by shim-signed:
Running in non-interactive mode, doing nothing.
--- /var/lib/shim-signed/dkms-list 2018-06-27 22:31:11.289407651 +0100
+++ /var/lib/shim-signed/dkms-list.new 2018-06-27 22:31:11.289407651 +0100
@@ -1,3 +1,3 @@
/var/lib/dkms
/var/lib/dkms/bbswitch
-/va
** 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 eit
@jsalisbury: I had the machine tested with this kernel:
Linux xa-xubu 4.18.0-041800rc1-generic #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
that I found via your link [0].
The result is that in this kernel, the problem is gone. So that sounds
like good news!
I t
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 from
I reproduced the same(?) issue by passing by passing an usb controller
to kvm.(https://www.redhat.com/archives/vfio-
users/2018-February/msg00030.html) When I shut down the virtual machine
and try to start again it always fails. Tested your kernel and still the
same issue. Hope this helps.
** Atta
** Attachment added: "after.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763594/+attachment/5157191/+files/after.log
--
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/1763594
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
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/1776822
Title:
linux: 4.4.0-130.156 -propose
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1776829
Title:
linux-aws: 4.4.0-1062.71
Also, linux-image-ex is not a valid package name. You can see the
kernels you have install with:
sudo dpkg -l | grep linux-image
--
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/1778610
Ti
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get 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/1778610
Title:
package l
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1776826
Title:
linux-kvm: 4.4.0-1029.34
Also, can you post a screen shot or digital picture of the error you see
while trying to boot?
--
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/1778584
Title:
linux-image-3.13.0-151-generi
** Changed in: kernel-sru-workflow/security-signoff
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1776824
Title:
linux-aws: 4.4.0-1024.25
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => Triaged
** Changed in
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the last kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first kernel
Thank you for providing a patch, and making Ubuntu better.
Can you provide some information on the status of the patch with regards
to getting it merged upstream? Has it been sent upstream, what sort of
feedback has it received, is it getting applied to a subsystem
maintainer's tree, etc?
o submi
Are you sure you posted the correct commit? The commit in the bug
description has been in mainline as of v4.10-rc1, so it has always been
in bionic as:
1596b5d i40e: restore workaround for removing default MAC filter
** Tags added: kernel-da-key
--
You received this bug notification because y
I built a v2 test kernel. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1777242
Can you test this kernel and see if it resolves this bug?
Also, can you post the output from dmesg?
--
You received this bug notification because you are a member of Kernel
Packages
I mistakenly filed this exact same bug against xorg-server [1], until
Alan Jenkins made a comment [2] about this one. I'm surprised that not
more people have reported it or registered as affected users.
[1] https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1775593
[2]
https://bugs.launch
When you applied the patch to the 4.4.0-122 kernel did you have to
perform any backporting? I had to with my test kernel, so maybe I
didn't perform the backport properly.
I'll do some investigating to see if a prereq patch is needed, so we
don't have to do any backporting.
--
You received this
I started a kernel bisect between v4.15.0-22 and v4.15.0-23. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
8eca6add0defde203282476d7969a7c13bbd7d91
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsa
I built the next test kernel, up to the following commit:
24040a58379e2f2fa6aa9466911b758073b6bdfa
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1752961
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on y
I see this on 4.13.0-45-generic of Ubuntu 16.04 HWE kernels.
--
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/1748689
Title:
Mounting SMB shares with vers=3.0 in fstab gives "ioctl error i
Please try this kernel, which has some back ported commits to solve the issue:
https://people.canonical.com/~khfeng/lp1763594/
--
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/1763594
Title:
** Changed in: kernel-sru-workflow/automated-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru
Reboot several times, not seeing this issue anymore.
** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/
Hi Laurie,
The easiest way to install the latest update kernel is to enable the
-proposed pocket and install the kernel packages from there, as
documented on https://wiki.ubuntu.com/Testing/EnableProposed.
Thank you,
Kleber
--
You received this bug notification because you are a member of Kerne
Thank you Douglas for the verification!
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1772991
Title:
The only thing that worked for me was downgrading the intel-microcode
package update (using Synaptic and its "force version" option in package
menu), and in particular upgrading to 151 kernel was not a fix for me
(and others apparently).
--
You received this bug notification because you are a mem
For those who see "xhci_hcd :00:14.0: xHCI host controller not
responding, assume dead" in the dmesg, please subscribe to LP: #1763594.
I am building a test kernel for that bug.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Confirming the same issue on Ubuntu Server 18.04 LTS:
Error calling EVIOCSKEYCODE on device node '/dev/input/event2' (scan code
0x9004c, key code 162): Invalid argument
CODE_FILE ../src/udev/udev-builtin-keyboard.c
CODE_FUNC map_keycode
CODE_LINE 103
ERRNO 22
PRIORITY3
Sorry to be late, but to downgrade intel-microcode I used synaptic,
which in the packages menu has the option to force version of a package
and then (after applying change) to hold it against updates. I chose the
only other version listed (2.2014something) and it worked. Hope this
helps.
--
You r
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1778772
Title:
linux-gcp: 4.15.0-101
I currently run on mainline 4.17.3-041703-generic #201806252030 SMP Tue
Jun 26 00:33:17 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux and it didn't
occur again. With the 4.15.0-23 I had up to 4 spontaneous reboots an
office day.
--
You received this bug notification because you are a member of Kernel
P
I now have 4.18.0-041800rc2-generic #201806241430 SMP Sun Jun 24
14:33:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.
No change.
Edit: I just change my description : my idle is > 99% but my load
average is =~ 1.1 (any kernel)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
** Description changed:
I have a many HP ProBook 450 G1 and HP ProBook 650 G3 with fresh install
of Ubuntu Desktop.
They all have a load average of 1.0 when idle (no graphical session
opened).
- vmstat shows idle=0% and waiting=~ 100%
+ vmstat shows idle =~ 100%
The process whic
Comment #1 is invalid, this test does not work on xenial/Azure because
of the module build issue (bug 1765673)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1778642
Title:
ubuntu_
I was able to capture a soft-lock with sysrq-l [1]. Networking and mouse
were still functional, but focusing windows and window activity in
Plasma were locked.
https://gist.github.com/rphillips/fae9540a8e7a3a83731c9a9809a98df4
Notes:
* AMD Ryzen 2700X
* SuperNOVA 650 G3 650W (Eco switch set to
** Tags removed: verification-done-bionic
** Tags added: verification-failed-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1769610
Title:
Support Intel Atom (Baytrail-I) HS-U
Mark this task as Incomplete for the lttng issue (bug 1778642)
4.15.0-1014.14 - azure
Regression test CMPL, RTB.
Issue to note in x86_64 (azure):
ebizzy - failed on Standard_A0, passed on the rest
monotonic_time - tsc failed on some instances, clock failed on
Standard_E4s_v3, Standard_E64-16
This issue could be found on 4.15.0-1014.14~16.04.1 Azure as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1778642
Title:
ubuntu_lttng_smoke_test failed on Azure 4.15
Statu
** Description changed:
+ ***THIS IS A POTENTIAL REGRESSION***
+
+ This test will pass with the older kernel, 4.15.0-1013-azure, but not
+ the 4.15.0-1014-azure in -proposed.
+
It looks like the kernel module can be installed, but four tests have
failed:
== lttng smoke test of session c
Hi Ronak,
Which of the two kernels have you tested?
--
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/1768143
Title:
vmxnet3: update to latest ToT
Status in linux package in Ubuntu:
In
Hardware Certification have begun testing this -proposed kernel.
** Changed in: kernel-sru-workflow/certification-testing
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/certification-testing
Assignee: Canonical Hardware Certification (canonical-hw-cert) =>
Taihsi
Hi,
I have an Intel Atom E3930 system, /dev/ttyS6 device node is no longer exposed
to the userspace starting from 4.15+ Ubuntu kernels.
BTW, it works fine on Debian kernels, for example on 4.16.0-2-amd64
I've tried supposed linux-oem-4.15.0-1006.9 but device node is still
missing, although appea
Setting qemu task to invalid per Colins explanation that the LP case
doesn't use it.
** Changed in: qemu (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin
(cypressyew)
--
You received this bug notification because you are a member
In this cycle the test failed with time difference:
TestFail: Failed to set hwclock back to Warthog's birthday. Output of
hwclock is '2004-10-20 04:09:59.590277+'
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:
** Summary changed:
- fanotify09 in LTP syscall test failed with T/X/A/B kernel
+ fanotify09 in LTP syscall test failed with T/X/A kernel
--
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/177
This issue has passed on Bionic in this cycle:
<<>>
tag=inotify09 stime=1529086352
cmdline="inotify09"
contacts=""
analysis=exit
<<>>
tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s
../../../../include/tst_fuzzy_sync.h:109: INFO: avg_diff = 12ns, avg_dev =
29ns, delay = 00076
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Invalid
** Changed in: kernel-sru-workflow/regression-testing
Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin
(cypressyew)
--
You received this bug notification because you are a member
** Tags removed: need-duplicate-check
--
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/1778851
Title:
package linux-headers-4.15.0-23-generic 4.15.0-23.25 failed to
install/upgrade: inst
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/1778851
Title:
package linux-headers-4.15.0-2
** Changed in: hwe-next
Status: New => Triaged
--
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/1778658
Title:
Nvidia fails after switching its mode
Status in HWE Next:
Triaged
S
Public bug reported:
I've done update to 18.04 from 17.10
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Archite
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 'verifica
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Unattached from this bug being closed because of inactivity I tried
again the DisplayPort adapter under kernel 4.17.3. That didn't work at
all, screen blackouts blinking from the beginning.
** Changed in: linux (Ubuntu)
Status: Expired => Incomplete
--
You received this bug notification b
If there is any more info I can provide, please let me know.
--
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/1762989
Title:
Display Port issues - screen blackouts
Status in linux package
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)
** Tags added: p9 triage-g
** Changed in: ubuntu-power-systems
Importance: Undecided => High
--
77 matches
Mail list logo
