From: Kevin Breit <mrproper@ximian.com>
To: Chris Meadors <clubneon@hereintown.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Need fixing of a rebooting system
Date: Mon, 15 Sep 2003 16:44:10 -0400 [thread overview]
Message-ID: <3F66249A.3020308@ximian.com> (raw)
In-Reply-To: <1063653132.224.32.camel@clubneon.priv.hereintown.net>
Chris Meadors wrote:
>On Mon, 2003-09-15 at 14:27, Kevin Breit wrote:
>
>
>
>>I disabled ACPI and that didn't help. I reenabled it now and I'm
>>looking for other options to disable. But I don't know where to start.
>>Any suggestions?
>>
>>
>
>What CPU are you running on? It isn't an Opteron is it? I saw the same
>thing with the NUMA support for the AMD64.
>
>Use "make menuconfig" and have a look at all the options under the first
>few menus. Make sure your CPU and power management options look right
>for your machine. When in doubt read the help text for the option, it
>is sometimes very helpful.
>
>
>
/proc/cpuinfo says:
model name: Celeron (Coppermine)
So my configuration for the first 5 main menu items that are enabled in
makeconfig are:
* Prompt for developer and/or incomplete code/drivers
* Select only drivers expected to compile cleanly
* Select only drivers that don't need compile-time external firmware
* Support for paging of anonymous memory
* System V IPC
* BSD Process Accounting
* Sysctl support
* Subarchitecture Type (PC-compatible)
* Processor family (Pentium-II/Celeron(pre-Coppermine))
* Preemptible Kernel
* Machine Check Exception
* /dev/cpu/microcode
* /dev/cpu/*/msr
* /dev/cpu/*/cpuid
* BIOS Enhanced Disk Drive calls determine boot disk
* Power Management support
*Full ACPI Support (minus the ASUS Laptop Extras and Toshiba Laptop
Extras)
Do you see anything in that list which I should look into ditching first?
Thanks
Kevin Breit
next prev parent reply other threads:[~2003-09-15 20:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-13 23:42 Need fixing of a rebooting system Kevin Breit
2003-09-13 23:46 ` Zwane Mwaikambo
2003-09-14 11:28 ` Kevin Breit
2003-09-14 13:05 ` Zwane Mwaikambo
2003-09-14 17:48 ` Kevin Breit
2003-09-14 21:42 ` Zwane Mwaikambo
2003-09-14 23:50 ` Kevin Breit
2003-09-15 0:57 ` Zwane Mwaikambo
2003-09-15 14:56 ` Kevin Breit
2003-09-15 16:20 ` Kevin Breit
2003-09-15 16:39 ` Kevin Breit
2003-09-15 18:27 ` Kevin Breit
2003-09-15 19:12 ` Chris Meadors
2003-09-15 20:44 ` Kevin Breit [this message]
2003-09-15 22:24 ` Chris Meadors
2003-09-15 23:20 ` Kevin Breit
2003-09-16 2:47 ` Kevin Breit
2003-09-16 2:44 ` Rahul Karnik
2003-09-16 4:30 ` Zwane Mwaikambo
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=3F66249A.3020308@ximian.com \
--to=mrproper@ximian.com \
--cc=clubneon@hereintown.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