From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 88A673CB37; Tue, 18 Feb 2020 14:16:09 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1582053363; bh=ISKSL6mMsvWU/3Y05o61kLjWPwFcfnKGb7sSCoYyjos=; h=X-UI-Sender-Class:Date:In-Reply-To:References:Subject:To:From; b=XiziMoVjgHM93CRdNWaWgO7/yKwaOEnqQLOyzGY2ZzeI86J75NAE4D7jUou28TZRf 4glg9hgGO6dfA2UcgoER75G9o5G7QtCNzgzKzGC5oICS7QnBlT8rRb1jmmQeCL+3Yo IryDxqFi9LKQxpbw8WkCS8r5tGMoQAJMXnMSXgTs= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from [10.152.23.61] ([80.187.112.237]) by mail.gmx.com (mrgmx105 [212.227.17.168]) with ESMTPSA (Nemesis) id 1MVN6t-1iv5NM2SbH-00SQgI; Tue, 18 Feb 2020 20:16:03 +0100 Date: Tue, 18 Feb 2020 20:15:27 +0100 User-Agent: K-9 Mail for Android In-Reply-To: <87h7znyc98.fsf@toke.dk> References: <87h7znyc98.fsf@toke.dk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----4M7MQ2AEXQ77FYRSGS10GNG8S8H957" Content-Transfer-Encoding: 7bit To: bloat@lists.bufferbloat.net, =?ISO-8859-1?Q?Toke_H=F8iland-J=F8rgensen?= , Rich Brown , cerowrt-devel-request@lists.bufferbloat.net From: Sebastian Moeller Message-ID: X-Provags-ID: V03:K1:1BdpTQw5PjzSmj4sAfYdWd1qvZ9OwzZny4WFxSdihbPa2avSZbJ TA+/DS4aPIsYpJlr+q8RvdABFIyypUltbK1rHzO821wcWVFBMLXkbmvsAHaYJEc/EYu5mzS CUuvc9ZWBb9fOATroMHMC3nF0aAXYKdNSlWeXu/z2wDg8Gpt9FQY6NLACGGku25d8o/8y1e XfnFQZqLkKAwa51yuS2Lg== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:2op76KGpLDE=:qqL+3YKXkiwxvaiqArjEbW D7mDi8ZlzDKjvQyE5O+VoaZajYzphMlKCpLtcqGZGKQoqioPsWWNzWWW3kQINIZdDT5Zmop24 BYrvtHOrfwayymx4DoFwj92u7E4ilVhiiAmyYCjfA/hdk7TimlNywjnqjfInXKXuY3nHTx/3o iolTI8VuoHmbOqAgo887W2xnOLbpfAIOINnReJOKcp4hAlcj1acb+OyOLBIX1RLMMxb7BQvWI 8tz4QYusWxZ/KebQ04Zu5uG2U85Hubqdkljak4Hf6zxXTvH26rPHzPup2M1WH1AfpCfiNwF0U upvbBFwws8hFIc40k2DUxCJ23MWZ0/GtSBZSev+k9nMcw+LSQb8Lo75b5aZ4uQbKPM+o6oiXl 7H69Euakj24UjWqo+GyPIEUH/gaXBoMCE8Hjy0X10MyjCaEuPAV0jO4RDySsJ7tdXaXUu+mwq BFW9feZ9ECk+AoVn65ZM9zUqFj2slX16x7Jk/Acys3bakzlqxEBsA1R+EBUYcucXUdX0gbNq9 8J0u7z7ATt+BVzmZrnvoQ4PlAZK9rh/WcD2gm02VSvqS0US81z2FJano1DrtOHn3gR360RVWs GzEKJoBFgvSitHWolzopUoJHrfH/bQIVcGF8D9PQQAiVgENtnsRA3jOQ2WTrmV8NXIcXUfa4X ZMn4r7wOBHM51u1lZP4ki6te0molS7SVV6SXUWd5XZ/kSUBPSyYLuacVB0eU66fANBDllKdah TmC10QAiCJgXaI7Be+FK+wfNP9IShI2MkUJfMw7x6Xnpf+IoGleGRbIKKNlBo8C14VPziSQRX NKhTpRQNs59gRXVLGc4CJ8x17/6KG0w9dMrsXb0E6MlD+E3AcSfdgHemF10U8AfWcGt1DRB5s Lx7zUbE0rHUTYJ4nf5OkKFkXP2JyZfqAQgMkZWBhHr2Mwq49D8zKsSLFHb7Ew+gWjHAtUCq27 wqtZ/UGZx56ni8j0JGxpMVUC5Cyc24xNG3qwTIl+5IbQCum0PzBr0/I8fUAyakT+wqUY5QTpL k9c6hWlsdROU9bsOHgo5DtzrM0zHAQxjy1kk3oiWUkRfQEpMrx5UWmzKCpeZLUpzK8mZRWhog mQmaJKrRXKmALVxpflxsECXNCelxnSut2cMZKl/t4xj4cpjzPSEQbAqMjjAjdKdIIZE5+nMYD CFZqaeboB4VuSe6wwBwRZnQApSv9qqXX6Czc6MM4FxVB6pFwaRTvkrf65B+AMHvqeaX4VT2GJ D3fKP6m+HV8B8ZtNX Subject: Re: [Bloat] Debugging a crash X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Feb 2020 19:16:09 -0000 ------4M7MQ2AEXQ77FYRSGS10GNG8S8H957 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Have a look at https://forum=2Eopenwrt=2Eorg/t/crashlog-retrieval-mips/1973= 1=2E It seems cat /sys/kernel/debug/crashlog after a reboot caused by a cra= sh mightcreveal some more details=2E Good luck Sebastian On February 18, 2020 7:35:31 PM GMT+01:00, "Toke H=C3=B8iland-J=C3=B8rgens= en" wrote: >Rich Brown writes: > >> Folks, >> >> I was running OpenWrt 19=2E07-rc2 on my Archer C7v2, and experienced a >> potentially-repeatable crash under heavy network traffic load=2E >> >> I was uploading several long videos to Youtube (> 5GBytes each) and >> watching Netflix on my 7mbps/768kbps DSL connection=2E 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=2E >> >> A couple times during the evening, the Netflix stream just crapped >out >> and I lost the connection=2E (Infinite buffering message on-screen, >> couldn't get to Google, etc=2E The LuCI GUI showed uptime of a minute >or >> so, and then things were fine again=2E) >> >> I now have OpenWrt 19=2E07=2E1 installed, and have a little bandwidth f= or >> repeating the experiment=2E >> >> What debugging information should I turn on/look for in case this >> happens again? Thanks=2E > >If the box reboots, this sounds like a kernel oops=2E In which case, we'd >really need a kernel stack dump to debug it=2E Which I'm not sure there's >a good way to get on OpenWrt without attaching a serial console :( > >Unless of course you can find a reliable way to reproduce it without >too >much delay, in which case someone with a serial console can take a >look, >I guess :) > >-Toke >_______________________________________________ >Bloat mailing list >Bloat@lists=2Ebufferbloat=2Enet >https://lists=2Ebufferbloat=2Enet/listinfo/bloat --=20 Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E ------4M7MQ2AEXQ77FYRSGS10GNG8S8H957 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Have a look at https://forum=2Eopenwrt=2Eorg/t/= crashlog-retrieval-mips/19731=2E It seems cat /sys/kernel/debug/crashlo= g after a reboot caused by a crash mightcreveal some more details=2E
Good luck
Sebastian

