public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: viking <viking@flying-brick.caverock.net.nz>
To: James Simmons <jsimmons@linux-fbdev.org>
Cc: Andrew Morton <andrewm@uow.edu.au>, linux-kernel@vger.kernel.org
Subject: Won't Power down (Was: More about 2.4.3 timer problems)
Date: Wed, 18 Apr 2001 09:54:46 +1200	[thread overview]
Message-ID: <3ADCBBA3.760C71CE@flying-brick.caverock.net.nz> (raw)
In-Reply-To: <Pine.LNX.4.10.10104170922070.2330-100000@www.transvirtual.com>

James Simmons wrote:

> >Thanks, that solved my problem.  Have added it to the patch...
> >THe patch & 2.4.3 kernel seem to be working well, except that I can't get
> >PowerOff to kick in - it stops dead there, where it used to power down.
>
> Is this the case when the patch is removed as well. When does this occur
> exactly? After you load the module? Do you get any oops messages or does
> it just hang.

<comedy>
Module? What module?  I don't need no steenking module to power down.
I jest pull de plug outta de wall!
</comedy>

It has happened with both straight kernel, and patched.
Incidentally, Andrew, thanks for that patch. And thanks to
James Simmons too, for that Makefile fix.
I get (on a Mandrake 7.2+bits of 8 system) roughly:

Starting killall script [OK}
Setting hardware clock to system time  [OK]
Unmounting filesystems [OK]
The system is halted.   <===== issued by rc  script
Power Down.         <========= issued by printk

... and it stops there... instead of turning the power off like it did under
2.2.18 and earlier.
No kernel oops message.  Also, SysRq-O doesn't work - it just puts SysRq: up
on the screen.
The other SysRq functions  I've tried work - (Kill), (Sync), (reBoot).
Thanks for your continued monitoring.

--
 /|   _,.:*^*:.,   |\           Cheers from the Viking family,
| |_/'  viking@ `\_| |            including Pippin, our cat
|    flying-brick    | $FunnyMail  Bilbo   : Now far ahead the Road has gone,
 \_.caverock.net.nz_/     5.39    in LOTR  : Let others follow it who can!




       reply	other threads:[~2001-04-17 22:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10104170922070.2330-100000@www.transvirtual.com>
2001-04-17 21:54 ` viking [this message]
     [not found] <3ADCE83D.478F765B@uow.edu.au>
2001-04-18 19:30 ` Won't Power down (Was: More about 2.4.3 timer problems) Eric Gillespie

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=3ADCBBA3.760C71CE@flying-brick.caverock.net.nz \
    --to=viking@flying-brick.caverock.net.nz \
    --cc=andrewm@uow.edu.au \
    --cc=jsimmons@linux-fbdev.org \
    --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