|
[GELÖST] syslog und Kernel-Log laufen voll
|
easyVDR - >VARforumsname - >[GELÖST] syslog und Kernel-Log laufen voll
| olsvse 18.Aug.2016 11:52:10 |
Hallo Zusammen,
momentan läuft mir meine Fest-Platte ständig voll.
Ich bekomme immer folgende Meldung:
Aug 18 11:49:23 easyvdr kernel: [ 4605.879567] ------------------------
Aug 18 11:49:23 easyvdr kernel: [ 4605.879599] WARNING: CPU: 0 PID: 2730 at /build/linux-lts-utopic-baiXlt/linux-lts-utopic-3.16.0/drivers/gpu/drm/i915/intel_uncore.c:132 gen6_gt_check_fifodbg.isra.10+0x3d/0x50 ()
Aug 18 11:49:23 easyvdr kernel: [ 4605.879609] GT wake FIFO error 0x1080000
Aug 18 11:49:23 easyvdr kernel: [ 4605.879619] Modules linked in: st joydev autofs4 stv6110x(OE) lnbp21(OE) snd_hda_codec_hdmi nfsd snd_hda_codec_realtek auth_rpcgss snd_hda_codec_generic nfs_acl ir_xmp_decoder(OE) nfs ir_lirc_codec(OE) lirc_dev(OE) ir_mce_kbd_decoder(OE) ir_sharp_decoder(OE) lockd snd_hda_intel ir_sanyo_decoder(OE) snd_hda_controller ir_sony_decoder(OE) sunrpc ir_jvc_decoder(OE) ir_nec_decoder(OE) ir_rc6_decoder(OE) ir_rc5_decoder(OE) dm_multipath coretemp fscache scsi_dh snd_hda_codec rc_tt_1500(OE) kvm_intel snd_hwdep ttusbir(OE) stv090x(OE) kvm snd_pcm rc_core(OE) snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul ghash_clmulni_intel snd_rawmidi snd_seq ddbridge(OE) cxd2099(OE) aesni_intel dvb_core(OE) snd_seq_device aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd xfs snd_timer serio_raw snd shpchp soundcore libcrc32c dw_dmac dw_dmac_core i2c_hid spi_pxa2xx_platform soc_button_array acpi_pad mac_hid iosf_mbi parport_pc ppdev lp parport btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper psmouse drm r8169 ahci mii libahci video sdhci_acpi sdhci
Aug 18 11:49:23 easyvdr kernel: [ 4605.879722] CPU: 0 PID: 2730 Comm: vdr Tainted: G W OE 3.16.0-51-generic #69~14.04.1-Ubuntu
Aug 18 11:49:23 easyvdr kernel: [ 4605.879724] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./N3150M, BIOS P1.10 06/02/2015
Aug 18 11:49:23 easyvdr kernel: [ 4605.879726] 0000000000000009 ffff880059e03ad0 ffffffff81766cee ffff880059e03b18
Aug 18 11:49:23 easyvdr kernel: [ 4605.879731] ffff880059e03b08 ffffffff8106de3d 0000000001080000 ffff88026f820078
Aug 18 11:49:23 easyvdr kernel: [ 4605.879735] 00000000ffffffff ffff88026f820080 0000000000000000 ffff880059e03b68
Aug 18 11:49:23 easyvdr kernel: [ 4605.879739] Call Trace:
Aug 18 11:49:23 easyvdr kernel: [ 4605.879744] [] dump_stack+0x45/0x56
Aug 18 11:49:23 easyvdr kernel: [ 4605.879748] [] warn_slowpath_common+0x7d/0xa0
Aug 18 11:49:23 easyvdr kernel: [ 4605.879752] [] warn_slowpath_fmt+0x4c/0x50
Aug 18 11:49:23 easyvdr kernel: [ 4605.879780] [] gen6_gt_check_fifodbg.isra.10+0x3d/0x50
Aug 18 11:49:23 easyvdr kernel: [ 4605.879818] [] __vlv_force_wake_put+0x3b/0x40
Aug 18 11:49:23 easyvdr kernel: [ 4605.879850] [] gen6_read32+0x107/0x110
Aug 18 11:49:23 easyvdr kernel: [ 4605.879875] [] gen8_ring_put_irq+0x7b/0xc0
Aug 18 11:49:23 easyvdr kernel: [ 4605.879902] [] __wait_seqno+0x42a/0x500
Aug 18 11:49:23 easyvdr kernel: [ 4605.879907] [] ? prepare_to_wait_event+0x100/0x100
Aug 18 11:49:23 easyvdr kernel: [ 4605.879912] [] ? poll_select_copy_remaining+0x130/0x130
Aug 18 11:49:23 easyvdr kernel: [ 4605.879934] [] i915_gem_object_wait_rendering__nonblocking+0xc5/0x140
Aug 18 11:49:23 easyvdr kernel: [ 4605.879958] [] i915_gem_set_domain_ioctl+0x91/0x140
Aug 18 11:49:23 easyvdr kernel: [ 4605.879974] [] drm_ioctl+0x1ec/0x660
Aug 18 11:49:23 easyvdr kernel: [ 4605.879981] [] ? do_readv_writev+0x171/0x240
Aug 18 11:49:23 easyvdr kernel: [ 4605.879985] [] do_vfs_ioctl+0x2e0/0x4c0
Aug 18 11:49:23 easyvdr kernel: [ 4605.879989] [] ? __sys_recvmsg+0x65/0x80
Aug 18 11:49:23 easyvdr kernel: [ 4605.879993] [] SyS_ioctl+0x81/0xa0
Aug 18 11:49:23 easyvdr kernel: [ 4605.879997] [] system_call_fastpath+0x1a/0x1f
Aug 18 11:49:23 easyvdr kernel: [ 4605.879999] ------
Kann das mit meinem anderen Problem zusammen hängen?
Oder könnte auch das MB defekt sein?
Oliver
|
| olsvse 27.Aug.2016 13:25:37 |
Nach der Installation mit einem neuen MB hat alles funktioniert.
Also wird es das MB gewesen sein
Gruß Oliver
|
