public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jordan Breeding" <jordan.breeding@inet.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems halting/rebooting with 2.4.{5,6}-ac
Date: Thu, 05 Jul 2001 13:41:01 -0500	[thread overview]
Message-ID: <3B44B4BD.DD7F7A5B@inet.com> (raw)
In-Reply-To: <3B44AD33.26D97B4C@inet.com>

Jordan Breeding wrote:
> 
> I have a Tyan Tiger 230 SMP system running dual 1 GHz PIII processors.
> The processors are of the same lot and revision, bought on the same
> day.  Everything worked fine or some time in regard to
> halting/rebooting.  I was using ac kernels configured with ACPI.  At the
> time of the merge with the Linus stuff which included new ACPI I started
> configuring with ACPI and ACPI bus management and I could no longer halt
> the system but rebooting worked OK.  As of 2.4.5-ac24 and 2.4.6-ac1 I
> can no longer halt or reboot my system properly using no power
> management or ACPI, and APM still displays the message about being
> broken on SMP.  Has anyone seen this problem, is there a fix for it?
> Another thing I have noticed is that my /proc/cpuinfo file looks like
> this:
> 
> processor       : 0
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 8
> model name      : Pentium III (Coppermine)
> stepping        : 6
> cpu MHz         : 999.694
> cache size      : 256 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 2
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 mmx fxsr sse
> bogomips        : 1992.29
> 
> processor       : 1
> vendor_id       : GenuineIntel
> cpu family      : 6
> model           : 8
> model name      : Pentium III (Coppermine)
> stepping        : 6
> cpu MHz         : 999.694
> cache size      : 256 KB
> fdiv_bug        : no
> hlt_bug         : no
> f00f_bug        : no
> coma_bug        : no
> fpu             : yes
> fpu_exception   : yes
> cpuid level     : 3
> wp              : yes
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
> mca cmov pat pse36 mmx fxsr sse
> bogomips        : 1998.84
> 
> Notice the difference in cpuid level and bogomips values between the
> two.  These processors should be exactly the same, same lot and revision
> and everything else according to the shrink wrapped Intel retail boxes
> they came out of.  What could be casuing them to show up at different
> cpuid levels?  Thanks for any help with either issue.
> 
> Jordan Breeding

Very sorry to have not included more information, when halting or
rebooting it now stop at INIT: there are no more processes left at this
run level and never actually reboots or halts.  To get around it I
either have to hit the power/reset buton or use SysReq to reboot it. 
Thanks again for any help.

Jordan Breeding

  reply	other threads:[~2001-07-05 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-05 18:08 Problems halting/rebooting with 2.4.{5,6}-ac Jordan Breeding
2001-07-05 18:41 ` Jordan Breeding [this message]
2001-07-06 16:30   ` Jordan Breeding

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=3B44B4BD.DD7F7A5B@inet.com \
    --to=jordan.breeding@inet.com \
    --cc=ledzep37@home.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