Seeing some strange "Device or resource busy" errors on the
/usr/bin/nvidia-debugdump file, seemingly due to Nvidia lossage. Closing
as likely unrelated to the packaging.
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: New => Invalid
--
You received this bug notification
Public bug reported:
This concerns nvidia-utils-535 (535.161.07-0ubuntu3) in Ubuntu noble.
I had already installed nvidia-cuda-toolkit, and then...
# apt-get install nvidia-utils-535
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Suggested
Public bug reported:
This concerns linux-base 4.0ubuntu1 in Ubuntu Xenial.
Removing Linux kernel packages from the system leads to initrd
generation and causes /var/run/reboot-required to appear. Neither of
these side effects should occur if only kernel packages older than the
running one are
I should point out, the update-initramfs invocations should also not be
happening for kernel packages being removed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1636701
Title:
Public bug reported:
I'm filing this against dkms 2.2.0.3-2ubuntu11.2 in Ubuntu Xenial,
although the issue may come down to a different package.
I issued an "apt-get --purge autoremove" command to clear out some old
kernel packages, and the command took several minutes to complete due to
kernel
Bryan: Are you saying 256MB was needed in order for the crash kernel to
boot, that 128MB was not enough?
(I'm not sure that there is any advantage to reserving more memory than
needed, aside from the kernel one day growing to need 129MB)
--
You received this bug notification because you are a
Ah, okay, that's an issue. Not only do we not have an easy way of
measuring how much memory a kernel needs to boot, we don't know how that
requirement varies depending on the system configuration...
--
You received this bug notification because you are a member of Kernel
Packages, which is
Agreed. It's not clear that there is *any* standard Ubuntu kernel
configuration that can boot in 64MB. And having that as a default is
worse than useless, because the crash-kernel's OOM prevents the system
from recovering automatically after a kernel crash.
--
You received this bug notification
Bryan: Could you elaborate on how this issue appears to be fixed in
13.04? Was the memory reservation increased to 128MB, or is the kernel
now capable of booting in 64MB? Given the lack of any updates here, I'm
doubtful that any progress has been made at all.
Dave: Have you tried crash-booting a
9 matches
Mail list logo
