Comment # 18
on bug 110822
from Gobinda Joy
(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.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
