Help identifying cause of Linux (¿kernel?) error

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I'm having some problems on my computer https://superuser.com/questions/1259808/windows-linux-wont-boot-from-any-disk-were-working-before. I've managed to install Ubuntu 17.10 and it works but I get a random error once in a while and sometimes it freezes the computer. I'm not able to find what's causing it so that's why I'm asking for help.



Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373314] ------------[ cut here ]------------
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373319] WARNING: CPU: 1 PID: 2213 at /build/linux-XO_uEE/linux-4.13.0/arch/x86/include/asm/fpu/internal.h:373 __kernel_fpu_end+0x7f/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373319] Modules linked in: ccm nls_iso8859_1 rfcomm cmac snd_hda_codec_hdmi bnep intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp btusb btrtl kvm_intel snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel snd_pcm pcbc snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi iwlmvm mac80211 aes_x86_64 crypto_simd glue_helper snd_seq cryptd snd_seq_device snd_timer iwlwifi intel_cstate intel_rapl_perf uas snd input_leds joydev cfg80211 usb_storage soundcore mei_me mei shpchp hci_uart btbcm serdev btqca btintel bluetooth acpi_als ecdh_generic mac_hid kfifo_buf industrialio intel_lpss_acpi intel_lpss acpi_pad parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_microsoft hid_logitech_hidpp
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373344] hid_logitech_dj usbhid nouveau mxm_wmi wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 ahci drm mii libahci video pinctrl_sunrisepoint pinctrl_intel i2c_hid hid
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373352] CPU: 1 PID: 2213 Comm: Classif~ Update Not tainted 4.13.0-16-generic #19-Ubuntu
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373353] Hardware name: Gigabyte Technology Co., Ltd. B250M-DS3H/B250M-DS3H-CF, BIOS F4 02/21/2017
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373354] task: ffff97ebe79b5f00 task.stack: ffffa99e49574000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373355] RIP: 0010:__kernel_fpu_end+0x7f/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373355] RSP: 0018:ffffa99e49577a70 EFLAGS: 00010282
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373356] RAX: 00000000fffffffe RBX: ffff97ec0d6cb000 RCX: ffff97ebe79b5f00
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373357] RDX: 00000000ffffffff RSI: 0000000000000400 RDI: ffff97ebe79b7300
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373357] RBP: ffffa99e49577a80 R08: 00000000dd26ba6f R09: 000000007af37ff3
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373358] R10: 000000009ea07279 R11: ffff97ec0d6cb3f0 R12: 0000000000000400
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373358] R13: ffffa99e49577b28 R14: ffffffffa5c47770 R15: ffff97ebe452e1f0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373359] FS: 00007fc9712fd700(0000) GS:ffff97ec2ec80000(0000) knlGS:0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373359] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373360] CR2: 00007fc984901020 CR3: 00000001e78ac000 CR4: 00000000003406e0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373360] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373361] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373361] Call Trace:
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373364] kernel_fpu_end+0xe/0x10
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373365] crc32c_pcl_intel_update+0x9c/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373366] crypto_shash_update+0x3f/0x120
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373368] ? jbd2__journal_start+0xda/0x1e0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373370] ext4_inode_bitmap_csum_set+0x68/0xb0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373371] __ext4_new_inode+0xdce/0x1500
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373373] ext4_create+0xb7/0x1c0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373374] path_openat+0x1316/0x1630
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373375] ? SyS_getdents+0xe4/0x130
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373377] do_filp_open+0x9b/0x110
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373378] ? __check_object_size+0xaf/0x1b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373380] ? __alloc_fd+0x46/0x170
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373381] do_sys_open+0x1bb/0x2b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373382] ? do_sys_open+0x1bb/0x2b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373383] SyS_openat+0x14/0x20
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373385] entry_SYSCALL_64_fastpath+0x1e/0xa9
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373385] RIP: 0033:0x7fc9a194370c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373386] RSP: 002b:00007fc9712f8760 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373387] RAX: ffffffffffffffda RBX: 000000000000006f RCX: 00007fc9a194370c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373387] RDX: 0000000000000241 RSI: 00007fc95a7bbb88 RDI: ffffffffffffff9c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373388] RBP: 0000000000000000 R08: 0000000000000000 R09: 00007fc95a7bb000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373388] R10: 00000000000001b4 R11: 0000000000000293 R12: 00007fc9712f8880
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373389] R13: 00007fc95a8d4ec0 R14: 0000000000000000 R15: 0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373389] Code: b9 00 14 00 00 48 89 7d f0 eb 0a 0f 1f 00 db e2 0f 77 db 45 f0 0f 1f 44 00 00 b8 ff ff ff ff 89 c2 48 0f c7 1f 31 c0 85 c0 74 af <0f> ff eb ab 31 c0 48 0f ae 89 00 14 00 00 85 c0 74 9d 0f ff eb 
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373404] ---[ end trace 1f94f12b6b3af23d ]---


