2003-05-08 15:19:52

by Greg Boyce

[permalink] [raw]
Subject: Not enough ptys in 2.5.69-mm2

Kernel folks,

I've been having a problem with some of the recent 2.5 mm series kernels
that I was hoping someone might have an idea about. The current version
I'm testing is 2.5.69-mm2. I have also seen the same problem on 2.5.69
itself, although I'm not sure about a straight 2.5.68.

The problem comes when I try to open an xterm or gnome-terminal within X.
The process attempts to start, but then just hangs indefinitly. When
launching from the commandline, I see the following:

gboyce@cthulhu gboyce $ xterm
xterm: Error 32, errno 2: No such file or directory
Reason: get_pty: not enough ptys

I'm attaching an strace of xterm, and my .config file. Please let me know
if there is any other information I can provide.

Gregory Boyce


Attachments:
xterm.strace (31.48 kB)
config-2.5.69-mm2 (25.15 kB)
Download all attachments

2003-05-08 15:29:55

by Kevin P. Fleming

[permalink] [raw]
Subject: Re: Not enough ptys in 2.5.69-mm2

Greg Boyce wrote:


> gboyce@cthulhu gboyce $ xterm
> xterm: Error 32, errno 2: No such file or directory
> Reason: get_pty: not enough ptys
>

Have you mounted devpts on /dev/pts? If not, that's now mandatory after
some devfs changes that went in during 2.5.68/2.5.69 timefreame.

2003-05-08 15:56:43

by Greg Boyce

[permalink] [raw]
Subject: Re: Not enough ptys in 2.5.69-mm2

On Thu, 8 May 2003, Kevin P. Fleming wrote:

> Greg Boyce wrote:

> > gboyce@cthulhu gboyce $ xterm
> > xterm: Error 32, errno 2: No such file or directory
> > Reason: get_pty: not enough ptys
> >
>
> Have you mounted devpts on /dev/pts? If not, that's now mandatory after
> some devfs changes that went in during 2.5.68/2.5.69 timefreame.

Hm. I thought I had tried that, but apparently not. Setting /etc/fstab
to mount devpts automatically caused xterms to start properly. I am
getting a panic now that I didn't get initially though. After
commenting devpts back out and rebooting, I still got the panic, so it's
probably unrelated.

If anyone is interested, here is the panic.

------------[ cut here ]------------
kernel BUG at include/linux/list.h:140!
invalid operand: 0000 [#1]
CPU: 0
EIP: 0060:[<c011b4e4>] Not tainted VLI
EFLAGS: 00010006
EIP is at remove_wait_queue+0x64/0x70
eax: df88be74 ebx: df88a000 ecx: df88be80 edx: df905e08
esi: 00000286 edi: df88be74 ebp: df88be38 esp: df88be30
ds: 007b es: 007b ss: 0068
Process hotplug (pid: 73, threadinfo=df88a000 task=dfbe0cc0)
Stack: df905e08 df88a000 df88bea0 c01b912a c03dd6c0 c14ee918 00000000 df905e04
dff706c0 00000000 dfbe0cc0 c0119e70 00000000 00000000 c0137db9 dfa3d005
dfaac5b0 00000000 dfbe0cc0 c0119e70 df905e08 df905e08 dfa3d005 00299a31
Call Trace:
[<c01b912a>] devfs_d_revalidate_wait+0x17a/0x190
[<c0119e70>] default_wake_function+0x0/0x20
[<c0137db9>] __alloc_pages+0x329/0x390
[<c0119e70>] default_wake_function+0x0/0x20
[<c015d5ac>] do_lookup+0x5c/0xb0
[<c015daa2>] link_path_walk+0x4a2/0x900
[<c015e836>] open_namei+0x76/0x470
[<c014e111>] filp_open+0x41/0x70
[<c014e5f5>] sys_open+0x55/0x90
[<c010954b>] syscall_call+0x7/0xb

Code: 43 08 83 e0 08 75 0b 8b 1c 24 8b 74 24 04 89 ec 5d c3 8b 1c 24 8b 74 24 04 89 ec 5d e9 46 e9 ff ff 0f 0b 8d 00 b5 65 37 c0 eb ca <0f> 0b 8c 00 b5 65 37 c0 eb b8 89 f6 55 89 e5 83 ec 0c 89 1c 24
<6>note: hotplug[73] exited with preempt_count 1