On 10/29/2012 02:51 PM, Alexandre Pereira da Silva wrote: >> I just tried both on a PHY3250 reference machine, and on a custom board >> and couldn't reproduce sth. like this. Booted the kernel and connected >> the ethernet cable later on, as well as with cable connected on boot. > > This is happening on my custom board. I didn't try this on the > reference board yet. > >> Any related patches applied? Can you reproduce this on a reference >> machine? Can you provide a .config for this? Any more detail about how >> this could be reproduced? > > No patches applied. I'm trying to bisect this. This happens on a clean > -rc1 as well. Doesn't happen on v3.6. > > Attached my .config > > To reproduce this, I am just running "reboot". I have the ethernet > cable always connected here.
Just tried this with your .config on the PHY3250 (w/o your initrd thought) but couldn't reproduce the issue. Maybe it's related to your Micrel ethernet PHY (activated in your config) which I don't have hardware for? Otherwise, we would need to have a look at your devicetree. Roland -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