Thanks!




ubuntu kernel kernel-panic




share|improve this question




















  • Not sure what caused it from this trace. How can you be sure this is this is the exact cause of the freeze? Many times, upon kernel oops, there isn't enough time to flush the kernel log to disk and the backtrace seen in logs is some other which didn't actually cause oops. Also on a different note, current stable kernel is 4.13.8 so you can expect bugs in 4.13.0 :)
    – bytefire
    Oct 20 '17 at 10:08










  • @Okash Hm, I'm not exactly sure. But looking the times in the log it seems to me that it is.
    – José María
    Oct 20 '17 at 10:21










  • Looks like filesystem corruption, which could be a one-time thing or, if it happens frequently, could be due to bad RAM or SSD. Can you boot from a rescue disk and run fsck on every filesystem?
    – Mark Plotnick
    Oct 20 '17 at 17:14











  • @MarkPlotnick It's not the SSD. I tried on two SSD and one USB disk. The same problem happens on all of them. I also tried another memory module from a friend, so it's not the RAM.
    – José María
    Oct 22 '17 at 9:51















up vote
0
down vote

favorite












I'm having some problems on my computer https://superuser.com/questions/1259808/windows-linux-wont-boot-from-any-disk-were-working-before. I've managed to install Ubuntu 17.10 and it works but I get a random error once in a while and sometimes it freezes the computer. I'm not able to find what's causing it so that's why I'm asking for help.



Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373314] ------------[ cut here ]------------
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373319] WARNING: CPU: 1 PID: 2213 at /build/linux-XO_uEE/linux-4.13.0/arch/x86/include/asm/fpu/internal.h:373 __kernel_fpu_end+0x7f/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373319] Modules linked in: ccm nls_iso8859_1 rfcomm cmac snd_hda_codec_hdmi bnep intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp btusb btrtl kvm_intel snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel snd_pcm pcbc snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi iwlmvm mac80211 aes_x86_64 crypto_simd glue_helper snd_seq cryptd snd_seq_device snd_timer iwlwifi intel_cstate intel_rapl_perf uas snd input_leds joydev cfg80211 usb_storage soundcore mei_me mei shpchp hci_uart btbcm serdev btqca btintel bluetooth acpi_als ecdh_generic mac_hid kfifo_buf industrialio intel_lpss_acpi intel_lpss acpi_pad parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_microsoft hid_logitech_hidpp
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373344] hid_logitech_dj usbhid nouveau mxm_wmi wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 ahci drm mii libahci video pinctrl_sunrisepoint pinctrl_intel i2c_hid hid
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373352] CPU: 1 PID: 2213 Comm: Classif~ Update Not tainted 4.13.0-16-generic #19-Ubuntu
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373353] Hardware name: Gigabyte Technology Co., Ltd. B250M-DS3H/B250M-DS3H-CF, BIOS F4 02/21/2017
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373354] task: ffff97ebe79b5f00 task.stack: ffffa99e49574000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373355] RIP: 0010:__kernel_fpu_end+0x7f/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373355] RSP: 0018:ffffa99e49577a70 EFLAGS: 00010282
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373356] RAX: 00000000fffffffe RBX: ffff97ec0d6cb000 RCX: ffff97ebe79b5f00
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373357] RDX: 00000000ffffffff RSI: 0000000000000400 RDI: ffff97ebe79b7300
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373357] RBP: ffffa99e49577a80 R08: 00000000dd26ba6f R09: 000000007af37ff3
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373358] R10: 000000009ea07279 R11: ffff97ec0d6cb3f0 R12: 0000000000000400
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373358] R13: ffffa99e49577b28 R14: ffffffffa5c47770 R15: ffff97ebe452e1f0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373359] FS: 00007fc9712fd700(0000) GS:ffff97ec2ec80000(0000) knlGS:0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373359] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373360] CR2: 00007fc984901020 CR3: 00000001e78ac000 CR4: 00000000003406e0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373360] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373361] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373361] Call Trace:
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373364] kernel_fpu_end+0xe/0x10
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373365] crc32c_pcl_intel_update+0x9c/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373366] crypto_shash_update+0x3f/0x120
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373368] ? jbd2__journal_start+0xda/0x1e0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373370] ext4_inode_bitmap_csum_set+0x68/0xb0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373371] __ext4_new_inode+0xdce/0x1500
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373373] ext4_create+0xb7/0x1c0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373374] path_openat+0x1316/0x1630
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373375] ? SyS_getdents+0xe4/0x130
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373377] do_filp_open+0x9b/0x110
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373378] ? __check_object_size+0xaf/0x1b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373380] ? __alloc_fd+0x46/0x170
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373381] do_sys_open+0x1bb/0x2b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373382] ? do_sys_open+0x1bb/0x2b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373383] SyS_openat+0x14/0x20
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373385] entry_SYSCALL_64_fastpath+0x1e/0xa9
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373385] RIP: 0033:0x7fc9a194370c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373386] RSP: 002b:00007fc9712f8760 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373387] RAX: ffffffffffffffda RBX: 000000000000006f RCX: 00007fc9a194370c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373387] RDX: 0000000000000241 RSI: 00007fc95a7bbb88 RDI: ffffffffffffff9c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373388] RBP: 0000000000000000 R08: 0000000000000000 R09: 00007fc95a7bb000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373388] R10: 00000000000001b4 R11: 0000000000000293 R12: 00007fc9712f8880
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373389] R13: 00007fc95a8d4ec0 R14: 0000000000000000 R15: 0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373389] Code: b9 00 14 00 00 48 89 7d f0 eb 0a 0f 1f 00 db e2 0f 77 db 45 f0 0f 1f 44 00 00 b8 ff ff ff ff 89 c2 48 0f c7 1f 31 c0 85 c0 74 af <0f> ff eb ab 31 c0 48 0f ae 89 00 14 00 00 85 c0 74 9d 0f ff eb 
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373404] ---[ end trace 1f94f12b6b3af23d ]---


