public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ed Tomlinson <edt@aei.ca>
To: linux-kernel@vger.kernel.org
Cc: Ethan Weinstein <lists@stinkfoot.org>
Subject: Re: 2.6.1 and irq balancing
Date: Sat, 10 Jan 2004 21:39:09 -0500	[thread overview]
Message-ID: <200401102139.09883.edt@aei.ca> (raw)
In-Reply-To: <40008745.4070109@stinkfoot.org>

Hi,

What is the load on the box when this is happening?  If its low think
this is optimal (for cache reasons).

Ed Tomlinson

On January 10, 2004 06:14 pm, Ethan Weinstein wrote:
> Greetings all,
> 
> I upgraded my server to 2.6.1, and I'm finding I'm saddled with only 
> interrupting on CPU0 again. 2.6.0 does this as well. This is the 
> Supermicro X5DPL-iGM-O (E7501 chipset), 2 Xeons@2.4ghz HT enabled. 
> /proc/cpuinfo is normal as per HT, displaying 4 cpus.
> 2.4.2(3|4) exhibited this behaviour as well, until I applied patches 
> from here: 
> http://www.hardrock.org/kernel/2.4.23/irqbalance-2.4.23-jb.patch, et al.
> 
> 
>             CPU0       CPU1       CPU2       CPU3
>    0:    1572323          0          0          0    IO-APIC-edge  timer
>    2:          0          0          0          0          XT-PIC  cascade
>    3:      23520          0          0          0    IO-APIC-edge  serial
>    8:          2          0          0          0    IO-APIC-edge  rtc
>    9:          0          0          0          0   IO-APIC-level  acpi
>   14:         10          0          0          0    IO-APIC-edge  ide0
>   16:         30          0          0          0   IO-APIC-level 
> sym53c8xx\r 22:       4162          0          0          0   IO-APIC-level 
> eth0 48:       7798          0          0          0   IO-APIC-level 
> aic79xx 49:       3385          0          0          0   IO-APIC-level 
> aic79xx 54:      17062          0          0          0   IO-APIC-level 
> eth1 NMI:          0          0          0          0
> LOC:    1572002    1572251    1572250    1572243
> ERR:          0
> MIS:          0
> 
> 
> THey keyboard isn't working either, but we see the i8042..
> 
> serio: i8042 KBD port at 0x60,0x64 irq 1
> 
> 
> -Ethan
> -
> 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:[~2004-01-11  2:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 23:14 2.6.1 and irq balancing Ethan Weinstein
2004-01-11  2:39 ` Ed Tomlinson [this message]
2004-01-11  3:38   ` Nick Piggin
2004-01-11  9:52     ` Arjan van de Ven
2004-01-11  5:19   ` Ethan Weinstein
2004-01-11  9:51 ` Arjan van de Ven
2004-01-11 16:50   ` Joe Korty
2004-01-11 18:19     ` Arjan van de Ven
2004-01-15 11:43     ` Pavel Machek
2004-01-11 13:14 ` Martin Schlemmer
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11 23:59 Nakajima, Jun
2004-01-12  4:42 ` Bill Davidsen
2004-01-12 14:06   ` Zwane Mwaikambo
2004-01-12 16:10   ` Martin J. Bligh
2004-01-13  6:50 ` Ethan Weinstein
2004-01-13  7:05   ` Nick Piggin
2004-01-13  7:57 Nakajima, Jun
2004-01-13  8:09 Nakajima, Jun

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=200401102139.09883.edt@aei.ca \
    --to=edt@aei.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@stinkfoot.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