Ros-general September 2012

ros-general@reactos.org

5 participants
4 discussions

Re: [ros-general] ReactOS BSOD / Freeze on large data transfers (and CPU load?)

by Michael Lackner

Greetings! I'm having some trouble with my eMail client, it seems the digest mode of the mailing list confuses it somehow, so I'll quote this part manually, sorry for that. I switched digest off now, hopefully the list will now deliver your eMails individually. :) Copying my test file to ReactOS is not that problematic, I can just boot Knoppix in the same VM, mount the ReactOS FAT32 filesystem, mount an external USB stick or something and copy it over, reboot to ReactOS, problem solved. But generally it would be nice to have stable FTP (or HTTP or SCP) transfers in ReactOS, so I kept trying different programs etc. I thought that this is such a basic thing that it just has to work! But yeah, BSOD every time. File size btw. is 668MBytes. Now the second thing is, I would like to run x264 (a H.264/AVC video encoder linked against the libav codec library for decoding) to transcode a video stream (that 668MB file). That part works for a few minutes and then crashes. If it helps I can generate logs, maybe you could tell me what exactly I could do that helps you. About that VMware Player configuration I just noticed that I gave you wrong info. I was indeed using the original setting set up by the 0.3.14 VMware image that I had downloaded. The vmx/vmxf configuration files are attached to this eMail, here are some settings beforehand: * Mem: 512MB * CPUs: 1 * HDD: 8GB * USB: Present * Display: Autodetect * OS Type: XP Pro I just tried it again a few times, and build #57337 boots into BSOD every single time using those settings on VMware Player "4.0.1 build-528992". Host OS is CentOS 6.3 Linux x86_64 in case it matters.. So if you require any specific tests or anything, just let me know. :) I might not be able to test on weekends though, as the machine I am testing on might not be available on weekends. Thanks! -Michael > Hi Michael! > Well...We can try several tricks to make it work :) > If your main objective is to "copy" the File into ReactOS, then the best option is to > "Mount" the Virtual HardDisk of your VirtualMachine. Mounting will let you place the > file inside ReactOS without issues and from your host OS.Then when booting ReactOS you > will see the file inside "magically". > > If your main objective is to test the MM and overall ReactOS behavior in Vmware then > thanks a lot, because your help could be really really helpful. :) > I've to say that lately ReactOS has improved a lot its stability under Vbox but seems > it didn't do the same under Vmware as your tests shows. > It would be really nice if you can share which is your Virtual Machine > configuration(Ram, HDD, etc) so maybe we can try to replicate the issue to find > something useful in the logs. > Or maybe you can create useful Logs for us :) > I have tried Filezilla under VBOX and seems to fail.Reason under this line: > (Trace cut out) > > If this didnt happen in 0.3.14 then we are in front of a regression. Nice catch! > We can try to find the guilty commit via Binary Search. > Thanks a lot! -- Michael Lackner Lehrstuhl für Informationstechnologie (CiT) Montanuniversität Leoben Tel.: +43 (0)3842/402-1505 | Mail: michael.lackner(a)unileoben.ac.at Fax.: +43 (0)3842/402-1502 | Web: http://institute.unileoben.ac.at/infotech

12 years, 2 months

Re: [ros-general] ReactOS BSOD / Freeze on large data transfers (and CPU load?)

by Michael Lackner

Hello! Thank you for your reply, I wasn't actually aware of those builds. I tried build #57337 (while I am writing this, it seems that 57338 is being released), but it went from bad to worse. While the transfer seemed to work longer than before (could be wrong about that though, not enough statistical data), it still ended with NTOSKRNL.EXE crashing. *** STOP: 0x0000001E (0xC000046, 0x808847C7, 0xF83495A8, 0x00000000) *** NTOSKRNL.EXE - Address 808847C7 base at 80800000 On top of that, trying to start Filezilla 3.5.3 now results in another BSOD of NTOSKRNL.EXE (also 0x0000001E), which did not happen in 0.3.14. Additionally, that build boots into a BSOD on VMware Player 4.0.1, but boots up fine on VirtualBox 4.2, but that could easily be a fault of my configuration, as I'm not currently using the settings from the 0.3.14 VM images, but fresh ones, as this is a different host machine now. It kind of looks like I'm not going to get my preferred software to work in a stable fashion on ReactOS, at least when virtualized.. I guess there is nothing I can do but to try new ReactOS builds every now and then? Thanks anyway! Aleksey Bragin wrote: > Hello! > > Could you try latest build from here http://www.reactos.org/getbuilds/ ? > It contains a number of networking improvements, however as for general > stability with regards to kernel crashes, the kernel memory manager is > still work in progress, so it may crash as easy as 0.3.14. But it would > be great to see whether the situation imprpved. > > If there is anything I can help with - let me know. > > Best regards, > Aleksey Bragin. > > On 17.09.2012 11:19, Michael Lackner wrote: >> Greetings! >> >> I would like to ask a question, maybe there is already an easy fix for this >> that I just cannot find using Google. >> >> So, I have set up ReactOS in both VirtualBox and VMware Player (4.0 & 5.0). >> >> What I am trying to do is to download a large ~700MB file using ftp.exe or >> Filezilla 2. Alternatively, I also tried to copy it from an ISO CD image. >> >> This never succeeds however. Either the machine just freezes or BSODs, >> according to bt it's something like "can't access memory at <some address>", >> with the error caused by the application doing the transfer. >> >> Mostly it just freezes though, especially when copying from CD ISO. >> >> So what I did then was to boot Knoppix and copy the file to ReactOS's >> partition offline. It's actually a video stream file. When I then tried to >> run my actual test (x264 video transcode), it works for a few minutes, then >> NTOSKRNL.EXE BSODs again, I didn't do a backtrace for that crash yet. >> >> Am I doing something specifically wrong to cause so many Kernel crashes, or >> is this still "normal" in 0.3.14? I mean: Is it normal to have the Kernel >> crash like that when just downloading or copying some files?! >> >> Thanks for any help you might be able to provide! -- Michael Lackner Lehrstuhl für Informationstechnologie (CiT) Montanuniversität Leoben Tel.: +43 (0)3842/402-1505 | Mail: michael.lackner(a)unileoben.ac.at Fax.: +43 (0)3842/402-1502 | Web: http://institute.unileoben.ac.at/infotech

12 years, 3 months

ReactOS BSOD / Freeze on large data transfers (and CPU load?)

by Michael Lackner

Greetings! I would like to ask a question, maybe there is already an easy fix for this that I just cannot find using Google. So, I have set up ReactOS in both VirtualBox and VMware Player (4.0 & 5.0). What I am trying to do is to download a large ~700MB file using ftp.exe or Filezilla 2. Alternatively, I also tried to copy it from an ISO CD image. This never succeeds however. Either the machine just freezes or BSODs, according to bt it's something like "can't access memory at <some address>", with the error caused by the application doing the transfer. Mostly it just freezes though, especially when copying from CD ISO. So what I did then was to boot Knoppix and copy the file to ReactOS's partition offline. It's actually a video stream file. When I then tried to run my actual test (x264 video transcode), it works for a few minutes, then NTOSKRNL.EXE BSODs again, I didn't do a backtrace for that crash yet. Am I doing something specifically wrong to cause so many Kernel crashes, or is this still "normal" in 0.3.14? I mean: Is it normal to have the Kernel crash like that when just downloading or copying some files?! Thanks for any help you might be able to provide! -- Michael Lackner Lehrstuhl für Informationstechnologie (CiT) Montanuniversität Leoben Tel.: +43 (0)3842/402-1505 | Mail: michael.lackner(a)unileoben.ac.at Fax.: +43 (0)3842/402-1502 | Web: http://institute.unileoben.ac.at/infotech

12 years, 3 months

Únete a mi red en LinkedIn

by Luis Taveras a través de LinkedIn

LinkedIn ------------ Luis Taveras ha solicitado añadirte como contacto en LinkedIn: ------------------------------------------ Me gustaría añadirte a mi red profesional en LinkedIn. Aceptar invitación de Luis Taveras http://www.linkedin.com/e/-rny37a-h6ssoju3-53/fXkAsYr7l3LFXWF9BRVwNUlk97bIv… Ver el perfil de Luis Taveras http://www.linkedin.com/e/-rny37a-h6ssoju3-53/rso/156754979/BW-r/name/19412… ------------------------------------------ Estás recibiendo invitaciones por correo electrónico. Este mensaje de correo electrónico estaba dirigido a ReactOS List. Averigua la razón por la que incluimos esto: http://www.linkedin.com/e/-rny37a-h6ssoju3-53/plh/http%3A%2F%2Fhelp%2Elinke… (c) 2012, LinkedIn Corporation. 2029 Stierlin Ct, Mountain View, CA 94043, EE.UU.

12 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Ros-general September 2012