Date: Mon, 19 Jul 2004 10:50:25 -0700 From: Nate Lawson <nate@root.org> To: John Baldwin <jhb@FreeBSD.org> Cc: freebsd-current@FreeBSD.org Subject: Re: acpi_timer broken Message-ID: <40FC09E1.9040509@root.org> In-Reply-To: <200406301134.09786.jhb@FreeBSD.org> References: <200407162010.i6GKAlUq005647@corona.sajd.net> <200406301134.09786.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40FC09E1.9040509>