Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 05 Jan 2011 22:39:24 +0100
From:      "Arno J. Klaassen" <arno@heho.snv.jussieu.fr>
To:        acpi@freebsd.org
Cc:        mav@freebsd.org
Subject:   Tyan S3992-E: hpet no longer working
Message-ID:  <wpk4ij3u9f.fsf@heho.snv.jussieu.fr>

next in thread | raw e-mail | index | archive | help

Hello,

I have (a long-lasting) problem to get hpet attached to a Tyan S3992-E
MB. My last known working kernel is 7.1-PRERELEASE Sep 2 2008" , I
rarely cared about this board for a while...

At that time the dmesg said :


  acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff
  on acpi0
  Timecounter "HPET" frequency 25000000 Hz quality 900

now it says (debug.acpi.hpet_test="1", debug.acpi.layer="ACPI_TIMER",
debug.acpi.level="ACPI_LV_ALL_EXCEPTIONS" enabled) :

  hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed03fff on
  acpi0
  hpet0: vendor 0xffff, rev 0xff, 232831Hz 64bit, 32 timers, legacy route
  hpet0:  t0: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t1: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t2: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t3: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t4: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t5: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t6: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t7: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t8: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t9: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t10: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t11: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t12: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t13: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t14: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t15: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t16: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t17: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t18: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t19: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t20: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t21: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t22: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t23: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t24: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t25: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t26: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t27: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t28: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t29: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t30: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0:  t31: irqs 0xffffffff (31), MSI, 64bit, periodic
  hpet0: 0.000000000: 4294967295 ... 4294967295 = 0
  hpet0: time per call: 0 ns
  hpet0: HPET never increments, disabling
  device_attach: hpet0 attach returned 6


Some things strike me :

  'vendor 0xffff, rev 0xf' and '4294967295 (== 0xffffffff)' as well
    as 232831Hz

  the change in iomem range :

      OK : iomem 0xfed00000-0xfed003ff
      KO : iomem 0xfed00000-0xfed03fff
                                  ^^^^

I can provide full dmesg and/or other extra needed info.

Merci, Arno



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wpk4ij3u9f.fsf>