public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Thomas Oulevey <thomas.oulevey@elonex.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4 lockup issue (flush_tlb_all)
Date: Sun, 7 Nov 2004 15:11:52 -0200	[thread overview]
Message-ID: <20041107171152.GA29846@logos.cnet> (raw)
In-Reply-To: <1099481807.4714.85.camel@localhost.localdomain>

On Wed, Nov 03, 2004 at 12:36:47PM +0100, Thomas Oulevey wrote:
> Hello,
> 
> We are experiencing some lockup problems with our SMP configuration. 
> Here are the details :
> - The computers lockup with no relevant logs.
> - The kernel still replies to ping but higher level services are not
> responding.
> - After few hours (5-8), the kernel answers again and the load is around
> 40 then decreasing. 
> 
> We manage to get some SysRq showPc output (screenshot :
> http://www.elonex.ch/shot/)
> According to the basic sysreq debugging, the problem seems to be related
> to the function flush_tlb_all, and it is triggered with a write or read
> (local or on nfs sometimes).
> 
> I looked at the LKML, and didn't find any known issues.
> Maybe it has been corrected but not backported by redhat ! 
> I'll appreciate any help.
> 
> Thank you in advance.
> 
> detailed configuration :
> ---------------
> Processor   : 2 x 2.8Ghz Pentium Xeon
> Motherboard : Intel se7501cw2
> Memory      : 4 x 512MB DDR 266 ECC registered
> Kernel      : 2.4.20-31 (Redhat 7.3 with updates)

You should report this one to the RH people, but I think RH 7.3 
isnt support anymore? 

Upgrading the kernel is a good idea.

      reply	other threads:[~2004-11-07 20:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03 11:36 2.4 lockup issue (flush_tlb_all) Thomas Oulevey
2004-11-07 17:11 ` Marcelo Tosatti [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=20041107171152.GA29846@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.oulevey@elonex.ch \
    /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