unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: romulasry@protonmail.com, via web <issues.guix.gnu.org@elephly.net>
Cc: 36757@debbugs.gnu.org
Subject: bug#36757: AMD-Vi IOMMU bug, kernel crashes using GuixSD 1.0.1
Date: Wed, 10 Jun 2020 03:56:44 +0200	[thread overview]
Message-ID: <874krjsmxv.fsf@nckx> (raw)
In-Reply-To: <7fb6383bab00.1f99c37e1a9151e4@guile.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 666 bytes --]

Romulasry,

romulasry@protonmail.com, via web 写道：
> It is a amdgpu firmware bug,

We've had some trouble booting with the non-free AMDGPU graphics 
cards before, but the ‘AMD-Vi IOMMU’ part is new to me.  What 
exactly happens?  Which error messages (if any) do you get 
(pictures are fine, but please compress them to a few 100k or host 
them elsewhere)?

> will guixsd ever support it?

We can certainly try, if we know what (kernel CONFIG_ option, 
kernel command-line option, …) is required.

Since you seem to know more about the bug, could you explain it in 
more detail of provide a link to more information?

Thanks,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

      reply	other threads:[~2020-06-10  1:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <JY7iFY2a15XvSmDM-VEbD_QYi4Ife3oZCJaT4IbIFyORLtOS-QqswZnDB-shZgDDA6CSEyUgJK9GPGp1sd76sGsjgb15fCVLOS0KO7DPrgU=@protonmail.com>
2019-07-22 14:09 ` bug#36757: AMD-Vi IOMMU bug, kernel crashes using GuixSD 1.0.1" romulasry
2019-07-25 17:14   ` Ludovic Courtès
2019-07-27  1:44     ` romulasry
2020-06-10  0:46 ` bug#36757: AMD-Vi IOMMU bug, kernel crashes using GuixSD 1.0.1 romulasry
2020-06-10  1:56   ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874krjsmxv.fsf@nckx \
    --to=bug-guix@gnu.org \
    --cc=36757@debbugs.gnu.org \
    --cc=issues.guix.gnu.org@elephly.net \
    --cc=me@tobias.gr \
    --cc=romulasry@protonmail.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).