linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: gshan <gshan@alcatel-lucent.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: xmon & SCSI ATA devices
Date: Tue, 29 Dec 2009 20:37:08 +1100	[thread overview]
Message-ID: <1262079428.2173.218.camel@pasglop> (raw)
In-Reply-To: <4B33197D.9000506@alcatel-lucent.com>

On Thu, 2009-12-24 at 02:34 -0500, gshan wrote:
> Hello,
> 
> xmon and SCSI SATA device driver were installed on my system. When I invoked
> xmon explicitly for kernel debugging, there're probably pending SCSI 
> requests issued.
> So those SCSI requests complained timeout when I quited from xmon. I want to
> find a way to suspend SCSI device before invoking xmon and resume that 
> before
> quiting from xmon. Anybody knew there is a way to do this?

Well, it's non trivial. xmon is very low level and doesn't muck around
with drivers etc...

We could add hacks to avoid those timeouts or even do what you suggest
with suspending devices, but that would make entering xmon a -lot- more
fragile. The idea is that xmon relies on very little kernel services and
can be entered even when things are utterly wrong.

To be honest, I'm tempted to leave that as it is. Most of the time,
getting into xmon is a one way trip.... 

Cheers,
Ben.

> Thanks,
> Gavin
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2009-12-29  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24  7:34 xmon & SCSI ATA devices gshan
2009-12-29  9:37 ` Benjamin Herrenschmidt [this message]
2009-12-30  4:09   ` gshan
2009-12-29 21:21     ` Benjamin Herrenschmidt
2009-12-30 10:51       ` gshan

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=1262079428.2173.218.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=gshan@alcatel-lucent.com \
    --cc=linuxppc-dev@lists.ozlabs.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).