From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Mike Galbraith <efault@gmx.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [ANNOUNCE] v5.9-rc3-rt3
Date: Wed, 9 Sep 2020 10:20:56 +0200 [thread overview]
Message-ID: <20200909082056.sw32jevyhdm4mzcm@linutronix.de> (raw)
In-Reply-To: <91828ea63ecd61d40bba0358e1c0efbe62976ba6.camel@gmx.de>
On 2020-09-09 07:45:22 [+0200], Mike Galbraith wrote:
> On Wed, 2020-09-09 at 05:12 +0200, Mike Galbraith wrote:
> > On Wed, 2020-09-02 at 17:55 +0200, Sebastian Andrzej Siewior wrote:
> > >
> > > Known issues
> > > - It has been pointed out that due to changes to the printk code the
> > > internal buffer representation changed. This is only an issue if tools
> > > like `crash' are used to extract the printk buffer from a kernel memory
> > > image.
> >
> > Ouch. While installing -rt5 on lappy via nfs, -rt5 server box exploded
> > leaving nada in logs. I have a nifty crash dump of the event, but...
>
> After convincing crash (with club) that it didn't _really_ need a
> log_buf, nfs had nothing to do with the crash, it was nouveau.
okay. Line 280 is hard to understand. My guess is that we got a pointer
and then the boom occurred but I can't tell why/how. A few lines later
there is args->x = y…
Do you see the lockdep splat without nouveau?
> crash> bt -l
> PID: 2146 TASK: ffff994c7fad0000 CPU: 0 COMMAND: "X"
> #0 [ffffbfffc11a76c8] machine_kexec at ffffffffb7064879
> /backup/usr/local/src/kernel/linux-master-rt/./include/linux/ftrace.h: 792
> #1 [ffffbfffc11a7710] __crash_kexec at ffffffffb7173622
> /backup/usr/local/src/kernel/linux-master-rt/kernel/kexec_core.c: 963
> #2 [ffffbfffc11a77d0] crash_kexec at ffffffffb7174920
> /backup/usr/local/src/kernel/linux-master-rt/./arch/x86/include/asm/atomic.h: 41
> #3 [ffffbfffc11a77e0] oops_end at ffffffffb702716f
> /backup/usr/local/src/kernel/linux-master-rt/arch/x86/kernel/dumpstack.c: 342
> #4 [ffffbfffc11a7800] exc_general_protection at ffffffffb79a2fc6
> /backup/usr/local/src/kernel/linux-master-rt/arch/x86/kernel/traps.c: 82
> #5 [ffffbfffc11a7890] asm_exc_general_protection at ffffffffb7a00a1e
> /backup/usr/local/src/kernel/linux-master-rt/./arch/x86/include/asm/idtentry.h: 532
> #6 [ffffbfffc11a78a0] nvif_object_ctor at ffffffffc07ee6a7 [nouveau]
> /backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nvif/object.c: 280
> #7 [ffffbfffc11a7918] __kmalloc at ffffffffb72eea12
> /backup/usr/local/src/kernel/linux-master-rt/mm/slub.c: 261
> #8 [ffffbfffc11a7980] nvif_object_ctor at ffffffffc07ee6a7 [nouveau]
> /backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nvif/object.c: 280
Sebastian
next prev parent reply other threads:[~2020-09-09 8:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 15:55 [ANNOUNCE] v5.9-rc3-rt3 Sebastian Andrzej Siewior
2020-09-05 4:47 ` v5.9-rc3-rt3 boot time networking lockdep splat Mike Galbraith
2020-09-05 5:19 ` Mike Galbraith
2020-09-08 15:12 ` Sebastian Andrzej Siewior
2020-09-08 15:59 ` Mike Galbraith
2020-09-08 16:02 ` Sebastian Andrzej Siewior
2020-09-08 12:19 ` Sebastian Andrzej Siewior
2020-09-08 14:56 ` Mike Galbraith
2020-09-08 15:06 ` Sebastian Andrzej Siewior
2020-09-08 16:19 ` Mike Galbraith
2020-09-09 2:39 ` Mike Galbraith
2020-09-09 3:12 ` [ANNOUNCE] v5.9-rc3-rt3 Mike Galbraith
2020-09-09 5:07 ` Mike Galbraith
2020-09-09 5:45 ` Mike Galbraith
2020-09-09 8:20 ` Sebastian Andrzej Siewior [this message]
2020-09-09 8:56 ` Mike Galbraith
2020-09-09 8:59 ` Sebastian Andrzej Siewior
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=20200909082056.sw32jevyhdm4mzcm@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).