linux-kernel - Re: BUG during shutdown - bisected to commit e2912009

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 5 Jan 2010 17:58:30 -0500
From:	Marc Dionne <marc.c.dionne@...il.com>
To:	Xiaotian Feng <dfeng@...hat.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: BUG during shutdown - bisected to commit e2912009

On Tue, Jan 5, 2010 at 5:18 AM, Xiaotian Feng <dfeng@...hat.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/