public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: Lin Ming <mlin@ss.pku.edu.cn>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Lin Ming <ming.m.lin@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Jens Axboe <axboe@kernel.dk>
Subject: Re: 3.0.3 kernel BUG at kernel/timer.c:1035
Date: Sat, 10 Sep 2011 10:41:23 +0200	[thread overview]
Message-ID: <20110910084123.GA23171@janus> (raw)
In-Reply-To: <CAF1ivSbWFahCM79uBD24yA2+KwRV=RC-n=E8ev4nLCUyFVeaEQ@mail.gmail.com>

On Fri, Sep 09, 2011 at 10:21:36PM +0800, Lin Ming wrote:
> On Thu, Sep 8, 2011 at 5:30 AM, Andrew Morton <akpm@linux-foundation.org> wrote:

(...)

> >
> > Probably this will "fix" it:
> 
> Frank,
> 
> Does Andrew's patch help?
> 
> Lin Ming
> 
> >
> > --- a/block/blk-sysfs.c~a
> > +++ a/block/blk-sysfs.c
> > @@ -4,6 +4,7 @@
> >  #include <linux/kernel.h>
> >  #include <linux/slab.h>
> >  #include <linux/module.h>
> > +#include <linux/timer.h>
> >  #include <linux/bio.h>
> >  #include <linux/blkdev.h>
> >  #include <linux/blktrace_api.h>
> > @@ -486,7 +487,7 @@ static void blk_release_queue(struct kob
> >                __blk_queue_free_tags(q);
> >
> >        blk_trace_shutdown(q);
> > -
> > +       del_timer_sync(&q->backing_dev_info.wb.wakeup_timer);
> >        bdi_destroy(&q->backing_dev_info);
> >        kmem_cache_free(blk_requestq_cachep, q);
> >  }
> > _
> >

I have no physical access to the machines showing the issue for a day
or 10 and it appears to be not very reproducable on my own machines:
I got only one trace so far (with a pristine 3.0.4 tree). I try to make
it more reproducable before trying out the above patch. So, it will take
some time before I have conclusive information on this.

-- 
Frank

  reply	other threads:[~2011-09-10  8:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 13:02 3.0.3 kernel BUG at kernel/timer.c:1035 Frank van Maarseveen
2011-08-30  9:08 ` Frank van Maarseveen
2011-09-02  8:10 ` Andrew Morton
2011-09-05 12:38   ` Frank van Maarseveen
     [not found]     ` <CAF1ivSYui_=tHbxHiy15a9wfiphHcpoY+J1MmAJ=dMQsAfEVLw@mail.gmail.com>
2011-09-06 14:48       ` Lin Ming
2011-09-07 10:24         ` Frank van Maarseveen
2011-09-07 12:36           ` Lin Ming
2011-09-07 21:30             ` Andrew Morton
2011-09-09 14:21               ` Lin Ming
2011-09-10  8:41                 ` Frank van Maarseveen [this message]
2011-09-20 13:16               ` Frank van Maarseveen

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=20110910084123.GA23171@janus \
    --to=frankvm@frankvm.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=mlin@ss.pku.edu.cn \
    /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