NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/44565: X works for about thirty seconds and then freezes on my MacBook1,1



The following reply was made to PR xsrc/44565; it has been noted by GNATS.

From: Taylor R Campbell <campbell+netbsd%mumble.net@localhost>
To: Martin Husemann <martin%duskware.de@localhost>
Cc: gnats-bugs%NetBSD.org@localhost
Subject: Re: kern/44565: X works for about thirty seconds and then freezes on 
my MacBook1,1
Date: Mon, 14 Feb 2011 16:31:05 +0000

    Date: Mon, 14 Feb 2011 16:24:59 +0100
    From: Martin Husemann <martin%duskware.de@localhost>
 
    Which userland did you build X against?
 
 I think I built X against 5.1_RC2 as of about eight months ago --
 either that or 5.0_STABLE as of about a year ago.  (pkg_info tells me
 that the kernel I was using was NetBSD 5.1_RC2, but I think I upgraded
 the kernel first and waited a long time to upgrade the userland.)
 
    Since you can ssh in, could you ktrace the X server an see where it
    freezes?
 
 I ktraced everything (a little tricky because the Xorg executable is
 setuid), and I don't see anything particularly out of the ordinary in
 the ktrace during the second or two after the one that xclock freezes
 at.  There is an out-of-order entry here (starred), presumably because
 Xorg and xclock executables are running on different cores:
 
   1070      1 Xorg     1297699912.019030271 CALL  select(0x7f,0x81bbbc0,0,0=
 ,0)
   1241      1 xclock   1297699912.019042214 CALL  read(3,0xbb683044,0x1000)
   ...
   1241      1 xclock   1297699913.017320137 CALL  writev(3,0xbfbfeb60,3)
   1241      1 xclock   1297699913.017341223 RET   writev 4096/0x1000
 * 1070      1 Xorg     1297699912.019036662 CSW   stop kernel
   1070      1 Xorg     1297699913.017344581 CSW   resume kernel
   1070      1 Xorg     1297699913.017350811 RET   select 1
 
 (1297699912 is the second that xclock stops at.)  However, I have no
 reason to suspect that this is indicative of a problem.  I don't see
 any ioctls or mmaps or anything like that nearby -- just a bunch of
 gettimeofday, clock_gettime, setitimer, select, poll, read/v, and
 write/v.<><>
 


Home | Main Index | Thread Index | Old Index