Re: Current kernel with http://gnats.netbsd.org/39965 and pmap patches

"T. Makinen" <[email protected]>
Newsgroups gmane.os.netbsd.ports.atari
Message-ID <[email protected]>
On Fri, Dec 19, 2008 at 2:47 PM, Izumi Tsutsui <[email protected]> wrote:
> [email protected] wrote:
>
>> I tried kernel with m68k/m68k/pmap_motorola.c and it failed with 030 as well.
>> Kernel prints following error:
>> panic: pool_put: buf8k: page header missing.
>
> Such pool panic generally happens on memory corruptions.
> Could you see any more info with options DIAGNOSTIC?

I fixed atari/dev/md_root.c which had problem with DIAGNOSTIC kernel (stopped
at assertion: bp->b_refcnt > 0). Funny thing is that problem seems to be
root cause for 68030 cpu installation panics and it no longer exist with fixed
/atari/dev/md_root.c. I'm no longer wondering why kernel panicked only with
installation :)

Here's links to patched ATARITT and FALCON kernels:
http://koti.welho.com/tmakinen/atari/netbsd-current-ATARITT-20081220.gz
http://koti.welho.com/tmakinen/atari/netbsd-current-FALCON-20081220.gz

> BTW, is the LOCK errors described in PR 39965 gone with
> accounting idepth patch? If so we should apply the changes first.

I never experienced LOCK errors. Maybe David R. can verify if that problem
still exist ?

Index: ../dev/md_root.c
===================================================================
RCS file: /cvsroot/src/sys/arch/atari/dev/md_root.c,v
retrieving revision 1.26
diff -u -r1.26 md_root.c
--- ../dev/md_root.c	4 Nov 2008 17:08:45 -0000	1.26
+++ ../dev/md_root.c	20 Dec 2008 00:47:23 -0000
@@ -233,6 +233,7 @@
 		bp->b_bcount = rsp->chunk;
 		bp->b_data   = rsp->bufp;
 		bp->b_error  = 0;
+		bp->b_refcnt++;

 		/* Initiate read */
 		(*rsp->strat)(bp);
@@ -313,6 +314,7 @@
 		bp->b_bcount = min(rsp->chunk, nbyte);
 		bp->b_data   = buf;
 		bp->b_error  = 0;
+		bp->b_refcnt++;

 		/* Initiate read */
 		(*rsp->strat)(bp);

-Tuomo
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.