From owner-freebsd-current Sat Oct 17 18:27:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14772 for freebsd-current-outgoing; Sat, 17 Oct 1998 18:27:37 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles113.castles.com [208.214.165.113]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA14757 for ; Sat, 17 Oct 1998 18:27:30 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA08718; Sat, 17 Oct 1998 18:31:47 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810180131.SAA08718@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tom Jackson cc: Karl Pielorz , Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: panic In-reply-to: Your message of "Sat, 17 Oct 1998 20:23:05 CDT." <19981017202305.A12163@TOJ.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 17 Oct 1998 18:31:47 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > nm tells me module_register (dugh) not module_init. > > For me, no amount of dumps on anything will produce a crash dump. On my > laptop it just says bad dump device and on my server (which is not crashing > now) I get a count down but no crash modules are produced. You can't write a dump to disk until you've found a disk to write to. Module_register is way too early. > btw, these are 100% elf and I don't think the panic is a smp problem. If you're running an ELF kernel, make sure your /boot/loader is up to date. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message