From: Christian Hewitt <christianshewitt@gmail.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, linux-usb@vger.kernel.org,
linux-amlogic@lists.infradead.org, furkan@fkardame.com,
Brad Harper <bjharper@gmail.com>
Subject: Re: Deadlock under load with Linux 5.9 and other recent kernels
Date: Sat, 26 Sep 2020 16:28:13 +0400 [thread overview]
Message-ID: <91886A80-8164-4699-8662-E7D3444A4F12@gmail.com> (raw)
In-Reply-To: <c431ae48-6913-acc0-dc0a-b52065e9eaed@kernel.dk>
> On 26 Sep 2020, at 4:13 pm, Jens Axboe <axboe@kernel.dk> wrote:
>
> On 9/26/20 5:55 AM, Christian Hewitt wrote:
>>>
>>> On 26 Sep 2020, at 2:51 pm, Jens Axboe <axboe@kernel.dk> wrote:
>>>
>>> On 9/26/20 1:55 AM, Christian Hewitt wrote:
>>>> I am using an ARM SBC device with Amlogic S922X chip (Beelink
>>>> GS-King-X, an Android STB) to boot the Kodi mediacentre distro
>>>> LibreELEC (which I work on) although the issue is also reproducible
>>>> with Manjaro and Armbian on the same hardware, and with the GT-King
>>>> and GT-King Pro devices from the same vendor - all three devices are
>>>> using a common dtsi:
>>>>
>>>> https://github.com/chewitt/linux/blob/amlogic-5.9-integ/arch/arm64/boot/dts/amlogic/meson-g12b-gsking-x.dts
>>>> https://github.com/chewitt/linux/blob/amlogic-5.9-integ/arch/arm64/boot/dts/amlogic/meson-g12b-gtking-pro.dts
>>>> https://github.com/chewitt/linux/blob/amlogic-5.9-integ/arch/arm64/boot/dts/amlogic/meson-g12b-gtking.dts
>>>> https://github.com/chewitt/linux/blob/amlogic-5.9-integ/arch/arm64/boot/dts/amlogic/meson-g12b-w400.dtsi
>>>>
>>>> I have schematics for the devices, but can only share those privately
>>>> on request.
>>>>
>>>> For testing I am booting LibreELEC from SD card. The box has a 4TB
>>>> SATA drive internally connected with a USB > SATA bridge, see dmesg:
>>>> http://ix.io/2yLh and I connect a USB stick with a 4GB ISO file that I
>>>> copy to the internal SATA drive. Within 10-20 seconds of starting the
>>>> copy the box deadlocks needing a hard power cycle to recover. The
>>>> timing of the deadlock is variable but the device _always_ deadlocks.
>>>> Although I am using a simple copy use-case, there are similar reports
>>>> in Armbian forums performing tasks like installs/updates that involve
>>>> I/O loads.
>>>>
>>>> Following advice in the #linux-amlogic IRC channel I added
>>>> CONFIG_SOFTLOCKUP_DETECTOR and CONFIG_DETECT_HUNG_TASK and was able to
>>>> get output on the HDMI screen (it is not possible to connect to UART
>>>> pins without destroying the box case). If you advance the following
>>>> video frame by frame in VLC you can see the output:
>>>>
>>>> https://www.dropbox.com/s/klvcizim8cs5lze/lockup_clip.mov?dl=0
>>>
>>> Try with this patch:
>>>
>>> https://lore.kernel.org/linux-block/20200925191902.543953-1-shakeelb@google.com/
>>
>> It still locks up approx. 25 seconds into the copy operation. Here’s the output in video again (a little blurry):
>>
>> https://www.dropbox.com/s/3j2czaq509arg6g/lockup_clip2.mov?dl=0
>
> Can you try and set CONFIG_SLUB in your .config instead of CONFIG_SLAB?
CONFIG_SLUB is already set, here’s the full defconfig http://paste.ubuntu.com/p/5BNdZv6J3c/
# dmesg | grep -i slub
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=6, Nodes=1
> Also, just take a picture, should be easier to get readable than a video.
> And the static trace is all that is needed.
This is from a GT-King Pro which someone reminded me has a large RS232 port on the rear:
https://pastebin.com/raw/sGtzgreN
Christian
next prev parent reply other threads:[~2020-09-26 12:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 7:55 Deadlock under load with Linux 5.9 and other recent kernels Christian Hewitt
2020-09-26 10:51 ` Jens Axboe
2020-09-26 11:55 ` Christian Hewitt
2020-09-26 12:13 ` Jens Axboe
2020-09-26 12:28 ` Christian Hewitt [this message]
2020-09-28 1:37 ` Christian Hewitt
2020-09-28 11:06 ` Patrik Nilsson
2020-09-28 13:36 ` Christian Hewitt
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=91886A80-8164-4699-8662-E7D3444A4F12@gmail.com \
--to=christianshewitt@gmail.com \
--cc=axboe@kernel.dk \
--cc=bjharper@gmail.com \
--cc=furkan@fkardame.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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