Re: 1.0.9b-pre2 uploaded

From: Jesse Pollard <pollard@cats-chateau.net>
Subject: Re: 1.0.9b-pre2 uploaded
Date: Sun, 12 Mar 2000 22:23:33 -0600

Next Article (by Subject): Re: 1.0.9b-pre2 uploaded ao@morpork.shnet.org (A. Ott)
Previous Article (by Subject): Re: 1.0.9b-pre2 uploaded Jesse Pollard
Top of Thread: 1.0.9b-pre2 uploaded ao@morpork.shnet.org (A. Ott)
Next in Thread: Re: 1.0.9b-pre2 uploaded ao@morpork.shnet.org (A. Ott)
Articles sorted by: [Date] [Author] [Subject]

Hi,
A followup on SMP testing -
1. I've finished reconfiguring my system. I now have a single 2G partition for
   testing. The test systems only use the one partition + swap. (Haven't
   finished web reconfig...)
2. I did load 2.2.13, and 2.3.47 onto it. The problems still occur -
   a. once I traced it down to a page fault (looked like disk failure...)
	this under 2.2.13
   b. once I traced it to the keyboard, also under 2.2.13
   c. Under 2.3.47, I couldn't get any output after the problem occured. I could
	type in 6 characters, and recieve the echo. Then it hung. No output
 	dump trace ever.
   d. Under 2.3.47, I tried a maintence kernel, but the same thing occured.

In all three cases I did a little extra testing while booting:

I added thefollowing code to rc.S, after enabling swap and running /bin/update:

if [ "`/bin/uname -r`" != "2.2.13.SMP" ]; then
    echo "CRASH TEST - echo of output"
    echo "CRASH TEST" >/CRASH.TEST
    echo "append test" >>/CRASH.TEST
    echo "after append test"
    echo " reading contents of CRASH.TEST"
    cat /CRASH.TEST
    echo "beginning keyboard read test"
    echo "beginning keyboard read test" >>CRASH.TEST
    read junk
    echo "READ ...${junk}..." >>CRASH.TEST

    echo " reading contents again:"
    cat /CRASH.TEST
fi

When I boot the system I do have the disk write enabled to see if anything
occured. The failure only occurs at the "read junk" line. I do get the
contents of the CRASH.TEST file output, even though it doesn't quite make it
to disk (might if I put a sync in there...)

One other thing I noticed -- from another post (AUTH problems):

> kernel: rsbac_reg_init(): Initializing RSBAC: REG module registration Mar 8
> 12:20:05 ganja kernel: rsbac_init(): Starting rsbacd thread Mar  8 12:20:05
> ganja kernel: rsbac_init(): Setting RSBAC auto timer Mar  8 12:20:05 ganja 
> kernel: rsbac_init(): Ready.

I don't get the line "kernel: rsbac_init(): Ready.". This may be due to
it being the very first boot.

A default /rsbac/useraci file was created.

If you have some debugging suggestions/configuration changes I'm ready to
try them out.
-- 
-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@cats-chateau.net

Any opinions expressed are solely my own.
-
To unsubscribe from the rsbac list, send a mail to
majordomo@morpork.shnet.org with
unsubscribe rsbac
as single line in the body.

Go to Compuniverse LWGate Home Page.