kernel.log and syslog keeps growing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Unknown
|
Unknown
|
|||
linux (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I noticed that my raspberry pi 4's boot drive is full and found out that the kernel.log and syslog is very big. Both always append this over and over again in the log files multiple times a second. I always truncate the content but this is a problem which come with the latest update 5.4.0-1011-raspi.
Didn't had the problems when I had 5.4.0-1008-raspi installed.
May 25 20:50:48 merts-pi kernel: [79846.673137] ------------[ cut here ]------------
May 25 20:50:48 merts-pi kernel: [79846.673159] WARNING: CPU: 2 PID: 281 at drivers/
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_
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_
May 25 20:50:48 merts-pi kernel: [79846.673234] lr : sdhci_prepare_
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_
May 25 20:50:48 merts-pi kernel: [79846.673280] sdhci_send_
May 25 20:50:48 merts-pi kernel: [79846.673282] sdhci_request+
May 25 20:50:48 merts-pi kernel: [79846.673286] __mmc_start_
May 25 20:50:48 merts-pi kernel: [79846.673289] mmc_start_
May 25 20:50:48 merts-pi kernel: [79846.673292] mmc_blk_
May 25 20:50:48 merts-pi kernel: [79846.673294] mmc_mq_
May 25 20:50:48 merts-pi kernel: [79846.673297] blk_mq_
May 25 20:50:48 merts-pi kernel: [79846.673301] blk_mq_
May 25 20:50:48 merts-pi kernel: [79846.673303] blk_mq_
May 25 20:50:48 merts-pi kernel: [79846.673306] __blk_mq_
May 25 20:50:48 merts-pi kernel: [79846.673308] blk_mq_
May 25 20:50:48 merts-pi kernel: [79846.673312] process_
May 25 20:50:48 merts-pi kernel: [79846.673314] worker_
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_
May 25 20:50:48 merts-pi kernel: [79846.673324] ---[ end trace 3f9a941cee68d128 ]---