Subject: Re: Unable to start X
To: Bill Studenmund <wrstuden@nas.nasa.gov>
From: fission <fission@mb.sympatico.ca>
List: port-macppc
Date: 11/12/1999 11:44:27
Wow, extremely interesting.  =)  I never knew I could do that. (or how,
for that matter).

This is what I came up with (running this as root because normal users
do not have priviledges to wskbd0/wsmouse0):

 15104 xinit    CALL  fcntl(0x3,0x4,0x4)
 15104 xinit    RET   fcntl 0
 15104 xinit    CALL  read(0x3,0x7fffe6b8,0x8)
 15104 xinit    RET   read -1 errno 35 Resource temporarily unavailable
 15104 xinit    CALL  poll(0x1846f80,0x1,0xffffffff)
 15105 Xmacppc  CALL  break(0x1a62000)
 15105 Xmacppc  RET   break 0
 15105 Xmacppc  CALL  gettimeofday(0x7fffe728,0)
 15105 Xmacppc  RET   gettimeofday 0
 15105 Xmacppc  CALL  access(0x19c1c34,0x6)
 15105 Xmacppc  NAMI  "/dev/ttyE0"
 15105 Xmacppc  RET   access 0
 15105 Xmacppc  CALL  open(0x19c1c34,0x2,0)
 15105 Xmacppc  NAMI  "/dev/ttyE0"
 15105 Xmacppc  RET   open -1 errno 6 Device not configured
 15105 Xmacppc  CALL  access(0x19c1c28,0x6)
 15105 Xmacppc  NAMI  "/dev/ttyE1"
 15105 Xmacppc  RET   access 0
 15105 Xmacppc  CALL  open(0x19c1c28,0x2,0)
 15105 Xmacppc  NAMI  "/dev/ttyE1"
 15105 Xmacppc  RET   open -1 errno 6 Device not configured
 15105 Xmacppc  CALL  access(0x19c1c1c,0x6)
 15105 Xmacppc  NAMI  "/dev/ttyE2"
 15105 Xmacppc  RET   access 0
 15105 Xmacppc  CALL  open(0x19c1c1c,0x2,0)
 15105 Xmacppc  NAMI  "/dev/ttyE2"
 15105 Xmacppc  RET   open -1 errno 6 Device not configured
 15105 Xmacppc  CALL  access(0x19c1c10,0x6)
 15105 Xmacppc  NAMI  "/dev/ttyE3"
 15105 Xmacppc  RET   access 0
 15105 Xmacppc  CALL  open(0x19c1c10,0x2,0)
 15105 Xmacppc  NAMI  "/dev/ttyE3"
 15105 Xmacppc  RET   open -1 errno 6 Device not configured
 15105 Xmacppc  CALL  access(0x19c1c04,0x6)
 15105 Xmacppc  NAMI  "/dev/ttyE4"
 15105 Xmacppc  RET   access -1 errno 2 No such file or directory
 15105 Xmacppc  CALL  access(0x19c1bf8,0x6)
 15105 Xmacppc  NAMI  "/dev/ttyE5"
 15105 Xmacppc  RET   access -1 errno 2 No such file or directory
 15105 Xmacppc  CALL  access(0x19c1bec,0x6)
 15105 Xmacppc  NAMI  "/dev/ttyE6"
 15105 Xmacppc  RET   access -1 errno 2 No such file or directory
 15105 Xmacppc  CALL  access(0x19c1be0,0x6)
 15105 Xmacppc  NAMI  "/dev/ttyE7"
 15105 Xmacppc  RET   access -1 errno 2 No such file or directory
 15105 Xmacppc  CALL  __sigaction14(0x1c,0x7fffe708,0x7fffe728)
 15105 Xmacppc  RET   __sigaction14 0
 15105 Xmacppc  CALL  write(0x2,0x7fffdff8,0x15)
 15105 Xmacppc  RET   write 21/0x15
 15105 Xmacppc  CALL  write(0x2,0x7fffe078,0x10)
 15105 Xmacppc  RET   write 16/0x10
 15105 Xmacppc  CALL  write(0x2,0x7fffdff8,0x1)
 15105 Xmacppc  RET   write 1
 15105 Xmacppc  CALL  __sigaction14(0x17,0x7fffe648,0x7fffe668)
 15105 Xmacppc  RET   __sigaction14 0
 15105 Xmacppc  CALL  exit(0x1)

I don't know what most of this means.  I assume that X is looking at
/dev/ttyE? for something or other and doesn't find it configured (which it
won't because the only terminal I have on is 'console').  I am booting
with a serial console, so...I figured it would be best just to use
'console' instead of some other terminal.

--fission

On Thu, 11 Nov 1999, Bill Studenmund wrote:

> Make sure the X server is not suid/sgid, and try:
> 
> ktrace -i -t cns startx
> 
> You need to not have the suid-ness as that'll stop the ktracing. The "-i"
> means children inherit the tracing. The "-t cns" means trace system
> _C_alls, _N_amei translations (lookups), and _S_ignals.
> 
> Then do kdump > dump_file
> 
> Then edit dump_file. It will show all the calls startx and then the X
> server made. Start from the bottom and work up. The bottom stuff will be
> error clean up. Proceed up until you find a call which generated an error.
> :-)
> 
> Take care,
> 
> Bill