From nobody@FreeBSD.org Thu Feb 26 14:57:42 2009 Return-Path: Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67F071065673 for ; Thu, 26 Feb 2009 14:57:42 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 3C0E98FC13 for ; Thu, 26 Feb 2009 14:57:42 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id n1QEvfpZ055919 for ; Thu, 26 Feb 2009 14:57:41 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id n1QEvfSv055918; Thu, 26 Feb 2009 14:57:41 GMT (envelope-from nobody) Message-Id: <200902261457.n1QEvfSv055918@www.freebsd.org> Date: Thu, 26 Feb 2009 14:57:41 GMT From: Ari Sovijärvi To: freebsd-gnats-submit@FreeBSD.org Subject: Device crypto makes the kernel unbootable X-Send-Pr-Version: www-3.1 X-GNATS-Notify: >Number: 132129 >Category: kern >Synopsis: [crypto] Device crypto makes the kernel unbootable >Confidential: no >Severity: non-critical >Priority: medium >Responsible: vwe >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Feb 26 15:00:11 UTC 2009 >Closed-Date: Sun Nov 21 00:56:34 UTC 2010 >Last-Modified: Sun Nov 21 00:56:34 UTC 2010 >Originator: Ari Sovijärvi >Release: FreeBSD 7.1-RELEASE-p3 >Organization: - >Environment: FreeBSD basestar2 7.1-RELEASE-p3 FreeBSD 7.1-RELEASE-p3 #3: Thu Feb 26 01:13:12 EET 2009 root@basestar2:/usr/obj/usr/src/sys/RAINFALL sparc64 >Description: I was following handbook's advice on enabling geom_eli and recompiled the kernel with the following line added to the default config: device crypto The resulting kernel seems to skip hardware detection (including HDDs) and then fails as it has no root device. From what I gather from the mailing lists, others have also hit this bug, but it seems to only happen on some platforms, so far I have found posts about it happening on sparc64 and PowerPC. Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE-p3 #2: Wed Feb 25 22:05:18 EET 2009 root at basestar2:/usr/obj/usr/src/sys/RAINFALL Timecounter "tick" frequency 548000000 Hz quality 1000 real memory = 1073741824 (1024 MB) avail memory = 1035673600 (987 MB) cpu0: Sun Microsystems UltraSparc-IIe Processor (548.00 MHz CPU) kbd0 at kbdmux0 nexus0: cryptosoft1: mem 0x1fe00000000-0x1fe0000ffff,0x1fe01000000-0x1fe010 cryptosoft0: on nexus0 nexus0: type unknown (no driver attached) Timecounters tick every 1.000 msec Trying to mount root from ufs:/dev/mirror/raid0a Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> ufs:/dev/mirror/raid0a Trying to mount root from ufs:/dev/mirror/raid0a Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0a ? List valid disk boot devices Abort manual input mountroot> panic: Root mount failed, startup aborted. >How-To-Repeat: Recompile the kernel on sparc64 or ppc with 'device crypto' added to the configuration, boot the new kernel. >Fix: >Release-Note: >Audit-Trail: State-Changed-From-To: open->feedback State-Changed-By: vwe State-Changed-When: Sat Aug 21 20:28:56 UTC 2010 State-Changed-Why: Ari, 7.1-RELEASE is quite old, as is your report. Sorry to see it's still open. Should the problem still persist, can we please see 1) a verbose boot dmesg and 2) your kernel configuration file? I'm pretty sure, crypto worked even in 7.1 Responsible-Changed-From-To: freebsd-bugs->vwe Responsible-Changed-By: vwe Responsible-Changed-When: Sat Aug 21 20:28:56 UTC 2010 Responsible-Changed-Why: track http://www.freebsd.org/cgi/query-pr.cgi?pr=132129 From: =?ISO-8859-1?Q?Ari_Sovij=E4rvi?= To: vwe@FreeBSD.org, bug-followup@FreeBSD.org Cc: Subject: kern/132129: [crypto] Device crypto makes the kernel unbootable Date: Sun, 22 Aug 2010 00:35:15 +0300 On 21/08/10 23:30, vwe@FreeBSD.org wrote: > Synopsis: [crypto] Device crypto makes the kernel unbootable > Ari, > 7.1-RELEASE is quite old, as is your report. Sorry to see it's still open. > Should the problem still persist, can we please see 1) a verbose boot dmesg and > 2) your kernel configuration file? > I'm pretty sure, crypto worked even in 7.1 AFAIK this was never fixed, but it was worked around. I'm no expert in the kernel internals, but to my understanding, for some reason having the crypto modules build-in prevents the system bus driver from loading, which again results in being unable to mount the root as the HDD controllers are nowhere to be found. It was worked around by building crypto as modules and loading them later on. This problem appeared in sparc64 and PPC, but not on i386 and amd64. Identical issue was reported here: http://lists.freebsd.org/pipermail/freebsd-bugs/2009-June/035852.html I also found several other sighting of this bug, but no solutions or patches. My current machine, HP Proliant, is amd64 thus I'm no longer affected by this issue nor can I test the 8-series kernel with the old hardware. The last kernel tested to crash was 7.1-p5. -- Ari Sovijärvi http://apz.fi/ State-Changed-From-To: feedback->closed State-Changed-By: marius State-Changed-When: Sun Nov 21 00:54:50 UTC 2010 State-Changed-Why: Close; this is a dupe of PR136123 and the submitter can no longer test patches. http://www.freebsd.org/cgi/query-pr.cgi?pr=132129 >Unformatted: