KDE issue

[Net Llama!]

On Thu, 7 Oct 2004 MHeinrich at genencor.com wrote:
> I am running Mandrake 9.1 and KDE 3.???  KDE does not seem to be running
> correctly.  What do I mean?  The kicker bar at the bottom is not there, it
> takes longer than 10 minutes to go from log in screen to finish logging
> in.  When I switch into command line mode (Alt-cntrl-F1) and log in as
> root, I get this error message:
>
> <1> Unable to handle kernel paging request at virtual address 8214b2e8
> printing eip:
> c0152532
> *pde = 00000000
> Oops: 0000
> sg st sr_mod sd_mod scsi_mod ide-cd cdrom floppy printer af_packet
> nls_iso8859-1 nls_cp850 vfat fat
> supermount 3c59x usb=ohci usbcore snd-pcm-oss snd-mixer-oss snd-emu10k1
> snd-rawmidi snd-pcm snd-timer
> snd-page-alloc snd-util-mem snd-ac97-codec snd-seq-device snd-dwdep snd
> soundcore
> CPU:    0
> EIP:    0010:[<c0152532>]  Not tainted
> EFLAGS: 00010287
> EIP is at d_lookup+0x62/0x110 [kernel]
> eax:  c214b2e8  ebx:  8214b2e8  exc:0000000d    edx:  c2140000
> esi:  8214b2d8  edi:  c10029ab  ebp:  c2035eb4  esp:  c2035e90
> ds:  0018       es:  0018       ss:  0018
> Process python (pid: 6807, stackpage=c0ce1000)
> Stack: c1f69013 8214b268 c214b2e8 c1f69023 c10029ab
>  "whole bunch of other addresses?"
> Call Trace:
> [<c01496c1>] cached_lookup+0x11/0x60 [kernel]
> [<c0149c77>] link+path_walk+0x397/0x6b0 [kernel]
> [<c014a119>] path_lookup+0x29/0x30 [kernel]
> [<c014a362>] __user_walk+0x32/0x50 [kernel]
> [<c014693e>] vfs_stat+0x1e/0x90 [kernel]
> [<c0146ef4>] sys_stat64+0x14/0x30 [kernel]
> [<c0137c64>] kmem_cach_free+0x14/0x30 [kernel]
> [<c013f2d2>] sys_open+0x72/0x90 [kernel]
> [<c0109093>] system_call+0x33/0x40 [kernel]
>
> Code: 8b 1b 39 7e 44 75 e7 8b 45 08 39 46 0c 75 df 8b 40 4c 85 c0
>
> I have no idea what this means or how it relates to me KDE problem.  Any
> suggestions on how to trouble shoot this issue would be greatly
> appreciated.

Youv'e got a kernel oops, which is VERY bad.  This either means that you
have a kernel bug, or a hardware problem (or both).  It looks like some
kind of python process (Process python (pid: 6807)) is what triggered the
oops.  If you're using a Mandrake kernel, then you need to contact
Mandrake to address this.  If you're running a vanilla kernel that you
built yourself, then either update to the latest stable version, or talk
to the LKML for help.

You can run the oops through ksymoops.  See
/usr/src/linux/scripts/ksymoops/README for more info.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Lonni J Friedman                                netllama at linux-sxs.org
Linux Step-by-step & TyGeMo                  http://netllama.ipfox.com