From owner-freebsd-stable@FreeBSD.ORG Mon Mar 26 16:54:25 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75524106564A for ; Mon, 26 Mar 2012 16:54:25 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id E83FC8FC14 for ; Mon, 26 Mar 2012 16:54:24 +0000 (UTC) Received: by lagv3 with SMTP id v3so5488150lag.13 for ; Mon, 26 Mar 2012 09:54:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=DO0vmCIqeFdfbnIlXtCsjuPwdEVqYFgttGP2f0IteVE=; b=Yc/hn0ml0jQ2STFlVvxsIWCRgbE0RRyRRwssgUX8AbrN/lZmxdimNCE/xiZAqZHlxj u76OS9GKemnnrnCTskP9vJ4gqkW5qi18tVYRPIqVQnCe9sEl14Bynt/hPWIWXidjxyhD OxdfsWM8F7VNSs5cjBSCpt+JPEQhdhjVaeBZ+y8DaxVZvC08YrXC/DqkdZqUUudUgaES vk3xU0eoDJYLCEpQZsKYdtH9xUSCu3phb7aqINkPQlpAMkIAkY6zJNRsPoafmXbkq+vH hw93g8Xkuu9Eew4mxqjtFy1Lv9f1+YMndThPXU8B7ajzJwWtBnTU4CdwQfr54g7Uv8rY sIdg== MIME-Version: 1.0 Received: by 10.152.105.211 with SMTP id go19mr16710095lab.51.1332780863798; Mon, 26 Mar 2012 09:54:23 -0700 (PDT) Received: by 10.112.100.229 with HTTP; Mon, 26 Mar 2012 09:54:23 -0700 (PDT) X-Originating-IP: [64.147.96.250] Date: Mon, 26 Mar 2012 12:54:23 -0400 Message-ID: From: Mark Saad To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQmxdZOkrjDjiB93sGVR2wIwwcE2W6Xiz/MY9CTzyyiZQdgR53HZ18Gv9uViASahqWRbLs1o Subject: ACPI Issues in 8-STABLE and on X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2012 16:54:25 -0000 All I was wondering if anyone has looking into this ACPI issue noted back in 2010. http://lists.freebsd.org/pipermail/freebsd-acpi/2010-February/006332.html I attempted to upgrade a 7-STABLE DL385g1 with 4G of ram to 9-STABLE and it was a disaster. The box was able to boot once and then on a normal reboot the root filesystem was corrupted beyond repair ( most likely unrelated , but some unknown issue with su+j *) and the system would not get past the point noted in the a fore mentioned thread . I tried to boot this box with 8.2-RELASE amd64 same issue, 9.0-BETA1 , same issue, 9.0-RELEASE same issue , and 9.0-STABLE as I pointed out worked intermittently. So the end result is that this box now only reliably runs 7.0-RELEASE - 7.4-RELEASE and 7-STABLE , 6.2-RELEASE - 6.4-RELEASE and 6-STABLE but nothing else. As a side test , NetBSD 6.0 beta amd64 boots with out issues on this box as well as DragonFlyBSD 3.01 amd64. So my solutions are to migrate back to 7-STABLE or use Net or Dfly. Does anyone know what the root issue is here ? * The su-j issue was most likely caused by me not properly converting the old su slice to su+j . I think I may have done a tunefs -j enable before I did a tunefs -n disable && fsck . -- mark saad | nonesuch@longcount.org