Re: oops in bk pull (oct 03)

Linus Torvalds (torvalds@transmeta.com)
Fri, 4 Oct 2002 18:02:15 -0700 (PDT)


On Fri, 4 Oct 2002, Alexander Viro wrote:
>
> Hell knows. The only explanation I see (and that's not worth much) is that
> we somehow confuse the chipset and get crapped on something like next cache
> miss.

I don't see any better explanation right now, so I guess we just revert
that thing.

The only other notion I might come up with is stack corruption, ie the
code in pci_read_bases() might corrupt the return stack subtly (it does
add another local variable whose address is taken), causing a jump to a
random address on return. Compiler bug?

Linus

-
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/