From: Anton Blanchard <anton@samba.org>
To: Darren Williams <dsw@gelato.unsw.edu.au>
Cc: Manfred Spraul <manfred@colorfullife.com>,
LKML <linux-kernel@vger.kernel.org>,
akpm@osdl.org
Subject: Re: [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2.5GB (correction)
Date: Wed, 25 Feb 2004 12:05:54 +1100 [thread overview]
Message-ID: <20040225010553.GF5801@krispykreme> (raw)
In-Reply-To: <20040225005804.GE18070@cse.unsw.EDU.AU>
> I have updated to the latest bk and new output can be found at:
> http://quasar.cse.unsw.edu.au/~dsw/public-files/lemon-debug/
> kern-log-bk
>
> Also I am quite confident that it is not a hardware problem.
Didnt itanium 1 use that dodgy software IOMMU code? From memory you
started having problems at around 2GB, perhaps thats near the cutoff point.
Anton
next prev parent reply other threads:[~2004-02-25 1:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-24 6:38 [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2.5GB (correction) Manfred Spraul
2004-02-24 6:56 ` Andrew Morton
2004-02-24 8:45 ` Darren Williams
2004-02-24 17:40 ` Manfred Spraul
2004-02-25 0:58 ` Darren Williams
2004-02-25 1:05 ` Anton Blanchard [this message]
2004-02-25 6:21 ` Manfred Spraul
2004-02-25 7:03 ` David S. Miller
2004-02-25 7:22 ` Andrew Morton
2004-02-25 8:24 ` Darren Williams
2004-02-25 17:18 ` Manfred Spraul
2004-02-26 0:30 ` Darren Williams
2004-02-25 8:55 ` Darren Williams
2004-02-25 10:18 ` Peter Chubb
2004-02-25 6:17 ` Darren Williams
-- strict thread matches above, loose matches on Subject: below --
2004-02-24 0:22 [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2GB Darren Williams
2004-02-24 1:14 ` [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2.5GB (correction) Darren Williams
2004-02-24 1:14 ` Darren Williams
2004-02-26 1:09 ` Darren Williams
2004-02-24 21:44 ` Darren Williams
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=20040225010553.GF5801@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=dsw@gelato.unsw.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.