public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Won't Power down (Was: More about 2.4.3 timer problems)
       [not found] <Pine.LNX.4.10.10104170922070.2330-100000@www.transvirtual.com>
@ 2001-04-17 21:54 ` viking
  0 siblings, 0 replies; 2+ messages in thread
From: viking @ 2001-04-17 21:54 UTC (permalink / raw)
  To: James Simmons; +Cc: Andrew Morton, linux-kernel

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!




^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Won't Power down (Was: More about 2.4.3 timer problems)
       [not found] <3ADCE83D.478F765B@uow.edu.au>
@ 2001-04-18 19:30 ` Eric Gillespie
  0 siblings, 0 replies; 2+ messages in thread
From: Eric Gillespie @ 2001-04-18 19:30 UTC (permalink / raw)
  To: Andrew Morton; +Cc: linux-kernel

On Tue, 17 Apr 2001, Andrew Morton wrote:

:viking wrote:
:> 
:> Incidentally, Andrew, thanks for that patch.
:
:My brain is fading.  Which patch was that?

Gee! 8-) and you suggested it to me!  It was the patch against 2.4.3-pre6
which corrected the system clock slowing down, due to the interrupts being
disabled for too long in framebuffer mode.  Well, it worked! I'm using it now,
and as I mentioned in the past email, my only trouble now is the non-powering
down of the machine.

Ah well, again, thanks for monitoring.And here's a few lines to add to that
patch too...your patch had neglected to turn on printk for all modules, and
when I compiled my kernel, that was fine, but my modules couldn't see
printk()!

--- linux-2.4.3-pre6/kernel/Makefile Sun Apr 15 20:00:00 2001
+++ lk/kernel/Makefile Sun Apr 15 21:00:00 2001
@@ -12,1 +12,1 @@

- export-objs = signal.o sys.o kmod.o context.o ksyms.o pm.o
+ export-objs = signal.o sys.o kmod.o context.o ksyms.o pm.o printk.o

Thanks again.

-- 
 /|   _,.:*^*:.,   |\           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!


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-04-18 20:17 UTC | newest]

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox