From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: "Stephen E. Baker" <baker.stephen.e@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: simplify ext4_sb_read_encoding regression
Date: Thu, 02 Jun 2022 13:47:03 -0400 [thread overview]
Message-ID: <874k13t0tk.fsf@collabora.com> (raw)
In-Reply-To: <CAFDdnB3U67YJ7pivdHQaMB-CkdmvvTbcpxp1FXxBmFyAgJPknw@mail.gmail.com> (Stephen E. Baker's message of "Mon, 30 May 2022 18:27:29 -0400")
"Stephen E. Baker" <baker.stephen.e@gmail.com> writes:
> On Mon, May 30, 2022 at 10:21 AM Gabriel Krisman Bertazi
> <krisman@collabora.com> wrote:
>>
>> "Stephen E. Baker" <baker.stephen.e@gmail.com> writes:
>>
>> > Hello,
>> >
>> > I have a Samsung Chromebook Plus (rk3399-gru-kevin) which boots linux
>> > off an external ssd plugged into USB. The root filesystem is ext4 with
>> > unicode support, case folding is enabled only on some directories in
>> > my home directory.
>> >
>> > Since 5.17 the system has been unbootable. I ran a git bisect and it
>> > pointed to aa8bf298a96acaaaa3af07d09cf7ffeb9798e48a ext4: simplify
>> > ext4_sb_read_encoding
>>
>> Hi Stephen,
>>
>> This series moved the UTF-8 data tables to a kernel module; before it,
>> the module had to be built-in.
>>
>> Since you have your rootfs as a case-insensitive filesystem, either the
>> utf8data module needs to be available in the initramfs or unicode
>> needs to be built-in. Are you building your own kernel?
>>
>> Can you confirm that utf8data.ko exists in your initramfs, and
>> regenerate it if missing? Alternatively, make sure that you have
>> CONFIG_UNICODE=y in your kernel configuration file.
>>
> Thanks Gabriel, I've verified that CONFIG_UNICODE=y, as well as
> CONFIG_UNICODE_UTF8_DATA which exists in this patch for that
> purpose, though it was removed earlier.
Thanks for checking. Indeed, UNICODE_UTF8_DATA was just transitional,
and went away right before being part of a release. CONFIG_UNICODE=y
should have adressed it, if it was a problem with module not being
available early enough.
>
>> If that doesn't work, can you provide the kernel log? If you can't
>> collect the console output, a photo of the screen displaying the error
>> will suffice.
>>
> I don't have any output to provide unfortunately. It fails before the
> backlight turns on, and nothing is written to disk. I seem to remember
> that someone else at Collabora had figured out a way to get a serial
> console on this device - perhaps Tomeu. I'm not equipped for that
> personally, particularly if it involves soldering.
I'm following the discussion with Ted on the other subthread, but I
don't have anything to add at the moment other than what is already
said.
Nothing stands out on that commit specifically and I couldn't reproduce
it in a vm. I've reached out to Tomeu to get my hands on that exact
chromebook, to try to reproduce it there. I will report back with my
findings.
--
Gabriel Krisman Bertazi
next prev parent reply other threads:[~2022-06-02 17:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 22:55 simplify ext4_sb_read_encoding regression Stephen E. Baker
2022-05-30 14:21 ` Gabriel Krisman Bertazi
2022-05-30 22:27 ` Stephen E. Baker
2022-05-31 0:56 ` Dave Chinner
2022-05-31 2:39 ` Stephen E. Baker
2022-06-02 17:47 ` Gabriel Krisman Bertazi [this message]
2022-06-05 0:11 ` Stephen E. Baker
2022-06-05 3:21 ` Stephen E. Baker
2022-06-05 6:23 ` Gabriel Krisman Bertazi
2022-06-05 13:56 ` Stephen E. Baker
[not found] <CAFDdnB1Rq3vNe_qt_0u+inzOuL4vrGhgbOoQZKBwfBktni=Npw@mail.gmail.com>
2022-05-29 1:24 ` Theodore Ts'o
2022-05-29 12:19 ` Theodore Ts'o
2022-05-29 22:49 ` Stephen E. Baker
2022-05-30 1:49 ` Theodore Ts'o
2022-05-30 22:20 ` Stephen E. Baker
2022-05-31 0:16 ` Theodore Ts'o
2022-05-31 1:37 ` Theodore Ts'o
2022-06-02 2:06 ` Stephen E. Baker
2022-06-02 14:47 ` Theodore Ts'o
2023-04-14 23:01 ` William McVicker
2023-04-16 5:47 ` Christoph Hellwig
2023-04-16 5:56 ` Christoph Hellwig
2023-04-17 3:26 ` Theodore Ts'o
2023-04-17 16:16 ` Will McVicker
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=874k13t0tk.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=baker.stephen.e@gmail.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).