Description of problem: In the last 6 days, this is happening 1-2 times per day. No new changes made, but I do have all the latest packages available. Version-Release number of selected component (if applicable): 2.6.30.9-90.fc11.i586 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Message from syslogd@server at Nov 1 21:41:58 ... kernel:invalid opcode: 0000 [#1] SMP Message from syslogd@server at Nov 1 21:41:58 ... kernel:last sysfs file: /sys/devices/virtual/vc/vcsa2/dev Message from syslogd@server at Nov 1 21:41:58 ... kernel:Process kswapd0 (pid: 22, ti=dfa28000 task=dfa20ca0 task.ti=dfa28000) Message from syslogd@server at Nov 1 21:41:58 ... kernel:Stack: Message from syslogd@server at Nov 1 21:41:58 ... kernel: 00000002 00000001 c117a740 c12f52a0 c103ba20 c103ba60 c103baa0 c110a600 Message from syslogd@server at Nov 1 21:41:58 ... kernel: c110a640 c110a6e0 c136f800 c10ebc40 c10ebc60 c10ebc80 c114e2e0 c114e260 Message from syslogd@server at Nov 1 21:41:58 ... kernel:Call Trace: Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c048bf17>] ? shrink_list+0x24d/0x4e1 Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c048893d>] ? get_dirty_limits+0x1f/0x2e1 Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c0423803>] ? set_next_entity+0xa0/0x10c Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c0402286>] ? __switch_to+0x78/0xfb Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c042c374>] ? finish_task_switch+0x8d/0xa7 Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c048c3c1>] ? shrink_zone+0x216/0x289 Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c048c8dc>] ? kswapd+0x369/0x51b Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c048b14e>] ? isolate_pages_global+0x0/0x19b Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c044065d>] ? autoremove_wake_function+0x0/0x34 Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c0422947>] ? complete+0x39/0x43 Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c048c573>] ? kswapd+0x0/0x51b Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c048c573>] ? kswapd+0x0/0x51b Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c0440365>] ? kthread+0x4b/0x6f Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c044031a>] ? kthread+0x0/0x6f Message from syslogd@server at Nov 1 21:41:58 ... kernel: [<c0403f87>] ? kernel_thread_helper+0x7/0x10 Message from syslogd@server at Nov 1 21:41:58 ... kernel:Code: f6 43 ea 01 75 24 8b 85 78 ff ff ff f6 40 08 40 0f 84 63 03 00 00 89 f0 e8 88 14 01 00 85 c0 0f 84 2d 03 00 00 bf 01 00 00 00 89 <f0> e8 db f0 ff ff 89 85 7c ff ff ff 8b 46 08 85 c0 78 2b 83 bd Message from syslogd@server at Nov 1 21:41:58 ... kernel:EIP: [<c048b90e>] shrink_page_list+0x1b0/0x56c SS:ESP 0068:dfa29d80 The semaphore timeout period has expired. Expected results: Smooth sailing... Additional info: Nothing else I can find. I do not see anything in the logs, but maybe I am not sure how to get to it.
I should note for the purpose of this bug that it only really occurs when cifs is active and I have external drives (via WinXP) mounted. The problem only recently began, though, and these cifs mounts have existed since cifs was samba.
This computer is officially dead now. It had kept dying on this semaphore issue, and now it keeps rebooting on Probing EDD. Any recourse, or am I out of luck? How do I get it to boot up again?
Sorry, spoke too soon. It was in a recursive reboot loop but after letting it rest for a few minutes, it's back up. However, I would like to know if anyone has any ideas about this semaphore issue. It seems everything else is falling apart now.
As part of this bug, I'm now getting errors like this (which I typed by hand, so please excuse any typos): BUG: unable to handle kernel paging request at efd86f5c *pde = 00000000 last sysfs file: /sys/devices/virtual/vc/vcsa6/dev Modules linked in: sco bridge stp llc bnep l2cap bluetooth autofs4 nls_utf8 cifs sunrpc ipv6 uinput snd_emu10k1_synth snd_emux_synth snd_seq_virimidi snd_seq_midi_event snd_seq_mid_emul snd_seq ppdev snd_emu10k1 snd_via82xx snd_ac97_codec ac97_bus snd_pcm snd_mpu401_uart snd_timer snd_rawmidi snd_page_alloc snd_util_mem snd_seq_device snd_hwdep via686a hwmon joydev snd pcspkr e1000 i2c_viapro emu10k1_gp gameport parport_pc soundcore parport ata_generic pata_acpi pata_via radeon drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan] Pid: 1990, com: java Not tainted (2.6.30.8-64.fc11.i586 #1) MS-6330 EIP: 0060:[<c0423fff>] EFLAGS 00010086 CPU: 0 EIP is at dequeue_entity+0x1f1/0x1fc EAX: f1099c5c EBX: ffffffff ECX: feced300 EDX: 000026d7 ESI: c1407b18 EDI: c1407ae0 EBP: d5a29d70 ESP: d5a29d4c DS: 007b ES: 007b FC: 00d8 GS: 0033 SS: 0068 Process java (pid: 1990, ti = d5a28000 task=df3d3340 task.ti=d5a28000 Stack: f1099c5c 000026d7 fcf8c733 ffffffff feced300 ffffffff c1407b18 df3d336c c1407ae0 d5a29d84 c042485d c073a384 df3d3340 00000000 d5a29db0 c0420d29 00000001 c1407ae0 dd163fc8 00000277 00000000 00000000 c1407ae0 c099b1dc Call Trace: [<c042485d>] ? dequeue_task_fair+0x21/0x61 [<c0420d29>] ? dequeue_task+0x125/0x134 [<c0420d86>] ? deactivate_task+0x24/0x2a [<c072d164>] ? __schedule+0x13f/0x7b0 [<c072d7e2>] ? schedule+0xd/0x1c [<c044ca8a>] ? futex_wait+0x188/0x340 [<c0484341>] ? file_accessed+0x19/0x1b [<c04863d6>] ? generic_file_aio_read+0x4b5/0x4ef [<c0485de1>] ? generic_file_aio_write+0x69/0xb1 [<c0429b21>] ? default_wake_function+0x0/0x12 [<c044dc89>] ? do_futex+0x6f/0x62b [<c04411dd>] ? autoremove_wake_function+0x0/0x34 [<c044e316>] ? sys_futex+0x31/0xe3 [<c040a40d>] ? syscall_trace_enter+0xdc+0xf0 [<c0403515>] ?syscall+call+0x7/0xb Code: 89 c1 89 d3 2b 4d dc 1b 5d e0 89 4d ec 83 fb 00 89 5d f0 7c 0d 7f 05 83 f9 00 76 06 89 45 dc 89 55 e0 8b 45 dc 8b 55 e0 89 46 14 <89> 56 18 83 c4 18 5b 5e 5f 5d ce 55 89 e5 89 e5 57 56 53 83 ec 2c 0f EIP: [<c0423fff>] dequeue_entity+0x1f1/0x1fc SS:ESP:0068:d5a29d4c CR2: 00000000efd86f5c ---[end of trace 2e4465db50ae58a0 ]--- Does anyone have ANY idea? This machine has crashed at least 15 times today....
More stuff. Can someone just give me an idea of what I could potentially uninstall or reinstall to fix this? Message from syslogd@server at Nov 10 11:03:42 ... kernel:Oops: 0002 [#1] SMP Message from syslogd@server at Nov 10 11:03:42 ... kernel:last sysfs file: /sys/devices/virtual/vc/vcsa3/dev Message from syslogd@server at Nov 10 11:03:42 ... kernel:Process java (pid: 2000, ti=df348000 task=df360000 task.ti=df348000) Message from syslogd@server at Nov 10 11:03:42 ... kernel:Stack: Message from syslogd@server at Nov 10 11:03:42 ... kernel: df349fac c04ab655 0176fd57 00000000 00000001 00000037 8c4118f8 00000000 Message from syslogd@server at Nov 10 11:03:42 ... kernel: df348000 c0403535 00000037 00000000 0176fd57 8c4118f8 00000000 8c411910 Message from syslogd@server at Nov 10 11:03:42 ... kernel:Call Trace: Message from syslogd@server at Nov 10 11:03:42 ... kernel: [<c056ecad>] ? might_fault+0x1c/0x1e Message from syslogd@server at Nov 10 11:03:42 ... kernel: [<c056edfc>] ? copy_to_user+0x34/0x10a Message from syslogd@server at Nov 10 11:03:42 ... kernel: [<c04ab655>] ? sys_llseek+0x59/0x77 Message from syslogd@server at Nov 10 11:03:42 ... kernel: [<c0403535>] ? syscall_call+0x7/0xb Message from syslogd@server at Nov 10 11:03:42 ... kernel:Code: e9 8d 55 ec 89 d8 e8 a4 f2 ff ff 58 5a 5b 5e 5f 5d c3 55 89 e5 53 89 c3 c6 44 10 0c 00 8b 90 0c 01 00 00 4a 89 90 0c 01 00 00 31 <c0> 85 d2 75 64 8b 03 8b 53 04 85 c0 89 02 74 03 89 50 04 c7 03 Message from syslogd@server at Nov 10 11:03:42 ... kernel:EIP: [<c072f36a>] collect_one_slot+0x19/0x85 SS:ESP 0068:df349f6c Message from syslogd@server at Nov 10 11:03:42 ... kernel:CR2: 000000006a991546 Message from syslogd@server at Nov 10 11:09:14 ... kernel:Oops: 0002 [#2] SMP Message from syslogd@server at Nov 10 11:09:14 ... kernel:last sysfs file: /sys/devices/virtual/vc/vcsa3/dev Message from syslogd@server at Nov 10 11:09:14 ... kernel:Process perl (pid: 2660, ti=d1a4a000 task=c8d1d860 task.ti=d1a4a000) Message from syslogd@server at Nov 10 11:09:14 ... kernel:Stack: Message from syslogd@server at Nov 10 11:09:14 ... kernel: 00000000 c08f5840 00000001 00000001 00000000 001201d2 00000000 00000246 Message from syslogd@server at Nov 10 11:09:14 ... kernel: c08f5020 c08f5020 001201d2 df77f54c c08f7120 d1a4be60 c04878d2 c08f7120 Message from syslogd@server at Nov 10 11:09:14 ... kernel:Call Trace: Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c04876b5>] ? get_page_from_freelist+0x22e/0x3a2 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c04878d2>] ? __alloc_pages_internal+0xa9/0x384 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c06cc245>] ? ip_local_deliver+0x66/0x6d Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c048967a>] ? __do_page_cache_readahead+0xa9/0x160 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c0489777>] ? do_page_cache_readahead+0x46/0x50 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c04836f0>] ? filemap_fault+0x149/0x31d Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c0494b66>] ? __do_fault+0x41/0x316 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c04950e5>] ? handle_mm_fault+0x2aa/0x640 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c072e1fa>] ? do_page_fault+0x206/0x215 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c072dff4>] ? do_page_fault+0x0/0x215 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c072c7ed>] ? error_code+0x6d/0x80 Message from syslogd@server at Nov 10 11:09:14 ... kernel: [<c072dff4>] ? do_page_fault+0x0/0x215 Message from syslogd@server at Nov 10 11:09:14 ... kernel:Code: 16 50 53 68 45 0f 84 c0 6a 33 68 34 0f 84 c0 e8 45 da eb ff 83 c4 14 8b 13 8b 43 04 89 42 04 89 10 c7 43 04 00 02 20 00 c7 03 00 <01> 10 00 8b 5d fc c9 c3 55 89 e5 57 89 cf 56 89 d6 53 89 c3 8b Message from syslogd@server at Nov 10 11:09:14 ... kernel:EIP: [<c0571b6c>] list_del+0x58/0x60 SS:ESP 0068:d1a4bdb0 Message from syslogd@server at Nov 10 11:09:14 ... kernel:CR2: 00000000a0cb2518
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.