public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "jeev" <naptime@cervnet.com>
To: <linux-kernel@vger.kernel.org>
Cc: "'Dan Chen'" <crimsun@email.unc.edu>, <akpm@zip.com.au>
Subject: RE: Linux 2.4.17 problem.
Date: Sat, 19 Jan 2002 23:25:16 -0800	[thread overview]
Message-ID: <002401c1a183$9c7cd920$0200a8c0@mainframe> (raw)
In-Reply-To: <20020120062620.GA25787@opeth.ath.cx>

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

The box is back up, someone rebooted for me from the location.

Unable to handle kernel paging request at virtual address 00400000
c012fce4
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<c012fce4>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000   ebx: ea0c71c0   ecx: ea0c71c0   edx: 00400000
esi: 00000002   edi: ea0c71c0   ebp: 00000000   esp: e6fe5eb8
ds: 0018   es: 0018   ss: 0018
Process rm (pid: 247, stackpage=e6fe5000)
Stack: c012fd0a ea0c71c0 c01308e8 ea0c71c0 ea0c71c0 00001000 c0130988
ea0c71c0 
       c1a83140 00000000 00000000 eedb16f0 c0122509 c1a83140 00000000
00000001 
       c0122523 c1a83140 00000000 c1a83140 c0122666 c1a83140 00000000
e6fe5f44 
Call Trace: [<c012fd0a>] [<c01308e8>] [<c0130988>] [<c0122509>]
[<c0122523>] 
   [<c0122666>] [<c0122711>] [<c01407cc>] [<c013eeac>] [<c01388fc>]
[<c01389d8>] 
   [<c0106e6b>] 
Code: 89 02 c7 41 30 00 00 00 00 51 e8 7d ff ff ff 83 c4 04 c3 89
Error (pclose_local): Oops_decode pclose failed 0xb
Error (Oops_decode): no objdump lines read for /tmp/ksymoops.rlyEvb

>>EIP; c012fce4 <__remove_from_queues+14/30>   <=====
Trace; c012fd0a <remove_from_queues+a/10>
Trace; c01308e8 <discard_buffer+68/80>
Trace; c0130988 <discard_bh_page+38/70>
Trace; c0122508 <do_flushpage+28/30>
Trace; c0122522 <truncate_complete_page+12/50>
Trace; c0122666 <truncate_list_pages+106/170>
Trace; c0122710 <truncate_inode_pages+40/70>
Trace; c01407cc <iput+9c/1d0>
Trace; c013eeac <d_delete+4c/70>
Trace; c01388fc <vfs_unlink+12c/160>
Trace; c01389d8 <sys_unlink+a8/120>
Trace; c0106e6a <system_call+32/38>

Unable to handle kernel paging request at virtual address 0a073344
c013073c
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<c013073c>]    Not tainted
EFLAGS: 00010202
eax: 0a073340   ebx: 00000000   ecx: ea073000   edx: 0a073340
esi: 00000000   edi: 00001000   ebp: 00000001   esp: dd375ea4
ds: 0018   es: 0018   ss: 0018
Process lmdd (pid: 1396, stackpage=dd375000)
Stack: c01307bd 00000001 c1a4adc0 00000301 000011fa c1dc3dc4 c01309d7
c1a4adc0 
       00001000 00000001 00000000 dd375f0c c0130bcb c1a4adc0 00000301
00001000 
       00000000 c1a4adc0 000011fa c1dc3dc4 e92b7000 c0130479 00001000
c01304c6 
Call Trace: [<c01307bd>] [<c01309d7>] [<c0130bcb>] [<c0130479>]
[<c01304c6>] 
   [<c0131222>] [<c0150ce0>] [<c01510b9>] [<c0150ce0>] [<c012542b>]
[<c012eb16>] 
   [<c0106e6b>] 
Code: c7 42 04 ff ff ff ff c7 42 28 00 00 00 00 c3 90 8d 74 26 00 
Error (pclose_local): Oops_decode pclose failed 0xb
Error (Oops_decode): no objdump lines read for /tmp/ksymoops.EItk8d

