linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <andrewm@uow.edu.au>
To: David Priban <david2@maincube.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: i2o & Promise SuperTrak100
Date: Wed, 28 Feb 2001 23:10:52 +0000	[thread overview]
Message-ID: <3A9D857C.CF9EF272@uow.edu.au> (raw)
In-Reply-To: <MPBBILLJAONHMANIJOPDOEFNFMAA.david2@maincube.net>

David Priban wrote:
> 
> > > Kernel panic: Aiee, killing interrupt handler !
> > > In interrupt handler - not syncing
> >
> > Run it through ksymoops and I might be able to guess what went wrong.
> >
> > In theory however i2o is a standard and all i2o works alike. In
> > practice i2o
> > is a pseudo standard and nobody seems to interpret the spec the
> > same way, the
> > implementations all tend to have bugs and the hardware sometimes does too.
> >
> Alan,
> This is what ksymoops gave me. One thing I didn't mention before:
> kernel panics when I hit Ctrl-Alt-Del after it hangs telling me this:
> 

This untested patch should fix the scheduling-in-interrupt
thing.


--- kernel/sys.c.orig	Thu Mar  1 10:06:14 2001
+++ kernel/sys.c	Thu Mar  1 10:07:43 2001
@@ -330,6 +330,12 @@
 	return 0;
 }
 
+static void deferred_cad(void *dummy)
+{
+	notifier_call_chain(&reboot_notifier_list, SYS_RESTART, NULL);
+	machine_restart(NULL);
+}
+
 /*
  * This function gets called by ctrl-alt-del - ie the keyboard interrupt.
  * As it's called within an interrupt, it may NOT sync: the only choice
@@ -337,10 +343,13 @@
  */
 void ctrl_alt_del(void)
 {
-	if (C_A_D) {
-		notifier_call_chain(&reboot_notifier_list, SYS_RESTART, NULL);
-		machine_restart(NULL);
-	} else
+	static struct tq_struct cad_tq = {
+		routine: deferred_cad,
+	};
+
+	if (C_A_D)
+		schedule_task(&cad_tq);
+	else
 		kill_proc(1, SIGINT, 1);
 }
 	
-

  reply	other threads:[~2001-02-28 23:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-27 17:14 i2o & Promise SuperTrak100 David Priban
2001-02-27 17:32 ` Alan Cox
2001-02-28 18:26   ` David Priban
2001-02-28 23:10     ` Andrew Morton [this message]
2001-03-01 20:40       ` David Priban
2001-02-28 20:11   ` David Priban
2001-02-28 23:38     ` Alan Cox
2001-03-03 17:14       ` David Woodhouse
2001-03-03 17:37         ` Alan Cox
2001-03-01  1:36   ` Jens Axboe
2001-04-09 13:07 Joao Paulo Martins
2001-04-10  7:22 ` Jens Axboe
2001-04-10 11:22   ` Alan Cox
2001-04-10 11:25     ` Jens Axboe
2001-04-10 11:59       ` Joao Paulo Martins
2001-04-10 15:19     ` Chris
2001-04-12 18:33     ` Andrew Chan
2001-04-12 19:30       ` Alan Cox

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=3A9D857C.CF9EF272@uow.edu.au \
    --to=andrewm@uow.edu.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=david2@maincube.net \
    --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 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).