From: "Joop Boonen" <joop_boonen@web.de>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: linux-smp@vger.kernel.org
Subject: Re: smp memory problem
Date: Wed, 1 Mar 2006 08:41:21 +0100 (CET) [thread overview]
Message-ID: <54891.62.140.141.8.1141198881.squirrel@worldcitizen.demon.nl> (raw)
In-Reply-To: <20060228213323.8657324c.rdunlap@xenotime.net>
Hello Randy,
The Kernel version is: Linux version 2.6.16-rc3-git3-2-smp
The bluesmoke developer team is also looking into this. See:
http://sourceforge.net/mailarchive/forum.php?forum_id=43090 The archive is
not updated yet. :-( The subject is: smp memory problem with edac
Regards,
Joop Boonen.
On Wed, March 1, 2006 6:33 am, Randy.Dunlap wrote:
> On Tue, 28 Feb 2006 11:07:04 +0100 (CET) Joop Boonen wrote:
>
>> Hello All,
>>
>> I have the following problem. I have a feeling that there is kernel bug
>> related to memory access.
>>
>> By the way parallel to this i'm also looking for tests, to see wither
>> there is a hardware problem. I already did memory test for several
>> hours.
>> No problems found. I have a tiger s2460 mainload with 2 thouroughbred A
>> 1800+ processors on it.
>>
>> This is the error i get:
>>
>> EDAC MC0: UE page 0x0, offset 0x0, grain 536870912, row 0, labels "":
>> AMD762
>> Kernel panic - not syncing: EDAC MC0: UE page 0x0, offset 0x0, grain
>> 536870912, row 0, labels "": AMD762
>>
>> Badness in smp_call_function at arch/i386/kernel/smp.c:595
>> [<c0112968>] smp_call_function+0x52/0xc0
>> [<c0120c13>] printk+0x14/0x18
>> [<c01129e9>] smp_send_stop+0x13/0x1c
>> [<c01202d9>] panic+0x5d/0xec
>> [<f97389d6>] edac_mc_handle_ue+0x12a/0x13e [edac_mc]
>> [<c011a0aa>] move_tasks+0x1d5/0x212
>> [<c0294330>] _spin_unlock_irq+0x5/0xa7
>> [<c0238f2c>] pci_conf1_write+0x99/0xa7
>> [<c0239faa>] pci_write+0x1d/0x22
>> [<f95ca2e0>] amd76x_check+0xc3/0xf7 [amd76x_edac]
>> [<f97387db>] do_edac_check+0x19/0xaf [edac_mc]
>> [<f9738c55>] edac_kernel_thread+0x3a/0x92 [edac_mc]
>> [<f9738c1b>] edac_kernel_thread+0x0/0x92 [edac_mc]
>> [<c0102005>] kernel_thread_helper+0x5/0xb
>>
>> REMARK: I typed this over from the screen. So there might be typos in
>> it.
>> I have a digital foto of the screen. If needed i can send it. You
>> sertainly don't want it on the mailing list.
>
> What kernel version? (always)
>
> Does the photo have any more info than this?
> Can you put it on the web somewhere so that we can download it?
> If not, send it to me and I can do that if you want me to.
>
> ---
> ~Randy
>
prev parent reply other threads:[~2006-03-01 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 10:07 smp memory problem Joop Boonen
2006-03-01 5:33 ` Randy.Dunlap
2006-03-01 7:41 ` Joop Boonen [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=54891.62.140.141.8.1141198881.squirrel@worldcitizen.demon.nl \
--to=joop_boonen@web.de \
--cc=linux-smp@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).