linux-kernel - Re: [BUG REPORT] smc911x: Auto negotiation NOT supported

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

Message-ID: <87a5b0800803070354x391ff718u3af9664804526da1@mail.gmail.com>
Date:	Fri, 7 Mar 2008 11:54:28 +0000
From:	"Will Newton" <will.newton@...il.com>
To:	"Jeongdo Son" <sohn9086@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linux-SH <linux-sh@...r.kernel.org>
Subject: Re: [BUG REPORT] smc911x: Auto negotiation NOT supported

On Fri, Mar 7, 2008 at 6:00 AM, Jeongdo Son <sohn9086@...il.com> wrote:

>  The problem is that only the first ifup after cold boot succeed.
>  Here is the instruction how to reproduce the symptom.
>  (smc911x is recognized as eth0 on the board.)
>  1. boot up the board, and login.
>  2. ifup eth0  (after doing this, ping works)
>  3. ifdown eth0
>  4. ifup eth0 ("Auto negotiation NOT supported" printed, and ping doesn't works)
>  Please refer to the bottom of this mail.

Are you getting interrupts from the chip? Sounds like it could be you
have missed and interrupt somewhere - check where your interrupt
polarities and where you are acking/clearing them down.
--
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/