From: Ingo Molnar <mingo@elte.hu>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [bug] networking broke, ssh: connect to port 22: Protocol error
Date: Wed, 6 Feb 2008 14:11:29 +0100 [thread overview]
Message-ID: <20080206131129.GB9950@elte.hu> (raw)
In-Reply-To: <20080206.043246.63923682.davem@davemloft.net>
* David Miller <davem@davemloft.net> wrote:
> From: Ingo Molnar <mingo@elte.hu>
> Date: Wed, 6 Feb 2008 13:22:48 +0100
>
> > So no, it does not fix the problem. The config i sent is a rather
> > generic one, it should boot on most whitebox PCs. TCP connections
> > will fail immediately, all the time.
>
> I suspect this got added recently with how often and how thoroughly
> you test things :-)
yeah, although various other upstream breakages prevented real long
randconfig series in the past 2-3 days. I'd say it's either in this pull
from your tree:
Author: Linus Torvalds <torvalds@woody.linux-foundation.org>
Date: Tue Feb 5 10:09:07 2008 -0800
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6
* git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6: (21 commits)
or perhaps in this one:
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon Feb 4 07:43:36 2008 -0800
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6
* git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6: (77 commits)
i'll figure it out, it's totally reproducible so it should be easy to
bisect. Just wanted to know whether you had anything queued up already
for something like this.
Ingo
next prev parent reply other threads:[~2008-02-06 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 11:38 [bug] networking broke, ssh: connect to port 22: Protocol error Ingo Molnar
2008-02-06 11:42 ` David Miller
2008-02-06 12:22 ` Ingo Molnar
2008-02-06 12:32 ` David Miller
2008-02-06 13:11 ` Ingo Molnar [this message]
2008-02-06 13:35 ` [bisected] " Ingo Molnar
2008-02-06 13:55 ` Stephen Smalley
2008-02-06 15:58 ` Casey Schaufler
2008-02-07 11:44 ` Ingo Molnar
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=20080206131129.GB9950@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).