From owner-freebsd-current@FreeBSD.ORG  Mon Jul 19 17:52:40 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 6A5C216A4CE; Mon, 19 Jul 2004 17:52:40 +0000 (GMT)
Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 2995143D1D; Mon, 19 Jul 2004 17:52:40 +0000 (GMT)
	(envelope-from nate@root.org)
Received: from [10.0.0.34] (adsl-63-195-111-154.dsl.snfc21.pacbell.net
	[63.195.111.154])
	by www.cryptography.com (8.12.8/8.12.8) with ESMTP id i6JHqcrb002978
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 19 Jul 2004 10:52:39 -0700
Message-ID: <40FC09E1.9040509@root.org>
Date: Mon, 19 Jul 2004 10:50:25 -0700
From: Nate Lawson <nate@root.org>
User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Baldwin <jhb@FreeBSD.org>
References: <200407162010.i6GKAlUq005647@corona.sajd.net>
	<200406301134.09786.jhb@FreeBSD.org>
In-Reply-To: <200406301134.09786.jhb@FreeBSD.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Pawel Worach <sajd@telia.com>
cc: freebsd-current@FreeBSD.org
Subject: Re: acpi_timer broken
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2004 17:52:40 -0000

John Baldwin wrote:
> On Friday 16 July 2004 04:10 pm, Pawel Worach wrote:
> 
>>Hi,
>>
>>Somewhere in the last few days the acpi timecounter is not detected on
>>my system anymore, the machine is an IBM xSeries 345.
>>
>>When it worked it looked like this:
>>Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000
>>acpi_timer0: <32-bit timer at 3.579545MHz> port 0x488-0x48b on acpi0
>>
>>Now it looks like this:
>>acpi_timer0: couldn't allocate I/O resource (port 0x488)
>>acpi_timer0 port 0x488-0x48b on acpi0
>>
>>Any ideas?
> 
> This is probably related to the recent ACPI sysresource changes.  Try asking 
> njl@ (cc'd) for pointers.  Disabling the "sysresource" driver and seeing if 
> that fixes the problem is a good first step.

John, your clock is off.  Your reply had a date of "June 30".  Pawel, 
send me the output of acpidump -t -d > ibm_xseries_345.asl

-- 
-Nate