From: Jesse Allen <the3dfxdude@hotmail.com>
To: cheuche+lkml@free.fr
Cc: linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ?
Date: Thu, 4 Dec 2003 16:05:28 -0700 [thread overview]
Message-ID: <20031204230528.GA189@tesore.local> (raw)
In-Reply-To: <20031204200208.GA4167@localnet>
On Thu, Dec 04, 2003 at 09:02:08PM +0100, cheuche+lkml@free.fr wrote:
> Hello,
>
> Along with the lockups already described here, I've noticed an
> unidentified source of interrupts on IRQ7.
...
> I wonder if people experiencing lockup problems also have these
> noise interrupts,
I just took a look at this, by setting up parport_pc, and yes I get noise.
This was my first sample with a kernel with APIC:
7: 29230 IO-APIC-edge parport0
Then I took a look again about 5 seconds later:
7: 41560 IO-APIC-edge parport0
And I looked again, and it was higher. If you take a look repeatally, you see
it increases for 2-3 seconds, then stops for 2-3, then starts increasing again
and continues like this. This is pretty much an idle system other than me
cat'ing. I'm not using the parallel port at all.
Then I looked at the irq with parport_pc setup and with a kernel with APIC all
disabled:
7: 0 XT-PIC parport0
And it is the same on repeated cat's.
These kernels are exactly the same except ones compiled with UP APIC and the
other isn't. I don't know how parport works, but seeing two different events
under this condition does seem suspicious.
> and I don't know if this has something to do with the
> lockups or if it is an independant problem.
>
I have no idea, but it is suspicious, as I get lockups and this noise with the
APIC enabled kernel.
Jesse
next prev parent reply other threads:[~2003-12-04 22:57 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 [this message]
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
2003-12-05 13:28 ` NForce2 pseudoscience stability testing (2.6.0-test11) Pat Erley
-- strict thread matches above, loose matches on Subject: below --
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=20031204230528.GA189@tesore.local \
--to=the3dfxdude@hotmail.com \
--cc=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 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.