All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis BUCHER <dbucherml@hsolutions.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel crashing with reare bug
Date: Fri, 02 Apr 2010 22:08:04 +0200	[thread overview]
Message-ID: <4BB64EA4.40601@hsolutions.ch> (raw)
In-Reply-To: <4BB64E5E.5050706@hsolutions.ch>

Le 02.04.2010 22:06, Denis BUCHER a écrit :
> Dear all,
>
> I am sorry to post a personal problem, but I saw it nowhere on the web,
> therefore I think it's really a special problem. Our server is regularly
> crashing (every 2 months), always too fast to get any log.
>
> But today we got this :
>
> kernel: alloc_fd: slot 0 not NULL!
>
> I would be very interested to know what it means ?!
>
> (Not being subscribed to the list, please answer personally...)
>
> Have a nice day, and thanks in advance for any hint :-)
>
> Denis


Maybe I should add :

kernel: Linux version 2.6.27.25-78.2.56.fc9.i686 (mockbuild@) (gcc 
version 4.3.0 20080428 (Red Hat 4.3.0-8) (GCC) ) #1 SMP Thu Jun 18 
12:47:50 EDT 2009

      reply	other threads:[~2010-04-02 20:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02 20:06 kernel crashing with reare bug Denis BUCHER
2010-04-02 20:08 ` Denis BUCHER [this message]

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=4BB64EA4.40601@hsolutions.ch \
    --to=dbucherml@hsolutions.ch \
    --cc=linux-kernel@vger.kernel.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.