From: john stultz <johnstul@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: apw@canonical.com
Subject: sshd issues with 2.6.38-rc1
Date: Thu, 20 Jan 2011 12:20:42 -0800 [thread overview]
Message-ID: <1295554842.2998.79.camel@work-vm> (raw)
Just an FYI: I'm having problems sshing to a machine I just updated to
2.6.38-rc1. The machine is running Ubuntu 10.10, and and 2.6.37 with the
same config doesn't seem to have a problem.
The box is always pingable. But when I ssh in from a client, it just
hangs before authenticating.
In the dmesg, on both kernels, I see:
sshd (1852): /proc/1852/oom_adj is deprecated, please
use /proc/1852/oom_score_adj instead.
Using ssh -vvv I get all the way to:
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: <blah blah>
With ps, I see:
root ... Ss ... sshd: [accepted]
sshd ... S ... sshd: [net]
Anyone have a clue? Otherwise I'll try bisecting it down.
thanks
-john
next reply other threads:[~2011-01-20 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 20:20 john stultz [this message]
2011-01-20 20:30 ` sshd issues with 2.6.38-rc1 Jesse Gross
2011-01-20 21:22 ` john stultz
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=1295554842.2998.79.camel@work-vm \
--to=johnstul@us.ibm.com \
--cc=apw@canonical.com \
--cc=linux-kernel@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