Kernel panic on CentOS 7.5 update (862 kernel)

Issues related to hardware problems
Post Reply
collinsl
Posts: 4
Joined: 2018/05/27 11:19:07

Kernel panic on CentOS 7.5 update (862 kernel)

Post by collinsl » 2018/05/27 20:12:48

I've recently upgraded to 7.5 and have found my system keeps restarting randomly when using the new 3.10.0-862.2.3.el7.x86_64 kernel.

This doesn't happen on kernel 3.10.0-693.21.1.el7.x86_64 or below.

I think I've traced it to a bluetooth keyboard in my case (device ending 43:df:95):

[ 40.424633] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 40.424641] Bluetooth: HIDP socket layer initialized
[ 40.428582] hid-generic 0005:17EF:6048.0004: unknown main item tag 0x0
[ 40.466619] input: ThinkPad Compact Bluetooth Keyboard with TrackPoint as /devices/pci0000:00/0000:00:13.0/usb5/5-1/5-1:1.0/bluetooth/hci0/hci0:71/input12
[ 40.467235] hid-generic 0005:17EF:6048.0004: input,hidraw3: BLUETOOTH HID v3.12 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint] on 00:1a:7d:da:71:13
[ 54.162115] fuse init (API version 7.22)
[ 55.616969] Bluetooth: RFCOMM TTY layer initialized
[ 55.616982] Bluetooth: RFCOMM socket layer initialized
[ 55.616993] Bluetooth: RFCOMM ver 1.11
[ 58.641439] rfkill: input handler disabled
[ 1900.814150] power_supply hid-90:7f:61:43:df:95-battery: driver failed to report `capacity' property: -5
[ 1900.814177] power_supply hid-90:7f:61:43:df:95-battery: driver failed to report `capacity' property: -5
[ 1900.814216] BUG: unable to handle kernel NULL pointer dereference at (null)
[ 1900.814222] IP: [<ffffffffa077991e>] hidinput_disconnect+0x2e/0xb0
[ 1900.814233] PGD 542b5067 PUD 542b6067 PMD 0
[ 1900.814240] Oops: 0000 [#1] SMP
[ 1900.814245] Modules linked in: rfcomm fuse joydev hidp 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 ipt_REJECT nf_reject_ipv4 tun bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter devlink rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache cmac bnep nct6775 hwmon_vid sunrpc snd_hda_codec_realtek snd_hda_codec_generic edac_mce_amd kvm_amd snd_hda_intel kvm snd_hda_codec irqbypass btusb snd_hda_core btrtl snd_hwdep crc32_pclmul btbcm snd_seq btintel snd_seq_device bluetooth ppdev ghash_clmulni_intel snd_pcm aesni_intel lrw gf128mul glue_helper ablk_helper cryptd snd_timer snd sg pcspkr k10temp rfkill soundcore i2c_piix4 parport_pc parport shpchp
[ 1900.814338] video acpi_cpufreq binfmt_misc ip_tables xfs libcrc32c ata_generic sd_mod crc_t10dif amdkfd crct10dif_generic pata_acpi amd_iommu_v2 radeon i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm ahci crct10dif_pclmul crct10dif_common drm pata_atiixp libahci crc32c_intel serio_raw libata r8169 mii i2c_core dm_mirror dm_region_hash dm_log dm_mod
[ 1900.814385] CPU: 0 PID: 5419 Comm: khidpd_17ef6048 Kdump: loaded Not tainted 3.10.0-862.2.3.el7.x86_64 #1
[ 1900.814389] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./FM2A58M-HD+ R2.0, BIOS P1.20 08/01/2014
[ 1900.814393] task: ffff8e733b251fa0 ti: ffff8e7338d34000 task.ti: ffff8e7338d34000
[ 1900.814397] RIP: 0010:[<ffffffffa077991e>] [<ffffffffa077991e>] hidinput_disconnect+0x2e/0xb0
[ 1900.814404] RSP: 0018:ffff8e7338d37c60 EFLAGS: 00010246
[ 1900.814408] RAX: 0000000000000000 RBX: ffff8e737a93e000 RCX: 000000018080007d
[ 1900.814412] RDX: 000000018080007e RSI: fffff4e2845ca240 RDI: 0000000040000000
[ 1900.814415] RBP: ffff8e7338d37c80 R08: ffff8e73d72894e0 R09: 000000018080007d
[ 1900.814419] R10: 00000000d7289501 R11: fffff4e2845ca240 R12: ffff8e737a93f8e8
[ 1900.814422] R13: ffff8e737a93e000 R14: ffff8e737a93e000 R15: ffff8e737a93f8d0
[ 1900.814427] FS: 00007f7e7972ea80(0000) GS:ffff8e73dec00000(0000) knlGS:0000000000000000
[ 1900.814431] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 1900.814434] CR2: 0000000000000000 CR3: 00000000542c2000 CR4: 00000000000407f0
[ 1900.814438] Call Trace:
[ 1900.814447] [<ffffffffa0775fa8>] hid_disconnect+0x88/0x90
[ 1900.814453] [<ffffffffa077606d>] hid_device_remove+0xbd/0xd0
[ 1900.814461] [<ffffffffa0672dc2>] __device_release_driver+0x82/0xf0
[ 1900.814467] [<ffffffffa0672e53>] device_release_driver+0x23/0x30
[ 1900.814474] [<ffffffffa067251b>] bus_remove_device+0x10b/0x180
[ 1900.814480] [<ffffffffa066e43a>] device_del+0x13a/0x210
[ 1900.814486] [<ffffffffa0776107>] hid_destroy_device+0x27/0x60
[ 1900.814495] [<ffffffffc0e74b12>] hidp_session_remove+0x52/0xb0 [hidp]
[ 1900.814535] [<ffffffffc089a4ad>] l2cap_unregister_user+0x4d/0x60 [bluetooth]
[ 1900.814543] [<ffffffffc0e74538>] hidp_session_thread+0x458/0x970 [hidp]
[ 1900.814552] [<ffffffffa02cee80>] ? wake_up_state+0x20/0x20
[ 1900.814558] [<ffffffffa02cee80>] ? wake_up_state+0x20/0x20
[ 1900.814565] [<ffffffffc0e740e0>] ? hidp_copy_session+0x190/0x190 [hidp]
[ 1900.814572] [<ffffffffa02bae31>] kthread+0xd1/0xe0
[ 1900.814580] [<ffffffffa02bad60>] ? insert_kthread_work+0x40/0x40
[ 1900.814587] [<ffffffffa091f5e4>] ret_from_fork_nospec_begin+0xe/0x21
[ 1900.814595] [<ffffffffa02bad60>] ? insert_kthread_work+0x40/0x40
[ 1900.814598] Code: 66 90 55 48 89 e5 41 56 49 89 fe 41 55 41 54 53 48 8b bf 98 1b 00 00 48 85 ff 74 31 e8 5c 23 fc ff 49 8b 86 98 1b 00 00 48 8b 00 <48> 8b 38 e8 5a d1 c7 ff 49 8b 86 98 1b 00 00 48 8b 38 e8 4b d1
[ 1900.814661] RIP [<ffffffffa077991e>] hidinput_disconnect+0x2e/0xb0
[ 1900.814667] RSP <ffff8e7338d37c60>
[ 1900.814670] CR2: 0000000000000000

Can anyone assist please?

User avatar
TrevorH
Forum Moderator
Posts: 23871
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Kernel panic on CentOS 7.5 update (862 kernel)

Post by TrevorH » 2018/05/28 12:06:19

This looks like a bug that needs to be reported to RH via bugzilla.redhat.com (search first, it may well already have been reported). One thing that does occur to me is that it would appear to be during a disconnect/connect and it's talking about power just before so I'd certainly try the obvious and replace the battery in the keyboard and see if that helps (I don't think it will fix it but it might make it less easy to trigger). Otherwise I suspect your only other alternative is to backlevel the kernel to the last 7.4 one until it gets fixed.
CentOS 5 died in March 2017 - migrate NOW!
Full time Geek, part time moderator. Use the FAQ Luke

collinsl
Posts: 4
Joined: 2018/05/27 11:19:07

Re: Kernel panic on CentOS 7.5 update (862 kernel)

Post by collinsl » 2018/05/28 16:19:06

Thanks for the suggestion - the keyboard itself is a wireless bluetooth keyboard from Lenovo which has a non-replaceable battery inside, it's charged via USB.

It "sleeps" after a period of inactivity and can be "woken" and reconnected by pressing a key, so that may well be the cause

I'll report it up to RedHat. Thanks.

Post Reply