Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Feb 2001 08:14:31 -0800 (PST)
From:      feczo@koli.kando.hu
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   misc/25230: ... SCB Memory Parity Error at seqaddr = 0x1
Message-ID:  <200102201614.f1KGEV456525@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         25230
>Category:       misc
>Synopsis:       ... SCB Memory Parity Error at seqaddr = 0x1
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Feb 20 08:20:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     Szabolcs Feczak
>Release:        4.2
>Organization:
Kando Kalman Dormority
>Environment:
FreeBSD bsdevil.koli 4.2-RELEASE FreeBSD 4.2-RELEASE #2: Tue Feb 13 20:41:14 CET 2001     root@bsdevil.koli:/usr/src/sys/compile/BSDEVIL  i386

>Description:
I've set up a gateway with 4 interfaces, 2 private network and dmz.
I'm using private address ranges on lan and using NAT to reach
the outside world from the workstations, I've also set up transparent
proxy with oops. The machine based on the Intel DK440LX mainboard,
using a 4GB scsi-2 disk and 128Mb of ram with 2 Compaq netelligent PCI,
1 3Com 509B combo ISA, and 1 Digital chip based PCI card.

The machine frozes if it gets more than some connection to NAT,
and after restart during booting the kernel I see the following
displayed : 

... SCB Memory Parity Error at seqaddr = 0x1
And several other numbers 5 or 6 times, but I can't read, because
the text is shaking (alternately prints the one line and the other)

I'v changed memory bank, and changed memory card 2 times ...
First time a similar 100Mhz one second time a brand (Memory Technology)
133Mhz one. I have changed the motherboard (same type), but problem
still exist.

This message only appears at kernel boot time and it won't start at all,
just shaking.
Before the freeze I can't see any suspicious message.


I don't know maybe it it is still a hardware problem 
(but some other os was working good on this hw config, but I've heard, that bsd is more sensitive for good hw components) or just 
I'm too lame to set
some of the kernel parameters ....etc, but I can't find it (what where and why)
Or just hit a bug ?
>How-To-Repeat:
unpredictable
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102201614.f1KGEV456525>