2.5.7: acct.c oops

2.5.7: acct.c oops

[Bob_Tracy]

I might have missed this one.  After all, this is a pretty low-traffic
list :-).

Running "accton" (with or without arguments) consistently generates
an oops at linux/kernel/acct.c:169
	BUG_ON(!spin_is_locked(&acct_globals.lock));

I first saw this when shutting down my machine.  The shutdown scripts
run "accton" without any arguments to terminate accounting, regardless
of whether it's running.

2.5.7 kernel on a Dell laptop running a Mandrake distribution.

-- 
-----------------------------------------------------------------------
Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------

Re: 2.5.7: acct.c oops

[Bob Miller]

On Thu, Mar 21, 2002 at 09:50:10AM -0600, Bob_Tracy wrote:
> I might have missed this one.  After all, this is a pretty low-traffic
> list :-).
> 
> Running "accton" (with or without arguments) consistently generates
> an oops at linux/kernel/acct.c:169
> 	BUG_ON(!spin_is_locked(&acct_globals.lock));
> 
> I first saw this when shutting down my machine.  The shutdown scripts
> run "accton" without any arguments to terminate accounting, regardless
> of whether it's running.
> 
> 2.5.7 kernel on a Dell laptop running a Mandrake distribution.
> 
> -- 
> -----------------------------------------------------------------------
> Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
> rct@frus.com
> -----------------------------------------------------------------------
Hi Tracy,

Do you have the rest of the of oops message passed through ksymoops?
I'll also try to reproduce here.  TIA.

-- 
Bob Miller					Email: rem@osdl.org
Open Source Development Lab			Phone: 503.626.2455 Ext. 17

Re: 2.5.7: acct.c oops

[OGAWA Hirofumi]

Bob Miller <rem@osdl.org> writes:

> On Thu, Mar 21, 2002 at 09:50:10AM -0600, Bob_Tracy wrote:
> > I might have missed this one.  After all, this is a pretty low-traffic
> > list :-).
> > 
> > Running "accton" (with or without arguments) consistently generates
> > an oops at linux/kernel/acct.c:169
> > 	BUG_ON(!spin_is_locked(&acct_globals.lock));
> > 
> > I first saw this when shutting down my machine.  The shutdown scripts
> > run "accton" without any arguments to terminate accounting, regardless
> > of whether it's running.
> > 
> > 2.5.7 kernel on a Dell laptop running a Mandrake distribution.
> > 
> > -- 
> > -----------------------------------------------------------------------
> > Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
> > rct@frus.com
> > -----------------------------------------------------------------------
> Hi Tracy,
> 
> Do you have the rest of the of oops message passed through ksymoops?
> I'll also try to reproduce here.  TIA.

Probably, his kernel is not SMP. if so, spin_is_locked() return 0 always.

Regards.
-- 
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>

Re: 2.5.7: acct.c oops

[Bob_Tracy]

Bob Miller wrote:
> On Thu, Mar 21, 2002 at 09:50:10AM -0600, Bob_Tracy wrote:
> > Running "accton" (with or without arguments) consistently generates
> > an oops at linux/kernel/acct.c:169
> > 	BUG_ON(!spin_is_locked(&acct_globals.lock));
> 
> Do you have the rest of the of oops message passed through ksymoops?
> I'll also try to reproduce here.  TIA.

Synopsis: after a fresh boot, ran "accton" with no arguments.  It died
with a segmentation violation, and generated an "oops".

Here's the ksymoops output.  Since this involves the libc acct() function,
you'll probably be interested in the C library version as well: 2.2.3.
Compiler is "gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)".

====--CUT HERE--====
ksymoops 2.4.5 on i586 2.5.7.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.5.7/ (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.

No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
kernel BUG at acct.c:169!
invalid operand: 0000
CPU:    0
EIP:    0010:[acct_file_reopen+8/224]    Not tainted
EFLAGS: 00010246
eax: d644d200   ebx: 00000000   ecx: 00000001   edx: 00000000
esi: 00000000   edi: d2d1e000   ebp: bffffa2c   esp: d2d1ffa4
ds: 0018   es: 0018   ss: 0018
Stack: d2d1e000 00000000 c011cd89 00000000 d2d1e000 00000001 00000000 c0107007 
       00000000 00000001 bffffa94 00000001 00000000 bffffa2c 00000033 0000002b 
       0000002b 00000033 400e4e6d 00000023 00000246 bffffa14 0000002b 
Call Trace: [sys_acct+197/232] [syscall_call+7/11] 
Code: 0f 0b a9 00 ff dd 22 c0 a1 2c cb 2c c0 85 c0 74 2f 89 c6 68 
Using defaults from ksymoops -t elf32-i386 -a i386


>>eax; d644d200 <END_OF_CODE+16150ed4/????>
>>edi; d2d1e000 <END_OF_CODE+12a21cd4/????>
>>ebp; bffffa2c Before first symbol
>>esp; d2d1ffa4 <END_OF_CODE+12a23c78/????>

Code;  00000000 Before first symbol
0000000000000000 <_EIP>:
Code;  00000000 Before first symbol
   0:   0f 0b                     ud2a   
Code;  00000002 Before first symbol
   2:   a9 00 ff dd 22            test   $0x22ddff00,%eax
Code;  00000007 Before first symbol
   7:   c0 a1 2c cb 2c c0 85      shlb   $0x85,0xc02ccb2c(%ecx)
Code;  0000000e Before first symbol
   e:   c0                        (bad)  
Code;  0000000f Before first symbol
   f:   74 2f                     je     40 <_EIP+0x40> 00000040 Before first symbol
Code;  00000011 Before first symbol
  11:   89 c6                     mov    %eax,%esi
Code;  00000013 Before first symbol
  13:   68 00 00 00 00            push   $0x0


2 warnings issued.  Results may not be reliable.
====--TUC EREH--====

-- 
-----------------------------------------------------------------------
Bob Tracy                   WTO + WIPO = DMCA? http://www.anti-dmca.org
rct@frus.com
-----------------------------------------------------------------------