From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.13.4 kernel Oops - proc related
Date: Thu, 12 Apr 2007 10:01:07 +0200 [thread overview]
Message-ID: <9a8748490704120101o7ae2645ei12bb096971da6dfe@mail.gmail.com> (raw)
Hi everyone,
Yesterday one of my servers Oops'ed on me :-(
The server was running an old 2.6.13.4 kernel.
I got a screenshot of the Oops which is available here :
http://www.kernel.org/pub/linux/kernel/people/juhl/images/2.6.13.4-crash.png
Even though this is a rather old kernel, I wanted to report the crash
just in case it's not a known bug. If it is already known and fixed,
then just ignore this mail.
Userspace is also rather old (but the kernel was not build on this box
with that ancient compiler, it's just running here) :
# scripts/ver_linux
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
Linux srv.mydomain.net 2.6.13.4 #1 SMP Wed Nov 16 11:13:51 CET 2005 i686 unknown
Gnu C 2.96
Gnu make 3.79.1
binutils 2.11.93.0.2
util-linux 2.11n
mount 2.11n
module-init-tools 3.0-pre1
e2fsprogs 1.27
reiserfsprogs 2001------------->
reiser4progs fsck.reiser4:
quota-tools 3.06.
nfs-utils 1.0.5
Linux C Library 2.2.5
Dynamic linker (ldd) 2.2.5
Procps 2.0.11
Net-tools 1.60
Console-tools 0.3.3
Sh-utils 2.0.11
Modules Loaded iptable_nat
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next reply other threads:[~2007-04-12 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 8:01 Jesper Juhl [this message]
2007-04-14 9:42 ` Alexey Dobriyan
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=9a8748490704120101o7ae2645ei12bb096971da6dfe@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome