On Thu, 27 Aug 2009 21:45:01 +0200 Rafael J. Wysocki wrote: > On Thursday 27 August 2009, Justin P. Mattock wrote: > > Rafael J. Wysocki wrote: > > > On Wednesday 26 August 2009, Justin P. Mattock wrote: > > > > > >> Rafael J. Wysocki wrote: > > >> > > >>> This message has been generated automatically as a part of a report > > >>> of recent regressions. > > >>> > > >>> The following bug entry is on the current list of known regressions > > >>> from 2.6.30. Please verify if it still should be listed and let me know > > >>> (either way). > > >>> > > >>> > > >>> Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14012 > > >>> Subject : latest git fried my x86_64 imac > > >>> Submitter : Justin P. Mattock<justinmattock@xxxxxxxxx> > > >>> Date : 2009-08-13 07:20 (13 days old) > > >>> References : http://marc.info/?l=linux-kernel&m=125014080427090&w=4 > > >>> > > >>> > > >>> > > >>> > > >>> > > >> if I revert this commit: > > >> af6af30c0fcd77e621638e53ef8b176bca8bd3b4 > > >> I can get a normal bootup. > > >> > > > > > > Hm, that's > > > > > > commit af6af30c0fcd77e621638e53ef8b176bca8bd3b4 > > > Author: Peter Zijlstra<peterz@xxxxxxxxxxxxx> > > > Date: Wed Aug 5 20:41:04 2009 +0200 > > > > > > ftrace: Fix perf-tracepoint OOPS > > > > > > I wonder what happens if you compile out ftrace? > > > > > > > > >> As for this bug, it seems I'm the only > > >> hitting this. The system is a fresh LFS build > > >> x86_64. > > >> In regards to keeping this open > > >> not sure, I don't have a problem with closing this > > >> and taking the blame as something I did during my build > > >> of the system, then if this becomes more frequent > > >> then open a new bug. > > >> > > > > > > OK, I'll close it for now. > > > > > > Thanks, > > > Rafael > > > -- > > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > > the body of a message to majordomo@xxxxxxxxxxxxxxx > > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > > Please read the FAQ at http://www.tux.org/lkml/ > > > > > > > > o.k. I tried disabling all of ftrace in the kernel, > > unfortunately the only one left > > is HAVE_FTRACE_SYSCALLS > > which seems to be selected by x86. > > seems the system still sticks > > without reverting perf-tracepoint oops. > > That's kind of strange. Can you attach the .config, please? That's what arch/x86/Kconfig does: ### Arch settings config X86 def_bool y ... select HAVE_FTRACE_SYSCALLS It just means that the $arch has that capability, not that it is enabled. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
