From: Romano <unobe@cpan.org>
To: 9front@9front.org,cinap_lenrek@felloff.net
Subject: Re: [9front] rpi4 shoots to 100% load and is unresponsive
Date: Thu, 07 May 2020 20:45:23 +0000 [thread overview]
Message-ID: <9A981BE5-1F22-4548-8A8D-4DA76246B9E6@cpan.org> (raw)
In-Reply-To: <CF08CCF3-3EBD-402E-95B5-599A83FB788C@cpan.org>
I didn't know if image attachments would filter my message, so I've uploaded some images to pasteboard.co and supllied the links below. When I did 'hg update 7709', rebuilt the kernel, and copied over to /n/pidos, I still get the breakage.. This is using thw latest firmware (mk clean, mk all) under /sys/src/boot/bcm. Note the jumps in load. The first jump is when things start locking up, but sometimes the mouse menu for stats still works for a bit (as shown). If I give it another minute, it'll be at 100%.
https://pasteboard.co/J7jOD5o.jpg
https://pasteboard.co/J7jOYoL.jpg
https://pasteboard.co/J7jPeRz.jpg
On May 7, 2020 8:06:51 PM UTC, Romano <unobe@cpan.org> wrote:
>Thanks , cinap.
>
>I noticed that too, but I think my inexperience with hg screwed me, or
>maybe just too late when I was messing with it. I thought of trying to
>roll back to an earlier commit to see how things built, and I think I
>did 'hg update 7726', rather than the changset prior.
>
>If I do 'hg update 7709', then 'mk' in /sys/src/9/bcm64, then copy the
>kernel over to /n/pidos, would that be heading in the right direction?
>Or should I revert the problematic commit in my working area, and see
>how that goes?
>
>
>On May 7, 2020 7:54:52 PM UTC, cinap_lenrek@felloff.net wrote:
>>i could imagine that the following change might have an inmpact?
>>
>>changeset: 7726:e2d79247a51c
>>user: cinap_lenrek@felloff.net
>>date: Sun Apr 26 19:54:46 2020 +0200
>>summary: kernel: improve page reclaimation strategy and locking
>>
>>i have not tested this change on raspi, but ran some stress tests
>>on a thinkpad, filling all memory and memory reclaimation worked
>>fine there.
>>
>>in any case, you can try reverting this change and see if it has
>>any impact?
>>
>>i do not have time now... maybe this weekend i can look into it
>>and try on raspberry pi.
>>
>>--
>>cinap
next prev parent reply other threads:[~2020-05-07 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 18:46 Romano
2020-05-07 19:25 ` [9front] " hiro
2020-05-07 19:47 ` Romano
2020-05-07 19:54 ` cinap_lenrek
2020-05-07 20:06 ` Romano
2020-05-07 20:45 ` Romano [this message]
2020-05-07 21:03 ` cinap_lenrek
2020-05-07 21:11 ` cinap_lenrek
2020-05-07 21:29 ` cinap_lenrek
2020-05-07 22:02 ` Romano
2020-05-08 4:44 ` kokamoto
2020-05-08 5:57 ` kokamoto
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9A981BE5-1F22-4548-8A8D-4DA76246B9E6@cpan.org \
--to=unobe@cpan.org \
--cc=9front@9front.org \
--cc=cinap_lenrek@felloff.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;
as well as URLs for NNTP newsgroup(s).