Thanks!




ubuntu kernel kernel-panic




share|improve this question




















  • Not sure what caused it from this trace. How can you be sure this is this is the exact cause of the freeze? Many times, upon kernel oops, there isn't enough time to flush the kernel log to disk and the backtrace seen in logs is some other which didn't actually cause oops. Also on a different note, current stable kernel is 4.13.8 so you can expect bugs in 4.13.0 :)
    – bytefire
    Oct 20 '17 at 10:08










  • @Okash Hm, I'm not exactly sure. But looking the times in the log it seems to me that it is.
    – José María
    Oct 20 '17 at 10:21










  • Looks like filesystem corruption, which could be a one-time thing or, if it happens frequently, could be due to bad RAM or SSD. Can you boot from a rescue disk and run fsck on every filesystem?
    – Mark Plotnick
    Oct 20 '17 at 17:14











  • @MarkPlotnick It's not the SSD. I tried on two SSD and one USB disk. The same problem happens on all of them. I also tried another memory module from a friend, so it's not the RAM.
    – José María
    Oct 22 '17 at 9:51













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I'm having some problems on my computer https://superuser.com/questions/1259808/windows-linux-wont-boot-from-any-disk-were-working-before. I've managed to install Ubuntu 17.10 and it works but I get a random error once in a while and sometimes it freezes the computer. I'm not able to find what's causing it so that's why I'm asking for help.



Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373314] ------------[ cut here ]------------
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373319] WARNING: CPU: 1 PID: 2213 at /build/linux-XO_uEE/linux-4.13.0/arch/x86/include/asm/fpu/internal.h:373 __kernel_fpu_end+0x7f/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373319] Modules linked in: ccm nls_iso8859_1 rfcomm cmac snd_hda_codec_hdmi bnep intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp btusb btrtl kvm_intel snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel snd_pcm pcbc snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi iwlmvm mac80211 aes_x86_64 crypto_simd glue_helper snd_seq cryptd snd_seq_device snd_timer iwlwifi intel_cstate intel_rapl_perf uas snd input_leds joydev cfg80211 usb_storage soundcore mei_me mei shpchp hci_uart btbcm serdev btqca btintel bluetooth acpi_als ecdh_generic mac_hid kfifo_buf industrialio intel_lpss_acpi intel_lpss acpi_pad parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_microsoft hid_logitech_hidpp
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373344] hid_logitech_dj usbhid nouveau mxm_wmi wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 ahci drm mii libahci video pinctrl_sunrisepoint pinctrl_intel i2c_hid hid
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373352] CPU: 1 PID: 2213 Comm: Classif~ Update Not tainted 4.13.0-16-generic #19-Ubuntu
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373353] Hardware name: Gigabyte Technology Co., Ltd. B250M-DS3H/B250M-DS3H-CF, BIOS F4 02/21/2017
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373354] task: ffff97ebe79b5f00 task.stack: ffffa99e49574000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373355] RIP: 0010:__kernel_fpu_end+0x7f/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373355] RSP: 0018:ffffa99e49577a70 EFLAGS: 00010282
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373356] RAX: 00000000fffffffe RBX: ffff97ec0d6cb000 RCX: ffff97ebe79b5f00
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373357] RDX: 00000000ffffffff RSI: 0000000000000400 RDI: ffff97ebe79b7300
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373357] RBP: ffffa99e49577a80 R08: 00000000dd26ba6f R09: 000000007af37ff3
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373358] R10: 000000009ea07279 R11: ffff97ec0d6cb3f0 R12: 0000000000000400
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373358] R13: ffffa99e49577b28 R14: ffffffffa5c47770 R15: ffff97ebe452e1f0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373359] FS: 00007fc9712fd700(0000) GS:ffff97ec2ec80000(0000) knlGS:0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373359] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373360] CR2: 00007fc984901020 CR3: 00000001e78ac000 CR4: 00000000003406e0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373360] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373361] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373361] Call Trace:
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373364] kernel_fpu_end+0xe/0x10
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373365] crc32c_pcl_intel_update+0x9c/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373366] crypto_shash_update+0x3f/0x120
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373368] ? jbd2__journal_start+0xda/0x1e0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373370] ext4_inode_bitmap_csum_set+0x68/0xb0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373371] __ext4_new_inode+0xdce/0x1500
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373373] ext4_create+0xb7/0x1c0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373374] path_openat+0x1316/0x1630
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373375] ? SyS_getdents+0xe4/0x130
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373377] do_filp_open+0x9b/0x110
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373378] ? __check_object_size+0xaf/0x1b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373380] ? __alloc_fd+0x46/0x170
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373381] do_sys_open+0x1bb/0x2b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373382] ? do_sys_open+0x1bb/0x2b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373383] SyS_openat+0x14/0x20
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373385] entry_SYSCALL_64_fastpath+0x1e/0xa9
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373385] RIP: 0033:0x7fc9a194370c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373386] RSP: 002b:00007fc9712f8760 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373387] RAX: ffffffffffffffda RBX: 000000000000006f RCX: 00007fc9a194370c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373387] RDX: 0000000000000241 RSI: 00007fc95a7bbb88 RDI: ffffffffffffff9c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373388] RBP: 0000000000000000 R08: 0000000000000000 R09: 00007fc95a7bb000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373388] R10: 00000000000001b4 R11: 0000000000000293 R12: 00007fc9712f8880
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373389] R13: 00007fc95a8d4ec0 R14: 0000000000000000 R15: 0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373389] Code: b9 00 14 00 00 48 89 7d f0 eb 0a 0f 1f 00 db e2 0f 77 db 45 f0 0f 1f 44 00 00 b8 ff ff ff ff 89 c2 48 0f c7 1f 31 c0 85 c0 74 af <0f> ff eb ab 31 c0 48 0f ae 89 00 14 00 00 85 c0 74 9d 0f ff eb 
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373404] ---[ end trace 1f94f12b6b3af23d ]---


