public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Michel LaBarre" <michel.labarre@rogers.com>
To: <Brian.Inglis@SystematicSw.ab.ca>,	<cygwin@cygwin.com>
Subject: RE: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
Date: Thu, 17 May 2018 22:09:00 -0000	[thread overview]
Message-ID: <000601d3ee1e$ee1b6a40$ca523ec0$@rogers.com> (raw)
In-Reply-To: <4310b729-b8b1-03aa-1c59-7a9c902edfef@SystematicSw.ab.ca>

L A Walsh,

Please forgive the following naïve points but since I saw no mention of the easy checks...

Did you do a "chkdsk" and "sfc /scannow" at any point to pare out any obvious corruptions?
(When you chkdsk on C:, you will be asked if you want to do it on reboot since the disk must be offline.)

No messages in windows App or system log?

Does anything else behave out of the ordinary?

Since your environment is suspect (given you moved a disk from another machine I believe) and Cygwin/win7 are not, why not rebuild and re-install?  
Re-installation would give you assurance going forward that no surprise is about to upset some schedule due to a different less innocuous failure.

Cheers,
Michel 
  (AKA "someone" - I replied to you directly L A Walsh because I assumed many would find no problem as with me resulting in lots of SPAM in the mailing list
   FTHOI I tried it on a Win 7 box and it worked ok as in my Win 10 systems
  uname -a
  YGWIN_NT-6.1 dell 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin
)





--
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

  parent reply	other threads:[~2018-05-17 20:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 12:58 L A Walsh
     [not found] ` <000a01d3ec54$a2bb2ca0$e83185e0$@rogers.com>
2018-05-15 16:51   ` L A Walsh
2018-05-15 17:18     ` James Darnley
     [not found]     ` <2b3cf1ed-1a3f-d8ff-136b-0ee533ae9e59@wagner.is>
2018-05-15 19:54       ` L A Walsh
2018-05-16 17:26 ` Andrey Repin
2018-05-17 13:22   ` L A Walsh
2018-05-17 19:41     ` Brian Inglis
2018-05-17 20:38       ` L A Walsh
2018-05-17 22:09       ` Michel LaBarre [this message]
2018-05-18  4:49         ` L A Walsh
2018-05-20 11:37 David Conrad
2018-05-21 20:18 ` L A Walsh
2018-05-22  2:07   ` Michel LaBarre
2018-05-22 10:48     ` L A Walsh
2018-05-23 20:13   ` Andrey Repin
2018-05-25  3:25     ` L A Walsh
2018-05-25 14:56       ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000601d3ee1e$ee1b6a40$ca523ec0$@rogers.com' \
    --to=michel.labarre@rogers.com \
    --cc=Brian.Inglis@SystematicSw.ab.ca \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).