public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Greg KH <gregkh@suse.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [GIT PATCH] driver core merge for 3.3
Date: Fri, 6 Jan 2012 22:31:48 +0000	[thread overview]
Message-ID: <20120106223148.GN20752@decadent.org.uk> (raw)
In-Reply-To: <20120106220608.GA20623@suse.de>

On Fri, Jan 06, 2012 at 02:06:08PM -0800, Greg KH wrote:
> On Fri, Jan 06, 2012 at 10:38:41PM +0100, Geert Uytterhoeven wrote:
> > On Fri, Jan 6, 2012 at 21:11, Greg KH <gregkh@suse.de> wrote:
> > > Ben Hutchings (1):
> > >      topology: Provide CPU topology in sysfs in !SMP configurations
> > 
> > FWIW, as reported before, I can confirm that 3.2.0-next-20120106 crashes
> > on m68k during boot:
[...]
> > Disabling lock debugging due to kernel taint
> > Kernel panic - not syncing: Attempted to kill init!
> > 
> > Reverting the above commit (ccbc60d3e19a1b6ae66ca0d89b3da02dde62088b)
> > fixes it.
> > 
> > So to preserve bisectability, you may want to drop this ommit until the
> > UP-only archs have been fixed.
> 
> Ick, sorry for missing that report, you are right.
> 
> Ben, I thought this patch was for UP systems, how did this work on your
> testing?

It works just fine on UP x86.  However I have been made aware that
it breaks on m68k and I told you as much in
<1325462025.13595.189.camel@deadeye>:

> None of these architectures appears to call register_cpu():
> 
>     c6x frv h8300 m68k microblaze openrisc score um xtensa
> 
> and therefore they will all panic at boot following this change (commit
> ccbc60d3e19a1b6ae66ca0d89b3da02dde62088b).  So either I can try to fix
> them or else it must be reverted for now.

Ben.

> Linus, can you revert this, or I can if you want me to.
> 
> thanks,
> 
> greg k-h
> 

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
                                                              - Albert Camus

  reply	other threads:[~2012-01-06 22:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-06 20:11 [GIT PATCH] driver core merge for 3.3 Greg KH
2012-01-06 21:38 ` Geert Uytterhoeven
2012-01-06 22:06   ` Greg KH
2012-01-06 22:31     ` Ben Hutchings [this message]
2012-01-07 19:29       ` Linus Torvalds
2012-01-13  1:11 ` Linus Torvalds
2012-01-13  1:39   ` Kay Sievers
2012-01-13  1:46     ` Linus Torvalds
2012-01-13 18:24     ` Greg KH
2012-01-13 19:03     ` Dirk Gouders

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=20120106223148.GN20752@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@suse.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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