View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0005544Kali LinuxGeneral Bugpublic2019-06-14 20:222020-02-10 17:38
Reportermyk Assigned To 
PrioritynormalSeveritycrashReproducibilityhave not tried
Status closedResolutionopen 
Product Version2019.2 
Summary0005544: 0010:r852_irq+0x160/0x200 [r852] errors cause log files to grow HUGE
Description

Recently i noticed some log files growing in size at a high rate. This files are;

/var/log/syslog
/var/log/kern.log
/var/log/messages

checked the process that was generating the error logs and found a recurring error by r852. The screenshots are attached below.

Running tail -f /var/log/syslog, tail -f /var/log/kern.log, and /var/log/messages all give the same output, and are growing at the same rate.

How do i stop this from growing that huge that fast? it has caused my system to crash twice in one day.

Additional Information

example:
command: tail -f /var/log/syslog

root@angry-it:~# tail -f /var/log/syslog
Jun 14 20:07:35 angry-it kernel: [12424.254343] RDX: 00000b4cbf40983c RSI: 00000b4cbf4097d6 RDI: 0000000000000000
Jun 14 20:07:35 angry-it kernel: [12424.254344] RBP: ffffa0223a0f7000 R08: ffffffffffc2f72a R09: 00000000000214c0
Jun 14 20:07:35 angry-it kernel: [12424.254346] R10: 000006a3426cc794 R11: ffffa0223ba20be8 R12: 0000000000000003
Jun 14 20:07:35 angry-it kernel: [12424.254347] R13: ffffffff93aba298 R14: 0000000000000003 R15: 0000000000000000
Jun 14 20:07:35 angry-it kernel: [12424.254352] do_idle+0x236/0x280
Jun 14 20:07:35 angry-it kernel: [12424.254354] cpu_startup_entry+0x6f/0x80
Jun 14 20:07:35 angry-it kernel: [12424.254358] start_kernel+0x511/0x531
Jun 14 20:07:35 angry-it kernel: [12424.254363] secondary_startup_64+0xa4/0xb0
Jun 14 20:07:35 angry-it kernel: [12424.254365] ---[ end trace d1d98fded3425dd9 ]---
Jun 14 20:07:35 angry-it systemd[1120]: tracker-extract.service: Succeeded.

Jun 14 20:18:34 angry-it kernel: [13083.506440] RIP: 0010:r852_irq+0x160/0x200 [r852]
Jun 14 20:18:34 angry-it kernel: [13083.506442] Code: 8b 35 14 2d 00 00 85 f6 74 05 66 66 66 66 90 be fb ff ff ff 48 89 df e8 fe fd ff ff 48 8d 7b 20 e8 75 32 36 d2 e9 02 ff ff ff <0f> 0b e9 e5 fe ff ff 48 8b b3 c0 00 00 00 48 8d 53 68 b9 19 00 00
Jun 14 20:18:34 angry-it kernel: [13083.506447] RSP: 0018:ffffa0223ba03ef0 EFLAGS: 00010002
Jun 14 20:18:34 angry-it kernel: [13083.506449] RAX: 0000000000000001 RBX: ffffa0222efca900 RCX: 0000000000000000
Jun 14 20:18:34 angry-it kernel: [13083.506451] RDX: ffffba5fc089d400 RSI: ffffa0222efca900 RDI: ffffa0222efca9dc
Jun 14 20:18:34 angry-it kernel: [13083.506452] RBP: ffffa0222efca9dc R08: 0000000000000001 R09: 0000000000000002
Jun 14 20:18:34 angry-it kernel: [13083.506454] R10: ffffa02135044218 R11: ffffa0223ab1cbb8 R12: 0000000000000082
Jun 14 20:18:34 angry-it kernel: [13083.506455] R13: ffffa0223ba03f5c R14: 0000000000000000 R15: 0000000000000000
Jun 14 20:18:34 angry-it kernel: [13083.506458] FS: 0000000000000000(0000) GS:ffffa0223ba00000(0000) knlGS:0000000000000000
Jun 14 20:18:34 angry-it kernel: [13083.506459] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 14 20:18:34 angry-it kernel: [13083.506461] CR2: 000022a713057000 CR3: 0000000105a0a000 CR4: 00000000000006f0
Jun 14 20:18:34 angry-it kernel: [13083.506462] Call Trace:
Jun 14 20:18:34 angry-it kernel: [13083.506466] <IRQ>
Jun 14 20:18:34 angry-it kernel: [13083.506473] __handle_irq_event_percpu+0x46/0x190
Jun 14 20:18:34 angry-it kernel: [13083.506476] handle_irq_event_percpu+0x30/0x80
Jun 14 20:18:34 angry-it kernel: [13083.506478] handle_irq_event+0x3c/0x5c
Jun 14 20:18:34 angry-it kernel: [13083.506481] handle_fasteoi_irq+0x9c/0x160
Jun 14 20:18:34 angry-it kernel: [13083.506485] handle_irq+0x1f/0x30
Jun 14 20:18:34 angry-it kernel: [13083.506489] do_IRQ+0x49/0xd0
Jun 14 20:18:34 angry-it kernel: [13083.506492] common_interrupt+0xf/0xf
Jun 14 20:18:34 angry-it kernel: [13083.506494] </IRQ>
Jun 14 20:18:34 angry-it kernel: [13083.506497] RIP: 0010:cpuidle_enter_state+0xb6/0x320
Jun 14 20:18:34 angry-it kernel: [13083.506500] Code: 90 31 ff e8 ac 78 b1 ff 80 7c 24 0b 00 74 17 9c 58 66 66 90 66 90 f6 c4 02 0f 85 3b 02 00 00 31 ff e8 2e 52 b7 ff fb 66 66 90 <66> 66 90 48 b8 ff ff ff ff f3 01 00 00 48 2b 1c 24 ba ff ff ff 7f
Jun 14 20:18:34 angry-it kernel: [13083.506501] RSP: 0018:ffffffff93a03e70 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffda
Jun 14 20:18:34 angry-it kernel: [13083.506503] RAX: ffffa0223ba21c00 RBX: 00000be63dbdcc5b RCX: 00000be63dbdcc5b
Jun 14 20:18:34 angry-it kernel: [13083.506505] RDX: 00000be63dbdcc5b RSI: 00000be63dbdcbe8 RDI: 0000000000000000
Jun 14 20:18:34 angry-it kernel: [13083.506506] RBP: ffffa0223a0f7000 R08: ffffffffffc2f736 R09: 00000000000214c0
Jun 14 20:18:34 angry-it kernel: [13083.506508] R10: 000007367853cb28 R11: ffffa0223ba20be8 R12: 0000000000000003
Jun 14 20:18:34 angry-it kernel: [13083.506509] R13: ffffffff93aba298 R14: 0000000000000003 R15: 0000000000000000
Jun 14 20:18:34 angry-it kernel: [13083.506514] do_idle+0x236/0x280
Jun 14 20:18:34 angry-it kernel: [13083.506517] cpu_startup_entry+0x6f/0x80
Jun 14 20:18:34 angry-it kernel: [13083.506521] start_kernel+0x511/0x531
Jun 14 20:18:34 angry-it kernel: [13083.506526] secondary_startup_64+0xa4/0xb0
Jun 14 20:18:34 angry-it kernel: [13083.506529] ---[ end trace d1d98fded342a143 ]---

