Date: Fri, 18 Sep 1998 10:57:38 +0200 From: felix@halef.rhrz.uni-bonn.de To: aic7xxx@FreeBSD.ORG Subject: Re: pre10 on a 2940u2w still shows BRKADRINT Message-ID: <19980918105435.A1704@halef.rhrz.uni-bonn.de> In-Reply-To: <3.0.5.32.19980917160154.008043b0@mail.cobaltmoon.com>; from Neil Magedman on Thu, Sep 17, 1998 at 04:01:54PM -0700 References: <3.0.5.32.19980917160154.008043b0@mail.cobaltmoon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, I've got the same problem here with a standard kernel 2.0.35 patched with the pre10. However, the those errormessages (0x17 1.time 0x1 after that) do show up only after reset, when the machine is warm. Turning off power for a while helps. While the system is up, i can't see any problems. My System is a P2 Asus P2BS. On Thu, Sep 17, 1998 at 04:01:54PM -0700, Neil Magedman wrote: > ... > I installed pre10 using the the rpm kernel-* files. After an initial > hurdle of not having an initrd prepared (the pre5 was monolithic), I ran > into a similar BRKADRINT bug. Whereas the pre5 would loop with > Data-Path Ram Parity Error > PCI Error Detected > (scsi 0) SEQADDR = 0x50 > the pre10 kernel would loop with > Data-Path Ram Parity Error > (scsi 0) SEQADDR = 0x17d [the first time] > (scsi 0) SEQADDR = 0x1 [subsequent times] ... > regards, > neil > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-aic7xxx" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-aic7xxx" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980918105435.A1704>