All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 194559] New: amdgpu problems loading 2 firmwares on multi-smp system
Date: Sun, 12 Feb 2017 14:34:36 +0000	[thread overview]
Message-ID: <bug-194559-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=194559

            Bug ID: 194559
           Summary: amdgpu problems loading 2 firmwares on multi-smp
                    system
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.4.9
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: janpieter.sollie@dommel.be
        Regression: No

Created attachment 254705
  --> https://bugzilla.kernel.org/attachment.cgi?id=254705&action=edit
dmesg.txt, lspci.txt and .config

System: opteron 2876 (*2), 128GB ram, x86_64.
VGA1: SI, cape verde pro.
VGA2: R9 nano.
VGA3: onboard mgag200.
Distribution: gentoo.
kernel: vanilla-sources-4.9.9.
kernel loader: lilo 24
firmware: linux-firmware-20170126.
bug: amdgpu loading on the system causes a reboot. even when disabling panic,
the kernel does not wait for me to reset the system. the issue occurs even when
booting the system with init=/bin/bash and then modprobe amdgpu.
solutions:
1) removing /lib/firmware/radeon.
2) removing /lib/firmware/amdgpu.
3) boot the kernel with nosmp.
Each of these solutions works, but causes hardware not to be initialized
Tried without success:
1) using the radeon module instead of amdgpu.
2) using amdgpu-pro.
3) using a different kernel version (4.4.39).
4) boot with iommu=soft.
5) first load drm (works), then load amdgpu (crashes).

I suspect a nonsafe threaded kernel bug in drm.

In attachment:
1) dmesg of noSMP boot.
2) lspci output.
3) config of current 4.9.9 kernel.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-02-12 14:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-12 14:34 bugzilla-daemon [this message]
2017-02-12 16:09 ` [Bug 194559] amdgpu problems loading 2 firmwares on multi-smp system bugzilla-daemon
2017-02-13  3:28 ` bugzilla-daemon
2017-02-14  6:55 ` bugzilla-daemon
2017-02-14  7:59 ` bugzilla-daemon
2017-02-14  8:00 ` bugzilla-daemon
2017-02-14  8:02 ` bugzilla-daemon
2017-02-14  8:15 ` bugzilla-daemon
2017-02-14  8:32 ` bugzilla-daemon
2017-02-14 15:05 ` bugzilla-daemon
2017-02-14 15:18 ` bugzilla-daemon
2017-02-16  9:15 ` bugzilla-daemon
2017-02-28  9:42 ` bugzilla-daemon
2017-03-16 10:01 ` 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-194559-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.