All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Rick Koch <mr.rickkoch@gmail.com>
Cc: linux-block@vger.kernel.org
Subject: Re: Kernel Oops in __blk_mq_all_tag_iter() using Raxda CM5
Date: Fri, 7 Feb 2025 10:39:16 +0800	[thread overview]
Message-ID: <Z6VyVEIP-228PiPb@fedora> (raw)
In-Reply-To: <CANa58eceasto+EzkRKp+10vLfUfi_O8gkc9mtu0PR01=o7-ACQ@mail.gmail.com>

On Thu, Feb 06, 2025 at 10:29:34AM -0500, Rick Koch wrote:
> Hello linux-block,
> 
> I am seeing a kernel Oops in early booting up of a Radxa CM5 board running
> Armbian
> on a 6.12.7 kernel.
> 
> I had reported a very similar Oops back on 2024-10-11 (Oct 11, 2024)
> 
> https://lore.kernel.org/all/CANa58ee6EeT9V7Q=epoZdqYw3sLh1CZGNWqJ0UcKMp6eRfcd+Q@mail.gmail.com/T/
> 
> Which you had provided me with a patch that fixed the issue and has not
> occurred again.
> 
> Here is the current Oops I am experiencing, maybe 1 out of every 10 boots.
> It does lockup after this, requiring me to re-power/boot the board.
> 
> Starting kernel ...
> 
> [    1.582430] Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP
> [    1.582984] Modules linked in:
> [    1.583256] CPU: 6 UID: 0 PID: 46 Comm: cpuhp/6 Not tainted
> 6.12.7-edge-rockchip64 #7
> [    1.583942] Hardware name: Saturn SDR, Radxa CM5, 8inch LCD/Touch panel
> (DT)
> [    1.584557] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS
> BTYPE=--)
> [    1.585167] pc : __blk_mq_all_tag_iter+0x3c/0x274
> [    1.585584] lr : blk_mq_all_tag_iter+0x14/0x20

Can you share where '__blk_mq_all_tag_iter+0x3c' points to?

Also running kernel with KASAN enabled often provides more helpful hint.



Thanks,
Ming


       reply	other threads:[~2025-02-07  2:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CANa58eceasto+EzkRKp+10vLfUfi_O8gkc9mtu0PR01=o7-ACQ@mail.gmail.com>
2025-02-07  2:39 ` Ming Lei [this message]
2025-02-06 15:43 Kernel Oops in __blk_mq_all_tag_iter() using Raxda CM5 Rick Koch

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=Z6VyVEIP-228PiPb@fedora \
    --to=ming.lei@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mr.rickkoch@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.