Re: 2.6.18-stable release plans?

[Chris Rankin]

> That's surely no reason to dump 2.6.19.x, you'll find the occasional
> such report on every(?) release since page mapcount went into 2.6.7.

This was the only time I've seen it, before or since.

> Oftentimes it's bad RAM (try memtest86)

There is nothing wrong with my RAM. I tested it quite extensively when I upgraded to 2 GB.

> sometimes it's a bad driver (probably the case for the tainted P report appended
> to your untainted one), sometimes it's unidentified memory corruption.

But MY kernel is clearly untainted. So what other explanation is there apart from a kernel bug?

Cheers,
Chris



		
___________________________________________________________ 
All New Yahoo! Mail ? Tired of unwanted email come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/