This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1880772

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Tags added: focal

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1880772

Title:
  5.4.0-1011-raspi flooding kernel.log and syslog with failed driver
  events

Status in linux-raspi package in Ubuntu:
  New

Bug description:
  As described here (this is not my post):
  
https://askubuntu.com/questions/1242733/kern-log-and-syslog-growing-uncontrollably-with-details

  The new kernel flooding the kernel.log and syslog files rapidly until
  there is no more space and sometimes make the raspberry pi
  unresponsive. I just downgraded and hold the 5.4.0-1008-raspi kernel
  until the bug has been fixed.

  This issue is really critical for me and others.

  I truncate the files in order to keep my system running normally but
  they reach the Gb mark in minutes. I attached both syslog and
  kernel.log in a trimmed version.

  kernel.log:

  May 25 20:50:48 merts-pi kernel: [79846.673159] WARNING: CPU: 2 PID: 281 at 
drivers/mmc/host/sdhci.c:1101 sdhci_prepare_data+0x3dc/0x7b0
  May 25 20:50:48 merts-pi kernel: [79846.673161] Modules linked in: 
binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth 
ecdh_generic ecc brcmfmac bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) brcmutil 
videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 videobuf2_common 
videodev snd_bcm2835(CE) mc snd_pcm snd_timer vc_sm_cma(CE) snd 
raspberrypi_hwmon rpivid_mem uio_pdrv_genirq uio sch_fq_codel sunrpc drm 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear crct10dif_ce spidev phy_generic uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd
  May 25 20:50:48 merts-pi kernel: [79846.673212] CPU: 2 PID: 281 Comm: 
kworker/2:1H Tainted: G        WC  E     5.4.0-1011-raspi #11-Ubuntu
  May 25 20:50:48 merts-pi kernel: [79846.673214] Hardware name: Raspberry Pi 4 
Model B Rev 1.1 (DT)
  May 25 20:50:48 merts-pi kernel: [79846.673223] Workqueue: kblockd 
blk_mq_run_work_fn
  May 25 20:50:48 merts-pi kernel: [79846.673228] pstate: a0400085 (NzCv daIf 
+PAN -UAO)
  May 25 20:50:48 merts-pi kernel: [79846.673231] pc : 
sdhci_prepare_data+0x3dc/0x7b0
  May 25 20:50:48 merts-pi kernel: [79846.673234] lr : 
sdhci_prepare_data+0x2cc/0x7b0
  May 25 20:50:48 merts-pi kernel: [79846.673235] sp : ffff800010eb39b0
  May 25 20:50:48 merts-pi kernel: [79846.673237] x29: ffff800010eb39b0 x28: 
ffff0000eb734000 
  May 25 20:50:48 merts-pi kernel: [79846.673240] x27: 0000000000000001 x26: 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673243] x25: ffff0000f63d1000 x24: 
ffff0000f63d1580 
  May 25 20:50:48 merts-pi kernel: [79846.673245] x23: 0000000000418958 x22: 
ffff0000eb03b498 
  May 25 20:50:48 merts-pi kernel: [79846.673247] x21: ffff0000f6193b80 x20: 
ffff0000eb03b518 
  May 25 20:50:48 merts-pi kernel: [79846.673250] x19: ffff0000f63d1580 x18: 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673252] x17: 0000000000000000 x16: 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673254] x15: 0000000000000000 x14: 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673256] x13: ffff0000fb74d000 x12: 
00000000001fffff 
  May 25 20:50:48 merts-pi kernel: [79846.673259] x11: 0000000000000003 x10: 
0000000000008000 
  May 25 20:50:48 merts-pi kernel: [79846.673261] x9 : 0000000000000080 x8 : 
0000000000000002 
  May 25 20:50:48 merts-pi kernel: [79846.673263] x7 : 000000003a600000 x6 : 
ffffd33c9ee09a44 
  May 25 20:50:48 merts-pi kernel: [79846.673266] x5 : ffffffffffffffff x4 : 
0000000000000020 
  May 25 20:50:48 merts-pi kernel: [79846.673268] x3 : 0000000000000002 x2 : 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673270] x1 : ffff0000eb07f000 x0 : 
