Date: Tue, 16 Nov 2004 15:21:25 -0800 From: Nate Lawson <nate@root.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: John Baldwin <jhb@FreeBSD.org> Subject: Re: New ACPI PCI Link Routing code Message-ID: <419A8B75.4060000@root.org> In-Reply-To: <16794.33094.416989.88341@grasshopper.cs.duke.edu> References: <200411111737.00537.jhb@FreeBSD.org> <200411161339.13818.jhb@FreeBSD.org> <16794.28367.159895.3565@grasshopper.cs.duke.edu> <200411161647.14543.jhb@FreeBSD.org> <16794.33094.416989.88341@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrew Gallatin wrote: > John Baldwin writes: > > On Tuesday 16 November 2004 04:19 pm, Andrew Gallatin wrote: > > > "panic: link_add_crs: too many interrupts" > > > > > > Full boot -v output at: > > > http://people.freebsd.org/~gallatin/pcilink.boot > > > > > > This is from a machine with an evil ACPI (but I don't want to mess > > > with it for fear of breaking the machine). > > > > Ok, that's weird. Can you hack the link_add_crs() function to print out the > > number of interrupts before the KASSERT()'s if it is not 1? > > There are 3 interrupts. Eg: > > pci_link1: <ACPI PCI Link LN00> on acpi0 > 3 interrupts > panic: link_add_crs: too many interrupts > > If you want me to extract any acpi info, just say the word (and let me > know what the incantation is). I have the asl and the dsdt I > extracted ages ago saved in ~gallatin/trinity.tgz on freefall. You'll need ASL to debug this, acpidump -t -d > trinity.asl It seems very surprising that _CRS would return 3 interrupts. I'm guessing the first is the active one? -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?419A8B75.4060000>