VU+ Solo 2 reboot loop

    Diese Seite verwendet Cookies. Durch die Nutzung unserer Seite erklären Sie sich damit einverstanden, dass wir Cookies setzen. Weitere Informationen

    • VU+ Solo 2 reboot loop

      Hi Guys,

      I have problem after updating to the latest VTI image (13.0.9)
      Receiver reboots every few minutes.
      I've seen some hdd errors, so unplugged it, but this did not solve the problem.
      here is log:

      Spoiler anzeigen

      May 28 14:59:08 vusolo2 user.warn kernel: FE tune
      May 28 14:59:08 vusolo2 user.warn kernel: [AUD]: AUDIO_SELECT_SOURCE 0
      May 28 14:59:08 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_BYPASS_MODE 0
      May 28 14:59:08 vusolo2 user.warn kernel: [AUD]: AC3 downmix 0 state : 0
      May 28 14:59:08 vusolo2 user.warn kernel: [AUD]: AUDIO_PAUSE 7963264
      May 28 14:59:08 vusolo2 user.warn kernel: [AUD]: AUDIO_PLAY 7963264 decoder start : 0
      May 28 14:59:08 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0 0
      May 28 14:59:08 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 1
      May 28 14:59:08 vusolo2 user.warn kernel: [VID]: VIDEO_FREEZE 7963264 0
      May 28 14:59:08 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 7963264 5 2
      May 28 14:59:08 vusolo2 user.warn kernel: [VID]: VIDEO_SLOWMOTION 0 1
      May 28 14:59:08 vusolo2 user.warn kernel: [VID]: VIDEO_FAST_FORWARD 0 1
      May 28 14:59:08 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 7963264 1
      May 28 14:59:08 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7963264 1 aph=0xcc459800
      May 28 14:59:08 vusolo2 user.warn kernel: [AUD]: Mute : 0
      May 28 14:59:08 vusolo2 user.warn kernel: [AUD]: AUDIO_CHANNEL_SELECT 0
      May 28 15:01:08 vusolo2 user.warn kernel: EXT4-fs warning (device sda1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
      May 28 15:01:08 vusolo2 user.warn kernel: EXT4-fs warning (device sda1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0)
      May 28 15:01:08 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 1 1
      May 28 15:01:08 vusolo2 user.warn kernel: [AUD]: AUDIO_STOP 7963264
      May 28 15:01:08 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE 7963264 0 aph=0x0
      May 28 15:01:08 vusolo2 user.warn kernel: [AUD]: AUDIO_CONTINUE aph=0 0 0
      May 28 15:01:09 vusolo2 user.warn kernel: [VID]: VIDEO_SET_STREAMTYPE 0
      May 28 15:01:09 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 1 0
      May 28 15:01:09 vusolo2 user.warn kernel: [VID]: VIDEO_PLAY 1 2 0
      May 28 15:01:09 vusolo2 user.warn kernel: [VID]: VIDEO_CONTINUE 1 1
      May 28 15:01:09 vusolo2 user.warn kernel: [VID]: VIDEO_CLEAR_BUFFER 1 1 0
      May 28 15:01:09 vusolo2 user.warn kernel: [VID]: VIDEO_STOP 0 1
      May 28 15:01:09 vusolo2 user.warn kernel: [VID]: VIDEO_SELECT_SOURCE 0 0
      May 28 15:01:10 vusolo2 user.err kernel: [LCD]: unknown cmd 0x1015
      May 28 15:01:10 vusolo2 user.err kernel: UBI error: ubi_open_volume: cannot open device 0, volume 0, error -16
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MUTE 0
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER -866804240
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : amixl 0, amixr 0
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -784, right volume -784
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER -866804240
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : amixl 10, amixr 10
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -70, right volume -70
      May 28 15:01:17 vusolo2 user.warn kernel: [AUD]: AUDIO_SET_MIXER : next left volume -784, right volume -784


      Bart

      Dieser Beitrag wurde bereits 1 mal editiert, zuletzt von ditschi1691 ()

    • I guess the log was done while the HDD was still concted?
      Obviously the HDD's filesystem is corrupt, thus the HDD can't be mounted.

      However, after unplugging the HDD the problem shouldn't occur anymore.
      If the system still reboots without the HDD, did you check the logs in this case, too?
      Is there anything in the log which could point to the error?