Bug 25230

Summary: ... SCB Memory Parity Error at seqaddr = 0x1
Product: Base System Reporter: feczo <feczo>
Component: miscAssignee: Justin T. Gibbs <gibbs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Unspecified   
Hardware: Any   
OS: Any   

Description feczo 2001-02-20 16:20:01 UTC 
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
Comment 1 dwmalone 2001-02-20 16:44:35 UTC 
On Tue, Feb 20, 2001 at 08:14:31AM -0800, feczo@koli.kando.hu wrote:
> ... 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)

SCBs are to do with SCSI, so it could be that your scsi
card is busted.

	David.
Comment 2 Justin T. Gibbs freebsd_committer freebsd_triage 2001-02-27 04:33:35 UTC 
State Changed
From-To: open->feedback

Your motherboard uses an aic7895.  The aic7xxx driver in 4.2R had some 
issues with this chip.  I believe that all aic7895 issues have been 
resolved in 4.2-stable.  Please upgrade your kernel and report if your 
problem still persists.
Comment 3 Justin T. Gibbs freebsd_committer freebsd_triage 2001-02-27 04:33:35 UTC 
Responsible Changed
From-To: freebsd-bugs->gibbs

my driver.
Comment 4 Jeroen Ruigrok van der Werven freebsd_committer freebsd_triage 2001-11-15 19:19:22 UTC 
State Changed
From-To: feedback->closed

No feedback, assume fixes helped person originating PR.