From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: Mike Galbraith <bitbucket@online.de>
Cc: linux-kernel mlist <linux-kernel@vger.kernel.org>,
linux-stable mlist <stable@kernel.org>,
Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Subject: Re: 3.0.60: general protection fault: 0000, Fixing recursive fault but reboot is needed
Date: Mon, 15 Apr 2013 12:05:12 +0200 [thread overview]
Message-ID: <20130415100512.GS28496@pcnci.linuxbox.cz> (raw)
In-Reply-To: <1366014586.4962.17.camel@marge.simpson.net>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
Hi Mike,
> Feeding that to scripts/decodecode
thanks, didn't know about that!
.
.
.
.
>
> That's here in dup_fd():
> for (i = open_files; i != 0; i--) {
> struct file *f = *old_fds++;
> if (f) {
> get_file(f);
>
> It's doing that get_file(), grabbing a reference to all open files in a
> loop, but old_fds points off into lala land, so I'd say you must have
> memory corruption, and open_files is garbage. Seeing "One of our
> servers..", operative word being "one", I'd tend to suspect heat or such
> given the box exploded in this extremely heavily exercised spot.
yes, that could be. I'll have this box checked, including memtest etc.
thanks a lot for Your time!
nik
>
> -Mike
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28.rijna 168, 709 00 Ostrava
tel.: +420 591 166 214
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2013-04-15 10:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 5:33 3.0.60: general protection fault: 0000, Fixing recursive fault but reboot is needed Nikola Ciprich
2013-04-15 8:29 ` Mike Galbraith
2013-04-15 10:05 ` Nikola Ciprich [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=20130415100512.GS28496@pcnci.linuxbox.cz \
--to=nikola.ciprich@linuxbox.cz \
--cc=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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