Re: ACPI Panic on Current, AMD64

Hello Eygene,

I know the patch won't fix anything :(

Here's the updated dmesg:

acpi0: <Nvidia NVDAACPI> on motherboard
acpi0:  [ITHREAD]
acpi0:  Power Button (fixed)
acpi0:  reservation of 0, a000 (3) failed
acpi0:  reservation of 100000, bfdf0000 (3) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port  0x1008-0x100b on acpi0
acip_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI Host PCI bus> on pcib0
pci_link26:      Index  IRQ  Rtd   Ref  IRQs
    MPASS               0    20      N       1  20 21 22 23
link type is 15
panic: Assertion link->l_prs_template.Type == ACPI_RESOURCE_TYPE_IRQ  
failed at /usr/src/sys/dev/acpica/acpi_pci_link.c:746
cpuid = 0
KDB: enter: panic
[thread pid 0 tid 100000 ]
Stopped at     kdb_enter+0x3d: movq $0,0x677da0(%rip)

I've compressed and attached acpidump because it was too big to send  
on the list. Hopefully this will get through to you. I can't run  
acpidump because of the crash, but I ran it on the 7.2-Stable  
partition. Is that what you mean?



Thanks,
Timothy.



On 27/05/2009, at 8:20 PM, Eygene Ryabinkin wrote:

> Timothy, good day.
>
> Wed, May 27, 2009 at 05:45:02PM +1000, Timothy Mukaibo wrote:
>> db> bt
>> Tracing pid 0 tid 100000 td 0fffffff80bd2ae0
>> kdb_enter() at kdb_enter+0x3d
>> panic() at panic+0x17b
>> acpi_pci_link_route_irqs() at acpi_pci_link_route_irqs+0x727
>> acpi_pci_link_route_interrupt() at acpi_pci_link_route_interrupt 
>> +0x1a9
>> acpi_pcib_route_interrupt() at acpi_pcib_route_interrupt+0x40d
>> pci_assign_interrupt() at pci_assign_interrupt+0x1c3
>> pci_add_resources() at pci_add_resources+0x147
>> pci_add_children() at pci_add_children+0x10e
>> acpi_pci_attach() at acpi_pci_attach+0xcd
>> device_attach() at device_attach+0x69
>> bus_generic_attach() at bus_generic_attach+0x1a
>> acpi_pcib_attach() at acpi_pcib_attach+0x1a7
>> acpi_pcib_acpi_attach() at acpi_pcib_acpi_attach+0x1a5
>> device_attach() at device_attach+0x69
>> bus_generic_attach() at bus_generic_attach+0x1a
>> acpi_attach() at acpi_attach+0xa50
>> device_attach() at device_attach+0x69
>> bus_generic_attach() at bus_generic_attach+0x1a
>> device_attach() at device_attach+0x69
>> root_bus_configure() at root_bus_configure+0x28
>> configure() at configure+0xa
>> mi_startup() at mi_startup+0x59
>> btext() at biext+0x2c
>
> OK, will try to look at it more closely.
>
>> I'll try your patch.
>
> Please, note that the patch just adds verbosity, currently it won't  
> heal
> anything.
>
> Still, the output from 'acpidump -dt' might be interesting.
> -- 
> Eygene
> _                ___       _.--.   #
> \`.|\..----...-'`   `-._.-'_.-'`   #  Remember that it is hard
> /  ' `         ,       __.--'      #  to read the on-line manual
> )/' _/     \   `-_,   /            #  while single-stepping the  
> kernel.
> `-'" `"\_  ,_.-;_.-\_ ',  fsc/as   #
>     _.-'_./   {_.'   ; /           #    -- FreeBSD Developers handbook
>    {_.-``-'         {_/            #
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org 
> "