From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 15 Jan 2001 19:22:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 15 Jan 2001 19:22:01 -0500 Received: from smtp3.jp.psi.net ([154.33.63.113]:48146 "EHLO smtp3.jp.psi.net") by vger.kernel.org with ESMTP id ; Mon, 15 Jan 2001 19:21:50 -0500 From: "Rainer Mager" To: "Marcelo Tosatti" Cc: Subject: RE: Oops with 4GB memory setting in 2.4.0 stable Date: Tue, 16 Jan 2001 09:21:39 +0900 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0005_01C07F9D.BB24D480" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C07F9D.BB24D480 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Ok, now were making progress. I did as you said and have attached (really!) the new parsed output. Now we have some useful information (I hope). I still got lots of warnings on symbols (which I have edited out of the parsed file for the sake of briefness). What's the next step? --Rainer > -----Original Message----- > From: linux-kernel-owner@vger.kernel.org > [mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Marcelo Tosatti > Sent: Tuesday, January 16, 2001 7:09 AM > To: Rainer Mager > Cc: linux-kernel@vger.kernel.org > Subject: RE: Oops with 4GB memory setting in 2.4.0 stable > > >>EIP; f889e044 <===== > Trace; f889d966 > Trace; c0140c10 > Trace; c0140e7c > Trace; c0140f9e > Trace; c0140e7c > > It seems the oops is happening in a module's function. > > You have to make ksymoops parse the oops output against a System.map which > has all modules symbols. Load each module by hand with the insmod -m > option ("insmod -m module.o") and _append_ the outputs to System.map. > > After that you can run ksymoops against this new System.map. ------=_NextPart_000_0005_01C07F9D.BB24D480 Content-Type: application/octet-stream; name="oops.parsed.edit" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="oops.parsed.edit" ksymoops 0.7c on i686 2.4.0. Options used=0A= -v /boot/vmlinux-2.4.0-bigmem (specified)=0A= -K (specified)=0A= -L (specified)=0A= -o /lib/modules/2.4.0/ (default)=0A= -m ./System.map-2.4.0-bigmem (specified)=0A= =0A= No modules in ksyms, skipping objects=0A= Unable to handle kernel NULL pointer dereference at virtual address = 00000000=0A= f889e044=0A= *pde =3D 00000000=0A= Oops: 0002=0A= CPU: 1=0A= EIP: 0010:[]=0A= Using defaults from ksymoops -t elf32-i386 -a i386=0A= EFLAGS: 00010246=0A= eax: 00000000 ebx: d5762800 ecx: 00000400 edx: c19665fc=0A= esi: d55be120 edi: 00000000 ebp: d5764260 esp: d5505f1c=0A= ds: 0018 es: 0018 ss: 0018=0A= Process ls (pid: 865, stackpage=3Dd5505000)=0A= Stack: d5762800 d55be120 d5764260 d5764260 d55be120 00000000 f889d966 = d55be120=0A= d5762800 d5504000 d5764260 fffffffe fffffffb d5762800 d5764260 = d55be120=0A= 00000000 d5764260 bffffa40 00000006 c0140c10 d5764260 d5505fb0 = c0140e7c=0A= Call Trace: [] [] [] [] = [] []=0A= Code: f3 ab e9 8b 00 00 00 90 8d 74 26 00 8b 44 24 14 c7 00 00 00=0A= =0A= >>EIP; f889e044 <=3D=3D=3D=3D=3D=0A= Trace; f889d966 =0A= Trace; c0140c10 =0A= Trace; c0140e7c =0A= Trace; c0140f9e =0A= Trace; c0140e7c =0A= Trace; c0108f4b =0A= Code; f889e044 =0A= 00000000 <_EIP>:=0A= Code; f889e044 <=3D=3D=3D=3D=3D=0A= 0: f3 ab repz stos %eax,%es:(%edi) = <=3D=3D=3D=3D=3D=0A= Code; f889e046 =0A= 2: e9 8b 00 00 00 jmp 92 <_EIP+0x92> f889e0d6 = =0A= Code; f889e04b =0A= 7: 90 nop =0A= Code; f889e04c =0A= 8: 8d 74 26 00 lea 0x0(%esi,1),%esi=0A= Code; f889e050 =0A= c: 8b 44 24 14 mov 0x14(%esp,1),%eax=0A= Code; f889e054 =0A= 10: c7 00 00 00 00 00 movl $0x0,(%eax)=0A= =0A= =0A= 367 warnings issued. Results may not be reliable.=0A= ------=_NextPart_000_0005_01C07F9D.BB24D480-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/