From: Bernd Schubert <bernd-schubert@web.de>
To: <linux-kernel@vger.kernel.org>
Subject: Symoops with Dual-Serverworks board
Date: Sat, 22 Jun 2002 00:24:56 +0200 [thread overview]
Message-ID: <200206220024.56296.bernd-schubert@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
Hi,
a few month ago I already wrote about this, but at this time the machine was
instable due to defect ECC-RAM, so I didn't create a symoops report.
Now the RAM is exchanged, the machine is much more stable, but not stable
enough, it keeps oopsing and sometimes it also crashes at all (no reaction to
keyboard (though Magic Sysrq's are enabled) and network).
Well the logfile is full of messages like this:
Jun 19 15:50:45 noether kernel: mtrr: Serverworks LE sdetected.
Write-combining disabled.
Jun 19 15:50:45 noether kernel: mtrr: your processor doesn't support
write-combining
Jun 19 15:50:45 noether kernel: mtrr: Serverworks LE detected. Write-combining
disabled.
Jun 19 15:50:45 noether kernel: mtrr: your processor doesn't support
write-combining
Unfortunality, the bios has no option to disable Write-combining (as someone
suggested).
For the last oops I've created a ksymoops report. Well, its my first one and I
hope I havn't made any mistakes (actually I havn't read the ksymoops manpage
in detail). The ksymoops output is attached as bzip2-file.
Thanks in advance for any help,
Bernd
PS: Some system specific details are also attached. If you need more
information, please don't hesitate to ask.
--
Bernd Schubert
Physikalisch Chemisches Institut
Abt. Theoretische Chemie
INF 229, 69120 Heidelberg
Tel.: 06221/54-5210
e-mail: bernd.schubert@pci.uni-heidelberg.de
[-- Attachment #2: symoops_noether.out.bz2 --]
[-- Type: application/x-bzip2, Size: 1130 bytes --]
[-- Attachment #3: cpuinfo.bz2 --]
[-- Type: application/x-bzip2, Size: 423 bytes --]
[-- Attachment #4: boot.msg.bz2 --]
[-- Type: application/x-bzip2, Size: 4702 bytes --]
reply other threads:[~2002-06-21 22:24 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=200206220024.56296.bernd-schubert@web.de \
--to=bernd-schubert@web.de \
--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