Thanks!




ubuntu kernel kernel-panic




share|improve this question












I'm having some problems on my computer https://superuser.com/questions/1259808/windows-linux-wont-boot-from-any-disk-were-working-before. I've managed to install Ubuntu 17.10 and it works but I get a random error once in a while and sometimes it freezes the computer. I'm not able to find what's causing it so that's why I'm asking for help.



Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373314] ------------[ cut here ]------------
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373319] WARNING: CPU: 1 PID: 2213 at /build/linux-XO_uEE/linux-4.13.0/arch/x86/include/asm/fpu/internal.h:373 __kernel_fpu_end+0x7f/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373319] Modules linked in: ccm nls_iso8859_1 rfcomm cmac snd_hda_codec_hdmi bnep intel_rapl arc4 x86_pkg_temp_thermal intel_powerclamp coretemp btusb btrtl kvm_intel snd_hda_codec_realtek kvm snd_hda_codec_generic snd_hda_intel irqbypass snd_hda_codec snd_hda_core crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel snd_pcm pcbc snd_seq_midi snd_seq_midi_event aesni_intel snd_rawmidi iwlmvm mac80211 aes_x86_64 crypto_simd glue_helper snd_seq cryptd snd_seq_device snd_timer iwlwifi intel_cstate intel_rapl_perf uas snd input_leds joydev cfg80211 usb_storage soundcore mei_me mei shpchp hci_uart btbcm serdev btqca btintel bluetooth acpi_als ecdh_generic mac_hid kfifo_buf industrialio intel_lpss_acpi intel_lpss acpi_pad parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_microsoft hid_logitech_hidpp
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373344] hid_logitech_dj usbhid nouveau mxm_wmi wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 ahci drm mii libahci video pinctrl_sunrisepoint pinctrl_intel i2c_hid hid
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373352] CPU: 1 PID: 2213 Comm: Classif~ Update Not tainted 4.13.0-16-generic #19-Ubuntu
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373353] Hardware name: Gigabyte Technology Co., Ltd. B250M-DS3H/B250M-DS3H-CF, BIOS F4 02/21/2017
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373354] task: ffff97ebe79b5f00 task.stack: ffffa99e49574000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373355] RIP: 0010:__kernel_fpu_end+0x7f/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373355] RSP: 0018:ffffa99e49577a70 EFLAGS: 00010282
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373356] RAX: 00000000fffffffe RBX: ffff97ec0d6cb000 RCX: ffff97ebe79b5f00
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373357] RDX: 00000000ffffffff RSI: 0000000000000400 RDI: ffff97ebe79b7300
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373357] RBP: ffffa99e49577a80 R08: 00000000dd26ba6f R09: 000000007af37ff3
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373358] R10: 000000009ea07279 R11: ffff97ec0d6cb3f0 R12: 0000000000000400
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373358] R13: ffffa99e49577b28 R14: ffffffffa5c47770 R15: ffff97ebe452e1f0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373359] FS: 00007fc9712fd700(0000) GS:ffff97ec2ec80000(0000) knlGS:0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373359] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373360] CR2: 00007fc984901020 CR3: 00000001e78ac000 CR4: 00000000003406e0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373360] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373361] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373361] Call Trace:
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373364] kernel_fpu_end+0xe/0x10
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373365] crc32c_pcl_intel_update+0x9c/0xa0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373366] crypto_shash_update+0x3f/0x120
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373368] ? jbd2__journal_start+0xda/0x1e0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373370] ext4_inode_bitmap_csum_set+0x68/0xb0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373371] __ext4_new_inode+0xdce/0x1500
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373373] ext4_create+0xb7/0x1c0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373374] path_openat+0x1316/0x1630
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373375] ? SyS_getdents+0xe4/0x130
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373377] do_filp_open+0x9b/0x110
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373378] ? __check_object_size+0xaf/0x1b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373380] ? __alloc_fd+0x46/0x170
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373381] do_sys_open+0x1bb/0x2b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373382] ? do_sys_open+0x1bb/0x2b0
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373383] SyS_openat+0x14/0x20
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373385] entry_SYSCALL_64_fastpath+0x1e/0xa9
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373385] RIP: 0033:0x7fc9a194370c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373386] RSP: 002b:00007fc9712f8760 EFLAGS: 00000293 ORIG_RAX: 0000000000000101
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373387] RAX: ffffffffffffffda RBX: 000000000000006f RCX: 00007fc9a194370c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373387] RDX: 0000000000000241 RSI: 00007fc95a7bbb88 RDI: ffffffffffffff9c
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373388] RBP: 0000000000000000 R08: 0000000000000000 R09: 00007fc95a7bb000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373388] R10: 00000000000001b4 R11: 0000000000000293 R12: 00007fc9712f8880
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373389] R13: 00007fc95a8d4ec0 R14: 0000000000000000 R15: 0000000000000000
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373389] Code: b9 00 14 00 00 48 89 7d f0 eb 0a 0f 1f 00 db e2 0f 77 db 45 f0 0f 1f 44 00 00 b8 ff ff ff ff 89 c2 48 0f c7 1f 31 c0 85 c0 74 af <0f> ff eb ab 31 c0 48 0f ae 89 00 14 00 00 85 c0 74 9d 0f ff eb 
Oct 20 10:25:28 jmmk-B250M-DS3H kernel: [ 116.373404] ---[ end trace 1f94f12b6b3af23d ]---


