All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: linux-kernel@vger.kernel.org
Cc: Bernhard Kaindl <bk@suse.de>, Andi Kleen <andi@firstfloor.org>,
	linux-usb@vger.kernel.org
Subject: debugging a modern laptop ...
Date: Wed, 23 Mar 2011 04:42:14 +0100	[thread overview]
Message-ID: <20110323034214.GC15541@MAIL.13thfloor.at> (raw)


Greetings!

I'm trying to evaluate my options on debugging a recent
laptop/notebook/table (and the Linux kernel on it of course) 
from early bootup to diagnostics when the machine has locked
up ...

normally the first thing I would do is to attach a serial
console to monitor the early bootup and have some way to
send sysrq triggers ... but here is the first problem,
the thing might not even have a serial port at all ...

most modern devices have at least one usb port, but as far
as I could figure out via google, there is no support for
console or similar over usb (serial or not) atm
(please feel free to correct me here :)

after some research, I also found a quite antique project
exploiting the ieee1394 DMA feature, called firescope and
after some issues finding the latest version of the tool and
of course getting a firewire cable, there seems to be some
kind of interaction between the monitoring system and the
device in question, but it seems that a few problems exist
and I didn't manage to get any relevant information that
way yet (please let me know if that is still maintained)

finally, ethernet and netconsole, which seems to work
reasonably well, at least for the console logging part but
requires at least a supported 'wired' ethernet interface
and a few tricks to send commands to the device ...
(but only partially suited or early bootup of course)

have I missed something? 

what about bluetooth? (usually requires USB)
what about wireless? (probably quite problematic)

maybe a new kind of debug interface is needed in the 
near future?

any ideas and real world experiences are more than
welcome ...

many thanks in advance,
Herbert


             reply	other threads:[~2011-03-23  4:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  3:42 Herbert Poetzl [this message]
2011-03-23  4:12 ` debugging a modern laptop Andi Kleen
2011-03-23 15:04 ` Alan Stern
2011-03-23 15:16   ` Mark Lord

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=20110323034214.GC15541@MAIL.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=andi@firstfloor.org \
    --cc=bk@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /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.