Re: Call Trace: 2.6.17-rt5: Call Trace: <ffffffff802500fd>{out_of_memory+55}

From: Mark Knecht
Date: Mon Aug 07 2006 - 16:27:14 EST

Hi all,
Thanks Daniel. I've not seen this before on any kernels myself.
I'll keep an eye on it and see if it comes up again.

I appreciate the info.


On 8/7/06, Daniel Walker <dwalker@xxxxxxxxxx> wrote:
On Mon, 2006-08-07 at 08:19 -0700, Mark Knecht wrote:
> Hi all,
> I've never seen this on 2.6.17-rt5. Up until today it had always
> been quite stable. I was running MythTV at the time. Nothing out of
> the ordinary.

Those message are cause by the system running out of memory. I've see
MythTV make the system run out of memory on non-RT kernels (must be a
memory leak someplace). So I wouldn't think it related to any real time

> Excuse my lack of experience here but after an event like this what
> is the proper way to make sure the kernel is as stable as it can be?
> Do I need to clean anything up? Reboot? Or is the cleanup all
> automatic and everything is fine?

The kernel will kill some running user space tasks to free memory. But
the kernel should be fine after that.


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