FSL P5040 board doesn't boot after DRM updates (drm-next-2024-09-19)

[Christian Zigotzky]

On 28 September 2024 at 01:46pm, Christian Zigotzky wrote:
> Am 28.09.24 um 10:42 schrieb Christophe Leroy:
>> Hi Christian,
>>
>> Le 28/09/2024 à 09:40, Christian Zigotzky a écrit :
>>> On 28 September 2024 at 09:21am, Christian Zigotzky wrote:
>>>  >
>>>  >> On Sun, Sep 22, 2024 at 12:28 AM Christian Zigotzky
>>>  >> <chzigotzky at xenosoft.de> wrote:
>>>  >>>
>>>  >>> Hi All,
>>>  >>>
>>>  >>> The lastest Git kernel doesn't boot anymore after the latest 
>>> DRM updates
>>>  >>> (drm-next-2024-09-19). [1]
>>>  >>>
>>>  >>> I tested it with an AMD Radeon HD 6970 (Cayman XT) and with an AMD
>>>  >>> Radeon HD 5870 (Cypress XT).
>>>  >>>
>>>  >>> I reverted the DRM updates and after that the kernel boots 
>>> without any
>>>  >>> problems.
>>>  >>>
>>>  >>> Please note: Due to a lack of time, I can't do a bisect.
>>>  >>>
>>>  >>> Please check the latest DRM updates.
>>> ------------
>>>  >>
>>>  >> Can you attach your dmesg output?  There was a regression in the 
>>> dma
>>>  >> subsystem what was fixed by this commit:
>>>  >>
>>>  >> commit b348b6d17fd1d5d89b86db602f02be
>>>  >> a54a754bd8
>>>  >> Author: Leon Romanovsky <leon at kernel.org>
>>>  >> Date:   Sun Sep 22 21:09:48 2024 +0300
>>>  >>
>>>  >>    dma-mapping: report unlimited DMA addressing in IOMMU DMA path
>>>  >>
>>>  >> Alex
>>>  >>
>>>
>>> ------------
>>> Hi Alex,
>>>
>>> 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.
>>>
>>> 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.
>>>
>>> This means, that the dma-mapping patch doesn't solve the boot issue.
>>>
>>> Please check the latest DRM updates.
>>
>> Can you bisect the problem ?
>>
>> Christophe
> I would like ... but I don't have time for it. Sorry.

Hi All,

Sorry, I have forgotten to add the boot arguments "console=ttyS0,115200" 
for the connecting of my FSL P5040 board with a serial cable to my PC.

Now, I have a serial log file with Radeon error messages (kernel trace). :-)

Link: https://www.xenosoft.de/PuTTY_P5040_U-Boot.log

I hope, you have an idea. The FSL P5020 boards aren't affected.

Thanks,
Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20240928/27ae11bf/attachment.htm>