Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Mar 2012 10:41:55 -0700
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        John Baldwin <jhb@freebsd.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: general protection fault panic
Message-ID:  <20120326174155.GA1931@troutmask.apl.washington.edu>
In-Reply-To: <201203261318.37373.jhb@freebsd.org>
References:  <20120323222313.GA1331@troutmask.apl.washington.edu> <20120326154359.GB14611@troutmask.apl.washington.edu> <20120326162129.GB1373@troutmask.apl.washington.edu> <201203261318.37373.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 26, 2012 at 01:18:37PM -0400, John Baldwin wrote:
> On Monday, March 26, 2012 12:21:29 pm Steve Kargl wrote:
> 
> You know your APIC ID is 0, so you should be able to find the IRQ for vector 
> 51 from here in apic_idt_to_irq():
> 
> 	irq = lapics[apic_id].la_ioint_irqs[vector - APIC_IO_INTS];
> 
> Your apic_id is 0, and APIC_IO_INTS is 48, so you should be able to do this
> in kgdb:
> 
> p lapics[0].la_ioint_irqs[3]
> 
> That should give you an index, and intr_lookup_source() just does an array
> lookup.  However, I'd be curious to see what the assembly looks like
> (x/10i $rip at this frame).
> 


(kgdb) p lapics[0].la_ioint_irqs[3]
$1 = 16
(kgdb) frame 27
#27 0xffffffff806dc186 in acpi_cpu_c1 ()
    at /usr/src/sys/amd64/acpica/acpi_machdep.c:97
97              __asm __volatile("sti; hlt");
(kgdb) x/10i $rip
0xffffffff806dc186 <acpi_cpu_c1+6>:     leaveq 
0xffffffff806dc187 <acpi_cpu_c1+7>:     retq   
0xffffffff806dc188 <acpi_cpu_c1+8>:     nopl   0x0(%rax,%rax,1)
0xffffffff806dc190 <nexus_acpi_attach>: push   %rbp
0xffffffff806dc191 <nexus_acpi_attach+1>:       mov    %rsp,%rbp
0xffffffff806dc194 <nexus_acpi_attach+4>:       push   %r12
0xffffffff806dc196 <nexus_acpi_attach+6>:       push   %rbx
0xffffffff806dc197 <nexus_acpi_attach+7>:       mov    %rdi,%rbx
0xffffffff806dc19a <nexus_acpi_attach+10>:
    callq  0xffffffff807551b0 <nexus_init_resources>
0xffffffff806dc19f <nexus_acpi_attach+15>:      mov    %rbx,%rdi


In another email thread, it appears that jkim is chasing
down some issues with the latest ACPI code.  Perhaps, this
is related?

If it helps, I'll put kernel.debug and vmcore.0 at 
http://troutmask.apl.washington.edu/~kargl/jhb
-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120326174155.GA1931>