Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Ruben Van Boxem <vanboxem.ruben@gmail.com>
Cc: dlemoal@kernel.org, linux-ide@vger.kernel.org
Subject: Re: ahci module throws "Internal error: synchronous external abort: 0000000096000210 [#1] SMP"
Date: Tue, 2 Apr 2024 20:52:13 +0200	[thread overview]
Message-ID: <ZgxT3QqHJ6rq9nqq@ryzen> (raw)
In-Reply-To: <CALc40c9+ZFnimQ_KP7YpCGgP=iQBeDSS-xPAwwiraeX42yK30g@mail.gmail.com>

On Tue, Apr 02, 2024 at 08:15:05PM +0200, Ruben Van Boxem wrote:
> Hi Niklas and others,
> 
> Op ma 26 feb 2024 om 21:41 schreef Niklas Cassel <cassel@kernel.org>:
> >
> > Hello Ruben,
> >
> > I would recommend you to test with the latest kernel, v6.8-rc6.
> >
> > I don't know which device tree you are using, but very often custom
> > add on cards/HATs require specific device tree overlays to enable
> > certain regulators etc.
> >
> > I suspect that this is something not related to AHCI, but rather
> > some regulator or similar that is not enabled.
> >
> > How does your kernel command line look on both kernels?
> >
> > Perhaps try to supply:
> > " clk_ignore_unused pd_ignore_unused regulator_ignore_unused"
> > on the kernel command line.
> >
> > (regulator_ignore_unused requires v6.8-rc1 or newer.)
> 
> I tried v6.8-rc6 and it wouldn't boot at the time.
> 
> It seems I ran into an old issue which may have started in version 6.5:
> https://patchwork.kernel.org/project/linux-rockchip/patch/20230509153912.515218-1-vincenzopalazzodev@gmail.com/
> 
> This describes pretty much what I see.
> I understand the solution presented there isn't ideal, but as some
> major ARM distributions are using it, I assume it will do for me for
> now.
> I'll try to use the variant that goes through the device tree flag and
> see if I can get a recent kernel working.
> I'm also unsure if this mailing list is still the relevant place for
> this, as I can't readily find where I found the e-mail address
> anymore.
> Guess I was born in a different age :).
> 
> If you have any more pointers given the above or an alternative
> solution that has more merit, I'm all ears.

rk3399 should boot fine on recent kernels (not sure which kernel I used,
but surely newer than v6.8-rc1).
If it doesn't boot for you, then there is probably something wrong with
your kernel config.

If you still have issues with a recent kernel, I guess you could try the
patch that you linked to, but you could also try:
https://lore.kernel.org/linux-pci/20240330035043.1546087-1-dlemoal@kernel.org/


Kind regards,
Niklas

  reply	other threads:[~2024-04-02 18:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 18:54 ahci module throws "Internal error: synchronous external abort: 0000000096000210 [#1] SMP" Ruben Van Boxem
2024-02-26 20:41 ` Niklas Cassel
2024-04-02 18:15   ` Ruben Van Boxem
2024-04-02 18:52     ` Niklas Cassel [this message]
2025-03-02 10:34       ` Ruben Van Boxem

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=ZgxT3QqHJ6rq9nqq@ryzen \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=vanboxem.ruben@gmail.com \
    /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