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. tglx - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- From: Andrew Morton <[email protected]>
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- References:
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- From: Andrew Morton <[email protected]>
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- From: Andrew Morton <[email protected]>
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- From: Thomas Gleixner <[email protected]>
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- From: Andrew Morton <[email protected]>
- Re: [patch 3/3] clockevents: Fix resume logic - updated version
- Prev by Date: Re: why does x86 "make defconfig" build a single, lonely module?
- Next by Date: Re: why does x86 "make defconfig" build a single, lonely module?
- Previous by thread: Re: [patch 3/3] clockevents: Fix resume logic - updated version
- Next by thread: Re: [patch 3/3] clockevents: Fix resume logic - updated version
- Index(es):
 |