public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: Bob Miller <rem@osdl.org>
Cc: Bob_Tracy <rct@gherkin.frus.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.7: acct.c oops
Date: Fri, 22 Mar 2002 02:59:31 +0900	[thread overview]
Message-ID: <87lmclyf7g.fsf@devron.myhome.or.jp> (raw)
In-Reply-To: <m16o4pO-0005khC@gherkin.frus.com> <20020321092526.A11399@doc.pdx.osdl.net>

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>

  reply	other threads:[~2002-03-21 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-21 15:50 2.5.7: acct.c oops Bob_Tracy
2002-03-21 17:25 ` Bob Miller
2002-03-21 17:59   ` OGAWA Hirofumi [this message]
2002-03-21 21:50   ` Bob_Tracy

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=87lmclyf7g.fsf@devron.myhome.or.jp \
    --to=hirofumi@mail.parknet.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rct@gherkin.frus.com \
    --cc=rem@osdl.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