Re: 3.0.3 kernel BUG at kernel/timer.c:1035

[Frank van Maarseveen]

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@xxxxxxxxxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/