Re: [acpi-jp 1661] Re: ASUS CUSL2 panic on acpi
On Thu, Jul 04, 2002 at 10:09:52PM +0900, Mitsuru IWASAKI wrote:
> My analysis was finished. Please try this patch.
>
> --- exfield.c-Thu Jul 4 21:54:24 2002
> +++ exfield.c Thu Jul 4 21:55:02 2002
> @@ -200,7 +200,7 @@
> /* Handle both ACPI 1.0 and ACPI 2.0 Integer widths */
>
> IntegerSize = sizeof (ACPI_INTEGER);
> -if (WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32)
> +if (WalkState->MethodNode != NULL && WalkState->MethodNode->Flags &
>ANOBJ_DATA_WIDTH_32)
> {
> /*
> * We are running a method that exists in a 32-bit ACPI table.
>
The patch works fine, thanks.
- Christian
--
http://www.unixpages.org[EMAIL PROTECTED]
GPG Pub-Key: www.unixpages.org/cbrueffer.asc
GPG Fingerprint: 0DB5 8563 2473 C72A A8D1 56EA DAD2 B05D 5F3C 3185
GPG Key ID : DAD2B05D5F3C3185
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [acpi-jp 1661] Re: ASUS CUSL2 panic on acpi
My analysis was finished. Please try this patch.
--- exfield.c- Thu Jul 4 21:54:24 2002
+++ exfield.c Thu Jul 4 21:55:02 2002
@@ -200,7 +200,7 @@
/* Handle both ACPI 1.0 and ACPI 2.0 Integer widths */
IntegerSize = sizeof (ACPI_INTEGER);
-if (WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32)
+if (WalkState->MethodNode != NULL && WalkState->MethodNode->Flags &
+ANOBJ_DATA_WIDTH_32)
{
/*
* We are running a method that exists in a 32-bit ACPI table.
BTW, this bug already fixed in 20020517 version.
> > > acpi0: 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 0xf, 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
>
> # if my understanding on i386 asm is correct,
> I think this is at (exfield.c):
> 203:if (WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32)
> where WalkState->MethodNode is NULL, this caused page fault.
>
> I'm waiting for further debug info. but I'll try to find where
> WalkState->MethodNode suppose to be set...
WalkState->MethodNode was initialized to NULL in AcpiDsInitAmlWalk()
which called by AcpiDsExecuteArguments(). AcpiExReadDataFromField()
assumes that WalkState->MethodNode always has a correct pointer.
That's the problem, I think.
ACPI_STATUS
AcpiDsExecuteArguments (
ACPI_NAMESPACE_NODE *Node,
ACPI_NAMESPACE_NODE *ScopeNode,
UINT32 AmlLength,
UINT8 *AmlStart)
...
Status = AcpiDsInitAmlWalk (WalkState, Op, NULL, AmlStart,
AmlLength, NULL, NULL, 3);
...
AcpiDsInitAmlWalk (
ACPI_WALK_STATE *WalkState,
ACPI_PARSE_OBJECT *Op,
ACPI_NAMESPACE_NODE *MethodNode,
UINT8 *AmlStart,
UINT32 AmlLength,
ACPI_OPERAND_OBJECT **Params,
ACPI_OPERAND_OBJECT **ReturnObjDesc,
UINT32 PassNumber)
Thanks
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: [acpi-jp 1655] Re: ASUS CUSL2 panic on acpi
Not fixed yet, just a intermediate report... > > acpi0: 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 0xf, 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 # if my understanding on i386 asm is correct, I think this is at (exfield.c): 203:if (WalkState->MethodNode->Flags & ANOBJ_DATA_WIDTH_32) where WalkState->MethodNode is NULL, this caused page fault. I'm waiting for further debug info. but I'll try to find where WalkState->MethodNode suppose to be set... Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ASUS CUSL2 panic on acpi
Here's a me too.. running on an ASUS A7V266-E > 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 0xf, 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 I had a movb 0x16(%eax),%al > db> trace > AcpiExReadDataFromField(c0f00400,c25da200,c054ea50,c25e50c0,0) at >AcpiExReadDataFromField+0x5a With ACPI disabled (hint.acpi.0.disable="1") the kernel runs without a problem. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ASUS CUSL2 panic on acpi
On Tue, Jul 02, 2002 at 11:55:18AM -0700, Shizuka Kudo wrote: > 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. > > Here's the panic message and a trace for those interested > > acpi0: 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 0xf, 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,,,1,c0500620) at AcpiNsWalkNamespace+0xad > AcpiWalkNamespace(0,,,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> > Hi, I'm getting a similar message with my Asus A7M266 (Yesterday's sources). What is the best way to record those messages at boot time? Writing them down by hand is pretty suboptimal and I don´t have a serial console installed. TIA, Christian -- http://www.unixpages.org[EMAIL PROTECTED] GPG Pub-Key: www.unixpages.org/cbrueffer.asc GPG Fingerprint: 0DB5 8563 2473 C72A A8D1 56EA DAD2 B05D 5F3C 3185 GPG Key ID : DAD2B05D5F3C3185 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ASUS CUSL2 panic on acpi
# 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: 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 0xf, 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,,,1,c0500620) at AcpiNsWalkNamespace+0xad > AcpiWalkNamespace(0,,,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
ASUS CUSL2 panic on acpi
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. Here's the panic message and a trace for those interested acpi0: 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 0xf, 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,,,1,c0500620) at AcpiNsWalkNamespace+0xad AcpiWalkNamespace(0,,,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
