CVS Build Dead

[Alex Ionescu]

Richard and I can't get the ros cvs build to boot...I get stuck on a 
black screen, and he gets a freeze on ndis.sys as well as a blackscreen 
if running the bootcd.

Can anyone confirm?

Best regards,
Alex Ionescu

[Steven Edwards]

Hi,

--- Alex Ionescu [e-mail] wrote:
> Richard and I can't get the ros cvs build to boot...I get stuck on a 
> black screen, and he gets a freeze on ndis.sys as well as a
> blackscreen 
> if running the bootcd.
>
> Can anyone confirm?

I got this same problem....of course I had to hack my tree quite a bit
just to get her to build and the patch I sent in does not have all the
misc hacks I had to add to get a build going. I thought it was just
me.....

Thanks
Steven

__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail

[Alex Ionescu]

DBG = 1 was on by default...I've commited a new DBG = 0 default config file.

The question remains why does it hang so horribly with DBG = 1.

Best regards,
Alex Ionescu

Steven Edwards wrote:
> Hi,
>
> --- Alex Ionescu [e-mail] wrote:
> > Richard and I can't get the ros cvs build to boot...I get stuck on a 
> > black screen, and he gets a freeze on ndis.sys as well as a
> > blackscreen 
> > if running the bootcd.
> >
> > Can anyone confirm?
>
> I got this same problem....of course I had to hack my tree quite a bit
> just to get her to build and the patch I sent in does not have all the
> misc hacks I had to add to get a build going. I thought it was just
> me.....
>
> Thanks
> Steven
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - You care about security. So do we.
> http://promotions.yahoo.com/new_mail
> _______________________________________________
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Alex Ionescu]

> > The question remains why does it hang so horribly with DBG = 1.

Apparently something in irq.c according to Richard. I'll take a look at 
it later this week if nobody else does. School starting again Monday :(.

Best regards,
Alex Ionescu

Alex Ionescu wrote:
> DBG = 1 was on by default...I've commited a new DBG = 0 default config 
> file.
>
> The question remains why does it hang so horribly with DBG = 1.
>
> Best regards,
> Alex Ionescu
>
> Steven Edwards wrote:
> > Hi,
> >
> > --- Alex Ionescu [e-mail] wrote:
> > > Richard and I can't get the ros cvs build to boot...I get stuck on a 
> > > black screen, and he gets a freeze on ndis.sys as well as a
> > > blackscreen if running the bootcd.
> > >
> > > Can anyone confirm?
> >
> > I got this same problem....of course I had to hack my tree quite a bit
> > just to get her to build and the patch I sent in does not have all the
> > misc hacks I had to add to get a build going. I thought it was just
> > me.....
> >
> > Thanks
> > Steven
> >
> > Do you Yahoo!?
> > Yahoo! Mail - You care about security. So do we.
> > http://promotions.yahoo.com/new_mail
> > _______________________________________________
> > Ros-dev mailing list
> > [e-mail]
> > http://reactos.com:8080/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Richard Campbell]

Actually, i did some checking, and i don't think it does, if one of our 
kernel people would like to take a look...

Richard

Alex Ionescu wrote:
> > > The question remains why does it hang so horribly with DBG = 1.
>
> Apparently something in irq.c according to Richard. I'll take a look 
> at it later this week if nobody else does. School starting again 
> Monday :(.
>
> Best regards,
> Alex Ionescu
>
> Alex Ionescu wrote:
> > DBG = 1 was on by default...I've commited a new DBG = 0 default 
> > config file.
> >
> > The question remains why does it hang so horribly with DBG = 1.
> >
> > Best regards,
> > Alex Ionescu
> >
> > Steven Edwards wrote:
> > > Hi,
> > >
> > > --- Alex Ionescu [e-mail] wrote:
> > > > Richard and I can't get the ros cvs build to boot...I get stuck on 
> > > > a black screen, and he gets a freeze on ndis.sys as well as a
> > > > blackscreen if running the bootcd.
> > > >
> > > > Can anyone confirm?
> > >
> > > I got this same problem....of course I had to hack my tree quite a bit
> > > just to get her to build and the patch I sent in does not have all the
> > > misc hacks I had to add to get a build going. I thought it was just
> > > me.....
> > >
> > > Thanks
> > > Steven
> > >    __________________________________
> > >
> > > Do you Yahoo!?
> > > Yahoo! Mail - You care about security. So do we.
> > > http://promotions.yahoo.com/new_mail
> > > _______________________________________________
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://reactos.com:8080/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://reactos.com:8080/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Casper Hornstrup]

Are you sure this is not the same problem that Hartmut reported?

Casper
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Richard Campbell
> Sent: 4. oktober 2004 13:49
> To: ReactOS Development List
> Subject: Re: [ros-dev] CVS Build Dead
>
> Actually, i did some checking, and i don't think it does, if 
> one of our kernel people would like to take a look...
>
> Richard
>
> Alex Ionescu wrote:
> > > > The question remains why does it hang so horribly with DBG = 1.
> >
> > Apparently something in irq.c according to Richard. I'll
>
> take a look
> > at it later this week if nobody else does. School starting again 
> > Monday :(.
> >
> > Best regards,
> > Alex Ionescu
> >
> > Alex Ionescu wrote:
> > > DBG = 1 was on by default...I've commited a new DBG = 0 default 
> > > config file.
> > >
> > > The question remains why does it hang so horribly with DBG = 1.
> > >
> > > Best regards,
> > > Alex Ionescu
> > >
> > > Steven Edwards wrote:
> > > > Hi,
> > > >
> > > > --- Alex Ionescu [e-mail] wrote:
> > > > > Richard and I can't get the ros cvs build to boot...I
>
> get stuck on
> > > > > a black screen, and he gets a freeze on ndis.sys as well as a 
> > > > > blackscreen if running the bootcd.
> > > > >
> > > > > Can anyone confirm?
> > > >
> > > > I got this same problem....of course I had to hack my
>
> tree quite a
> > > > bit just to get her to build and the patch I sent in does
>
> not have
> > > > all the misc hacks I had to add to get a build going. I
>
> thought it
> > > > was just me.....
> > > >
> > > > Thanks
> > > > Steven
> > > >    __________________________________
> > > >
> > > > Do you Yahoo!?
> > > > Yahoo! Mail - You care about security. So do we.
> > > > http://promotions.yahoo.com/new_mail
> > > > _______________________________________________
> > > > Ros-dev mailing list
> > > > [e-mail]
> > > > http://reactos.com:8080/mailman/listinfo/ros-dev
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://reactos.com:8080/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://reactos.com:8080/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[Hartmut Birr]

Hi,

the problem can be fixed by adding the option '--strip-debug' to kernel
targets in mkhelper.mk. This reduces the size of ntoskrnl and the drivers.
But I think that is not the real problem.

- Hartmut
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Casper Hornstrup
> Sent: Monday, October 04, 2004 2:12 PM
> To: 'ReactOS Development List'
> Subject: RE: [ros-dev] CVS Build Dead
>
> Are you sure this is not the same problem that Hartmut reported?
>
> Casper

[Hartmut Birr]

Hi,

the problem is fixed. Ntoskrnl is only loaded up to the end of the bss
section. The protection for pages after the bss section may not be changed.
The bug was a side effect of my last loader changes.

- Hartmut

[Casper Hornstrup]

Great. So I can recommit the patch?
> -----Original Message-----
> From: [e-mail] 
> [mailto:[e-mail]] On Behalf Of Hartmut Birr
> Sent: 4. oktober 2004 20:04
> To: 'ReactOS Development List'
> Subject: RE: [ros-dev] CVS Build Dead
>
> Hi,
>
> the problem is fixed. Ntoskrnl is only loaded up to the end 
> of the bss section. The protection for pages after the bss 
> section may not be changed.
> The bug was a side effect of my last loader changes.
> Hartmut
>
> Ros-dev mailing list
> [e-mail]
> http://reactos.com:8080/mailman/listinfo/ros-dev

[James Tabor]

Alex Ionescu wrote:
> Richard and I can't get the ros cvs build to boot...I get stuck on a 
> black screen, and he gets a freeze on ndis.sys as well as a blackscreen 
> if running the bootcd.
>
> Can anyone confirm?
>
> Best regards,
> Alex Ionescu

CVS 10/04/04 11:32:30 last change from arty.

<snip....>

DriverBase for \SystemRoot\System32\kbdus.dll: dd50f000
WL-Status: ReactOS is starting up...
(service/sctrl.c:120) ScDispatcherLoop() called
DriverBase for \SystemRoot\system32\drivers\tcpip.sys: dd989000
(network/router.c:536)(RouterStartup) Called.
(network/route.c:407)(RouteStartup) Called.
(network/neighbor.c:134)(NBStartup) Called.
domaininit starting
(1) Domain internet initializing
Registering protocols for internet
Domaininit done
(network/prefix.c:44)(CreatePLE) Called. IF (0xC081BF18)  Prefix (0xC0819FC8)  L
ength (8).
(network/prefix.c:46)(CreatePLE) Prefix (127.0.0.1).
(network/neighbor.c:277)(NBAddNeighbor) Called. Interface (0xC081BF18)  Address
(0xC0819FC8)  LinkAddress (0x0)  LinkAddressLength (0)  State (0x80)
Assertion 'Address->Type == IP_ADDRESS_V4' failed at network/neighbor.c line 279
KeBugCheckWithTf at ke/catch.c:164
Bug detected (code 1e param 0 0 0 0)
   KMODE_EXCEPTION_NOT_HANDLED

Breakpoint Exception: 3(0)
Processor: 0 CS:EIP 8:c0005974 <ntoskrnl.exe: 5974>
cr2 7ffdd000 cr3 1cf84000 Proc: c07e00c8 Pid: 6 <services> Thrd: c07ed270 Tid: 2
a
DS 10 ES 10 FS 30 GS 10
EAX: 00000051   EBX: 00000010   ECX: 00000000
EDX: 000003f8   EBP: dd861cc8   ESI: c003513a   ESP: dd861c54
EDI: dd861e8a   EFLAGS: 00000282 kESP dd861c54 kernel stack base dd85f000
Frames: <ntoskrnl.exe: 8482a> <tcpip.sys: 28c3d> <tcpip.sys: 1cacd> tcpip.sys:
6b51 <tcpip.sys: 47b0> <ntoskrnl.exe: 3523a> <ntoskrnl.exe: 366b6> <ntoskrnl.ex
e: 35a5> <77F83B34>

After a make clean, still the same,
James

[James Tabor]

Hi!
Anyone know what happen here? Is it a setup hive registry issue?
James

James Tabor wrote:
> CVS 10/04/04 11:32:30 last change from arty.
>
> <snip....>

[James Tabor]

The best fix for this, is to comment out most or all of the networking drivers
in hivesys.inf. The reasoning behind that is, there is no nic driver loaded.

FYI
James

James Tabor wrote:
> CVS 10/04/04 11:32:30 last change from arty.
>
> <snip....>
>
> DriverBase for \SystemRoot\System32\kbdus.dll: dd50f000
> WL-Status: ReactOS is starting up...
> (service/sctrl.c:120) ScDispatcherLoop() called
> DriverBase for \SystemRoot\system32\drivers\tcpip.sys: dd989000
> (network/router.c:536)(RouterStartup) Called.
> (network/route.c:407)(RouteStartup) Called.
> (network/neighbor.c:134)(NBStartup) Called.
> domaininit starting
> (1) Domain internet initializing
> Registering protocols for internet
> Domaininit done
> (network/prefix.c:44)(CreatePLE) Called. IF (0xC081BF18)  Prefix 
> (0xC0819FC8)  L
> ength (8).
> (network/prefix.c:46)(CreatePLE) Prefix (127.0.0.1).
> (network/neighbor.c:277)(NBAddNeighbor) Called. Interface (0xC081BF18)  
> Address
> (0xC0819FC8)  LinkAddress (0x0)  LinkAddressLength (0)  State (0x80)
> Assertion 'Address->Type == IP_ADDRESS_V4' failed at network/neighbor.c 
> line 279
> KeBugCheckWithTf at ke/catch.c:164
> Bug detected (code 1e param 0 0 0 0)
>   KMODE_EXCEPTION_NOT_HANDLED
>
> Breakpoint Exception: 3(0)
> Processor: 0 CS:EIP 8:c0005974 <ntoskrnl.exe: 5974>
> cr2 7ffdd000 cr3 1cf84000 Proc: c07e00c8 Pid: 6 <services> Thrd: 
> c07ed270 Tid: 2
> a
> DS 10 ES 10 FS 30 GS 10
> EAX: 00000051   EBX: 00000010   ECX: 00000000
> EDX: 000003f8   EBP: dd861cc8   ESI: c003513a   ESP: dd861c54
> EDI: dd861e8a   EFLAGS: 00000282 kESP dd861c54 kernel stack base dd85f000
> Frames: <ntoskrnl.exe: 8482a> <tcpip.sys: 28c3d> <tcpip.sys: 1cacd> 
> tcpip.sys:
> 6b51 <tcpip.sys: 47b0> <ntoskrnl.exe: 3523a> <ntoskrnl.exe: 366b6> 
> <ntoskrnl.ex
> e: 35a5> <77F83B34>

[art yerkes]

On Fri, 08 Oct 2004 16:05:57 +0000
James Tabor [e-mail] wrote:
> The best fix for this, is to comment out most or all of the networking drivers
> in hivesys.inf. The reasoning behind that is, there is no nic driver loaded.

I seriously think this is a cleaning failure in the make files rather than some
specific code at work.  I honestly can't see how that assertion can be made to
fail.

Does anybody else get this error?
-- 
Hey, Adam Smith, keep your invisible hands to yourself!