freebsd-current
[Prev] Thread [Next] | [Prev] Date [Next]
Re: ACPI Panic on Current, AMD64 John Baldwin Wed May 27 15:00:36 2009
On Wednesday 27 May 2009 8:39:32 am Andriy Gapon wrote: > on 27/05/2009 14:11 Timothy Mukaibo said the following: > > 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 > > So resource type is ACPI_RESOURCE_TYPE_IRQ, but link type is > ACPI_RESOURCE_TYPE_EXTENDED_IRQ. Interesting. I think the _PRS returned one type and _CRS is returning another (or some such). I'm not sure what the "right" thing to do is in that case. Presumably this is while building the buffer for _SRS? Hmm, I guess you could just make it able to read the IRQ out of the _PRS no matter what format it is. But we might should be copying the resource that is in _PRS instead and building a new resource list instead of overwriting the fields in _CRS. That is a bit more involved. -- John Baldwin _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
- ACPI Panic on Current, AMD64 Timothy Mukaibo
- Re: ACPI Panic on Current, AMD64 Eygene Ryabinkin
- Re: ACPI Panic on Current, AMD64 Timothy Mukaibo
- Re: ACPI Panic on Current, AMD64 Eygene Ryabinkin
- Re: ACPI Panic on Current, AMD64 Timothy Mukaibo
- Re: ACPI Panic on Current, AMD64 Andriy Gapon
- Re: ACPI Panic on Current, AMD64 John Baldwin <=
- Re: ACPI Panic on Current, AMD64 Timothy Mukaibo
- Re: ACPI Panic on Current, AMD64 John Baldwin
- Re: ACPI Panic on Current, AMD64 Andriy Gapon
- Re: ACPI Panic on Current, AMD64 Timothy Mukaibo
- Re: ACPI Panic on Current, AMD64 Andriy Gapon
- RE: ACPI Panic on Current, AMD64 Moore, Robert
- Re: ACPI Panic on Current, AMD64 Andriy Gapon
- Re: ACPI Panic on Current, AMD64 Timothy Mukaibo