cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
524
Views
0
Helpful
3
Replies

Cisco 3850 Switch stuck in BUG: scheduling while atomic: sirq-rcu/0/0x10000001/13, CPU#0

Lee Win Neng
Level 1
Level 1

Hi,

 

I would like to request for assistance/advice on the bug logs as shown below which found from the WS-C3850-24T on version 03.02.03.SE. During the incident, the switch was stuck/hung which unable to SSH or take control from the device via console which require hard reboot by pulling the power cable. 

 

After restarted, the switch was back to normal and I would like to request for anyone that experiencing this issue might able to provide some guidance. Kindly informed that the log shows below was captured before hard reboot when console to the switch.

 

Logs:-

BUG: scheduling while atomic: sirq-rcu/0/0x10000001/13, CPU#0
Modules linked in: rtc_ds1307 mtd_map bpa_mem crashinfo pds tun cpumem exportfs nfsd ipv6 OOBnd(P) OOBhal(P) cvmx_mdio cvmx_gpio aipcmod(P) mtsmod procfs(P) utaker_mod dplr_pci [last unloaded: sysmgr_hb]
Call Trace:
[<ffffffff8110e100>] dump_stack+0x8/0x34
[<ffffffff8110efe0>] __schedule+0x770/0x990
[<ffffffff811105e8>] __mutex_lock_slowpath+0x1a8/0x278
[<ffffffff811106f8>] mutex_lock+0x40/0x48
[<ffffffff8111219c>] __reacquire_kernel_lock+0x2c/0x50
[<ffffffff8110ed08>] __schedule+0x498/0x990
[<ffffffff8110f350>] schedule+0x10/0x28
[<ffffffff8110f758>] schedule_timeout+0x190/0x350
[<ffffffff811f5ab8>] msleep+0x28/0x38
[<ffffffff811b06b4>] die+0x134/0x150
[<ffffffff811130b0>] do_page_fault+0x350/0x4a8
[<ffffffff81100984>] ret_from_exception+0x0/0x10
[<ffffffff812a4870>] __link_path_walk+0x68/0x1408
[<ffffffff812a5ec4>] path_walk+0x64/0x108
[<ffffffff812a6080>] do_path_lookup+0x60/0x68
[<ffffffff812a6ecc>] do_filp_open+0xdc/0xbc8
[<ffffffff81253e70>] nova_default_koops_write_oops_to_persistent_store+0x48/0x120
[<ffffffff81254194>] koops_save_oops+0x18c/0x338
[<ffffffff811b0698>] die+0x118/0x150
[<ffffffff811130b0>] do_page_fault+0x350/0x4a8
[<ffffffff81100984>] ret_from_exception+0x0/0x10
[<ffffffff812a4870>] __link_path_walk+0x68/0x1408
[<ffffffff812a5ec4>] path_walk+0x64/0x108
[<ffffffff812a6080>] do_path_lookup+0x60/0x68
[<ffffffff812a6ecc>] do_filp_open+0xdc/0xbc8
[<ffffffff81253e70>] nova_default_koops_write_oops_to_persistent_store+0x48/0x120
[<ffffffff81254194>] koops_save_oops+0x18c/0x338
[<ffffffff811b0698>] die+0x118/0x150
[<ffffffff811b1c38>] do_ade+0x0/0x2b0

 

Thank you for kind advice and guidance.

3 Replies 3

Mark Malone
VIP Alumni
VIP Alumni
Hi
That image is way to old to be running due to bugs and was never an advisable image , upgrade to a newer stable image its 6 years old , the train is up to 3.7 now and then the newer package releases too like Everest etc

 

Leo Laohoo
Hall of Fame
Hall of Fame
I'm not even going to try to troubleshoot an issue from an old code like 3.2.X.
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: