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 110822] [Bisected]Booting with kernel version 5.1.0 or higher on RX 580 hangs
Date: Wed, 12 Jun 2019 04:35:19 +0000	[thread overview]
Message-ID: <bug-110822-502-jSVusQC26X@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110822-502@http.bugs.freedesktop.org/>


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

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

--- Comment #18 from Gobinda Joy <gobinda.joy@gmail.com> ---
(In reply to b6khqjqov4 from comment #17)
> (In reply to Gobinda Joy from comment #16)
> > This doesn't seems like the same bug. For instance, in my case the whole
> > boot process hangs check the attached log files. In your case you can boot
> > the system but problem arise when you load the GPU maybe. Not the same bug.
> 
> You could still try disabling the integrated graphics in the BIOS. AFAICR I
> could always log in into the Cinnamon desktop and only then I would get a
> hard freeze within minutes up to several hours, not within the boot process
> itself, so maybe indeed not the same bug. The RX 590 needed additional
> commits to be supported in Linux, so maybe similar but different issues.
> (I assume you can you boot without the RX 590 using your CPU's integrated
> graphics without any issues with the problematic commit/it really is a RX590
> issue, well it must be I guess since it's in AMDgpu and you tested it.)
> 
> Because of the Athlon 200GE my 3000 MHz RAM is also running at slower
> 2133MHz, but even at the, in fact, safe 2133, that should not be the reason
> for the hangs/freezes, as the proof is that you fixed it by bisecting and I
> fixed my freezes with my mentioned method. 
> 
> I don't know anything about the calls of those functions and I hope your bug
> report is on the devs' radar, especially that you found out the problematic
> commit ad51c46e, now.
> 
> PS: Fortunately I still have had no freezes/any issues since my fixes
> (5.1.8-arch1-1-ARCH now).

I'm using a discrete GPU so obviously the integrated GPU is disabled. Also I'm
using Vt-D to passthrough a LAN card and a sound card to my windows VM. I don't
use that for gaming though. Only use fedora/wine for gaming. Need the windows
VM for some work related stuff and sometimes music as the sound card driver is
superior in windows.

My 24GB DDR3 Ram is running at 1600 (10-10-10-26 maybe haven't checked in a
while). And you are right slow ram shouldn't be the reason for freezes or
hangs. Apart from that previous kernel was perfect for me. Since your card is
RX590 you do need the new commits/kernel to support that. I was happy with
kernel 5.0.17 until fedora decided to push 5.1+ kernel through update.

I am not sure about those function calls myself. But as I read through the
source they are traversing the PCIe tree for the min bandwidth bottleneck or
limiter. and using that to set the max bandwidth for the device in context.

What I don't get is why they are using 2 calls to get the bandwidth reading.
Since both function walking the PCIe tree what's the point. Also it seems like
the call to pcie_bandwidth_available() function is casing the freeze/hangs in
my system. So that's counts for something.

I hope devs noticed this too. As they asked me to bisect this. If they don't I
did all this for nothing. Sorry, not for nothing as I can now run the latest
kernel with that commit reverted.

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

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

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

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

  parent reply	other threads:[~2019-06-12  4:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03  9:37 [Bug 110822] booting with kernel version 5.1.0 or higher on RX 580 hangs bugzilla-daemon
2019-06-03  9:42 ` bugzilla-daemon
2019-06-03 22:03 ` bugzilla-daemon
2019-06-04  6:29 ` bugzilla-daemon
2019-06-04  6:44 ` bugzilla-daemon
2019-06-04  8:34 ` bugzilla-daemon
2019-06-04 13:35   ` sylvain.bertrand
2019-06-04 13:35 ` bugzilla-daemon
2019-06-04 18:54 ` bugzilla-daemon
2019-06-04 18:55 ` bugzilla-daemon
2019-06-04 18:56 ` bugzilla-daemon
2019-06-04 18:56 ` bugzilla-daemon
2019-06-04 18:57 ` bugzilla-daemon
2019-06-05  9:51 ` bugzilla-daemon
2019-06-05 11:47 ` bugzilla-daemon
2019-06-06 18:43 ` [Bug 110822] [Bisected]Booting " bugzilla-daemon
2019-06-10 11:09 ` bugzilla-daemon
2019-06-10 11:19 ` bugzilla-daemon
2019-06-10 11:27 ` bugzilla-daemon
2019-06-10 14:08 ` bugzilla-daemon
2019-06-10 15:00 ` bugzilla-daemon
2019-06-10 16:22 ` bugzilla-daemon
2019-06-11 14:44 ` bugzilla-daemon
2019-06-12  4:35 ` bugzilla-daemon [this message]
2019-06-12 18:30 ` bugzilla-daemon
2019-06-13  7:44 ` bugzilla-daemon
2019-06-28  9:44 ` bugzilla-daemon
2019-11-19  9:29 ` 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-110822-502-jSVusQC26X@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