Windows Bluescreen

>
> Sample command:
> git push omv master\r
>
> config. =
>
> [core]
>         repositoryformatversion = 0
>         filemode = false
>         bare = false
>         logallrefupdates = true
>         symlinks = false
>         ignorecase = true
>         hideDotFiles = dotGitOnly
> [remote "omv"]
>         url = gitpush@192.168.0.100:/git-repos/HexEncrypter
>         fetch = +refs/heads/*:refs/remotes/omv/*
>

> Hi Erik,
>
> On Tue, Feb 10, 2015 at 9:12 AM,  <erik@aercon.net> wrote:
>>
>> I find that preview 1.8 is bluescreening on about 1 of 3 ssh pushes.  1.9
>> preview 12-17-2014 doesn't even bluescreen, the windows gui locks until
>> reset.
>
> Does this mean that pushing over git:// file:// and http:// are
> unaffected? Can you successfully do other (non-git) things over ssh?
>
>>
>> Sample command:
>> git push omv master\r
>>
>> config. =
>>
>> [core]
>>         repositoryformatversion = 0
>>         filemode = false
>>         bare = false
>>         logallrefupdates = true
>>         symlinks = false
>>         ignorecase = true
>>         hideDotFiles = dotGitOnly
>> [remote "omv"]
>>         url = gitpush@192.168.0.100:/git-repos/HexEncrypter
>>         fetch = +refs/heads/*:refs/remotes/omv/*
>>
>
> You might get a more helpful response out of the msysgit folks (I've
> added them to the Cc list).

> Pushing over http and https are unaffected..  My linux nas died, so on
> rebuild I tried to do the ssh thing, and realized quite soon that
> things weren't right.
>
> As far as other uses of ssh, I don't know, I use putty frequently, but
> I am not clear if it is using the same libraries or not.

> On Wed, Feb 11, 2015 at 3:56 AM, Chris Packham <judge.packham@gmail.com> wrote:
>> Hi Erik,
>>
>> On Tue, Feb 10, 2015 at 9:12 AM,  <erik@aercon.net> wrote:
>>>
>>> I find that preview 1.8 is bluescreening on about 1 of 3 ssh pushes.  1.9
>>> preview 12-17-2014 doesn't even bluescreen, the windows gui locks until
>>> reset.
>>
>> Does this mean that pushing over git:// file:// and http:// are
>> unaffected? Can you successfully do other (non-git) things over ssh?
>>
>>>
>>> Sample command:
>>> git push omv master\r
>>>
>>> config. =
>>>
>>> [core]
>>>         repositoryformatversion = 0
>>>         filemode = false
>>>         bare = false
>>>         logallrefupdates = true
>>>         symlinks = false
>>>         ignorecase = true
>>>         hideDotFiles = dotGitOnly
>>> [remote "omv"]
>>>         url = gitpush@192.168.0.100:/git-repos/HexEncrypter
>>>         fetch = +refs/heads/*:refs/remotes/omv/*
>>>
>>
>> You might get a more helpful response out of the msysgit folks (I've
>> added them to the Cc list).

> On Thu, Feb 12, 2015 at 1:33 AM, Erik Friesen <erik@aercon.net> wrote:
>> Pushing over http and https are unaffected..  My linux nas died, so on
>> rebuild I tried to do the ssh thing, and realized quite soon that
>> things weren't right.
>>
>> As far as other uses of ssh, I don't know, I use putty frequently, but
>> I am not clear if it is using the same libraries or not.
>
> I think putty ships it's own ssh implementation rather than using an
> openSSH port.
>
>> I hunted around for the bugreport email on mysgit but couldn't seem to
>> find it.  It seems in the foggy recesses I remember reading about an
>> ssh issue with windows, but can't find it now.
>>
>
> https://github.com/msysgit/git/issues
>
> Happy hunting :). Actually if it is a ssh problem it might be a
> generic MSYS issue. So there's another bug tracker to look through
>
> http://sourceforge.net/p/mingw/bugs/
>
>
>> On Wed, Feb 11, 2015 at 3:56 AM, Chris Packham <judge.packham@gmail.com> wrote:
>>> Hi Erik,
>>>
>>> On Tue, Feb 10, 2015 at 9:12 AM,  <erik@aercon.net> wrote:
>>>>
>>>> I find that preview 1.8 is bluescreening on about 1 of 3 ssh pushes.  1.9
>>>> preview 12-17-2014 doesn't even bluescreen, the windows gui locks until
>>>> reset.
>>>
>>> Does this mean that pushing over git:// file:// and http:// are
>>> unaffected? Can you successfully do other (non-git) things over ssh?
>>>
>>>>
>>>> Sample command:
>>>> git push omv master\r
>>>>
>>>> config. =
>>>>
>>>> [core]
>>>>         repositoryformatversion = 0
>>>>         filemode = false
>>>>         bare = false
>>>>         logallrefupdates = true
>>>>         symlinks = false
>>>>         ignorecase = true
>>>>         hideDotFiles = dotGitOnly
>>>> [remote "omv"]
>>>>         url = gitpush@192.168.0.100:/git-repos/HexEncrypter
>>>>         fetch = +refs/heads/*:refs/remotes/omv/*
>>>>
>>>
>>> You might get a more helpful response out of the msysgit folks (I've
>>> added them to the Cc list).

> I'd say this is related.  http://sourceforge.net/p/mingw/bugs/2240/
>
> There isn't much hope, that was filed months ago with no action.  I
> suggest moving to another ssh library perhaps?  Anyways, this is a
> windows git bug report, so it really needs to stay with mysgit in my
> opinion.
>
> I'd say it should reproduce without much effort.  Do a git push using
> win7 64 pro or similar, I'd say it will have issues.
>
> At minimum, this should be on the list for others to view.  I have run
> across problems from others, but I don't think they realized it could
> be an ssh problem.
>
> On Thu, Feb 12, 2015 at 4:33 AM, Chris Packham <judge.packham@gmail.com> wrote:
>> On Thu, Feb 12, 2015 at 1:33 AM, Erik Friesen <erik@aercon.net> wrote:
>>> Pushing over http and https are unaffected..  My linux nas died, so on
>>> rebuild I tried to do the ssh thing, and realized quite soon that
>>> things weren't right.
>>>
>>> As far as other uses of ssh, I don't know, I use putty frequently, but
>>> I am not clear if it is using the same libraries or not.
>>
>> I think putty ships it's own ssh implementation rather than using an
>> openSSH port.
>>
>>> I hunted around for the bugreport email on mysgit but couldn't seem to
>>> find it.  It seems in the foggy recesses I remember reading about an
>>> ssh issue with windows, but can't find it now.
>>>
>>
>> https://github.com/msysgit/git/issues
>>
>> Happy hunting :). Actually if it is a ssh problem it might be a
>> generic MSYS issue. So there's another bug tracker to look through
>>
>> http://sourceforge.net/p/mingw/bugs/
>>
>>
>>> On Wed, Feb 11, 2015 at 3:56 AM, Chris Packham <judge.packham@gmail.com> wrote:
>>>> Hi Erik,
>>>>
>>>> On Tue, Feb 10, 2015 at 9:12 AM,  <erik@aercon.net> wrote:
>>>>>
>>>>> I find that preview 1.8 is bluescreening on about 1 of 3 ssh pushes.  1.9
>>>>> preview 12-17-2014 doesn't even bluescreen, the windows gui locks until
>>>>> reset.
>>>>
>>>> Does this mean that pushing over git:// file:// and http:// are
>>>> unaffected? Can you successfully do other (non-git) things over ssh?
>>>>
>>>>>
>>>>> Sample command:
>>>>> git push omv master\r
>>>>>
>>>>> config. =
>>>>>
>>>>> [core]
>>>>>         repositoryformatversion = 0
>>>>>         filemode = false
>>>>>         bare = false
>>>>>         logallrefupdates = true
>>>>>         symlinks = false
>>>>>         ignorecase = true
>>>>>         hideDotFiles = dotGitOnly
>>>>> [remote "omv"]
>>>>>         url = gitpush@192.168.0.100:/git-repos/HexEncrypter
>>>>>         fetch = +refs/heads/*:refs/remotes/omv/*
>>>>>
>>>>
>>>> You might get a more helpful response out of the msysgit folks (I've
>>>> added them to the Cc list).

> I'd say this is related.  http://sourceforge.net/p/mingw/bugs/2240/
> 
> There isn't much hope, that was filed months ago with no action.  I
> suggest moving to another ssh library perhaps?  Anyways, this is a
> windows git bug report, so it really needs to stay with mysgit in my
> opinion.
> 
> I'd say it should reproduce without much effort.  Do a git push using
> win7 64 pro or similar, I'd say it will have issues.
> 
> At minimum, this should be on the list for others to view.  I have run
> across problems from others, but I don't think they realized it could
> be an ssh problem.

> Am Donnerstag, den 12.02.2015, 07:21 -0500 schrieb Erik Friesen:
>> I'd say this is related.  http://sourceforge.net/p/mingw/bugs/2240/
>>
>> There isn't much hope, that was filed months ago with no action.  I
>> suggest moving to another ssh library perhaps?  Anyways, this is a
>> windows git bug report, so it really needs to stay with mysgit in my
>> opinion.
>>
>> I'd say it should reproduce without much effort.  Do a git push using
>> win7 64 pro or similar, I'd say it will have issues.
>>
>> At minimum, this should be on the list for others to view.  I have run
>> across problems from others, but I don't think they realized it could
>> be an ssh problem.
>
> (Please don't TOP post)
>
> The cited bug report does not correlate to msysgit as we compile and
> ship our own openssh.
>
> Git for Windows Version 1.8.x might still have the old and slow openssh.
> With the newest version I get speeds of up to 30MB/s over Gigabit LAN.
>
> Can you create a minimal test case to reprocude the problem?
>

> Sorry, I don't know what this TOP posting problem is, and hitting
> reply only replies to the last sender.   If you prefer, and you have
> some regular bugtracker, I could use that instead of email posting.
> 
> To repro-
> Set up git user on local linux repo, in my case 192.168.0.100
> 
> On a windows 7 64bit machine-
> $ cd myproject
> $ git init
> $ git add .
> $ git commit -m 'initial commit'
> $ git remote add origin git@192.168.0.100:/opt/git/project.git
> $ git push origin master
> (Shamelessly copied from git page)
> 
> Problem happens after entering password, it may or may not get started.
> 
> The nature of a bluescreen doesn't make debugging and reproduction
> real easy.  If it helps, I can get the dumps from those crashes.  To
> move on, I moved back to local http pushes.

> -----Original Message-----
> From: Erik Friesen
> Sent: Thursday, February 12, 2015 7:22
> 
> I'd say this is related.  http://sourceforge.net/p/mingw/bugs/2240/
> 
> There isn't much hope, that was filed months ago with no action.  I
> suggest moving to another ssh library perhaps?  Anyways, this is a
> windows git bug report, so it really needs to stay with mysgit in my
> opinion.

> 
> I'd say it should reproduce without much effort.  Do a git push using
> win7 64 pro or similar, I'd say it will have issues.
> 
> At minimum, this should be on the list for others to view.  I have run
> across problems from others, but I don't think they realized it could
> be an ssh problem.
> 
> On Thu, Feb 12, 2015 at 4:33 AM, Chris Packham 
> <judge.packham@gmail.com> wrote:
> > On Thu, Feb 12, 2015 at 1:33 AM, Erik Friesen 
> <erik@aercon.net> wrote:
> >> Pushing over http and https are unaffected..  My linux nas 
> died, so on
> >> rebuild I tried to do the ssh thing, and realized quite soon that
> >> things weren't right.
> >>
> >> As far as other uses of ssh, I don't know, I use putty 
> frequently, but
> >> I am not clear if it is using the same libraries or not.
> >
> > I think putty ships it's own ssh implementation rather than using an
> > openSSH port.
> >
> >> I hunted around for the bugreport email on mysgit but 
> couldn't seem to
> >> find it.  It seems in the foggy recesses I remember 
> reading about an
> >> ssh issue with windows, but can't find it now.
> >>
> >
> > https://github.com/msysgit/git/issues
> >
> > Happy hunting :). Actually if it is a ssh problem it might be a
> > generic MSYS issue. So there's another bug tracker to look through
> >
> > http://sourceforge.net/p/mingw/bugs/
> >
> >