Public bug reported:
Microsoft reported the following kernel config options that were not
set.
Since linux-azure on 22.10 is not at its final version yet, I am
creating this request to track this when the new version is uploaded.
CONFIG_PCI_HYPERV, CONFIG_PCI_HYPERV_INTERFACE, and CONFIG_HIBERNA
** Package changed: kexec-tools (Ubuntu) => kdump-tools (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
Matching subscriptions: Maintainer
https://bugs.launchpad.net/bugs/1908090
Title:
ubuntu 20.04 kdump
For anyone that finds this in a search:
Bionic LP tracking this commit release:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1963717
Focal:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1964422
--
You received this bug notification because you are a member of Kernel
Packages, whic
Works for me as well. Thank you for the quick fix. I thought I was going
to have a run a -proposed kernel package for a few weeks.
--
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/1956401
Ti
@Kelsey, thank you for the quick proposed kernel. I installed it in my
system here and it solved my amdgpu errors completely. It boots quickly
again into the graphical login screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Same here with AMD Ryzen 5 3400G on kernel 5.13.0-23-generic
It never gets to the graphical login screen. I tested with xorg on
21.10, I did not test wayland. I expect that to be the same. I can do
Ctrl+Alt+F4 to get to a text login screen a few mins after booting. This
screen is where I saw the "
Validation results. Proper number of vpus did show up in Bionic, Focal,
Groovy, and Xenial-4.15. The Xenial 4.4 kernel only saw 256 vcpus.
ubuntu@ip-172-31-5-48:~$ uname -r && nproc
4.4.0-1121-aws
144
ubuntu@ip-172-31-5-48:~$ uname -r && nproc
4.4.0-1122-aws
256
ubuntu@ip-172-31-5-48:~$ uname -
cnewcome@wintermute:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
cnewcome@wintermute:~$ cat /proc/version
Linux version 5.3.0-42-generic (buildd@lcy01-amd64-019) (gcc version 7.4.0
(Ubuntu 7.4.0-1ubuntu1~18.04.1))
gcc package upgraded in 18.04 and new kernel compiled with that version
hasn't been released yet.
** Package changed: gcc-defaults (Ubuntu) => linux (Ubuntu)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are
The issue I found is that the walinuxagent Extension installs the 16.04
cuda drivers on Ubuntu 18.04. The issue here is the driver has changed a
bit with the inclusion of libglx-mesa0 in Ubuntu 18.04, where it was not
previously in 16.04.
This causes the failure to install nvidia-driver-* package.
We had similar behavior on GCE by running Elasticsearch through the following
suite of unit tests:
https://github.com/elastic/rally-eventdata-track
The test suite takes about 5 days to run fully and any corruption can be found
by running:
zgrep CorruptIndexException /var/log/elasticsearch/elasti
Public bug reported:
While installing linux-azure package, it installs linux-cloud-tools-
azure
Bionic + linux-azure
The following NEW packages will be installed:
linux-azure linux-azure-cloud-tools-5.0.0-1024 linux-azure-headers-5.0.0-1024
linux-azure-tools-5.0.0-1024 linux-cloud-tools-5.0.0-10
I don't believe this is anything new with the -34 kernel. I accidentally
installed the -32 kernel because I didn't save the sources.list file
with -proposed enabled and it gave me the same error. It appears to be
because the image is not set up for encryption and the cryptsetup-
initramfs package i
Disco verification: SUCCESS (except for crypt error not seen on Eoan
when running update-initramfs)
The package did experience a crypt error while the finish scripts were running
update-initramfs:
update-initramfs: Generating /boot/initrd.img-5.0.0-34-generic
cryptsetup: WARNING: The initramfs im
Eoan Verification: SUCCESS
Eoan:
I1107 01:13:14.719551 1 iotest.go:34] Starting loop...
I1107 01:13:14.719636 1 iotest.go:38] Generating chunk done. Took:
29.737µs
I1107 01:13:14.719693 1 iotest.go:45] Writing chunk done. Took: 44.206µs
I1107 01:13:14.723320 1 iotest.go:49
This was reproduced with the linux-generic kernels. The generic kernels
that experience this behavior are: 5.0.0-31-generic and
5.3.0-16-generic.
This behavior was corrected when the following upstream commits were added to
the lttng-modules package in Bionic:
2ca0c84f0b ("Fix: mm: create the new
Public bug reported:
Background: Napi_tx is a Linux kernel feature that makes the virtio
driver call the skb destructor after the packets are actually “out”
(i.e., at TX completion interrupt), as opposed to immediately after the
packets are enqueued. This provides socket backpressure and is critic
Public bug reported:
Our internal cluster has run into a few ceph client related issues, which were
root caused to be resolved by the following commits:
https://github.com/ceph/ceph-client/commit/f42a774a2123e6b29bb0ca296e166d0f089e9113
https://github.com/ceph/ceph-client/commit/093ea205acd4b047c
** Attachment added: "cloud-init collect-logs"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271884/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https
** Attachment added: "cloud-init analyze blame"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271879/+files/ci-analyze-blame.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
h
I created a test instance and was able to produce most of the data
requested. Attachments incoming.
** Attachment added: "cloud-init analyze show"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271877/+files/ci-analyze-show.txt
--
You received this bug notifi
** Attachment added: "cloud-init analyze dump"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271878/+files/ci-analyze-dump.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
htt
This sosreport contains the systemd analyze blame output. It is from a
test instance that I was able to reproduce this issue on.
** Attachment added: "sosreport-cnewcomer-1559258602-20190530234322.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1830740/+attachment/5271880/+f
issue.
If I run "sudo chvt 1", it will not switch out of that tty again until I
reboot my laptop again. Using 2 through 12 all work and switch the
display to that tty.
Thanks,
Chris Newcomer
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
24 matches
Mail list logo
