Fedora Linux Support Community & Resources Center
  #1  
Old 26th December 2007, 12:59 PM
TSPx Offline
Registered User
 
Join Date: Oct 2006
Posts: 5
fedora kernel: BUG: soft lockup

I am using Fedora 8 and i am getting freezes from time to time, this is what i get in my message logs.
http://pastebin.com/m7ac9858

A little sample

Dec 21 16:29:27 fedora kernel: BUG: soft lockup - CPU#0 stuck for 24s! [wish:2244]
Dec 21 16:29:27 fedora kernel:
Dec 21 16:29:27 fedora kernel: Pid: 2244, comm: wish
Dec 21 16:29:27 fedora kernel: EIP: 0073:[<00824902>] CPU: 0
Dec 21 16:29:27 fedora kernel: EIP is at 0x824902
Dec 21 16:29:27 fedora kernel: ESP: 007b:bfc55cc4 EFLAGS: 00000206 Not tainted (2.6.23.9-85.fc8 #1)
Dec 21 16:29:27 fedora kernel: EAX: 00000000 EBX: 0987f2cc ECX: 00000080 EDX: 00062e5d
Dec 21 16:29:27 fedora kernel: ESI: bfc55cc8 EDI: 00062e5d EBP: bfc55d14 DS: 007b ES: 007b FS: 0000
Dec 21 16:29:27 fedora kernel: CR0: 8005003b CR2: 099327e8 CR3: 1de04000 CR4: 000006d0
Dec 21 16:29:27 fedora kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Dec 21 16:29:27 fedora kernel: DR6: ffff0ff0 DR7: 00000400
Dec 21 16:29:27 fedora kernel: =======================
Dec 21 16:30:03 fedora kernel: BUG: soft lockup - CPU#0 stuck for 266s! [swapper:0]
Dec 21 16:30:03 fedora kernel:
Dec 21 16:30:03 fedora kernel: Pid: 0, comm: swapper
Dec 21 16:30:03 fedora kernel: EIP: 0060:[<c05382e6>] CPU: 0
Dec 21 16:30:03 fedora kernel: EIP is at acpi_idle_enter_simple+0x17b/0x1f1
Dec 21 16:30:03 fedora kernel: EFLAGS: 00000206 Not tainted (2.6.23.9-85.fc8 #1)
Dec 21 16:30:03 fedora kernel: EAX: 00000000 EBX: 000006ce ECX: 00000000 EDX: 00000000
Dec 21 16:30:03 fedora kernel: ESI: 00000000 EDI: 00d505a8 EBP: 00d4feda DS: 007b ES: 007b FS: 00d8
Dec 21 16:30:03 fedora kernel: CR0: 8005003b CR2: 08ec4788 CR3: 1d3c9000 CR4: 000006d0
Dec 21 16:30:03 fedora kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Dec 21 16:30:03 fedora kernel: DR6: ffff0ff0 DR7: 00000400
Dec 21 16:30:03 fedora kernel: [<c05a2399>] cpuidle_idle_call+0x5c/0x7f
Dec 21 16:30:03 fedora kernel: [<c05a233d>] cpuidle_idle_call+0x0/0x7f
Dec 21 16:30:03 fedora kernel: [<c040340b>] cpu_idle+0xab/0xcc
Dec 21 16:30:03 fedora kernel: [<c073fa6c>] start_kernel+0x32c/0x334
Dec 21 16:30:03 fedora kernel: [<c073f177>] unknown_bootoption+0x0/0x195
Dec 21 16:30:03 fedora kernel: =======================

Any help is muh apprecited, i want to keep using this great distro!

Ps: My laptop is a Hp nx9020 (Intel Celerom 1400, / Intel video and wireless / 512 mb RAM)
Reply With Quote
  #2  
Old 27th December 2007, 02:26 PM
PhillyFloyd Offline
Registered User
 
Join Date: Jun 2007
Location: Washington DC
Posts: 338
LOL -- that's a good one, let's eliminate the obvious ---> Are you using 2.6.24 kernel version ... or compiled a custom kernel with some high resolution timers included?

Post:

# uname -a

I have only ever seen this problem in development, never in a stable kernel version, but I haven't seen it all by any stretch of the imagination
__________________
"You're as useless as a jiffy in a tickless kernel."
Reply With Quote
  #3  
Old 27th December 2007, 02:43 PM
TSPx Offline
Registered User
 
Join Date: Oct 2006
Posts: 5
i am using fedora stable kernel Linux fedora 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 i686 i386 GNU/Linux
I have this problem since the first stable kernel version in Fedora 8

BTW: what is funny? "let's eliminate the obvious???!!! seams like is not so obvious don't you think?

Last edited by TSPx; 27th December 2007 at 02:51 PM.
Reply With Quote
  #4  
Old 27th December 2007, 06:12 PM
PhillyFloyd Offline
Registered User
 
Join Date: Jun 2007
Location: Washington DC
Posts: 338
Howdy

Thanks for the info (I misuse LOL all the time, I use it as a greeting sometimes, so I end up confusing folks, sorry)

Try booting with ACPI off: acpi=off on the kernel line

The chipset isn't SMP so turning off ACPI wouldn't be a major issue, plus MSP should be able to detect these older CPUs if they are SMP regardless.

Anyway ... try the acpi=off and see if that improves stability for you, if these continue with acpi off you can try idle=poll on the boot line but I think this isn't very useful anymore except with oprofile ... you also need to watch out for your CPU overheating -- probably not such a great idea

Let's see how turning off acpi works for u
__________________
"You're as useless as a jiffy in a tickless kernel."
Reply With Quote
  #5  
Old 27th December 2007, 08:31 PM
TSPx Offline
Registered User
 
Join Date: Oct 2006
Posts: 5
Hi again! thanks for your help i will try this options tomorrow at work where i get this freezes and post the results.
happy new year!

Cheers!
Reply With Quote
  #6  
Old 29th December 2007, 05:20 PM
sceotend Offline
Registered User
 
Join Date: Jul 2007
Location: Canada
Age: 43
Posts: 15
I have the same problem happening on my system since a bunch of updates yesterday.

Linux draegon 2.6.23.9-85.fc8 #1 SMP Fri Dec 7 15:49:59 EST 2007 i686 i686 i386 GNU/Linux

The system is an Intel(R) Pentium(R) D CPU 3.00GHz on an ASUS P5LD2 Deluxe motherboard.

Kernel Errors:
Code:
Dec 29 11:45:56 draegon kernel: BUG: soft lockup - CPU#0 stuck for 11s! [X:3483]
Dec 29 11:45:56 draegon kernel:
Dec 29 11:45:56 draegon kernel: Pid: 3483, comm:                    X
Dec 29 11:45:56 draegon kernel: EIP: 0060:[<f8b7177d>] CPU: 0
Dec 29 11:45:56 draegon kernel: EIP is at _ZN4Asic22ElapsedTS_PollingUntil19ConditionSuccessfulEv+0x1d/0x80 [fglrx]
Dec 29 11:45:56 draegon kernel:  EFLAGS: 00203286    Tainted: P         (2.6.23.9-85.fc8 #1)
Dec 29 11:45:56 draegon kernel: EAX: 000e0070 EBX: f5d43d84 ECX: f8ff3020 EDX: 00011000
Dec 29 11:45:56 draegon kernel: ESI: 00000000 EDI: f5d43d84 EBP: f5d43d2c DS: 007b ES: 007b FS: 00d8
Dec 29 11:45:56 draegon kernel: CR0: 80050033 CR2: a54e0000 CR3: 33487000 CR4: 000006d0
Dec 29 11:45:56 draegon kernel: DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
Dec 29 11:45:56 draegon kernel: DR6: ffff0ff0 DR7: 00000400
Dec 29 11:45:56 draegon kernel:  [<f8b71098>] _ZN4Asic9WaitUntil15WaitForCompleteEv+0x38/0xf0 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<f8b70126>] _ZN4Asic19PM4ElapsedTimeStampERK23PM4_TS_INTERRUPT_PARAMSj14_LARGE_INTEGER+0x166/0x200 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<c04244ce>] __wake_up_common+0x32/0x55
Dec 29 11:45:56 draegon kernel:  [<c0615774>] unix_stream_recvmsg+0x3a2/0x4c3
Dec 29 11:45:56 draegon kernel:  [<f8b65560>] _Z19uQSTimeStampRetiredjjj14_LARGE_INTEGER+0xf0/0x100 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<f8b63a92>] _Z8uCWDDEQCjjjPvjS_+0x282/0xcc0 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<f8b54c44>] CMMQS_uCWDDEQC+0x34/0x40 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<f8b245e8>] firegl_cmmqs_CWDDE_32+0x238/0x340 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<f8b23606>] firegl_cmmqs_CWDDE32+0x76/0x110 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<f8b23590>] firegl_cmmqs_CWDDE32+0x0/0x110 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<f8b134ce>] firegl_ioctl+0x1ae/0x230 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<f8b0791c>] ip_firegl_ioctl+0x1c/0x21 [fglrx]
Dec 29 11:45:56 draegon kernel:  [<c048b4c9>] do_ioctl+0x4d/0x63
Dec 29 11:45:56 draegon kernel:  [<c048b716>] vfs_ioctl+0x237/0x249
Dec 29 11:45:56 draegon kernel:  [<c048b774>] sys_ioctl+0x4c/0x64
Dec 29 11:45:56 draegon kernel:  [<c040518a>] syscall_call+0x7/0xb
Dec 29 11:45:56 draegon kernel:  [<c0610000>] xfrm_state_sort+0x2e/0x5a
Dec 29 11:45:56 draegon kernel:  =======================
Recent Updates:
Code:
Dec 28 23:56:47 draegon yum: Updated: avahi - 0.6.21-8.fc8.i386
Dec 28 23:57:29 draegon yum: Updated: policycoreutils - 2.0.33-3.fc8.i386
Dec 28 23:57:30 draegon yum: Updated: totem-plparser - 2.20.1-2.fc8.i386
Dec 28 23:57:31 draegon yum: Updated: gimp-libs - 2:2.4.3-1.fc8.i386
Dec 28 23:57:32 draegon yum: Updated: SDL - 1.2.12-5.fc8.i386
Dec 28 23:57:33 draegon yum: Updated: avahi-compat-libdns_sd - 0.6.21-8.fc8.i386
Dec 28 23:57:34 draegon yum: Updated: avahi-compat-howl - 0.6.21-8.fc8.i386
Dec 28 23:57:35 draegon yum: Updated: avahi-qt3 - 0.6.21-8.fc8.i386
Dec 28 23:57:36 draegon yum: Updated: avahi-glib - 0.6.21-8.fc8.i386
Dec 28 23:57:37 draegon yum: Updated: imlib - 1:1.9.15-6.fc8.i386
Dec 28 23:57:59 draegon yum: Updated: amsn - 0.97-1.fc8.i386
Dec 28 23:58:04 draegon yum: Updated: scim-bridge - 0.4.14-1.fc8.i386
Dec 28 23:58:05 draegon yum: Updated: scim-bridge-gtk - 0.4.14-1.fc8.i386
Dec 28 23:58:28 draegon yum: Updated: gimp - 2:2.4.3-1.fc8.i386
Dec 28 23:58:55 draegon yum: Updated: totem - 2.20.1-2.fc8.i386
Dec 28 23:59:02 draegon yum: Updated: totem-mozplugin - 2.20.1-2.fc8.i386
Dec 28 23:59:05 draegon yum: Updated: gdb - 6.6-38.fc8.i386
Dec 28 23:59:10 draegon yum: Updated: selinux-policy - 3.0.8-72.fc8.noarch
Dec 28 23:59:34 draegon yum: Updated: selinux-policy-devel - 3.0.8-72.fc8.noarch
Dec 28 23:59:39 draegon yum: Updated: SDL-devel - 1.2.12-5.fc8.i386
Dec 28 23:59:39 draegon yum: Updated: yum-fastestmirror - 1.1.9-2.fc8.noarch
Dec 28 23:59:41 draegon yum: Updated: amsn-plugins - 0.97-1.fc8.i386
Dec 29 00:00:31 draegon yum: Updated: selinux-policy-targeted - 3.0.8-72.fc8.noarch
Dec 29 00:00:32 draegon yum: Updated: yum-utils - 1.1.9-2.fc8.noarch
Dec 29 00:00:35 draegon yum: Updated: yum-updatesd - 1:0.9-1.fc8.noarch
Dec 29 00:00:36 draegon yum: Updated: python-iniparse - 0.2.3-3.fc8.noarch
Dec 29 00:00:37 draegon yum: Updated: avahi-devel - 0.6.21-8.fc8.i386
Dec 29 00:00:37 draegon yum: Updated: yum-protectbase - 1.1.9-2.fc8.noarch
Dec 29 00:00:39 draegon yum: Updated: policycoreutils-gui - 2.0.33-3.fc8.i386
The avahi update is my first suspect - CUPS is having a disagreement with it in the messages log, and printing isn't working all the time since the update:

