linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Christian Zigotzky <chzigotzky@xenosoft.de>
Cc: DRI developers <dri-devel@lists.freedesktop.org>,
	mad skateman <madskateman@gmail.com>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	Darren Stevens <darren@stevens-zone.net>,
	hypexed@yahoo.com.au,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: FSL P5040 board doesn't boot after DRM updates (drm-next-2024-09-19)
Date: Sat, 28 Sep 2024 10:42:05 +0200	[thread overview]
Message-ID: <14b64e90-2e3b-4bee-a8c9-2f8d6eed5d68@csgroup.eu> (raw)
In-Reply-To: <48f59b5b-b26e-49c5-9b58-1c877bea394d@xenosoft.de>

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@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@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


  parent reply	other threads:[~2024-09-28  8:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADnq5_MM6UYOwFSPkZRauAyckFaUjCRGT97cVhsK=xZ9CzuXVw@mail.gmail.com>
     [not found] ` <20EA4BE5-B349-4406-89EA-3D442717EC03@xenosoft.de>
2024-09-28  7:40   ` FSL P5040 board doesn't boot after DRM updates (drm-next-2024-09-19) Christian Zigotzky
2024-09-28  8:08     ` mad skateman
2024-09-28  8:42     ` Christophe Leroy [this message]
2024-09-28 11:46       ` Christian Zigotzky
2024-09-28 12:15         ` Christian Zigotzky
2024-09-29 14:37       ` Christian Zigotzky
2024-09-30 13:26         ` Alex Deucher
2024-10-01  4:26           ` Kernel " Christian Zigotzky
2024-10-01 12:09             ` Hoi Pok Wu
2024-10-01 12:23               ` Christophe Leroy
2024-10-01 14:41                 ` Hoi Pok Wu
2024-10-02 13:43                 ` Hoi Pok Wu
2024-10-03  4:57                   ` Christian Zigotzky

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=14b64e90-2e3b-4bee-a8c9-2f8d6eed5d68@csgroup.eu \
    --to=christophe.leroy@csgroup.eu \
    --cc=alexander.deucher@amd.com \
    --cc=chzigotzky@xenosoft.de \
    --cc=darren@stevens-zone.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hypexed@yahoo.com.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=rtd2@xtra.co.nz \
    /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;
as well as URLs for NNTP newsgroup(s).