From mboxrd@z Thu Jan  1 00:00:00 1970
From: Alexander Beregalov <a.beregalov@gmail.com>
Subject: Re: next-20090318: sunhme does not transmit packets
Date: Tue, 24 Mar 2009 18:50:55 +0300
Message-ID: <a4423d670903240850w223cdb74k7165ffd70cd7b357@mail.gmail.com>
References: <a4423d670903180958j4847717eh99a41534633dd314@mail.gmail.com>
	 <20090318.234451.38898787.davem@davemloft.net>
	 <a4423d670903190116p157b2ebfl69d270e0576c6d9a@mail.gmail.com>
	 <20090322.215110.261185328.davem@davemloft.net>
	 <a4423d670903240432m1a4e8e08x9c97a0947d89800a@mail.gmail.com>
	 <a4423d670903240846j252a825cy1e8a50b5ac3a11ef@mail.gmail.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <netdev-owner@vger.kernel.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        bh=MKD74E8+Nxr5mSM0CEWzkkdivPre2kO5g+YshRvD8xU=;
        b=YRxMQQ2878IgMeaPMkqdSgUSTD7zrrZagILY/Q2qgSzANTeB+E4qEaeKat1fiGNR+H
         UB4u9XI47/tgz2p/mKYPEzJtcEls2AObiXOtrk019PDZhmZku41iQGbEpgnReUCAUoAZ
         LT6S3Ezo1FQ19HfgKHvhuY+oO5j4OhohHbdrY=
In-Reply-To: <a4423d670903240846j252a825cy1e8a50b5ac3a11ef@mail.gmail.com>
Sender: netdev-owner@vger.kernel.org
List-ID: <kernel-testers.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: David Miller <davem@davemloft.net>, Roel Kluin <roel.kluin@gmail.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-next@vger.kernel.org, Kernel Testers List <kernel-testers@vger.kernel.org>

2009/3/24 Alexander Beregalov <a.beregalov@gmail.com>:
> 2009/3/24 Alexander Beregalov <a.beregalov@gmail.com>:
>>>> 2009/3/19 David Miller <davem@davemloft.net>:
>>>> > Does the current vanilla kernel work fine?
>>>>
>>>> Yes. The problem happens only with -next tree.
>>>
>>> I have one of my ultra10s up and will try to reproduce and diagnose
>>> this locally.
>>
>> Hi David
>>
>> 2.6.29 also does not work.
>>
>> The guilty patch should be between 2.6.29-rc8 and final 2.6.29
>>
>> even more narrow - 59fcbdd..v2.6.29
>>
>> I can try to bisect.
>
> e4a389a9b5c892446b5de2038bdc0cca8703c615 is first bad commit

No, it is wrong, sorry.
I will do more tests tomorrow.