This bug was fixed in the package kdump-tools - 1:1.6.10ubuntu2.2
---
kdump-tools (1:1.6.10ubuntu2.2) jammy; urgency=medium
* Disable the initramfs generation in our kernel-postinst hook when
we detect we are running in a chroot. LP: #2043059.
-- dann frazier Thu, 01 Feb
This bug was fixed in the package kdump-tools - 1:1.8.1ubuntu1.1
---
kdump-tools (1:1.8.1ubuntu1.1) mantic; urgency=medium
* Disable the initramfs generation in our kernel-postinst hook when
we detect we are running in a chroot. LP: #2043059.
-- dann frazier Thu, 01 Feb
** Attachment added: "jammy: verification steps 4-6"
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+attachment/5744328/+files/jammy.log
** Tags removed: verification-needed verification-needed-jammy
verification-needed-mantic
** Tags added: verification-done
** Attachment added: "mantic: verification steps 4-6"
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+attachment/5744327/+files/mantic.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
# verification steps 1-3: installation in a chroot
I set up 2 chroots - one w/ the normal sources.list, the other w/
proposed enabled, and did a side by side install test.
$ for chroot in mantic mantic-proposed jammy jammy-proposed; do sudo chroot
$chroot apt list kdump-tools; done
Listing...
Hello Brad, or anyone else affected,
Accepted kdump-tools into mantic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/kdump-
tools/1:1.8.1ubuntu1.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Description changed:
- Processing triggers for linux-image-5.15.0-1040-nvidia (5.15.0-1040.40) ...
- /etc/kernel/postinst.d/dkms:
- * dkms: running auto installation service for kernel 5.15.0-1040-nvidia
-...done.
- /etc/kernel/postinst.d/initramfs-tools:
- update-initramfs: Generating
** Also affects: linux-nvidia (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Also affects: kdump-tools (Ubuntu Noble)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Fix Released
** Also affects: linux-nvidia (Ubuntu Mantic)
Importance: Undecided
On Fri, Dec 15, 2023 at 3:55 PM Sam Tannous <2043...@bugs.launchpad.net> wrote:
>
> You're correct. It can fail for other reasons. I don't think we could check
> the errno, could we? It would be 1, "Operation not permitted".
The exit code is not documented in the manpage, and it appears to
This bug was fixed in the package kdump-tools - 1:1.8.2ubuntu1
---
kdump-tools (1:1.8.2ubuntu1) noble; urgency=medium
* Merge from Debian unstable. Remaining changes:
- debian/control/tests: sleep while waiting for systemd service.
- Bump amd64 crashkernel from 384M-:128M
You're correct. It can fail for other reasons. I don't think we could check
the errno, could we? It would be 1, "Operation not permitted".
If not, I think we can live with the last suggestion.
Thanks,
--
You received this bug notification because you are a member of Kernel
Packages, which
Cool, thanks for testing Sam. Apologies for the missing ${SW_IMG}.
And thanks for the 'unshare -U true' suggestion. I gather your point is
that 'unshare -U' will fail in any chroot environment. I'm not an expert
on namespaces but, from what I can tell, that does seem to be true in
all modern
Hey Dann,
This seems to work ok if I make the changes in our script.
Let me propose this script change to the owners I'll get back to you.
Thanks,
Sam
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia in Ubuntu.
hey Sam,
I looked into ways to try to teach the chroot detection tools how to
detect a chroot in a new pid namespace (which is actually the problem,
not the mount namespace), but I didn't find a good solution there.
However, it occurs to me that you can simply override the answer:
ln -sf
** Also affects: kdump-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-nvidia (Ubuntu)
Status: New => Invalid
** Changed in: kdump-tools (Ubuntu)
Status: New => Triaged
** Changed in: kdump-tools (Ubuntu)
Assignee: (unassigned) => dann frazier
Thanks, Dann,
This dpkg-divert won't work unless we first remove the package this "clashes"
with (nvidia-crashdump had already diverted this file). Not sure if this is
really much better than just removing kdump-tools (and dependencies) and then
reinstalling them later.
We're still looking
Thanks for providing that script Sam. Jamie has nailed the problem in
Comment #2. A *seemingly* obvious solution is to add code to the
/etc/kernel/postinst.d/kdump-tools hook that detects when it is running
in a chroot, and if so, exits before trying to make an initramfs. When
the real system
Hello Ian,
I've uploaded the cm-chroot-sw-img script here.
Please let me know if you need more info.
--Sam
** Attachment added: "cm-chroot-sw-img script"
https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2043059/+attachment/5719804/+files/cm-chroot-sw-img
--
You received this
Hello Ian,
It looks like we are mounting /dev:
here is how /dev is mounted when you use the cm-chroot-sw-image command,
jd-b91-s15sp4-11-07:~ # mount | grep image
udev on /cm/images/default-image/dev type devtmpfs
(rw,relatime,size=4096k,nr_inodes=1048576,mode=755,inode64)
devpts on
Hi Ian,
I have access to
http://bright-dev.nvidia.com/base-distributions/x86_64/dgx-os/dgx-
os-6.1-trd4/DGXOS-6.1.0-DGX-H100.tar.gz
And can upload it here if you need.
--Sam
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia
I don't appear to have access to the image file used in the reproducer.
http://bright-dev.nvidia.com/base-distributions/x86_64/dgx-os/dgx-os-6.1-trd4/DGXOS-6.1.0-DGX-H100.tar.gz
So instead I'm using the following image for reproducing.
I believe the key to the reproducer is having the kdump-tools package
installed in the chroot. The kdump-tools package provides a
/etc/kernel/postinst.d/kdump-tools script, which has the following
snippet:
(Apologies for formatting, the interface removes the leading spaces from
this code)
43
The complete recreate steps with errors are the following:
Steps to reproduce:
1. Create a directory on a BCM head node or any Linux sever, say
/cm/images/dgx-h100-image
2. Download and unpack the DGX-OS base tar archive into the above
directory
$ wget
23 matches
Mail list logo
