public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Soeren Sonnenburg <kernel@nn7.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: pts/pty problem since 2.6.8-rc2
Date: Tue, 10 Aug 2004 14:38:03 +0200	[thread overview]
Message-ID: <1092141482.18080.42.camel@localhost> (raw)
In-Reply-To: <E1BuVgG-0000sc-2z@rhn.tartu-labor>

On Tue, 2004-08-10 at 14:24, Meelis Roos wrote:
> SS> Whenever I boot a kernel of the 2.6.8-* series (also -rc3) I cannot open
> SS> up any xterms in X. I first have to lsof /dev/pts and kill all the 1-5
> SS> processes listed there. Afterwards xterm etc pops up without problems.
> 
> Might be relevant: I saw similar behaviour on a sparc64 at about
> 2.6.8-rc1 time - I could use only 2 pty's. That was with a kernel with
> PREEMPT turned on. The specific kernel gave BUGs and oopses because
> PREEMPT is not finished on sparc64 and I thought that the pty problem
> was caused by broken PREEMPT. I turned PREEMPT off and haven't seen the
> problem since then (running 2.6.8-rc4 currently).

actually I don't use a PREEMPT enabled kernel... but still see this
problem (but not with 2.6.7)...

I don't have a real idea what is causing this... anyway if I kill all
processes that were listed in lsof /dev/pts the problem seems gone... 
not sure whether this is some endianess thing (powerpc here)...

clueless,
Soeren


      reply	other threads:[~2004-08-10 12:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05  7:10 pts/pty problem since 2.6.8-rc2 Soeren Sonnenburg
2004-08-10 12:24 ` Meelis Roos
2004-08-10 12:38   ` Soeren Sonnenburg [this message]

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=1092141482.18080.42.camel@localhost \
    --to=kernel@nn7.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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