mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Smith <msmith@freebsd.org>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: "'Marcin Gogolewski'" <marcing@ms-itti.com.pl>,
	linux-kernel@vger.kernel.org,
	"Mike Smith (E-mail)" <msmith@freebsd.org>
Subject: Re: Oops with ACPI (in sched:566)
Date: Sat, 02 Mar 2002 14:07:46 -0800	[thread overview]
Message-ID: <200203022207.g22M7kx01385@mass.dis.org> (raw)
In-Reply-To: Your message of "Fri, 01 Mar 2002 10:49:35 PST." <59885C5E3098D511AD690002A5072D3C02AB7C9F@orsmsx111.jf.intel.com>


I haven't checked for BIOS updates for the SLT2 for a while, but in the 
code as of 6-12 months ago there is definitely a mutex deadlock.

Andrew already has all the details.

> > From: Marcin Gogolewski [mailto:marcing@ms-itti.com.pl]
> > I have STL2 machine, if I compile kernel (2.4.18) with ACPI I got:
> > [...] (I hope this is OK, I write it down from monitor ;-) )
> > ACPI: Core Subsystem version [20011018]
> > Scheduling in interrupt
> > kernel BUG at sched:566!
> 
> I've heard of problems with STL2 before, due to a poor ACPI BIOS.
> 
> If you're willing, I'd be great if you could get the ACPI pmtools
> (http://developer.intel.com/technology/iapc/acpi/downloads.htm), run
> acpidmp, and send me the output. At least then I can put the STL2 on the
> ACPI blacklist, and maybe we can figure out more about the problem, too.
> 
> Regards -- Andy

-- 
To announce that there must be no criticism of the president,
or that we are to stand by the president, right or wrong, is not
only unpatriotic and servile, but is morally treasonable to 
the American public.  - Theodore Roosevelt



  reply	other threads:[~2002-03-02 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-01 18:49 Grover, Andrew
2002-03-02 22:07 ` Michael Smith [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-01  8:39 Marcin Gogolewski

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=200203022207.g22M7kx01385@mass.dis.org \
    --to=msmith@freebsd.org \
    --cc=andrew.grover@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcing@ms-itti.com.pl \
    /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®