From: Greg KH <greg@kroah.com>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: Stephen Hemminger <shemminger@linux-foundation.org>,
Linux Netdev List <netdev@vger.kernel.org>,
stable@kernel.org
Subject: Re: [stable] Upgrading 2.6.21.7->2.6.22.9 kills my network (sky2): sky2 eth0: rx error, status 0x402300 length 60
Date: Fri, 28 Sep 2007 09:13:28 -0700 [thread overview]
Message-ID: <20070928161328.GB28246@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0709281304590.17152@bizon.gios.gov.pl>
On Fri, Sep 28, 2007 at 01:11:27PM +0200, Krzysztof Oledzki wrote:
>
>
> On Fri, 28 Sep 2007, Krzysztof Oledzki wrote:
>
>>
>>
>> On Fri, 28 Sep 2007, Krzysztof Oledzki wrote:
>>
>>> Hello,
>>> After upgrading my kernel from 2.6.21.7 to 2.6.22.9 my 88E8053 no longer
>>> works:
>>
>> Small update: 2.6.22.9 with sky2.c/sky2.h from 2.4.22.4 works without any
>> problems.
>
> Final update.
>
> Reverting this patch:
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.22.y.git;a=commitdiff_plain;h=8c07a8e30ba8a2e0831da4b134202598435f8358
> solved my problem.
>
> I also found this one:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff_plain;h=d6532232cd3de79c852685823a9c52f723816d0a
>
> Could it go to a next -stable ASAP, please? It seems that 2.6.22.5-2.6.22.9
> kernels have broken sky2 if used with vlans. :( Such regression in a
> -stable kernel isn't nice. :(
So should we just apply the second patch? I'll let Stephen tell us what
we should do :)
thanks,
greg k-h
next prev parent reply other threads:[~2007-09-28 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 7:59 Upgradeing 2.6.21.7->2.6.22.9 kill my network (sky2): sky2 eth0: rx error, status 0x402300 length 60 Krzysztof Oledzki
2007-09-28 9:45 ` Krzysztof Oledzki
2007-09-28 11:11 ` Upgrading 2.6.21.7->2.6.22.9 kills " Krzysztof Oledzki
2007-09-28 16:13 ` Greg KH [this message]
2007-09-28 18:36 ` [stable] " Krzysztof Oledzki
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=20070928161328.GB28246@kroah.com \
--to=greg@kroah.com \
--cc=netdev@vger.kernel.org \
--cc=olel@ans.pl \
--cc=shemminger@linux-foundation.org \
--cc=stable@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).