Re: Two Oops with aic7xxx in 2.2.10

Kurt Huwig (kurt@huwig.de)
Wed, 29 Sep 1999 15:02:18 +0200

"Richard B. Johnson" wrote:
> On Wed, 29 Sep 1999, Kurt Huwig wrote:
> > The first oops ('oops') appears, when I have my hardware problem with my
> > SCSI-disk; sometimes it is not correctly recognized by the BIOS. The
> > name shows like C_N_E_ _F_4_0_s, i.e. every second character is broken,
> > where '_' is a weird character.
> >
> A problem with WORD transfers. It didn't negotiate for sync
> transfers properly upon startup. This is usually caused by termination
> problems.

I thought this, too, but the machine is terminated correctly with an
active terminator. So I think the drive went bad.

> However, no machine can be considered to be working if
> it's over-clocked. When you over-clock the CPU (and its interface chips),
> you put timing out-of-spec. All bets are off. The fact that a CPU manages
> to boot an OS when it's over-clocked means nothing.

The CPU is overclocked, not the peripheral. It runs for about 5 month
without crashes besides this boot effects, that only happen after a fsck
at boot time.

Kurt

-- 
----------------------------------------------------------------
Let me make myself perfectly clear:  Step 1: Find plan!
                                     Step 2: Save world!
Let's get crackin'...                Step 3: Get outta my house!


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/