On Sun, 2007-05-13 at 23:42 -0700, Andrew Morton wrote: > On Sun, 13 May 2007 18:12:50 +0200 Thomas Gleixner <tglx@xxxxxxxxxxxxx> wrote: > > > On Sat, 2007-05-12 at 02:00 -0700, Andrew Morton wrote: > > > Still hangs in the same fashion, sorry. > > > > > > It's peculiar that the hang happens when acpi_evaluate_object() hits its > > > return statement. Any theories there? > > > > I assume you have a printk right before the return and one after the > > call to acpi_evaluate_object(). > > > > Can you dump the stack at the point before the return, so we can see if > > the stack is corrupt there ? A WARN_ON(1) should do the trick. > > > > It all looks clean. I spose I should do a hex dump and a byte-by-byte > walkthough, but time is short... I could backport the highres/dyntick stuff to 2.6.20, so we have the other changes out of the picture. tglx - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
