Re: Hello scenario gets stuck
Markus Partheymueller <[email protected]>
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <CAGLQ9fRnETiMDDeNR7wCyDC8CLH=jYhgrDF+qJ0Rvfk6nEADYA@mail.gmail.com> |
It seems to me as if bootstrap lists RAM regions beyond addressable memory.
I have a region that is being limited:
Limiting 'RAM' region [100000000, 43e5fffff] {33e600000} to [100000000,
10ea7c3ff] { ea7c400} due to 3024 MB limit
but in fact has to be dropped if I am not completely mistaken. When
dropping regions above ~0UL, everything works fine.
On 4 June 2013 19:27, Adam Lackorzynski <[email protected]> wrote:
> On Tue Jun 04, 2013 at 08:33:02 +0200, Markus Partheymueller wrote:
> > When I enable pagefault tracing, the last one I see is a fault at address
> > 0xffffffff on that instruction. The respective source code is in
> > /pkg/cxx/lib/tl/include/list_alloc:L182. I assume dereferencing c in
> > c->next is the problem?
>
> Yes, seems so. Coming back to the memory map provided by the bootloader,
> is there maybe a difference between the machine that works and this
> one? Maybe you could also try to nail down where that possible -1 is
> written e.g. with some if's at the write locations.
>
>
> Adam
> --
> Adam [email protected]
> Lackorzynski http://os.inf.tu-dresden.de/~adam/
>
_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers