* Yinghai Lu <yhlu.kernel@gmail.com> wrote:

quoted text
> On Wed, Aug 20, 2008 at 2:15 AM, Ingo Molnar <mingo@elte.hu> wrote:
> >
> > * Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> >
> >> > This is true if he reverted just the 3def3d6d... commit, but if he
> >> > also reverts the similar, and immediately following, 1e934dda...
> >> > commit, then his 2.6.26 kernel runs fine.
> >>
> >> interesting,
> >>
> >> David, can you try only comment out
> >>
> >> late_initcall(lapic_insert_resource);
> >
> > i.e. the patch below?
> >
> > what's your theory, what could be the reason for David's lockups?
> 
> could be insert_resource related.
> 1. revert patch that change back insert_resource doesn't work
> 2. insert_resource for lapic address moved to late after ....
> 
> need to add debug printout for insert_resource/request_resource to 
> make sure thing going well

but what can happen if it does not "go well"? The resource list is 
basically there to make sure we dont overlap resources. But is there a 
real danger here for any overlap?

And insert_resource() differs from request_resource() in that 
insert_resource() allows "complete overlap". David has done printks of 
all resources in this thread - can you see anything suspicious in there?

and what's the connection to your e820 patches?

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/