From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209025] The "VFIO_MAP_DMA failed: Cannot allocate memory" bug is back
Date: Tue, 25 Aug 2020 17:09:05 +0000 [thread overview]
Message-ID: <bug-209025-28872-dV11PwqzYf@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209025-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209025
--- Comment #9 from Niklas Schnelle (niklas@komani.de) ---
Hi Robert,
git does not know what you compiled so you could just
do "git bisect;git good v5.8;git bad v5.9-rc1"
with that said it is of course best to always compile the versions
you tell git are (not) working.
I'm a fellow Arch Linux user (on all my private machines) and actually suspect
its current QEMU and other package versions were necessary to expose this bug
and are the reason Alex could not reproduce this.
I did not do the git bisect with PKGBUILDs though, instead I
have a custom systemd-boot entry and in the .config set LOCALVERSION="-niklas"
then I used the following commands:
cd linux
zcat /proc/config.gz > .config # once ton get Arch Config
make oldconfig
make -j 24
sudo make modules_install -j INSTALL_MOD_STRIP=1
sudo cp arch/x86_64/boot/bzImage /boot/vmlinuz-linux-niklas
sudo mkinitcpio -p linux-niklas
The last part is arch specific, on other distros there is a special
installkernel script that does the copy to /boot and rebuilds the initramfs and
also creates bootloader entries.
Also only add the strip flag if you don't need debug symbols
in modules.
The manual cp/modules_install of course means I have
to delete the /usr/lib/modules/.. folders manually but they all have "niklas"
in the name so that's easy enough ;-)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-08-25 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 16:35 [Bug 209025] New: The "VFIO_MAP_DMA failed: Cannot allocate memory" bug is back bugzilla-daemon
2020-08-24 20:43 ` [Bug 209025] " bugzilla-daemon
2020-08-24 20:57 ` bugzilla-daemon
2020-08-25 0:53 ` bugzilla-daemon
2020-08-25 3:14 ` bugzilla-daemon
2020-08-25 7:26 ` bugzilla-daemon
2020-08-25 14:32 ` bugzilla-daemon
2020-08-25 14:32 ` bugzilla-daemon
2020-08-25 16:31 ` bugzilla-daemon
2020-08-25 17:09 ` bugzilla-daemon [this message]
2020-08-25 17:13 ` bugzilla-daemon
2020-08-25 17:47 ` bugzilla-daemon
2020-08-25 17:55 ` bugzilla-daemon
2020-08-25 18:06 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-209025-28872-dV11PwqzYf@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox