ReactOS on eBox and embedded systems

Ask your support questions in here

Moderator: Moderator Team

hto
Developer
Posts: 2193
Joined: Sun Oct 01, 2006 3:43 pm

Post by hto » Mon Oct 24, 2011 2:57 pm

What is the bug number that you think is related?
6590. A regression after revision 52446.
Here is the new debug log:
[…]
Pff, now it crashes in another unexpected place. Something goes wrong behind the scenes…

pbreneman
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Re: ReactOS on eBox and embedded systems

Post by pbreneman » Sat Nov 05, 2011 9:39 pm

I am able to install and run ReactOS on a new version on my industrial board similar to an eBox!

The BIOS of the new version of the board has a selection where "Standard IDE Compatible" can be enabled.

Here is a zip with two debug logs that can be compared to show what ReactOS recognizes:
http://www.turbocontrol.com/RosDbgTermTwoBoards.zip

The LAN is not yet working with Ros and hopefully I can jump into that soon. But first I'll start another support message about the (general) serial port problems I'm having.

Thanks for all the help and suggestions.

vicmarcal
Test Team
Posts: 2732
Joined: Mon Jul 07, 2008 12:35 pm

Re: ReactOS on eBox and embedded systems

Post by vicmarcal » Mon Nov 07, 2011 3:25 pm

pbreneman wrote:I am able to install and run ReactOS on a new version on my industrial board similar to an eBox!

The BIOS of the new version of the board has a selection where "Standard IDE Compatible" can be enabled.

Here is a zip with two debug logs that can be compared to show what ReactOS recognizes:
http://www.turbocontrol.com/RosDbgTermTwoBoards.zip

The LAN is not yet working with Ros and hopefully I can jump into that soon. But first I'll start another support message about the (general) serial port problems I'm having.

Thanks for all the help and suggestions.
Open a Bugreport with the serial problems.And attach the debuglogs. It will be catch the attention of ReactOS devs
Image

pbreneman
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Re: ReactOS on eBox and embedded systems

Post by pbreneman » Thu Nov 24, 2011 3:55 am

Here is a new bug report on the LAN problem:
http://www.reactos.org/bugzilla/show_bug.cgi?id=6686

EmuandCo
Developer
Posts: 4080
Joined: Sun Nov 28, 2004 7:52 pm
Location: Germany, Bavaria, Steinfeld
Contact:

Re: ReactOS on eBox and embedded systems

Post by EmuandCo » Sun Nov 27, 2011 9:25 pm

Hm, I have my problems with a embedded hardware too. A Fujitsu Siemens Futro A100 alias Teco TR2220 Device. Its a SIS 550 SOC with 64 MB RAM, IDE Port and normally a 32 mb CF Card as Master. Well, I plugged a 2.5'' 120 GB HDD and a DVD Drive in there and tried to install ROS. It even goes to the 2nd stage setup, but dies at the hardware installation. Sadly I was not able to get Screen Debugging run. I get 20 blocks on top when it should jump inside the Console again and these blocks change with every typing, seems like they are the console in a badly scrambled way. LOG File Debug just gives this: http://www.reactos.org/paste/index.php/9595/
Image
ReactOS is still in alpha stage, meaning it is not feature-complete and is recommended only for evaluation and testing purposes.

pbreneman
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Re: ReactOS on eBox and embedded systems

Post by pbreneman » Sat Dec 17, 2011 5:38 pm

Just tried r54672 and PC locks up whenever the LAN cable is connected which is the same as before.

pbreneman
Posts: 78
Joined: Wed Feb 25, 2009 5:12 am

Re: ReactOS on eBox and embedded systems

Post by pbreneman » Mon May 28, 2012 5:49 am

I just installed and tested r56661 dbg and it all seems to work OK but crashes when I plug the LAN cable in. I captured a little of a debug log (below) but I'll try to gather more info soon. Please let me know if you have any ideas or suggestions.

Code: Select all

Boot took 15849399734 cycles!
Interrupts: 1915 System Calls: 15640 Context Switches: 1869
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/se/semgr.c:705) HACK: Should deny access for caller: granted 0x90003, desired 0x190003 (generic mapping B09089F8).
(/srv/buildbot_cmake/full_cmake/build/base/services/wlansvc/wlansvc.c:145) wlansvc: main() started
(/srv/buildbot_cmake/full_cmake/build/base/services/wlansvc/wlansvc.c:96) ServiceMain() called
(/srv/buildbot_cmake/full_cmake/build/base/services/wlansvc/wlansvc.c:130) ServiceMain() done
(/srv/buildbot_cmake/full_cmake/build/base/system/services/rpcserver.c:1721) RNotifyBootConfigStatus(00000000 1) called
Boot took 16801114441 cycles!
Interrupts: 2039 System Calls: 25118 Context Switches: 3860
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/se/semgr.c:705) HACK: Should deny access for caller: granted 0x0, desired 0x100000 (generic mapping B09089F8).
DHCPCSVC: DHCP service is starting up
(/srv/buildbot_cmake/full_cmake/build/base/services/umpnpmgr/umpnpmgr.c:3191) Removal pending: Root\*PNP0501\0000
(/srv/buildbot_cmake/full_cmake/build/base/services/umpnpmgr/umpnpmgr.c:3187) Removal vetoed: Root\*PNP0501\0000
(/srv/buildbot_cmake/full_cmake/build/lib/rtl/actctx.c:874) Unsupported yet language attribute (*)
Using shell hooks for notification of shell events.
WARNING:  BackupRead at /srv/buildbot_cmake/full_cmake/build/dll/win32/kernel32/client/file/backup.c:34 is UNIMPLEMENTED!
WARNING:  BackupRead at /srv/buildbot_cmake/full_cmake/build/dll/win32/kernel32/client/file/backup.c:34 is UNIMPLEMENTED!
(/srv/buildbot_cmake/full_cmake/build/ntoskrnl/mm/ARM3/pool.c:482) Paged pool expansion: 1 2

*** Fatal System Error: 0x0000007f
                       (0x00000008,0x00000000,0x00000000,0x00000000)

[7hEntered debugger on embedded INT3 at 0x0008:0x8091b918.
kdb:>
bt
Eip:
<NTOSKRNL.EXE:11b919 (/srv/buildbot_cmake/full_cmake/build/lib/rtl/i386/debug_asm.S:46 (_RtlpBreakWithStatusInstruction@0))>
Frames:
<NTOSKRNL.EXE:80441 (ReactOS/ntoskrnl/ke/bug.c:1081 (KeBugCheckWithTf@24))>
<NTOSKRNL.EXE:10090b (ReactOS/ntoskrnl/ke/i386/exp.c:1133 (@KiSystemFatalException@8))>
<NTOSKRNL.EXE:105f75 (ReactOS/ntoskrnl/ke/i386/traphdlr.c:824 (@KiTrap08Handler@4))>
<NTOSKRNL.EXE:1045ba (/srv/buildbot_cmake/full_cmake/build/ntoskrnl/ke/i386/trap.s:0 (_KiTrap08))>
<NTOSKRNL.EXE:815c0 (ReactOS/ntoskrnl/ke/dpc.c:718 (KeInsertQueueDpc@12))>
<ndis.sys:8984>
<NTOSKRNL.EXE:101c86 (ReactOS/include/crt/mingw32/intrin_x86.h:86 (@KiInterruptDispatch@8))>
<NTOSKRNL.EXE:101a76 (ReactOS/ntoskrnl/ke/i386/irqobj.c:312 (@KiInterruptTemplateHandler@8))>

*** Fatal System Error: 0x0000000a
                       (0x7FFBA00C,0xFFFFFFFF,0x00000000,0x80917BDC)

Entered debugger on embedded INT3 at 0x0008:0x8091b918.

hto
Developer
Posts: 2193
Joined: Sun Oct 01, 2006 3:43 pm

Post by hto » Mon May 28, 2012 9:35 am

Bug 6686, probably.

Post Reply

Who is online

Users browsing this forum: No registered users and 8 guests