Syslog läuft voll

german

#1

Hallo,
ich habe bei mehreren neu aufgesetzten UCCs mit neuer Hardware das Problem, dass das syslog voll läuft und damit auch die ganze Platte.
Was kann ich dagegen tun?
Es wird sekündlich geloggt:
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950267] WARNING: CPU: 1 PID: 0 at /build/linux-lts-utopic-zuu1pO/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:132 gen6_gt_ch$
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950278] GT wake FIFO error 0x1080000
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950285] Modules linked in: dm_crypt snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda$
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950542] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G W 3.16.0-53-generic #72~14.04.1-Ubuntu
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950553] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./N3150B-ITX, BIOS P1.20 06/02/2015
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950562] 00000000 00000000 f286de1c c168fd94 f286de5c f286de4c c105c44e f8322a96
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950594] f286de78 00000000 f83187e8 00000084 f82b9f11 f82b9f11 01080000 0001a074
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950626] f5408070 f286de64 c105c4a3 00000009 f286de5c f8322a96 f286de78 f286de84
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950659] Call Trace:
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950681] [] dump_stack+0x41/0x52
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950700] [] warn_slowpath_common+0x7e/0xa0
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.950857] [] ? gen6_gt_check_fifodbg.isra.10+0x41/0x50 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951005] [] ? gen6_gt_check_fifodbg.isra.10+0x41/0x50 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951025] [] warn_slowpath_fmt+0x33/0x40
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951177] [] gen6_gt_check_fifodbg.isra.10+0x41/0x50 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951339] [] __vlv_force_wake_put+0x37/0x40 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951487] [] gen6_read32+0xf5/0x100 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951636] [] ? gen6_read32+0x57/0x100 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951783] [] intel_ring_get_active_head+0x8f/0xd0 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951924] [] i915_hangcheck_elapsed+0xc5/0x400 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951945] [] ? intel_pstate_timer_func+0x322/0x4b0
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951965] [] ? update_blocked_averages+0x296/0x840
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.951986] [] call_timer_fn+0x30/0xf0
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952003] [] ? cascade+0x5f/0x80
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952143] [] ? cherryview_irq_handler+0xe0/0xe0 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952163] [] run_timer_softirq+0x174/0x280
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952304] [] ? cherryview_irq_handler+0xe0/0xe0 [i915]
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952325] [] __do_softirq+0xc3/0x230
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952345] [] ? cpu_callback+0x160/0x160
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952366] [] do_softirq_own_stack+0x22/0x30
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952375] [] irq_exit+0x95/0xa0
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952406] [] smp_apic_timer_interrupt+0x38/0x50
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952427] [] apic_timer_interrupt+0x34/0x3c
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952449] [] ? cpuidle_enter_state+0x3e/0xd0
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952468] [] cpuidle_enter+0x14/0x20
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952487] [] cpu_startup_entry+0x2bd/0x3c0
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952505] [] ? clockevents_register_device+0xaa/0x100
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952528] [] start_secondary+0x207/0x2e0
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952541] —[ end trace 3d9c3f135d230037 ]—
Jan 26 11:05:04 pkr-pc29 kernel: [ 2123.952769] ------------[ cut here ]------------


#2

Hallo,

ich würde es zunächst einmal mit einem neueren Kernel versuchen und schauen, ob das Problem dort behoben ist. Dazu können die Pakete
linux-generic-lts-vivid (Kernel 3.19) oder linux-generic-lts-wily (Kernel 4.2) testweise installiert werden. Standardmäßig wird bei UCC 2.1 der Kernel 3.16 aus utopic verwendet.


#3

Hallo,
danke, das hat geklappt. Bisher zeigen sich keine “Nebenwirkungen”.