lkml.org 
[lkml]   [2006]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: Call Trace: 2.6.17-rt5: Call Trace: <ffffffff802500fd>{out_of_memory+55}
From
Date
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
changes.

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

Daniel

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

\
 
 \ /
  Last update: 2006-08-07 17:39    [W:0.040 / U:0.296 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site