+++ This bug was initially created as a clone of Bug #1235021 +++ Description of problem: Can't report about kernel problem "Server responded with an error: 'uReport data is invalid.'" --- Additional comment from Mikhail on 2015-06-23 15:05:30 EDT --- --- Additional comment from Marek Bryša on 2015-06-24 03:14:41 EDT --- The modules were parsed wrong. Oops: ...correct modules here... video irq event stamp: 416210 hardirqs last enabled at (416209): [<ffffffff8188cdac>] restore_args+0x0/0x30 hardirqs last disabled at (416210): [<ffffffff8188d11d>] apic_timer_interrupt+0x6d/0x80 softirqs last enabled at (416208): [<ffffffff810b2d03>] __do_softirq+0x3b3/0x670 softirqs last disabled at (416203): [<ffffffff810b3245>] irq_exit+0x145/0x150 Resulted in uReport: , "videoirq" , "event" , "stamp:" , "416210hardirqs" , "last" , "enabled" , "at" , "(416209):" --- Additional comment from Marek Bryša on 2015-06-24 03:17:08 EDT --- Thank you for reporting this bug. It seems that the format of kernel oopses has changed again and we need to reflect it in our parser. --- Additional comment from Marek Bryša on 2015-06-24 04:23:25 EDT --- Upstream pull request: https://github.com/abrt/satyr/pull/231 --- Additional comment from Fedora Update System on 2015-07-08 06:02:56 EDT --- libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22 --- Additional comment from Fedora Update System on 2015-07-13 15:14:24 EDT --- Package libreport-2.6.1-1.fc22, abrt-2.6.1-1.fc22, satyr-0.19-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreport-2.6.1-1.fc22 abrt-2.6.1-1.fc22 satyr-0.19-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-11434/libreport-2.6.1-1.fc22,abrt-2.6.1-1.fc22,satyr-0.19-1.fc22 then log in and leave karma (feedback). --- Additional comment from Fedora Update System on 2015-07-18 21:56:30 EDT --- libreport-2.6.1-1.fc22, abrt-2.6.1-1.fc22, satyr-0.19-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Created attachment 1278771 [details] oops-2017-05-14-20:21:19-1052-0
I would have thought that a bug that prevented other bugs from being reported would be a priority. I haven't been able to report kernel bugs in rawhide for 2 1/2 months now, at least not using the automated tools. How's this one coming along?
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Same happens in Fedora 26 also (kernel 4.14.8-200.fc26.x86_64).
(In reply to Doncho N. Gunchev from comment #4) > Same happens in Fedora 26 also (kernel 4.14.8-200.fc26.x86_64). [11820.237474] ------------[ cut here ]------------ [11820.237491] WARNING: CPU: 7 PID: 0 at net/core/dev.c:5547 net_rx_action+0x2d0/0x3c0 [11820.237494] Modules linked in: ses enclosure scsi_transport_sas uas usb_storage rfcomm ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c tun bridge stp llc fuse ebtable_filter ebtables ip6table_filter ip6_tables arc4 cmac bnep sunrpc vfat fat dcdbas intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_realtek joydev snd_hda_codec_generic uvcvideo kvm videobuf2_vmalloc videobuf2_memops iTCO_wdt ath10k_pci videobuf2_v4l2 snd_hda_intel videobuf2_core ath10k_core snd_hda_codec iTCO_vendor_support videodev irqbypass hid_multitouch snd_hda_core snd_hwdep intel_cstate media mac80211 snd_seq hci_uart btusb intel_uncore btrtl snd_seq_device btqca btbcm snd_pcm [11820.237572] btintel intel_rapl_perf ath bluetooth snd_timer cfg80211 snd acer_wmi i2c_i801 soundcore wmi_bmof mei_me rtsx_pci_ms sparse_keymap ucsi_acpi memstick tpm_crb idma64 typec_ucsi mei ecdh_generic intel_lpss_pci intel_pch_thermal typec tpm_tis rfkill intel_lpss_acpi pinctrl_sunrisepoint tpm_tis_core pinctrl_intel tpm intel_lpss acpi_pad shpchp binfmt_misc btrfs xor zstd_decompress zstd_compress xxhash raid6_pq dm_crypt nouveau i915 rtsx_pci_sdmmc mmc_core mxm_wmi ttm i2c_algo_bit crct10dif_pclmul drm_kms_helper crc32_pclmul r8169 crc32c_intel ghash_clmulni_intel drm serio_raw mii rtsx_pci i2c_hid wmi video i2c_dev [11820.237641] CPU: 7 PID: 0 Comm: swapper/7 Not tainted 4.14.8-200.fc26.x86_64 #1 [11820.237644] Hardware name: Acer Predator PH317-51/Sienna_KLS, BIOS V1.09 07/06/2017 [11820.237647] task: ffff98e3ec24bf80 task.stack: ffffb1eb41998000 [11820.237653] RIP: 0010:net_rx_action+0x2d0/0x3c0 [11820.237656] RSP: 0018:ffff98e3fedc3ec0 EFLAGS: 00010297 [11820.237660] RAX: 000000000000004d RBX: 00000000ffffffff RCX: ffff98e3de931e88 [11820.237663] RDX: ffff98df86318000 RSI: 0000000000000000 RDI: ffffffffc0d4ed40 [11820.237665] RBP: ffff98e3fedc3f30 R08: 0000000000000002 R09: 0000000000000000 [11820.237668] R10: 0000000000006e68 R11: 0000000000000001 R12: ffff98e3de937ba0 [11820.237671] R13: 0000000000000040 R14: 0000000000000000 R15: 0000000000000003 [11820.237674] FS: 0000000000000000(0000) GS:ffff98e3fedc0000(0000) knlGS:0000000000000000 [11820.237678] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [11820.237680] CR2: 0000171b64183000 CR3: 0000000252e09002 CR4: 00000000003606e0 [11820.237684] Call Trace: [11820.237687] <IRQ> [11820.237697] __do_softirq+0xe3/0x2bd [11820.237704] irq_exit+0xfb/0x100 [11820.237709] do_IRQ+0x80/0xd0 [11820.237716] common_interrupt+0x9d/0x9d [11820.237718] </IRQ> [11820.237726] RIP: 0010:cpuidle_enter_state+0x130/0x2d0 [11820.237729] RSP: 0018:ffffb1eb4199be70 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffda [11820.237733] RAX: ffff98e3fedda440 RBX: 00000ac01cfcde8f RCX: 000000000000001f [11820.237736] RDX: 00000ac01cfcde8f RSI: 0000093023f680d8 RDI: 0000000000000000 [11820.237739] RBP: ffffb1eb4199beb0 R08: 00000000000006ed R09: 0000000000000018 [11820.237741] R10: ffffb1eb4199be40 R11: 00000000000002ee R12: ffff98e3fede2b00 [11820.237744] R13: 0000000000000000 R14: 0000000000000006 R15: ffffffffacecdeb8 [11820.237753] cpuidle_enter+0x17/0x20 [11820.237759] call_cpuidle+0x23/0x40 [11820.237764] do_idle+0x181/0x1d0 [11820.237770] cpu_startup_entry+0x73/0x80 [11820.237775] start_secondary+0x192/0x1e0 [11820.237781] secondary_startup_64+0xa5/0xa5 [11820.237785] Code: 8b 7e 08 49 83 c6 18 44 89 e9 44 89 fa 4c 89 e6 41 ff d2 4d 8b 16 4d 85 d2 75 e4 4c 8b 75 90 44 89 f8 41 39 c5 0f 8d 95 fe ff ff <0f> ff 41 39 c5 0f 8f 93 fe ff ff 49 8b 44 24 10 a8 04 0f 85 88 [11820.237850] ---[ end trace f6cc8a11d86d2644 ]--- I used to be able to report kernel OOPS with Fedora 26, but last 3 months or so it is not working any more.
See also bug #1532004.
Any progress? I'm close to disabling abrt since it is now just annoying without providing any value to anyone.
Yes, we have fixed it and new version was released. We need to update our server now and it should work. I'm gonna update the server this week and I'll let you know.
It works now.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 EOL if it remains open with a Fedora 'version' of '27'. 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. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 27 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.