On Tue, 21 Sep 2010, Andriy Gapon wrote:
 > on 21/09/2010 01:15 Daniel Bilik said the following:
 > > I've tried to get FreeBSD run on HP Mini 5102, but both 8-STABLE and
 > > 9-CURRENT fail to attach ACPI:
 > > cpu0 (BSP): APIC ID:  0
 > > cpu1 (AP/HT): APIC ID:  1
 > > ioapic0: Changing APIC ID to 1
 > > ioapic0 <Version 2.0> irqs 0-23 on motherboard
 > > kbd1 at kbdmux0
 > > acpi0: <HPQOEM SLIC-MPC> on motherboard
 > > ACPI Error: No handler for Region [PMIO] (0xffffff00024b1d00) [SystemIO] 
 > > (20100331/evregion-487)
 > > ACPI Error: Region SystemIO(0x1) has no handler (20100331/exfldio-383)
 > > ACPI Error (psparse-0633): Method parse/execution failed [\_SB_.PCI0.GSWS] 
 > > (Node 0xffffff00024c63e0), AE_NOT_EXIST
 > > ACPI Error (psparse-0633): Method parse/execution failed [\_SB_.SSMI] 
 > > (Node 0xffffff00024af400), AE_NOT_EXIST
 > > ACPI Error (psparse-0633): Method parse/execution failed 
 > > [\_SB_.PCI0.GFX0._REG] (Node 0xffffff00024ac9e0), AE_NOT_EXIST
 > > acpi0: Could not initialise SystemMemory handler: AE_NOT_EXIST
 > Hmm, seems like a dependency problem with address space handlers?
 > I.e. registration of SystemMemory handler requires SystemIO handler to be
 > already installed?
 > BTW, it seems that NetBSD 5 has the block that installs the handlers under 
 > 'notyet'.
 > Also, it seems that AcpiEnableSubsystem() also installs the default 
 > handlers, if
 > not already installed, but without calling _REG methods.  I mean the call to
 > AcpiEvExecuteRegMethods at the end of AcpiInstallAddressSpaceHandler.
 > Or, is this a general ACPICA issue of calling _REG that it shouldn't actually
 > call?  Perhaps a bug in AcpiEvRegRun?
 > P.S. Link to ASL of supposedly this machine that I googled up:
 > http://tavvva.net/data/hp_mini_5102-acpidump.txt

I don't know anything about that, but having looked over our RTC code 
lately re another issue, I also wonder about the significance of this:

 > RTC BIOS diagnostic error 96<clock_battery,memory_size,invalid_time>

 > Timecounters tick every 1.000 msec
 > md0: Preloaded image </boot/mfsroot> 4194304 bytes at 0xffffffff80e6aa98
 > SMP: AP CPU #1 Launched!
 > Trying to mount root from ufs:/dev/md0

 > warning: no time-of-day clock registered, system time will not be set 
 > accurately

That diag message suggests that the RTC battery has failed, or been 
disconnected - unlikely on a new machine, though not impossible - or 
something else has triggered that (adding or removing RAM, perhaps?)

Usually in such a condition you'd get a BIOS message on initial startup, 
and thrown straight into the BIOS setup.  If in doubt, entering BIOS 
setup, saving settings and quitting might reset the RTC properly.

Andriy: do we refer to the RTC's idea of how much memory exists at all?  
I notice this is relying on mfsroot, so maybe memory could be an issue?

Daniel: have there been any other RTC messages like that along the way?
Perhaps seeing all of your dmesg might shine some more light?

Just a thought ..

cheers, Ian
freebsd-acpi@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"

Reply via email to