public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Miquel van Smoorenburg <miquels@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.46: kernel BUG at kernel/timer.c:333!
Date: Sat, 09 Nov 2002 10:51:03 -0800	[thread overview]
Message-ID: <3DCD5917.FEEA7C5D@digeo.com> (raw)
In-Reply-To: aqj8bf$ff2$1@ncc1701.cistron.net

Miquel van Smoorenburg wrote:
> 
> I can reliably crash 2.5.X on one of our newsservers (dual PIII/450, GigE,
> lots of disk- and network I/O).
> 
> The last crash I posted here was a bit garbled. So I tried again,
> this one is clean. Crash appears to be timer related ?
> 
> kernel BUG at kernel/timer.c:333!

There are timer fixes in Linus's current tree.  The problem which
they address could cause this BUG.

>..
> Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
> Call Trace:
>  [<c0117be8>] __might_sleep+0x54/0x58
>  [<c013578c>] set_shrinker+0x3c/0x7c
>  [<c01686b4>] mb_cache_create+0x1c4/0x244
>  [<c0168380>] mb_cache_shrink_fn+0x0/0x170
>  [<c01050ab>] init+0x47/0x1ac
>  [<c0105064>] init+0x0/0x1ac
>  [<c0106e8d>] kernel_thread_helper+0x5/0xc

That's different.  A fix for this is in Linus's tree.

So..  Please grab an update from
ftp://ftp.kernel.org/pub/linux/kernel/v2.5/snapshots/
or retest 2.5.47.

  reply	other threads:[~2002-11-09 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-09 15:07 2.5.46: kernel BUG at kernel/timer.c:333! Miquel van Smoorenburg
2002-11-09 18:51 ` Andrew Morton [this message]
2002-11-10 14:32   ` Miquel van Smoorenburg
2002-11-10 17:13     ` Andrew Morton
2002-11-11 10:57       ` Miquel van Smoorenburg
2002-11-11 18:13         ` Andrew Morton

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=3DCD5917.FEEA7C5D@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miquels@cistron.nl \
    /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