From: Geert Uytterhoeven <geert@linux-m68k.org>
To: linux-sh@vger.kernel.org
Subject: Re: Boot-time warning?
Date: Wed, 06 Feb 2019 07:48:50 +0000 [thread overview]
Message-ID: <CAMuHMdUeB7ihj_CTEWoK61dcn=T-8WyudO=r-GP=ojDGqJkpvw@mail.gmail.com> (raw)
Hi Rob,
On Thu, Jan 31, 2019 at 7:42 AM Rob Landley <rob@landley.net> wrote:
> Is this still the same problem we had a couple releases back, or is it a new
> one? (From today's git, but it's been around for a while...)
>
> WARNING: CPU: 0 PID: 1 at mm/slub.c:2443 ___slab_alloc.constprop.34+0x196/0x288
>
> CPU: 0 PID: 1 Comm: swapper Not tainted 4.20.0 #1
> PC is at ___slab_alloc.constprop.34+0x196/0x288
> PR is at __slab_alloc.constprop.33+0x2a/0x4c
> PC : 8c09d9f6 SP : 8f829ea0 SR : 400080f0
> TEA : c0001240
> R0 : 8c09d860 R1 : 8c01cbec R2 : 00000000 R3 : 00000000
> R4 : 8f8020a0 R5 : 006080c0 R6 : 8c01d74e R7 : 8fff5180
> R8 : 8c011a40 R9 : 8fff5180 R10 : 8f8020a0 R11 : 00008000
> R12 : 8c01d74e R13 : 006080c0 R14 : 8f80211c
> MACH: 00000080 MACL: 0ae4849d GBR : 00000000 PR : 8c09db12
>
> Call trace:
> [<(ptrval)>] arch_local_irq_restore+0x0/0x24
> [<(ptrval)>] unmask_irq.part.4+0x14/0x2c
> [<(ptrval)>] irq_exit+0x6a/0xc0
Yes, I believe it's still the same.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2019-02-06 7:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 7:48 Geert Uytterhoeven [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-01-31 6:42 Boot-time warning? Rob Landley
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='CAMuHMdUeB7ihj_CTEWoK61dcn=T-8WyudO=r-GP=ojDGqJkpvw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=linux-sh@vger.kernel.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 NNTP newsgroup(s).