From: Mike Fedyk <mfedyk@matchmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Remotely rebooting a machine with state 'D' processes, how?
Date: Fri, 10 Aug 2001 17:04:07 -0700 [thread overview]
Message-ID: <20010810170407.G28914@mikef-linux.matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0108101557180.1048-100000@penguin.transmeta.com> <20010811095051.A28624@gondor.apana.org.au>
In-Reply-To: <20010811095051.A28624@gondor.apana.org.au>
On Sat, Aug 11, 2001 at 09:50:51AM +1000, Herbert Xu wrote:
> On Fri, Aug 10, 2001 at 03:58:02PM -0700, Linus Torvalds wrote:
> >
> > Besides, does the reboot system call actually get the BKL? I don't think
> > it should need it..
>
> Actually, the machine in question turned out to be UP :)
>
> However, it does have RAID 1 and the notifier call chain stuff looks like
> a killer to me since it leads to do_md_stop.
>
> Perhaps we need a RESTART3 that restarts without notifying?
Interesting...
I have an oldworld ppc mac with RAID1 compiled on 2.2.19, and a bad floppy
made badblocks unkillable.
Is there another way to kill that will work when kill -9 won't?
next prev parent reply other threads:[~2001-08-11 0:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-10 21:19 Remotely rebooting a machine with state 'D' processes, how? Axel Thimm
2001-08-10 21:57 ` Brian
2001-08-10 21:59 ` Linus Torvalds
2001-08-10 22:50 ` Herbert Xu
2001-08-10 22:55 ` Andi Kleen
2001-08-10 23:05 ` Herbert Xu
2001-08-10 22:57 ` Robert Love
2001-08-10 22:58 ` Linus Torvalds
2001-08-10 23:50 ` Herbert Xu
2001-08-11 0:04 ` Mike Fedyk [this message]
2001-08-19 4:02 ` Troy Benjegerdes
2001-08-11 0:06 ` Chris Abbey
2001-08-10 22:58 ` Chris Wedgwood
2001-08-11 7:26 ` Axel Thimm
2001-08-11 11:28 ` Kai Henningsen
-- strict thread matches above, loose matches on Subject: below --
2001-08-10 23:25 Ricardo Galli
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=20010810170407.G28914@mikef-linux.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=linux-kernel@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.