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@xxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html