Thanks!





ubuntu kernel kernel-panic





share|improve this question











share|improve this question




share|improve this question










asked Oct 20 '17 at 9:44









José María

1012




1012











  • Not sure what caused it from this trace. How can you be sure this is this is the exact cause of the freeze? Many times, upon kernel oops, there isn't enough time to flush the kernel log to disk and the backtrace seen in logs is some other which didn't actually cause oops. Also on a different note, current stable kernel is 4.13.8 so you can expect bugs in 4.13.0 :)
    – bytefire
    Oct 20 '17 at 10:08










  • @Okash Hm, I'm not exactly sure. But looking the times in the log it seems to me that it is.
    – José María
    Oct 20 '17 at 10:21










  • Looks like filesystem corruption, which could be a one-time thing or, if it happens frequently, could be due to bad RAM or SSD. Can you boot from a rescue disk and run fsck on every filesystem?
    – Mark Plotnick
    Oct 20 '17 at 17:14











  • @MarkPlotnick It's not the SSD. I tried on two SSD and one USB disk. The same problem happens on all of them. I also tried another memory module from a friend, so it's not the RAM.
    – José María
    Oct 22 '17 at 9:51

















  • Not sure what caused it from this trace. How can you be sure this is this is the exact cause of the freeze? Many times, upon kernel oops, there isn't enough time to flush the kernel log to disk and the backtrace seen in logs is some other which didn't actually cause oops. Also on a different note, current stable kernel is 4.13.8 so you can expect bugs in 4.13.0 :)
    – bytefire
    Oct 20 '17 at 10:08










  • @Okash Hm, I'm not exactly sure. But looking the times in the log it seems to me that it is.
    – José María
    Oct 20 '17 at 10:21










  • Looks like filesystem corruption, which could be a one-time thing or, if it happens frequently, could be due to bad RAM or SSD. Can you boot from a rescue disk and run fsck on every filesystem?
    – Mark Plotnick
    Oct 20 '17 at 17:14











  • @MarkPlotnick It's not the SSD. I tried on two SSD and one USB disk. The same problem happens on all of them. I also tried another memory module from a friend, so it's not the RAM.
    – José María
    Oct 22 '17 at 9:51
















