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
Hi David,
On Tue, 12 Nov 2002, David Lloyd wrote:
>
> 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<===================================
On Fri, 20 Sep 2002, Neale Banks wrote:
>
> 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.
>
> --- linux-2.4.20-pre4/drivers/char/agp/agpgart_fe.c Mon Aug 13 03:38:48 2001
> +++ linux-2.4.20-pre4-ntb/drivers/char/agp/agpgart_fe.c Fri Sep 20 08:57:40 2002
> @@ -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<===================================
> 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.
Neale,
> 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
--
Angel of Music, why deny me?
Turning from true beauty!
Angel of music, do not shun me,
Turn to your strange Angel!
On Tue, 2002-11-12 at 11:06, David Lloyd wrote:
>
> Neale,
>
> > 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.