From owner-freebsd-current@FreeBSD.ORG Sat Nov 6 17:46:47 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A02D16A4CE for ; Sat, 6 Nov 2004 17:46:47 +0000 (GMT) Received: from amitabha.axelero.hu (fe04.axelero.hu [195.228.240.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 955A743D46 for ; Sat, 6 Nov 2004 17:46:45 +0000 (GMT) (envelope-from gmicsko@szintezis.hu) Received: from amitabha (localhost-02 [127.0.2.1]) by amitabha.axelero.hu (8.12.11/8.12.11) with SMTP id iA6Hkiir035360; Sat, 6 Nov 2004 18:46:44 +0100 (CET) Received: from fe04.axelero.hu [127.0.2.1] via SMTP gateway by amitabha [195.228.240.92]; id A08A1B45E57 at Sat, 06 Nov 2004 18:46:44 +0100 Received: from 148.20-182-adsl-pool.axelero.hu (148.20-182-adsl-pool.axelero.hu [81.182.20.148]) (authenticated bits=0) by fe04.axelero.hu (8.12.11/8.12.11) with ESMTP id iA6HkgF6035349; Sat, 6 Nov 2004 18:46:43 +0100 (CET) From: Gabor MICSKO To: Hans Lambermont In-Reply-To: <20041106165147.GF79763@moya.lambermont.dyndns.org> References: <1099672914.7059.13.camel@alderaan.trey.hu> <20041106165147.GF79763@moya.lambermont.dyndns.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-k4AvWI/ajO95OA71y0RX" Message-Id: <1099762840.11450.15.camel@alderaan.trey.hu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 06 Nov 2004 18:40:41 +0100 cc: freebsd-current@freebsd.org Subject: Re: 5.3-RC2: Fatal trap 19: non-maskable interrupt trap while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 17:46:47 -0000 --=-k4AvWI/ajO95OA71y0RX Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Quote from Matthew Dillon: ":Type '?' for a list of commands, 'help' for more detailed help. :OK boot -Dh :... :fwohci0: OHCI version 1.10 (ROM=3D1) :NMI ISA b1, EISA ff :RAM parity error, likely hardware failure. : :Fatal trap 19: non-maskable interrupt trap while in kernel mode :instruction pointer =3D 0x8:0xc01e3b6e :... :interrupt mask =3D net tty bio cam :kernel: type 19 trap, code=3D0 :Stopped at fwohci_init+0xfa: movl %ecx,%edi :db> tr :fwohci_init(c9823000,c604af18) at fwohci_init+0xfa Ok. Hmm. It fails in the same place. The code in question is this: ... /* Available Isochrounous DMA channel probe */ OWRITE(sc, OHCI_IT_MASK, 0xffffffff); OWRITE(sc, OHCI_IR_MASK, 0xffffffff); reg =3D OREAD(sc, OHCI_IT_MASK) & OREAD(sc, OHCI_IR_MASK); OWRITE(sc, OHCI_IT_MASKCLR, 0xffffffff); OWRITE(sc, OHCI_IR_MASKCLR, 0xffffffff); for (i =3D 0; i < 0x20; i++) if ((reg & (1 << i)) =3D=3D 0) break; ... It fails just after the OREAD's. My guess is that something in the fwohci init code is blowing up the system hardware. OpenBSD has similar but slightly different initialization code, but the differences shouldn't account for the failure.=20 The question is... when you booted up OpenBSD did it probe the firewire interface at all? NetBSD also has similar code, but in NetBSD's case it also clears the command pointers after probing the transmit bitmap. But this occurs after the crash point. In anycase, my guess is that if you do not use firewire you can compile up a DragonFly kernel that does not probe the firewire controller and it will work. It is clearly NOT a ram problem... it's definitely a firewire initialization issue that is causing the firewire hardware to blow up the system bus. If you have the ability to compile up DragonFly kernels with some patches and want to try to get the firewire working I could put together a patch for you to try." Please read this thread: http://marc.theaimsgroup.com/?t=3D109967176800001&r=3D1&w=3D2 I have problem ONLY with FreeBSD 5.x and DragonFly BSD. IMHO this is a FreeBSD specific thing. CPU not overclocked, memtest86 said my memory module is OK. I tested this thing six different brand new memory module. Maybe this is a firewire specific problem.=20 2004-11-06, szo keltez=E9ssel 17:51-kor Hans Lambermont ezt =EDrta: > Gabor MICSKO wrote: >=20 > > I've tried to install FreeBSD 5.3-RC2, FreeBSD 5.3-RC*, FreeBSD > > 5.2.1-RELEASE, FreeBSD 5.2-RELEASE on my amd64 based laptop, but at > > boot kernel is paniced.=20 >=20 > Just to be clear about the obvious: >=20 > > NMI ISA a1, EISA ff > > RAM parity error, likely hardware failure. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >=20 > I'm not surprised you get a kernel panic with this system. Your RAM has > faults. Unless you're absolutely sure this is not the case and the NMI > complaint is bogus (I see you've tested with various other OSes, and > even then it might be true) I suggest swapping RAM and trying again. >=20 > regards, > Hans Lambermont --=20 Micsk=F3 G=E1bor HP Accredited Platform Specialist, System Engineer (APS, ASE) Szint=E9zis Computer Rendszerh=E1z Rt. =20 H-9021 Gy=F5r, Tihanyi =C1rp=E1d =FAt 2. Tel: +36-96-502-216 Fax: +36-96-318-658 E-mail: gmicsko@szintezis.hu Web: http://www.hup.hu/ GPG Key fingerprint: 6FA1 D8BF 3C73 0570 ED5D 82AC A3BE 4E6A CF95 5F50 --=-k4AvWI/ajO95OA71y0RX Content-Type: application/pgp-signature; name=signature.asc Content-Description: Ez az =?ISO-8859-1?Q?=FCzenetr=E9sz?= =?ISO-8859-1?Q?_digit=E1lis?= =?ISO-8859-1?Q?_al=E1=EDr=E1ssal?= van =?ISO-8859-1?Q?ell=E1tva?= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBjQyYo75Oas+VX1ARAuDhAJoCtliLY1ccMoloUB2uxx1N1FHq7ACfeckL TiUENgUe06Tx9o0mfEqeKvg= =CSdK -----END PGP SIGNATURE----- --=-k4AvWI/ajO95OA71y0RX--