Not targetted to be enabled in the installers for 19.04, due to ongoing
usability & correctness questions.
** No longer affects: s390-tools (Ubuntu Bionic)
** Changed in: debian-installer (Ubuntu)
Status: New => Incomplete
** Changed in: subiquity
Status: New => Incomplete
** Chan
Looks like this got pulled into mainline:
$ git describe 2448a299ec416a80f699940a86f4a6d9a4f643b1
v4.20-rc5-2-g2448a299ec41
$ git describe 78b1a52e05c9db11d293342e8d6d8a230a04b4e7
v4.20-rc5-3-g78b1a52e05c9
Should we request kernel team to pull these into ubuntu SRUs trees? or
have these been alr
i think this is referenced as a duplicate.
** 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/1726362
Title
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Tags added: bot-stop-nagging
** Package changed: udisks (Ubuntu) => udisks2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
** Description changed:
- Description: only when trying to change some attributes chzdev fails because
it cant find modprobe under Ubuntu 18.04
-
- root@m83lp09:~# chzdev zfcp --type datarouter=0 dbflevel=5
- sh: 1: /usr/sbin/modprobe: not found
-
Given that python2 is effectively EOL soon, and python3 has been
available since forever... the switch must happen. Including stable
releases of kernel, imho.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.la
Tested xenial live session with stock systemd/udev and upgraded one from
proposed. My dell laptop is not affected by this issue. But at least
rfkill keys still work for me with both old and new systemd/udevd and
there are no error messages in dmesg.
** Tags removed: verification-needed verificatio
Either this change will make the rfkill button work (good), or not
(current behaviour). Given the code paths, validating similar SKUs for
non-regression is a good enough confidence level that this change
doesn't regress other/unrelated machines. It's a low risk to accept this
change as is, because
Public bug reported:
When running autopkgtests one is located at the top of the unpacked debian
source tree.
There is no location given as to where that is, in an environment variable, but
it is trivial to cache it.
Also, one is supposed to use AUTOPKGTEST_TMP directory for most of the disk
spa
i downloaded that, and tried to poke it.
First of all, i've never seen a 77MB tarball of /sys alone.
Also unpacking that, is dangerous as it does explode in size. However, is
debugging that, please only _list_ the files present in the tarball and only
extract things you need/want.
Reuploaded to
The default sysctl setting for kernel.sysrq in Ubuntu is 176 (and was in
bionic and xenial) and it is shipped in /etc/sysctl.d/10-magic-
sysrq.conf file. This file is provided by a required package from the
minimal task, called `procps`.
176 enables:
128 - allow reboot/poweroff
32 - enable remount
linux-modules-4.18.0-8-generic has:
./lib/modules/4.18.0-8-generic/kernel/arch/s390/crypto/paes_s390.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/pkey.ko
./lib/modules/4.18.0-8-generic/kernel/drivers/s390/crypto/zcrypt.ko
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: s390-tools (Ubuntu)
Status: New => In Progress
--
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 locations in
** Also affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
--
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
Joseph Salisbury (jsalisbury) why did you move it from linux src to
autopkgtest src?
the unpacked src tree is there and it linux kernel source package that
needs fixing!
Specifically the code that is cloned from and executed by debian/tests/*
in the src:linux
** Also affects: linux (Ubuntu)
I
* Temporarily disable ZFS tests on s390x due to conflict between
zfsutils-linux and s390-tools (LP: #1788314)
however bionic was never affected, and cosmic has been long fixed
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-failed verification-f
Hi,
I recommend you to change your test system.
For example, you can modify /etc/systemd/system.conf and change DefaultTasksMax
there. But that is for the systemd started units...
Note that TasksMax these days can accept % values of kernel configured max
tasks too, meaning i.e. one can set it t
** No longer affects: systemd (Ubuntu Cosmic)
** Tags added: cosmic
--
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/1776654
Title:
systemd upstream sysusers tests fails
Status in linux
How is reboot requested/triggered?
Systemd has 30min timeout on the reboot, so things must timeout and
force-self-reboot after 30min.
** No longer affects: systemd (Ubuntu Bionic)
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
** Changed in: klibc (Ubuntu Cosmic)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
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/1760106
Title:
FFe: Enable configur
** Changed in: systemd (Ubuntu Xenial)
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/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM Priority P
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
--
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/1762385
Title:
dell_wmi: Unknown key codes
Status in OEM Pr
Could you please download and install
https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702/+files/finalrd_3_all.deb
(this is a link from
https://launchpad.net/ubuntu/+source/finalrd/3/+build/15227702 )
And check if that helps with reboots? This should perform pivot-root
from rootfs to i
Ideally, we'd want to bisect and fix the kernel itself to reliably
shutdown. yanking ahci sounds like a large hammer. Invalidating systemd
task, and pinging kernely people.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
--
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/1796346
Title:
linux: 4.18.0-9.10 -proposed tracker
** Changed in: debian-installer (Ubuntu Cosmic)
Status: New => 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/1796346
Title:
linux: 4.18.0-9.10 -proposed tracker
St
@cborntra
At the moment, fix committed is the kernel only for bionic & cosmic.
Please check and comment if the kernels look sane to be released into
-updates.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
** Tags added: verification-done-cosmic
--
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/1787405
Title:
[FEAT] Guest-dedicated Crypto Adapters
Status in Ubuntu on IBM z Systems:
In Prog
Ok, so we are now awaiting for this to be accepted into the -proposed
from the queue, as I do see crash in bionic unapproved queue at
https://launchpad.net/ubuntu/bionic/+queue?queue_state=1&queue_text=crash
** Changed in: crash (Ubuntu Bionic)
Status: Incomplete => Confirmed
--
You recei
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
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/1792957
Title:
Provide mode where all vCPUs on a core m
Public bug reported:
s390x qemu vt220 terminal, tput cols and lines is reported as 80x24,
whilst that's not true.
The number of columns is semi-true, as the shell wraps them, however,
one can print things beyond 80 cols.
Ideally resizing qemu window, should manage to report the actual number
of
tput reset -> breaks the terminal
resizing the qemu window -> fixes things
Thus e.g. SIGWINCH is probably handled correctly. However it seems like
there is terminal definitions missing or something.
** Tags added: s390x
--
You received this bug notification because you are a member of Kernel
P
** Changed in: ubuntu-z-systems
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu)
Status: Triaged => 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/17994
Public bug reported:
On an LPAR, execute Customize/Delete Activation Profile. Customize
profile. In security section, tick "Input/Output (I/O) configuration
control". Save. Ok. Close.
Execute Deactivate task.
Execute Activate task.
ssh into lpar.
Try to modprobe hmcdrv module, whilst setting ca
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217764/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217761/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.lau
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217766/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217765/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217769/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217763/+files/Lspci.txt
--
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/1806115
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217767/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217768/+files/UdevDb.txt
--
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/1806115
dmesg output:
[ 61.741644] Hardware name: IBM 2964 N63 400 (LPAR)
[ 61.741645] Krnl PSW : d4fd3f9b 8aabe5b8
(__alloc_pages_nodemask+0xe96/0x1068)
[ 61.741649]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0
RI:0 EA:3
[ 61.741650] Krnl GPRS:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1806115/+attachment/5217762/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
Looking at the source code, it seems like the __get_free_pages call is
failing. But I don't know what is the significance of said call, and why
it fails beyond the 1MiB limit.
/**
* hmcdrv_cache_startup() - startup of HMC drive cache
* @cachesize: cache size
*
* Return: 0 on success, else a (n
So. I'm working on the new server installer for s390x, and it already
works quite good on qemu/kvm.
(whilst most of the UX improvements are not visible in the daily images,
it does boot and completes the install in qemu/kvm. We have colors
support, and partitioning changes/improvements staged in g
Well, we discussed the performance. It seems like this interface is not
meant to be used as a backing storage for rootfs.
Will try other options instead.
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: ubuntu-z-systems
Status: New => Won't Fix
--
You r
Can I have like vt1-7, on per-HMC/zvm/user basis, exported and wired up
via HMC/c3270/qemu-serial? =)
** No longer affects: ncurses (Ubuntu)
** No longer affects: qemu (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: ubuntu-z-systems
Status
Confirming libvirt task back on, as there are appear to be a few small
patches for libvirt.
** Changed in: libvirt (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Cosmic)
Importance: Undecided
St
** Branch unlinked: lp:~xnox/britney/hints-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/1790513
Title:
kdump-config status - not ready to kdump with v4.18 kernel
Status in linu
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1817097
Title:
pvmove causes file system corruption without not
"automated-testing: Stalled -- testing FAILED" -> is this autopkgtests?
cause in-distro they look all green / all good.
http://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#linux-meta
Or is this some other automated testing?
--
You received this bug notification b
I see that this bug was created with Ubuntu 18.10 (judging by the tags).
I am trying to reproduce the issue on Ubuntu 19.04 (current development
release).
I am failing to produce a mixed blocksize cryptsetup device:
$ sudo cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1
is faili
Ok, reproduced this on x86_64 with raw files which are in multiples of
4k.
This is not an architecture specific 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/1817097
Title:
pvmo
This is a well-known upstream issue/bug.
This is not s390x, Ubuntu 18.10, any other Ubuntu release specific.
There is no dataloss -> one can execute pvmove operation in reverse (or i guess
onto any 512 sector size PV) to mount the filesystems again.
Thus this is not critical at all.
Also, I am f
/etc/mke2fs.conf:
[defaults]
blocksize = 4096
[fs_types]
small = {
blocksize = 1024
inode_size = 128
inode_ratio = 4096
}
We default to 4k, unless one is formatting small filesystems which from manpage:
If the filesystem size
klibc ftbfs on i386 in disco.
--
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/1760106
Title:
FFe: Enable configuring resume offset via sysfs
Status in OEM Priority Project:
Fix Release
ibc (Ubuntu Cosmic)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
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/1760106
Title:
FFe: Enable configuring resume offset via sysfs
I believe I am affected, trying this out using the kernel from comment
44.
--
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/1678184
Title:
APST quirk needed for Samsung 512GB NVMe drive
S
Wasn't scrashme renamed into trinity in December 2010 (as per
https://lwn.net/Articles/536173/)?
https://github.com/kernelslacker/trinity
Trinity claims s390x support and compiles successfully for me.
--
You received this bug notification because you are a member of Kernel
Packages, which is su
On 12 May 2017 at 15:30, Louis Bouchard wrote:
> Hello,
>
> Well, this is to be expected as the postinst script will only change the
> target of the symlink if the architecture is ppc64EL and not ppc64LE (
> EL != LE).
>
> Now if both are interchangeable (I must admit my ignorance of this
> archit
@twetzel21 this is not related to those changes at all.
--
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/1835660
Title:
initramfs unpacking failed
Status in OEM Priority Project:
New
St
** Changed in: grub2 (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => 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/1835660
Titl
so what grub is doing is correct.
It pads/aligns every initrd by 4, which is fine, and as per spec.
https://www.kernel.org/doc/html/latest/driver-api/early-userspace
/buffer-format.html
initramfs size can be filled with arbitrary amount of "\0" all the way
upto initramfs_size.
"In human terms,
** Description changed:
"initramfs unpacking failed: Decoding failed", message appears on boot
up.
If I "update-initramfs" using gzip instead of lz, then boot up passes
without decoding failed message.
---
However, we currently believe that the decoding error reported in dmes
starting verification of the groovy's build. It will take a bit of time
=)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1905620
Title:
please promote modules from extra to module
Deployed focal image.
And checked where currently loaded modules are coming from
$ cat /proc/modules |cut -f1 -d\ | xargs -L1 modinfo | sed -n 's/filename:
*//p' | xargs dpkg -S
linux-modules-5.4.0-24-generic:
/lib/modules/5.4.0-24-generic/kernel/drivers/uio/uio_pdrv_genirq.ko
linux-modules-5.4
and it looks like that is failing to reboot over telnet connection =/
i'll build a brand new image with 5.8.0-11 kernel directly and will try
that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchp
Built a fresh riscv64 image with
$ dpkg-query -W linux-* | grep 5.8
linux-generic 5.8.0.11.11
linux-headers-5.8.0-11-generic 5.8.0-11.13
linux-headers-generic 5.8.0.11.11
linux-image-5.8.0-11-generic5.8.0-11.13
linux-image-generic 5.8.0.11.11
linux-image-unsigned-5.8.0-11-generic
l
@mihajlov
that is a good point. When there are less than 4GB of RAM, the default
cryptsetup benchmark should probably be capped at 128M of RAM, rather
than 1-2GB. Will ponder about that.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to mak
** Changed in: s390-tools (Ubuntu Focal)
Milestone: None => ubuntu-20.04.2
--
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/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
I've already bootstrapped rustc using these changes. In both focal &
groovy. This is really good!
For me it was enough to have it just in -proposed. But yeah, we do need
this in -updates too.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this
@julian Ubuntu Desktop in 20.04.2 will receive the 20.10's kernel by
default and thus will adopt the 20.10 default. Imho the linux-generic
(ga) kernel should also be updated to the same default, to make it the
same across -generic, -hwe, -oem kernel flavours in 20.04. Because in
20.04, defaulting t
@colin-king with or without additional measurements default to
performance and relying on userspace to switch to ondemand at some later
point during boot is wrong. It means we are risking melting laptops and
catching fire. I.e. boot machine, walk away, it sits in the initrd at
the LUKS unlock promp
Public bug reported:
linux-generic-hwe-20.04 transitional to linux-generic does not exist in
groovy, instead it still points at 5.4 kernel.
Please create transitional meta from linux-generic-hwe-20.04 to linux-
generic.
Otherwise machines that installed Ubuntu Desktop focal, then upgrade to
groo
** Changed in: linux (Ubuntu)
Status: Fix Committed => In Progress
** Changed in: ubuntu-z-systems
Status: Fix Committed => In Progress
** Package changed: linux (Ubuntu) => zfcpdump-kernel (Ubuntu)
** Changed in: zfcpdump-kernel (Ubuntu)
Assignee: Canonical Kernel Team (canon
All tests run automatically, and yes flatpak-builder was automatically
tested and new flatpak with this fix migrated fine.
See http://autopkgtest.ubuntu.com/packages/flatpak-builder/groovy/s390x
** Also affects: flatpak (Ubuntu)
Importance: Undecided
Status: New
** Changed in: flatpak
** Changed in: linux-meta (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1893205
Title:
linux-generic-hwe-20.04 transitional to linux-gener
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
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/1894611
Title:
kmod in bionic can't parse hwe/cloud kernel sign
Public bug reported:
* linux lacks CET, not upstream yet
* snapd lacks CET, as golang has no support for CET yet
* libunwind lacks CET, as no upstream support yet
* klibc lacks CET, no upstream support yet
** Affects: golang-defaults (Ubuntu)
Importance: Undecided
Status: New
**
Yes, kexec-tools should ship finalrd hook to fix this.
** Changed in: finalrd (Ubuntu)
Status: New => Won't Fix
** Changed in: kexec-tools (Ubuntu)
Status: New => Triaged
** Changed in: kexec-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification be
Public bug reported:
[Availability]
* Groovy Universe
[Rationale]
* Needed to apply microcode updates, on bare-metal public-cloud
machines, that otherwise boot without a full initrd.
[Security]
* This package is tiny, just a single small shell script trigger hook
that create microcode-init
https://lists.ubuntu.com/archives/kernel-team/2020-September/113356.html
** Package changed: linux-aws (Ubuntu) => linux-meta-aws (Ubuntu)
** Changed in: linux-meta-aws (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, wh
** 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/1863116
Title:
debian/rules editconfigs does not work on s390x to change
i think this was since fixed, no?!
** Tags removed: update-excuse
--
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/1721558
Title:
ubuntu-regression-suite fails
Status in linux packag
** Also affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Changed in: netplan.io (Ubuntu)
Status: New => Confirmed
** Changed in: netplan.io (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Pack
https://www.freedesktop.org/software/systemd/man/systemd.network.html#VRF=
VRF= The name of the VRF to add the link to. See systemd.netdev(5).
vrf A Virtual Routing and Forwarding (VRF) interface to create separate
routing and forwarding domains.
[VRF] Section Options
The [VRF] section only app
Public bug reported:
[Impact]
* Currently Canonical Livepatch service is signing kernel modules that
are not trusted by the default Ubuntu kernels
* to make Canonical Livepatch service out of the box compatible with
SecureBoot, please add Canonical Livepatch service key as trusted in the
kerne
** Description changed:
[Impact]
- * Currently Canonical Livepatch service is signing kernel modules that
+ * Currently Canonical Livepatch service is signing kernel modules that
are not trusted by the default Ubuntu kernels
- * to make Canonical Livepatch service out of the box compa
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Description changed:
[Impact]
* Currently Canonical Livepatch service is signing kernel modules that
are not trusted b
@balint
Kernel has no facility to startup in one mode, and later transition to
another.
I think maybe we should measure the difference between "performance,
then on demand" vs "balanced performance".
If the difference is not significant, maybe we can simply change the
kernel default to "balanced
1) Did you intend for this bug report to be publicly visible against
public Ubuntu Project? Instead for example using a private bug report
against private project for this platform? Usually certification
escalations arrive differently.
2) Can you please describe the raid controller? Is it hardware
4) Is this bug report reproducible with Legacy Server installer?
The one from http://cdimage.ubuntu.com/ubuntu-legacy-
server/releases/20.04/release/
--
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: subiquity
Status: New => Incomplete
** Changed in: grub2 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
Public bug reported:
# apt install linux-libc-dev:amd64 linux-libc-dev:riscv64
Reading package lists... Done
Building dependency tree
Reading state information... Done
linux-libc-dev is already the newest version (5.4.0-26.30).
Some packages could not be installed. This may mean that you ha
Should kernel team even own linux-libc-dev ? Maybe foundations should
hijack linux-libc-dev away from kernel team, and let us handle it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs
301 - 400 of 1816 matches
Mail list logo
