public inbox for linux-smp@vger.kernel.org
 help / color / mirror / Atom feed
From: "Vicente J. Ruiz Jurado" <vjrj@ourproject.org>
To: linux-smp@vger.kernel.org
Subject: SMP problems in Dual Xeon with 2.4.25 and 2.6.5
Date: Mon, 05 Apr 2004 17:38:03 +0200	[thread overview]
Message-ID: <1081179480.1250.699.camel@bangkok> (raw)

Hi everybody. 

I have a Dell Poweredge 1600SC (2 Xeons 2.40GHz) with problems running
kernels (2.4.* and 2.6.*) with SMP with or without hiperthreading. 

The machine is only 100% stable when I run a kernel without SMP (nosmp).
With kernels 2.4.* I get signals 8/11 doing kernel compilation. With
2.4.25 I get the segmentation fault in gcc only in one of 400
compilations (but sometimes with more frequency and sometimes with less
frequency). 

I have test my hardware with some dell diagnostic tools, with memtest86
for long without detect any problem. I have the BIOS firmware, the RAID
firmware, and the processors microcode up to date.

With 2.6.5 I get ocasional compiler errors compiling the kernel (2
errors after 200 compilations), for instance:
  xfs_bmap.c:5194: internal compiler error: in expand_stmt, at   
  c-semantics.c:869
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See <URL:http://gcc.gnu.org/bugs.html> for instructions.

and also sometimes I see strange ^@^@^@^@ chars in the files generated
during the compilation (which fails). For instance, one line in my
mm/.depend:

   /usr/src/linux-2.4.25-test/ð^]^@^@ude/linux/bootmem.h \

I have tried different kernel parameters (noapic apm=off acpi=off) but
without success with smp (with or without hyperthreading).

My configs:
http://213.97.99.199/otros/config2.6.5
http://213.97.99.199/otros/config2.4.25

I'm using debian, but also happens with other distros.

Any idea? Now, I my mind is blank ... It's this the correct forum to ask
this question?

Any help will be appreciated.

TIA,

Vicente


                 reply	other threads:[~2004-04-05 15:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1081179480.1250.699.camel@bangkok \
    --to=vjrj@ourproject.org \
    --cc=linux-smp@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