Akregator freezes from times to time. Unfortunately it is not reproducable when, but by accident I found the following in the syslog: kernel [12927.663078] BUG: soft lockup - CPU#2 stuck for 22s! [akregator:12428] kernel [12927.663083] Modules linked in: nls_iso8859_1(F) snd_hrtimer(F) pci_stub vboxpci(OF) vboxnetadp(OF) vboxnetflt(OF) vboxdrv(OF) usblp input_polldev bnep rfcomm parport_pc(F) ppdev(F) deflate(F) ctr(F) twofish_generic(F) twofish_x86_64_3way(F) twofish_x86_64(F) twofish_common(F) camellia_generic(F) camellia_x86_64(F) serpent_sse2_x86_64(F) glue_helper(F) serpent_generic(F) blowfish_generic(F) blowfish_x86_64(F) blowfish_common(F) cast5_generic(F) des_generic(F) xcbc(F) rmd160(F) crypto_null(F) af_key(F) xfrm_algo(F) binfmt_misc(F) uvcvideo videobuf2_core videodev videobuf2_vmalloc qmi_wwan videobuf2_memops usbnet cdc_wdm qcserial usb_wwan usbserial btusb bluetooth snd_hda_codec_hdmi coretemp snd_hda_codec_conexant snd_hda_intel arc4(F) snd_hda_codec kvm iwldvm mac80211 snd_hwdep(F) snd_pcm(F) thinkpad_acpi snd_seq_midi(F) snd_rawmidi(F) ghash_clmulni_intel(F) aesni_intel(F) snd_seq_midi_event(F) snd_seq(F) ablk_helper(F) snd_timer(F) cryptd(F) lrw(F) aes_x86_64(F) snd_seq_device(F) kernel iwlwifi xts(F) gf128mul(F) psmouse(F) lpc_ich snd(F) mei intel_ips microcode(F) cfg80211 mac_hid serio_raw(F) snd_page_alloc(F) soundcore(F) nvram(F) lp(F) parport(F) btrfs(F) zlib_deflate(F) libcrc32c(F) raid10(F) raid456(F) async_pq(F) async_xor(F) xor(F) async_memcpy(F) async_raid6_recov(F) raid6_pq(F) async_tx(F) raid1(F) raid0(F) multipath(F) linear(F) i915 drm_kms_helper drm e1000e(F) ums_realtek usb_storage(F) uas i2c_algo_bit wmi video(F) kernel [12927.663156] CPU 2 kernel [12927.663160] Pid: 12428, comm: akregator Tainted: GF O 3.7.0-7-generic #15-Ubuntu LENOVO 3680ZKY/3680ZKY kernel [12927.663161] RIP: 0033:[<0000003a6ec80516>] [<0000003a6ec80516>] 0x3a6ec80515 kernel [12927.663168] RSP: 002b:00007fffefca5ae0 EFLAGS: 00000297 kernel [12927.663169] RAX: 0000000000000001 RBX: 000000000000fe2e RCX: 0000000000000005 29.12.2012 18:13:18 beuys kernel [12927.663170] RDX: 000000006155ef10 RSI: 0000003a6efb87d8 RDI: 0000000000000051 kernel [12927.663171] RBP: 00000000000001f0 R08: 000000000000001f R09: 0000000000000020 kernel [12927.663172] R10: 00000000fffffe00 R11: 0000000000000007 R12: 00000000000001f0 kernel [12927.663173] R13: ffffffff816afa48 R14: ffff880063649f70 R15: 0000003a6efb8740 kernel [12927.663174] FS: 00007f199f04b7c0(0000) GS:ffff88023bd00000(0000) knlGS:0000000000000000 kernel [12927.663176] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 kernel [12927.663177] CR2: 00007f196c77f000 CR3: 0000000020e11000 CR4: 00000000000007e0 29.12.2012 18:13:18 beuys kernel [12927.663178] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 kernel [12927.663179] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 kernel [12927.663180] Process akregator (pid: 12428, threadinfo ffff880063648000, task ffff88016de31700) Reproducible: Sometimes
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of akregator (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.