All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104472] Gigabyte AB350 and Radeon Pro WX2100 crashes with activated ACPI
Date: Wed, 03 Jan 2018 07:49:33 +0000	[thread overview]
Message-ID: <bug-104472-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 957 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=104472

            Bug ID: 104472
           Summary: Gigabyte AB350 and Radeon Pro WX2100 crashes with
                    activated ACPI
           Product: DRI
           Version: DRI git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: lcid-fire@gmx.net

Downstream prompted to file a bug for
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740019

I am running a Ubuntu 16.04 on a Gigabyte AB350-Gaming 3 board. It runs fine
with a Nvidia Quadro GPU. When I switch the Quadro with a Radeon Pro WX2100 the
system stops booting (leads to kernel panics).
The only way to boot is then to add `acpi=off`.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2323 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2018-01-03  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-03  7:49 bugzilla-daemon [this message]
2018-01-03  7:55 ` [Bug 104472] Gigabyte AB350 and Radeon Pro WX2100 crashes with activated ACPI bugzilla-daemon
2019-11-19  8:28 ` 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-104472-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.