Bug#548630: #548630

To: Ben Hutchings <ben@decadent.org.uk>, 548630@bugs.debian.org
Subject: Bug#548630: #548630
From: Hans IJ <hans.ij@gmail.com>
Date: Sun, 18 Oct 2009 22:41:40 +0200
Message-id: <[🔎] b3812d420910181341j463bcb4em1cfad03e63a3cfc0@mail.gmail.com>
Reply-to: Hans IJ <hans.ij@gmail.com>, 548630@bugs.debian.org
In-reply-to: <[🔎] 1255556403.2488.226.camel@localhost>
References: <b3812d420909290203j26b643afjff47506bd61e7f95@mail.gmail.com> <[🔎] 1255229360.25061.79.camel@localhost> <b3812d420910141304v29da05f2v862b1a620619ccc4@mail.gmail.com> <[🔎] 1255556403.2488.226.camel@localhost>

Hi Ben,

I run some more tests with linux-image-2.6.30-2-686. My system has 2x2GB memory in dual channel configuration.

- When I removed one of the 2GB memory sticks, all went fine. I have tested both sticks. Both are ok.

- When I put 2x2GB in single channel configuration, all went fine

- I tested this on both MB's, all went fine

- I tested this with normal and largemem kernel. Again, all went fine.

- I have tested the 2X2GB dual channel configuration with the memtest86+, passed successfully

- I have tested the 2X2GB dual channel configuration with Windows 7. I was not able to trigger a crash.

--> I only have the crash with Linux when using the dual channel configuration. I am not sure if it is a memory issue. The sticks work fine when used stand alone or when used in single channel configuration (or with Windows). I am not an expert in this area. Any conclusions?

Reply to:

References:
- Bug#548630: #548630
  - From: Ben Hutchings <ben@decadent.org.uk>
- Bug#548630: #548630
  - From: Ben Hutchings <ben@decadent.org.uk>

Prev by Date: Re: Status of Linux 2.6.31
Next by Date: Re: Status of Linux 2.6.31
Previous by thread: Bug#548630: #548630
Next by thread: Processed: tagging 548259
Index(es):
- Date
- Thread