Jun 14 20:18:34 angry-it kernel: [13083.614317] WARNING: CPU: 0 PID: 0 at drivers/mtd/nand/raw/r852.c:746 r852_irq+0x160/0x200 [r852]
Jun 14 20:18:34 angry-it kernel: [13083.614320] Modules linked in: ctr ccm ppdev parport_pc parport fuse vmw_vsock_vmcitransport vsock vmw
vmci uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_hda_codec_si3054 snd_hda_codec_realtek arc4 me
dia snd_hda_codec_generic snd_hda_intel snd_hda_codec iwl4965 snd_hda_core snd_hwdep snd_pcm iwlegacy r852 snd_timer sm_common mac80211 i915
snd nand r592 soundcore cfg80211 nand_ecc nand_bch drm_kms_helper hp_wmi sparse_keymap joydev evdev bch wmi_bmof mtd rfkill memstick drm se
rio_raw sg pcspkr i2c_algo_bit coretemp wmi iTCO_wdt iTCO_vendor_support video button pcc_cpufreq battery ac acpi_cpufreq binfmt_misc firewi
re_sbp2 ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic fscrypto ecb crypto_simd cryptd glue_helper aes_x86_64 hid_generic
usbhid
Jun 14 20:18:34 angry-it kernel: [13083.614387] hid sr_mod cdrom sd_mod ata_generic ahci ata_piix libahci libata lpc_ich scsi_mod psmouse s
dhci_pci cqhci sdhci i2c_i801 mmc_core firewire_ohci firewire_core crc_itu_t r8169 realtek libphy ehci_pci uhci_hcd ehci_hcd usbcore usb_com
mon thermal
Jun 14 20:18:34 angry-it kernel: [13083.614417] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G W 4.19.0-kali4-amd64 0000001 Debian 4.19.
28-2kali1

Attached Files
Screenshot-20190614200930-1057x436.png (382,507 bytes)
Screenshot-20190614200458-1266x671.png (629,323 bytes)

Activities

g0tmi1k

g0tmi1k

2020-02-10 17:38

administrator   ~0012110

Due to the age of the OS (Kali Moto [v1], Kali Safi [v2], Kali Rolling <= 2019.2), these legacy versions are no longer supported.
We will be closing this ticket due to inactivity.

Please could you see if you are able to replicate this issue with the latest version of Kali Linux - https://www.kali.org/downloads/?

If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup?
For more information, please read: https://kali.training/topic/filing-a-good-bug-report/

Issue History

Date Modified Username Field Change
2019-06-14 20:22 myk New Issue
2019-06-14 20:22 myk File Added: Screenshot-20190614200930-1057x436.png
2019-06-14 20:22 myk File Added: Screenshot-20190614200458-1266x671.png
2020-02-10 17:38 g0tmi1k Note Added: 0012110
2020-02-10 17:38 g0tmi1k Status new => closed