devfs
[Top] [All Lists]

Fwd: Bug#145718: devfsd: invalid operand: 0000

To: devfs@xxxxxxxxxxx
Subject: Fwd: Bug#145718: devfsd: invalid operand: 0000
From: Russell Coker <russell@xxxxxxxxxxxx>
Date: Sat, 4 May 2002 09:07:53 +1000
Reply-to: Russell Coker <russell@xxxxxxxxxxxx>
Sender: owner-devfs@xxxxxxxxxxx

----------  Forwarded Message  ----------

Subject: Bug#145718: devfsd: invalid operand: 0000
Date: Fri, 3 May 2002 14:41:19 -0400
From: Matt Zimmerman <mdz@xxxxxxxxxx>
To: Debian Bug Tracking System <submit@xxxxxxxxxxxxxxx>

Package: devfsd
Version: 1.3.25-6
Severity: normal

I have a system which periodically issues this error, killing devfsd:

invalid operand: 0000
CPU:    1
EIP:    0010:[<c0147871>]    Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 5a5a5a00   ebx: d907aaa0   ecx: c34d3260   edx: d907aad0
esi: c34d3260   edi: f724b620   ebp: d907aaa0   esp: cf6a7f18
ds: 0018   es: 0018   ss: 0018
Process devfsd (pid: 22189, stackpage=cf6a7000)
Stack: f705f9e0 c015e67e d907aaa0 c34d3260 d907aaa0 00000000 cf6a7fa4
 f724d940 c013ea2e d907aaa0 00000000 cf6a7f74 c013f1f1 f724d940 cf6a7f74
 00000000 e91dc000 00000000 cf6a7fa4 00000009 00000009 e91dc005 00000000
 e91dc004 Call Trace: [<c015e67e>] [<c013ea2e>] [<c013f1f1>] [<c013f46a>]
 [<c013f8e1>] [<c013c51d>] [<c0106f7b>]
Code: 0f 0b f0 fe 0d a0 46 26 c0 0f 88 ed 8b 09 00 85 c9 74 12 8b

>>EIP; c0147871 <d_instantiate+11/44>   <=====
>>
>>eax; 5a5a5a00 Before first symbol
>>ebx; d907aaa0 <_end+18db8114/3854a674>
>>ecx; c34d3260 <_end+32108d4/3854a674>
>>edx; d907aad0 <_end+18db8144/3854a674>
>>esi; c34d3260 <_end+32108d4/3854a674>
>>edi; f724b620 <_end+36f88c94/3854a674>
>>ebp; d907aaa0 <_end+18db8114/3854a674>
>>esp; cf6a7f18 <_end+f3e558c/3854a674>

Trace; c015e67e <devfs_d_revalidate_wait+8e/b8>
Trace; c013ea2e <cached_lookup+2e/54>
Trace; c013f1f1 <link_path_walk+581/7e0>
Trace; c013f46a <path_walk+1a/1c>
Trace; c013f8e1 <__user_walk+35/50>
Trace; c013c51d <sys_stat64+19/70>
Trace; c0106f7b <system_call+33/38>

Code;  c0147871 <d_instantiate+11/44>
00000000 <_EIP>:
Code;  c0147871 <d_instantiate+11/44>   <=====
   0:   0f 0b                     ud2a      <=====
Code;  c0147873 <d_instantiate+13/44>
   2:   f0 fe 0d a0 46 26 c0      lock decb 0xc02646a0
Code;  c014787a <d_instantiate+1a/44>
   9:   0f 88 ed 8b 09 00         js     98bfc <_EIP+0x98bfc> c01e046d
 <stext_lock+2e55/719a> Code;  c0147880 <d_instantiate+20/44>
   f:   85 c9                     test   %ecx,%ecx
Code;  c0147882 <d_instantiate+22/44>
  11:   74 12                     je     25 <_EIP+0x25> c0147896
 <d_instantiate+36/44> Code;  c0147884 <d_instantiate+24/44>
  13:   8b 00                     mov    (%eax),%eax

Details vary, of course, but the stack trace is pretty much the same always.
The system is running a custom 2.4.17 kernel, the only substantial
differences from the stock 686-smp kernel are CONFIG_HIGHMEM4G=y and
CONFIG_MPENTIUMIII=y.

I am about to upgrade to a similar 2.4.18 kernel, and will report as to
whether I see this happen again (could take a few days).

--
 - mdz

-------------------------------------------------------

-- 
If you send email to me or to a mailing list that I use which has >4 lines
of legalistic junk at the end then you are specifically authorizing me to do
whatever I wish with the message and all other messages from your domain, by
posting the message you agree that your long legalistic sig is void.

<Prev in Thread] Current Thread [Next in Thread>