From owner-freebsd-current Mon Jul 8 14:42:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 80A2137B401 for ; Mon, 8 Jul 2002 14:42:42 -0700 (PDT) Received: from porthos.spock.org (alb-66-67-128-5.nycap.rr.com [66.67.128.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94B2343E42 for ; Mon, 8 Jul 2002 14:42:41 -0700 (PDT) (envelope-from jon@porthos.spock.org) Received: from porthos.spock.org (foouser@localhost [127.0.0.1]) by porthos.spock.org with ESMTP serial EF600Q3T-B7F; Mon, 8 Jul 2002 17:42:40 -0400 (EDT) (envelope-from jon@porthos.spock.org) X-OrigTo: freebsd-current@FreeBSD.ORG Received: (from jon@localhost) by porthos.spock.org (8.12.4/8.12.3/Submit) id g68Lge8D035472; Mon, 8 Jul 2002 17:42:40 -0400 (EDT) (envelope-from jon) Date: Mon, 8 Jul 2002 17:42:40 -0400 From: Jonathan Chen To: Mitsuru IWASAKI Cc: freebsd-current@FreeBSD.ORG Subject: Re: -CURRENT bootup panics (ACPI related?) Message-ID: <20020708174239.C26973@porthos.spock.org> References: <20020708104502.A26973@porthos.spock.org> <20020709.042903.63134736.iwasaki@jp.FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x In-Reply-To: <20020709.042903.63134736.iwasaki@jp.FreeBSD.org>; from iwasaki@jp.FreeBSD.org on Tue, Jul 09, 2002 at 04:29:03AM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Jul 09, 2002 at 04:29:03AM +0900, Mitsuru IWASAKI wrote: > Hi, > > > I just got myself an IBM Thinkpad T30, most things work fine on -STABLE > > (trying to get specs from IBM for the rest), but -CURRENT won't boot with > > ACPI enabled. I'd be glad to track that down, but I have no clue where to > > start, nor do I have any more than a passing knowledge of ACPI. I could > > disable it and boot -CURRENT (and install works fine since there's no ACPI > > there), but things go wrong as soon as the kernel touches UFS. This > [snip] > db> trace > crfree(73cc3000,c04aa2e0,5,0,d68cb6e4) at crfree+0x8 > getnewbuf(0,0,800,4000,4000) at getnewbuf+0x187 > getblk(c4236a00,0,0,800,0) at getblk+0x269 > breadn(c4236a00,0,0,800,0) at breadn+0x2f > bread(c4236a00,0,0,800,0) at bread+0x20 > ffs_blkatoff(c4236a00,0,0,0,d68cb848) at ffs_blkatoff+0xb2 > ufs_lookup(d68cb970,d68cb9ac,c029c751,d68cb970,c4236e74) at ufs_lookup+0x32a I really doubt that this is the problem. The kernel I was using was less than 2 days old, and the only change in ufs in that timeframe was a printf format error fix. Besides, the same problem was happening over a sampling of GENERICs in 2 months, which strongly indicate that this problem is feature and/or hardware specific. -Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message