Results 1 to 4 of 4

Thread: Stuttering issue I have never seen and its driving me MAD!! (not hard drive)

  1. #1
    Join Date
    Jul 2005
    Posts
    504

    Stuttering issue I have never seen and its driving me MAD!! (not hard drive)

    I am having a problem with my TivoHD which I can't figure out how to troubleshoot.

    I have a few offending videos saved and wonder if anyone has a place I could upload a sample so some of you could play it on your Tivo and see if it has the same problem.

    It happens "randomly" during live TV or a previously recorded show. The video and audio will pause one second, the audio plays for one second, then video plays for one second, at which point the cycle will repeat. It will do this for 1-5 minutes before working fine again. I have already ran smart tests on both drives and they passed. I can have both tuners recording a high bitrate HD show or have them both on channels I don't receive with no change.

    The strange thing is that it always does it in the exact same place in the video. Button presses are cached so I can press pause which will pause the video after a while and then i can start the video from the beginning and it works fine until the exact same frame. I can even reboot the tivo and play the same video and it will stutter in the same spot.

    For a while I thought it may be some type of HDMI negotiation but I disconnected the hdmi connection and used component cables directly to the display with no change in behavior.

    Thank you for your advice

    edit: For fun I did a kickstart 52 but it made no difference. If it helps my specs are -
    THD Lifetime service. Two internal 1tb drives. Hacked prom but with totally unmodified software 11.0h
    Last edited by ciper; 08-04-2010 at 08:01 AM.

  2. #2
    Join Date
    Jan 2002
    Posts
    5,601
    Quote Originally Posted by ciper View Post
    I am having a problem with my TivoHD which I can't figure out how to troubleshoot.

    I have a few offending videos saved and wonder if anyone has a place I could upload a sample so some of you could play it on your Tivo and see if it has the same problem.

    It happens "randomly" during live TV or a previously recorded show. The video and audio will pause one second, the audio plays for one second, then video plays for one second, at which point the cycle will repeat. It will do this for 1-5 minutes before working fine again. I have already ran smart tests on both drives and they passed. I can have both tuners recording a high bitrate HD show or have them both on channels I don't receive with no change.

    The strange thing is that it always does it in the exact same place in the video. Button presses are cached so I can press pause which will pause the video after a while and then i can start the video from the beginning and it works fine until the exact same frame. I can even reboot the tivo and play the same video and it will stutter in the same spot.

    For a while I thought it may be some type of HDMI negotiation but I disconnected the hdmi connection and used component cables directly to the display with no change in behavior.

    Thank you for your advice

    edit: For fun I did a kickstart 52 but it made no difference. If it helps my specs are -
    THD Lifetime service. Two internal 1tb drives. Hacked prom but with totally unmodified software 11.0h
    Obviously, there are some errors in the material recorded to the drive. Understand that a digital stream with error checking / correction is being transmitted. If the errors in a particular data block were uncorrectable the resulting frames cannot be reconstructed. Thus, the video and audio freeze. Whether this occurred because of bad spots on the platter, or an error in the signal received I can't say.

    PlainBill
    There's a difference between needing help, and just being plain ole' lazy.

    "You cannot teach a man anything. You can only help him find it for himself." Galileo Galilei (1564-1642)

    HR20-700 with 2 TB, HR22-100, HR22-100, HR22-100, HR23-100 all running 0x5cd and networked.

  3. #3
    Join Date
    Jul 2005
    Posts
    504
    Any advice on how to figure out the source? I removed the drives from the Tivo and saw some kernel log entries that may help.

    Aug 4 21:16:11 (none) kernel: Audio on HDMI is AC3 & Audio on SPDIF is AC3
    Aug 4 21:16:12 (none) kernel: Bit Rate information not available for Audio type 3
    Aug 4 21:17:12 (none) last message repeated 6 times
    Aug 4 21:17:24 (none) kernel: --- bdecode_get_video_audio_pts_impl() video FIFO is stuck? video FIFO level = 66764
    Aug 4 21:17:26 (none) kernel: --- bplaypump_direct_io_impl() video FIFO is stuck? video FIFO level = 66764
    Aug 4 21:17:26 (none) kernel: --- bdecode_get_video_audio_pts_impl(): video FIFO is moving
    Aug 4 21:17:28 (none) kernel: --- bdecode_get_video_audio_pts_impl() video FIFO is stuck? video FIFO level = 26100
    Aug 4 21:17:33 (none) kernel: --- bplaypump_direct_io_impl() video FIFO is stuck? video FIFO level = 26100
    Aug 4 21:17:33 (none) kernel: --- bdecode_get_video_audio_pts_impl(): video FIFO is moving
    Aug 4 21:17:35 (none) kernel: --- bdecode_get_video_audio_pts_impl() video FIFO is stuck? video FIFO level = 16708
    Aug 4 21:17:43 (none) kernel: --- bplaypump_direct_io_impl() video FIFO is stuck? video FIFO level = 16708
    Aug 4 21:17:43 (none) kernel: --- bplaypump_direct_io_impl(): video FIFO is moving
    Aug 4 21:17:45 (none) kernel: --- bdecode_get_video_audio_pts_impl() video FIFO is stuck? video FIFO level = 47996
    Aug 4 21:17:51 (none) kernel: --- bdecode_get_video_audio_pts_impl(): video FIFO is moving
    Aug 4 21:17:55 (none) kernel: --- bdecode_get_video_audio_pts_impl() video FIFO is stuck? video FIFO level = 64732
    Aug 4 21:17:56 (none) kernel: --- bplaypump_direct_io_impl() video FIFO is stuck? video FIFO level = 64732
    Aug 4 21:17:56 (none) kernel: --- bdecode_get_video_audio_pts_impl(): video FIFO is moving

    Aug 4 21:18:04 (none) kernel: Audio on HDMI is PCM & Audio on SPDIF is PCM
    Aug 4 21:18:04 (none) kernel: Audio on HDMI is PCM & Audio on SPDIF is PCM
    Aug 4 21:18:09 (none) kernel: BHDM Interrupt ID=0x9!
    I tried to use Seatools to check the status of my drives (maxtor drives under winxp) but it crashes


    So I found an open source alternative that runs on nearly any OS http://gsmartcontrol.berlios.de/home/index.php/en/Home

    Edit: Hmm maybe it is a failing drive? I am not used to the smartctl output. Can you give me a second set of eyes?
    Code:
    [SIZE="1"]smartctl 5.39.1 2010-01-28 r3054 [i686-pc-mingw32-xp-sp3] (sf-win32-5.39.1-1)
    Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
    
    === START OF INFORMATION SECTION ===
    Model Family:     Seagate Maxtor DiamondMax 22
    Device Model:     MAXTOR STM31000340AS
    Serial Number:    9QJ0QFP5
    Firmware Version: XM15
    User Capacity:    1,000,204,886,016 bytes
    Device is:        In smartctl database [for details use: -P show]
    ATA Version is:   8
    ATA Standard is:  ATA-8-ACS revision 4
    Local Time is:    Wed Aug 04 18:46:39 2010 PDT
    
    ==> WARNING: There are known problems with these drives,
    see the following Seagate web pages:
    http://seagate.custkb.com/seagate/cr...p?DocId=207931
    http://seagate.custkb.com/seagate/cr...p?DocId=207969
    http://seagate.custkb.com/seagate/cr...p?DocId=207975
    
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    See vendor-specific Attribute list for marginal Attributes.
    
    General SMART Values:
    Offline data collection status:  (0x82)	Offline data collection activity
    					was completed without error.
    					Auto Offline Data Collection: Enabled.
    Self-test execution status:      (   0)	The previous self-test routine completed
    					without error or no self-test has ever 
    					been run.
    Total time to complete Offline 
    data collection: 		 ( 642) seconds.
    Offline data collection
    capabilities: 			 (0x7b) SMART execute Offline immediate.
    					Auto Offline data collection on/off support.
    					Suspend Offline collection upon new
    					command.
    					Offline surface scan supported.
    					Self-test supported.
    					Conveyance Self-test supported.
    					Selective Self-test supported.
    SMART capabilities:            (0x0003)	Saves SMART data before entering
    					power-saving mode.
    					Supports SMART auto save timer.
    Error logging capability:        (0x01)	Error logging supported.
    					General Purpose Logging supported.
    Short self-test routine 
    recommended polling time: 	 (   1) minutes.
    Extended self-test routine
    recommended polling time: 	 ( 231) minutes.
    Conveyance self-test routine
    recommended polling time: 	 (   2) minutes.
    SCT capabilities: 	       (0x103b)	SCT Status supported.
    					SCT Feature Control supported.
    					SCT Data Table supported.
    
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x000f   099   092   006    Pre-fail  Always       -       27180975
      3 Spin_Up_Time            0x0003   091   089   000    Pre-fail  Always       -       0
      4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       38
      5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       1261
      7 Seek_Error_Rate         0x000f   076   060   030    Pre-fail  Always       -       69417970734
      9 Power_On_Hours          0x0032   084   084   000    Old_age   Always       -       14317
     10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       3
     12 Power_Cycle_Count       0x0032   100   100   020    Old_age   Always       -       38
    184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0
    187 Reported_Uncorrect      0x0032   001   001   000    Old_age   Always       -       176
    188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       2
    189 High_Fly_Writes         0x003a   001   001   000    Old_age   Always       -       871
    190 Airflow_Temperature_Cel 0x0022   063   042   045    Old_age   Always   In_the_past 37 (0 4 37 28)
    194 Temperature_Celsius     0x0022   037   058   000    Old_age   Always       -       37 (0 16 0 0)
    195 Hardware_ECC_Recovered  0x001a   041   027   000    Old_age   Always       -       27180975
    197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       87
    198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       87
    199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0
    
    SMART Error Log Version: 1
    ATA Error Count: 176 (device log contains only the most recent five errors)
    	CR = Command Register [HEX]
    	FR = Features Register [HEX]
    	SC = Sector Count Register [HEX]
    	SN = Sector Number Register [HEX]
    	CL = Cylinder Low Register [HEX]
    	CH = Cylinder High Register [HEX]
    	DH = Device/Head Register [HEX]
    	DC = Device Command Register [HEX]
    	ER = Error register [HEX]
    	ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    
    Error 176 occurred at disk power-on lifetime: 14278 hours (594 days + 22 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 00 ff ff ff ef 00  42d+04:29:53.794  READ DMA EXT
      25 00 00 ff ff ff ef 00  42d+04:29:52.564  READ DMA EXT
      25 00 01 ff ff ff ef 00  42d+04:29:52.546  READ DMA EXT
      25 00 00 ff ff ff ef 00  42d+04:29:52.542  READ DMA EXT
      25 00 00 ff ff ff ef 00  42d+04:29:52.524  READ DMA EXT
    
    Error 175 occurred at disk power-on lifetime: 14278 hours (594 days + 22 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 00 ff ff ff ef 00  42d+04:29:34.420  READ DMA EXT
      35 00 00 b6 5e c3 eb 00  42d+04:29:34.418  WRITE DMA EXT
      35 00 00 b6 5d c3 eb 00  42d+04:29:34.416  WRITE DMA EXT
      35 00 00 b6 5c c3 eb 00  42d+04:29:34.415  WRITE DMA EXT
      e7 00 00 bf 50 df a0 00  42d+04:29:34.387  FLUSH CACHE
    
    Error 174 occurred at disk power-on lifetime: 14278 hours (594 days + 22 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 00 ff ff ff ef 00  42d+04:29:30.755  READ DMA EXT
      25 00 00 ff ff ff ef 00  42d+04:29:30.460  READ DMA EXT
      35 00 00 ff ff ff ef 00  42d+04:29:30.458  WRITE DMA EXT
      35 00 00 ff ff ff ef 00  42d+04:29:30.457  WRITE DMA EXT
      35 00 00 ff ff ff ef 00  42d+04:29:30.455  WRITE DMA EXT
    
    Error 173 occurred at disk power-on lifetime: 14278 hours (594 days + 22 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 00 ff ff ff ef 00  42d+04:29:20.465  READ DMA EXT
      35 00 00 b6 48 c3 eb 00  42d+04:29:20.464  WRITE DMA EXT
      35 00 00 b6 47 c3 eb 00  42d+04:29:20.430  WRITE DMA EXT
      e7 00 00 bf 3a df a0 00  42d+04:29:20.308  FLUSH CACHE
      35 00 00 ff ff ff ef 00  42d+04:29:20.306  WRITE DMA EXT
    
    Error 172 occurred at disk power-on lifetime: 14278 hours (594 days + 22 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 00 ff ff ff 0f  Error: UNC at LBA = 0x0fffffff = 268435455
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      25 00 00 ff ff ff ef 00  42d+04:29:16.540  READ DMA EXT
      35 00 00 b6 46 c3 eb 00  42d+04:29:16.538  WRITE DMA EXT
      e7 00 00 bf 38 df a0 00  42d+04:29:16.499  FLUSH CACHE
      35 00 00 ff ff ff ef 00  42d+04:29:16.497  WRITE DMA EXT
      35 00 00 ff ff ff ef 00  42d+04:29:16.495  WRITE DMA EXT
    
    SMART Self-test log structure revision number 1
    Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
    # 1  Short offline       Completed without error       00%     14317         -
    # 2  Extended offline    Aborted by host               90%     12072         -
    # 3  Conveyance offline  Completed without error       00%     12072         -
    # 4  Short offline       Completed without error       00%     12072         -
    
    SMART Selective self-test log data structure revision number 1
     SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
        1        0        0  Not_testing
        2        0        0  Not_testing
        3        0        0  Not_testing
        4        0        0  Not_testing
        5        0        0  Not_testing
    Selective self-test flags (0x0):
      After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    Last edited by ciper; 08-04-2010 at 10:15 PM.

  4. #4
    Join Date
    Jul 2005
    Posts
    504
    I am starting to think my drive is failing and that the onboard kickstart smart testing on the Tivo and Smart warnings are USELESS! My tivo has two identical MAXTOR STM31000340AS and below you can compare a specific section of the output from smarttcl . Look at section 5, 187, 188, 189, 197 and 198

    drive a
    Code:
    ID#	ATTRIBUTE_NAME	RAW_VALUE							
    1	Raw_Read_Error_Rate		27180975							
    3	Spin_Up_Time			0							
    4	Start_Stop_Count		38							
    5	Reallocated_Sector_Ct		1263							
    7	Seek_Error_Rate			69417971140							
    9	Power_On_Hours			14317							
    10	Spin_Retry_Count		3							
    12	Power_Cycle_Count		38							
    184	End-to-End_Error		0							
    187	Reported_Uncorrect		176							
    188	Command_Timeout			2							
    189	High_Fly_Writes			871							
    190	Airflow_Temperature_Cel		37 (0 4 37 28)							
    194	Temperature_Celsius		37 (0 16 0 0)							
    195	Hardware_ECC_Recovered		27180975							
    197	Current_Pending_Sector		87							
    198	Offline_Uncorrectable		87							
    199	UDMA_CRC_Error_Count		0							
    SMART Error Log Version: 1								
    ATA Error Count: 176 (device log contains only the most recent five errors)
    drive b
    Code:
    ID#	ATTRIBUTE_NAME	RAW_VALUE							
    1	Raw_Read_Error_Rate		165409830							
    3	Spin_Up_Time			0							
    4	Start_Stop_Count		36							
    5	Reallocated_Sector_Ct		0							
    7	Seek_Error_Rate			528436278293							
    9	Power_On_Hours			14264							
    10	Spin_Retry_Count		1							
    12	Power_Cycle_Count		36							
    184	End-to-End_Error		0							
    187	Reported_Uncorrect		0							
    188	Command_Timeout			0						
    189	High_Fly_Writes			171							
    190	Airflow_Temperature_Cel		27 (0 210 27 25)							
    194	Temperature_Celsius		27 (0 17 0 0)							
    195	Hardware_ECC_Recovered		165409830							
    197	Current_Pending_Sector		0							
    198	Offline_Uncorrectable		0							
    199	UDMA_CRC_Error_Count		0							
    SMART Error Log Version: 1								
    NoErrors Logged
    edit: I'm trying to figure out how to play musical chairs with drives and images.
    I am wondering if the following would work -
    dd if=/dev/sda bs=1024k | gzip -5 > /backup.gz
    then
    gzip -d -c /backup.gz | dd of=/dev/sda
    Any advice on changes I can make to improve throughput on large drive? Do you think on a fast machine that higher compression levels would put less stress on the target file thus speeding up the copy? Or would lower compression help speed more since its not relying on the cpu?
    Last edited by ciper; 08-05-2010 at 03:20 AM.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •