netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: Mark Lord <lkml@rtr.ca>, Matt Mackall <mpm@selenic.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: Using netconsole for debugging suspend/resume
Date: Mon, 12 Jun 2006 14:25:45 -0700	[thread overview]
Message-ID: <448DDBD9.6030900@goop.org> (raw)
In-Reply-To: <200606121746.34880.ak@suse.de>

Andi Kleen wrote:
> On Monday 12 June 2006 17:38, Mark Lord wrote:
>   
>> Okay, so I'm daft.  But.. *what* is "it" ??
>>
>> We have two machines:  target (being debugged), and host (anything).
>> Sure, the target has to have ohci1394 loaded, and firescope running.
>> But what about the *other* end of the connection?  What commands?
>>     
>
> From the same manpage:
> "The raw1394 module must be loaded and its device node
>  be writable (this normally requires root)" 
>
> Ok it doesn't say you need ohci1394 too and doesn't say that's the target.
> If I do a new revision I'll perhaps expand the docs a bit.
>
> So load ohci1394/raw1394 and run firescope as root. Your distribution
> will hopefully take care of the device nodes. Usually you want 
> something like firescope -Au System.map  
>   

I think the confusion here is that the target doesn't need to be running 
anything; you can DMA chunks of memory with the OHCI controller with no 
need for any software support.  The debugger host is what's running 
firescope.

Unless I'm confused too, which is likely.  Andi, I think your docs 
should be more explicit about what runs where.

Also, the tricky bit for me is debugging resume; firescope still 
requires the OHCI device to come up to be useful, but I that's no 
different from using netconsole.

Neat stuff; I need to get my two firewire-enabled machines close enough 
to each other to try it out.

    J

  reply	other threads:[~2006-06-12 21:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 17:50 Using netconsole for debugging suspend/resume Jeremy Fitzhardinge
2006-06-08 20:35 ` Auke Kok
2006-06-08 20:40 ` Rafael J. Wysocki
2006-06-09  1:56   ` Jeremy Fitzhardinge
2006-06-09 10:34     ` Rafael J. Wysocki
2006-06-08 21:07 ` Matt Mackall
2006-06-09  1:54   ` Jeremy Fitzhardinge
2006-06-09  5:13     ` Auke Kok
2006-06-09  5:23       ` David Miller
2006-06-09  5:50         ` Andi Kleen
2006-06-09 17:14           ` Matt Mackall
2006-06-09  5:45       ` Jeremy Fitzhardinge
2006-06-09  2:15   ` [PATCH RFC] netpoll: don't spin forever sending to stopped queues Jeremy Fitzhardinge
2006-06-11 20:04     ` Matt Mackall
2006-06-12 20:57       ` Jeremy Fitzhardinge
2006-06-12 20:53         ` Matt Mackall
2006-06-12 21:20           ` Jeremy Fitzhardinge
2006-06-09  3:46 ` Using netconsole for debugging suspend/resume Andi Kleen
2006-06-09 15:24   ` Mark Lord
2006-06-12 11:21     ` Andi Kleen
2006-06-12 15:38       ` Mark Lord
2006-06-12 15:46         ` Andi Kleen
2006-06-12 21:25           ` Jeremy Fitzhardinge [this message]
2006-06-13  3:47             ` Andi Kleen
2006-06-13  4:49               ` David Miller
2006-06-13  4:54                 ` Andi Kleen
2006-06-13  5:03                   ` David Miller
2006-06-13  7:18                     ` Christoph Hellwig
2006-06-13  7:31                       ` David Miller
2006-06-09  8:34 ` Pavel Machek

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=448DDBD9.6030900@goop.org \
    --to=jeremy@goop.org \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=mpm@selenic.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).