All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: david@fortyoz.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [Fwd: [reiserfs-dev] [Fwd: [reiserfs-list] 2.4.3-pre1 oops w/ rsync &  ReiserFS]]
Date: Tue, 20 Mar 2001 18:40:41 +0300	[thread overview]
Message-ID: <3AB779F9.6D7BAA38@namesys.com> (raw)

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

David, did you determine if it was a memory bug?

[-- Attachment #2: Type: message/rfc822, Size: 6022 bytes --]

From: Danilov Nikita <NikitaDanilov@Yahoo.COM>
To: Hans Reiser <reiser@namesys.com>
Subject: Re: [reiserfs-dev] [Fwd: [reiserfs-list] 2.4.3-pre1 oops w/ rsync & ReiserFS]
Date: Tue, 20 Mar 2001 15:18:28 +0300
Message-ID: <15031.19092.764777.859191@beta.namesys.com>

Just to note: stack trace doesn't involve reiserfs at all. Other people
suggested that it may me memory bug.

Nikita.

Hans Reiser writes:
 > Who is taking this one?
 > 
 > HansReturn-Path: <reiserfs-list-return-3481-reiser=namesys.com@namesys.com>
 > Delivered-To: reiser@namesys.com
 > Received: (qmail 30581 invoked by uid 501); 19 Mar 2001 23:27:52 -0000
 > Mailing-List: contact reiserfs-list-help@namesys.com; run by ezmlm
 > Precedence: bulk
 > list-help: <mailto:reiserfs-list-help@namesys.com>
 > list-unsubscribe: <mailto:reiserfs-list-unsubscribe@namesys.com>
 > list-post: <mailto:reiserfs-list@namesys.com>
 > Delivered-To: mailing list reiserfs-list@namesys.com
 > Received: (qmail 30574 invoked from network); 19 Mar 2001 23:27:52 -0000
 > Date: Mon, 19 Mar 2001 15:28:42 -0800
 > From: David Raufeisen <david@fortyoz.org>
 > To: linux-kernel@vger.kernel.org
 > Cc: reiserfs-list@namesys.com
 > Message-ID: <20010319152842.A11014@fortyoz.org>
 > Reply-To: David Raufeisen <david@fortyoz.org>
 > Mime-Version: 1.0
 > Content-Type: text/plain; charset=us-ascii
 > Content-Disposition: inline
 > User-Agent: Mutt/1.3.12i
 > X-Operating-System: Linux 2.2.17 i686
 > Subject: [reiserfs-list] 2.4.3-pre1 oops w/ rsync & ReiserFS
 > X-Mozilla-Status2: 00000000
 > 
 > Getting oops every time I run rsync today.. happens after it receives file list and is starting to stat all the files.. filesystem is reiser.
 > 
 > Linux prototype 2.4.3-pre1 #2 Thu Mar 15 00:24:43 PST 2001 i686 unknown
 > 
 > 15:25:28 up 1 day, 20:05,  4 users,  load average: 0.00, 0.03, 0.00
 > 
 > Linux prototype 2.4.3-pre1 #2 Thu Mar 15 00:24:43 PST 2001 i686 unknown
 >  
 > Gnu C                  2.95.3
 > Gnu make               3.79.1
 > binutils               2.11.90.0.1
 > util-linux             2.11a
 > modutils               2.4.2
 > e2fsprogs              1.19
 > reiserfsprogs          3.x.0b
 > Linux C Library        2.2.2
 > Dynamic linker (ldd)   2.2.2
 > Procps                 2.0.7
 > Net-tools              1.59
 > Kbd                    command
 > Sh-utils               2.0.11
 > Modules Loaded         NVdriver
 > 
 > prototype:~# ksymoops oops.txt    
 > ksymoops 2.3.7 on i686 2.4.3-pre1.  Options used
 >      -V (default)
 >      -k /proc/ksyms (default)
 >      -l /proc/modules (default)
 >      -o /lib/modules/2.4.3-pre1/ (default)
 >      -m /System.map (default)
 > 
 > Warning: You did not tell me where to find symbol information.  I will
 > assume that the log matches the kernel and modules that are running
 > right now and I'll use the default options above for symbol resolution.
 > If the current kernel and/or modules do not match the log, you can get
 > more accurate output by telling me the kernel version and where to find
 > map, modules, ksyms etc.  ksymoops -h explains the options.
 > 
 > Unable to handle kernel paging request at virtual address 4280d8c4
 > c01410c0
 > *pde = 00000000
 > Oops: 0000
 > CPU:    0
 > EIP:    0010:[<c01410c0>]
 > Using defaults from ksymoops -t elf32-i386 -a i386
 > EFLAGS: 00210207
 > eax: c7fdc5e0   ebx: 4280d8ac   ecx: 0000000e   edx: 21cd5a87
 > esi: 00000000   edi: c71424c0   ebp: 4280d8c4   esp: c37b1f04
 > ds: 0018   es: 0018   ss: 0018
 > Process rsync (pid: 16269, stackpage=c37b1000)
 > Stack: c37b1f68 00000000 c71424c0 c37b1fa4 c7fdc5e0 c5919022 21cd5a87 0000000a 
 >        c01392d0 c71424c0 c37b1f68 c37b1f68 c0139a92 c71424c0 c37b1f68 00000000 
 >        c5919000 00000000 c37b1fa4 00000000 c5919000 00000000 c01390da 00000008 
 > Call Trace: [<c01392d0>] [<c0139a92>] [<c01390da>] [<c013a0dc>] [<c0137116>] [<c012f453>] [<c0108e8b>] 
 > Code: 8b 6d 00 8b 54 24 18 39 53 48 75 7c 8b 44 24 24 39 43 0c 75 
 > 
 > >>EIP; c01410c0 <d_lookup+60/100>   <=====
 > Trace; c01392d0 <cached_lookup+10/60>
 > Trace; c0139a92 <path_walk+562/7d0>
 > Trace; c01390da <getname+5a/a0>
 > Trace; c013a0dc <__user_walk+3c/60>
 > Trace; c0137116 <sys_lstat64+16/70>
 > Trace; c012f453 <sys_close+43/60>
 > Trace; c0108e8b <system_call+33/38>
 > Code;  c01410c0 <d_lookup+60/100>
 > 00000000 <_EIP>:
 > Code;  c01410c0 <d_lookup+60/100>   <=====
 >    0:   8b 6d 00                  mov    0x0(%ebp),%ebp   <=====
 > Code;  c01410c3 <d_lookup+63/100>
 >    3:   8b 54 24 18               mov    0x18(%esp,1),%edx
 > Code;  c01410c7 <d_lookup+67/100>
 >    7:   39 53 48                  cmp    %edx,0x48(%ebx)
 > Code;  c01410ca <d_lookup+6a/100>
 >    a:   75 7c                     jne    88 <_EIP+0x88> c0141148 <d_lookup+e8/100>
 > Code;  c01410cc <d_lookup+6c/100>
 >    c:   8b 44 24 24               mov    0x24(%esp,1),%eax
 > Code;  c01410d0 <d_lookup+70/100>
 >   10:   39 43 0c                  cmp    %eax,0xc(%ebx)
 > Code;  c01410d3 <d_lookup+73/100>
 >   13:   75 00                     jne    15 <_EIP+0x15> c01410d5 <d_lookup+75/100>
 > 
 > 
 > 1 warning issued.  Results may not be reliable.
 > 
 > 
 > 
 > -- 
 > David Raufeisen <david@fortyoz.org>
 > Cell: (604) 818-3596
 > 


                 reply	other threads:[~2001-03-20 16:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3AB779F9.6D7BAA38@namesys.com \
    --to=reiser@namesys.com \
    --cc=david@fortyoz.org \
    --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.