mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@suse.de>, Chris Largret <largret@gmail.com>
Subject: WAS Re: 2.6.19-rc1, timebomb?, now -rc2 progress
Date: Sun, 22 Oct 2006 07:20:59 -0400	[thread overview]
Message-ID: <200610220720.59531.gene.heskett@verizon.net> (raw)
In-Reply-To: <200610212011.37914.gene.heskett@verizon.net>

On Saturday 21 October 2006 20:11, Gene Heskett wrote:
>On Saturday 21 October 2006 13:25, Andi Kleen wrote:
>>Gene Heskett <gene.heskett@verizon.net> writes:
>>> ISTR that was the second time an un-logged powerdown has been done
>>> since that kernel became the default.
>>
>>It might be overheating. During a critical overheat condition the
>>ACPI code will just power off. It should still get console messages
>>out (but nothing on disk), so if you configure serial or net console
>>you would see a message.
>>
>>And check your fans are ok.
>>
>>-Andi
>>-
>
>Thanks Andi, but heating isn't a problem that I'm aware of, I'm no longer
>running a seti client since they moved it all to BOINC & refused to set
>priorities to reasonable values.  Cpu temps are pretty steady at 120F.
>
>I tried to build and boot to 2.6.19-rc2 twice today, but each time it
> fails at the initrd read phase, saying no (mutter) or cpio magic.  And
> this is with exactly the same command line as always generating the
> initrd and then copying it to the /boot partition.  This works well for
> 2.6.18, which I just rebuilt after having discovered I'd lost the himem
> magic somehow.

Someplace along the line, either a make oldconfig screwed up, or my .config 
chain of succession my scripts use got totally fubared when I was trying 
to build 19-rc2.

After 3 more rebuilds to add stuff like emu10k1 & the RAMFS bits, -rc2 has 
now booted.  So now we wait for the other shoe to drop & see if the auto 
powerdowns persist.
[...]
>I haven't tried to setup a seriel console because both serial ports on
> this box are already busy with other things.  I could free a serial port
> if someone could tell me howto make the bulldog ups monitoring software
> from belkin use a usb port instead.  Anyone have a clue to share on that
> subject?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

      reply	other threads:[~2006-10-22 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-20  5:30 2.6.19-rc1, timebomb? Gene Heskett
2006-10-21  4:22 ` Chris Largret
2006-10-21  4:37   ` Gene Heskett
2006-10-21  5:03     ` Chris Wedgwood
2006-10-21  6:08       ` Gene Heskett
2006-10-21 15:10         ` Gene Heskett
2006-10-21 17:25     ` Andi Kleen
2006-10-22  0:11       ` Gene Heskett
2006-10-22 11:20         ` Gene Heskett [this message]

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=200610220720.59531.gene.heskett@verizon.net \
    --to=gene.heskett@verizon.net \
    --cc=ak@suse.de \
    --cc=largret@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®