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

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

Post by Neale Bank » Wed, 13 Nov 2002 12:50:07



Hi David,


> 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<===================================


> Date: Fri, 20 Sep 2002 09:15:27 +1000 (EST)



> 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

>    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<===================================

Quote:> 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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

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

Post by David Lloy » Wed, 13 Nov 2002 13:00:11


Neale,

Quote:> 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!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

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

Post by Alan Co » Wed, 13 Nov 2002 16:30:12



> 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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. atyfb on kernel 2.4.18 with debian woody

Hi,

I've a problem with atyfb framebuffer with my ati 3d rage pro card (mach64).
When I compile my kernel with atyfb (without Vesa standard), the boot resolution
is 640x400.
I tried to put some paramters like video=atyfb:mode:800x600 or/and vga=789 at
lilo prompt to change the resolution but no change.
After the boot, I can change the resolution with fbset "800x600-75" and atyfb
works fine (I can use fbi) and fbset tell me that it is using atyfb.

If I compile my kernel with Vesafb, I can change boot resolution with vga=789
(800x600) or vga=792 (1024x768) but I can't use fbi (I think my ati card is not
full compatible).

If I compile both frame buffer devices (atyfb and vesafb), I can't use atyfb but
only vesafb. (i tried video=atyfb but no change)

Have you an idea? what's wrong ?

Thanks

2. Howtdo you share files between win95 and linux

3. Debian (woody, kernel 2.4.18) on Compaq Armada 1590DT - Power saving kills X server

4. Help: lowlevel.o errors during Kernel compile

5. Linux Kernel Crash - Vanilla 2.4.18/Redhat 2.4.18-5

6. ftp server shut down

7. Linux Kernel Crash - Vanilla 2.4.18/Redhat 2.4.18-5 (2nd try =) )

8. Hex

9. Can boot after recompile 2.4.18 kernel using Debian kernel-package

10. Debian 3.0/kernel 2.4.18 ARP "reflection?"

11. Problem Compile Kernel 2.4.18 in Debian 3.0

12. pppd giving error with 2.4.18 kernel, everything OK with 2.4.7 kernel

13. VMware 3.1 with Debian & 2.4.18 kernel