Tejun Heo wrote: > Please test this one instead. Thanks. Yup, the second patch fixes it. -Berck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
- From: "Berck E. Nash" <flyboy@gmail.com>
- Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
- From: Andrew Morton <akpm@linux-foundation.org>
- Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
- From: Tejun Heo <htejun@gmail.com>
- Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
- From: Tejun Heo <htejun@gmail.com>
- Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
- From: Tejun Heo <htejun@gmail.com>
- 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
- Prev by Date: Re: Fw: [PATCH -mm] workqueue: debug possible endless loop in cancel_rearming_delayed_work
- Next by Date: Removing VM_LOCKED from user memory
- Previous by thread: Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
- Next by thread: Re: 2.6.21-rc7-mm1 BUG at kernel/sched-clock.c:175 init_sched_clock()
- Index(es):
 |