This is the mail archive of the cygwin-xfree mailing list for the Cygwin XFree86 project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: XWin too slow to start


Stephen More wrote:
On 8/13/07, Larry Hall (Cygwin X) <reply-to-list-only-lh-x <AT> cygwin <DOT> com> wrote:
                                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.


Stephen More wrote:
What is causing XWin to startup so slow ?

Good question. What did you change recently?

Like all users would say....I did not change a thing. ( Could it have been an automatic update for XP ? ) I even re-installed cygwin from scratch to debug this issue.


As I mentioned, the X stuff hasn't changed in years (as there is no
maintainer - you want to be it?) so I would expect much help here.
As for whether the auto update of XP could have an effect, the answer
is of course!




My WAG is that you've changed some network/firewall settings that are
slowing down the X server startup.

What type of network traffic is the X server trying ? Is it trying to do DNS lookups ? Is it trying to connect to a website ?


X uses TCP by default for it's connections.  6000 is the common default
port.  You can change and/or disable that of course if you want (see
the X server documentation).


After a "strace -o /tmp/strace XWin"  followed by sort -n /tmp/strace
I see 2 large pauses:

   21   20702 [sig] XWin 972 wait_sig: signalling pack.wakeup 0x6E8
   43   20745 [main] XWin 972 sig_send: returning 0x0 from sending signal -34
   44   20789 [main] XWin 972 writev: writev (3, 0x22C780, 1)
   32   20821 [main] XWin 972 fhandler_base::write: binary write
   34   20855 [main] XWin 972 writev: 34 = write (3, 0x22C780, 1), errno 2
20775776 20796631 [main] XWin 972 sig_send: sendsig 0x6E4, pid 972,
signal -34, its_me 1
   57 20796688 [main] XWin 972 sig_send: wakeup 0x6D8
  108 20796796 [main] XWin 972 sig_send: Waiting for pack.wakeup 0x6D8
   28 20796824 [sig] XWin 972 wait_sig: signalling pack.wakeup 0x6D8


29 235 [main] XWin 2844 set_myself: myself->dwProcessId 2844 58 293 [main] XWin 2844 child_copy: dll data - hp 0x5AC low 0x61100000, high 0x61104BA0, res 1 24014688 24014981 [main] XWin 2844 child_copy: dll bss - hp 0x5AC low 0x6113F000, high 0x611483D0, res 1 272 24015253 [main] XWin 2844 child_copy: user heap - hp 0x5AC low 0x100F0000, high 0x10130000, res 1 28 24015281 [main] XWin 2844 child_copy: done 574 24015855 [main] XWin 2844 child_copy: data - hp 0x5AC low 0x733000, high 0x77EDD0, res 1 298 24016153 [main] XWin 2844 child_copy: bss - hp 0x5AC low 0x7D9000, high 0x80B3F0, res 1 29 24016182 [main] XWin 2844 child_copy: done


Does this info help at all ?


Not really no.  However, if you had not changed any Cygwin piece prior to
noticing the problem, I think it's safe to assume that the delay is
introduced by some external change, which is why I mentioned network and
firewall possibilities.  Depending on your source for A/V software, this
is a possible culprit too.


-- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 429-6305 - FAX Holliston, MA 01746

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]