>>EIP; c013073c <get_unused_buffer_head+3c/80>   <=====
Trace; c01307bc <create_buffers+1c/e0>
Trace; c01309d6 <create_empty_buffers+16/50>
Trace; c0130bca <__block_prepare_write+4a/200>
Trace; c0130478 <balance_dirty_state+18/60>
Trace; c01304c6 <balance_dirty+6/30>
Trace; c0131222 <block_prepare_write+22/40>
Trace; c0150ce0 <ext2_get_block+0/380>
Trace; c01510b8 <ext2_prepare_write+18/20>
Trace; c0150ce0 <ext2_get_block+0/380>
Trace; c012542a <generic_file_write+45a/660>
Trace; c012eb16 <sys_write+96/d0>
Trace; c0106e6a <system_call+32/38>

 <1>Unable to handle kernel paging request at virtual address 2e86369c
c013eb66
*pde = 00000000
Oops: 0002
CPU:    0
EIP:    0010:[<c013eb66>]    Not tainted
EFLAGS: 00010202
eax: 00000003   ebx: 2e863640   ecx: 00000000   edx: dd6bdf74
esi: ef8ac009   edi: 2e86369c   ebp: ef72e9c0   esp: dd6bdf14
ds: 0018   es: 0018   ss: 0018
Process bash (pid: 466, stackpage=dd6bd000)
Stack: 00000000 eeec7780 eeec77e8 ef72e9c0 2e86369c c0136d58 ef72e9c0
dd6bdf74 
       dd6bdf74 00000000 dd6bdfa4 eeec7780 c013738e ef72e9c0 dd6bdf74
00000000 
       ef8ac000 00000000 dd6bdfa4 00000009 c0136acd 00000009 ef8ac00c
00000000 
Call Trace: [<c0136d58>] [<c013738e>] [<c0136acd>] [<c01375ca>]
[<c0137955>] 
   [<c0134bf9>] [<c0106e6b>] 
Code: 66 a5 a8 01 74 01 a4 eb 10 90 50 56 8b 44 24 18 50 e8 84 30
Error (pclose_local): Oops_decode pclose failed 0xb
Error (Oops_decode): no objdump lines read for /tmp/ksymoops.9ibQXh

>>EIP; c013eb66 <d_alloc+96/180>   <=====
Trace; c0136d58 <real_lookup+38/c0>
Trace; c013738e <link_path_walk+4be/6e0>
Trace; c0136acc <getname+5c/a0>
Trace; c01375ca <path_walk+1a/20>
Trace; c0137954 <__user_walk+34/50>
Trace; c0134bf8 <sys_stat64+18/70>
Trace; c0106e6a <system_call+32/38>


38 warnings and 8 errors issued.  Results may not be reliable.

j

> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> owner@vger.kernel.org] On Behalf Of Dan Chen
> Sent: Saturday, January 19, 2002 10:26 PM
> To: jeev
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: Linux 2.4.17 problem.
> 
> Would you run those through ksymoops and repost?
> 
> On Sat, Jan 19, 2002 at 09:24:56PM -0800, jeev wrote:
> > Hi, im running slackware with the kernel 2.4.17, when I tar -zxvf a
big
> > file, ie. hlds_l_3108_full.tar.gz.
> >
> > It cuts off saying format violated..
> > This is an amd 1.4ghz with 768 mbram 41gb 7200rpm harddrive (brand
new
> > stuff)
> 
> --
> Dan Chen                 crimsun@email.unc.edu
> GPG key:   www.unc.edu/~crimsun/pubkey.gpg.asc

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3224 bytes --]

  parent reply	other threads:[~2002-01-20  7:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-20  5:24 Linux 2.4.17 problem jeev
2002-01-20  6:26 ` Dan Chen
2002-01-20  6:31   ` jeev
2002-01-20  7:25   ` jeev [this message]
2002-01-20  8:08   ` jeev

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='002401c1a183$9c7cd920$0200a8c0@mainframe' \
    --to=naptime@cervnet.com \
    --cc=akpm@zip.com.au \
    --cc=crimsun@email.unc.edu \
    --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