From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [GIT PULL] ext2, quota, and udf fixes for 6.6-rc1
Date: Fri, 24 Nov 2023 18:47:14 +0200 [thread overview]
Message-ID: <ZWDTkmQZ7uojegiS@smile.fi.intel.com> (raw)
In-Reply-To: <5884527d-a4a2-44e2-96bc-4b300c9e2fb8@leemhuis.info>
On Wed, Nov 22, 2023 at 09:15:06AM +0100, Linux regression tracking #update (Thorsten Leemhuis) wrote:
> On 22.10.23 15:46, Linux regression tracking #adding (Thorsten Leemhuis)
> wrote:
> > On 17.10.23 12:27, Andy Shevchenko wrote:
> >> On Wed, Aug 30, 2023 at 12:24:34PM +0200, Jan Kara wrote:
> >>> Hello Linus,
> >>>
> >>> could you please pull from
> >>>
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_v6.6-rc1
> >>
> >> This merge commit (?) broke boot on Intel Merrifield.
> >> It has earlycon enabled and only what I got is watchdog
> >> trigger without a bit of information printed out.
> >>
> >> I tried to give a two bisects with the same result.
> >
> > #regzbot ^introduced 024128477809f8
> > #regzbot title quota: boot on Intel Merrifield after merge commit
> > 1500e7e0726e
> > #regzbot ignore-activity
>
> Removing this from the tracking. To quote Linus from
> https://lore.kernel.org/all/CAHk-=wgEHNFHpcvnp2X6-fjBngrhPYO=oHAR905Q_qk-njV31A@mail.gmail.com/
>
> """
> The quota thing remains unexplained, and honestly seems like a timing
> issue that just happens to hit Andy. Very strange, but I suspect that
> without more reports (that may or may not ever happen), we're stuck.
> """
>
> No other reports showed up afaik.
Yeah, have no time to dig into this more... Maybe later, who knows?
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-11-24 16:47 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 10:24 [GIT PULL] ext2, quota, and udf fixes for 6.6-rc1 Jan Kara
2023-08-30 19:50 ` pr-tracker-bot
2023-10-17 10:27 ` Andy Shevchenko
2023-10-17 10:29 ` Andy Shevchenko
2023-10-17 10:32 ` Andy Shevchenko
2023-10-17 11:36 ` Jan Kara
2023-10-17 11:49 ` Andy Shevchenko
2023-10-17 11:46 ` Andy Shevchenko
2023-10-17 13:32 ` Jan Kara
2023-10-17 13:42 ` Andy Shevchenko
2023-10-17 14:50 ` Andy Shevchenko
2023-10-17 15:14 ` Andy Shevchenko
2023-10-17 15:34 ` Andy Shevchenko
2023-10-17 16:02 ` Andy Shevchenko
2023-10-18 18:46 ` Jan Kara
2023-10-19 8:46 ` Andy Shevchenko
2023-10-19 10:18 ` Jan Kara
2023-10-19 12:01 ` Andy Shevchenko
2023-10-19 14:12 ` Andy Shevchenko
2023-10-19 14:49 ` Andy Shevchenko
2023-10-19 14:44 ` Andy Shevchenko
2023-10-19 16:42 ` Josh Poimboeuf
2023-10-19 17:05 ` Andy Shevchenko
2023-10-19 17:26 ` Linus Torvalds
2023-10-19 17:51 ` Linus Torvalds
2023-10-19 18:10 ` Andy Shevchenko
2023-10-19 18:16 ` Andy Shevchenko
2023-10-19 18:43 ` Linus Torvalds
2023-10-20 14:51 ` Andy Shevchenko
2023-10-20 15:06 ` Andy Shevchenko
2023-10-20 15:12 ` Andy Shevchenko
2023-10-20 17:26 ` Linus Torvalds
2023-10-20 18:09 ` Jan Kara
2023-10-21 1:48 ` Baokun Li
2023-10-23 12:19 ` Andy Shevchenko
2023-10-23 13:40 ` Baokun Li
2023-10-20 17:23 ` Linus Torvalds
2023-10-20 18:29 ` Andy Shevchenko
2023-10-20 18:31 ` Andy Shevchenko
2023-10-20 19:43 ` Linus Torvalds
2023-10-20 20:36 ` andy.shevchenko
2023-10-21 23:36 ` Kees Cook
2023-10-23 11:45 ` Andy Shevchenko
2023-10-23 12:15 ` Jan Kara
2023-10-23 16:08 ` Kees Cook
2023-10-20 18:05 ` Jan Kara
2023-10-20 20:29 ` andy.shevchenko
2023-10-20 11:07 ` Jan Kara
2023-10-22 13:46 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-11-22 8:15 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-24 16:47 ` Andy Shevchenko [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=ZWDTkmQZ7uojegiS@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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).