Netdev List
 help / color / mirror / Atom feed
From: "Adam Langley" <agl@imperialviolet.org>
To: "Peter Palfrader" <peter@palfrader.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.25.6: warn_on_slowpath in tcp_input.c
Date: Mon, 30 Jun 2008 16:56:13 -0700	[thread overview]
Message-ID: <396556a20806301656ydc44e3ey6deb229ab69904@mail.gmail.com> (raw)
In-Reply-To: <20080630230954.GS16698@anguilla.noreply.org>

On Mon, Jun 30, 2008 at 4:09 PM, Peter Palfrader <peter@palfrader.org> wrote:
> I've had 13 or so of them since upgrading the machine to a 2.6.25 kernel
> 20 days ago.

Which kernel was it running before?

AGL

-- 
Adam Langley agl@imperialviolet.org http://www.imperialviolet.org

  reply	other threads:[~2008-06-30 23:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 23:09 2.6.25.6: warn_on_slowpath in tcp_input.c Peter Palfrader
2008-06-30 23:56 ` Adam Langley [this message]
2008-07-01  7:38   ` Peter Palfrader
2008-07-17 15:01     ` Ilpo Järvinen
2008-07-23  9:03       ` Peter Palfrader

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=396556a20806301656ydc44e3ey6deb229ab69904@mail.gmail.com \
    --to=agl@imperialviolet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=peter@palfrader.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