linux-kernel - Re: 2.6.24-rt1 IRQ routing anomaly

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.58.0802211005380.9890@gandalf.stny.rr.com>
Date:	Thu, 21 Feb 2008 10:08:14 -0500 (EST)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Mark Hounschell <markh@...pro.net>
cc:	Mark Hounschell <dmarkh@....rr.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jon Masters <jonathan@...masters.org>
Subject: Re: 2.6.24-rt1 IRQ routing anomaly


On Thu, 21 Feb 2008, Mark Hounschell wrote:
> >
> > To prove this is the problem, boot with noapic in the kernel command line.
> > 1) the problem should disappear.
> > 2) (I'm betting) you see that the eth and EMU10K1 share the same
> >    interrupt line.
> >
>
> Yep, you were right. They do share the same IRQ and the problem does go away.
> Unfortunately  I can't run this machine with noapic. I need irq affinity.
>

Thanks for verifying. OK, I'll see if I can get the workaround on i386. I
thought I saw a patch someplace where someone ported that workaround. I'm
still sorting out bugs in -rt2 (why it is still not out). I'll see if I
can find time to get the workaround to i386 for -rt2 as well.

-- Steve

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