00000000ffffffe4 
  May 25 20:50:48 merts-pi kernel: [79846.673273] Call trace:
  May 25 20:50:48 merts-pi kernel: [79846.673277]  
sdhci_prepare_data+0x3dc/0x7b0
  May 25 20:50:48 merts-pi kernel: [79846.673280]  sdhci_send_command+0xe0/0x5f0
  May 25 20:50:48 merts-pi kernel: [79846.673282]  sdhci_request+0x110/0x150
  May 25 20:50:48 merts-pi kernel: [79846.673286]  
__mmc_start_request+0x88/0x1a8
  May 25 20:50:48 merts-pi kernel: [79846.673289]  mmc_start_request+0x98/0xc0
  May 25 20:50:48 merts-pi kernel: [79846.673292]  
mmc_blk_mq_issue_rq+0x30c/0x778
  May 25 20:50:48 merts-pi kernel: [79846.673294]  mmc_mq_queue_rq+0x14c/0x320
  May 25 20:50:48 merts-pi kernel: [79846.673297]  
blk_mq_dispatch_rq_list+0xa4/0x5f8
  May 25 20:50:48 merts-pi kernel: [79846.673301]  
blk_mq_do_dispatch_sched+0x68/0x108
  May 25 20:50:48 merts-pi kernel: [79846.673303]  
blk_mq_sched_dispatch_requests+0x164/0x1c0
  May 25 20:50:48 merts-pi kernel: [79846.673306]  
__blk_mq_run_hw_queue+0xfc/0x158
  May 25 20:50:48 merts-pi kernel: [79846.673308]  blk_mq_run_work_fn+0x28/0x38
  May 25 20:50:48 merts-pi kernel: [79846.673312]  process_one_work+0x1d0/0x430
  May 25 20:50:48 merts-pi kernel: [79846.673314]  worker_thread+0x54/0x4a0
  May 25 20:50:48 merts-pi kernel: [79846.673318]  kthread+0xfc/0x128
  May 25 20:50:48 merts-pi kernel: [79846.673322]  ret_from_fork+0x10/0x1c
  May 25 20:50:48 merts-pi kernel: [79846.673324] ---[ end trace 
3f9a941cee68d128 ]---

  syslog:

  May 25 20:50:48 merts-pi kernel: [79846.673159] WARNING: CPU: 2 PID: 281 at 
drivers/mmc/host/sdhci.c:1101 sdhci_prepare_data+0x3dc/0x7b0
  May 25 20:50:48 merts-pi kernel: [79846.673161] Modules linked in: 
binfmt_misc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua btsdio bluetooth 
ecdh_generic ecc brcmfmac bcm2835_v4l2(CE) bcm2835_mmal_vchiq(CE) brcmutil 
videobuf2_vmalloc cfg80211 videobuf2_memops videobuf2_v4l2 videobuf2_common 
videodev snd_bcm2835(CE) mc snd_pcm snd_timer vc_sm_cma(CE) snd 
raspberrypi_hwmon rpivid_mem uio_pdrv_genirq uio sch_fq_codel sunrpc drm 
ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 
raid0 multipath linear crct10dif_ce spidev phy_generic uas usb_storage 
aes_neon_bs aes_neon_blk crypto_simd cryptd
  May 25 20:50:48 merts-pi kernel: [79846.673212] CPU: 2 PID: 281 Comm: 
kworker/2:1H Tainted: G        WC  E     5.4.0-1011-raspi #11-Ubuntu
  May 25 20:50:48 merts-pi kernel: [79846.673214] Hardware name: Raspberry Pi 4 
Model B Rev 1.1 (DT)
  May 25 20:50:48 merts-pi kernel: [79846.673223] Workqueue: kblockd 
blk_mq_run_work_fn
  May 25 20:50:48 merts-pi kernel: [79846.673228] pstate: a0400085 (NzCv daIf 
+PAN -UAO)
  May 25 20:50:48 merts-pi kernel: [79846.673231] pc : 
sdhci_prepare_data+0x3dc/0x7b0
  May 25 20:50:48 merts-pi kernel: [79846.673234] lr : 
