From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Folkert van Heusden <folkert@vanheusden.com>
Cc: linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [2.6.28-rc5] RCU detected CPU 0 stall (t=4294893165/750 jiffies)
Date: Fri, 21 Nov 2008 17:30:12 +0800 [thread overview]
Message-ID: <49267FA4.60609@cn.fujitsu.com> (raw)
In-Reply-To: <20081119123717.GE24427@vanheusden.com>
Hi, Folkert van Heusden,
Can you tell me how can I reproduce this bug.
Thanx, Lai
Folkert van Heusden wrote:
> During the boot-process of a 2.6.28-RC5 kernel I got the followin on
> the console:
>
> - [ 3.479998] RCU detected CPU 0 stall (t=4294893165/750 jiffies)
> ! [ 3.480004] Pid: 1, comm: swapper Not tainted 2.6.28-rc5-custom2 #1
> ! [ 3.480004] Call Trace:
> ! [ 3.480004] [<c0300c33>] ? printk+0xf/0x14
> ! [ 3.480004] [<c0166f15>] __rcu_pending+0x53/0x189
> ! [ 3.480004] [<c0167067>] rcu_pending+0x1c/0x47
> ! [ 3.480004] [<c0132aa4>] update_process_times+0x2b/0x4e
> ! [ 3.480004] [<c0144c8d>] tick_sched_timer+0x6d/0x9b
> ! [ 3.480004] [<c0144c20>] ? tick_sched_timer+0x0/0x9b
> ! [ 3.480004] [<c013e0cc>] __run_hrtimer+0x60/0x97
> ! [ 3.480004] [<c013eb35>] hrtimer_interrupt+0xfe/0x166
> ! [ 3.480004] [<c0112eea>] smp_apic_timer_interrupt+0x6c/0x7f
> ! [ 3.480004] [<c0104829>] apic_timer_interrupt+0x2d/0x34
> ! [ 3.480004] [<c043c454>] ? inflate_codes+0x272/0x3bc
> ! [ 3.480004] [<c043cf22>] inflate_dynamic+0x4c0/0x4f0
> ! [ 3.480004] [<c043d775>] unpack_to_rootfs+0x524/0x975
> ! [ 3.480004] [<c0147eaf>] ? debug_check_no_locks_freed+0x1a/0x123
> ! [ 3.480004] [<c043e202>] ? populate_rootfs+0x0/0xcd
> ! [ 3.480004] [<c043e202>] ? populate_rootfs+0x0/0xcd
> ! [ 3.480004] [<c043e278>] populate_rootfs+0x76/0xcd
> ! [ 3.480004] [<c0101130>] _stext+0x48/0x11e
> ! [ 3.480004] [<c0206830>] ? ida_get_new_above+0x157/0x171
> ! [ 3.480004] [<c0218a08>] ? _raw_spin_lock+0x53/0xfa
> ! [ 3.480004] [<c02189b1>] ? _raw_spin_unlock+0x74/0x78
> ! [ 3.480004] [<c0303759>] ? _spin_unlock+0x1d/0x20
> ! [ 3.480004] [<c01c1ab1>] ? proc_register+0x146/0x157
> ! [ 3.480004] [<c01c1bda>] ? create_proc_entry+0x7b/0x91
> ! [ 3.480004] [<c0166600>] ? register_irq_proc+0x7b/0x9b
> ! [ 3.480004] [<c0166666>] ? init_irq_proc+0x46/0x59
> ! [ 3.480004] [<c04392ee>] kernel_init+0x102/0x150
> ! [ 3.480004] [<c04391ec>] ? kernel_init+0x0/0x150
> ! [ 3.480004] [<c0104987>] kernel_thread_helper+0x7/0x10
> + [ 4.773412] Freeing initrd memory: 53252k freed
>
> This is a P4 with hyperthreading. 0.5GB ram. IDE disk.
>
>
> Folkert van Heusden
>
next prev parent reply other threads:[~2008-11-21 9:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 12:37 [2.6.28-rc5] RCU detected CPU 0 stall (t=4294893165/750 jiffies) Folkert van Heusden
2008-11-21 9:30 ` Lai Jiangshan [this message]
2008-11-21 9:45 ` Folkert van Heusden
2008-11-21 15:12 ` Paul E. McKenney
2008-11-21 15:34 ` Folkert van Heusden
2008-11-21 15:53 ` Paul E. McKenney
2008-11-21 17:38 ` Folkert van Heusden
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=49267FA4.60609@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.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