From: mvf <mvf@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Linux Kernal
Date: Fri, 29 Jan 2021 15:35:18 +0100 [thread overview]
Message-ID: <20210129143518.SCu9xpWuzleiRiJNwqVfHE5QC3MkZx9QKswooOcqeTk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27423@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 638 bytes --]
New comment by mvf on void-packages repository
https://github.com/void-linux/void-packages/issues/27423#issuecomment-769841241
Comment:
Booting with `intel_iommu=off` like Leah suggested will fix this since it disables the panicking code path. See the [GRUB section of the docs](https://docs.voidlinux.org/config/kernel.html#grub) on how to do this. To test it first without changing your system, you can select the kernel in GRUB, press <kbd>E</kbd>, append `intel_iommu=off` to the command line and press <kbd>F10</kbd> to boot.
There's still a Void bug here. `CONFIG_INTEL_IOMMU_DEFAULT_ON=y` is not suitable for a distro kernel.
next prev parent reply other threads:[~2021-01-29 14:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 14:34 [ISSUE] " ayoubkafi
2020-12-29 10:01 ` Mek101
2020-12-30 18:27 ` leahneukirchen
2021-01-05 10:47 ` Anachron
2021-01-21 17:28 ` ericonr
2021-01-22 9:03 ` ayoubkafi
2021-01-22 9:19 ` Anachron
2021-01-28 17:48 ` ayoubkafi
2021-01-28 19:04 ` ericonr
2021-01-28 20:46 ` ayoubkafi
2021-01-28 21:28 ` ericonr
2021-01-29 14:35 ` mvf [this message]
2021-01-29 14:52 ` ericonr
2021-01-29 14:57 ` ahesford
2021-01-29 17:30 ` ayoubkafi
2021-01-29 17:33 ` ayoubkafi
2021-01-29 17:35 ` ayoubkafi
2021-01-29 17:35 ` ayoubkafi
2021-01-29 17:46 ` Anachron
2021-01-29 17:58 ` ayoubkafi
2021-02-04 12:48 ` ayoubkafi
2021-02-04 13:07 ` Anachron
2021-02-04 13:11 ` travankor
2021-02-17 10:50 ` Anachron
2021-02-17 15:35 ` ahesford
2021-02-17 15:35 ` [ISSUE] [CLOSED] " ahesford
2021-02-17 15:36 ` ahesford
2021-03-24 12:22 ` ayoubkafi
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=20210129143518.SCu9xpWuzleiRiJNwqVfHE5QC3MkZx9QKswooOcqeTk@z \
--to=mvf@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).