public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marek Habersack <grendel@caudium.net>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OOPS] with 2.4.25 - same on several machines
Date: Wed, 3 Mar 2004 13:42:29 +0100	[thread overview]
Message-ID: <20040303124229.GA1221@thanes.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0403030719300.2537-100000@dmt.cyclades>

[-- Attachment #1: Type: text/plain, Size: 927 bytes --]

On Wed, Mar 03, 2004 at 07:21:23AM -0300, Marcelo Tosatti scribbled:
[snip]
> > Mar  1 17:47:24 colo19 kernel: 
> > Mar  1 17:47:24 colo19 kernel: Code: 8b 7d 08 ff 48 14 0f 94 c0 84 c0 75 18 8b 5c 24 08 8b 74 24 
> > 
> > The processes in all cases were different (a shell script, lsof, apache).
> > The kernels are patched with grsec2 and libsata, but it doesn't seem to be
> > relevant in this case. Could anybody shed some light on it? If necessary, I
> > will post the machine configs and all the information needed to diagnose.
> 
> Hi Marek, 
> 
> <standard reply>
> 
> Can you reproduce the problem on vanilla 2.4.25 ? 
I'll try, it will probably take a while, at least till the weekend. The only
common pattern between the machines was the uptime - slightly above 36h. I
will be able to install 2.4.25 vanilla tomorrow, so I suppose Sunday at the
latest I will have some results.

thanks

marek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-03-03 12:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-02 22:36 [OOPS] with 2.4.25 - same on several machines Marek Habersack
2004-03-03 10:21 ` Marcelo Tosatti
2004-03-03 12:42   ` Marek Habersack [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=20040303124229.GA1221@thanes.org \
    --to=grendel@caudium.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com \
    /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