From: Andi Kleen <andi@firstfloor.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <srostedt@redhat.com>,
Bruce Duncan <bwduncan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [git pull] ftrace for v2.6.27
Date: Wed, 13 Aug 2008 21:53:41 +0200 [thread overview]
Message-ID: <873al81yka.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080813151827.GA10819@elte.hu> (Ingo Molnar's message of "Wed, 13 Aug 2008 17:18:27 +0200")
Ingo Molnar <mingo@elte.hu> writes:
>
> try latest tip/master plus an USB debug key, then enable
> CONFIG_EARLY_PRINTK_DBGP=y in your .config on the host, add the
> earlyprintk=dbgp,keep boot parameter and reboot [and disable USB for
> good measure]. On the other host you connect to via an USB cable, enable
> USB_SERIAL_DEBUG=y and use /dev/ttyUSB0 with the serial terminal app of
> your choice.
>
> that, as long as the USB ports are operational, gives a working serial
> console on just about any laptop.
Unfortunately the usb debug dongle cables are hard to get and
expensive. A more available alternative would be to use firescope if
your laptop has firewire, because firewire cables are widely
available. The kernel supports early firewire since some time too, so
it can be even used for early debugging. Another advantage is that
firescope can even get data from a dead kernel as long as the firewire
hardware is not disabled.
For details see Documentation/debugging-via-ohci1394.txt
-Andi
next prev parent reply other threads:[~2008-08-13 19:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 14:22 [git pull] ftrace for v2.6.27 Ingo Molnar
2008-08-13 1:48 ` Bruce Duncan
2008-08-13 7:19 ` Ingo Molnar
2008-08-13 15:11 ` Steven Rostedt
2008-08-13 15:18 ` Ingo Molnar
2008-08-13 19:53 ` Andi Kleen [this message]
2008-08-13 17:15 ` Steven Rostedt
2008-08-13 18:08 ` Bruce Duncan
2008-08-15 9:29 ` Ingo Molnar
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=873al81yka.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=bwduncan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=srostedt@redhat.com \
/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