From: Frank Scheiner <frank.scheiner@web.de>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Sparc kernel list <sparclinux@vger.kernel.org>
Cc: debian-sparc <debian-sparc@lists.debian.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: Regression in 028abd92 for Sun UltraSPARC T1
Date: Mon, 22 Mar 2021 22:55:25 +0100 [thread overview]
Message-ID: <4d033ff9-329e-77e7-20de-720aa65bba3e@web.de> (raw)
In-Reply-To: <186a7992-6e83-dc8a-1cfc-d07bb36935f5@physik.fu-berlin.de>
Hi,
On 22.03.21 22:48, John Paul Adrian Glaubitz wrote:
> On 3/22/21 10:30 PM, Frank Scheiner wrote:
>> Riccardo Mottola first recognized a problem with 5.10.x kernels on his
>> Sun T2000 with UltraSPARC T1 (details in [this thread]). I could verify
>> the problem also on my Sun T1000 and it looks like this specific issue
>> breaks the mounting of the root FS or maybe mounting file systems at
>> all. This affects both booting from disk and from network.
>> (...)
>> ...as first bad commit.
>>
>> ```
>> commit 028abd9222df0cf5855dab5014a5ebaf06f90565
>> Author: Christoph Hellwig <hch@lst.de>
>> Date: Thu Sep 17 10:22:34 2020 +0200
>>
>> fs: remove compat_sys_mount
>>
>> compat_sys_mount is identical to the regular sys_mount now, so
>> remove it
>> and use the native version everywhere.
>> ```
>>
>> [1]:
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=028abd9222df0cf5855dab5014a5ebaf06f90565
>
> Looking at this change, I think it's rather unexpected that this particular
> change would break the kernel on a specific CPU target. Are you sure that
> this is the right bad commit?
Well, I strictly followed the `git bisect` process and tested each and
every proposed revision. It's indeed strange that this only affects
UltraSPARC T1s, but the changes match the behavior: mounting of (root)
FS is broken.
> If you found the right commit, then I assume there is something wrong with
> the syscall handling on UltraSPARC T1.
Could be, all in all the T1 is a first of its kind.
Cheers,
Frank
next prev parent reply other threads:[~2021-03-22 21:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 21:30 Regression in 028abd92 for Sun UltraSPARC T1 Frank Scheiner
2021-03-22 21:48 ` John Paul Adrian Glaubitz
2021-03-22 21:55 ` Frank Scheiner [this message]
2021-03-23 16:50 ` Jan Engelhardt
2021-03-23 16:57 ` Christoph Hellwig
2021-03-23 17:39 ` Frank Scheiner
2021-03-23 22:17 ` Frank Scheiner
2021-03-24 8:28 ` Christoph Hellwig
2021-03-24 12:30 ` Frank Scheiner
2021-03-24 12:42 ` Anatoly Pugachev
2021-03-24 12:48 ` Frank Scheiner
2021-03-24 12:49 ` John Paul Adrian Glaubitz
2021-03-24 13:09 ` Frank Scheiner
2021-03-24 13:16 ` John Paul Adrian Glaubitz
2021-03-24 13:19 ` Frank Scheiner
2021-03-24 13:24 ` Anatoly Pugachev
2021-03-24 13:29 ` Frank Scheiner
2021-03-24 13:57 ` Frank Scheiner
2021-03-24 15:22 ` Jan Engelhardt
2021-03-24 15:58 ` Frank Scheiner
2021-03-24 16:10 ` Christoph Hellwig
2021-03-24 16:33 ` Frank Scheiner
2021-03-24 16:37 ` Frank Scheiner
2021-03-25 7:50 ` Christoph Hellwig
2025-09-02 20:18 ` John Paul Adrian Glaubitz
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=4d033ff9-329e-77e7-20de-720aa65bba3e@web.de \
--to=frank.scheiner@web.de \
--cc=debian-sparc@lists.debian.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=hch@lst.de \
--cc=sparclinux@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 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.