X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ZfqS3E5ZsA2uofNF
	u+f1u0ciDw5PdIdSyBNV0b7DUl6VA9deqy3B+174Us3BqkoUn7OhLf2KDo6QXhcm
	I57rVErfOnVuaXWFWupXkxwXjh+9wdxNkrusCXt3hbmn2/AY5cta+ZLVR+k6Gx+6
	EZNJN/IHHlyE+hdpOT5NmRLFHSs=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:reply-to:mime-version:to
	:subject:references:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=MGiyl9gPLAs5IJdaSmUGQb
	9hl9w=; b=JeRhBWldN0hjAFQH+UThxqwUFus3dx5T3KDLGzemnM429YRNVQgg5C
	HOxAy0WKGSmZbXo9OSM4tAQPYF1Obi0rWxxMu+4L2MH/TBK8X0n402CkogCvowt7
	V54VdWnqPOjyxWSBRLa/+Z3KqaiXKdF151MEsHO9rKPvdM2b9wdQk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Spam-SWARE-Status: No, score=3.4 required=5.0 tests=AWL,BAYES_50,BOTNET,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,TW_YG autolearn=no version=3.3.1
Message-id: <51A8CF41.4000104@cygwin.com>
Date: Fri, 31 May 2013 12:26:41 -0400
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh AT cygwin DOT com>
Reply-to: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Postinstall Script Errors With Exit Code 128
References: <OFB98AFA0A DOT C98BEEC2-ON85257B79 DOT 006C2BC1-85257B79 DOT 006C532B AT LocalDomain> <OF146666CE DOT 12B8AAEA-ON85257B7A DOT 00581A1E-85257B7A DOT 005844B4 AT desknetinc DOT com> <51A62CAE DOT 3080504 AT cygwin DOT com> <OF932F29B5 DOT 7FF500EF-ON85257B7A DOT 0065C25E-85257B7A DOT 006A199F AT desknetinc DOT com> <51A65C03 DOT 3050107 AT cygwin DOT com> <OF160D8D15 DOT B9C70282-ON85257B7C DOT 00239146-85257B7C DOT 0023B02A AT desknetinc DOT com>
In-reply-to: <OF160D8D15.B9C70282-ON85257B7C.00239146-85257B7C.0023B02A@desknetinc.com>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit

On 5/31/2013 2:29 AM, Paul DOT Nickerson AT desknetinc DOT com wrote:
>> From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
>> To: cygwin at cygwin dot com,
>> Date: 05/29/2013 03:51 PM
>> Subject: Re: Postinstall Script Errors With Exit Code 128
>> Sent by: cygwin-owner at cygwin dot com
>>
>> On 5/29/2013 3:18 PM, Paul.Nickerson at desknetinc dot com wrote:
>>> So, I think that one of these functions hangs when
>>> cygwin1.dll is present. I'm thinking dump_dodgy_apps.
>>
>> Possibly.  You may have a BLODA problem (
> http://cygwin.com/acronyms/#BLODA),
>> whether known or unknown.  If so, getting rid of it will certainly help.
>>
>>> I tried copying cygcheck.exe to other directories and leaving
> cygwin1.dll
>>> in bin, and cygcheck does not hang when run from other directories.
>>
>> Interesting.  Maybe there's some Windows permission problems in the
>> directory you were running from?
>
> I have fixed it. Thank you for your help.
>
> I have a few other AWS EC2 instances. One other was having trouble with
> Cygwin install, and none of the rest were. I tried comparing installed
> applications, but got nowhere. I also tried installing Windows updates on
> the troubled system, and copying the cygwin from a healthy system to the
> troubled one. Neither attempt worked. I had looked into folder permissions
> before, which all looked fine, and tried installing to another folder and
> even another drive, but that hadn't helped.
>
> I then used WinDbg to run C:\cygwin\bin\bash.exe --norc --noprofile
> "/etc/postinstall/000-cygwin-post-install.sh", and I think I got this
> error: SetContext failed, 0x8007001F. Looking online, it seems that code
> is associated with "A device attached to the system is not functioning". I
> have already rebooted a bunch of times. I used Belarc Advisor to grab the
> virtual hardware version. Belarc Advisor said the System Model / Main
> Circuit Board / BIOS on both troubled instances was "Xen HVM domU
> 3.1.2-92.1.13.el5.", while on the other working instances it was "Xen HVM
> domU 3.4.3-2.6.18 09/01/2012".
>
> So, I shut down the instance (I use EBS volumes), created an AMI from it,
> created an Instance from the AMI, and started up that instance. This has
> the effect of applying a new virtual hardware if available (proven by the
> fact that I get a new Instance ID), as well as moving to different
> physical hardware. After this, Belarc Advisor reported the good virtual
> hardware version. And, I was able to successfully install and use Cygwin
> normally. :)
>
> I have attached the output of running that bash.exe command inside WinDbg,
> just in case it's useful for anything.
>
> Again, thank you for you help.

You're welcome.  Thanks for your efforts in tracking this down and reporting
back.  I suspect it will help others in the future if they see similar
issues.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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