All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Willy Tarreau <willy@w.ods.org>,
	linux mailing-list <linux-kernel@vger.kernel.org>
Subject: Re: X killed
Date: Tue, 17 Jan 2006 20:54:51 +0000	[thread overview]
Message-ID: <43CD599B.8050002@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0601172111070.11929@yvahk01.tjqt.qr>

Jan Engelhardt wrote:
>>My point is that there is no way to tell what kills me. No messages in
>>syslog...nothing. Surely the OOM killer would send a message to ksyslog, or at
>>least dmesg?
>>
> 
> Yes, OOM usually does printk(). So it depends on how you have syslog set 
> up (and the console loglevel - which is reponsible for bringing it right 
> to console).
> 
> 
> Jan Engelhardt

So, I can conclude that as I am not seeing any OOM messages in dmesg, 
that the OOM is not responsible for my kills. Even without syslog set 
up, I should see the OOM in dmesg shouldn't I?

So, I have a mystery reason why X getting killed.

Can anyone else suggest any other possible causes for unexpected X 
getting killed?

James


  parent reply	other threads:[~2006-01-17 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 17:36 X killed James Courtier-Dutton
2006-01-15 19:27 ` Willy Tarreau
2006-01-17 12:40   ` James Courtier-Dutton
2006-01-17 20:12     ` Jan Engelhardt
2006-01-17 20:17       ` Lee Revell
2006-01-19 16:06         ` Nix
2006-01-17 20:54       ` James Courtier-Dutton [this message]
2006-01-17 21:32         ` Ram Gupta
2006-01-17 21:41           ` Willy Tarreau
2006-01-19 11:09             ` James Courtier-Dutton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=43CD599B.8050002@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=willy@w.ods.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.