On Sat, Feb 12, 2000 at 04:12:13 -0600, Jim Bryant wrote:
> I seem to have had a problem with the ahc driver since around the
> beginning of the year. Due to mail problems, this is the first I've
> been able to report this.
>
> I am running a Tyan Thunder2 [DLUA-1696] motherboard with
> -current/SMP. This board has the aic7895 [3940UW] on it. The error I
> get causes immediate panic on boot with the message:
>
> { MPARERR, "Scratch or SCB Memory Parity Error" },
>
> The only way I have found to fix this seems to be to comment out the
> enabling of scratchpad SRAM parity checking:
[ ... ]
> I don't know if this is a side effect of this change [as I can't get
> it running with the parity checking enabled], but i get a system
> freeze requiring hard reset when using my tape drive with my change.
> I don't understand how that can happen as a result of commenting out
> this one line, so I cannot say that it is a related or seperate
> issue. All I know is that everything works fine with a kernel from
> before the driver was changed in January.
>
> Since I only managed to resubscribe to the -lists today, I was
> unaware of a code freeze at the moment for -current, but this is a
> *FATAL* bug in the ahc code on this particular motherboard.
>
> I would like to hear from other Tyan DLUA-1696 users as to whether or
> not they are experiencing the same boot panic using the stock ahc
> driver, also if they experience bus problems when dumping to tape when
> using the above fix.
You need to upgrade to the latest -current. I believe Justin fixed this on
Wednesday:
----------------------------
revision 1.28
date: 2000/02/09 21:00:22; author: gibbs; state: Exp; lines: +23 -9
Fix parity error detection logic for aic7880 and aic7895 chips during
the probe of external SRAM.
Approved by: [EMAIL PROTECTED]
----------------------------
Ken
--
Kenneth Merry
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
