All of lore.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Paul P Komkoff Jr <i@stingr.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Dumb question] 100k RTC interrupts/sec on SMP system: why?
Date: Thu, 4 Jan 2007 14:44:45 -0500	[thread overview]
Message-ID: <200701041444.45250.lenb@kernel.org> (raw)
In-Reply-To: <1163166183.3138.707.camel@laptopd505.fenrus.org>

On Friday 10 November 2006 08:43, Arjan van de Ven wrote:
> On Fri, 2006-11-10 at 16:35 +0300, Paul P Komkoff Jr wrote:
> > Replying to Arjan van de Ven:
> > > Also have you tried acpi=off or the linux firmware test kit (see url in
> > 
> > acpi=off fixed this.
> >   8:          1          0    IO-APIC-edge  rtc
> acpi=on had this
> 
> >  8: 3673166897 3674697116   IO-APIC-level  rtc
> 
> spot the level-vs-edge difference.... your acpi interrupt routing looks
> bust.
> 
> 
> > So I got rid of "interrupt storm" but what I've lost (except poweroff)?
> 
> you can get power off with APM as well.

Servers don't have APM.

It seems this is an additional sighting of this BIOS bug:

http://bugzilla.kernel.org/show_bug.cgi?id=7679

(perhaps you can note that in the bug report)

pnpacpi=off should be a sufficient workaround for now.

thanks,
-Len

ps. there is nothing dumb about this question:-)

      reply	other threads:[~2007-01-04 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-09 10:09 [Dumb question] 100k RTC interrupts/sec on SMP system: why? Paul P Komkoff Jr
2006-11-10  4:41 ` Andrew Morton
2006-11-10 12:35   ` Paul P Komkoff Jr
2006-11-10 13:00     ` Arjan van de Ven
2006-11-10 13:15       ` Paul P Komkoff Jr
2006-11-10 13:35       ` Paul P Komkoff Jr
2006-11-10 13:43         ` Arjan van de Ven
2007-01-04 19:44           ` Len Brown [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=200701041444.45250.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=arjan@infradead.org \
    --cc=i@stingr.net \
    --cc=linux-kernel@vger.kernel.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 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.