Hide Forgot
Description of problem: it happens randomly running the weekly raid scrub Additional info: reporter: libreport-2.8.0 BUG: unable to handle kernel paging request at 0000000000100020 IP: [<ffffffffc0630631>] raid_run_ops+0x4d1/0x15a0 [raid456] PGD 0 Oops: 0000 [#1] SMP Modules linked in: bnep cfg80211 nfnetlink_queue nfnetlink_log bluetooth rfkill fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun ip6t_REJECT nf_reject_ipv6 xt_conntrack ip6t_rpfilter ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_mangle ip6table_security ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_raw iptable_mangle iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables xfs dm_cache_smq dm_cache coretemp kvm_intel snd_hda_codec_analog snd_hda_codec_generic iTCO_wdt gpio_ich iTCO_vendor_support kvm raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx dm_thin_pool dm_persistent_data dm_bio_prison libcrc32c raid6_pq irqbypass dvb_pll cx22702 cx88_dvb cx88_vp3054_i2c videobuf2_dvb dvb_core ir_lirc_codec lirc_dev rc_cinergy_1400 snd_hda_intel snd_hda_codec snd_hda_core joydev snd_hwdep snd_seq i2c_i801 cx8800 cx8802 i2c_smbus cx88xx snd_seq_device videobuf2_dma_sg videobuf2_memops tveeprom videobuf2_v4l2 videobuf2_core snd_pcm rc_core v4l2_common videodev media lpc_ich snd_timer snd soundcore acpi_cpufreq shpchp asus_atk0110 tpm_tis tpm_tis_core tpm binfmt_misc nfsd auth_rpcgss nfs_acl lockd grace sunrpc ata_generic pata_acpi nouveau serio_raw firewire_ohci firewire_core video mxm_wmi wmi i2c_algo_bit drm_kms_helper crc_itu_t skge ttm hid_logitech ff_memless drm pata_jmicron fjes CPU: 0 PID: 743 Comm: md127_raid5 Not tainted 4.8.6-300.fc25.x86_64 #1 Hardware name: System manufacturer System Product Name/P5B-Deluxe, BIOS 1238 09/30/2008 task: ffff99e7b7651d40 task.stack: ffff99e7b68a8000 RIP: 0010:[<ffffffffc0630631>] [<ffffffffc0630631>] raid_run_ops+0x4d1/0x15a0 [raid456] RSP: 0018:ffff99e7b68abab0 EFLAGS: 00010206 RAX: 0000000034d4ac88 RBX: ffff99e70a8d2ab8 RCX: 0000000034d4ac80 RDX: 0000000000000001 RSI: 0000000000000021 RDI: ffff99e70a8d2940 RBP: ffff99e7b68abb70 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001 R13: 0000000000000178 R14: ffff99e70a8d2968 R15: 0000000000100000 FS: 0000000000000000(0000) GS:ffff99e7bfc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000100020 CR3: 00000001772e4000 CR4: 00000000000006f0 Stack: ffff99e7b68abb18 00000003bfc99580 00000000bfc99580 ffff99e700000005 ffff99e7594ad7c0 ffff99e7b68abaf0 ffffffffb00caab2 ffffd1ea3fc00110 ffff99e7b68abb18 ffff99e70a8d29a8 0000000000000000 ffff99e70a8d2940 Call Trace: [<ffffffffb00caab2>] ? check_preempt_curr+0x52/0x90 [<ffffffffc06350e3>] handle_stripe+0xc13/0x2490 [raid456] [<ffffffffb00e4d9b>] ? autoremove_wake_function+0x2b/0x40 [<ffffffffb00e4600>] ? __wake_up_common+0x30/0x80 [<ffffffffc0636af8>] handle_active_stripes.isra.52+0x198/0x4d0 [raid456] [<ffffffffc06372b3>] raid5d+0x483/0x710 [raid456] [<ffffffffb0654db9>] md_thread+0x139/0x150 [<ffffffffb00e4d70>] ? prepare_to_wait_event+0xf0/0xf0 [<ffffffffb0654c80>] ? find_pers+0x70/0x70 [<ffffffffb00c0c08>] kthread+0xd8/0xf0 [<ffffffffb080277f>] ret_from_fork+0x1f/0x40 [<ffffffffb00c0b30>] ? kthread_worker_fn+0x180/0x180 Code: 00 4c 89 bb 08 02 00 00 48 8b 7d 98 c6 47 68 00 fb 66 66 90 66 66 90 4d 85 ff 4c 8b 45 90 74 96 48 8b 8b 20 02 00 00 48 8d 41 08 <49> 3b 47 20 76 85 4e 8d ac 2f f0 01 00 00 eb 16 4d 8b 3f 4d 85 RIP [<ffffffffc0630631>] raid_run_ops+0x4d1/0x15a0 [raid456] RSP <ffff99e7b68abab0> CR2: 0000000000100020 Potential duplicate: bug 1357290
Created attachment 1220094 [details] File: dmesg
This has been going on for a long time, irrespective of the kernel release. Can you help me finding out where the problem is?
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 25 kernel bugs. Fedora 25 has now been rebased to 4.9.3-200.fc25. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26. If you experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.