linux-kernel - Re: [BUG][mvebu] mvneta: cannot request irq 25 on openblocks-ax3

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

Message-ID: <CABx3TkUnOrWAdw70+2Sg=UGmp6pEWa2qM4QtY=XofJgOU5=UiA@mail.gmail.com>
Date:	Tue, 19 Mar 2013 19:11:50 -0700
From:	Ryan Press <presslab@...mail.com>
To:	linux-kernel@...r.kernel.org
Cc:	gregory.clement@...e-electrons.com
Subject: Re: [BUG][mvebu] mvneta: cannot request irq 25 on openblocks-ax3

Hi Gregory,

>On 03/19/2013 05:43 PM, Gregory CLEMENT wrote:
>> On Tue, Mar 19, 2013 at 10:12:37PM +0900, Masami Hiramatsu wrote:
>>>
>>> Here I've hit a bug on the recent kernel. As far as I know, this bug
>>> exists on 3.9-rc1 too.
>>>
>>> When I tried the latest mvebu for-next tree
>>> (git://git.infradead.org/users/jcooper/linux.git mvebu/for-next),
>>> I got below warning at bootup time and mvneta didn't work (link was never up).
>>> I ensured that "ifconfig ethX up" always caused that.
>>>
>>> Does anyone succeed to boot openblocks-ax3 recently or hit same
>>> trouble?
>
>Hi Masami,
>
>You can try this patch if you want.
>I don't have the hardware today so I didn't test it.
>If you (and also Florian and Ezequiel) can test it and if it fixed
>the bug, then I will be able send a proper email for it,

Thanks for this!  I've been trying to build 3.9-rc1 on my Mirabox, and
I had the same problem as Masami.  The patch allows mvneta to be
built-in to the kernel, but built as a module it gives the linker
error below:

ERROR: "request_percpu_irq" [drivers/net/ethernet/marvell/mvneta.ko] undefined!
ERROR: "free_percpu_irq" [drivers/net/ethernet/marvell/mvneta.ko] undefined!

Linking it into the kernel and installing allows the network
interfaces to come up, and they can receive traffic, but oddly enough
even though tcpdump shows that traffic is transmitting and the link
lights blink, the other side does not see any traffic.  I've tested
this with different computers and different link speeds to no avail.
The fact that the link lights blink when transmitting makes me think
it's not a firewall problem (and that this rootfs works with another
arm box), but I'm not sure where to look next.  Any idea?

Thanks,
Ryan
--
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/