sdhci_prepare_data+0x2cc/0x7b0
  May 25 20:50:48 merts-pi kernel: [79846.673235] sp : ffff800010eb39b0
  May 25 20:50:48 merts-pi kernel: [79846.673237] x29: ffff800010eb39b0 x28: 
ffff0000eb734000 
  May 25 20:50:48 merts-pi kernel: [79846.673240] x27: 0000000000000001 x26: 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673243] x25: ffff0000f63d1000 x24: 
ffff0000f63d1580 
  May 25 20:50:48 merts-pi kernel: [79846.673245] x23: 0000000000418958 x22: 
ffff0000eb03b498 
  May 25 20:50:48 merts-pi kernel: [79846.673247] x21: ffff0000f6193b80 x20: 
ffff0000eb03b518 
  May 25 20:50:48 merts-pi kernel: [79846.673250] x19: ffff0000f63d1580 x18: 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673252] x17: 0000000000000000 x16: 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673254] x15: 0000000000000000 x14: 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673256] x13: ffff0000fb74d000 x12: 
00000000001fffff 
  May 25 20:50:48 merts-pi kernel: [79846.673259] x11: 0000000000000003 x10: 
0000000000008000 
  May 25 20:50:48 merts-pi kernel: [79846.673261] x9 : 0000000000000080 x8 : 
0000000000000002 
  May 25 20:50:48 merts-pi kernel: [79846.673263] x7 : 000000003a600000 x6 : 
ffffd33c9ee09a44 
  May 25 20:50:48 merts-pi kernel: [79846.673266] x5 : ffffffffffffffff x4 : 
0000000000000020 
  May 25 20:50:48 merts-pi kernel: [79846.673268] x3 : 0000000000000002 x2 : 
0000000000000000 
  May 25 20:50:48 merts-pi kernel: [79846.673270] x1 : ffff0000eb07f000 x0 : 
00000000ffffffe4 
  May 25 20:50:48 merts-pi kernel: [79846.673273] Call trace:
  May 25 20:50:48 merts-pi kernel: [79846.673277]  
sdhci_prepare_data+0x3dc/0x7b0
  May 25 20:50:48 merts-pi kernel: [79846.673280]  sdhci_send_command+0xe0/0x5f0
  May 25 20:50:48 merts-pi kernel: [79846.673282]  sdhci_request+0x110/0x150
  May 25 20:50:48 merts-pi kernel: [79846.673286]  
__mmc_start_request+0x88/0x1a8
  May 25 20:50:48 merts-pi kernel: [79846.673289]  mmc_start_request+0x98/0xc0
  May 25 20:50:48 merts-pi kernel: [79846.673292]  
mmc_blk_mq_issue_rq+0x30c/0x778
  May 25 20:50:48 merts-pi kernel: [79846.673294]  mmc_mq_queue_rq+0x14c/0x320
  May 25 20:50:48 merts-pi kernel: [79846.673297]  
blk_mq_dispatch_rq_list+0xa4/0x5f8
  May 25 20:50:48 merts-pi kernel: [79846.673301]  
blk_mq_do_dispatch_sched+0x68/0x108
  May 25 20:50:48 merts-pi kernel: [79846.673303]  
blk_mq_sched_dispatch_requests+0x164/0x1c0
  May 25 20:50:48 merts-pi kernel: [79846.673306]  
__blk_mq_run_hw_queue+0xfc/0x158
  May 25 20:50:48 merts-pi kernel: [79846.673308]  blk_mq_run_work_fn+0x28/0x38
  May 25 20:50:48 merts-pi kernel: [79846.673312]  process_one_work+0x1d0/0x430
  May 25 20:50:48 merts-pi kernel: [79846.673314]  worker_thread+0x54/0x4a0
  May 25 20:50:48 merts-pi kernel: [79846.673318]  kthread+0xfc/0x128
  May 25 20:50:48 merts-pi kernel: [79846.673322]  ret_from_fork+0x10/0x1c
  May 25 20:50:48 merts-pi kernel: [79846.673324] ---[ end trace 
3f9a941cee68d128 ]---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880772/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to