From: Mike Galbraith <efault@gmx.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.24-rc7-rt2: WARNING: at include/linux/rcupreempt.h:110 rcu_enter_nohz()
Date: Tue, 15 Jan 2008 04:44:56 +0100 [thread overview]
Message-ID: <1200368696.4061.5.camel@homer.simson.net> (raw)
In-Reply-To: <1200336080.318.8.camel@localhost.localdomain>
Greetings,
I receive $subject upon every resume.
[ 115.223202] CPU1 is down
[ 3.725918] Intel machine check architecture supported.
[ 3.725925] Intel machine check reporting enabled on CPU#0.
[ 3.725927] CPU0: Intel P4/Xeon Extended MCE MSRs (12) available
[ 3.725930] CPU0: Thermal monitoring enabled
[ 3.725936] Back to C!
[ 3.726468] Force enabled HPET at resume
[ 3.726532] Enabling non-boot CPUs ...
[ 3.726796] CPU0 attaching NULL sched-domain.
[ 3.726912] SMP alternatives: switching to SMP code
[ 3.727602] Booting processor 1/1 eip 3000
[ 3.727605] CPU 1 irqstacks, hard=b042d000 soft=b042b000
[ 3.737950] Initializing CPU#1
[ 3.798694] Calibrating delay using timer specific routine.. 5986.21 BogoMIPS (lpj=2993108)
[ 3.798703] CPU: After generic identify, caps: bfebfbff 00000000 00000000 00000000 00004400 00000000 00000000 00000000
[ 3.798714] CPU: Trace cache: 12K uops, L1 D cache: 8K
[ 3.798717] CPU: L2 cache: 512K
[ 3.798719] CPU: Physical Processor ID: 0
[ 3.798721] CPU: After all inits, caps: bfebfbff 00000000 00000000 0000b080 00004400 00000000 00000000 00000000
[ 3.798729] Intel machine check architecture supported.
[ 3.798734] Intel machine check reporting enabled on CPU#1.
[ 3.798738] CPU1: Intel P4/Xeon Extended MCE MSRs (12) available
[ 3.798741] CPU1: Thermal monitoring enabled
[ 3.798893] CPU1: Intel(R) Pentium(R) 4 CPU 3.00GHz stepping 09
[ 3.798916] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
[ 3.818995] CPU0 attaching sched-domain:
[ 3.819000] domain 0: span 3
[ 3.819002] groups: 1 2
[ 3.819006] domain 1: span 3
[ 3.819009] groups: 3
[ 3.819013] CPU1 attaching sched-domain:
[ 3.819016] domain 0: span 3
[ 3.819018] groups: 2 1
[ 3.819020] domain 1: span 3
[ 3.819021] groups: 3
[ 3.819615] CPU1 is up
[ 3.820379] ACPI: Unable to turn cooling device [ef83ab80] 'off'
[ 3.820424] PM: Writing back config space on device 0000:00:01.0 at offset 7 (was 22a0a0a0, writing 2a0a0a0)
[ 3.820444] ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 16 (level, low) -> IRQ 17
[ 3.820450] PCI: Setting latency timer of device 0000:00:1d.0 to 64
[ 3.820481] ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 18
[ 3.820487] PCI: Setting latency timer of device 0000:00:1d.1 to 64
[ 3.820517] ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 16
[ 3.820523] PCI: Setting latency timer of device 0000:00:1d.2 to 64
[ 3.820553] ACPI: PCI Interrupt 0000:00:1d.3[A] -> GSI 16 (level, low) -> IRQ 17
[ 3.820558] PCI: Setting latency timer of device 0000:00:1d.3 to 64
[ 3.820614] BUG: bad accounting of dynamic ticks
[ 3.820616] will try to fix, but it is best to reboot
[ 3.820618] WARNING: at include/linux/rcupreempt.h:110 rcu_enter_nohz()
[ 3.820621] Pid: 0, comm: swapper Not tainted 2.6.24-rt2-smp #64
[ 3.820624] [<b010522a>] show_trace_log_lvl+0x1a/0x30
[ 3.820631] [<b0105ccd>] show_trace+0x12/0x14
[ 3.820634] [<b010641f>] dump_stack+0x6c/0x72
[ 3.820637] [<b0148f10>] tick_nohz_stop_sched_tick+0x2fa/0x30c
[ 3.820641] [<b010256d>] cpu_idle+0x27/0xd2
[ 3.820644] [<b0116f01>] start_secondary+0x19f/0x1a5
[ 3.820648] [<00000000>] 0x0
[ 3.820661] =======================
next prev parent reply other threads:[~2008-01-15 3:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 18:41 2.6.24-rc7-rt2 Steven Rostedt
2008-01-14 20:02 ` 2.6.24-rc7-rt2 Mark Knecht
2008-01-14 22:16 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-14 22:30 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 17:10 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17 2:07 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:11 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-17 17:25 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-17 17:57 ` 2.6.24-rc7-rt2 Mariusz Kozlowski
2008-01-15 0:37 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16 3:50 ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16 4:04 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 6:23 ` 2.6.24-rc7-rt2 Valdis.Kletnieks
2008-01-16 14:12 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 16:22 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-21 11:31 ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-21 12:49 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-27 21:51 ` 2.6.24-rc7-rt2 Esben Nielsen
2008-01-28 2:32 ` 2.6.24-rc7-rt2 Stefan Monnier
2008-01-16 13:17 ` 2.6.24-rc7-rt2 Alan Cox
2008-01-16 4:01 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-16 7:12 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-16 10:11 ` 2.6.24-rc7-rt2 S.Çağlar Onur
2008-01-17 2:20 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 3:44 ` Mike Galbraith [this message]
2008-01-15 16:27 ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-15 18:06 ` 2.6.24-rc7-rt2 Steven Rostedt
2008-01-15 20:04 ` 2.6.24-rc7-rt2 Luotao Fu
2008-01-16 12:03 ` 2.6.24-rc7-rt2 [PATCH] latency tracer fix for ppc32 Luotao Fu
2008-01-17 3:26 ` Steven Rostedt
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=1200368696.4061.5.camel@homer.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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