Li, Shaohua wrote: > Hi Jonas, > What the dmesg in the failure case? It seems the attched dmesg has the > correct pm-timer info. yes, this is the "my own hardcoded" version. attaching one from failure case. thank you for looking at it. /Jonas > > Thanks, > Shaohua > > >>-----Original Message----- >>From: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org [mailto:acpi-devel- >>admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org] On Behalf Of Andrew Morton >>Sent: Wednesday, September 21, 2005 2:18 PM >>To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org >>Cc: Jonas Oreland >>Subject: [ACPI] Fw: ACPI, pm timer and ASUS a8v >> >> >>Jonas, you'll probably need to raise an ACPi report at > > bugzilla.kernel.org > >>for this one please. >> >>Begin forwarded message: >> >>Date: Tue, 20 Sep 2005 14:12:53 +0200 >>From: Jonas Oreland >>To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org >>Subject: ACPI, pm timer and ASUS a8v >> >> >>Hi, >> >>I running 2.6.12-gentoo-r10 >>I have a ASUS a8v motherboard with a AMD64 X2 >> >>This gives me problem with clock drift >>(see http://bugzilla.kernel.org/show_bug.cgi?id=5105) >> >>So I tried using notsc to force usage of pm timer. >> >>But! >>The the acpi code find the fadt->xpm_tmr_blk.address to 0 >>Making the code yet again fall back to PIT/TSC >> >>I booted my system can run >>perch> grep PM_ /proc/ioports >>0808-080b : PM_TMR >> >>And harded the address 0x808 into pmtmr_ioport >>This works. The system is using pmtmr and I get no clock drift >>(tested now for ~a day) >> >>But why do ACPI find 0 as pmtmr_ioport? >> >>/Jonas > > >