** 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/1829749
Title:
[MIR] Please add support for SIPL
Status in Lau
https://lists.ubuntu.com/archives/kernel-team/2019-July/102204.html
https://lists.ubuntu.com/archives/kernel-team/2019-July/102205.html
--
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/18297
Public bug reported:
zfs-units fire by default on host and container, even when there are no
zfs filesystems
instead of enabling units by default, they should be pulled in by udev.
udev already modprobes zfs module when it notices any zfs filesystems, and it
should also enable the scan/import/et
Public bug reported:
Enable CONFIG_SCSI_UFS_QCOM as a module on arm64.
SCSI_UFS_QCOM this enables UFS storage on QCOM based laptops such as Lenovo
Yoga C630.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: In Progress
** Changed in: linux (Ubuntu)
Status: New
https://lists.ubuntu.com/archives/kernel-team/2019-July/102465.html
--
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/1837332
Title:
Please enable CONFIG_SCSI_UFS_QCOM as a module on arm64
It's funny how long it took them to figure it out, but yes
https://bugzilla.redhat.com/show_bug.cgi?id=1195029#c22
is the right answer. Please use that patch / combination of tagging the
device with tag&wants using udev rule + making the service bind to it.
--
You received this bug notification
Public bug reported:
[Impact]
* linux autopkgtest should only execute either rebuild tests, when triggered
by toolchain.
or execute regression suite when triggered by meta
but never both. As otherwise, it results in false negative results for the
kernel
[Test Case]
* Trigger adt test
** Also affects: subiquity
Importance: Undecided
Status: New
** Tags added: rls-dd-incoming
--
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/1534162
Title:
symlinks managed by k
I think last time it was fixed by fixing base-installer.
http://launchpadlibrarian.net/235185956/base-installer_1.158ubuntu1_1.158ubuntu2.diff.gz
but this time around, we need to decide who/what/where should write out
kernel-img.conf.
because we do not have kernel-common by default.
** Also affe
** Also affects: curtin
Importance: Undecided
Status: New
** Changed in: livecd-rootfs (Ubuntu)
Status: New => Invalid
** Changed in: curtin
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Description changed:
+
+ On Ubuntu/Debian like systems /etc/kernel-img.conf should be created by the
"installer". It is currently done by base-installer/live-installer/ubiquity but
not curtin, but it should be. At the moment we require kernel-img.conf and we
do not have the correct per-arch
Public bug reported:
Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: squashfs_read_data failed
to read block 0x6ff3660032757063
Apr 11 18:32:52 ubuntu-server kernel: SQUASHFS error: Unable to read metadata
cache entry [6ff3660032757063]
Apr 11 18:32:55 ubuntu-server kernel: SQUASHFS error:
got a few more tweaks to the storage test, and it's now more
consistently passing on all other architectures but ppc64le.
--
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/1814373
Title:
st
Public bug reported:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on
amd64, meaning s
Public bug reported:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on
amd64, meaning s
** Description changed:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as w
*** This bug is a duplicate of bug 1824864 ***
https://bugs.launchpad.net/bugs/1824864
** This bug has been marked a duplicate of bug 1824864
CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64
--
You received this bug notification because you are a member of Kernel
Packages, which is subs
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at lea
`| lz4 > date.img` is incorrect
One must use `lz4 -9 -l`
For xz one should use `xz --check=crc32`
--
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/1840945
Title:
Concatenated lz4 initrds
Should we match these defaults for initramfs too?
At the moment I have switched to lz4 across the board, but maybe it does
make sense to use lzo on s390x and gzip on armhf, etc.
Should I escalate to IBM supporting lz4 on ppc64le?
--
You received this bug notification because you are a member of
Public bug reported:
Please include DTBs from qcom for-next tree:
arm64: dts: qcom: Add Asus NovaGo TP370QL
arm64: dts: qcom: Add HP Envy x2
arm64: dts: qcom: Add Lenovo Miix 630
https://git.kernel.org/pub/scm/linux/kernel/git/qcom/linux.git/log/?h
=for-next
In foundations, we have Miix 630 and
** Also affects: e2fsprogs (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lvm2 (Ubuntu)
Status: Incomplete => Invalid
** Changed in: e2fsprogs (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packag
Public bug reported:
Please add support for zipl ("z/ecureBoot") signing.
It should be similar to opal signing, but using the new zipl signing
key.
I am expecting to sign s390-tools stage3.bin and kernel images using
this key.
s390-tools -> can be signed already
kernels -> should only sign v5.2
$ cat /boot/config-5.0.0-16-generic | grep LOG_BUF
CONFIG_LOG_BUF_SHIFT=18
CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT=13
$ uname -a
Linux doerfel 5.0.0-16-generic #17-Ubuntu SMP Wed May 15 10:54:19 UTC 2019
aarch64 aarch64 aarch64 GNU/Linux
And journal shows complete kernel boot messages, thus this all no
I do wonder, if we can somehow arch-specify opal signing.
Cause it's opal for power, zipl for s390x, yet both just use kmodsign.
Just a different key.
Not sure if i want to copy&paste all the methods, and tests.
--
You received this bug notification because you are a member of Kernel
Packages,
Can kernel team elaborate on this ticket?
Cause as far as I can tell, we can change flash-kernel / boot.scr in
eoan, and kernels do support compressed images on armhf And rewrite
boot.scr on upgrade to eoan+
Is there something that I'm missing from shipping compressed kernels
here? Something
Public bug reported:
[CONFIG] please enable highdpi font FONT_TER16x32
This is now available in v5.0
config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136a
Public bug reported:
[CONFIG] please enable highdpi font FONT_TER16x32
This is now available in v5.0
config/config.common.ubuntu:# CONFIG_FONT_TER16x32 is not set
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/diff/lib/fonts/Kconfig?id=ac8b6f148fc97e9e10b48bd337ef571b1d1136a
I am in ecstasy! this is so good! OMG! My eyes! I love this!
After installing your kernel, one needs to enable the font in console-
setup too:
$ cat /etc/default/console-setup | grep '^FONT'
FONTFACE="TER"
FONTSIZE="16x32"
Then i did update-initramfs, and rebooted, and omg how nice my tty is
now
Indeed, i booted the stock kernel with my new console-setup settings...
and i get readable ttys still.
And the config for your kernel did not appear to list 16x32 there
either.
Can you please share the source for the kernel you have built?
Also I wonder where the TER 16x32 font is coming from, a
nested kvm is disabled by default on s390x. One can force-enable that by
booting with kernel cmdline kvm.nested=1 in /etc/zipl.conf and rerun $
sudo zipl; and reboot.
However, I'm confused why this is filed, when this is the expected
default behaviour and has been previously raised and discussed i
** Changed in: systemd (Ubuntu Eoan)
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/1814373
Title:
storage / luks / dmsetup regressed (or got
Public bug reported:
linux-oracle 4.15.0-1014.16 FTBFS
http://autopkgtest.ubuntu.com/packages/l/linux-oracle/disco/amd64
Note that rebuild test is failing, blocking SRU of reverse-build
dependency, as it appears as if openssl is breaking compiling linux-
oracle.
HOSTCC scripts/selinux/genhe
Possibly duplicate bug reports:
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1823429
https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1826993
** Changed in: linux-oracle (Ubuntu)
Importance: Undecided => High
** Changed in: linux-oracle (Ubuntu)
Importance: High
It is not acceptable to build linux-oracle in bionic, copy it up into
all releases, when it cannot be rebuilt in any later series, for 3
cycles now.
is linux-oracle be indefinately be built on bionic?
** Changed in: linux-oracle (Ubuntu Disco)
Importance: Undecided => High
** Changed in: linu
Currently blocking 3 SRUs requiring manual analysis and intervention
from uploaders and the SRU team.
Also, it is a questionable quality kernel if it cannot be compiled on
any later series.
** Tags removed: rls-ee-incoming
--
You received this bug notification because you are a member of Kernel
It's up to the kernel team to manage kernel bugs.
Are you linux-oracle maintainer?
On Tue, 4 Jun 2019, 21:35 Dan Streetman,
wrote:
> This is difficult because security/selinux/ doesn't use the *actual*
> kernel headers for the kernel being built to get the AF_MAX/PF_MAX defines;
> those are not
** Tags added: block-proposed rls-ee-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1823429
Title:
linux-oracle ftbfs in disco
Status in linux-oracle package in Ubuntu:
Well, it's "better" but still failing.
http://autopkgtest.ubuntu.com/packages/systemd/eoan/ppc64el
** Changed in: systemd (Ubuntu Eoan)
Status: Fix Released => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubu
Public bug reported:
Use `lz4 -9 -l` compression for initramfs by default as discussed on
ubuntu-devel.
This would also pull the lz4 package into main
https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
St
** Changed in: lz4 (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Committed
** Changed in: live-build (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which
** Changed in: livecd-rootfs (Ubuntu)
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/1831736
Title:
[MIR] lz4 by default
Status in initramfs-tools pa
Can you boot with old initrd from the boot menu options?
Can you unlock things by-hand from the initramfs shell, and continue the
boot by exiting the shell?
What is the expected layout of things that should be done? And what are
the contents of /etc/crypttab /etc/fstab ?
** Changed in: lvm2 (Ub
** Summary changed:
- linux-oracle ftbfs in disco
+ linux v4.15 ftbfs on a newer host kernel (e.g. hwe)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ [Impact]
+
+ * linux v4.15.x fails to build on newer host machine kernels (i.e. hwe /
** Description changed:
[Impact]
* linux v4.15.x fails to build on newer host machine kernels (i.e. hwe /
v4.18+ )
[Fix]
* Instead of relying on a potentially incompatible host system/kernel
definitions of PF_MAX, use the one from the source tree.
* Upstream commit
** Changed in: lz4 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/183
** Description changed:
Use `lz4 -9 -l` compression for initramfs by default as discussed on
ubuntu-devel.
This would also pull the lz4 package into main
https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html
+
+ [Regression Potential]
+
+ We are trying to optimize fo
** Description changed:
Use `lz4 -9 -l` compression for initramfs by default as discussed on
ubuntu-devel.
This would also pull the lz4 package into main
https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html
[Regression Potential]
We are trying to optimize fo
I.e. instead of the current
$ cat debian/linux-firmware.postinst
#!/bin/sh
set -e
if [ -x /usr/sbin/update-initramfs ]; then
/usr/sbin/update-initramfs -u -k all
fi
#DEBHELPER#
It should do instead
$ cat cat debian/linux-firmware.triggers
activate-noawait update-initramfs
** Chan
** Changed in: linux-raspi2 (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1783961
Title:
CONFIG_KVM
tested s390-tools packages on dogfood which look correct.
** 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-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
** Changed in: s390-tools (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
Title:
Please add support for zipl signing
S
s390-tools in UNAPPROVED
https://launchpad.net/ubuntu/eoan/+queue?queue_state=1&queue_text=s390-tools
s390-tools-signed in source NEW
https://launchpad.net/ubuntu/eoan/+queue?queue_state=0&queue_text=s390-tools-signed
** Summary changed:
- Please add support for zipl signing
+ Please add support
** Summary changed:
- Please add support for SIPL
+ [MIR] Please add support for SIPL
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1829749
Title:
[MIR] Please add support for S
** Changed in: subiquity
Status: Incomplete => Fix Released
** Changed in: ubuntu-z-systems
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
** Changed in: subiquity
Status: Fix Released => Invalid
--
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/1776631
Title:
[19.04 FEAT] I/O device pre-configuration
Status in subiqui
** Description changed:
+ [Impact]
+
+ * Too small dmsg kernel buf ring size leads to loosing/missing early
+ boot kernel messages which happen before journald starts slurping them
+ up and storing them on disc. This results in messages similar to this
+ one on boot "missed NN kernel messages on
Requesting to rerun linux test cases, as triggered by gcc-8 to confirm the fix.
As currently they pass rebuild test, but end up as an overall FAIL due to
regression suite.
they should turn green under:
http://people.canonical.com/~ubuntu-archive/proposed-migration/cosmic/update_excuses.html#gcc-8
https://people.canonical.com/~ubuntu-archive/proposed-
migration/cosmic/update_excuses.html#gcc-8 all is now green, and
checking the results one can see that rebuild test passed, and the
regression test suite was skipped, correctly.
Great stuff.
** Tags removed: verification-needed-cosmic
** Tags
Triggering for example linux adt test in bionic, as triggered by openssl
to verify the fix.
--
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/1823056
Title:
autopkgtests run too often, too
http://autopkgtest.ubuntu.com/packages/l/linux/bionic/amd64 and it
passed. Works as expected.
** 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 Ubu
What's the output of: $ ip a ?
Also matching dmesg / syslog / journal?
--
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/1838258
Title:
Unable to configure VLAN on an additional OSA interf
Public bug reported:
s390x support secureboot via secure IPL mechanism.
When booted with Secure IPL, lock-down should be enabled.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1839622
Title:
enable lockdown on s390x
In eoan we shipped:
57d53162face UBUNTU: SAUCE: Revert "s390/dasd: Add discard support for
ESE volumes"
And as it is a SAUCE patch, we continue to ship it, as we don't implicitely
drop them:
964ce509e2de Revert "s390/dasd: Add discard support for ESE volumes"
Currently if you grep for DASD_FE
Ok, I see that either https://lists.ubuntu.com/archives/kernel-
team/2020-January/107107.html needs to land in unstable & focal kernel
trees, or better thing-provisioning support.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ub
Can I have it as a snap please?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1862255
Title:
focal/linux-5.4: 5.4.0-14.17 -proposed tracker
Status in Kernel SRU Workflow:
Fix Rel
We currently believe that the decoding error reported in dmesg is
actually harmless and has no impact on usability on the system.
Switching from lz4 to gzip compression, simply papers over the warning,
without any benefits, and slows down boot.
Kernel should be fixed to correctly parse lz4 compre
Public bug reported:
multipath nvme, failed to install with multipath disabled install failed
crashed with CalledProcessError
so trying to install with nvme_core.multipath=0 set on the cmdline, and that
fails.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: subiquity (1641)
ProcVersionSi
/dev/nvme0* is now gone, yet still mounted as /target. Yeap this is
borken.
--
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/1871611
Title:
multipath nvme, failed to install with multipath
Looks like with nvme_core.multipath=0 nvme install still fails.
** Also affects: curtin
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/1871611
i wonder if usb-hub can reproduce it.
--
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/1866852
Title:
System Display black screen on reboot or after a clean shutdown with
USB-C Dock Moni
Due to a bug in gcc-9 (default version) packaging, it has been
configured in focal with both march & mtune set to z13.
And gcc-9 will remain configured this way in focal (20.04). At this
point we don't have enough time for a full archive rebuild with mtune
set to z15, and majority of distribution
The URL is changed intentionally, to notify all users that these images
are deprecated and will not be updated after 20.04.0 GA, and will no
longer be published in the future.
You should not be using virt-install, and simply boot the s390x cloud-
image in-place, with suitable cloud-config drive at
** Also affects: ubuntu-cdimage
Importance: Undecided
Status: New
** Changed in: ubuntu-cdimage
Status: New => Opinion
** Changed in: virt-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is
Renaming the artefacts was a compromise. the other option was to not
publish them at all.
d-i artefacts will not exist for 20.10 release, nor for 20.04.1 release,
on any architecture. Thus renamed d-i artefacts is a transitional period
of ~3 months until 20.04.1 is released.
cloud-images for s390
never midn i had extras & headers left over
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
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/1873838
Title:
Purging Kernels lea
Public bug reported:
I've purged kernels
Some directories were not removed because they were non-empty
$ du -a ls 5.4.0-1*
du: cannot access 'ls': No such file or directory
216 5.4.0-1002-oem/usr/lib/modules/5.4.0-1002-oem/modules.order
8 5.4.0-1002-oem/usr/lib/modules/5.4.0-1002-oem/m
Public bug reported:
$ dpkg-query -W linux-image-*
linux-image-5.4.0-25-generic5.4.0-25.29
linux-image-generic-hwe-20.04 5.4.0.25.31
$ ubuntu-drivers list
nvidia-driver-390
nvidia-driver-435
nvidia-driver-440
$ sudo ubuntu-drivers install
Reading package lists... Done
Building dependency
** Patch added:
"0001-UBUNTU-download-signed-improve-to-support-grub2-down.patch"
https://bugs.launchpad.net/ubuntu/+source/s390-tools-signed/+bug/1876875/+attachment/5366680/+files/0001-UBUNTU-download-signed-improve-to-support-grub2-down.patch
--
You received this bug notification because
Public bug reported:
[Impact]
* Improve and generalise download-signed script to allow using it with any
signed binaries we care about
* Add support to download simply the most current version
* Add support to download /uefi/ signed binaries
* Clean up arg parsing, add help, drop unused stat
https://lists.ubuntu.com/archives/kernel-team/2020-May/109572.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1876875
Title:
Improve download-signed script to support current
We can either revert the path change in s390-tools or rebuild the
zfcpdump kernel flavour with the new name.
** Also affects: zfcpdump-kernel (Ubuntu)
Importance: Undecided
Status: New
** Also affects: s390-tools (Ubuntu)
Importance: Undecided
Status: New
** No longer affects
** Package changed: linux (Ubuntu) => linux-base (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-base in Ubuntu.
https://bugs.launchpad.net/bugs/1877088
Title:
[UBUNTU 20.04] installkernel script does not symlink /boot/in
what's in the dvd rom? is it empty or does it have some CD that has a
package pool which apt-cdrom tries to mount (and has mounted)?
--
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/1877388
Public bug reported:
To support older userspace running on newer kernels please backport
syscall table updates in linux-libc-dev.
Alternatively make linux-libc-dev be shipped by a standalone source
package (linux "flavour") to easily update it.
Currently snapd wants to apply seccomp filters on a
Earlier
## Warning: Input data exceeds 1048576 bytes - truncated
sounds already scary.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1878432
Title:
rpi3a+ does not boot with cor
@ plars
How come you manage to use Bionic classic, Focal classic, UC18 on that
Pi 3A+ without adjusting config.txt and believe that this is a UC20
regression?
Given that my understanding is that 3A+ needs that manual adjustment on
all our other targets.
** Changed in: linux-raspi (Ubuntu)
Public bug reported:
Rebuild linux-raspi kernel snaps against new initrd and gate it with QA
[Next Tasks]
1) Please change
https://launchpad.net/~canonical-kernel-snaps/+snap/pi-kernel--uc20 publication
channels:
from
20/beta 20/edge
to
20/edge
I.e. remove the beta risk level via the API !!!
** 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/1879290
Title:
pc: no message on the screen for ~30s on fast HW
Hi,
Each signed object is published on in the repository under
/$suite/main/signed/$src-$arch. I.e. the linux in focal proposed signed
artefacts can be found at:
http://ports.ubuntu.com/dists/focal-proposed/main/signed/linux-ppc64el/
I.e. http://ports.ubuntu.com/dists/focal-proposed/main/signed/
What is gmain in the above log?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4 in Ubuntu.
https://bugs.launchpad.net/bugs/1310717
Title:
process segfaults, hung task timeouts
Status in linux-ti-omap4 package in Ubuntu:
@ddstreet
Indeed, https://www.freedesktop.org/software/systemd/man/systemd.net-
naming-scheme.html b1 seems to stand for "Broadcom bus (BCMA) core
number"
So it seems to me that our stock vanilla kernel has gained support for
this broadcom wifi chip with proper Broadcom bus support.
Yet we also
@MarkF (az2008)
What you have experienced is abnormal. Normally there is only one driver
for device, we offer the best driver we have, and once connected to the
internet, the connection persists without any disconnects. And copies
wifi config into the target installed system. Such that one never h
@Alberto Milone
Something odd is happening for the user of BCM4313 wifi chip.
The devices appears to jump from bus1 to bus0, and thus getting a new
name.
Or as if, there are two different drivers offered to the user and/or
operational via different buses. Such that udev identifies the same card
@fheimes
No, in comment #2 I did not agree to bump the parameter.
@heinz-werner_seeck
My previous comment was not responded to. LUKS2 and Argon2i have no
effect on steady state RAM usage, and thus should not affect crashkernel
memory requirements significantly. Normally, Argon2i decryption has hi
UC20 only uses predictable names. It is intentional to use stable names.
There is nothing in the gadget about it. But rather kernel drivers, dtb,
udev.
eth0 name is a bug. And it means udev failed to establish a predictable
name for it.
I think we either need to add an additional policy file for
encrypted volume of the system being dump, or the encrypted volume which
is the target where to store the dump? (and thus more memory is needed
to unlock the drive?)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
h
Eoan and later d-i, new installer, curtin do not install /etc/kernel-img.conf.
Upgraded systems keep having it (ie. installed with bionic or xenial, and
upgraded).
Can you please let me know if _removing_ /etc/kernel-img.conf breaks $
sudo make install, and if adding /etc/kernel-img.conf back fix
On Fri, 26 Jun 2020 at 15:01, bugproxy <1877...@bugs.launchpad.net> wrote:
>
> --- Comment From niklas.schne...@ibm.com 2020-06-26 09:45 EDT---
> (In reply to comment #17)
> > Eoan and later d-i, new installer, curtin do not install
> > /etc/kernel-img.conf.
> > Upgraded systems keep having
1 - 100 of 1815 matches
Mail list logo
