linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Mark Brown <broonie@kernel.org>
Cc: "kernel test robot" <oliver.sang@intel.com>,
	oe-lkp@lists.linux.dev, lkp@intel.com,
	"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Jiri Slaby" <jirislaby@kernel.org>,
	"Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"Dhruva Gole" <d-gole@ti.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"John Ogness" <john.ogness@linutronix.de>,
	"Johan Hovold" <johan@kernel.org>,
	"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
	"Vignesh Raghavendra" <vigneshr@ti.com>
Subject: Re: [PATCH v5 3/3] serial: core: Fix serial core controller port name to show controller id
Date: Thu, 3 Aug 2023 09:52:49 +0300	[thread overview]
Message-ID: <20230803065249.GF14799@atomide.com> (raw)
In-Reply-To: <ca09d15f-50ab-452c-a3d5-f2b4cde6426f@sirena.org.uk>

* Mark Brown <broonie@kernel.org> [230802 18:20]:
> On Wed, Aug 02, 2023 at 04:15:28PM +0800, kernel test robot wrote:
> 
> > kernel test robot noticed machine hang on:
> 
> > commit: 4de64f4800a581e7eeba6392b3b2ce2131195145 ("[PATCH v5 3/3] serial: core: Fix serial core controller port name to show controller id")
> > url: https://github.com/intel-lab-lkp/linux/commits/Tony-Lindgren/serial-core-Controller-id-cannot-be-negative/20230725-134452
> > base: https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty.git tty-testing
> > patch link: https://lore.kernel.org/all/20230725054216.45696-4-tony@atomide.com/
> > patch subject: [PATCH v5 3/3] serial: core: Fix serial core controller port name to show controller id
> > 
> > in testcase: boot
> > 
> > compiler: gcc-12
> > test machine: 96 threads 2 sockets Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz (Cascade Lake) with 512G memory
> 
> I've also bisected this commit as causing boot hangs on at least the
> i.MX8MP-EVK, though most of the boards in my lab and a huge swathe of
> those in KernelCI are out:
> 
>    https://linux.kernelci.org/test/job/next/branch/master/kernel/next-20230802/plan/baseline/
> 
> which is having a pretty devastating effect on -next testing.

Yes sorry about that, I should have noticed it right away. I thought I
still had my test machine set to use the console=DEVNAME:0.0 style
naming and I mostly test over ssh and was just looking at the DEVNAME.

Regards,

Tony

  reply	other threads:[~2023-08-03  6:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25  5:42 [PATCH v5 0/3] Serial core controller port device name fixes Tony Lindgren
2023-07-25  5:42 ` [PATCH v5 1/3] serial: core: Controller id cannot be negative Tony Lindgren
2023-07-25  5:42 ` [PATCH v5 2/3] serial: core: Fix serial core port id to not use port->line Tony Lindgren
2023-07-25  5:42 ` [PATCH v5 3/3] serial: core: Fix serial core controller port name to show controller id Tony Lindgren
2023-07-25  9:07   ` Andy Shevchenko
2023-07-26  3:28     ` Tony Lindgren
2023-07-31 15:14     ` Greg Kroah-Hartman
2023-07-31 20:02       ` Andy Shevchenko
     [not found]   ` <202308021529.35b3ad6c-oliver.sang@intel.com>
2023-08-02  9:23     ` Tony Lindgren
2023-08-02  9:39       ` Greg Kroah-Hartman
2023-08-02 10:47         ` Tony Lindgren
2023-08-02 11:52           ` Tony Lindgren
2023-08-02 18:19     ` Mark Brown
2023-08-03  6:52       ` Tony Lindgren [this message]
2023-08-03 22:18   ` Guenter Roeck
2023-08-04  4:20     ` Andy Shevchenko
2023-08-04  4:38       ` Guenter Roeck

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=20230803065249.GF14799@atomide.com \
    --to=tony@atomide.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=broonie@kernel.org \
    --cc=d-gole@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=johan@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).