On Wed, Feb 24, 1999 at 08:05:23AM +0100, Bengt Kleberg wrote:
> > On Tue, Feb 23, 1999 at 05:57:42PM +0000, Peter Hunter wrote:
> > The tests in the perf directory all seem to give kernel GPFs
> Several tests do end up in kdb. One that seems to be running fine is
> 'iocall'. What do you get when running it? Also, do not forget to do a
> 'make init.hd'. This is sometimes (and I do not know when) neccessary,
> so I do it all the time.
iocall gives a kernel GPF like the rest, just after the test proper gets going. (In other words, the kernel boots, mounts the EROS partition, starts the test, goes into the idle loop and then dies. I don't get kdb at all - the systems halts, and I get a register dump. If I _could_ get kdb to start, I could at least get a stack trace. Is there any way to do this? I'm eager to do a little debugging.
I too always do a make init.hd, just in case.
Is it possible this is an AMD K6 issue? Or a motherboard issue?
There is one curiosity which I wondered about. In building the tests, unlike the rest of the kernel which now builds smoothly for me, the tests won't build just using make, since the compiler gives a warning "return type of `main' is not `int'" and sure enough the return type of main() is void in all the tests as far as I can see. Since they are compiled with -Werror, the warning is treated as an error, and the compile stops. I "fixed" this by simply removing the -Werror flag from the makevars.mk file when building these tests. Am I doing something wrong? Where do I read documentation which tells me how to build the tests?
Thanks, Bengt, for your help.