Description of problem: The problem occurs on a acer sw5 271 and seems to have to do with the USB port, because if I connect an external drive to it manifests a bug that prevents the system from booting. Additional info: reporter: libreport-2.8.0 BUG: unable to handle kernel NULL pointer dereference at 0000000000000001 IP: [<ffffffffc02d9de5>] i2c_hid_irq+0x75/0x120 [i2c_hid] PGD 0 Oops: 0000 [#1] SMP Modules linked in: hid_sensor_hub(+) acer_wmi(+) ghash_clmulni_intel(+) intel_cstate intel_uncore iwlmvm(+) intel_rapl_perf mac80211 uvcvideo snd_soc_rt5640 snd_soc_rl6231 videobuf2_vmalloc videobuf2_memops iwlwifi videobuf2_v4l2 videobuf2_core btusb videodev btrtl snd_soc_ssm4567 btbcm snd_soc_core btintel bluetooth media snd_hda_codec_realtek snd_hda_codec_generic snd_compress snd_hda_codec_hdmi snd_pcm_dmaengine ac97_bus cfg80211 joydev i2c_i801 i2c_smbus intel_pch_thermal snd_hda_intel lpc_ich rfkill snd_hda_codec snd_hda_core acpi_als kfifo_buf snd_hwdep snd_seq industrialio snd_seq_device snd_pcm int3403_thermal snd_soc_sst_acpi snd_soc_sst_match wmi dw_dmac snd_timer i2c_designware_platform i2c_designware_core snd spi_pxa2xx_platform int3402_thermal int3406_thermal int3400_thermal mei_me acpi_thermal_rel acpi_pad mei intel_vbtn processor_thermal_device int340x_thermal_zone tpm_tis soundcore sparse_keymap tpm_tis_core shpchp intel_soc_dts_iosf soc_button_array tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc uas usb_storage i915 i2c_algo_bit drm_kms_helper drm crc32c_intel serio_raw sdhci_acpi sdhci mmc_core video i2c_hid fjes hid_chicony CPU: 2 PID: 530 Comm: irq/28-ITE8351: Not tainted 4.9.4-201.fc25.x86_64 #1 Hardware name: Acer Aspire SW5-271/Aspire SW5-271, BIOS V1.08 11/26/2014 task: ffff8a1c18ff0000 task.stack: ffffa174409f4000 RIP: 0010:[<ffffffffc02d9de5>] [<ffffffffc02d9de5>] i2c_hid_irq+0x75/0x120 [i2c_hid] RSP: 0018:ffffa174409f7e10 EFLAGS: 00010246 RAX: 0000000000000028 RBX: ffff8a1c1696ab40 RCX: 0000000000000000 RDX: 0000000000000000 RSI: 0000000000000002 RDI: ffff8a1c15afb0e8 RBP: ffffa174409f7e28 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000085340800 R11: 0000000000000000 R12: 0000000000000028 R13: ffff8a1c18c14000 R14: ffff8a1c18ff0000 R15: ffffffffa1100940 FS: 0000000000000000(0000) GS:ffff8a1c1ed00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000001 CR3: 0000000155d92000 CR4: 00000000003406e0 Stack: ffff8a1c15bc8380 ffff8a1c18c14000 ffff8a1c18c14000 ffffa174409f7e50 ffffffffa1100960 ffff8a1c15bc8380 ffff8a1c15bc8380 ffff8a1c18ff0000 ffffa174409f7ec0 ffffffffa1100baf 0000000000000000 ffff8a1c18ff0000 Call Trace: [<ffffffffa1100960>] irq_thread_fn+0x20/0x50 [<ffffffffa1100baf>] irq_thread+0x12f/0x1b0 [<ffffffffa11009c0>] ? wake_threads_waitq+0x30/0x30 [<ffffffffa1100a80>] ? irq_thread_dtor+0xc0/0xc0 [<ffffffffa10c2569>] kthread+0xd9/0xf0 [<ffffffffa10c2490>] ? kthread_park+0x60/0x60 [<ffffffffa181ced5>] ret_from_fork+0x25/0x30 Code: 89 e0 89 c1 48 c7 c2 40 b5 2d c0 48 c7 c6 e8 b2 2d c0 48 83 c7 20 e8 4b d7 26 e1 5b b8 01 00 00 00 41 5c 41 5d 5d c3 4c 8b 43 38 <41> 0f be 48 01 45 0f be 28 c1 e1 08 41 09 cd 75 1f f0 0f ba 73 RIP [<ffffffffc02d9de5>] i2c_hid_irq+0x75/0x120 [i2c_hid] RSP <ffffa174409f7e10> CR2: 0000000000000001
Created attachment 1243304 [details] File: dmesg
*********** 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.10.9-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 2 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.