From: Alexander Beregalov <a.beregalov@gmail.com>
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>
Subject: Re: next-20090318: sunhme does not transmit packets
Date: Tue, 24 Mar 2009 18:46:09 +0300 [thread overview]
Message-ID: <a4423d670903240846j252a825cy1e8a50b5ac3a11ef@mail.gmail.com> (raw)
In-Reply-To: <a4423d670903240432m1a4e8e08x9c97a0947d89800a@mail.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
commit e4a389a9b5c892446b5de2038bdc0cca8703c615
Author: Roel Kluin <roel.kluin@gmail.com>
Date: Wed Mar 18 23:12:13 2009 -0700
net: kfree(napi->skb) => kfree_skb
next prev parent reply other threads:[~2009-03-24 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a4423d670903180958j4847717eh99a41534633dd314@mail.gmail.com>
[not found] ` <20090318.234451.38898787.davem@davemloft.net>
[not found] ` <a4423d670903190116p157b2ebfl69d270e0576c6d9a@mail.gmail.com>
[not found] ` <20090322.215110.261185328.davem@davemloft.net>
[not found] ` <20090322.215110.261185328.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2009-03-24 11:32 ` next-20090318: sunhme does not transmit packets Alexander Beregalov
2009-03-24 15:46 ` Alexander Beregalov [this message]
2009-03-24 15:50 ` Alexander Beregalov
2009-03-24 20:23 ` David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a4423d670903240846j252a825cy1e8a50b5ac3a11ef@mail.gmail.com \
--to=a.beregalov@gmail.com \
--cc=davem@davemloft.net \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roel.kluin@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox