public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Shepard <daveman@bellatlantic.net>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at inode.c:1034!
Date: Tue, 05 Nov 2002 14:14:05 -0500	[thread overview]
Message-ID: <3DC8187D.4090907@bellatlantic.net> (raw)
In-Reply-To: 20021105043628.GY23425@holomorphy.com

William Lee Irwin III wrote:

>On Mon, Nov 04, 2002 at 11:33:42PM -0500, David Shepard wrote:
>  
>
>>I am running kernel 2.4.19 plain and have been doing so successfully for 
>>quite some time. In the past few days, I am seeing a repeatable BUG on 
>>reboot/shutdown. Please let me know if there is any more information I 
>>can provide.
>>    
>>
>
>Please decode this oops.
>
>
>Bill
>
>  
>
Not sure why the warning...

ksymoops 2.4.7 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 /usr/src/linux/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.

kernel BUG at inode.c:1034!
invalid operand: 0000
CPU:    0
EIP:    0010:[<c0156d33>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: c56db150   ebx: c56db040   ecx: c56db150   edx: c56db040
esi: 00000000   edi: c7f42e00   ebp: c910a620   esp: c47f3f00
ds: 0018   es: 0018   ss:0018
Process umount (pid: 7961, stackpage=c47f3000
Stack: c11660c0 c56db040 00000296 c47f3f48 00000296 c11660c0 c56d6740 
c56d6740
Stack: c0157ea4 c11660c0 c56d6740 00000001 c7f42e60 00000001 c01573ad 
c7f42e00
Stack: c7f42ec4 c7f42e34 c910a620 c910468d c56db040 c7f42e00 c7f42e40 
c0143207
Call Trace:    [<c0157ea4>] [<c01573ad>] [<c910a620>] [<c910468d>] 
[<c0143207>]
  [<c015ad05>] [<c015add1>] [<c015ae67>] [<c01074a3>]
Code: 0f 0b 0a 04 9d bb 27 c0 e9 48 fa ff ff 55 57 56 53 83 ec 14


 >>EIP; c0156d33 <iput+5d3/5e0>   <=====

 >>eax; c56db150 <_end+53b03f8/8dc0308>
 >>ebx; c56db040 <_end+53b02e8/8dc0308>
 >>ecx; c56db150 <_end+53b03f8/8dc0308>
 >>edx; c56db040 <_end+53b02e8/8dc0308>
 >>edi; c7f42e00 <_end+7c180a8/8dc0308>
 >>ebp; c910a620 <[usbcore]usbdevfs_sops+0/44>
 >>esp; c47f3f00 <_end+44c91a8/8dc0308>

Trace; c0157ea4 <dispose_list+54/90>
Trace; c01573ad <invalidate_inodes+7d/90>
Trace; c910a620 <[usbcore]usbdevfs_sops+0/44>
Trace; c910468d <[usbcore]usbdevfs_put_super+4d/60>
Trace; c0143207 <kill_super+167/190>
Trace; c015ad05 <__mntput+35/60>
Trace; c015add1 <sys_umount+81/100>
Trace; c015ae67 <sys_oldumount+17/20>
Trace; c01074a3 <system_call+33/38>

Code;  c0156d33 <iput+5d3/5e0>
00000000 <_EIP>:
Code;  c0156d33 <iput+5d3/5e0>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c0156d35 <iput+5d5/5e0>
   2:   0a 04 9d bb 27 c0 e9      or     0xe9c027bb(,%ebx,4),%al
Code;  c0156d3c <iput+5dc/5e0>
   9:   48                        dec    %eax
Code;  c0156d3d <iput+5dd/5e0>
   a:   fa                        cli
Code;  c0156d3e <iput+5de/5e0>
   b:   ff                        (bad)
Code;  c0156d3f <iput+5df/5e0>
   c:   ff 55 57                  call   *0x57(%ebp)
Code;  c0156d42 <remove_dquot_ref+2/1a0>
   f:   56                        push   %esi
Code;  c0156d43 <remove_dquot_ref+3/1a0>
  10:   53                        push   %ebx
Code;  c0156d44 <remove_dquot_ref+4/1a0>
  11:   83 ec 14                  sub    $0x14,%esp


1 warning issued.  Results may not be reliable.


  reply	other threads:[~2002-11-05 19:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05  4:33 kernel BUG at inode.c:1034! David Shepard
2002-11-05  4:36 ` William Lee Irwin III
2002-11-05 19:14   ` David Shepard [this message]
2002-11-06  2:43     ` David Shepard
2002-11-05 16:05 ` David Liana
  -- strict thread matches above, loose matches on Subject: below --
2002-11-06 10:57 Wolfram Gloger

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=3DC8187D.4090907@bellatlantic.net \
    --to=daveman@bellatlantic.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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