mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Ossevoort <justin@brains.student.utwente.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: nforce2 stability on 2.6.0-test5 and 2.6.0-test9
Date: Wed, 05 Nov 2003 06:08:16 +0100	[thread overview]
Message-ID: <3FA885C0.8030906@brains.student.utwente.nl> (raw)

Hello,

I've got an A7N8X mobo, and the same problems. 'noapic' makes the
system run much better. You also have a big interrupt count on int21.
Mine is going beserk. Top shows that almost 30% of my cpu is being
used up on hi (Hardware Interrupts I guess).
Watching /proc/interrupts reveals I get tens of thousands of
interrupts on 21 every second, disabling usb or the soundcard doesn't
help, disabling both does help. Is interrupt 21 doing something funny?

Regards,

        justin....

ross.alexander@uk.neceur.com wrote in message news:<Mh8m.BT.7@gated-at.bofh.it>...
> **** /proc/interrupts ****
> 
>            CPU0 
>   0:   77764351          XT-PIC  timer
>   1:      35127    IO-APIC-edge  i8042
>   2:          0          XT-PIC  cascade
>   8:          1    IO-APIC-edge  rtc
>   9:          0   IO-APIC-level  acpi
>  12:     146812    IO-APIC-edge  i8042
>  14:     105553    IO-APIC-edge  ide0
>  15:       1371    IO-APIC-edge  ide1
>  19:    5329271   IO-APIC-level  nvidia
>  21:   12326898   IO-APIC-level  NVidia nForce2, eth0
> NMI:          0 
> LOC:   77761842 
> ERR:          0
> MIS:          4




             reply	other threads:[~2003-11-05  5:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05  5:08 Justin Ossevoort [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05  0:38 Allen Martin
2003-11-04  9:00 ross.alexander
2003-11-03 18:36 Allen Martin
2003-10-29 19:17 Allen Martin
2003-10-30  9:11 ` ross.alexander
2003-10-30 12:46 ` really bensoo_at_soo_dot_com
2003-10-29 15:07 Denis Perchine
2003-10-29 11:57 ross.alexander
2003-10-29 14:13 ` Brad House
2003-10-29 14:35   ` ross.alexander
2003-10-29 14:52     ` Brad House

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=3FA885C0.8030906@brains.student.utwente.nl \
    --to=justin@brains.student.utwente.nl \
    --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

all inboxes | Powered by JetHome®