From: "David S. Miller" <davem@redhat.com>
To: paulus@au1.ibm.com
Cc: alan@lxorguk.ukuu.org.uk, jamagallon@able.es, r.post@sara.nl,
morten.helgesen@nextframe.net, linux-kernel@vger.kernel.org
Subject: Re: writing OOPS/panic info to nvram?
Date: Wed, 04 Sep 2002 16:48:08 -0700 (PDT) [thread overview]
Message-ID: <20020904.164808.00001963.davem@redhat.com> (raw)
In-Reply-To: <15734.39068.766611.169333@argo.ozlabs.ibm.com>
From: Paul Mackerras <paulus@au1.ibm.com>
Date: Thu, 5 Sep 2002 09:34:52 +1000 (EST)
I believe SCSI defeated him. :)
If you can get at the interrupt handler, and the interrupt handler is
coded well enough to handle sharing interrupts (%99 of PCI scsi
drivers are) then it is doable. Just submit it as normal through
scsi, mark it high priority somehow, and then keep calling the
interrupt handler in a loop until your command completes or fails :-)
next prev parent reply other threads:[~2002-09-04 23:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 11:50 writing OOPS/panic info to nvram? Roy Sigurd Karlsbakk
2002-09-04 12:02 ` Morten Helgesen
2002-09-04 12:21 ` Alan Cox
2002-09-04 12:31 ` Morten Helgesen
2002-09-04 12:49 ` Alan Cox
2002-09-04 12:54 ` Morten Helgesen
2002-09-04 14:02 ` Remco Post
2002-09-04 14:08 ` J.A. Magallon
2002-09-04 14:23 ` Remco Post
2002-09-06 10:06 ` Pavel Machek
2002-09-10 14:55 ` Remco Post
2002-09-13 17:03 ` Pavel Machek
2002-09-04 14:25 ` Alan Cox
2002-09-04 14:41 ` J.A. Magallon
2002-09-04 14:49 ` Lars Marowsky-Bree
2002-09-06 10:09 ` Pavel Machek
2002-09-04 23:34 ` Paul Mackerras
2002-09-04 23:48 ` David S. Miller [this message]
2002-09-05 0:07 ` Alan Cox
2002-09-06 6:48 ` Rusty Russell
2002-09-05 10:38 ` Suparna Bhattacharya
-- strict thread matches above, loose matches on Subject: below --
2005-01-24 15:18 Christoph Stueckjuergen
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=20020904.164808.00001963.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=morten.helgesen@nextframe.net \
--cc=paulus@au1.ibm.com \
--cc=r.post@sara.nl \
/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.