dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108361] Radeon/Xorg crash during boot with Radeon R5 M230
Date: Mon, 15 Oct 2018 05:58:40 +0000	[thread overview]
Message-ID: <bug-108361-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 108361
           Summary: Radeon/Xorg crash during boot with Radeon R5 M230
           Product: DRI
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: jian-hong@endlessm.com

Created attachment 142025
  --> https://bugs.freedesktop.org/attachment.cgi?id=142025&action=edit
journal log when radeon/Xorg crash

This is found on Acer Veriton Z4660G desktop equipped with Intel(R) Core(TM)
i7-8700 CPU and an AMD/ATI Jet PRO Radeon R5 M230 graphic card.

01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Jet
PRO [Radeon R5 M230] [1002:6665] (rev 83)
        Subsystem: PC Partner Limited / Sapphire Technology Jet PRO [Radeon R5
M230] [174b:e332]
        Flags: bus master, fast devsel, latency 0, IRQ 127
        Memory at 90000000 (64-bit, prefetchable) [size=256M]
        Memory at 7c300000 (64-bit, non-prefetchable) [size=256K]
        I/O ports at 4000 [size=256]
        Expansion ROM at 7c340000 [disabled] [size=128K]
        Capabilities: [48] Vendor Specific Information: Len=08 <?>
        Capabilities: [50] Power Management version 3
        Capabilities: [58] Express Legacy Endpoint, MSI 00
        Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
        Capabilities: [150] Advanced Error Reporting
        Capabilities: [200] #15
        Capabilities: [270] #19
        Kernel driver in use: radeon
        Kernel modules: radeon, amdgpu

I have tested it with Linux kernel 4.19-rc7.  System (radeon module) sometimes
hits the error during boot, then Xorg crashes.

Oct 12 17:28:52 endless kernel: [drm:atom_op_jump [radeon]] *ERROR* atombios
stuck in loop for more than 5secs aborting
Oct 12 17:28:52 endless kernel: [drm:atom_execute_table_locked [radeon]]
*ERROR* atombios stuck executing 67C0 (len 254, WS 0, PS 4) @ 0x67CE
Oct 12 17:28:52 endless kernel: [drm:atom_execute_table_locked [radeon]]
*ERROR* atombios stuck executing 612C (len 78, WS 12, PS 8) @ 0x6165
Oct 12 17:28:52 endless kernel: iwlwifi 0000:00:14.3: HCMD_ACTIVE already clear
for command SCAN_REQ_UMAC
Oct 12 17:28:52 endless kernel: [drm] PCIE gen 3 link speeds already enabled
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: Wait for MC idle timedout
!
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: Wait for MC idle timedout
!
Oct 12 17:28:54 endless eos-metrics-ins[606]: Failed to start GeoClue2 client:
GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected
from message bus without replying.
Oct 12 17:28:54 endless kernel: [drm] PCIE GART of 2048M enabled (table at
0x0000000000040000).
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: WB enabled
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 0 use
gpu addr 0x0000000080000c00 and cpu addr 0x000000007d0c53c5
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 1 use
gpu addr 0x0000000080000c04 and cpu addr 0x000000006e1c12be
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 2 use
gpu addr 0x0000000080000c08 and cpu addr 0x00000000a603d5e9
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 3 use
gpu addr 0x0000000080000c0c and cpu addr 0x0000000039a9e421
Oct 12 17:28:54 endless kernel: radeon 0000:01:00.0: fence driver on ring 4 use
gpu addr 0x0000000080000c10 and cpu addr 0x00000000ba920de2
Oct 12 17:28:55 endless kernel: [drm:r600_ring_test [radeon]] *ERROR* radeon:
ring 0 test failed (scratch(0x850C)=0xCAFEDEAD)
Oct 12 17:28:55 endless kernel: [drm:si_resume [radeon]] *ERROR* si startup
failed on resume

I also tried to disable radeon's runtime power management by passing
"radeon.runpm=0" to boot command.  It makes system working stable on this
model.

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

[-- Attachment #1.2: Type: text/html, Size: 5723 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-10-15  5:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  5:58 bugzilla-daemon [this message]
2019-04-17  2:17 ` [Bug 108361] Radeon/Xorg crash during boot with Radeon R5 M230 bugzilla-daemon
2019-11-19  9:34 ` 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-108361-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox