From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, tglx@tglx.de
Subject: Re: [PATCH] x86: print DMI information in the oops trace
Date: Wed, 17 Sep 2008 11:13:17 -0700 [thread overview]
Message-ID: <48D148BD.5020302@goop.org> (raw)
In-Reply-To: <20080916112730.0b57689d@infradead.org>
Arjan van de Ven wrote:
> From: Arjan van de Ven <arjan@linux.intel.com>
> Subject: [PATCH] x86: print DMI information in the oops trace
>
> in order to diagnose hard system specific issues, it's useful to
> have the system name in the oops (as provided by DMI)
>
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
> ---
> arch/x86/kernel/process_32.c | 10 ++++++++--
>
Not on 64-bit too?
J
> 1 files changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/process_32.c b/arch/x86/kernel/process_32.c
> index 4eb2159..d9f34cf 100644
> --- a/arch/x86/kernel/process_32.c
> +++ b/arch/x86/kernel/process_32.c
> @@ -37,6 +37,7 @@
> #include <linux/tick.h>
> #include <linux/percpu.h>
> #include <linux/prctl.h>
> +#include <linux/dmi.h>
>
> #include <asm/uaccess.h>
> #include <asm/pgtable.h>
> @@ -127,6 +128,7 @@ void __show_regs(struct pt_regs *regs, int all)
> unsigned long d0, d1, d2, d3, d6, d7;
> unsigned long sp;
> unsigned short ss, gs;
> + const char *board;
>
> if (user_mode_vm(regs)) {
> sp = regs->sp;
> @@ -139,11 +141,15 @@ void __show_regs(struct pt_regs *regs, int all)
> }
>
> printk("\n");
> - printk("Pid: %d, comm: %s %s (%s %.*s)\n",
> +
> + board = dmi_get_system_info(DMI_PRODUCT_NAME);
> + if (!board)
> + board = "";
> + printk("Pid: %d, comm: %s %s (%s %.*s) %s\n",
> task_pid_nr(current), current->comm,
> print_tainted(), init_utsname()->release,
> (int)strcspn(init_utsname()->version, " "),
> - init_utsname()->version);
> + init_utsname()->version, board);
>
> printk("EIP: %04x:[<%08lx>] EFLAGS: %08lx CPU: %d\n",
> (u16)regs->cs, regs->ip, regs->flags,
>
prev parent reply other threads:[~2008-09-17 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 18:27 [PATCH] x86: print DMI information in the oops trace Arjan van de Ven
2008-09-17 9:53 ` Ingo Molnar
2008-09-17 18:13 ` Jeremy Fitzhardinge [this message]
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=48D148BD.5020302@goop.org \
--to=jeremy@goop.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@tglx.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 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.