* Re: Windows Bluescreen
2015-02-12 12:21 ` Erik Friesen
@ 2015-02-12 12:25 ` Erik Friesen
2015-02-12 12:42 ` Thomas Braun
2015-02-12 12:53 ` Jason Pyeron
2 siblings, 0 replies; 11+ messages in thread
From: Erik Friesen @ 2015-02-12 12:25 UTC (permalink / raw)
To: Chris Packham; +Cc: GIT, msysgit
Also, as another nuance of this bug, this destroyed the local repo in
the process, inserting >>>>>> HEAD, ========, <<<<<<<md5hashes, and
doubling up on stuff everywhere.
On Thu, Feb 12, 2015 at 7:21 AM, Erik Friesen <erik@aercon.net> wrote:
> 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).
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Re: Windows Bluescreen
2015-02-12 12:21 ` Erik Friesen
2015-02-12 12:25 ` Erik Friesen
@ 2015-02-12 12:42 ` Thomas Braun
2015-02-12 13:21 ` Erik Friesen
2015-02-12 12:53 ` Jason Pyeron
2 siblings, 1 reply; 11+ messages in thread
From: Thomas Braun @ 2015-02-12 12:42 UTC (permalink / raw)
To: Erik Friesen; +Cc: Chris Packham, GIT, msysgit
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?
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Re: Windows Bluescreen
2015-02-12 12:42 ` Thomas Braun
@ 2015-02-12 13:21 ` Erik Friesen
2015-02-12 13:48 ` Yue Lin Ho
2015-02-13 21:09 ` Thomas Braun
0 siblings, 2 replies; 11+ messages in thread
From: Erik Friesen @ 2015-02-12 13:21 UTC (permalink / raw)
To: Thomas Braun; +Cc: Chris Packham, GIT, msysgit
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.
On Thu, Feb 12, 2015 at 7:42 AM, Thomas Braun
<thomas.braun@virtuell-zuhause.de> wrote:
> 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?
>
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Re: Windows Bluescreen
2015-02-12 13:21 ` Erik Friesen
@ 2015-02-12 13:48 ` Yue Lin Ho
2015-02-13 21:09 ` Thomas Braun
1 sibling, 0 replies; 11+ messages in thread
From: Yue Lin Ho @ 2015-02-12 13:48 UTC (permalink / raw)
To: msysgit; +Cc: thomas.braun, judge.packham, git, erik
[-- Attachment #1.1: Type: text/plain, Size: 1262 bytes --]
Erik Friesen於 2015年2月12日星期四 UTC+8下午9時21分40秒寫道：
>
> Sorry, I don't know what this TOP posting problem is, and hitting
> reply only replies to the last sender.
>
top post:
The answer is ...
> I have a question that ...
"don't top post":
> I have a question that ...
The answer is ...
Yue Lin Ho
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2680 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Re: Windows Bluescreen
2015-02-12 13:21 ` Erik Friesen
2015-02-12 13:48 ` Yue Lin Ho
@ 2015-02-13 21:09 ` Thomas Braun
1 sibling, 0 replies; 11+ messages in thread
From: Thomas Braun @ 2015-02-13 21:09 UTC (permalink / raw)
To: Erik Friesen; +Cc: Chris Packham, GIT, msysgit
Am 12.02.2015 um 14:21 schrieb Erik Friesen:
> 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.
I'm doing pushes over ssh on a daily basis against my linux server.
And I'm using a Win7 64bit machine as well.
Can you try if it makes any difference if you use ssh login with public
keys instead of passwords?
You can also try to add "LogLevel Debug" to ~/.ssh/config in order to
get more verbose ssh output.
--
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
^ permalink raw reply [flat|nested] 11+ messages in thread
* RE: Windows Bluescreen
2015-02-12 12:21 ` Erik Friesen
2015-02-12 12:25 ` Erik Friesen
2015-02-12 12:42 ` Thomas Braun
@ 2015-02-12 12:53 ` Jason Pyeron
2 siblings, 0 replies; 11+ messages in thread
From: Jason Pyeron @ 2015-02-12 12:53 UTC (permalink / raw)
To: 'Erik Friesen', 'Chris Packham'; +Cc: 'GIT', msysgit
> -----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.
FWIW, if it does not get fixed you can use the cygwin git and openssh without many problems, and the cygwin group is pretty responsive to issues like this.
>
> 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/
> >
> >
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Principal Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
This message is copyright PD Inc, subject to license 20080407P00.
^ permalink raw reply [flat|nested] 11+ messages in thread