DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=htXaezW6b7a2kY2LRY1l1zNPqDreGohPCwgvL2ImQLAOS1hmJFOqpnBVN3xJjK5oodG5aW8xtZmuyNj45l9zW5hSCqBdiAnywl97Arx7qmGAOzeqjs6XEamNxgjF/Q1TQM/jsGe1qyvg5ERwu+mFdvk99QOnwRWDeC7/0BxAjtE=
Message-ID: <87a5b0800803070354x391ff718u3af9664804526da1@mail.gmail.com>
Date: Fri, 7 Mar 2008 11:54:28 +0000
From: "Will Newton" <will.newton@gmail.com>
To: "Jeongdo Son" <sohn9086@gmail.com>
Subject: Re: [BUG REPORT] smc911x: Auto negotiation NOT supported
Cc: LKML <linux-kernel@vger.kernel.org>, Linux-SH <linux-sh@vger.kernel.org>
In-Reply-To: <59fd4ce80803062200n203e5cd7o152be120adbdb717@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <59fd4ce80803062200n203e5cd7o152be120adbdb717@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 913
Lines: 19

On Fri, Mar 7, 2008 at 6:00 AM, Jeongdo Son <sohn9086@gmail.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/