Re: [PATCH 0/1] Recurse when searching for empty slots in resourcestrees

From: Linus Torvalds
Date: Wed Jun 17 2009 - 16:13:26 EST

On Wed, 17 Jun 2009, Andrew Patterson wrote:
> >
> > This is why I'd really like to see the output of my test-patch. It would
> > show exactly _where_ that resource is inserted, and the whole call-chain.
> >
> > I'm appending a version that only does it for resources that have names
> > starting with "PCI Bus", so it should be less noisy. But again, it's
> > totally untested.
> >
> Here you go (I can provide the full boot log if needed). Note, there is
> nothing for c3 here:

Ok, so that means it got inserted into the resource tree some other way
entirely. Or maybe the name got changed after-the-fact. Both of which
imply that something is really really wrong.

The ones your trace _does_ show are the ones that got inserted correctly
and aren't buggy. Can anybody see how that buggy resource got inserted?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at