public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Yu Luming <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: "William M. Shubert"
	<wms-GS4XM6VRHqgdnm+yROfE0A@public.gmane.org>,
	len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: Linux kernel crash in ACPI code
Date: Wed, 28 Sep 2005 15:29:15 +0800	[thread overview]
Message-ID: <200509281529.15826.luming.yu@intel.com> (raw)
In-Reply-To: <1127505777.13580.55.camel-r49W/1Cwd2cZLhczpVEeqB2eb7JE58TQ@public.gmane.org>

>
> As you can see, it crashes inside the ACPI code, apparently because a
> spinlock is being used before it is initialized. I'm not sure that the
> dump is exactly the same every time, but I have noticed that it always
> includes several "acpi_..." functions in the stack.
>
> The system is a KDS Valiant 6000 laptop, with a pentium III cpu. This
> dump is from kernel 2.6.12-1.1456_FC4, although I have seen it in at
> least two other FC4 kernels.
>
> My apologies if this bug has already been found and fixed, or if this is
> sent to the wrong email address. Let me know if you need any more
> information to help track this down.

Could you try base kernel 2.6.14-rc1 or later?

>
> PS - Len, I think we worked together at intel some years ago. Were you
> ever working in Cornell Oaks in the enterprise servers group?



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl

      parent reply	other threads:[~2005-09-28  7:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-23 20:02 Linux kernel crash in ACPI code William M. Shubert
     [not found] ` <1127505777.13580.55.camel-r49W/1Cwd2cZLhczpVEeqB2eb7JE58TQ@public.gmane.org>
2005-09-28  7:29   ` Yu Luming [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=200509281529.15826.luming.yu@intel.com \
    --to=luming.yu-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=wms-GS4XM6VRHqgdnm+yROfE0A@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