lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 21 May 2007 21:08:44 +0900
From:	Komuro <komurojun-mbn@...ty.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu
Subject: Re: [SMP BUG]  [clockevents: i386 drivers patch]  introduces 
 irqbalance-does-not-work-properly problem

On Sun, 20 May 2007 15:47:04 +0200
Thomas Gleixner <tglx@...utronix.de> wrote:

> And how exactly is this related to clock events ?

Maybe, side-effects.

I will re-analyze this problem.

Thanks.


Best Regards
Komuro


> On Sun, 2007-05-20 at 19:48 +0900, Komuro wrote:
> > The problem is CPU1 receives 38239 interrupt-16
> > but CPU0 receives only 15 interrupt-16
> > CPU0 should receive more interrupts.
> > 
> >            CPU0       CPU1       
> >   0:         85          0   IO-APIC-edge      timer
> >   1:          0        698   IO-APIC-edge      i8042
> >   6:          0          5   IO-APIC-edge      floppy
> >   8:          0          1   IO-APIC-edge      rtc
> >   9:          0          0   IO-APIC-fasteoi   acpi
> >  12:          0        114   IO-APIC-edge      i8042
> >  14:        369       2281   IO-APIC-edge      ide0
> >  15:          0         24   IO-APIC-edge      ide1
> >  16:         15      38239   IO-APIC-fasteoi   yenta, pcnet_cs   <<< problem
> >  17:          0          0   IO-APIC-fasteoi   yenta
> > NMI:          0          0 
> > LOC:      50548      50547 
> > ERR:          0
> > MIS:      15503
> 
> And how exactly is this related to clock events ?
> 
> 	tglx
> 
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