From owner-freebsd-current@FreeBSD.ORG Sat Oct 29 21:26:30 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18D441065670 for ; Sat, 29 Oct 2011 21:26:30 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id D12AE8FC08 for ; Sat, 29 Oct 2011 21:26:29 +0000 (UTC) Received: by qyg14 with SMTP id 14so6382534qyg.13 for ; Sat, 29 Oct 2011 14:26:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=VkL2dfbPUZ2//qB4q2rJ++x8YAwXwO+FiggNv42v4JQ=; b=cJO3dycV4i+VaQkGaDPitQKm4xxxmSC+e96FzETkovyuY5CiW3eE9FnthyVWgWMdF6 FTOUIS3McJSCebN6zsLX2YPugHs209i5Gu7Hk3CumZTXVxs2ggGBCoX4+/Px4dyjOD2P m7w0ShlEPJOhIhRgPsy+bTyVRW8OaZZbXEijM= MIME-Version: 1.0 Received: by 10.229.92.2 with SMTP id p2mr1876496qcm.222.1319923589300; Sat, 29 Oct 2011 14:26:29 -0700 (PDT) Received: by 10.229.226.65 with HTTP; Sat, 29 Oct 2011 14:26:29 -0700 (PDT) Date: Sat, 29 Oct 2011 23:26:29 +0200 Message-ID: From: "deeptech71@gmail.com" To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: lockup during probing because of a memory stick X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Oct 2011 21:26:30 -0000 If a USB mass storage device was connected when the computer was turned on or reset and the device is left connected, then the system locks up somewhere around the ``acpi0: on motherboard'' line (not exactly deterministically at that line). Otherwise (if the device is connected or disconnected just before FreeBSD started booting, or if the device is nowhere near the computer for the whole booting process), the system boots fine. I'm using a -CURRENT kernel. I don't recall this case happening some time ago. But now, this happens with and without the NEW_PCIB option. I mention this because ``acpi0: on motherboard'' is shortly followed by ``acpi0: reservation of 0, a0000 (3) failed'', whatever that means.