This does not seem to be the case here as the VM system has not yet
started up, and thus the kmalloc being used is still just stealing
physical pages.
Ben
On Fri, 23 Mar 2001, Alexandra Fedorova wrote:
vaddr does not look valid. Your kmalloc() is probably
overwriting some
instructions or data that it should not.
On Fri, 23 Mar 2001, Ben Zotto wrote:
Hi all,
We are getting a pretty unusual panic during bootstrap:
panic: Fatal exception 2 in kernel mode
panic: EPC 0x80006ca0, exception vaddr 0x4
panic: I can't handle this... I think I'll just die now...
This happens after the lamebus configuration when the console gets
attached to the file system. I've traced the code well into the
nitty-gritty FS subsystems, and have given up on finding the exact line of
code it fails on. Unfortunately, tracing it this deep tells us nothing,
as none of that code is ours.
Oddly, we saw very similar random problems (failure deep within the
filesystem stuff) while doing asst2, and by just changing schedulers (!)
we got things up and running OK (that doesn't work this time).
Can anyone shed light on some probably cause for this kind of issue, or
has anyone seen anything like it before? Am I missing something
obvious? Any and all suggestions appreciated! Thanks.
Regards from the scenic SC basement,
Ben
_______________________________________________
cs161-list mailing list
cs161-list(a)fas.harvard.edu
http://www.fas.harvard.edu/mailman/listinfo/cs161-list
_______________________________________________
cs161-list mailing list
cs161-list(a)fas.harvard.edu
http://www.fas.harvard.edu/mailman/listinfo/cs161-list