From owner-acpi-jp@jp.freebsd.org  Wed Oct 18 14:07:10 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id OAA25243;
	Wed, 18 Oct 2000 14:07:10 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id OAA25236
	for <acpi-jp@jp.freebsd.org>; Wed, 18 Oct 2000 14:07:08 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1])
	by shidahara1.planet.sci.kobe-u.ac.jp (8.9.3/8.9.3) with ESMTP id OAA18327
	for <acpi-jp@jp.freebsd.org>; Wed, 18 Oct 2000 14:05:51 +0900 (JST)
	(envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp)
Message-Id: <200010180505.OAA18327@shidahara1.planet.sci.kobe-u.ac.jp>
To: acpi-jp@jp.freebsd.org
In-reply-to: Your message of "Tue, 17 Oct 2000 18:07:40 MST."
             <4148FEAAD879D311AC5700A0C969E8905DE3EF@orsmsx35.jf.intel.com>
Date: Wed, 18 Oct 2000 14:05:51 +0900
From: Takanori Watanabe <takawata@shidahara1.planet.sci.kobe-u.ac.jp>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 882
Subject: [acpi-jp 882] Re: Busy wait solution. (Re: ACPI megapatch ) 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: takawata@shidahara1.planet.sci.kobe-u.ac.jp

In message <4148FEAAD879D311AC5700A0C969E8905DE3EF@orsmsx35.jf.intel.com>, "Gro
ver, Andrew" $B$5$s$$$o$/(B:
>I don't know if it's related, but we were running into a problem like this
>on some IBM laptops because we were calling their SMI-invoking control
>methods with the Global Lock held (by accident). Linux had a problem where

Where shall we check for it? According to his ASL
http://www.jp.freebsd.org/cgi/cvsweb.cgi/ACPI/data/Dell_I7500_A11.asl?rev=1.1&cvsroot=freebsd-jp
and 29056201.pdf (PIIX4 datasheet) from intel,I think it accesses
 PIIX4 PCI configuration space and try to make DEVICE Resource J to locate 
I/O port 0x370.After that, the SMC1 region(and INDX DATA field and 
IndexField made of INDX,DATA)  seems to be enabled.

Though I don't understand what Device Resource J in PIIX4 acts.

>grabbing ANY mutex also grabbed the GL. Could it be the same issue?
>Inserting a counter on While ops seems like a big kludge to me..

But it is fatal to loop without yielding other context for kernel code.
It will cause hang up just like Win16 programming model.It may be ugly,
but I don't think it wrong.

Takanori Watanabe
<a href="http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html">
Public Key</a>
Key fingerprint =  2C 51 E2 78 2C E1 C5 2D  0F F1 20 A3 11 3A 62 2A 