Not sure what caused it from this trace. How can you be sure this is this is the exact cause of the freeze? Many times, upon kernel oops, there isn't enough time to flush the kernel log to disk and the backtrace seen in logs is some other which didn't actually cause oops. Also on a different note, current stable kernel is 4.13.8 so you can expect bugs in 4.13.0 :)
– bytefire
Oct 20 '17 at 10:08




Not sure what caused it from this trace. How can you be sure this is this is the exact cause of the freeze? Many times, upon kernel oops, there isn't enough time to flush the kernel log to disk and the backtrace seen in logs is some other which didn't actually cause oops. Also on a different note, current stable kernel is 4.13.8 so you can expect bugs in 4.13.0 :)
– bytefire
Oct 20 '17 at 10:08












@Okash Hm, I'm not exactly sure. But looking the times in the log it seems to me that it is.
– José María
Oct 20 '17 at 10:21




@Okash Hm, I'm not exactly sure. But looking the times in the log it seems to me that it is.
– José María
Oct 20 '17 at 10:21












Looks like filesystem corruption, which could be a one-time thing or, if it happens frequently, could be due to bad RAM or SSD. Can you boot from a rescue disk and run fsck on every filesystem?
– Mark Plotnick
Oct 20 '17 at 17:14





Looks like filesystem corruption, which could be a one-time thing or, if it happens frequently, could be due to bad RAM or SSD. Can you boot from a rescue disk and run fsck on every filesystem?
– Mark Plotnick
Oct 20 '17 at 17:14













@MarkPlotnick It's not the SSD. I tried on two SSD and one USB disk. The same problem happens on all of them. I also tried another memory module from a friend, so it's not the RAM.
– José María
Oct 22 '17 at 9:51





@MarkPlotnick It's not the SSD. I tried on two SSD and one USB disk. The same problem happens on all of them. I also tried another memory module from a friend, so it's not the RAM.
– José María
Oct 22 '17 at 9:51
















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399316%2fhelp-identifying-cause-of-linux-kernel-error%23new-answer', 'question_page');

);

Post as a guest






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















 

draft saved


draft discarded















































 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399316%2fhelp-identifying-cause-of-linux-kernel-error%23new-answer', 'question_page');

);

Post as a guest
































































-

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more