All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: James Hogan <james.hogan@imgtec.com>
Cc: Petr Mladek <pmladek@suse.com>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Tejun Heo <tj@kernel.org>,
	linux-metag@vger.kernel.org
Subject: Re: qemu:metag image runtime failure in -next due to 'kthread: allow to cancel kthread work'
Date: Fri, 16 Sep 2016 14:37:18 -0700	[thread overview]
Message-ID: <20160916213718.GA32384@roeck-us.net> (raw)
In-Reply-To: <20160916212720.GA18931@jhogan-linux.le.imgtec.org>

On Fri, Sep 16, 2016 at 10:27:20PM +0100, James Hogan wrote:
> On Fri, Sep 16, 2016 at 01:38:19PM -0700, Guenter Roeck wrote:
> > Hi,
> > 
> > I see the following runtime error in -next when running a metag qemu emulation.
> > 
> > [ ... ]
> > workingset: timestamp_bits=30 max_order=16 bucket_order=0
> > io scheduler noop registered (default)
> > brd: module loaded
> > Warning: unable to open an initial console.
> > List of all partitions:
> > 0100           16384 ram0  (driver?)
> > No filesystem could mount root, tried: 
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
> > 
> > An example for a complete log is at:
> > http://kerneltests.org/builders/qemu-metag-next/builds/489/steps/qemubuildcommand/logs/stdio
> > 
> > bisect points to commit ef98de028afde ("kthread: allow to cancel kthread work").
> > I don't know (yet) if other architectures are affected. bisect log is attached.
> > 
> > The scripts to run this test are available at
> > https://github.com/groeck/linux-build-test/tree/master/rootfs/metag.
> > 
> > Guenter
> 
> Thanks Guenter,
> 
> It appears to be related to the command line. After that commit the
> command line is shown as empty (rather than your "rdinit=/sbin/init
> doreboot"), but it can still be overridden in the config and then it
> continues to work.
> 
Weird.

> I'll debug a little deeper to see if I can figure out whats going wrong.
> 
Thanks!
Guenter

> Cheers
> James
> 
> > 
> > --
> > # bad: [ddf9d15aed5ba5786cf4b082576c44ce37cd29c2] Add linux-next specific files for 20160916
> > # good: [9395452b4aab7bc2475ef8935b4a4fb99d778d70] Linux 4.8-rc6
> > git bisect start 'HEAD' 'v4.8-rc6'
> > # good: [03593c66538f0dd2c46f14dfdd9c7c0b96d12163] Merge remote-tracking branch 'crypto/master'
> > git bisect good 03593c66538f0dd2c46f14dfdd9c7c0b96d12163
> > # good: [144ff127c1a802bc466cd9fe64033682193c0831] Merge remote-tracking branch 'edac-amd/for-next'
> > git bisect good 144ff127c1a802bc466cd9fe64033682193c0831
> > # good: [cfab536f2992d0db27424f146cf0e13bb4a2c0c4] Merge remote-tracking branch 'staging/staging-next'
> > git bisect good cfab536f2992d0db27424f146cf0e13bb4a2c0c4
> > # good: [f185e7dd5ed5eb7e1a834bde8ad6ea1393737037] Merge remote-tracking branch 'gpio/for-next'
> > git bisect good f185e7dd5ed5eb7e1a834bde8ad6ea1393737037
> > # good: [a69892f0ba574e71154f8c5c647626a7dd065ce5] ipc-msg-avoid-waking-sender-upon-full-queue-checkpatch-fixes
> > git bisect good a69892f0ba574e71154f8c5c647626a7dd065ce5
> > # good: [209370566ef8c38dcea40561db2c46fadb0078ce] Merge tag 'clk-renesas-for-v4.9-tag3' of git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers into clk-next
> > git bisect good 209370566ef8c38dcea40561db2c46fadb0078ce
> > # good: [be3400244f19bb16b16b5dd32d8719e59790f361] Merge remote-tracking branch 'coresight/next'
> > git bisect good be3400244f19bb16b16b5dd32d8719e59790f361
> > # good: [513d99d37db2a9ceb489e7123fb1458b29eeafff] Merge remote-tracking branch 'nvdimm/libnvdimm-for-next'
> > git bisect good 513d99d37db2a9ceb489e7123fb1458b29eeafff
> > # good: [9101ca3b2763583e10ec93a453363a8af3ced438] kthread: add kthread_create_worker*()
> > git bisect good 9101ca3b2763583e10ec93a453363a8af3ced438
> > # bad: [57169cae0bc5472d9d3eee5c0923ae6d5ae8d299] kthread: better support freezable kthread workers
> > git bisect bad 57169cae0bc5472d9d3eee5c0923ae6d5ae8d299
> > # good: [5c204b8f9b8f30bf641095f4005fa320cd192254] kthread: initial support for delayed kthread work
> > git bisect good 5c204b8f9b8f30bf641095f4005fa320cd192254
> > # bad: [26242e2b569d11fbbfdf40c93d9d11329825724a] kthread: allow to modify delayed kthread work
> > git bisect bad 26242e2b569d11fbbfdf40c93d9d11329825724a
> > # bad: [ef98de028afde6861712a208b0e25f6b6af3912a] kthread: allow to cancel kthread work
> > git bisect bad ef98de028afde6861712a208b0e25f6b6af3912a
> > # first bad commit: [ef98de028afde6861712a208b0e25f6b6af3912a] kthread: allow to cancel kthread work

WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux-0h96xk9xTtrk1uMJSBkQmQ@public.gmane.org>
To: James Hogan <james.hogan-1AXoQHu6uovQT0dZR+AlfA@public.gmane.org>
Cc: Petr Mladek <pmladek-IBi9RG/b67k@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Andrew Morton
	<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
	Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
	linux-metag-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: qemu:metag image runtime failure in -next due to 'kthread: allow to cancel kthread work'
Date: Fri, 16 Sep 2016 14:37:18 -0700	[thread overview]
Message-ID: <20160916213718.GA32384@roeck-us.net> (raw)
In-Reply-To: <20160916212720.GA18931-4bYivNCBEGTR3KXKvIWQxtm+Uo4AYnCiHZ5vskTnxNA@public.gmane.org>

On Fri, Sep 16, 2016 at 10:27:20PM +0100, James Hogan wrote:
> On Fri, Sep 16, 2016 at 01:38:19PM -0700, Guenter Roeck wrote:
> > Hi,
> > 
> > I see the following runtime error in -next when running a metag qemu emulation.
> > 
> > [ ... ]
> > workingset: timestamp_bits=30 max_order=16 bucket_order=0
> > io scheduler noop registered (default)
> > brd: module loaded
> > Warning: unable to open an initial console.
> > List of all partitions:
> > 0100           16384 ram0  (driver?)
> > No filesystem could mount root, tried: 
> > Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
> > 
> > An example for a complete log is at:
> > http://kerneltests.org/builders/qemu-metag-next/builds/489/steps/qemubuildcommand/logs/stdio
> > 
> > bisect points to commit ef98de028afde ("kthread: allow to cancel kthread work").
> > I don't know (yet) if other architectures are affected. bisect log is attached.
> > 
> > The scripts to run this test are available at
> > https://github.com/groeck/linux-build-test/tree/master/rootfs/metag.
> > 
> > Guenter
> 
> Thanks Guenter,
> 
> It appears to be related to the command line. After that commit the
> command line is shown as empty (rather than your "rdinit=/sbin/init
> doreboot"), but it can still be overridden in the config and then it
> continues to work.
> 
Weird.

> I'll debug a little deeper to see if I can figure out whats going wrong.
> 
Thanks!
Guenter

> Cheers
> James
> 
> > 
> > --
> > # bad: [ddf9d15aed5ba5786cf4b082576c44ce37cd29c2] Add linux-next specific files for 20160916
> > # good: [9395452b4aab7bc2475ef8935b4a4fb99d778d70] Linux 4.8-rc6
> > git bisect start 'HEAD' 'v4.8-rc6'
> > # good: [03593c66538f0dd2c46f14dfdd9c7c0b96d12163] Merge remote-tracking branch 'crypto/master'
> > git bisect good 03593c66538f0dd2c46f14dfdd9c7c0b96d12163
> > # good: [144ff127c1a802bc466cd9fe64033682193c0831] Merge remote-tracking branch 'edac-amd/for-next'
> > git bisect good 144ff127c1a802bc466cd9fe64033682193c0831
> > # good: [cfab536f2992d0db27424f146cf0e13bb4a2c0c4] Merge remote-tracking branch 'staging/staging-next'
> > git bisect good cfab536f2992d0db27424f146cf0e13bb4a2c0c4
> > # good: [f185e7dd5ed5eb7e1a834bde8ad6ea1393737037] Merge remote-tracking branch 'gpio/for-next'
> > git bisect good f185e7dd5ed5eb7e1a834bde8ad6ea1393737037
> > # good: [a69892f0ba574e71154f8c5c647626a7dd065ce5] ipc-msg-avoid-waking-sender-upon-full-queue-checkpatch-fixes
> > git bisect good a69892f0ba574e71154f8c5c647626a7dd065ce5
> > # good: [209370566ef8c38dcea40561db2c46fadb0078ce] Merge tag 'clk-renesas-for-v4.9-tag3' of git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-drivers into clk-next
> > git bisect good 209370566ef8c38dcea40561db2c46fadb0078ce
> > # good: [be3400244f19bb16b16b5dd32d8719e59790f361] Merge remote-tracking branch 'coresight/next'
> > git bisect good be3400244f19bb16b16b5dd32d8719e59790f361
> > # good: [513d99d37db2a9ceb489e7123fb1458b29eeafff] Merge remote-tracking branch 'nvdimm/libnvdimm-for-next'
> > git bisect good 513d99d37db2a9ceb489e7123fb1458b29eeafff
> > # good: [9101ca3b2763583e10ec93a453363a8af3ced438] kthread: add kthread_create_worker*()
> > git bisect good 9101ca3b2763583e10ec93a453363a8af3ced438
> > # bad: [57169cae0bc5472d9d3eee5c0923ae6d5ae8d299] kthread: better support freezable kthread workers
> > git bisect bad 57169cae0bc5472d9d3eee5c0923ae6d5ae8d299
> > # good: [5c204b8f9b8f30bf641095f4005fa320cd192254] kthread: initial support for delayed kthread work
> > git bisect good 5c204b8f9b8f30bf641095f4005fa320cd192254
> > # bad: [26242e2b569d11fbbfdf40c93d9d11329825724a] kthread: allow to modify delayed kthread work
> > git bisect bad 26242e2b569d11fbbfdf40c93d9d11329825724a
> > # bad: [ef98de028afde6861712a208b0e25f6b6af3912a] kthread: allow to cancel kthread work
> > git bisect bad ef98de028afde6861712a208b0e25f6b6af3912a
> > # first bad commit: [ef98de028afde6861712a208b0e25f6b6af3912a] kthread: allow to cancel kthread work


  reply	other threads:[~2016-09-16 21:37 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 20:38 qemu:metag image runtime failure in -next due to 'kthread: allow to cancel kthread work' Guenter Roeck
2016-09-16 21:27 ` James Hogan
2016-09-16 21:27   ` James Hogan
2016-09-16 21:37   ` Guenter Roeck [this message]
2016-09-16 21:37     ` Guenter Roeck
2016-09-16 23:32     ` James Hogan
2016-09-16 23:32       ` James Hogan
2016-09-16 23:32       ` [kernel-hardening] " James Hogan
2016-09-17  2:58       ` Kees Cook
2016-09-17  2:58         ` Kees Cook
2016-09-17  2:58         ` [kernel-hardening] " Kees Cook
2016-09-19 13:59         ` James Hogan
2016-09-19 13:59           ` James Hogan
2016-09-19 13:59           ` [kernel-hardening] " James Hogan
2016-09-19 19:53           ` Kees Cook
2016-09-19 19:53             ` [kernel-hardening] " Kees Cook
2016-09-19 21:37             ` James Hogan
2016-09-19 21:37               ` James Hogan
2016-09-19 21:37               ` [kernel-hardening] " James Hogan
2016-09-19 21:51               ` Kees Cook
2016-09-19 21:51                 ` [kernel-hardening] " Kees Cook
2016-09-19 22:57                 ` James Hogan
2016-09-19 22:57                   ` James Hogan
2016-09-19 22:57                   ` [kernel-hardening] " James Hogan
2016-09-19 23:19                   ` Kees Cook
2016-09-19 23:19                     ` Kees Cook
2016-09-19 23:19                     ` [kernel-hardening] " Kees Cook
2016-09-19 14:55       ` James Hogan
2016-09-19 14:55         ` James Hogan
2016-09-19 14:55         ` [kernel-hardening] " James Hogan
2016-09-19 15:45         ` Guenter Roeck
2016-09-19 15:45           ` Guenter Roeck
2016-09-19 15:45           ` [kernel-hardening] " Guenter Roeck
2016-09-27 10:12           ` Petr Mladek
2016-09-27 10:12             ` Petr Mladek
2016-09-27 10:12             ` [kernel-hardening] " Petr Mladek
2016-09-27 10:19             ` James Hogan
2016-09-27 10:19               ` James Hogan
2016-09-27 10:19               ` [kernel-hardening] " James Hogan

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=20160916213718.GA32384@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=james.hogan@imgtec.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-metag@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=tj@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.