All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Yimin Deng <yimin11.deng@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Oops or bad page in page_alloc.c
Date: Wed, 11 May 2022 18:18:56 +0200	[thread overview]
Message-ID: <Ynvh8Nh7hyp4tSKk@linutronix.de> (raw)
In-Reply-To: <CAAh1qtktzZQxXp_t43YhxL6FZTS58rn_xvK2Zrq33-s3=j_sGQ@mail.gmail.com>

On 2022-05-09 15:40:43 [+0800], Yimin Deng wrote:
> Hi
Hi,

> I encountered an oops in isolate_pcp_pages() and a bad page in
> get_page_from_freelist().
> 
> linux: 3.12.37-rt51  (CONFIG_PREEMPT_RT_BASE not enabled)
> arch: PowperPC (e500)
…
What you mean by CONFIG_PREEMPT_RT_BASE is not enabled? Is
CONFIG_PREEMPT_RT_FULL enabled or none of those options?

> Any suggestions will be appreciated!
> 
> [18857088.953420] Unable to handle kernel paging request for data at
> address 0x00100104
> [18857089.046143] Faulting instruction address: 0xc0075624
…
> [18857090.073578] NIP [c0075624] isolate_pcp_pages+0x84/0xc4
> [18857090.138173] LR [c0078f24] free_hot_cold_page+0x124/0x174
…

I can't even tell if I saw a report as yours earlier or not. I do
remember that I saw the "bad page state" reports earlier but I don't
remember how they went away. I know that I had two 8572DS systems and
one started to report all kind different errors (including "bad page
state") but this was due to bad RAM (probably) since the other system
never had this error despite that they had the same configuration.

Your kernel is kind of old. The latest v3.12 is v3.12.74-rt99 which
contains a few bug fixes including commit
    f1aca90802af9 ("Revert "slub: delay ctor until the object is requested"")

which is probably not what you see but a possible crash.
You could disable memory compacting and so on but as far as I remember
they could lead higher latencies in some cases, not to a crash.
You could enable list-debugging in case an entry is added/removed
multiple times.
The e500 support is quite good upstream so you could upgrade to a later
kernel (one of the current LTS kernels).

> B.R.
> Yimin

Sebastian

  reply	other threads:[~2022-05-11 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09  7:40 Oops or bad page in page_alloc.c Yimin Deng
2022-05-11 16:18 ` Sebastian Andrzej Siewior [this message]
2022-05-12  3:55   ` Yimin Deng
2022-05-12  5:52     ` Sebastian Andrzej Siewior
2022-05-11 23:19 ` Thomas Gleixner

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=Ynvh8Nh7hyp4tSKk@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=yimin11.deng@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.