netdev - [BUG] mvneta: mirabox ethernet only works if initialized by uboot

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

Message-ID: <CACzLR4vv4kNVVkFx46jwcmB=hk_aT_XRrvU-Mpc0ZKdEQ-c_Fg@mail.gmail.com>
Date:	Thu, 8 Aug 2013 22:31:37 -0700
From:	Ethan Tuttle <ethan@...antuttle.com>
To:	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	netdev@...r.kernel.org
Subject: [BUG] mvneta: mirabox ethernet only works if initialized by uboot

I ran into this issue after upgrading my mirabox from the old marvell
kernel to 3.11-rc4.  Although ethernet interfaces are present, and
'link up' is reported, it isn't possible to send or receive packets.
I'm using a vanilla kernel with .config from ArchLinuxARM[1].

Jochen De Smet posted a more detailed report[2] and a work-around on
the Fedora ARM list: if an interface is started using the dhcp command
in uboot, ethernet works in linux.

I reproduced the issue on -rc3 and -rc1 as well, so it isn't a recent
regression.

It should be easy to reproduce on a mirabox, even when tftping a
kernel: just try to use the other interface :).

Reporting here because I don't see any other reports to the
maintainers.  I'm happy to provide more debug output or test patches
if it will help.

Thanks,
Ethan

[1] https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-mvebu/config
[2] http://www.mail-archive.com/arm@lists.fedoraproject.org/msg05244.html
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html