linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Craig Bradney <cbradney@zip.com.au>
To: Bob <recbo@nishanet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: NForce2 pseudoscience stability testing (2.6.0-test11) - IRQ flood related ?
Date: Fri, 05 Dec 2003 08:01:44 +0100	[thread overview]
Message-ID: <1070607704.4100.11.camel@athlonxp.bradney.info> (raw)
In-Reply-To: <3FD01BE0.5030807@nishanet.com>

nforce net is off. 3com is on. (in bios)

Craig

On Fri, 2003-12-05 at 06:47, Bob wrote:
> Do you have onboard ethernet enabled with nforce2
> mboard? I am fine with pre-emptive kernel but have
> to disable onboard ethernet in cmos setup or I see
> "Disabling IRQ7" and problems develop.
> 
> -Bob
> 
> 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 :)
> >
> >Craig
> >
> >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
> >>
> >>-
> >>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >>the body of a message to majordomo@vger.kernel.org
> >>More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >>Please read the FAQ at  http://www.tux.org/lkml/
> >>
> >>    
> >>
> >
> >-
> >To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >Please read the FAQ at  http://www.tux.org/lkml/
> >
> >  
> >
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2003-12-05  7:01 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 [this message]
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
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=1070607704.4100.11.camel@athlonxp.bradney.info \
    --to=cbradney@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=recbo@nishanet.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;
as well as URLs for NNTP newsgroup(s).