tags 548630 + moreinfo
quit
Hi,
Hans IJ wrote:
> I cannot use the hardware to reproduce. It is currently my LAMP server, and
> used 24/7. Sorry. I was able to fix at that time the bug by putting the two
> DDR modules in 32 bit configuration, and not in 64 bit.
>
> I hope this helps a bit...
No
Hi Jonathan,
I cannot use the hardware to reproduce. It is currently my LAMP server, and
used 24/7. Sorry. I was able to fix at that time the bug by putting the two
DDR modules in 32 bit configuration, and not in 64 bit.
I hope this helps a bit...
Best regards
Hans
On Sat, Sep 3, 2011 at 7:36 P
Hi,
Hans IJ wrote:
> I can reproduce this problem on both an ASUS P5Q-VM and Intel DG45ID
> Motherboard. Both MB's have same ICH10 chipset.
> Let me know if you need more.
Sorry for the loong delay. The assertion triggered here is in
mm/vmscan.c, function isolate_lru_pages():
s
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 tes
On Wed, 2009-10-14 at 22:04 +0200, Hans IJ wrote:
> Hi Ben
>
> I tested with linux-image-2.6.30-2-686. It did not solve the problem.
>
> I did do another test. I was using luks/dm-crypt on both drives. I
> also tested now on a drive w/o encryption. It still crashed, but
> *only* after 100GB, w
On Tue, 2009-09-29 at 11:03 +0200, Hans IJ wrote:
> Additional testing information:
> - Setting BIOS IDE mode to "IDE" does not solve the problem. It does
> reproduce a bit more random, but it does happen if the transferred
> data is large enough.
> - Re-tested with Ubuntu 9.04, with latest updates
I booted with kernel 2.6.26-1-686 instead of kernel 2.6.26-2-686
Same crash happened, but I was able to catch folliwing trace at the remote
syslog:
kernel: [ 1393.297389] kernel BUG at mm/vmscan.c:725!
...hope this helps!
Additional testing information:
- Setting BIOS IDE mode to "IDE" does not solve the problem. It does
reproduce a bit more random, but it does happen if the transferred data is
large enough.
- Re-tested with Ubuntu 9.04, with latest updates: Same Problem happens.
- To rule out memory issues: memtest
Package: linux-image-2.6.26-2-686
Version: 2.6.26-19
Severity: important
System was configured in BIOS with IDE mode set to AHCI.
- ASUS p5q-vm MB, latest BIOS.
- When having heavy disk writing (disk to disk, or via network rsync from
machine 1 to
target machine), system hangs after several GBy
9 matches
Mail list logo
