lkml.org 
[lkml]   [2010]   [Jan]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: BUG during shutdown - bisected to commit e2912009
From
On Tue, Jan 5, 2010 at 5:18 AM, Xiaotian Feng <dfeng@redhat.com> wrote:
> This is outputed by sound module, but it will not affect clockevents, could
> you please try following patch and let me know the output before BUG_ON
> happens? We can gather more information on the BUG_ON. Thank you.
>
> diff --git a/kernel/time/clockevents.c b/kernel/time/clockevents.c
> index 6f740d9..7c945e8 100644
> --- a/kernel/time/clockevents.c
> +++ b/kernel/time/clockevents.c
> @@ -260,6 +260,9 @@ void clockevents_notify(unsigned long reason, void *arg)
>                list_for_each_entry_safe(dev, tmp, &clockevent_devices, list)
> {
>                        if (cpumask_test_cpu(cpu, dev->cpumask) &&
>                            cpumask_weight(dev->cpumask) == 1) {
> +                               if (dev->mode != CLOCK_EVT_MODE_UNUSED)
> +                                       printk("invalid dev %s mode %d on
> cpu %d\n", dev->name,
> +                                               dev->mode, cpu);
>                                BUG_ON(dev->mode != CLOCK_EVT_MODE_UNUSED);
>                                list_del(&dev->list);

I don't get anything on screen from the printk - is there a trick
needed to getting printk output at that stage of shutting down? I
tried inserting an mdelay() before the BUG, which delayed the bug
output but still didn't print the invalid dev message.

Thanks,
Marc
--
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/

\
 
 \ /
  Last update: 2010-01-06 00:01    [W:2.346 / U:0.064 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site