From owner-freebsd-questions Fri Oct 27 12:57:39 2000 Delivered-To: freebsd-questions@freebsd.org Received: from front5m.grolier.fr (front5m.grolier.fr [195.36.216.55]) by hub.freebsd.org (Postfix) with ESMTP id F404F37B4FE for ; Fri, 27 Oct 2000 12:57:34 -0700 (PDT) Received: from nas22-34.vlt.club-internet.fr (nas22-34.vlt.club-internet.fr [195.36.172.34]) by front5m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with ESMTP id VAA14254; Fri, 27 Oct 2000 21:56:53 +0200 (MET DST) Date: Fri, 27 Oct 2000 19:57:31 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-Sender: groudier@linux.local To: Joey Garcia Cc: questions@FreeBSD.ORG, Matthew Jacob Subject: Re: sym0 error messages (and kernel panic) - what do these messages mean? (fwd) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Oct 2000, Matthew Jacob wrote: > ---------- Forwarded message ---------- > Date: Tue, 24 Oct 2000 20:24:09 -0700 (PDT) > From: Joey Garcia > To: questions@FreeBSD.ORG > Subject: sym0 error messages (and kernel panic) - what do these messages > mean? >=20 >=20 > Greetings! >=20 > Seems like I spoke too soon. After retrying the same > I/O test (untaring the ports.tar.gz) to make sure > everything was okay, it gave me a kernel panic. Here > is the exact panic message. What could it mean? How > can I fix it? >=20 > panic: assertion "i && sym_get_cam_status(cp->cam_ccb) > =3D=3D CAM_REQUEUE_REQ" failed: file > "../../dev/sym/sym_hipd.c", line 5208 This assertion wasn't expected to fail. ;-) The involved code is only triggerred when a pending SCSI command=20 times out or when the driver is asked by CAM for resetting a device. This happens generally when the SCSI BUS is stalled due to=20 something bad having happened. > --- Joey Garcia wrote: > > Date: Tue, 24 Oct 2000 20:07:34 -0700 (PDT) > > From: Joey Garcia > > Subject: Tekram 390F and sym0 Error messages - what > > do these messages mean? > > To: questions@freebsd.org > >=20 > > Greetings!! > >=20 > > I have FreeBSD 4.1.1 installed with a Tekram 390F > > SCSI > > card and a Compaq (Seagate) ST34371W hardrive. I > > had > > posted a message on the list before about some > > problems. Since then I have updated the BIOS on the > > SCSI card. I did the ran the same I/O intensive > > application (untar the ports tree - port.tar.gz) and > > instead of it panicing (spelling?) it gave some > > error > > messages and went on. > >=20 > > What do these messages mean? Is there something > > wrong > > with my hardware/software configuration? Could it > > be > > the hardrive? I hear so many wonderfull things > > about > > the Tekram 390F that I am convinced it couldn't be > > the > > card. > >=20 > > The messages are listed below. > > Oct 24 20:00:00 bsd newsyslog[299]: logfile turned > > over > > Oct 24 20:01:28 bsd login: ROOT LOGIN (root) ON > > ttyv1 > > Oct 24 20:03:00 bsd /kernel: sym0:0: ERROR (81:0) > > (e-ae-0) (f/9d) @ (scripta 90:1e000000). > > Oct 24 20:03:00 bsd /kernel: sym0: script cmd =3D > > 82030000 The error condition corresponds to an "ILLEGAL INSTRUCTION DETECTED"=20 The messages seem to indicate that the SCRIPTS tried to execute a MOVE instruction of zero byte, which is illegal. > > Oct 24 20:03:00 bsd /kernel: sym0: regdump: da 10 80 > > 9d 47 0f 00 0f 00 0e 80 ae 80 00 06 08 00 66 ff 05 > > 2a > > ff ff ff. > > Oct 24 20:03:00 bsd /kernel: > > (noperiph:sym0:0:-1:-1): > > SCSI BUS reset detected. > > Oct 24 20:03:21 bsd /kernel: sym0:0: message c sent > > on > > bad reselection. > >=20 > >=20 > > Thank you for all the help! Could you describe your hardware. I wouldn't be surprised if it encounters memory problems. Obviously, it is just my first idea and I may be wrong. The driver may also have been confused by some weird SCSI error, but I would prefer to be sure that your hardware is sane prior to any further investigation. If, as numerous FreeBSD users, you also have a Linux distribution installed, building the Linux kernel a couple of times will have every chance to trigger a signal 11, if your system has memory problems. Don't ask me why the Linux kernel build detects memory problems far better than BSD kernel build, just trust me about. :-) Obviously, you may run some academic memory testers, instead. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message