SCIENTIFIC-LINUX-USERS Archives

June 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Larry Linder <[log in to unmask]>
Reply To:
Larry Linder <[log in to unmask]>
Date:
Mon, 28 Jun 2010 10:04:49 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (59 lines)
Forgot most important thing.

Kernal boot parameters

kernel /vmlinuz-2.6.18-194.3.1.el5 ro root=LABEL=/ rhgb quiet nosmp noapic 
apm=force noapic apci=off pci=noacpi

There are two that are redundant.

Thank You
Larry Linder

On Monday 28 June 2010 09:07, Alan Bartlett wrote:
> On 28 June 2010 13:52, Larry Linder <[log in to unmask]> wrote:
> > Nothing seems to prevent the Spurious Interrupt.
> > Jun 28 08:08:42 engr01 kernel: spurious APIC interrupt on CPU#0, should
> > never happen.
> > Jun 28 08:09:57 engr01 kernel: spurious APIC interrupt on CPU#0, should
> > never happen.
> > Jun 28 08:11:23 engr01 kernel: spurious APIC interrupt on CPU#0, should
> > never happen.
> > Jun 28 08:12:53 engr01 kernel: spurious APIC interrupt on CPU#0, should
> > never happen.
> > Jun 28 08:13:59 engr01 last message repeated 2 times
> > Jun 28 08:15:29 engr01 last message repeated 2 times
> > Jun 28 08:18:45 engr01 last message repeated 2 times
> > Jun 28 08:20:15 engr01 last message repeated 3 times
> > Jun 28 08:22:08 engr01 last message repeated 2 times
> > Jun 28 08:25:40 engr01 kernel: spurious APIC interrupt on CPU#0, should
> > never happen.
> > Jun 28 08:28:46 engr01 last message repeated 2 times
> > Jun 28 08:30:16 engr01 kernel: spurious APIC interrupt on CPU#0, should
> > never happen.
> > Jun 28 08:34:02 engr01 last message repeated 3 times
> > Jun 28 08:36:57 engr01 kernel: spurious APIC interrupt on CPU#0, should
> > never happen.
> > Jun 28 08:39:26 engr01 last message repeated 2 times
> >
> > There has got to be rational explanation or this is a Kernal bug.
> > The suggestions, the last change seems to slow it down but not remove the
> > problem.   It appears to happen every minute instead of every couple of
> > seconds.
> > Is there some solution to the problem?
>
> Would you clarify your kernel boot parameters, please?
>
> I would test the following four lines (and further permutations
> thereof, if required) --
>
> nosmp noapic nolapic
>
> nosmp noapic nolapic noirqbalance
>
> nosmp noapic nolapic irqpoll
>
> nosmp noapic nolapic irqfixup
>
> Alan.

ATOM RSS1 RSS2