From: Andi Kleen <ak@linux.intel.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"markus.t.metzger@gmail.com" <markus.t.metzger@gmail.com>,
"roland@redhat.com" <roland@redhat.com>,
"eranian@googlemail.com" <eranian@googlemail.com>,
"oleg@redhat.com" <oleg@redhat.com>,
"Villacis, Juan" <juan.villacis@intel.com>,
"ak@linux.jf.intel.com" <ak@linux.jf.intel.com>
Subject: Re: [patch] x86, bts: use atomic memory allocation
Date: Fri, 20 Mar 2009 09:37:35 +0100 [thread overview]
Message-ID: <49C355CF.1040409@linux.intel.com> (raw)
In-Reply-To: <928CFBE8E7CB0040959E56B4EA41A77E923FFCA4@irsmsx504.ger.corp.intel.com>
>
> When I boot that configuration (without the additional patches), I get some
> error dumps on the screen including a call trace. Unfortunately, the interesting
> part scrolls out of the top of my screen and the boot stops.
Standard ways to handle that:
- boot with vga=0x0f07 to get smaller fonts (if it doesn't work use vga=ask and select suitable number)
- use a serial console, possibly with earlyprintk
- use firescope if the system has a ieee1394 connection. That can access the log buffer. You
need a 1394 cable, but those are easy to get. See Documentation/debugging-via-ohci1394.txt
For this particular case it might be enough to move the selftest to run much later
and then use netconsole or similar after it has been set up.
-Andi
next prev parent reply other threads:[~2009-03-20 8:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 18:27 [patch] x86, bts: use atomic memory allocation Markus Metzger
2009-03-19 16:11 ` Ingo Molnar
2009-03-20 8:07 ` Metzger, Markus T
2009-03-20 8:37 ` Andi Kleen [this message]
2009-03-20 16:23 ` Metzger, Markus T
2009-03-20 18:55 ` Ingo Molnar
2009-03-20 18:59 ` Markus Metzger
2009-03-25 9:07 ` Metzger, Markus T
2009-05-07 9:21 ` [tip:tracing/core] " tip-bot for Markus Metzger
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=49C355CF.1040409@linux.intel.com \
--to=ak@linux.intel.com \
--cc=ak@linux.jf.intel.com \
--cc=eranian@googlemail.com \
--cc=hpa@zytor.com \
--cc=juan.villacis@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=roland@redhat.com \
--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 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.