From: "andriy.shevchenko@linux.intel.com" <andriy.shevchenko@linux.intel.com>
To: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Kurmi, Suresh Kumar" <suresh.kumar.kurmi@intel.com>,
"Saarinen, Jani" <jani.saarinen@intel.com>
Subject: Re: Regression on linux-next (next-20250210)
Date: Sun, 16 Feb 2025 22:13:12 +0200 [thread overview]
Message-ID: <Z7JG2BAR0taUWHAU@smile.fi.intel.com> (raw)
In-Reply-To: <SJ1PR11MB6129D6C5644D4A6C858A4F04B9F92@SJ1PR11MB6129.namprd11.prod.outlook.com>
The fix landed upstream, will be in next Linux Next.
c213375e3283 ("serial: 8250_dw: Call dw8250_quirks() conditionally")
On Sat, Feb 15, 2025 at 04:16:58PM +0000, Borah, Chaitanya Kumar wrote:
> Hello Andy,
>
> Hope you are doing well. I am Chaitanya from the linux graphics team in Intel.
>
> This mail is regarding a regression we are seeing in our CI runs[1] on linux-next repository.
>
> Since the version next-20250210 [2], many machines in our CI are unable to boot.
>
> Unfortunately, we have not been able to collect any logs (even from pstore).
>
> However after bisecting the tree, the following patch [3] seems to be the first "bad"
> commit
>
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
> commit bfd3d4a40f3905ec70b17dbfa9b78764e59e4b4f
> Author: Andy Shevchenko mailto:andriy.shevchenko@linux.intel.com
> Date: Mon Feb 3 14:14:56 2025 +0200
>
> serial: 8250_dw: Drop unneeded NULL checks in dw8250_quirks()
>
> Since platform data is being provided for all supported hardware,
> no need to NULL check for it. Drop unneeded checks.
>
> `````````````````````````````````````````````````````````````````````````````````````````````````````````
>
> We also verified that if we revert the patch the issue is not seen.
>
> Could you please check why the patch causes this regression and provide a fix if necessary?
>
> Thank you.
>
> Regards
>
> Chaitanya
>
> [1] https://intel-gfx-ci.01.org/tree/linux-next/combined-alt.html?
> [2] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250210
> [3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?h=next-20250210&id=bfd3d4a40f3905ec70b17dbfa9b78764e59e4b4f
>
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-02-16 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-15 16:16 Regression on linux-next (next-20250210) Borah, Chaitanya Kumar
2025-02-16 20:13 ` andriy.shevchenko [this message]
2025-02-17 8:24 ` Borah, Chaitanya Kumar
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=Z7JG2BAR0taUWHAU@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.saarinen@intel.com \
--cc=linux-serial@vger.kernel.org \
--cc=suresh.kumar.kurmi@intel.com \
/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