netdev - Re: 3.7-rc3 oops on reboot

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

Message-ID: <CAAAP30HRRnZQVhJAP19HZ_nJtn6GPeWZeEsst2pyhYZ5JM=Eow@mail.gmail.com>
Date:	Mon, 29 Oct 2012 15:41:50 -0200
From:	Alexandre Pereira da Silva <aletes.xgr@...il.com>
To:	Roland Stigge <stigge@...com.de>
Cc:	"David S. Miller" <davem@...emloft.net>,
	Alexey Kuznetsov <kuznet@....inr.ac.ru>,
	James Morris <jmorris@...ei.org>,
	Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
	Patrick McHardy <kaber@...sh.net>, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: 3.7-rc3 oops on reboot

On Mon, Oct 29, 2012 at 12:41 PM, Roland Stigge <stigge@...com.de> wrote:
> 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.

Thanks for testing. I will investigate this further to see if I can
narrow source of the problem.
--
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