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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1344361660.27383.4.camel@sbsiddha-desk.sc.intel.com>
Date:	Tue, 07 Aug 2012 10:47:40 -0700
From:	Suresh Siddha <suresh.b.siddha@...el.com>
To:	Robert Richter <robert.richter@....com>
Cc:	Borislav Petkov <bp@...64.org>, mingo@...nel.org, hpa@...or.com,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	torvalds@...ux-foundation.org, a.p.zijlstra@...llo.nl,
	tglx@...utronix.de, linux-tip-commits@...r.kernel.org,
	"Petkov, Borislav" <borislav.petkov@....com>
Subject: Re: do_IRQ: 1.55 No irq handler for vector (irq -1)

On Tue, 2012-08-07 at 19:28 +0200, Robert Richter wrote:
> On 07.08.12 09:24:21, Suresh Siddha wrote:
> > Boris, Robert, Can you please send me the complete dmesg
> > and /proc/interrupts on a successful boot?
> 
> Sent to you in private mail.

Thanks.

> 
> What information are you looking for specifically? Maybe we can
> provide something here on the ml.

I was looking for what APIC mode and it was a PIC/IO-APIC interrupt.

So it looks like it is using logical flat mode and the interrupt was
from IO-APIC.

So most likely on your system after a successful boot, if you manually
set the affinity of one of those SATA/PATA interrupts to a specific
logical cpu say 0, I think the interrupt still get routed to other
logical cpu's. Can you confirm?

thanks,
suresh

--
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