From: Andreas Schwab <schwab@linux-m68k.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
LKML <linux-kernel@vger.kernel.org>,
Alexander Graf <agraf@suse.de>
Subject: Re: 3.13-rc1: eth0 hw csum failure on powerpc
Date: Sat, 30 Nov 2013 23:05:14 +0100 [thread overview]
Message-ID: <87vbz9pmud.fsf@igel.home> (raw)
In-Reply-To: <alpine.DEB.2.11.1311301314220.31521__48727.6146108799$1385846242$gmane$org@trent.utfs.org> (Christian Kujau's message of "Sat, 30 Nov 2013 13:16:34 -0800 (PST)")
Christian Kujau <lists@nerdbynature.de> writes:
> On Sat, 30 Nov 2013 at 02:11, Christian Kujau wrote:
>> On Sat, 30 Nov 2013 at 02:07, Christian Kujau wrote:
>> > while trying to upgrade from 3.12.0 to 3.13-rc1 or -rc2, the following
>> > happens early during bootup:
>> >
>> > [...]
>> > Freeing unused kernel memory: 204K (c06ea000 - c071d000)
>> > eth0: hw csum failure
>> > CPU: 0 PID: 0 Comm: swapper Not tainted 3.13.0-rc2 #1
>> > Call Trace:
>>
>> Btw, full dmesg & .config: http://nerdbynature.de/bits/3.13-rc1/
>
> Oh, this has already been reported earlier this week:
>
> https://lists.ozlabs.org/pipermail/linuxppc-dev/2013-November/113584.html
No solution yet, though, 3.13-rc2 is still broken.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-11-30 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 10:07 3.13-rc1: eth0 hw csum failure on powerpc Christian Kujau
2013-11-30 10:11 ` Christian Kujau
2013-11-30 21:16 ` Christian Kujau
[not found] ` <alpine.DEB.2.11.1311301314220.31521__48727.6146108799$1385846242$gmane$org@trent.utfs.org>
2013-11-30 22:05 ` Andreas Schwab [this message]
2013-12-15 0:40 ` 3.13-rc1: eth0 hw csum failure on powerpc (bisected) Christian Kujau
2013-12-15 3:34 ` 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=87vbz9pmud.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=agraf@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
--cc=netdev@vger.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).