# Cc acpi-jp

From: Shizuka Kudo <[EMAIL PROTECTED]>
Subject: ASUS CUSL2 panic on acpi
Date: Tue, 2 Jul 2002 11:55:18 -0700 (PDT)
Message-ID: <[EMAIL PROTECTED]>

> Dear all,
> 
> I wonder if anyone experienced the same issue as mime. I have an ASUS CUSL2 running 
>-current and
> starting about three days ago, it panic when acpi is autoloaded. If I unset 
>acpi_load at the boot
> prompt, the machine works fine.

Could you send ACPI related data to [EMAIL PROTECTED] as follows?
 # acpidump -o ASUS-CUSL2.dsdt > ASUS-CUSL2.asl
 # tar czvf ASUS-CUSL2.tar.gz ASUS-CUSL2.dsdt ASUS-CUSL2.asl

And one more thing, recompile acpi module w/ ACPI_DEBUG, add 2 lines
to your /boot/loader.conf and send new panic message?
----
debug.acpi.layer="ACPI_ALL_COMPONENTS"
debug.acpi.level="ACPI_LV_EXEC"
----

Thanks

> Here's the panic message and a trace for those interested
> 
> acpi0: <ASUS   CUSL2   > on motherboard
> 
> 
> Fatal trap 12: page fault while in kernel mode
> fault virtual address   = 0x16
> fault code              = supervisor read, page not present
> instruction pointer     = 0x8:0xc04f9aca
> stack pointer           = 0x10:0xc054ea14
> frame pointer           = 0x10:0xc054ea34
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, def32 1, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 0 (swapper)
> kernel: type 12 trap, code=0
> Stopped at      AcpiExReadDataFromField+0x5a:   movzbl  0x16(%eax),%eax
> db> trace
> AcpiExReadDataFromField(c0f00400,c25da200,c054ea50,c25e50c0,0) at 
>AcpiExReadDataFromField+0x5a
> AcpiExResolveNodeToValue(c0f005b0,c0f00400,1,c0ed6d40,c054eab0) at 
>AcpiExResolveNodeToValue+0xd9
> AcpiExResolveToValue(c0f005b0,c0f00400,c0f00400,0,c054eab0) at 
>AcpiExResolveToValue+0x53
> AcpiExResolveOperands(5b80,c0f005b4,c0f00400,c0efbe00,c0f00400) at 
>AcpiExResolveOperands+0x1cf
> AcpiDsEvalRegionOperands(c0f00400,c25d6480,c050411e,c25d6480,0) at 
>AcpiDsEvalRegionOperands+0x50
> AcpiDsExecEndOp(c0f00400,c054eb14,c0f00414,c0f0040c,cdd4f1b1) at 
>AcpiDsExecEndOp+0x258
> AcpiPsParseLoop(c0f00400,c257f900,c054eb74,0,0) at AcpiPsParseLoop+0x579
> AcpiPsParseAml(c0f00400,c25dcc40,0,cdd4f1a6,e) at AcpiPsParseAml+0x7c
> AcpiDsExecuteArguments(c0efbe00,c051de10,e,cdd4f1a6,c257fdc0) at 
>AcpiDsExecuteArguments+0x182
> AcpiDsGetRegionArguments(c257fdc0,0,c0efbe00,1,c054ec10) at 
>AcpiDsGetRegionArguments+0x56
> AcpiNsInitOneObject(c0efbe00,1,c054ec60,0,0) at AcpiNsInitOneObject+0xd8
> AcpiNsWalkNamespace(0,ffffffff,ffffffff,1,c0500620) at AcpiNsWalkNamespace+0xad
> AcpiWalkNamespace(0,ffffffff,ffffffff,c0500620,c054ec60) at AcpiWalkNamespace+0x77
> AcpiNsInitializeObjects(0,c054ecc8,c050b8ab,0,2) at AcpiNsInitializeObjects+0x4d
> AcpiEnableSubsystem(0,2,c04fd110,0,0) at AcpiEnableSubsystem+0x8a
> acpi_attach(c25d7580,c25b5090,c03d3590,c0ed4d00,c0f04c80) at acpi_attach+0x13b
> device_probe_and_attach(c25d7580,c0f04c80,c054ed2c,c0368864,c0f04c80) at
> device_probe_and_attach+0xaf
> bus_generic_attach(c0f04c80,0,c0ed4d00,c0efda80,c0f04c80) at bus_generic_attach+0x28
> nexus_attach(c0f04c80,c2596090,c03d3590,c03c4480,0) at nexus_attach+0x14
> device_probe_and_attach(c0f04c80,c0ef9780,c054ed80,c035b5e5,c0f04f00) at
> device_probe_and_attach+0xaf
> root_bus_configure(c0f04f00,c03c4480,0,c054ed98,c020b175) at root_bus_configure+0x28
> configure(0,54b000,54bc00,54b000,0) at configure+0x35
> mi_startup() at mi_startup+0xb5
> begin() at begin+0x43
> db>
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Sign up for SBC Yahoo! Dial - First Month Free
> http://sbc.yahoo.com
> 
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to