<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 28 September 2024 at 01:46pm,
Christian Zigotzky wrote:<br>
</div>
<blockquote type="cite"
cite="mid:d10b0d41-8389-4b09-a531-c9c5d67df3b7@xenosoft.de">Am
28.09.24 um 10:42 schrieb Christophe Leroy:
<br>
<blockquote type="cite">Hi Christian,
<br>
<br>
Le 28/09/2024 à 09:40, Christian Zigotzky a écrit :
<br>
<blockquote type="cite">On 28 September 2024 at 09:21am,
Christian Zigotzky wrote:
<br>
>
<br>
>> On Sun, Sep 22, 2024 at 12:28 AM Christian Zigotzky
<br>
>> <a class="moz-txt-link-rfc2396E" href="mailto:chzigotzky@xenosoft.de"><chzigotzky@xenosoft.de></a> wrote:
<br>
>>>
<br>
>>> Hi All,
<br>
>>>
<br>
>>> The lastest Git kernel doesn't boot anymore
after the latest DRM updates
<br>
>>> (drm-next-2024-09-19). [1]
<br>
>>>
<br>
>>> I tested it with an AMD Radeon HD 6970 (Cayman
XT) and with an AMD
<br>
>>> Radeon HD 5870 (Cypress XT).
<br>
>>>
<br>
>>> I reverted the DRM updates and after that the
kernel boots without any
<br>
>>> problems.
<br>
>>>
<br>
>>> Please note: Due to a lack of time, I can't do a
bisect.
<br>
>>>
<br>
>>> Please check the latest DRM updates.
<br>
------------
<br>
>>
<br>
>> Can you attach your dmesg output? There was a
regression in the dma
<br>
>> subsystem what was fixed by this commit:
<br>
>>
<br>
>> commit b348b6d17fd1d5d89b86db602f02be
<br>
>> a54a754bd8
<br>
>> Author: Leon Romanovsky <a class="moz-txt-link-rfc2396E" href="mailto:leon@kernel.org"><leon@kernel.org></a>
<br>
>> Date: Sun Sep 22 21:09:48 2024 +0300
<br>
>>
<br>
>> dma-mapping: report unlimited DMA addressing in
IOMMU DMA path
<br>
>>
<br>
>> Alex
<br>
>>
<br>
<br>
------------
<br>
Hi Alex,
<br>
<br>
I tested the latest Git kernel on my FSL P5040 board today and
it doesn't boot. Our FSL P5020 boards boot without any
problems.
<br>
<br>
I connected my FSL P5040 board with a serial cable to my PC
for getting error messages. Unfortunately there aren't any
error messages after the loading of the uImage.
<br>
<br>
This means, that the dma-mapping patch doesn't solve the boot
issue.
<br>
<br>
Please check the latest DRM updates.
<br>
</blockquote>
<br>
Can you bisect the problem ?
<br>
<br>
Christophe
<br>
</blockquote>
I would like ... but I don't have time for it. Sorry.
<br>
</blockquote>
<br>
Hi All,<br>
<br>
Sorry, I have forgotten to add the boot arguments "<span
class="posthilit">console</span>=ttyS0,115200" for the connecting
of my FSL P5040 board with a serial cable to my PC.<br>
<br>
Now, I have a serial log file with Radeon error messages (kernel
trace). :-)<br>
<br>
Link: <a class="moz-txt-link-freetext" href="https://www.xenosoft.de/PuTTY_P5040_U-Boot.log">https://www.xenosoft.de/PuTTY_P5040_U-Boot.log</a><br>
<br>
I hope, you have an idea. The FSL P5020 boards aren't affected.<br>
<br>
Thanks,<br>
Christian<br>
</body>
</html>