All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gordon Sadler <gbsadler1@lcisp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: 2.4.4 oops, will not boot
Date: Wed, 2 May 2001 22:39:12 -0500	[thread overview]
Message-ID: <20010502223912.A7803@debian-home> (raw)
In-Reply-To: <20010502030735.A650@debian-home> <3AEFF4CB.4D2CBE36@uow.edu.au>
In-Reply-To: <3AEFF4CB.4D2CBE36@uow.edu.au>; from andrewm@uow.edu.au on Wed, May 02, 2001 at 09:51:39PM +1000

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

On Wed, May 02, 2001 at 09:51:39PM +1000, Andrew Morton wrote:
> Envelope-to: gbsadler@localhost
> From: Andrew Morton <andrewm@uow.edu.au>
> X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.3-ac13 i686)
> To: Gordon Sadler <gbsadler1@lcisp.com>
> Subject: Re: PROBLEM: 2.4.4 oops, will not boot
> 
> Gordon Sadler wrote:
> > 
> > Please CC on replies.
> > Attached is REPORTING-BUGS template from source, and a hand copied oops
> > that I ran through ksymoops. I really hope this is resolved, anything
> > further needed, just ask.
> 
> Unfortunately the ksymoops output doesn't show the call trace.
> Can you please try again?  A reproducable oops is, err, rather
> important.  The syntax to feed into ksymoops is
> 
> Call Trace: [<c0111234>] [<c0123456>] ...
> 
> Thanks.
> 
Right, I see the problem now.. s/Calltrace/Call Trace/

Reran oops through ksymoops with change to Call Trace, output attached.



[-- Attachment #2: ksym.out --]
[-- Type: text/plain, Size: 2082 bytes --]

ksymoops 2.4.1 on i686 2.2.19.  Options used
     -V (default)
     -K (specified)
     -L (specified)
     -o /lib/modules/2.4.4/ (specified)
     -m /boot/System.map-2.4.4 (specified)

No modules in ksyms, skipping objects
Unable to handle kernel NULL pointer dereference at virtual address 00000014 printing EIP: c01254b5
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010: [<c01254b5>]
Using defaults from ksymoops -t elf32-i386 -a i386
eflags: 00010013
eax: c1227e08   ebx: c1227e08     ecx: c7e3ff68       edx: 00000000
esi: 00000286   edi: 00000007     ebp: c12343c0       esp: c7e3feec
ds: 0018        es: 0018       ss: 0018
stack: 00000000 c1263080 c12630dc c013ec88 c1277e08 00000007 00000000 c1263080
       c12630dc c12343c0 00000005 c01370c8 c12343c0 c7e3ff68 c7e3ff68 00000000
       c12343c0 c7e3ffa4 c0137819 c12343c0 c7e3ff68 00000000 c1265000 00000000
Call Trace: [<c013ec88>] [<c01370c8>] [<c0137819>] [<c0136e4a>] [<c0137e3c>] [<c0134f36>] [<c0106b9b>]
Code: 8b 42 14 ff 42 10 89 c1 0f af 4b 0c 03 4a 0c 8b 44 82 18 89

>>EIP; c01254b5 <kmem_cache_alloc+15/60>   <=====
Trace; c013ec88 <d_alloc+18/190>
Trace; c01370c8 <real_lookup+38/c0>
Trace; c0137819 <path_walk+579/7c0>
Trace; c0136e4a <getname+5a/a0>
Trace; c0137e3c <__user_walk+3c/60>
Trace; c0134f36 <sys_lstat64+16/70>
Trace; c0106b9b <system_call+33/38>
Code;  c01254b5 <kmem_cache_alloc+15/60>
00000000 <_EIP>:
Code;  c01254b5 <kmem_cache_alloc+15/60>   <=====
   0:   8b 42 14                  mov    0x14(%edx),%eax   <=====
Code;  c01254b8 <kmem_cache_alloc+18/60>
   3:   ff 42 10                  incl   0x10(%edx)
Code;  c01254bb <kmem_cache_alloc+1b/60>
   6:   89 c1                     mov    %eax,%ecx
Code;  c01254bd <kmem_cache_alloc+1d/60>
   8:   0f af 4b 0c               imul   0xc(%ebx),%ecx
Code;  c01254c1 <kmem_cache_alloc+21/60>
   c:   03 4a 0c                  add    0xc(%edx),%ecx
Code;  c01254c4 <kmem_cache_alloc+24/60>
   f:   8b 44 82 18               mov    0x18(%edx,%eax,4),%eax
Code;  c01254c8 <kmem_cache_alloc+28/60>
  13:   89 00                     mov    %eax,(%eax)


  parent reply	other threads:[~2001-05-03  3:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-02  8:07 PROBLEM: 2.4.4 oops, will not boot Gordon Sadler
     [not found] ` <3AEFF4CB.4D2CBE36@uow.edu.au>
2001-05-02 19:43   ` Gordon Sadler
2001-05-03  3:39   ` Gordon Sadler [this message]
     [not found] <3AF0FBF8.F8C6E6E6@uow.edu.au>
2001-05-03  8:38 ` Gordon Sadler
     [not found] <3AF13D85.4D8ADCFB@uow.edu.au>
2001-05-03 17:41 ` Gordon Sadler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010502223912.A7803@debian-home \
    --to=gbsadler1@lcisp.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.