Bluetooth occurs: Internal error: Oops: 207 [#1] SMP ARM #3494
Comments
|
Please include the whole stack trace - everything between the start and end lines. |
|
I have similar problem with TP-Link UB400 BT dongle. After some times the dongle stops working and in logs is: Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... Message from syslogd@rpi at Apr 30 14:59:39 ... My configuration: Pi4B 4GB Which OS and version (cat /etc/rpi-issue)? Which firmware version (vcgencmd version)? Which kernel version (uname -a)? |
|
And also: Apr 30 09:52:51 rpi kernel: [56353.481787] Unable to handle kernel NULL pointer dereference at virtual address 00000012 |
|
I saw this message as well. Wifi didn't work even if I set country in wpa_supplicant.conf file. |
|
Same problem. Stack trace:
|
|
Same problem, reconnecting a bluetooth keyboard: Jan 15 18:51:07 4GB kernel: [435222.428754] Unable to handle kernel NULL pointer dereference at virtual address 00000100 |
We got issue as follows: [home]# fsck.ext4 -fn ram0yb e2fsck 1.45.6 (20-Mar-2020) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Symlink /p3/d14/d1a/l3d (inode #3494) is invalid. Clear? no Entry 'l3d' in /p3/d14/d1a (3383) has an incorrect filetype (was 7, should be 0). Fix? no As the symlink file size does not match the file content. If the writeback of the symlink data block failed, ext4_finish_bio() handles the end of IO. However this function fails to mark the buffer with BH_write_io_error and so when unmount does journal checkpoint it cannot detect the writeback error and will cleanup the journal. Thus we've lost the correct data in the journal area. To solve this issue, mark the buffer as BH_write_io_error in ext4_finish_bio(). Cc: [email protected] Signed-off-by: Ye Bin <[email protected]> Reviewed-by: Jan Kara <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Theodore Ts'o <[email protected]>
commit a2b0b20 upstream. We got issue as follows: [home]# fsck.ext4 -fn ram0yb e2fsck 1.45.6 (20-Mar-2020) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Symlink /p3/d14/d1a/l3d (inode raspberrypi#3494) is invalid. Clear? no Entry 'l3d' in /p3/d14/d1a (3383) has an incorrect filetype (was 7, should be 0). Fix? no As the symlink file size does not match the file content. If the writeback of the symlink data block failed, ext4_finish_bio() handles the end of IO. However this function fails to mark the buffer with BH_write_io_error and so when unmount does journal checkpoint it cannot detect the writeback error and will cleanup the journal. Thus we've lost the correct data in the journal area. To solve this issue, mark the buffer as BH_write_io_error in ext4_finish_bio(). Cc: [email protected] Signed-off-by: Ye Bin <[email protected]> Reviewed-by: Jan Kara <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Theodore Ts'o <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit a2b0b20 upstream. We got issue as follows: [home]# fsck.ext4 -fn ram0yb e2fsck 1.45.6 (20-Mar-2020) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Symlink /p3/d14/d1a/l3d (inode #3494) is invalid. Clear? no Entry 'l3d' in /p3/d14/d1a (3383) has an incorrect filetype (was 7, should be 0). Fix? no As the symlink file size does not match the file content. If the writeback of the symlink data block failed, ext4_finish_bio() handles the end of IO. However this function fails to mark the buffer with BH_write_io_error and so when unmount does journal checkpoint it cannot detect the writeback error and will cleanup the journal. Thus we've lost the correct data in the journal area. To solve this issue, mark the buffer as BH_write_io_error in ext4_finish_bio(). Cc: [email protected] Signed-off-by: Ye Bin <[email protected]> Reviewed-by: Jan Kara <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Theodore Ts'o <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
commit a2b0b20 upstream. We got issue as follows: [home]# fsck.ext4 -fn ram0yb e2fsck 1.45.6 (20-Mar-2020) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Symlink /p3/d14/d1a/l3d (inode raspberrypi#3494) is invalid. Clear? no Entry 'l3d' in /p3/d14/d1a (3383) has an incorrect filetype (was 7, should be 0). Fix? no As the symlink file size does not match the file content. If the writeback of the symlink data block failed, ext4_finish_bio() handles the end of IO. However this function fails to mark the buffer with BH_write_io_error and so when unmount does journal checkpoint it cannot detect the writeback error and will cleanup the journal. Thus we've lost the correct data in the journal area. To solve this issue, mark the buffer as BH_write_io_error in ext4_finish_bio(). Cc: [email protected] Signed-off-by: Ye Bin <[email protected]> Reviewed-by: Jan Kara <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Theodore Ts'o <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
|
Same happpend here, command was: dmesg says: Only rebooting fixes bluetooth connections again. |
Is this the right place for my bug report?
Yes, the error starts with:
raspberrypi kernel: [ 4188.416710] Unable to handle kernel NULL pointer dereference at virtual address 00000100Describe the bug
This error occurs when connecting with my bluetooth keyboard incl. trackpad and the Raspberry Pi 4. The error doesn't occur with every connection establishment (approximately after 50 connects and disconnects).
It affects bluetooth (hidp, rfcomm, hci ... ).
To reproduce
System
Copy and paste the results of the raspinfo command in to this section. Alternatively, copy and paste a pastebin link, or add answers to the following questions:
Which model of Raspberry Pi? e.g. Pi3B+, PiZeroW
Pi4B 4GB
Which OS and version (
cat /etc/rpi-issue)?Raspberry Pi reference 2019-09-26
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen,
80d486687ea77d31fc3fc13cf3a2f8b464e129be, stage4
Which firmware version (
vcgencmd version)?Feb 12 2020 12:36:21
Copyright (c) 2012 Broadcom
version c3c8dbdf147686fb0c3f32aece709d0653368810 (clean) (release) (start)
Which kernel version (
uname -a)?Linux raspberrypi 4.19.97-v7l+ problem with device tree overlay at86rf233 #1294 SMP Thu Jan 30 13:21:14 GMT 2020
armv7l GNU/Linux
Logs
If applicable, add the relevant output from
dmesgor similar.Mar 8 21:48:51 raspberrypi kernel: [ 4188.416710] Unable to handle kernel NULL pointer dereference at virtual address 00000100 Mar 8 21:48:51 raspberrypi kernel: [ 4188.416732] pgd = 024205b4 Mar 8 21:48:51 raspberrypi kernel: [ 4188.416743] [00000100] *pgd=80000000004003, *pmd=00000000 Mar 8 21:48:51 raspberrypi kernel: [ 4188.416761] Internal error: Oops: 207 [#1] SMP ARM Mar 8 21:48:51 raspberrypi kernel: [ 4188.416772] Modules linked in: hidp rfcomm bnep hci_uart btbcm serdev bluetooth ecdh_generic fuse 8021q garp stp llc evdev sg snd_usb_audio snd_hwdep uvcvideo snd_usbmidi_lib snd_rawmidi snd_seq_device vc4 brcmfmac brcmutil sha256_generic drm_kms_helper v3d snd_soc_core snd_compress gpu_sched snd_pcm_dmaengine bcm2835_v4l2(C) bcm2835_codec(C) v4l2_mem2mem snd_bcm2835(C) bcm2835_mmal_vchiq(C) snd_pcm cfg80211 v4l2_common drm snd_timer raspberrypi_hwmon rfkill hwmon syscopyarea drm_panel_orientation_quirks videobuf2_dma_contig sysfillrect sysimgblt fb_sys_fops snd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media vc_sm_cma(C) rpivid_mem uio_pdrv_genirq uio i2c_dev ip_tables x_tables ipv6 Mar 8 21:48:51 raspberrypi kernel: [ 4188.416923] CPU: 3 PID: 10046 Comm: kworker/u9:2 Tainted: G C 4.19.97-v7l+ #1294 Mar 8 21:48:51 raspberrypi kernel: [ 4188.416934] Hardware name: BCM2835 Mar 8 21:48:51 raspberrypi kernel: [ 4188.417035] Workqueue: hci0 hci_rx_work [bluetooth] Mar 8 21:48:51 raspberrypi kernel: [ 4188.417060] PC is at __wake_up_common+0x6c/0x144 Mar 8 21:48:51 raspberrypi kernel: [ 4188.417077] LR is at _raw_spin_unlock_irqrestore+0x6c/0x70The text was updated successfully, but these errors were encountered: