Re: [foxboro] E-box very slow to start X & Openwin
- From: <duc.do@xxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 31 Aug 2011 17:32:21 -0400
I love this list!
Today I have an AW-51 exhibits the same slow boot-up symptoms (it hung at
"Default Letterbugs" or some such echo, before the crosshatched blue screen),
but mine is a D-box. It eventually got to display the DM after I gave up
waiting and went to lunch.
Nonetheless, I sorta remember there was something along this line at some point
in the recent past, so a quick perusal of my foxboro folder led me to this
thread, and I renamed /etc/X0.hosts and /etc/X1.hosts to X0.hosts.saved and
X1.hosts.saved, respectively. And poof, the box booted up and proceeded to
display the DM at normal speed as it should.
Like Kevin, I would like to know what role these files play in the boot-up
sequence and why their presence hangs the boot. Even curiouser, my files have
time/date stamp of Jul 13, 2007. We've booted this box multiple times since
then, I am certain, without seeing this hang-up.
Duc
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Kevin Fitzgerrell
Sent: Wednesday, May 11, 2011 5:13 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] E-box very slow to start X & Openwin
Removing these files did allow the WP to boot normally. Now I just need to
understand why...
Cheers,
Kevin
On Wed, May 11, 2011 at 9:44 AM, Kevin Fitzgerrell <fitzgerrell@xxxxxxxxx>
wrote:
> Scott,
> We do have the /etc/X0.hosts and /etc/X1.hosts files from mkhosts.sh.
> I see CAR 1009006 that looks similar and supports removing these files, but
> I also see the knowledgebase document SOL482 which notes these are necessary
> in a mixed system for the node to communicate properly to the mesh via the
> ATS.
> Any thoughts?
> Regards,
> Kevin
> On Tue, May 10, 2011 at 9:21 PM, Landry, Scott <Scott.Landry@xxxxxxxxxxxx>
> wrote:
>
>>
>>
>> Kevin,
>>
>>
>> X0 stands out from your truss output, Did you do a recent commit on
>> this box ?
>> Did you run the /usr/fox/bin/mkhosts.sh afterwards ?
>>
>> On some Unix boxes the commit process/running of mkhosts.sh makes a
>> couple of files that need to be deleted, namely /etc/X0.hosts and
>> /etc/X1.hosts , look for these and delete them and do the reboot again.
>>
>>
>> Regards,
>>
>>
>> Scott
>>
>> ________________________________________
>> From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On
>> Behalf Of Terry Doucet [doucet427@xxxxxxxxxxx]
>> Sent: Tuesday, May 10, 2011 6:30 AM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] E-box very slow to start X & Openwin
>>
>> Wow, an hour and 45 minutes - you're very patient! I think I have been in
>> that situation before but never waited that length of time. Its been a while
>> since that happened but I think that I restored from backup or Day0'ed the
>> box and never really tried to find out the specific problem.
>>
>> Have you tried deleting the /dev/fb* and then doing a boot -r to
>> reconfigure the two screen devices? Does the RAM show the correct value?
>> Have you tried re-seating the RAM?
>>
>> "Followed shortly by the DM's" probably means that it is not a DM or OM
>> problem.
>>
>> Terry
>>
>>
>> > Date: Tue, 10 May 2011 11:40:15 +0900
>> > Subject: [foxboro] E-box very slow to start X & Openwin
>> > From: fitzgerrell@xxxxxxxxx
>> > To: foxboro@xxxxxxxxxxxxx
>> >
>> > Hi all,
>> > I've got a WP, an E box with dual monitors at IA 6.5.6 that seems to take
>> > an
>> > extraordinary amount of time to boot.
>> > Everything goes normally until it gets to the X and Openwin start. Then I
>> > wait for about an hour and 45 minutes before I get the blue Openwin
>> > screens,
>> > followed shortly by my display managers.
>> >
>> > Anyone got any ideas?
>> >
>> > While waiting, I see openwin stuff as follows:
>> >
>> > WP003B# ps -ef | egrep '(openwin|olwm)'
>> >
>> > root 972 1 0 08:18:43 ? 0:00 /bin/sh
>> > /usr/openwin/bin/openwin -dev /dev/fb0 -dev /dev/fb1 top -nobanner
>> > root 992 972 0 08:18:44 ? 0:00 /usr/openwin/bin/xinit --
>> > /usr/openwin/bin/X :0 -dev /dev/fb0 -dev /dev/fb1 top
>> > root 994 992 1 08:18:44 ? 0:06 /usr/openwin/bin/X :0 -dev
>> > /dev/fb0 -dev /dev/fb1 top -nobanner -auth //.xsun.W
>> >
>> > root 1055 997 0 08:19:27 ? 0:00 /usr/openwin/bin/xset +fp
>> > /usr/fox/wp/fonts
>> >
>> >
>> >
>> > After X/Openwin starts I see:
>> > WP003B# ps -ef | egrep '(openwin|olwm)'
>> > root 972 1 0 08:18:43 ? 0:00 /bin/sh
>> > /usr/openwin/bin/openwin -dev /dev/fb0 -dev /dev/fb1 top -nobanner
>> > root 992 972 0 08:18:44 ? 0:00 /usr/openwin/bin/xinit --
>> > /usr/openwin/bin/X :0 -dev /dev/fb0 -dev /dev/fb1 top
>> > root 994 992 0 08:18:44 ? 0:07 /usr/openwin/bin/X :0 -dev
>> > /dev/fb0 -dev /dev/fb1 top -nobanner -auth //.xsun.W
>> > root 8251 992 0 10:04:09 ? 0:00 sh /usr/openwin/lib/Xinitrc
>> > root 8286 8251 0 10:04:12 ? 0:00 olwm -syncpid 8285
>> > root 8288 8286 0 10:04:12 ? 0:00 olwmslave
>> > root 8294 1 0 10:04:13 ?? 0:00 /usr/openwin/bin/shelltool
>> > -Wp 1600 950 -Ws 560 780 +Wi -C
>> >
>> > I was watching xinit with truss while waiting for something to happen.
>> > While waiting, xinit showed:
>> > WP003B# truss -p -v all 992
>> > open("/tmp/.X11-pipe/X0", O_RDWR) (sleeping...)
>> >
>> > As soon as startup continued I saw:
>> > WP003B# truss -p -v all 992
>> > open("/tmp/.X11-pipe/X0", O_RDWR) (sleeping...)
>> > Received signal #16, SIGUSR1, in open() [caught]
>> > siginfo: SIGUSR1 pid(tm)4 uid=0
>> > open("/tmp/.X11-pipe/X0", O_RDWR) Err#4 EINTR
>> > sigaction(SIGUSR1, 0xEFFFECF8, 0xEFFFEDF8) = 0
>> > new: hand = 0xEF53E2CC mask = 0 0 0 0 flags = 0x0012
>> > old: hand = 0x00000000 mask = 0 0 0 0 flags = 0x0000
>> > setcontext(0xEFFFEEF8)
>> > open("/etc/netconfig", O_RDONLY) = 3
>> > etc............
>> >
>> >
>> > Cheers,
>> >
>> > Kevin
>> >
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
