Bug#673107: marked as done (kirkwood: TCP checksum errors when using MTU 9000)
Your message dated Thu, 27 Jun 2013 19:44:39 +0200
with message-id <20130627174439.GH4252@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #673107,
regarding kirkwood: TCP checksum errors when using MTU 9000
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
673107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673107
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: kirkwood: TCP checksum errors when using MTU 9000
- From: Martin Michlmayr <tbm@cyrius.com>
- Date: Wed, 16 May 2012 08:53:39 +0100
- Message-id: <20120516075339.GA28693@jirafa.cyrius.com>
Package: linux-2.6
Version: 2.6.32-45
A user on the Kirkwood platform reported TCP checksum errors when
using MTU 9000:
http://forum.qnap.com/viewtopic.php?f=147&t=59281&p=266527#p266527
This has been previously discussed:
http://lists.debian.org/debian-arm/2009/11/msg00087.html
iirc a patch went into the kernel to set the limits for the various
platforms (orion, kirkwood)... or maybe it was just discussed and
never went in.
Arnaud, can you investigate whether this patch really went in or
what's going on here?
--
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz
--- End Message ---
Reply to: