All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Len Brown <lenb@kernel.org>
Cc: "Zhao, Yakui" <yakui.zhao@intel.com>,
	"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
	"Lin, Ming M" <ming.m.lin@intel.com>,
	"Zhang, Rui" <rui.zhang@intel.com>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	Alexey Starikovskiy <astarikovskiy@suse.de>,
	Sitsofe Wheeler <sitsofe@yahoo.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"stable@kernel.org" <stable@kernel.org>,
	"Barnes, Jesse" <jesse.barnes@intel.com>
Subject: Re: [PATCH 2.6.28-rc6] ACPICA: don't cond_resched() when irqs_disabled()
Date: Sat, 20 Dec 2008 08:34:43 +0800	[thread overview]
Message-ID: <20081220003443.GC5928@localhost> (raw)
In-Reply-To: <alpine.LFD.2.00.0812191325020.3745@localhost.localdomain>

On Fri, Dec 19, 2008 at 08:35:41PM +0200, Len Brown wrote:
> 
> 
> 
> On Fri, 19 Dec 2008, Wu Fengguang wrote:
> 
> > On Fri, Dec 19, 2008 at 10:38:18AM +0200, Len Brown wrote:
> > > >     The issue on Fengguang's laptop is different with that on the box of
> > > > T61.  On Fengguang's laptop after evaluating one ACPI object(GPE
> > > > _L18object), the irq is disabled mystically. After some investigations
> > > > we find that it is caused by SMI(The SMI will be triggered while
> > > > evaluating the ACPI object. And this issue is also related with Video). 
> > > 
> > > Interesting.
> > > I hadn't realized you root-caused that failure.
> > > This is good to know, but the fact that SMM can
> > > leave interrupts disabled is frightening.
> > 
> > > If the BIOS SMM on that box disables interrupts when
> > > random AML is run, then it is going to run into
> > > all kinds of other problems in addition to this one...
> > 
> > Exactly. This is another warning:
> > 
> > [ 6559.754331] irq status before SMI: enable
> > [ 6559.757388] irq status after SMI: disable, value: 0xF3
> > [ 6599.816127] Corrupted low memory at ffff88000000fe08 (fe08 phys) = 01007062
> > [ 6599.816253] Corrupted low memory at ffff88000000fe10 (fe10 phys) = 7ba83066
> > [ 6599.816376] Corrupted low memory at ffff88000000fe18 (fe18 phys) = 00010062
> > [ 6599.816492] Corrupted low memory at ffff88000000fe20 (fe20 phys) = 01006062
> 
> I proposed a long term fix for this years ago.
> If it had been implemented, this insanity would not be possible.
> 
> Every time a BIOS writer uses SMM, they should be rewarded
> by having a digit severed.
> 
> This is a very simple proposal, very easy to understand.
> Further, with "10-strikes and you're out", it comprehends that
> there may be some BIOS writerse that take a while to catch on...
> 
> However, when they run out of fingers I'd draw the line
> and insist that they find a new line of work.

I'm not sure I understand your scheme.  But what if the first
10-strikes already makes system unstable?

OpRegion seeks to replace SMI, however it may take time.

  reply	other threads:[~2008-12-20  0:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26  6:35 [PATCH 2.6.28-rc6] ACPICA: don't cond_resched() when irqs_disabled() Wu Fengguang
2008-11-26 13:55 ` Wu Fengguang
2008-11-26 23:20   ` Andrew Morton
2008-12-02  2:45     ` Wu Fengguang
2008-12-19  5:22   ` Len Brown
2008-12-19  7:02     ` Zhao Yakui
2008-12-19  8:38       ` Len Brown
2008-12-19 11:01         ` Wu Fengguang
2008-12-19 18:24           ` Len Brown
2008-12-20  0:28             ` Wu Fengguang
2008-12-19 13:51         ` Wu Fengguang
2008-12-19 18:35           ` Len Brown
2008-12-20  0:34             ` Wu Fengguang [this message]
2009-01-01 19:39           ` Robert Hancock

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=20081220003443.GC5928@localhost \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=astarikovskiy@suse.de \
    --cc=jesse.barnes@intel.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=rjw@sisk.pl \
    --cc=rui.zhang@intel.com \
    --cc=shaohua.li@intel.com \
    --cc=sitsofe@yahoo.com \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=yakui.zhao@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.