Do you have an non-upgraded machine where you can run the sosreport
prior the upgrade ? then run the upgrade (and if the problem occurs) run
a second sosreport post upgrade ?
- Eric
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Not sure if it's related but I'll leave this here.
We have a bunch of EC2 instances running Ubuntu 18.04 LTS and GitLab
Runner, with the latter configured to execute build jobs inside Docker
containers. Our EC2 instances are of the t2.medium, t2.xlarge and
t3.medium sizes and run in the
and send me the generated sosreport file : sla...@ubuntu.com (if
sensible data) otherwise attach to the lp bug.
--
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/1796376
Title:
Bug
Looks like the issue is not seen with 4.18 kernel , please let me know
still Ubuntu requires the log with 4.15 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/1795453
Title:
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/1795583
Title:
linux-aws:
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/1795585
Title:
linux-aws:
** Changed in: ubuntu-z-systems
Status: Fix Committed => 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/1794346
Title:
check and fix zkey required kernel modules
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-
driver-390)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails
https://bugzilla.kernel.org/show_bug.cgi?id=201379#c6
"Unfortunately we do not have information to determine 'Product' and
'Component'.
The only information we have is that the hanging process is gnome-shell (or at
least that this was the case in at least one instance), that the screen blinks
The commit in the description is the the Cosmic Ubuntu-4.18.0-9 kernel.
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Cosmic)
Importance: Medium
Status: Triaged
**
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1797420
Title:
rtl8192cu driver and D-Link DWA-121 USB WiFi dongle LED
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
@Eric : Sosreport sent by email. Did you try the second time (with
cloud-init installed) to reproduce with unattended upgrades on shutdown
mode ? I did not mention it but upgrading the package outside of
unattended upgrades on shutdown mode works.
--
You received this bug notification because
https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3
We lack the 'Call Trace'
--
Cristian Aravena Romero (caravena)
--
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/1796385
Title:
Hi @kleber-souza,
The kernel fixes the issue. I changed the tag to
verification-done. Thanks!
Christian
** 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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Can you run sosreport from an impacted system ? It may provide more
context.
--
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/1796376
Title:
Bug #1739107 fix causes
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
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/1797080
Title:
linux-gcp:
Could you also test the latest upstream 4.15 stable kernel? It is available
from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.18/
We should be able to perform a reverse bisect to identify the commits in
4.18 that resolve this bug.
** Changed in: linux (Ubuntu)
Importance: Undecided
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
Actually, instead of testing proposed, 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"
--
You received this bug
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags
Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19
Also another version (other than default version of Ubuntu 18.04.01) of
4.15 kernel fixes the issue
--
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/1795453
Title:
IO's are issued with
Private bug reported:
Every time you run an nvme format on a Intel NVMe drive (whether
specifying the secure/crypto erase options or not), the format
apparently works (drive is wiped clean) but the drive's admin queue
(queue 0) times out, making the nvme device driver flag an error and
reset the
** 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-oem in Ubuntu.
https://bugs.launchpad.net/bugs/1793338
Title:
Fix unusable NVIDIA GPU after S3
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
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/1797062
Title:
linux-gcp: 4.15.0-1023.24
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
--
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/1797061
Title:
linux: 4.15.0-38.41 -proposed
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
@Eric : The server was installed with a 4.15.0-34.37 kernel from a
corporate OS image, and linux-cloud-tools-common package was also in
version 4.15.0-34.37. All packages where in state "ii".
I dist-upgrade the server with APT (to version 4.15.0-36.39) and only
downgrade the
** Changed in: ubuntu-z-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/1793086
Title:
qeth: use vzalloc for QUERY OAT buffer
Status
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => 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/1795589
Title:
linux-kvm:
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
I have the same.
I have the less loaded instances in my real environment crashing and
the environment where I am trying to reproduce the issue stressing it
not crashing.
I am finding a way to reproduce it.
How did you reproduce it?
--
You received this bug notification because you are a
So far the best I could reach is get the kernel call trace but not
crashing the node yet.
Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.306845] INFO: task java:1932
blocked for more than 120 seconds.
Oct 12 15:33:41 ip-10-16-21-10 kernel: [10919.308573] Not tainted
4.4.0-1069-aws
I built the next test kernel, up to the following commit:
cc2180a5880d0fd8491182cdc65e8df9696a7c9e
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788997
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
Can you confirm the state of the package pre-upgrade ?
--
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/1796376
Title:
Bug #1739107 fix causes linux-cloud-tools-common not to be
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
--
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/1796351
Title:
linux-gcp: 4.18.0-1002.3
Seems to me like the package "4.15.0-34.37" was already not in "ii"
state :
2018-10-10 10:16:57 status half-configured
linux-cloud-tools-4.15.0-34-generic:amd64 4.15.0-34.37
2018-10-10 10:16:57 status half-installed
linux-cloud-tools-4.15.0-34-generic:amd64 4.15.0-34.37
2018-10-10 10:16:57
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-cosmic
** Tags removed: block-proposed
--
You received this bug notification
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
--
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/1796350
Title:
linux-azure:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
** Changed in: kernel-sru-workflow/promote-to-proposed
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/1797379
Title:
linux: 4.18.0-10.11
** Changed in: linux (Ubuntu Cosmic)
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/1790832
Title:
crypto/vmx - Backport of Fix
** 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
** Description changed:
This issue was fixed in the upstream 4.13 kernel, so the devel release
(and bionic) of ubuntu are no longer affected, closing.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hi! I have an Omen by HP 15-ce004la with NVIDIA GTX1060 Q-MAX and the
bug is still present.
This is my setup:
Ubuntu 18.04 with kernel 4.18.13-041813-generic
I'am getting acpi errors like this one below in boot time too:
[0.104082] ACPI BIOS Error (bug): Failure creating
Hi,
it was a great idea to test by running without installation,
and i test it on:
ubuntu-16.04.1-desktop-amd64 - don't see my Bluetooth headset
ubuntu-17.10.1-desktop-amd64 - same problems with skipping as with current
version
ubuntu-18.04-desktop-amd64 - same problems with skipping as with
Still no apparent issue on my side.
# dpkg
ii cloud-init18.3-9-g2e62cb8a-0ubuntu1~18.04.2 all
Init scripts for cloud instances
ii linux-cloud-tools-common 4.15.0-36.39 all
Linux kernel version specific cloud tools
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
This bug was fixed in the package linux - 4.18.0-9.10
---
linux (4.18.0-9.10) cosmic; urgency=medium
* linux: 4.18.0-9.10 -proposed tracker (LP: #1796346)
* Cosmic update: v4.18.12 upstream stable release (LP: #1796139)
- crypto: skcipher - Fix -Wstringop-truncation warnings
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => 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/1797066
Title:
linux-aws: 4.15.0-1025.25
Skipped "x86/speculation/l1tf: Fix up pte->pfn conversion for PAE"
because we already use the proper conversion.
Skipped because we already applied it for CVE-2018-6554
* "irda: Fix memory leak caused by repeated binds of irda socket"
Skipped because we already applied it for CVE-2018-6555
*
** Changed in: kernel-sru-workflow/verification-testing
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1795596
Title:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => 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/1797359
Would it be possible for you to test the proposed kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.
Thank you in advance!
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
**
This occurred right after I upgraded to 18.10 from 18.04.1.
Earlier today I got an apt upgrade to kernel 4.18.0-9-generic.
The machine is much more stable now.
I can't test further at the moment.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Here's the log from the failing VM. Doesn't look too unusual to me...
https://paste.ubuntu.com/p/JpmSxmwjfM/
** Description changed:
Using latest MAAS master, I'm unable to compose a VM over the UI
- successfully. BY this it means that the VM is created, but it fails with
- a kernel panic.
-
Xenial SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-October/096035.html
Bionic SRU request:
https://lists.ubuntu.com/archives/kernel-team/2018-October/096032.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
It will be good if you could provide us the exact commit (Patch) which
fixes the issue
--
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/1795453
Title:
IO's are issued with incorrect
** Summary changed:
- Composing a VM in MAAS with exactly 2048 MB RAM causes kernel panic
+ Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 1797581
and then change the status of the bug to 'Confirmed'.
If, due to the
And /var/log/libvirt/qemu/.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/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
kernel panic
Status in
This only happened once so far. One too many.
--
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/1797349
Title:
GPU hang, full freeze / lockup
Status in linux package in Ubuntu:
** Description changed:
- == Comment: #0 - Paulo Flabiano Smorigo
+
+ == SRU Justification ==
+ IBM is requesting this patch in all releases order to fix the sleep-in-atomic
+ bugs in AES-CBC and AES-XTS VMX implementations.
+
+ This patch is a clean cherry pick and has already been applied to
@Bounty
Could you temporarily change the video card to rule out problems with
it?
Your current video card is:
[AMD/ATI] Curacao PRO [Radeon R7 370 / R9 270/370 OEM]
Best regards,
--
Cristian Aravena Romero (caravena)
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You
Here's an example of working XML (with 2047 MB RAM) that MAAS generated:
https://paste.ubuntu.com/p/mkF6Kp4hx8/
And here's an example of non-working XML (with 2048 MB RAM) that MAAS
generated:
https://paste.ubuntu.com/p/27HHDrzwm8/
** Changed in: linux (Ubuntu)
Status: Incomplete =>
Here's the version information.
libvirt-bin:
Installed: 4.0.0-1ubuntu8.5
Candidate: 4.0.0-1ubuntu8.5
Version table:
*** 4.0.0-1ubuntu8.5 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
4.0.0-1ubuntu8.2 500
I'm unable to recreate with a daily bionic cloud-image on a bionic host
with the same versions.
% sudo apt install uvtool libvirt
% uvt-simplestreams-libvirt -vv sync --source
http://cloud-images.ubuntu.com/daily 'supported=True' arch=amd64 release=bionic
% uvt-kvm create --memory 2048 --cpu 1
The backing image:
/var/lib/libvirt/maas-images/e5d185a9-8ccb-4ca6-959a-bd8eff0ee184
What boot image is that? Can I get a copy of that from maas-images? or
how is it created?
On the node with the vm that fails, can you:
virsh start --console
Assuming it's a normal ubuntu image which has
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Cosmic)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia-
driver-390)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails
https://bugzilla.kernel.org/show_bug.cgi?id=201393
--
Cristian Aravena Romero (caravena)
** Bug watch added: Linux Kernel Bug Tracker #201393
https://bugzilla.kernel.org/show_bug.cgi?id=201393
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=201393
Importance:
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-release
Status: New => Confirmed
** Tags removed: block-proposed-cosmic
** Tags removed: block-proposed
--
You received this bug notification
Public bug reported:
tc filter seems still leak with ubuntu kernel 4.15.0-36-generic,
it can be reproduced with the following steps.
```
tc qdisc add dev eth0 ingress
tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip
dst 192.168.5.113/32 police rate 10Mbit burst
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04
apt-cache policy pkgname
N: Unable to locate package pkgname
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-53-generic 3.13.0-53.87
ProcVersionSignature: Ubuntu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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/1797670
Title:
upgrading to 16.04 bug
The packages appear to still be the build from 10/01.
--
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/1752961
Title:
With kernel 4.13 btrfs scans for devices before all devices have been
I've got some interesting news. I did in fact contact Acer Support and
opened a case. Went from Lvl1 to Lvl2 support, was called a couple weeks
later with a survey about support, I gave my honest opinion, stating
that I don't blame support team as they are limited in what they can do.
Today I
hi,
FINALLY, i was able to localize problem :)
all my headsets are skipping only when setting window is open!
so basically when you click test left or test right - it is in settings window
and thus it sounds terribly.
But, if you close setting window - every headset works just fine (on online
Here's a full console log from the failure.
https://paste.ubuntu.com/p/zmS7CP7NKr/
--
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/1797581
Title:
Composing a VM in MAAS with exactly
No, they started in a fresh new installation (18.04).
Sorry, I can't test it anymore cause I changed to Deepin and, last month, I
changed back to Ubuntu but I completely removed gnome and installed DDE as my
window manager. So sorry.
--
You received this bug notification because you are a
acpidump:
5B10: 39 5F 48 49 44 00 A0 13 93 54 43 50 44 0A 02 A4 9_HIDTCPD...
5B20: 0D 53 59 4E 41 33 32 35 35 00 A0 13 93 54 43 50 .SYNA3255TCP
5B30: 44 0A 03 A4 0D 41 4C 50 53 31 32 31 45 00 A4 0D DALPS121E...
5B40: 45 4C 41 4E 34 36 39 44 00 08 45 49 43 30 11 21
** Tags added: regression-testing-passed
--
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/1797379
Title:
linux: 4.18.0-10.11 -proposed tracker
Status in Kernel SRU Workflow:
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 1797581
and then change the status of the bug to 'Confirmed'.
If, due to the
Adding the linux package; we should narrow down the issue to see if it's
in kernel space or user space.
** Summary changed:
- [2.5, UI] Composing a VM over the UI is broken - VM has kernel panic
+ [2.5] Composing a VM with 2048 MB RAM causes kernel panic
** Changed in: maas
Status:
To be clear, the kernel panic is seen when a VM is composed in MAAS with
exactly 2048 MB of RAM. Composing with 2047 or 2049 MB RAM results in a
working VM.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We can't run apport-collect since the machine doesn't boot, but this was
seen with a non-tainted 4.15.0.36-generic kernel in my environment.
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
- [2.5] Composing a VM with 2048 MB RAM causes kernel panic
+ Composing
I can't see anything obvious in the sosreport, minus the fact I clearly
see the package in "iFR" state.
I asked a colleague of mine to test in Azure to double-check but my KVM
guest tests look good so far :
# apt-get install linux-cloud-tools-common -y
Reading package lists... Done
Building
Can you attach the guest xml and host kernel/qemu/libvirt packages?
--
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/1797581
Title:
Composing a VM in MAAS with exactly 2048 MB RAM causes
1 - 100 of 202 matches
Mail list logo
