public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: yun wang <wangyun@linux.vnet.ibm.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 3.11.0-rc4 (Linus GIT) -- WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185 can_stop_full_tick+0x7e/0x89()
Date: Tue, 06 Aug 2013 13:34:39 +0800	[thread overview]
Message-ID: <52008AEF.2050601@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAHFgRy8V7Zp=CRipj+zVq2O+exxnpMuN0BdKwZXmJ1BeReQFYA@mail.gmail.com>

Hi, Miles

On 08/06/2013 12:30 PM, Miles Lane wrote:
> I am not seeing any problems in the behavior of the computer, but
> wonder if this indicates something that needs fixing.
>
> [    1.969109] WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185
> can_stop_full_tick+0x7e/0x89()

According to the comments:

                 /*
                  * Don't allow the user to think they can get
                  * full NO_HZ with this machine.
                  */

I guess this WARN is just supposed to notify user that two feature are 
conflict.

I'm not sure whether this is the right way, may be declaim while making 
config will be better, but consider that nohz could also be enabled by 
boot option, may be this is a good way...

Regards,
Michael Wang


> [    1.969121] NO_HZ FULL will not work with unstable sched clock
> [    1.969129] Modules linked in:
> [    1.969142] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.11.0-rc4 #150
> [    1.969152] Hardware name: ASUSTeK Computer Inc.         UL50VT
>           /UL50VT    , BIOS 217     03/01/2010
> [    1.969166]  0000000000000000 ffff88013f303eb0 ffffffff8138347b
> ffff88013f303ef8
> [    1.969183]  ffff88013f303ee8 ffffffff8103454f ffffffff81079bbf
> ffff88013f30d7b0
> [    1.969199]  0000000000000001 ffff88013a801dc0 ffff88013a802240
> ffff88013f303f48
> [    1.969216] Call Trace:
> [    1.969222]  <IRQ>  [<ffffffff8138347b>] dump_stack+0x4e/0x82
> [    1.969241]  [<ffffffff8103454f>] warn_slowpath_common+0x75/0x8e
> [    1.969253]  [<ffffffff81079bbf>] ? can_stop_full_tick+0x7e/0x89
> [    1.969265]  [<ffffffff810345af>] warn_slowpath_fmt+0x47/0x49
> [    1.969278]  [<ffffffff81079bbf>] can_stop_full_tick+0x7e/0x89
> [    1.969290]  [<ffffffff8107a046>] tick_nohz_irq_exit+0x63/0x7f
> [    1.969302]  [<ffffffff810384ec>] irq_exit+0xa4/0xac
> [    1.969314]  [<ffffffff810239e8>] smp_apic_timer_interrupt+0x30/0x3c
> [    1.969327]  [<ffffffff8138ef6f>] apic_timer_interrupt+0x6f/0x80
> [    1.969336]  <EOI>  [<ffffffff8100c676>] ? save_stack_trace+0x26/0x41
> [    1.969355]  [<ffffffff813893cd>] ? _raw_spin_unlock_irqrestore+0x3c/0x69
> [    1.969369]  [<ffffffff813810fb>] __slab_free+0x53/0x317
> [    1.969382]  [<ffffffff811f08c6>] ? debug_check_no_obj_freed+0x103/0x153
> [    1.969397]  [<ffffffff810eb271>] kfree+0x102/0x111
> [    1.969410]  [<ffffffff81237171>] ? acpi_ns_get_node+0xb6/0xc6
> [    1.969422]  [<ffffffff81237171>] acpi_ns_get_node+0xb6/0xc6
> [    1.969434]  [<ffffffff813893ec>] ? _raw_spin_unlock_irqrestore+0x5b/0x69
> [    1.969447]  [<ffffffff81053a3a>] ? up+0x34/0x39
> [    1.969459]  [<ffffffff812198d2>] ? acpi_os_signal_semaphore+0x1c/0x28
> [    1.969472]  [<ffffffff81237aa0>] acpi_get_handle+0x7e/0x92
> [    1.969486]  [<ffffffff816aa050>] pnpacpi_add_device_handler+0x57/0x217
> [    1.969499]  [<ffffffff812378ca>] acpi_ns_get_device_callback+0x135/0x14b
> [    1.969511]  [<ffffffff81053a3a>] ? up+0x34/0x39
> [    1.969523]  [<ffffffff8123728f>] acpi_ns_walk_namespace+0xc3/0x17a
> [    1.969535]  [<ffffffff81237795>] ? acpi_walk_namespace+0xc0/0xc0
> [    1.969547]  [<ffffffff812376c0>] acpi_get_devices+0x5d/0x72
> [    1.969560]  [<ffffffff816a9ff9>] ? ispnpidacpi+0x84/0x84
> [    1.969571]  [<ffffffff816aa210>] ? pnpacpi_add_device_handler+0x217/0x217
> [    1.969584]  [<ffffffff816aa26e>] pnpacpi_init+0x5e/0x8c
> [    1.969596]  [<ffffffff81000276>] do_one_initcall+0x8e/0x12b
> [    1.969608]  [<ffffffff8104d796>] ? parameq+0x1d/0x1f
> [    1.969619]  [<ffffffff8104d924>] ? parse_args+0x18c/0x23f
> [    1.969632]  [<ffffffff81684dd4>] kernel_init_freeable+0x115/0x196
> [    1.969643]  [<ffffffff816846b4>] ? do_early_param+0x88/0x88
> [    1.969654]  [<ffffffff81379a6d>] ? rest_init+0x131/0x131
> [    1.969665]  [<ffffffff81379a76>] kernel_init+0x9/0xd1
> [    1.969676]  [<ffffffff8138e26c>] ret_from_fork+0x7c/0xb0
> [    1.969687]  [<ffffffff81379a6d>] ? rest_init+0x131/0x131
> --
> 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/
>


      reply	other threads:[~2013-08-06  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-06  4:30 3.11.0-rc4 (Linus GIT) -- WARNING: CPU: 1 PID: 1 at kernel/time/tick-sched.c:185 can_stop_full_tick+0x7e/0x89() Miles Lane
2013-08-06  5:34 ` yun wang [this message]

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=52008AEF.2050601@linux.vnet.ibm.com \
    --to=wangyun@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miles.lane@gmail.com \
    /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