From owner-freebsd-questions Thu Nov 19 19:41:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04454 for freebsd-questions-outgoing; Thu, 19 Nov 1998 19:41:35 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA04447 for ; Thu, 19 Nov 1998 19:41:33 -0800 (PST) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-121.laker.net [208.0.233.21]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id WAA26391; Thu, 19 Nov 1998 22:40:59 -0500 Message-Id: <199811200340.WAA26391@laker.net> From: "Steve Friedrich" To: "Jerry Bell" , "questions@FreeBSD.ORG" Date: Thu, 19 Nov 1998 22:38:54 -0500 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Random and frequent reboots and lockups with 3.0 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 19 Nov 1998 20:29:54 -0500, Jerry Bell wrote: >Bad DMI table checksum! This error message was in your dmesg. How long has this been occurring ? AFAIK, the DMI table is a table that the BIOS uses to communicate info about PNP devices in the system. I would pull a daughter card and see if the BIOS updates the DMI and corrects the checksum. I suspect the problem may be caused by bogus data in the table being used by FreeBSD in spite of the checksum error. If that's the case, it indicates a bug in FreeBSD, in that it should NOT use the data if it detects a checksum... Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message