linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: cheuche+lkml@free.fr
To: linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ?
Date: Fri, 5 Dec 2003 09:16:23 +0100	[thread overview]
Message-ID: <20031205081623.GA4043@localnet> (raw)
In-Reply-To: <20031204200208.GA4167@localnet>

I've just seen something strange about IRQ7, during one test, the
interrupt counter on IRQ7 was in sync with the timer counter, and the
difference was about 21400. I rebooted to see what happens at 21.4
seconds after boot and it is more or less the time some modules get
loaded by auto-detecting hardware. But unfortunately I now cannot
reproduced it, I only get bursts of IRQ7 as initially reported.

I also noted in dmesg of 2.6.0-test that part about timer interrupt :

..TIMER: vector=0x31 pin1=2 pin2=-1
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...  failed.
...trying to set up timer as Virtual Wire IRQ... failed.
...trying to set up timer as ExtINT IRQ... works.

This is interesting because 2.4.22 and 2.4.23-pre9 shows :

..TIMER: vector=0x31 pin1=2 pin2=0
..MP-BIOS bug: 8254 timer not connected to IO-APIC
...trying to set up timer (IRQ0) through the 8259A ...
..... (found pin 0) ...works.

and then the timer is not in XT-PIC mode but IO-APIC-edge mode, and I
also noticed there is no flood of IRQ7 with these 2.4 kernels. Is it 
Related or not with the IRQ flood or the lockups I don't know.

By the way 2.4.23 shows the same thing as 2.6.0-test, timer in XT-PIC
mode and some IRQ7, but way less than 2.6.0-test.

Mathieu

  parent reply	other threads:[~2003-12-05  8:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 12:17 NForce2 pseudoscience stability testing (2.6.0-test11) b
2003-12-04 15:19 ` Craig Bradney
2003-12-04 16:32   ` Josh McKinney
2003-12-04 17:08     ` Julien Oster
2003-12-04 17:55       ` Josh McKinney
2003-12-04 20:02         ` NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ? cheuche+lkml
2003-12-04 20:48           ` Bob
2003-12-04 23:05           ` Jesse Allen
2003-12-04 23:14             ` Prakash K. Cheemplavam
2003-12-04 23:21               ` Craig Bradney
2003-12-04 23:36                 ` Prakash K. Cheemplavam
2003-12-05  5:47                 ` Bob
2003-12-05  7:01                   ` Craig Bradney
2003-12-05 12:33                   ` Prakash K. Cheemplavam
2003-12-05  8:16           ` cheuche+lkml [this message]
2003-12-05 13:28 ` NForce2 pseudoscience stability testing (2.6.0-test11) Pat Erley
2003-12-05  5:56 NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ? b

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=20031205081623.GA4043@localnet \
    --to=cheuche+lkml@free.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).