You may need to selectively enable/disable the debug trace during a particular call.
I suspect that the problem is happening during the execution of the ACPICA interface AcpiSetCurrentResources (aka acpi_set_current_resources). Here's the way I would do it: Set a breakpoint on acpi_set_current_resources. When you get there, enable debug output. When finished, disable debugging. If this isn't possible with your debugger, you can always change the source to enable/disable debugging at the start and end of acpi_set_current_resources. Bob > -----Original Message----- > From: Luck, Tony > Sent: Friday, February 10, 2006 2:59 PM > To: Moore, Robert; 'Thomas Renninger'; Brown, Len > Cc: '[email protected]'; '[email protected]' > Subject: RE: some new unaligned access while booting ia64 (HP rx2620) > > > That looks good. You'll probably need to increase your dmesg buffer > > or send the output to a serial port, since you will get megabytes > > of info. > > I only have a serial port on this machine ... but all the interesting > output happens before it is enabled ... i.e. is buffered up in log_buf > until the serial console is brought online. > > I made log_buf as big as I could (2^21 bytes is the biggest it would > let me go), and that is not enough for all the ACPI messages ... so the > initial part where the unaligned messages were printed was lost in the > wraparound before anything could be dumped to the serial port. > > Now I've got network problems in the lab ... when I can reconnect to > my systems, I'll change lib/Kconfig.debug to allow a bigger log_buf > and try again. > > -Tony - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
