public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: tomepperly-Wuw85uim5zDR7s880joybQ@public.gmane.org
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: RE: PROBLEM: CPU lockup during halt for Shuttle SB61G2 p4 with hyperthreading 2.4.24
Date: Tue, 03 Feb 2004 16:09:19 +0000	[thread overview]
Message-ID: <020320041609.13086.5cb9@comcast.net> (raw)

I've never had this trouble when using a non-SMP kernel. I ran with a non-SMP kernel for around 3 weeks before starting to explore hyperthreading.

I will submit the issue to bugzilla.

Tom
> > I saw there is a separate list for ACPI issues, and based on the
> > traceback, I thought this might be an ACPI issue. Please Cc me on
> > replies if there are any.
> 
> How about UP kernel ?
> 
> > 
> > Here is another oops. This one doesn't have the nvidia module loaded.
> > The hardware is identical to my original post.
> > 
> 
> Would you please file this info on bugzilla.kernel.org in PM/ACPI
> component.
> 
> --Luming
> 


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

             reply	other threads:[~2004-02-03 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-03 16:09 tomepperly-Wuw85uim5zDR7s880joybQ [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-03  8:47 PROBLEM: CPU lockup during halt for Shuttle SB61G2 p4 with hyperthreading 2.4.24 Yu, Luming
2004-01-31  5:36 Tom Epperly

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=020320041609.13086.5cb9@comcast.net \
    --to=tomepperly-wuw85uim5zdr7s880joybq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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