We should drop it from the seed since we're not building ARM ISOs
anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2062667
Title:
Fails on (and should be
Why is Mantic won't fix? This could potentially break a lot of kernel
ADT testing for Mantic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2055200
Title:
tests-in-lxd
A couple of retries and the test finally passes. There's some flakiness.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2038433
Title:
systemd autopkgtest regression on
The first container reboot fails because seeding takes too long (which
is bug 1878225). Then the hack kicks in and a second image build is
attempted with also fails. The hack masks the problematic services
9811s Created symlink /etc/systemd/system/snapd.service → /dev/null.
9817s Created symlink
2023-11-29T11:00:34.713689+00:00 mantic-test systemd[1]: Reached target
cloud-init.target - Cloud-init target.
2023-11-29T11:00:34.713731+00:00 mantic-test systemd[1]: Startup finished in
5.934s.
2023-11-29T11:00:34.766612+00:00 mantic-test systemd[1]: dmesg.service:
Deactivated successfully.
Ok that's not it. It looks like a container reboot takes longer than 1
min with newer kernels resulting in a timeout error and subsequent
failure.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
>From my limited testing, it looks like it was introduced in 6.5.0-10.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2038433
Title:
systemd autopkgtest regression on
So the workaround for the above in systemd/debian/tests/tests-in-lxd is
problematic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2038433
Title:
systemd autopkgtest
Oh -> bug 1878225
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2038433
Title:
systemd autopkgtest regression on arm64 and s390x on mantic
Status in linux package in
Is seems the container fails to boot. From a bad run:
9109s autopkgtest [10:39:17]: test tests-in-lxd: [---
9145s 2023-11-28T10:39:50Z INFO Waiting for automatic snapd restart...
9259s lxd 5.19-8635f82 from Canonical** installed
9288s Creating autopkgtest-prepare-jhI
9475s
This has landed in upstream bluez now:
https://github.com/bluez/bluez/commit/303925b28110469ad002ac19ce0eb9c84d6aceb2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2041496
I don't think that is sufficient for all possible source, meta and
binary kernel package incarnations. I need to do some testing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
** No longer affects: libcamera (Ubuntu Noble)
** No longer affects: linux-meta-raspi (Ubuntu Noble)
** No longer affects: linux-raspi (Ubuntu Noble)
** No longer affects: mesa (Ubuntu Noble)
** No longer affects: pipewire (Ubuntu Noble)
** No longer affects: rpi-eeprom (Ubuntu Noble)
** No
https://lore.kernel.org/linux-
bluetooth/20231026182426.032a776d@gollum/#t
Proposed patch:
https://lore.kernel.org/linux-bluetooth/20231027055423.13617-1-juerg.haefli...@canonical.com/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
On Mantic:
$ btmgmt --index 1 info
Unable to open 1: No such file or directory (2)
Index list with 1 item
hci0: Primary controller
addr B8:27:EB:CB:F8:8D version 9 manufacturer 305 class 0x6c
supported settings: powered connectable fast-connectable discoverable
Maybe something like this?
https://git.launchpad.net/~juergh/+git/apport/log/?h=juergh/ubuntu/devel
Move and rename source_linux.py to general-hooks/zz-kernel.pi, ensure it
runs last (because it wants properties that are set by other general
hooks) and only for kernel and related (firmware and
Maybe it doesn't matter if the kernel hook is triggered for those since
they never get bug reports anyways :-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2018128
Title:
List of kernel source packages as of 2023/10/23.
** Attachment added: "ubuntu-kernels.list"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2018128/+attachment/5712664/+files/ubuntu-kernels.list
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I don't think we can do this with a regex. There are linux- package
that are not kernels.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2018128
Title:
Apport does not
Or the kernel package itself needs to provide the symlink.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2018128
Title:
Apport does not collect all logs when the package
This needs some rework. Kernel source package names change a lot and
with every release so static symlinks will not work. We might have to
query LP to get up-to-date kernel source information.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2018128
Title:
Apport does not collect all logs when the
This introduces an unacceptable regression on Raspberry Pis. An
interface that is *not* listed must not cause a 2 min timeout.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
*** This bug is a duplicate of bug 2038539 ***
https://bugs.launchpad.net/bugs/2038539
** This bug has been marked a duplicate of bug 2038539
bluetooth connections are unstable with linux-image-6.5.0-7-generic (MANTIC)
--
You received this bug notification because you are a member of
** Tags added: kern-8255
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2039278
Title:
Consistent naming of onboard NIC on all Pi on all Ubuntu
Status in linux-raspi
FWIW, this works correctly with a 6.2 lunar kernel and mantic userspace.
** Attachment added: "udev-6-2-3b+.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708655/+files/udev-6-2-3b+.log
--
You received this bug notification because you are a member
udev debug log from a 3B
** Attachment added: "udev-3b.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708641/+files/udev-3b.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
udev debug log from a 3B+
** Attachment added: "udev-3b+.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708640/+files/udev-3b+.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: linux-meta-raspi (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux-raspi (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in
Debdiff with squash of
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450
Briefly tested on Pi 5, 4 and 400. Desktop comes up and glx and vulkan
are accelerated.
** Patch added: "mesa_23.2.1-1ubuntu2.debdiff"
** Changed in: libcamera (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
** Changed in: linux-meta-raspi (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
** Changed in: linux-raspi (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
*
*** This bug is a duplicate of bug 2037642 ***
https://bugs.launchpad.net/bugs/2037642
Public bug reported:
Backport support for new BCM2712 HW (used on Pi 5) to Mantic mesa.
Upstream MR:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450
** Affects: mesa (Ubuntu)
Public bug reported:
ubuntu-server in Mantic pulls in zfs userspace packages and systemd
services are automatically enabled, which means zfs kernel modules are
automatically loaded at boot, for everybody. On Raspberry Pi, this
results in +5MB of additional memory consumption which is not
** Description changed:
+ [Impact]
+
After updating to Kernel 6.2 a few days ago, I have been experiencing
issues with my system's shutdown and reboot functions. During these
processes, the system becomes unresponsive and hangs on a black screen,
which displays both the Dell and Ubuntu
Thanks for the confirmation, will send the patch to our mailing list.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2031352
Title:
Nouveau driver crash - Ubuntu 22.04.3
I've builtt a test kernel with the above patch:
https://kernel.ubuntu.com/~juergh/lp2031352/
Can someone give it a try, please? Note that the kernel is not signed so
you need to disable SecureBoot to be able to boot it. Install linux-
image-unsigned, linux-modules and maybe linux-modules-extra.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu Lunar)
Without digging too deep, maybe this:
https://lore.kernel.org/lkml/cacavsv6-aj4ehg7pnuwgsncn0cyro8gwd3nr8pu32a-wxso...@mail.gmail.com/T/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Summary changed:
- Ubuntu 22.04.3 LTS stuck on power-off/reboot screen
+ Ubuntu 22.04.3 LTS stuck on power-off/reboot screen (nouveau driver crash)
** Summary changed:
- Ubuntu 22.04.3 LTS stuck on power-off/reboot screen (nouveau driver crash)
+ Nouveau driver crash - Ubuntu 22.04.3 LTS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2031352
Title:
Nouveau driver crash - Ubuntu 22.04.3 LTS stuck on power-off/reboot
screen
Status in linux-hwe-6.2 package
@steffel et al.
I believe there are two different problems here.
1) A generic reboot/suspend/halt issue. When powering off or suspending,
the machine doesn't fully turn off. The fan is still spinning and it can
only be revived by pulling the plug. This is what this bug is about.
2) A similarly
@ianrussel your log shows:
Aug 22 09:57:02 ianrussel kernel: nouveau :01:00.0: fb: VPR locked, but no
scrubber binary!
Aug 22 09:57:02 ianrussel kernel: BUG: kernel NULL pointer dereference,
address:
Aug 22 09:57:02 ianrussel kernel: #PF: supervisor instruction fetch in
It's not trivial since it happens so infrequently. I need to think about
this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2031352
Title:
Ubuntu 22.04.3 LTS stuck on
It's not a systemd issue.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2031352
Title:
Ubuntu
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2031352
Title:
Ubuntu 22.04.3 LTS stuck on
ubuntu@rpi-4b-rev1d2-164b:~$ cat /etc/apt/preferences.d/proposed-updates
Package: *
Pin: release a=lunar-proposed
Pin-Priority: 500
ubuntu@rpi-4b-rev1d2-164b:~$ apt-cache policy linux-raspi
linux-raspi:
Installed: 6.2.0.1004.6
Candidate: 6.2.0.1005.8
Version table:
6.2.0.1005.8 500
Thanks for the verification.
> there is also a non-existent version 6.2.0.1005.8 that causes
conflict.
That's a valid meta package version and the meta packages should be
available from lunar-proposed.
http://ports.ubuntu.com/ubuntu-ports/pool/main/l/linux-meta-raspi/
--
You received this bug
** Changed in: systemd (Ubuntu)
Status: New => Invalid
** Also affects: systemd (Ubuntu Lunar)
Importance: Undecided
Status: Invalid
** Also affects: linux-raspi (Ubuntu Lunar)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu Lunar)
Status:
Sigh. I missed to forward-port the revert of that commit from kinetic to
lunar.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2017209
Title:
[Raspberry Pi/lunar]
** Tags added: kern-6572
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2017209
Title:
[Raspberry Pi/lunar] systemd-oomd fails with
Test packages: https://launchpad.net/~juergh/+archive/ubuntu/mesa
** Description changed:
- The Lenovo X13s ARM laptop contains an Ardeno a690 GPU. Please add Mesa
+ The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa
support for this GPU. This landed in upstream Mesa here:
** Attachment added: "mesa_23.0.1-1ubuntu1_23.0.1-1ubuntu2.diff.gz"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2015182/+attachment/5660728/+files/mesa_23.0.1-1ubuntu1_23.0.1-1ubuntu2.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Public bug reported:
The Lenovo X13s ARM laptop contains an Adreno a690 GPU. Please add Mesa
support for this GPU. This landed in upstream Mesa here:
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21573
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
Yes, it's horribly broken :-(
** Changed in: rsync (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2002918
Title:
ERROR: rejecting
Clarification: The raspi kernel contains a bunch of downstream HW
specific patches pulled primarily from the raspberrypi kernel. These
code modifications are never exercised in an OpenStack VM or LXD
container so it's rather pointless to do so.
--
You received this bug notification because you
Time to turn off ADT testing for raspi kernels since it adds no real
value.
** Changed in: linux-raspi (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This is a general problem when running any raspi kernel in ADT since the
raspi kernels don't support ACPI. Software configuration seems to be
different across different arm64 host HW in the ADT OpenStack cloud.
Older HW has older qemu-efi installed which presents both ACPI *and* a
DT to the guest
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1930082
Title:
systemd/247.3-3ubuntu3 ADT test failure with
** Tags added: kern-4615
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1971712
Title:
Add support for Intel DG2
Status in linux-firmware package in Ubuntu:
Fix Released
Log entries from failure:
==
FAIL: test_no_failed (__main__.ServicesTest)
No failed units
--
Traceback (most recent call last):
File
Upstream is aware since 2007 [1] :-) But apparently lacking NFSv4
support is not painful enough to get some traction. I'm currently
digging through the code.
[1] https://lists.zytor.com/archives/klibc/2007-February/002062.html
--
You received this bug notification because you are a member of
Please do test the work-around. If indeed NFSv4 solves your overlayfs
problem then that would be another reason for fixing nfsmount.
We can carry Ubuntu specific fixes if for some reason Debian doesn't
want them but the preferred way is obviously to fix it in Debian so that
it tickles down
It simply means that the ticket has been acknowledged as a bug/issue,
nothing more. As you might have noticed it's been reported in Debian in
2007, so it doesn't seem to be that important. I know that doesn't help
you but the fact that there's a work-around makes it even less
important. I'll take
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409272#14 for a
work-around which replaces nfsmount in the initrd with /sbin/mount.nfs.
But that probably pulls in dependencies and blows up the size of the
initrd.
--
You received this bug notification because you are a member of Ubuntu
Debian 11 is also broken if an intird is being used but Raspberry Pi OS
is *not* using an initrd hence not using nfsmount.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
** Changed in: linux-raspi (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-raspi (Ubuntu Kinetic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
Ah never mind I looked at the amd64 image manifest, not raspi :-(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1947311
Title:
Unexpected partition growth on first
Did you disable it in user-data?
cloud-initramfs-growroot is no longer installed per the manifest
https://cdimage.ubuntu.com/ubuntu-server/daily-
preinstalled/current/jammy-preinstalled-server-amd64.manifest
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Hirsute is EOL so closing this bug. Please open a new one if the problem
still persists with one of the supported series.
** Changed in: linux-firmware (Ubuntu Hirsute)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
If you want this fixed in Ubuntu I need to know what series are
affected. Hirsute goes EOL at the end of the month. Are Impish and/or
Jammy working or affected as well?
** Changed in: linux-firmware (Ubuntu Hirsute)
Status: Confirmed => Incomplete
--
You received this bug notification
@antonio-petricca, What series? What kernel?
I can produce a hirsute linux-firmware package with the reverted sdma
firmware but need someone to verify it on hirsute with the hirsute
kernel. Any takers? Or have you all moved on to impish?
--
You received this bug notification because you are a
lid
** Changed in: linux-firmware (Ubuntu Hirsute)
Status: New => Confirmed
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-firmware (Ubuntu Hirsute)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notifica
@antonio-petricca, sorry but 5.15.2 is not a supported Ubuntu kernel and
especially not on Bionic with (old) Bionic firmware.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu Focal)
Assignee: (unassigned) => Juerg Haefliger (juergh)
** Chan
*** This bug is a duplicate of bug 1939986 ***
https://bugs.launchpad.net/bugs/1939986
** This bug has been marked a duplicate of bug 1939986
Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads
i915
--
You received this bug notification because you are a member of
** Changed in: linux-firmware (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1939986
Ti
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1939986
Title:
Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
loads i915
Status in
Hi. I'm picking up this ticket from Seth. Reading through the history it
seems it's still an open issue? My understanding is that upstream
'fixed' this by reverting fw blobs in version 20210818. I can produce a
linux-firmware test package for hirsute 20.04 with these reverts if
necessary. Just let
** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu)
** Also affects: bluez (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: pi-bluetooth (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Groovy)
The default for both core20 and server is 'net.ifnames=0' which disables
persistent network interface names so it's expected to see eth0 and
wlan0.
cat /proc/cmdline
coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1280
bcm2708_fb.fbheight=1024 bcm2708_fb.fbswap=1
** Changed in: u-boot (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1648267
Title:
Regression with Zesty binutils building
Zesty is long gone.
** Changed in: u-boot (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1648267
Title:
Regression with Zesty
There seem to be multiple issues related to these benign errors:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949444
Just to be clear, it's not a kernel (linux) package problem.
** Bug watch added: Debian Bug tracker #948257
Public bug reported:
On Bionic with linux-raspi2-5.3 arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/arm64/l/lxd/20191219_143544_26c78@/log.gz
** Affects: lxd (Ubuntu)
Importance: Undecided
Status: New
**
Above log is from an Eoan run. Here is Bionic:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20191219_142612_71881@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-eoan/eoan/arm64/l/lxc/20191216_204800_eb922@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
Public bug reported:
On Bionic with linux-raspi2-5.3 arm64:
PASS: lxc-tests: lxc-test-api-reboot (78s)
PASS: lxc-tests: lxc-test-apparmor (1s)
PASS: lxc-tests: lxc-test-apparmor-mount (52s)
PASS: lxc-tests: lxc-test-attach (3s)
PASS: lxc-tests: lxc-test-autostart (68s)
PASS: lxc-tests:
On 32-bit sfdisk fails to parse the label-id if the MSB is set and thus
generates a new one. We happen to be unlucky with our (i386) cloud image
in that the original label-id has the MSB set. So when growpart run
(which calls sfdisk), the disk ID is regenerated and subsequent boots
fail because
https://lore.kernel.org/util-
linux/20190222160412.26652-1-jue...@canonical.com
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1817302
Title:
growpart changes diskid
Verified that the new package fixes the issue.
** Tags removed: verification-needed-trusty
** Tags added: verification-done-trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
This is looking great so far. Instance booted nicely, no signs of a
kernel panic. The driver was happily picked up in the initramfs. I'm
going to run it through some stress-ng tests to make sure everything is
fine but we're off to a good start.
** Tags removed: verification-needed-xenial
**
The following patch has been tested succesfully:
--- hook-functions.orig 2017-08-21 08:00:47.303094616 +
+++ hook-functions 2017-08-23 07:43:56.893817027 +
@@ -519,6 +519,9 @@ auto_add_modules()
macvtap.ko pcmcia sb1000.ko team tokenring \
** Description changed:
- We're adding a backported bnxt driver to Xenial (LP #1711056). It's an
- alternate for the regular Xenial driver that only manages NICs that are
- not supported by the regular Xenial driver. But it's a boot-critical
- driver so it needs to be added to the initramfs.
+
Public bug reported:
We're adding a backported bnxt driver to Xenial (LP #1711056). It's an
alternate for the regular Xenial driver that only manages NICs that are
not supported by the regular Xenial driver. But it's a boot-critical
driver so it needs to be added to the initramfs.
---
94 matches
Mail list logo
