Messages in this thread |  | | Subject | Re: [: Stumped about where to post an Oops!] | | From | "Stephen C. Tweedie" <> | | Date | 02 Aug 2004 11:21:31 +0100 |
| |
Hi,
On Mon, 2004-07-26 at 21:34, Andrew Morton wrote: > The 0x00040004 access address almost looks like some pointer-poisoning > thing.
It's the result of doing
> 0: 39 72 04 cmp %esi,0x4(%edx) <=====
when %edx is 0x00040000.
That looks to me like a single bit-flip in memory, and get_hash_table is one of those functions that shows up in traces all the time when you've got bad memory (it's one of the kernel's hottest functions for doing list-walks over dynamically-allocated data structures.)
This footprint would definitely have me reaching for memtest86 as the next step. It certainly has all the hallmarks of a classic bit-flip bad memory trace.
--Stephen
- 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/
|  |