From owner-freebsd-current@FreeBSD.ORG Mon Oct 31 02:46:00 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 18C95106566C for ; Mon, 31 Oct 2011 02:46:00 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id CB5AE8FC0C for ; Mon, 31 Oct 2011 02:45:59 +0000 (UTC) Received: by qyk35 with SMTP id 35so3973956qyk.13 for ; Sun, 30 Oct 2011 19:45:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=DjHFBiV0qLlgGLSBtVKqVjU3HNL65jQlrVagD8Ro28c=; b=g823hdk0lPftJBuTP0feQQV8cWm0+HTz/fMGZMJ0eB+VMHE9MOAA3UemSd1Y1+sefG 0uFTm8EKCkBPH5SsKtebg72dSE5kL0eGeKXUyLyJ+CZdie2Vh8I/wg2Smn/uzKZF9nOu yVFOffvWptPaaDzaacMkXc9QuqcTCu7aYoRng= MIME-Version: 1.0 Received: by 10.229.65.70 with SMTP id h6mr1235677qci.146.1320029159039; Sun, 30 Oct 2011 19:45:59 -0700 (PDT) Received: by 10.229.226.65 with HTTP; Sun, 30 Oct 2011 19:45:58 -0700 (PDT) In-Reply-To: <5083193D-4DEA-4BFC-BD87-612C11B46C90@gmail.com> References: <201110302127.51898.hselasky@c2i.net> <5083193D-4DEA-4BFC-BD87-612C11B46C90@gmail.com> Date: Mon, 31 Oct 2011 03:45:58 +0100 Message-ID: From: "deeptech71@gmail.com" To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: 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: Mon, 31 Oct 2011 02:46:00 -0000 On Mon, Oct 31, 2011 at 3:01 AM, Garrett Cooper wrote: > On Oct 30, 2011, at 6:47 PM, deeptech71@gmail.com wrote: > >> On Sun, Oct 30, 2011 at 9:27 PM, Hans Petter Selasky = wrote: >> >>> On Saturday 29 October 2011 23:26:29 deeptech71@gmail.com wrote: >> >>>> 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. >> >> >> >>> ACPI involves some USB BIOS code most likely which is causing the crash= . I >> >>> think this is maybe not a FreeBSD issue, but if you can binary search t= he >> >>> revisions to find exactly what commit broke your system, them I can loo= k >> >>> further at your issue. >> >> >> >> Actually, I've just tested a pre-compiled 7.3-RELEASE GENERIC kernel, >> and the lockup also occurs there. >> >> >> >>> Have you tried to turn off USB legacy support in the BIOS? >> >> >> >> Hmm. Interesting, only a combination of the following result in the lock= up: >> >> - Legacy USB Support: Auto (enable if and only if a USB device is >> connected) or Enabled, >> >> - USB 2.0 Controller: Enabled, >> >> - USB 2.0 Controller Mode: HiSpeed, >> >> - the memory stick is plugged in when the computer starts, and >> >> - the memory stick is plugged in when FreeBSD boots. >> >> Note that, to reproduce the lockup, it is not sufficient to just have >> the said BIOS settings (Legacy USB Support: Enabled, etc.), it is also >> required that the mutherboard recognize the memory stick when the >> computer starts, and to have the memory stick connected when FreeBSD >> boots. (If I disable 2.0 support, or set the speed to FullSpeed, or >> disable legacy support, or do not have the stick plugged in when the >> computer starts, or do not have the stick plugged in when FreeBSD >> boots, then the lockup does not occur.) >> >> >> >> But Windows XP does not produce any lockups in the case where FreeBSD >> does. Furthermore, in all cases, the memory stick is usable from >> FreeBSD if FreeBSD boots successfully. So why should I expect FreeBSD >> to lock up? > > > =A0 =A0 =A0 =A0Vendor hacks and limited testing on other OSes is the most= likely cause, if it's not a bug within FreeBSD. Just to narrow things down= a bit... > 1. Are there are BIOS updates for your motherboard? Yes, and I have the latest non-beta version (v1019 (dated 2004-11-08) for P4P800 mutherboards). > 2. Do you have ACPI 2.0 support enabled in the BIOS (I was reminded of th= is because some ASUS MBs default this setting to off -- which may or may no= t cause problems with FreeBSD)? Yes (also, I've just tried disabling ACPI 2.0, with no luck).