public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Illich <michal@illich.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 crash
Date: Wed, 07 Aug 2002 21:50:49 +0200	[thread overview]
Message-ID: <3D517A19.2060608@illich.cz> (raw)

output from ksymoops:

-------------------------------------------
ksymoops 2.4.4 on i686 2.4.19.  Options used
      -V (default)
      -k /proc/ksyms (default)
      -l /proc/modules (default)
      -o /lib/modules/2.4.19/ (default)
      -m /boot/System.map-2.4.19 (default)

Warning: You did not tell me where to find symbol information. [...]

No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Aug  7 09:47:16 [...] kernel: Unable to handle kernel paging request at 
virtual address 45ca6234
Aug  7 09:47:16 [...] kernel: c0128c80
Aug  7 09:47:16 [...] kernel: *pde = 00000000
Aug  7 09:47:16 [...] kernel: Oops: 0000
Aug  7 09:47:16 [...] kernel: CPU:    0
Aug  7 09:47:16 [...] kernel: EIP:    0010:[<c0128c80>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
Aug  7 09:47:16 [...] kernel: EFLAGS: 00010813
Aug  7 09:47:16 [...] kernel: eax: 999f7887   ebx: c2217e50   ecx: df4c8000 
   edx: f762e680
Aug  7 09:47:16 [...] kernel: esi: 00000246   edi: cfbc4380   ebp: 000000f0 
   esp: ddff7de8
Aug  7 09:47:16 [...] kernel: ds: 0018   es: 0018   ss: 0018
Aug  7 09:47:16 [...] kernel: Process [...] (pid: 2133, stackpage=ddff7000)
Aug  7 09:47:16 [...] kernel: Stack: 00000000 ecb0109c 009bb6d0 e55216c0 
00000000 00000000 00001000 00000001
Aug  7 09:47:16 [...] kernel:        c0132804 c2217e50 000000f0 c01328b6 
00000001 df4c8940 04a87241 00000000
Aug  7 09:47:16 [...] kernel:        0000a324 c212b320 00000341 0000a325 
c212b320 c0132ae6 c212b320 00001000
Aug  7 09:47:16 [...] kernel: Call Trace:    [<c0132804>] [<c01328b6>] 
[<c0132ae6>] [<c0133158>] [<c01239ad>]
Aug  7 09:47:16 [...] kernel:   [<c0123a47>] [<c01534f0>] [<c0124035>] 
[<c0124288>] [<c0126408>] [<c01247fa>]
Warning (Oops_read): Code line not seen, dumping what data is available

 >>EIP; c0128c80 <kfree+30/a0>   <=====
Trace; c0132804 <block_read_full_page+c4/230>
Trace; c01328b6 <block_read_full_page+176/230>
Trace; c0132ae6 <cont_prepare_write+86/240>
Trace; c0133158 <generic_direct_IO+48/160>
Trace; c01239ad <___wait_on_page+2d/b0>
Trace; c0123a47 <unlock_page+17/70>
Trace; c01534f0 <ext3_block_truncate_page+100/360>
Trace; c0124035 <do_generic_file_read+b5/420>
Trace; c0124288 <do_generic_file_read+308/420>
Trace; c0126408 <remove_suid+58/59>
Trace; c01247fa <sys_sendfile+1a/200>

3 warnings issued.  Results may not be reliable.
-----------------------------------------------

both lsmod and ksyms produce no output, I think this is ok in case of lsmod, 
because everything is compiled in. I don't know if it is ok with ksyms; if 
you need it I can play little more with that...

[...] are my edits


             reply	other threads:[~2002-08-07 19:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07 19:50 Michal Illich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-09 10:02 2.4.19 crash Michal Illich
2002-08-09 12:01 ` Alan Cox
2002-08-09 12:13   ` Michal Illich
2002-08-07 18:17 Michal Illich
2002-08-07 22:04 ` Alan Cox

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=3D517A19.2060608@illich.cz \
    --to=michal@illich.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox