From: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
To: Craig Bradney <cbradney@zip.com.au>
Cc: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>,
Jesse Allen <the3dfxdude@hotmail.com>,
cheuche+lkml@free.fr, linux-kernel@vger.kernel.org
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ?
Date: Fri, 05 Dec 2003 00:36:19 +0100 [thread overview]
Message-ID: <3FCFC4F3.8030407@gmx.de> (raw)
In-Reply-To: <1070580108.4100.8.camel@athlonxp.bradney.info>
Craig Bradney wrote:
> Prakash,
>
> try it without preempt.. just to see. As soon as I removed it today the
> crashes went away (for 5 hours).. PC is now up for 2.5 hours and I'm
> waiting to see if it will be 5 hrs or 5 days this time around :)
Oh Ok, I did a mistake: Checking my kernel config again I noticed my
last experiment indeed was with preemp OFF, so it didn't help.
Prakash
> On Fri, 2003-12-05 at 00:14, Prakash K. Cheemplavam wrote:
>
>>Jesse Allen wrote:
>>
>>>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
>>
>>I just did an experminent with a very light kernel, nearly nothing
>>compiled inside, except apic acpi, preempt and needed stuff plus
>>scsi+libata and no ide. IRQ 7 was not present and every device had its
>>own irq. Nevertheless system locked up at second hdparm run...
>>
>>Prakash
next prev parent reply other threads:[~2003-12-04 23:36 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 [this message]
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=3FCFC4F3.8030407@gmx.de \
--to=prakashpublic@gmx.de \
--cc=cbradney@zip.com.au \
--cc=cheuche+lkml@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=the3dfxdude@hotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox