From owner-freebsd-current Sun May 23 19:22:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 07CD914D5A for ; Sun, 23 May 1999 19:22:44 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id WAA00560 for ; Sun, 23 May 1999 22:22:43 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <199905240222.WAA00560@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@freebsd.org From: "Louis A. Mamakos" Subject: panic() in devfs_makelink() with recent -current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 May 1999 22:22:43 -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently tried building a new kernel after quite a bit, and I get a panic while the system's booting in devfs_makelink, apparently being called from fd_attach(). Is DEVFS and the new-bus code hopelessly incompatable, and should I just unconfigure DEVFS? Or is this something that I can dig into a bit more and find a relatively simple fix? I copied down some of what the trace command spewed in ddb, and it appears that the first argument to devfs_makelink is 0, which is sorta weird.. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message