General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Rich Brown <richb.hanover@gmail.com>
To: bloat@lists.bufferbloat.net, cerowrt-devel-request@lists.bufferbloat.net
Subject: [Bloat] Debugging a crash
Date: Tue, 18 Feb 2020 11:27:08 -0500	[thread overview]
Message-ID: <B090B915-2CFD-4615-820D-AEFEF920D2FE@gmail.com> (raw)

Folks,

I was running OpenWrt 19.07-rc2 on my Archer C7v2, and experienced a potentially-repeatable crash under heavy network traffic load.

I was uploading several long videos to Youtube (> 5GBytes each) and watching Netflix on my 7mbps/768kbps DSL connection. Things were working fine (latency remained acceptable - YAY SQM!) My upstream pipe (slow as it is) was totally filled by the three competing uploads, and Netflix was doing its best to show me the West Wing.

A couple times during the evening, the Netflix stream just crapped out and I lost the connection. (Infinite buffering message on-screen, couldn't get to Google, etc. The LuCI GUI showed uptime of a minute or so, and then things were fine again.)

I now have OpenWrt 19.07.1 installed, and have a little bandwidth for repeating the experiment.

What debugging information should I turn on/look for in case this happens again? Thanks.

Rich

PS The new Youtube uploader facility is excellent. If you keep the window open, it automagically resumes the transfer after interruption. It's great for people like me who have large files to upload on a slow link, where the likelihood of a link failure (or needing to move my laptop to a different location) is high.

             reply	other threads:[~2020-02-18 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-18 16:27 Rich Brown [this message]
2020-02-18 18:35 ` Toke Høiland-Jørgensen
2020-02-18 19:15   ` Sebastian Moeller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=B090B915-2CFD-4615-820D-AEFEF920D2FE@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cerowrt-devel-request@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox