unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: romulasry <romulasry@protonmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#36757: AMD-Vi IOMMU bug, kernel crashes using GuixSD 1.0.1"
Date: Sat, 27 Jul 2019 01:44:23 +0000	[thread overview]
Message-ID: <ofa8qO5VXwvIfCynnQ3XiZV-WhGInPAa--8nH68EXs6oPVWaGrkORcjUQxGXJDoX5C-HE06AMFtXZHDTG7Qn-cj6jUwkWoVZG2fvLtNHGzg=@protonmail.com> (raw)
In-Reply-To: <871ryet4sg.fsf@gnu.org>

I get the same hang when I turn off amd virtualization.

It must be the bottom error that is causing it. I assume because i get the same error then hang when it is the IOMMU setting is set to off in the UEFI.
Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, July 25, 2019 10:14 AM, Ludovic Courtès <ludo@gnu.org> wrote:

> Hello romulasry,
>
> romulasry romulasry@protonmail.com skribis:
>
> > https://ibb.co/kyBrwRc
>
> I don’t actually see a crash on this picture, just repeated messages
> like:
>
> AMD-Vi: Event logged [IO_PAGE_FAULT …]
>
> Did the system actually crash or hang?
>
> I suppose it would be worth reporting the issue to the kernel developers
> because that doesn’t seem to be Guix-specific.
>
> Thanks,
> Ludo’.

  reply	other threads:[~2019-07-27 21:11 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 [this message]
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

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='ofa8qO5VXwvIfCynnQ3XiZV-WhGInPAa--8nH68EXs6oPVWaGrkORcjUQxGXJDoX5C-HE06AMFtXZHDTG7Qn-cj6jUwkWoVZG2fvLtNHGzg=@protonmail.com' \
    --to=romulasry@protonmail.com \
    --cc=ludo@gnu.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.
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).