Skip to contentSkip to conversation

Kernel Memory Errors (Debian Woody 2.4.18-bf2.4)

DISCUSSION David Lloyd 4 participants 4 messages Nov 11, 2002 – Nov 12, 2002

lore
Share & tools
lore
#0 lore raw

I am experiencing some strange behaviour with Debian Woody. I have attached a log as plain text and the output of dmesg.

I suspect it may be faulty RAM.

This occurs ONLY when I am in a KDE kdm managed X session and press ctrl+alt+f[1-6] to get to a virtual console. It's not always consistent but that's when it's most likely to happen.

X disappears from underneath me as well.

DSL

Nov 12 09:08:41 lothlorien kernel: memory : ca174cd0
Nov 12 09:08:41 lothlorien kernel: memory : 00000000
Nov 12 09:08:41 lothlorien kernel: memory : ca174410
Nov 12 09:08:42 lothlorien kdm[4949]: session start failed
Nov 12 09:08:43 lothlorien kernel: memory : ca174cd0
#1 lore raw

Hi David,

Quoted 5 lines · David Lloyd

I am experiencing some strange behaviour with Debian Woody. I have attached a log as plain text and the output of dmesg.

I suspect it may be faulty RAM.

Nah, it's most likely not telling you anything like that. Your log:

	Nov 12 09:08:41 lothlorien kernel: memory : ca174cd0
	Nov 12 09:08:41 lothlorien kernel: memory : 00000000
	Nov 12 09:08:41 lothlorien kernel: memory : ca174410
	Nov 12 09:08:42 lothlorien kdm[4949]: session start failed
	Nov 12 09:08:43 lothlorien kernel: memory : ca174cd0

The giveaway is the space before the colon. Here's what I previously posted on this issue:

===================================8<===================================

Quoted 25 lines · Neale Banks

Date: Fri, 20 Sep 2002 09:15:27 +1000 (EST)
From: Neale Banks <[email protected]>
To: [email protected]
Cc: Gustavo Lozano <[email protected]>
Subject: [PATCH 2.(2|4)] agpgart_fe printk is too terse

Appended patch against 2.4.20-pre4 fixes a (IMHO) way-too-terse printk in drivers/char/agp/agpgart_fe.c

Motivation is that when scrounging through syslog etc finding an entry that simply says "memory : <value>" leaves rather too much to the imagination (not to mention being interesting to grep out of the source).

This applies to 2.2 also (but has already been applied to 2.5).

Thanks,
Neale.

drivers/char/agp/agpgart_fe.c line 307

Quoted 8 lines
drivers/char/agp/agpgart_fe.c +1 -1
@@ -301,7 +301,7 @@
 	agp_memory *memory;
 
 	memory = agp_allocate_memory(pg_count, type);
-   	printk(KERN_DEBUG "memory : %p\n", memory);
+   	printk(KERN_DEBUG "agp_allocate_memory: %p\n", memory);
 	if (memory == NULL) {
 		return NULL;
 	}

===================================8<===================================

Quoted 5 lines

This occurs ONLY when I am in a KDE kdm managed X session and press ctrl+alt+f[1-6] to get to a virtual console. It's not always consistent but that's when it's most likely to happen.

X disappears from underneath me as well.

Probably an X issue that's not relevant here.

What's the video card?

HTH,
Neale.

#2 lore raw

Neale,

Quoted 3 lines

Probably an X issue that's not relevant here.

What's the video card?

It's an i810 Intel Card on an all-in-one mainly SiS based board...not there until tomorrow when I can get more details about it.

DSL

Signature · 4 lines
Angel of Music, why deny me?
 Turning from true beauty!
Angel of music, do not shun me,
 Turn to your strange Angel!
#3 lore raw
Quoted 9 lines · David Lloyd

Neale,

Quoted 3 lines

Probably an X issue that's not relevant here.

What's the video card?

It's an i810 Intel Card on an all-in-one mainly SiS based board...not there until tomorrow when I can get more details about it.

If it is an i810 using the onboard video make sure you are using XFree86 4.1/4.2 and the -fixed- (using pci_alloc_*) kernel module for it. Otherwise you may well get weird happenings

Marcelo's current tree has the kernel stuff, supporting XFree 4.1/4.2, but 4.2 is IMHO a lot better on i810 especially at 3D.