On Februa= ry 18, 2020 7:35:31 PM GMT+01:00, "Toke H=C3=B8iland-J=C3=B8rgensen" <to= ke@toke=2Edk> wrote:
Rich Brown <richb=2Ehanover@gmail=2Ecom> write=
s:

 Folks,

=
 I was running OpenWrt 19=2E07-rc2 on my Archer C7v2, and experienced a
=
 potentially-repeatable crash under heavy network traffic load=2E

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

 A couple times du=
ring the evening, the Netflix stream just crapped out
 and I lost the co=
nnection=2E (Infinite buffering message on-screen,
 couldn't get to Goog=
le, etc=2E The LuCI GUI showed uptime of a minute or
 so, and then thing=
s were fine again=2E)

 I now have OpenWrt 19=2E07=2E1 installed, and=
 have a little bandwidth for
 repeating the experiment=2E

 What d=
ebugging information should I turn on/look for in case this
 happens aga=
in? Thanks=2E

If the box reboots, this sounds like a ke=
rnel oops=2E In which case, we'd
really need a kernel stack dump to debu=
g it=2E Which I'm not sure there's
a good way to get on OpenWrt without =
attaching a serial console :(

Unless of course you can find a reliab=
le way to reproduce it without too
much delay, in which case someone wit=
h a serial console can take a look,
I guess :)

-Toke
Bloat mai=
ling list
Bloat@lists=2Ebufferbloat=2Enet
https://lists=2Ebufferbloat=2Enet/listinf=
o/bloat

--
Sent from my Android dev= ice with K-9 Mail=2E Please excuse my brevity=2E ------4M7MQ2AEXQ77FYRSGS10GNG8S8H957--