public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Strange Memory Corruption Problem with Core2Duo E6700, P965 Chipset MB and >=4GB RAM
Date: Mon, 17 Dec 2007 02:15:43 +0100	[thread overview]
Message-ID: <20071217011543.GA3226@citd.de> (raw)
In-Reply-To: <20071216013947.GA3679@citd.de>

On 16.12.2007 02:39, Matthias Schniedermeyer wrote:
> Hi

It appears i found my culprit. <Knocking on wood> :-)

I have a ISDN-controller which is driven by the HFC-PCI-driver and it 
appears to not be 64bit-safe.

I will test more thorough after i have relocated the card to another 
computer.





Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.


      reply	other threads:[~2007-12-17  1:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-16  1:39 Strange Memory Corruption Problem with Core2Duo E6700, P965 Chipset MB and >=4GB RAM Matthias Schniedermeyer
2007-12-17  1:15 ` Matthias Schniedermeyer [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=20071217011543.GA3226@citd.de \
    --to=ms@citd.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