From: "Theodore Ts'o" <tytso@mit.edu>
To: "Đỗ Văn Ngọc (VF-KHTVPMDDT-TTTKLKDDT)" <v.ngocdv4@vinfast.vn>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: File system hung on kernel 4.14
Date: Mon, 30 Oct 2023 23:05:45 -0400 [thread overview]
Message-ID: <20231031030545.GB9741@mit.edu> (raw)
In-Reply-To: <fee3ba3c4b9205afc1b60aa981193fb28deab7f3.camel@vinfast.vn>
On Mon, Oct 30, 2023 at 07:37:09AM +0000, Đỗ Văn Ngọc (VF-KHTVPMDDT-TTTKLKDDT) wrote:
> Dear Linux kernel ext4, Dear Ted,
>
> We are developing project on Android 9 which used kernel 4.14.133
> version.
> And while normal using device, we have a issue device freezing and
> reboot after few minute.
> I checked the log and saw kernel hung on filesystem as below:
I've already replied to your first e-mail sent directly to me. It
appears to be a hardware problem, or possibly a device driver issue.
But it's not a file system issue. Basically, ext4 submitted an I/O,
and then calls io_schedule(), and I/O never completes....
- Ted
[15159.874154] Call trace:
[15159.874157] [<000000005e1d80e5>] __switch_to+0x94/0xd8
[15159.874161] [<00000000a85c7184>] __schedule+0x274/0x940
[15159.874163] [<00000000c9c2c8f0>] schedule+0x40/0xa8
[15159.874167] [<00000000a97520e1>] io_schedule+0x20/0x40
[15159.874175] [<000000008d5c36d0>] blk_mq_get_tag+0x194/0x340
[15159.874178] [<00000000f97393cb>] blk_mq_get_request+0x164/0x3b0
[15159.874181] [<00000000e69c8e58>] blk_mq_make_request+0xc8/0x6f8
[15159.874187] [<00000000e88e7453>] generic_make_request+0xf4/0x288
[15159.874190] [<0000000016cf2add>] submit_bio+0x5c/0x1d0
[15159.874196] [<0000000097be4708>] ext4_io_submit+0x54/0x68
[15159.874199] [<00000000e9c80f00>] ext4_bio_write_page+0x1b0/0x528
[15159.874202] [<000000009bf94bad>] mpage_submit_page+0x60/0x90
[15159.874205] [<00000000da1a9585>] mpage_map_and_submit_buffers+0x138/0x238
[15159.874208] [<00000000c84c3e14>] ext4_writepages+0x8dc/0xe08
[15159.874214] [<000000007a345b10>] do_writepages+0x5c/0x108
[15159.874217] [<00000000ef1a522d>] __writeback_single_inode+0x48/0x4f8
[15159.874220] [<00000000aeac1ba5>] writeback_sb_inodes+0x1c0/0x470
[15159.874223] [<00000000f7f818b4>] __writeback_inodes_wb+0x78/0xc8
[15159.874225] [<00000000ae30bb56>] wb_writeback+0x24c/0x3d8
[15159.874228] [<00000000b489a91f>] wb_workfn+0x1c4/0x490
[15159.874233] [<000000004df896a9>] process_one_work+0x1d8/0x498
[15159.874236] [<00000000d7fa6dd7>] worker_thread+0x4c/0x478
[15159.874240] [<00000000f46ec2f2>] kthread+0x138/0x140
[15159.874243] [<000000009e914ea4>] ret_from_fork+0x10/0x1c
prev parent reply other threads:[~2023-10-31 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 7:37 File system hung on kernel 4.14 Đỗ Văn Ngọc (VF-KHTVPMDDT-TTTKLKDDT)
2023-10-31 3:05 ` Theodore Ts'o [this message]
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=20231031030545.GB9741@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=v.ngocdv4@vinfast.vn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.