** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu Focal)
Status: Triaged => New
** Changed in: linux (Ubuntu Groovy)
Status: Incomplete => New
--
You received this bug notification because you are
Public bug reported:
posix_spawn usage in gnu make causes failures on s390x
Recently in gnu-make v4.3 https://paste.ubuntu.com/p/tYhbJFKN76/ it
started to use posix_spawn, instead of fork()/exec().
This has caused failure of an unrelated package flatpak-builder
autopkgtests on s390x only, like s
> Is this a native s390x build, or something qemu-user? Thanks.
That's a very good question.
The failing autopkgtest, was run on an LPAR, which is running OpenStack
Nova, which launched qemu-system kvm, v5.4 Ubuntu kernel, and then run
make inside that.
I will double check if those old builds of
Ubuntu no longer uses vt.handover and it should not be specified at all
anymore.
We boot directly to tty1, always and everywhere, and we should not be
setting that at all.
Thus a patch changing that from 7 to 1 is not a good idea for focal+.
And I can't quite remember which releases we have chan
For us to develop this feature we need hardware access to such system,
which we do not have.
Can you please provide us with such hardware? either remote access, or
ship it to us?
Need to be able to remotely power it up and down, and be able to control
bootloader to boot new installers.
** Change
Public bug reported:
To allow prebuilding apparmor profiles during cloud-images build, the
chroot where cloud-image is created need access to the
/sys/kernel/security/apparmor/features of the target kernel.
It would be nice, if kernels were booted, that file stored, and
installed in the linux-ima
Ideally the .features file as seen in the
/var/cache/apparmor/*/.features
--
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/1888023
Title:
Please ship apparmor features files
Status in lin
Ideally this wouldn't need to be fetched from live / boot system, and
instead kernel's apparmor subsystem can just build that during source
build of the kernel.
Afterall, the source code knows what that features will be supported,
right?
--
You received this bug notification because you are a me
Thank you for gcc-9 and gcc-10 patch.
We are about to switch default compiler to gcc-10 in 20.10, so not sure
if we will need gcc-9 patch in groovy or not.
** Package changed: linux (Ubuntu) => gcc-10 (Ubuntu)
** Also affects: gcc-9 (Ubuntu)
Importance: Undecided
Status: New
--
You
Related gcc patches are at
https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1888653
** Package changed: linux (Ubuntu) => binutils (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/bu
@frank @ibm
this ticket is not helpful, and there is no need for any s390-tools
maintainers to comment on.
this ticket has been resolved and new name is in use and has been
uploaded 3 weeks ago.
However, it is not available as it is blocked on manual kernel team
review to allow signing of the zf
@colin-king @juliank
It feels to me that the oem flavour should default to
(powersave/ondemand), as it is more-or-less laptop kernel flavour.
I feel like generic kernel flavour should remain on performance.
I feel like we should have a unit, that for chassis=laptop turns on
(powersave/ondemand).
Only "linux-5.4" task was changed to invalid before it was removed.
The "linux" task was and still is confirmed.
Launchpad bug tracker supports tracking multiple states across multiple
packages simultaniously. You can always see the correct status of the
bug, for each task, at the top of the page.
** Changed in: linux-raspi (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1881159
Title:
BUG: soft lockup on return from recover to run
Public bug reported:
qemu-system-arm -M virt -m 4096 -smp 2,sockets=2,cores=1,threads=1
-drive file=./groovy-server-cloudimg-armhf.img,if=virtio -kernel
./vmlinuz-5.8.0-21-generic-lpae -initrd ./initrd.img-5.8.0-21-generic-
lpae -append 'root=LABEL=cloudimg-rootfs break=bottom' -nographic
[
I wonder if this is because -M virt defaults to highmem=on, I will try
again with highmem=off
--
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/1899519
Title:
booting armhf kernel under qem
-M virt,highmem=off still shows relocation 28 out of range upon trying
to load any kernel modules.
--
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/1899519
Title:
booting armhf kernel unde
20, 21 kernels were both bad. Testing 22 kernel now.
--
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/1899519
Title:
booting armhf kernel under qemu results in relocations out of range,
@ubuntu-kernel-bot given i can't boot past initrd, what do you expect
from me?
** Tags added: bot-stop-nagging
** Summary changed:
- booting armhf kernel under qemu results in relocations out of range, and thus
no modules are loaded
+ booting linux-generic-lpae armhf kernel under qemu results i
** Package changed: ceph (Ubuntu) => linux (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/1899582
Title:
ceph: fix inode number handling on arches with 32-bit ino_t
Status in U
Has this been forwarded to the stable trees?
I do not see it applied on 5.8.x-stable or lower trees.
Currently only available in linux-5.9 which we are not shipping yet.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a membe
and same with 22 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/1899519
Title:
booting linux-generic-lpae armhf kernel under qemu results in
relocation out of range, and thus n
[0.110128] /cpus/cpu@0 missing clock-frequency property
[0.110426] /cpus/cpu@1 missing clock-frequency property
[0.190376] CPU1: Spectre v2: firmware did not set auxiliary control
register IBE bit, system vulnerable
[ 11.068045] cryptd: section 4 reloc 15 sym '__stack_chk_fail': relo
So
>> 1/ inode numbers will be seen to have changed between kernel versions.
>>32-bit arches will see large inode numbers now instead of the hashed
>>ones they saw before.
>>
That seems fine to me. This is all during runtime only, and doesn't
change ondisk format at all right?
>> 2/ any
CONFIG_ARM64_MODULE_PLTS is enabled; because CONFIG_ARM64_ERRATUM_843419
is enabled in zesty+ (backported to yakkety too) see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647793
groovy/master:debian.master/config/annotations:CONFIG_ARM64_ERRATUM_843419
policy<{'arm64'
I ponder if raspi kernel also needs this on armhf
debian.raspi/config/config.common.ubuntu:# CONFIG_ARM_MODULE_PLTS is not
set
--
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/1899519
Title
@paulo awesome; will there be a kernel respin? if yes, can we also take
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899582 ?
--
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/1899519
The plan was to move kernel to v5.4 kernel in bionic. and the firmware
was already matching that.
You could enable focal repository and install linux-raspi kernel v5.4
from there?
** Also affects: linux-raspi2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notific
Public bug reported:
UC20 kernel missing /firmware/regulatory.db and
/firmware/regulatory.db.p7s
Whilst present in the UC18 kernel snap.
At runtime, this causes failure to load regulatory database, and perform
wifi scan.
[ 27.510199] platform regulatory.0: Direct firmware load for
regulatory.
wait, raspi images must already be using v5.4 kernel on bionic
See https://launchpad.net/ubuntu/+source/linux-raspi-5.4
Why are you upgrading firmware, without upgrading the kernel to v5.4?
Why are you using obsolete images, from the archived location, instead
of the most recent ones?
v4.15 ke
https://lists.ubuntu.com/archives/kernel-team/2020-October/114068.html
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: bot-stop-nagging
** Tags added: patch
--
You received this bug notification
** Changed in: linux-meta (Ubuntu)
Status: Confirmed => Fix Released
--
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 lin
** Changed in: linux (Ubuntu Groovy)
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/1899519
Title:
booting linux-generic-lpae armhf kernel under
Can you open bug report against ubiquity with like $ ubuntu-bug ubiquity
?
that would collect all the installer logs, which will help to
investigate this.
Or can you please attach /var/log/installer as a tarball? do check for
any sensitive info there, or feel free to mark this bug report private.
btw, what is the state of MOK? i.e.
$ sudo mokutil --list-enrolled
$ ls /var/lib/shim-signed
$ ls /var/lib/shim-signed/mok/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1899678
Title:
Oct 20 17:23:15 ubuntu-budgie ubiquity: /sbin/update-secureboot-policy: 44: 3:
Bad file descriptor#015
Oct 20 17:23:15 ubuntu-budgie ubiquity: Done.#015
looks like when 3rd party drivers box is not ticked (and mok enrolment
pin not configured), and broadcom driver is attempted to be installed,
an
Two things:
1) Old iso used, which had dkms bit fixed in the 21 iso.
2) nvidia-graphics-drivers-455 got built and migrated with a matching
lrm.
nvidia-graphics-drivers-455 must have never migrated to groovy-release
without lrm
** Also affects: linux-restricted-modules (Ubuntu)
Import
** Tags added: block-proposed-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1900865
Title:
NVIDIA drivers aren't running after fresh groovy install with Secure
Related ubuntu-drivers bug for better UX
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-
common/+bug/1900870
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-restricted-modules in Ubuntu.
https://bugs.launchpad.net/bugs/1900
It is unclear how to reproduce the issue.
So far, I always have multiple VLANs configured and accessible. The only
time I see errors similar to the ones from the reporter, is when the
same vlan with the same name is configured multiple times in a row
(which is an input/configuration error)
This b
However dropping vt.handoff is not regression free it may impact
flavours that use lightdm.
--
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/1845801
Title:
[nvidia] A
We could use gfxpalyload blacklist, to mark certain nvidia cards there.
And then gfxpayload will not be set to keep, and then vt.handoff will
not be appended.
See grub-gfxpayload-lists package, and files in /usr/share/grub-
gfxpayload-lists/blacklist/
My current preference would be the gdm3 fix.
We do not provide subiquity images for arm64 in bionic.
** Changed in: subiquity
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
** Summary changed:
- Bring back ondemand.service or switch kernel default governor for pstate -
pstate now defaults to performance governor
+ Please switch default kernel governor to ondemand, such that advanced
userspace utilities such as game-mode can be later used to rev-up to to
performanc
** Description changed:
- In a recent merge from Debian we lost ondemand.service, meaning all CPUs
- now run in Turbo all the time when idle, which is clearly suboptimal.
+ [Impact]
- The discussion in bug 1806012 seems misleading, focusing on p-state vs
- other drivers, when in fact, the scrip
** Description changed:
[Impact]
* Kernel should have sensible default governor set to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y for the generic, hwe, raspi,
- riscv64, oem kernel flavours in Focal and Groovy+.
+ riscv, oem kernel flavours in Focal and Groovy+.
* ondemand.service must
Proof that we must not use performance governor attached, from one of my
team mates.
** No longer affects: systemd (Ubuntu)
** Attachment added: "performance-governor.jpg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885730/+attachment/5403156/+files/performance-governor.jpg
--
You
*** This bug is a duplicate of bug 1885730 ***
https://bugs.launchpad.net/bugs/1885730
We are finally fixing this.
** This bug has been marked a duplicate of bug 1885730
Please switch default, hwe, oem kernel flavours governor to
CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y , such that advanced
Public bug reported:
ubuntu-seed / ubuntu-boot partition detection could be improved
Currently in the initrd, snapd-bootstrap searches for ubuntu-boot /
ubuntu-seed partition by label or by UEFI variable that was set by sd-
boot.
sdboot uses devicepath UEFI protocol to establish MEDIA_DEVICE_PAT
yes kernel config changes will be needed for this.
** Changed in: ubuntu-power-systems
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/1903288
Title:
** Changed in: s390-tools (Ubuntu Focal)
Importance: Undecided => Wishlist
--
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
Are these installs with zkey/paes or without?
Because, in Ubuntu, when zkey was introduced I have reverted the
s390-tools upstream change to lower the argon2i settings. Due to my lack
of understanding of the security features there. And later, we have made
similar choices for TPM backed encryption
https://github.com/snapcore/secboot/pull/127
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1877533
Title:
[20.10 FEAT] Increase the crashkernel setting if the root volume is
lu
Also i guess we (i) need to retest if
https://github.com/lz4/lz4/releases/tag/v1.9.3 fixes all the things =/
--
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 unpac
@Siarhei
That looks very valid. And we were close to getting to that, when apw &
I timed out looking at this.
lz4 -l Use Legacy format (typically for Linux Kernel compression)
Note : -l is not compatible with -m (--multiple) nor -r
Which must always be used when creating initrd
linux-meta-aws patch is submitted at https://lists.ubuntu.com/archives
/kernel-team/2020-November/114920.html
** Also affects: linux-meta-aws (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
+ Now that micorocode-initrd is in focal, linux-meta-aws should start
+ depen
Public bug reported:
5.8.0-9.11 and other v5.8 kernels all fail to boot in qemu with opensbi
and qemu.
I'm booting a cloud-image with kenrel install like this:
qemu-system-riscv64 -machine virt -m 2048 -smp 4 -kernel
/usr/lib/riscv64-linux-gnu/opensbi/generic/fw_jump.elf -device
loader,file=/usr
So lz4 compressed initrd looks like this with hexdump
568f580 0523 00ac 54bf 4152 4c49 5245 2121 0021
568f590 0001 1cff 0050
568f59a
I do wonder what ram is initialized too, and how those things look when
kernel reads initrd from memory as loaded by the bootloader / qemu.
Public bug reported:
please promote modules from extra to modules for HiFive Unleashed
The following modules are used by the HiFive Unleashed board from extra
Please install them in modules.
linux-modules-extra-5.4.0-24-generic:
/lib/modules/5.4.0-24-generic/kernel/drivers/net/phy/mscc.ko
lin
** Also affects: grub2 (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/1835660
Title:
initramfs unpacking failed
Status in OEM Priori
(Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
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
NAK on the linux patch.
I think this is a grub bug.
When loading multiple initrds, grub aligns_up each one of them at 4bytes
boundary, and allocates pages for that. And it declares and passes
ramdisk_image as the total allocated memory. Rather than the true size
of the initrds.
** Changed in: gr
Public bug reported:
[ 19.051518] Freeing unused kernel memory: 308K
[ 19.062326] [ cut here ]
[ 19.066219] riscv/mm: Found insecure W+X mapping at address
(ptrval)/0xffdff800
[ 19.074930] WARNING: CPU: 0 PID: 1 at arch/riscv/mm/ptdump.c:200
note_p
Public bug reported:
Sep 25 12:06:39 s390-dasd[4637]: ECKD DASD 0.0.0200 configure failed
Sep 25 12:06:39 s390-dasd[4637]: Error: Could not write file
/sys/bus/ccw/drivers/dasd-eckd/0.0.0200/online: Input/output error
Sep 25 12:06:39 s390-dasd[4637]: Configuring devices in the active
configu
** Attachment added: "dasd-log.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845323/+attachment/5291135/+files/dasd-log.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/1
** Summary changed:
- Trying to online dasd drive results in invalid input/output from the kernel
+ Trying to online dasd drive results in invalid input/output from the kernel
on z/VM
** Tags added: bot-stop-nagging
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Canonical Kernel (
** Description changed:
SRU Justification:
==
[Impact]
* Trying to online dasd drive results in invalid input/output from the
kernel on z/VM
[Fix]
- * ? TODO - hopefully patch attached ?
+ * Ignore errors from non-essential metadata reads, which may or may n
https://lists.ubuntu.com/archives/kernel-team/2019-September/104072.html
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
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/18453
** Attachment added: "subiquity-1.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1840122/+attachment/5291857/+files/subiquity-1.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
** Attachment added: "subiquity-2.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1840122/+attachment/5291858/+files/subiquity-2.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
subiquity image has similar, but it manages to reboot fine (attaching
subiquity screenshots)
squashfs errors are still bad though.
--
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/1840122
T
** Changed in: casper (Ubuntu Eoan)
Importance: High => Critical
** Changed in: casper (Ubuntu Eoan)
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.
Public bug reported:
[Impact]
* Under certain conditions, the discard operation on the new ESE DASD
may lead to data corruption.
[Test Case]
* Internal IBM testing
[Regression Potential]
* ESE DASD / thin provisioning, is the a new subtype of DASD drives
specific to s390 architecture. The
Ubuntu enables discard by default in all the installers, all
filesystems, and all layers (e.g. mdadm/lvm/luks discard).
Assumption until now, has been that it is harmless, when underlying
storage doesn't support discard and always non-harmful when it is
supported.
I agree, we should revert discar
Revert of discard is to be tracked in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846219
--
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/1830731
Title:
[19.10 FEAT] Thin provisi
https://lists.ubuntu.com/archives/kernel-team/2019-October/104176.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/1846219
Title:
Revert ESE DASD discard support
Status in linux pack
akkety)
Importance: Undecided => Medium
** Changed in: s390-tools (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: s390-tools (Ubuntu Aa-series)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
** Changed in: s390-tools (Ubuntu Aa-series)
Milestone: None
I wonder if this really should go to linux-stable too.
--
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/1682871
Title:
attempts to rename vlans / vlans have addr_assign_type of 0 on kernel
** Description changed:
+ [Impact]
+
+ * When vlan interfaces are created, their mac address is copied from
+ the underlying interface, but it is not marked by kernel as stolen.
+
+ * When underlying interface MAC address is changed, it does not
+ propagate to the vlan interfaces.
+
+ [Test C
Adding a cloud-init workaround patch for kernels before 4.7 too.
** Description changed:
[Impact]
- * When vlan interfaces are created, their mac address is copied from
+ * When vlan interfaces are created, their mac address is copied from
the underlying interface, but it is not marked b
** Patch added: "vlans-steal-mac-addresses.patch"
https://bugs.launchpad.net/cloud-init/+bug/1682871/+attachment/4864966/+files/vlans-steal-mac-addresses.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
The cloud init patch needs work...
>>> interface_has_own_mac('bonding_masters')
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/cloudinit/net/__init__.py", line 226, in
interface_has_own_mac
uevent = read_sys_net_safe(ifname, 'uevent').splitlin
Hm, I don't think you will win much here. vlans made from a bond have
addr_assign_type 3.
root@xnox-iad-16:/sys/class/net# uname -r
4.8.0-46-generic
root@xnox-iad-16:/sys/class/net# grep -e 0 -e 1 -e 2 -e 3 */addr_assign_type
bond0.101/addr_assign_type:3
bond0.401/addr_assign_type:3
bond0/addr_as
Hello, I will retest this with the sru kernel.
The udevadm monitor appears to monitor things that it knows about
thus first one needs to load nbd module, start monitor, unload nbd
module, then proceed with the test case.
I've started validating this on wednesday, but had to travel away from a
With uname -a listing 4.4.0-100-generic #123-Ubuntu I get two change
events, on the parent nbd3 device when connecting nbd export to
/dev/nbd3 with two partitions (nbd3p1 and nbd3p2).
With uname -a listing 4.4.0-98 I do not get such events.
This bug is verified on xenial, will prepate matching sy
** Also affects: makedumpfile (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Bionic)
Importance: Undecided
Assignee: Canonical Foundations Team (canonica
Systemd regression introduced in:
$ git describe 2d058a87ffb2d31a50422a8aebd119bbb4427244
v232-626-g2d058a8
Reverted in:
$ git describe 9e4ea9cc34fa032a47c253ddd94ac6c7afda663e
v234-72-g9e4ea9c
Thus affected releases were artful and bionic.
Bionic is now on v235 and thus is fixed-release for the
** Changed in: systemd (Ubuntu Artful)
Importance: Undecided => High
** Changed in: systemd (Ubuntu Artful)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu Bionic)
Importance: Undecided => Wishlist
** Changed in: makedumpfile (Ubuntu Artful)
Importance: Undecided =>
Let's assume there is a systemd fault here too, thus marking systemd as
affected. I will try to play around with this, but may get to this by
December 14th the earliest.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because yo
** 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/1754059
Title:
linux: 4.15.0-12.13 -proposed tracker
** Branch linked: lp:~xnox/britney/custom-kernels-cannot-pass
--
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/696435
Title:
wait-for-root fails to detect nbd root
Status in linux package
** Branch unlinked: lp:~xnox/britney/custom-kernels-cannot-pass
--
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/696435
Title:
wait-for-root fails to detect nbd root
Status in linux packa
Confirmed with systemd 229-4ubuntu21.2 that dev-nbd4p1.device is only
"plugged", after client is running, and all symlinks and partitions
exist.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug noti
I believe the best way forward is to postpone this request to 18.10, which will
be based on the 4.16 (or later) kernel.
Then it will be included in the tools packages, and arrive in 18.04 via -hwe
kernel, verbantim.
In the meantime, it is quite trivial to get that single script onto systems, by
** 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/1757164
Title:
linux: 4.15.0-13.14 -proposed tracker
** Changed in: debian-installer (Ubuntu Bionic)
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/1757164
Title:
linux: 4.15.0-13.14 -proposed tracker
S
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => 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/1757164
Title:
linux: 4.15.0-13.14 -proposed tracker
Status
Moving to ibm-java71 package, please ignore the 71 suffix, used for
internal tracking only.
** Package changed: linux (Ubuntu) => ibm-java71 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
There are a few steps that need to happen:
1) determine which kernel modules are required for that hardware
2) check if those kernel modules are build and available from the regular
userspace package
3) check if those kernel modules are included in the udeb kernel package for
the installer
4) che
zesty is End Of Life
** Changed in: linux (Ubuntu Zesty)
Status: In Progress => Won't 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/1717224
Title:
virsh start of virtual gue
401 - 500 of 1816 matches
Mail list logo
