On Saturday, 8 November 2025 08:27:51 Greenwich Mean Time Dale wrote:
> Michael wrote:
> > On Friday, 7 November 2025 23:48:21 Greenwich Mean Time Dale wrote:
> >> Michael wrote:
> >>> On Friday, 7 November 2025 17:26:29 Greenwich Mean Time Dale wrote:
> >>>> Howdy,
> >>>> 
> >>>> I noticed videos started doing this weird stutter so I checked the
> >>>> messages file.  As to changes, I moved a external hard drive into the
> >>>> case and I added a hard drive to my data group.  It's up to 60TBs now.
> >>>> I did move the case but the system ran the whole time.  Love hot
> >>>> plugging SATA drives.  This is the only error I can find so I figure
> >>>> this is somehow causing my video to stutter.  This is what is in the
> >>>> messages log, filtering out the unneeded cruft.
> >>>> 
> >>>> 
> >>>> Nov  7 10:16:41 Gentoo-1 kernel: r8169 0000:08:00.0 enp8s0: NETDEV
> >>>> WATCHDOG: CPU: 4: transmit queue 0 timed out 5480 ms
> >>>> Nov  7 10:26:06 Gentoo-1 kernel: r8169 0000:08:00.0 enp8s0: NETDEV
> >>>> WATCHDOG: CPU: 3: transmit queue 0 timed out 5106 ms
> >>>> Nov  7 10:32:46 Gentoo-1 kernel: r8169 0000:08:00.0 enp8s0: NETDEV
> >>>> WATCHDOG: CPU: 7: transmit queue 0 timed out 5003 ms
> >>>> Nov  7 10:34:12 Gentoo-1 kernel: r8169 0000:08:00.0 enp8s0: NETDEV
> >>>> WATCHDOG: CPU: 3: transmit queue 0 timed out 5561 ms
> >>>> Nov  7 10:37:40 Gentoo-1 kernel: r8169 0000:08:00.0 enp8s0: NETDEV
> >>>> WATCHDOG: CPU: 4: transmit queue 0 timed out 5054 ms
> >>>> Nov  7 10:45:25 Gentoo-1 kernel: r8169 0000:08:00.0 enp8s0: NETDEV
> >>>> WATCHDOG: CPU: 7: transmit queue 0 timed out 5225 ms
> >>>> Nov  7 10:48:31 Gentoo-1 kernel: r8169 0000:08:00.0 enp8s0: NETDEV
> >>>> WATCHDOG: CPU: 0: transmit queue 0 timed out 5008 ms
> >>>> 
> >>>> 
> >>>> I'm using the same kernel so the driver hasn't changed.  It worked fine
> >>>> after last weekends update up until the drive additions and case move.
> >>>> The only change is adding those drives and moving the case so I can
> >>>> take
> >>>> the sides off.  I did some searching.  Most problems point to a bad
> >>>> driver.  Since I haven't changed drivers and it worked fine for months,
> >>>> I doubt that is my problem.
> >>>> 
> >>>> Could this be a bad cable or some other issue?  I unplugged and plugged
> >>>> the cables back up.  Given I only have to twist my case enough to take
> >>>> the sides off, I'm kinda doubtful it is a cable but weird things
> >>>> happen.
> >>>> 
> >>>> I might also add, as I type this message, when it stutters, it also
> >>>> stops seeing what I'm typing.  It leaves out characters I've typed.  It
> >>>> kinda freezes everything for a second or so.  Pretty annoying.
> >>>> 
> >>>> Anyone have any thoughts on this?  Ran into this problem and found a
> >>>> fix?  I'll keep trying things.  See if I luck up on something in the
> >>>> meantime.
> >>>> 
> >>>> Thanks.
> >>>> 
> >>>> Dale
> >>>> 
> >>>> :-)  :-)
> >>> 
> >>> Your log error refers to your NIC.  Are you playing the video file over
> >>> the
> >>> LAN?  If you haven't touched the kernel drivers then it looks like a
> >>> problem with your ethernet cable, or your NIC.  Having checked both end
> >>> connectors on the cable you could try reloading the NIC module to see if
> >>> 'dmesg -W' prints any errors.
> >> 
> >> Want to hear something funny.  I went to my sis-n-laws and helped her
> >> with some things.  She just got a new porch.  Anyway, I got back and
> >> then went to deliver a gift to a friend.  I was gone a few hours during
> >> all that.  I checked the logs and not a single error.  Just the usual
> >> smartd stuff about changing temps and my VPN resetting its connection.
> >> Oh, cron ran a few times as well.  No network error or anything.
> >> 
> >> To add to that, I been watching TV for about 30 minutes.  Video hasn't
> >> missed a beat yet.  Nice stable playing of the video.  What does the NIC
> >> have to do with video, not a thing.  I just noticed that when the video
> >> stuttered, the NIC error was in messages.  I'm not streaming over a
> >> network either.  The video file is on one of the LVM drive groups inside
> >> the case.  That's what made it so weird.
> >> 
> >> Makes one wonder doesn't it???  :/
> >> 
> >> Dale
> >> 
> >> :-)  :-)
> > 
> > A power glitch perhaps?  Have you sized your PSU for all these bigger
> > drives? Do they lights in the neighbourhood dim momentarily when you spin
> > them up?> 
> > :-)
> 
> No power problems that I know of.  My power supply is plenty big
> enough.  Likely to big.  I think it is a 750 watt or something. 
> According to the UPS, it pulls about 200 watts, which included two
> monitors, modem, router, little audio amp and such which isn't powering
> the computer itself. 
> 
> I checked the logs just now, while my onion rings cook.  No problems at
> all.  Just the normal stuff.  Best I can figure, my ISP was having some
> issue maybe???  Odd that it started when I had to twist my rig around
> and take the sides off tho.  That is what was so confusing about this
> error.  It didn't make sense.  I didn't even touch the mobo itself. 
> Turned out I had enough power and a couple SATA cables already
> available.  I guess from when I switched to larger drives. 
> 
> I have to say tho, this much larger case is coming in handy.  ;-)  I
> still have a couple drive holes in the bottom and a few more in the
> stack area.  I can add more drives and store more data if needed.  :-D 
> 
> Dale
> 
> :-)  :-) 

Does 'ip -s -s link' reveal transmission errors?  Either way, as you say NIC 
queueing errors should not make a difference in playing a video locally.  Is 
the stuttering recurring if you play the same video again?

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to