Peter Wemm wrote:
> Richard Todd wrote:
> > In message <[EMAIL PROTECTED]>, Peter Wemm write
s:
> > >Richard Todd wrote:
> > >
> > >> < No crashes as of here
> > >> pushl $begin /* jump to high virtualized add
> > >ress */
> > >> ret
> > >>
> > >> /* no
Richard Todd wrote:
> In message <[EMAIL PROTECTED]>, Peter Wemm writes:
> >Richard Todd wrote:
> >
> >> < No crashes as of here
> >>pushl $begin /* jump to high virtualized add
> >ress */
> >>ret
> >>
> >> /* now running relocated at KERNBASE where t
In message <[EMAIL PROTECTED]>, Peter Wemm writes:
>Richard Todd wrote:
>
>> < No crashes as of here
>> pushl $begin /* jump to high virtualized add
>ress */
>> ret
>>
>> /* now running relocated at KERNBASE where the system is linked to run */
>> b
Richard Todd wrote:
[..]
> The pushl and ret is where the boot code is jumping to "begin:" at its proper
> virtual address after the page tables are setup. I'm guessing that
> create_pagetables is somehow losing and creating bogus page tables such that
> the jump to the kernel virtual address spa
Richard Todd wrote:
> < No crashes as of here
> pushl $begin /* jump to high virtualized add
ress */
> ret
>
> /* now running relocated at KERNBASE where the system is linked to run */
> begin:
> < crashes before it gets here!!!
> /* se
On my system (dual PII/400 running -current), I've noticed for some time that
if I build a kernel with too many device drivers in it (where "too many" seems
to correspond to text size >3M for the resulting kernel), the system reboots
itself immediately upon booting with the new kernel. Other peop
