public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Leete <tleete@mountain.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [OOPS] testing/prerelease of 01/03 on startup
Date: Thu, 04 Jan 2001 04:08:30 -0500	[thread overview]
Message-ID: <3A543D8E.9489F715@mountain.net> (raw)

Hello,

kernel is 2.4.0-prerelease with testing/prerelease patch of Jan. 3, i486.
Oops is repeatable.

I caught this one on serial console just as init begins:

$ ksymoops -K -L -O -v /boot/vmlinux-2.4.0-prerelease -m
/boot/System.map-2.4.0-prerelease tleete.prerelease.oops
ksymoops 2.3.5 on i486 2.4.0-test13-pre4.  Options used
     -v /boot/vmlinux-2.4.0-prerelease (specified)
     -K (specified)
     -L (specified)
     -O (specified)
     -m /boot/System.map-2.4.0-prerelease (specified)

Unable to handle kernel paging request at virtual address 08048004
c011240a
*pde = 01151067
Oops: 0003
CPU:    0
EIP:    0010:[<c011240a>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 08048000   ebx: c1169120   ecx: c11690ac   edx: c1169090
esi: c1169090   edi: c1169154   ebp: 00000000   esp: c11dbf28
ds: 0018   es: 0018   ss: 0018
Process init (pid: 1, stackpage=c11db000)
Stack: c3758000 c116a534 c116aa44 c02210c0 c1167550 c11da000 c11690c4
c1169154
       c11690ac c11da000 c116755c c1169090 c0112c52 00000011 c3758000
c11da000
       bffffa18 bffff998 c11dbfbc 00000000 c11dbf94 fffffff4 00000000
00000000
Call Trace: [<c0112c52>] [<c0107804>] [<c0108e63>] [<c0100023>]
Code: 89 78 04 89 43 34 8b 44 24 18 89 47 04 89 7e 34 85 ed 75 22

>>EIP; c011240a <copy_mm+27a/2d0>   <=====
Trace; c0112c52 <do_fork+472/6c0>
Trace; c0107804 <sys_fork+14/20>
Trace; c0108e63 <system_call+33/40>
Trace; c0100023 <startup_32+23/139>
Code;  c011240a <copy_mm+27a/2d0>
00000000 <_EIP>:
Code;  c011240a <copy_mm+27a/2d0>   <=====
   0:   89 78 04                  mov    %edi,0x4(%eax)   <=====
Code;  c011240d <copy_mm+27d/2d0>
   3:   89 43 34                  mov    %eax,0x34(%ebx)
Code;  c0112410 <copy_mm+280/2d0>
   6:   8b 44 24 18               mov    0x18(%esp,1),%eax
Code;  c0112414 <copy_mm+284/2d0>
   a:   89 47 04                  mov    %eax,0x4(%edi)
Code;  c0112417 <copy_mm+287/2d0>
   d:   89 7e 34                  mov    %edi,0x34(%esi)
Code;  c011241a <copy_mm+28a/2d0>
  10:   85 ed                     test   %ebp,%ebp
Code;  c011241c <copy_mm+28c/2d0>
  12:   75 22                     jne    36 <_EIP+0x36> c0112440
<copy_mm+2b0/2d0>

Kernel panic: Attempted to kill init!
$

Everything is looged on the serial console machine, so if you need more,
it's here.

Hope this helps,
Tom
-
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/

             reply	other threads:[~2001-01-04  9:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04  9:08 Tom Leete [this message]
2001-01-04  9:31 ` [OOPS] testing/prerelease of 01/03 on startup Linus Torvalds
2001-01-04 11:08   ` Tom Leete

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=3A543D8E.9489F715@mountain.net \
    --to=tleete@mountain.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox