NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/42937: hpet at acpi disappeared in recent current kernel

The following reply was made to PR kern/42937; it has been noted by GNATS.

From: Quentin Garnier <>
Subject: Re: kern/42937: hpet at acpi disappeared in recent current kernel
Date: Mon, 8 Mar 2010 22:16:50 +0000

 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 On Mon, Mar 08, 2010 at 09:25:00PM +0000, wrote:
 > >Number:         42937
 > >Category:       kern
 > >Synopsis:       hpet at acpi disappeared in recent current kernel on Fuj=
 istu FM-V LOOX P70WN (Lifebook)
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    kern-bug-people
 > >State:          open
 > >Class:          sw-bug
 > >Submitter-Id:   net
 > >Arrival-Date:   Mon Mar 08 21:25:00 +0000 2010
 > >Originator:     Ryo ONODERA
 > >Release:        NetBSD 5.99.24
 > >Organization:
 > =09
 > >Environment:
 > System: NetBSD 5.99.24 NetBSD 5.99.24 (BRIGH=
 TGIRL7) #3: Tue Mar 9 05:53:48 JST 2010
 usr/obj/sys/arch/i386/compile/BRIGHTGIRL7 i386
 > Architecture: i386
 > Machine: i386
 > >Description:
 > The dmesg in 2007 (See has following lines.
 > hpet0 at acpi0 (HPET, PNP0103)
 > hpet0: mem 0xfed00000-0xfed003ff
 > hpet0: Found 64-bits HPET, will only use lowest 32-bits
 > timecounter: Timecounter "hpet0" frequency 14318179 Hz quality 2000
 > But current kernel does not detect hpet.
 > I apply following patch to src/sys/dev/acpi/hpet_acpi.c and get dmesg.
 > I will include it in this message.
 > The value of aa->aa_node->ad_type is assumed to be ACPI_TYPE_DEVICE (0x06=
 > but in my kernel the value is 0x0d (ACPI_TYPE_THERMAL).
 Well, the value appears while the kernel is probing the acpitz devices,
 so it is expected.
 > acpi0: HID PNP0103 found in scope \_SB_ level 3
 >        STA 0x0000000f
 the device is there, and active.
 > DIGI (FUJ02E6) at acpi0 not configured
 > BTNS (FUJ02BF) at acpi0 not configured
 > FJEX (FUJ02B1) at acpi0 not configured
 > acpiec0 at acpi0 (EC, PNP0C09): io 0x62,0x66
 > attimer1 at acpi0 (TIME, PNP0100): io 0x40-0x43 irq 0
 > pcppi1 at acpi0 (SPKR, PNP0800): io 0x61
 > npx1 at acpi0 (MATH, PNP0C04): io 0xf0-0xfe irq 13
 > pckbc1 at acpi0 (KBC, PNP0320) (kbd port): io 0x60,0x64 irq 1
 > pckbc2 at acpi0 (PS2M, PNP0F13) (aux port): irq 12
 > FEXT (FUJ02E3) at acpi0 not configured
 > acpilid0 at acpi0 (LID, PNP0C0D): ACPI Lid Switch
 > acpibut0 at acpi0 (PWRB, PNP0C0C): ACPI Power Button
 > acpiacad0 at acpi0 (AC, ACPI0003): ACPI AC Adapter
 > acpibat0 at acpi0 (CMB1, PNP0C0A-1): ACPI Battery
 The main problem I see right now is that the printf you added to
 hpet_acpi.c should trigger for all of those attachments.
 > ACPI Warning for \_SB_.CMB1._BIF: Converted Buffer to expected String at =
 index 9 (20090730/nsrepair-215)
 > acpibat0: battery info: Fujitsu LION 1 CP240502=20
 > Not ACPI Device from hpet_acpi_match(), aa->aa_node->ad_type =3D 000d
 > acpitz0 at acpi0 (TZ00): critical 100.0C passive 95.0C, passive cooling
 > Not ACPI Device from hpet_acpi_match(), aa->aa_node->ad_type =3D 000d
 > acpitz1 at acpi0 (TZ01): critical 100.0C passive 95.0C, passive cooling
 Can I see the ioconf.c of your kernel?  The configuration, too.
 I notice another differences with the past dmesg:  DIGI used to be
 matched by com(4), and it still should.
 Quentin Garnier - -
 "See the look on my face from staying too long in one place
 [...] every time the morning breaks I know I'm closer to falling"
 KT Tunstall, Saving My Face, Drastic Fantastic, 2007.
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 Version: GnuPG v1.4.10 (NetBSD)

Home | Main Index | Thread Index | Old Index