From: Mike Galbraith <efault@gmx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Cc: 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, 09 Sep 2020 07:45:22 +0200 [thread overview]
Message-ID: <91828ea63ecd61d40bba0358e1c0efbe62976ba6.camel@gmx.de> (raw)
In-Reply-To: <6ed14b9743f5ce400137a4ae5561604575e72b13.camel@gmx.de>
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.
KERNEL: vmlinux-5.9.0.gf4d51df-rt5-rt.gz
DUMPFILE: vmcore
CPUS: 8
DATE: Wed Sep 9 04:41:24 2020
UPTIME: 00:08:10
LOAD AVERAGE: 3.17, 1.86, 0.99
TASKS: 715
NODENAME: homer
RELEASE: 5.9.0.gf4d51df-rt5-rt
VERSION: #1 SMP PREEMPT_RT Wed Sep 9 03:22:01 CEST 2020
MACHINE: x86_64 (3591 Mhz)
MEMORY: 16 GB
PANIC: ""
PID: 2146
COMMAND: "X"
TASK: ffff994c7fad0000 [THREAD_INFO: ffff994c7fad0000]
CPU: 0
STATE: TASK_RUNNING (PANIC)
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
#9 [ffffbfffc11a79d0] nvif_mem_ctor_type at ffffffffc07eef48 [nouveau]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nvif/mem.c: 74
#10 [ffffbfffc11a7aa8] nouveau_mem_vram at ffffffffc08b5291 [nouveau]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nouveau_mem.c: 155
#11 [ffffbfffc11a7b10] nouveau_vram_manager_new at ffffffffc08b594d [nouveau]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nouveau_ttm.c: 76
#12 [ffffbfffc11a7b30] ttm_bo_mem_space at ffffffffc05af2ac [ttm]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/ttm/ttm_bo.c: 1065
#13 [ffffbfffc11a7b88] ttm_bo_validate at ffffffffc05afaca [ttm]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/ttm/ttm_bo.c: 1137
#14 [ffffbfffc11a7c18] ttm_bo_init_reserved at ffffffffc05afe70 [ttm]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/ttm/ttm_bo.c: 1330
#15 [ffffbfffc11a7c60] ttm_bo_init at ffffffffc05afff7 [ttm]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/ttm/ttm_bo.c: 1364
#16 [ffffbfffc11a7cc8] nouveau_bo_init at ffffffffc08b0f7b [nouveau]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nouveau_bo.c: 317
#17 [ffffbfffc11a7d38] nouveau_gem_new at ffffffffc08b2f7b [nouveau]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nouveau_gem.c: 206
#18 [ffffbfffc11a7d70] nouveau_gem_ioctl_new at ffffffffc08b3001 [nouveau]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nouveau_gem.c: 272
#19 [ffffbfffc11a7da0] drm_ioctl_kernel at ffffffffc066f564 [drm]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/drm_ioctl.c: 793
#20 [ffffbfffc11a7de0] drm_ioctl at ffffffffc066f88e [drm]
/backup/usr/local/src/kernel/linux-master-rt/./include/linux/uaccess.h: 168
#21 [ffffbfffc11a7ed0] nouveau_drm_ioctl at ffffffffc08abf56 [nouveau]
/backup/usr/local/src/kernel/linux-master-rt/drivers/gpu/drm/nouveau/nouveau_drm.c: 1163
#22 [ffffbfffc11a7f08] __x64_sys_ioctl at ffffffffb733255e
/backup/usr/local/src/kernel/linux-master-rt/fs/ioctl.c: 49
#23 [ffffbfffc11a7f40] do_syscall_64 at ffffffffb79a25c3
/backup/usr/local/src/kernel/linux-master-rt/arch/x86/entry/common.c: 46
#24 [ffffbfffc11a7f50] entry_SYSCALL_64_after_hwframe at ffffffffb7a0008c
/backup/usr/local/src/kernel/linux-master-rt/arch/x86/entry/entry_64.S: 125
RIP: 00007f96707a6ac7 RSP: 00007ffc1cbc2998 RFLAGS: 00000246
RAX: ffffffffffffffda RBX: 000055743cf152e0 RCX: 00007f96707a6ac7
RDX: 00007ffc1cbc29f0 RSI: 00000000c0306480 RDI: 000000000000000e
RBP: 00007ffc1cbc29f0 R8: 0000000000000000 R9: 0000000000000003
R10: fffffffffffffd98 R11: 0000000000000246 R12: 00000000c0306480
R13: 000000000000000e R14: 000055743ce99040 R15: 000055743c60cfd0
ORIG_RAX: 0000000000000010 CS: 0033 SS: 002b
next prev parent reply other threads:[~2020-09-09 5:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 15:55 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 16:17 ` Mike Galbraith
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 [this message]
2020-09-09 8:20 ` Sebastian Andrzej Siewior
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=91828ea63ecd61d40bba0358e1c0efbe62976ba6.camel@gmx.de \
--to=efault@gmx.de \
--cc=bigeasy@linutronix.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
all inboxes | Powered by JetHome®