From owner-freebsd-current Mon Mar 3 21: 2: 7 2003 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 EC56837B401 for ; Mon, 3 Mar 2003 21:02:06 -0800 (PST) Received: from smtp-send.myrealbox.com (smtp-send.myrealbox.com [192.108.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3565843F93 for ; Mon, 3 Mar 2003 21:02:06 -0800 (PST) (envelope-from wa1ter@myrealbox.com) Received: from myrealbox.com wa1ter@smtp-send.myrealbox.com [66.126.109.103] by smtp-send.myrealbox.com with NetMail SMTP Agent $Revision: 3.32 $ on Novell NetWare via secured & encrypted transport (TLS); Mon, 03 Mar 2003 22:02:09 -0700 Message-ID: <3E64335A.60408@myrealbox.com> Date: Mon, 03 Mar 2003 21:02:18 -0800 From: walt Organization: none User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3b) Gecko/20030213 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: nvidia module panics today's kernel [03-03-03] Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My mini 'disaster' of earlier today was caused by the nvidia kernel module being autoloaded at boot, which causes an immediate kernel panic. The newest kernel seems fine until I try to load the module manually, at which time I still get the kernel panic even after re-compiling the module. Maxime, it looks like the nvidia module will need to be sculpted one more time. :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message