Hi,

I did a little more debugging and was able to extract the following 
information.

The reboots happen in acpi_attach (dev/acpi/acpi.c).  Here are commented boot 
messages:

acpi0 at mainbus0
acpi0: X/RSDT: OemId <HP-MCD,EA RSDT ,01820000>, AslId < LTP,00000000>

#### The next two lines are from the call to AcpiInstallAddressSpaceHandler.  
Despite the errors, it appears that AcpiInstallAddressSpaceHandler returns 
AE_OK because the acpi_attach code continues.

    ACPI-1286: *** Error: Method execution failed [\_SB_.PCI0.FDS_.FCB1.CSID] 
(Node 0xc090e320), AE_NOT_EXIST
    ACPI-1286: *** Error: Method execution failed [\_SB_.PCI0.FDS_._REG] (Node 
0xc090e6a0), AE_NOT_EXIST

acpi0: SCI interrupting at int 9
#### The next line is from acpi_enable_fixed_events
acpi0: fixed-feature power button present

#### The call to acpi_pci_fixup causes a reboot.

#### If I comment out the call to acpi_pci_fixup, the boot continues until the 
call to acpi_build_tree.  This call causes a reboot as well.  Commenting it 
out allows the computer to complete the boot process.

Sverre

PS  The only acpi related config file parameters that are enabled is the 
device:

	acpi0  at mainbus0

and the options

	options         ACPI_MADT_DEBUG # ACPI debug flag
	options         ACPI_PROBE_DEBUG        # ACPI debug flag
	options         MPVERBOSE       # ACPI debug flag
	options         ACPIVERBOSE     # verbose ACPI device autoconfig messages

On Monday 13 January 2003 11:55, Sverre Froyen wrote:
> Hi,
>
> Thank's for the suggestions.  It turns out I can comment out all the
> devices and I still get the reboots.  In fact, the only line I need is the
>
> acpi0           at mainbus0
>
> line.
>
> Sverre
>
> On Saturday 11 January 2003 17:59, you wrote:
> > G'day,
> >
> > what happens if you comment out the acpibat device? Does it still reboot
> > your laptop?
> >
> > The kernel will crash on my laptop whenever the acpibat device is
> > enabled.
> >
> > cheerio Berndt
> >
> > > Hi,
> > >
> > > On an HP Omnibook 6000 (i386), I added the following options to my
> > > config file (source is current from 10 Jan.):
> > >
> > > ioapic* at mainbus?
> > >
> > > acpi0           at mainbus0
> > > options         ACPI_PCI_FIXUP=1        # PCI interrupt routing via
> > > ACPI options         ACPI_ACTIVATE_DEV=0     # If set, activate
> > > inactive devices
> > >
> > > # ACPI devices
> > > acpiacad*       at acpi?                # ACPI AC Adapter
> > > acpibat*        at acpi?                # ACPI Battery
> > > acpibut*        at acpi?                # ACPI Button
> > > acpiec*         at acpi?                # ACPI Embedded Controller
> > > acpilid*        at acpi?                # ACPI Lid Switch
> > > acpitz*         at acpi?                # ACPI Thermal Zone
> > >
> > > # Mainboard devices
> > > com*            at acpi?                # Serial communications
> > > interface fdc*            at acpi?                # Floppy disk
> > > controller lpt*            at acpi?                # Parallel port
> > > npx*            at acpi?                # Math coprocessor
> > > pckbc*          at acpi?                # PC keyboard controller
> > > wss*            at acpi?                # NeoMagic 256AV in wss mode
> > >
> > > The resulting kernel makes the computer reboot during what appears to
> > > be the acpi section.
> > >
> > > Here are three examples of (garbled) dmesg output:
> > >
> > > (Node 0xc0922320), AE_NOT_EXISod execution failed [\_SB_.PCI0.
> > >
> > > acpi0 at mainbus0
> > > acpi0: X/RSDT: Oe
> > >
> > >  mainbus0
> > > acpi0: X/RSDT: OemId <HP-MCD,EA RSDT ,01820000>, AslId < LTP,00000000>
> > >
> > > Sverre