Code:
Dec 29 11:47:44 draegon cupsd[2494]: *** WARNING *** The program 'cupsd' uses the Apple Bonjour compatibility layer of Avahi.
Dec 29 11:47:44 draegon cupsd[2494]: *** WARNING *** Please fix your application to use the native API of Avahi!
Dec 29 11:47:44 draegon cupsd[2494]: *** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=cupsd>
Rolling back all the other updates will be the next step to try and resolve this issue, since the system was very stable before the batch listed went in (is there an easy way to accomplish that??).
Reply With Quote
  #7  
Old 29th December 2007, 08:29 PM
PhillyFloyd Offline
Registered User
 
Join Date: Jun 2007
Location: Washington DC
Posts: 338
Have you recently modified anything pertaining to your ATI driver ... looks like possible problems with ACPI and your fglrx driver ... not an expert by any stretch, other possible problems possible with do_ioctl not calling drv_open but I would start with checking your video driver and possibly rolling back to the past fglrx if it was recently updated....also what else you had running as far as X apps might be useful ... doubt the DNS/avahi has much to do with it from the backtrace above

you can also try the acpi=off or noacpi (can't remember if it matters) on the kernel boot line and see how you fare
__________________
"You're as useless as a jiffy in a tickless kernel."
Reply With Quote
  #8  
Old 9th July 2009, 05:50 AM
milovikasse Offline
Registered User
 
Join Date: Jul 2009
Posts: 1
Hi,
same problem I found in fc5 with kernel 2.6.15-1.2054_FC5smp #1 SMP
oft lockup detected on CPU#1!

Pid: 15, comm: kblockd/1
EIP: 0060:[<c02f2260>] CPU: 1
EIP is at _spin_lock_irqsave+0x2/0xd
EFLAGS: 00200247 Not tainted (2.6.15-1.2054_FC5smp #1)
EAX: f7151920 EBX: f7152e00 ECX: 00000001 EDX: 00200247
ESI: f715180c EDI: f7fdf6c0 EBP: 00200247 DS: 007b ES: 007b
CR0: 8005003b CR2: b7f00000 CR3: 06a20440 CR4: 000006f0
[<c01d05d1>] cfq_kick_queue+0x16/0x80
[<c01314b0>] run_workqueue+0x7f/0xba [<c01d05bb>] cfq_kick_queue+0x0/0x80
[<c0131c9d>] worker_thread+0x0/0x117 [<c0131d83>] worker_thread+0xe6/0x117
[<c011da13>] default_wake_function+0x0/0xc [<c01345b1>] kthread+0x9d/0xc9
[<c0134514>] kthread+0x0/0xc9 [<c0102005>] kernel_thread_helper+0x5/0xb
BUG: soft lockup detected on CPU#0!

Pid: 14, comm: kblockd/0
EIP: 0060:[<c02f2234>] CPU: 0
EIP is at _spin_unlock_irqrestore+0xa/0xc
EFLAGS: 00200247 Not tainted (2.6.15-1.2054_FC5smp #1)
EAX: 00000000 EBX: 00200247 ECX: 00000001 EDX: 00200247
ESI: f7152e9c EDI: f7fdf740 EBP: 00200247 DS: 007b ES: 007b
CR0: 8005003b CR2: b7f00000 CR3: 36e1c200 CR4: 000006f0
[<c0131496>] run_workqueue+0x65/0xba [<c01d05bb>] cfq_kick_queue+0x0/0x80
[<c0131c9d>] worker_thread+0x0/0x117 [<c0131d83>] worker_thread+0xe6/0x117
[<c011da13>] default_wake_function+0x0/0xc [<c01345b1>] kthread+0x9d/0xc9
[<c0134514>] kthread+0x0/0xc9 [<c0102005>] kernel_thread_helper+0x5/0xb
BUG: soft lockup detected on CPU#1!
Reply With Quote
Reply

Tags
bug, fedora, kernel, lockup, soft

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Fedora Kernel: soft lockup ever resolved? simpfeld Using Fedora 0 9th November 2008 07:49 PM
bug: soft lockup detected on cpu#0 ded1717 Using Fedora 0 8th January 2006 07:35 PM


Current GMT-time: 18:50 (Tuesday, 29-07-2014)

TopSubscribe to XML RSS for all Threads in all ForumsFedoraForumDotOrg Archive
logo

All trademarks, and forum posts in this site are property of their respective owner(s).
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.

Privacy Policy | Term of Use | Posting Guidelines | Archive | Contact Us | Founding Members

Powered by vBulletin® Copyright ©2000 - 2012, vBulletin Solutions, Inc.

FedoraForum is Powered by RedHat