The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: kernel test robot <lkp@intel.com>
Cc: Jon Mason <jdmason@kudzu.us>, Dave Jiang <dave.jiang@intel.com>,
	Allen Hubbe <allenbh@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	lkp@01.org
Subject: Re: [NTB] 26b3a37b92: WARNING:at_kernel/params.c:#param_sysfs_init
Date: Fri, 26 Jul 2019 12:08:39 -0600	[thread overview]
Message-ID: <36d29c75-07bb-8e79-feeb-4e6dc96124df@deltatee.com> (raw)
In-Reply-To: <20190726082329.GF22106@shao2-debian>



On 2019-07-26 2:23 a.m., kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-4.9):
> 
> commit: 26b3a37b928457ba2cd98eaf6d7b0feca5a30fa6 ("NTB: Introduce MSI library")
> https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master
> 
> in testcase: locktorture
> with following parameters:
> 
> 	runtime: 300s
> 	test: cpuhotplug
> 
> test-description: This torture test consists of creating a number of kernel threads which acquire the lock and hold it for specific amount of time, thus simulating different critical region behaviors.
> test-url: https://www.kernel.org/doc/Documentation/locking/locktorture.txt
> 
> 
> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 2G
> 
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> 
> 
> +----------------------------------------------+------------+------------+
> |                                              | d217e07b32 | 26b3a37b92 |
> +----------------------------------------------+------------+------------+
> | boot_successes                               | 4          | 0          |
> | boot_failures                                | 0          | 4          |
> | WARNING:at_kernel/params.c:#param_sysfs_init | 0          | 4          |
> | RIP:param_sysfs_init                         | 0          | 4          |
> +----------------------------------------------+------------+------------+
> 

Oh shoot.

This confusing report is caused by me accidentally leaving the MODULE_
defines in a file that ended up not being a module. I'll send a patch ASAP.

Logan



      reply	other threads:[~2019-07-26 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-26  8:23 [NTB] 26b3a37b92: WARNING:at_kernel/params.c:#param_sysfs_init kernel test robot
2019-07-26 18:08 ` Logan Gunthorpe [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=36d29c75-07bb-8e79-feeb-4e6dc96124df@deltatee.com \
    --to=logang@deltatee.com \
    --cc=allenbh@gmail.com \
    --cc=dave.jiang@intel.com \
    --cc=jdmason@kudzu.us \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=lkp@intel.com \
    --cc=torvalds@linux-foundation.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