($INBOX_DIR/description missing)
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: benson_young@sercomm.com
Cc: meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] linux-fslc 5.4.114: rcu_preempt detected stalls on IMX7D #dunfell #meta-freescale
Date: Tue, 11 Jan 2022 09:31:11 -0300	[thread overview]
Message-ID: <CAP9ODKqpFE9cEWX6POyU5EO2_45s7UVwOSEAgBk0FbUSpvTrxQ@mail.gmail.com> (raw)
In-Reply-To: <AzJM.1641895683786982194.qQoa@lists.yoctoproject.org>

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

Hello,

Em ter., 11 de jan. de 2022 às 07:08, <benson_young@sercomm.com> escreveu:

> We are experiencing kernel crash when we are stress testing WiFi
> functionality over SDIO interface.
> please see attachment for kernel dump (near end of log)
> we have read that rcu_preempt dump are sometimes caused by spin lock used
> by driver when kernel has PREEMPT enabled.
> and suggested solution is making change as something below
> spin_unlock_irq(&signal->obj.wait.lock);   --->
> raw_spin_unlock_irq(&signal->obj.wait.lock);
> spin_lock_irq(&signal->obj.wait.lock);   ----->
> raw_spin_lock_irq(&signal->obj.wait.lock);
> however, the wireless driver on our platform doesn't use such calls.
>
> When we used the same wireless driver on official NXP BSP (gatesgarth),
> this issue isn't observed.
> Attaching the kernel configs for the two BSPs.
>
> Can anyone please advise on possible cause and solution?
>
> much appreciate the assistance and best regards,
>

You'll need to compare the branches and see if it has been fixed in a newer
kernel release.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

[-- Attachment #2: Type: text/html, Size: 1830 bytes --]

       reply	other threads:[~2022-01-11 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AzJM.1641895683786982194.qQoa@lists.yoctoproject.org>
2022-01-11 12:31 ` Otavio Salvador [this message]
2022-01-11 13:06 ` [meta-freescale] linux-fslc 5.4.114: rcu_preempt detected stalls on IMX7D #dunfell #meta-freescale Fabio Estevam
     [not found] ` <16C93929407A6CAE.24574@lists.yoctoproject.org>
2022-01-11 14:05   ` Fabio Estevam
     [not found] ` <Groupsio.1.AzJM.1641895683786982194.qQoa@lists.yoctoproject.org>
2022-01-12 12:26   ` Fabio Estevam

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=CAP9ODKqpFE9cEWX6POyU5EO2_45s7UVwOSEAgBk0FbUSpvTrxQ@mail.gmail.com \
    --to=otavio.salvador@ossystems.com.br \
    --cc=benson_young@sercomm.com \
    --cc=meta-freescale@lists.yoctoproject.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).