From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Justin P. Mattock" Subject: Re: [Bug #14012] latest git fried my x86_64 imac Date: Thu, 27 Aug 2009 11:01:46 -0700 Message-ID: <4A96CA0A.90405@gmail.com> References: <_yaHeGjHEzG.A.NXH.BtGlKB@chimera> <4A9481B9.3070607@gmail.com> <200908262306.38464.rjw@sisk.pl> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=I8uGQgh1rdZ8h2GJbsFqE35lPnjvJP/GnEmZHjFlRec=; b=YkBMRB6NE3DS6F62qUlaLZqGsj5bnIdodBQYAu6lHxPsoYPHyrRNuYdUDcYAduZigr SFWSdpLcDfJW8txG4YMAn8pk6aBDWHxJTdYVoJxppLM0KrevSnXhfbNU/g9Xxs+zapM3 KIklyOqycFqRdjq5ng8zXFsAzrLvSvdR2Py88= In-Reply-To: <200908262306.38464.rjw-KKrjLPT3xs0@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii"; format="flowed" To: "Rafael J. Wysocki" Cc: Linux Kernel Mailing List , Kernel Testers List , Peter Zijlstra , Ingo Molnar 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 >>> 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 > 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-u79uwXL29TY76Z2rM5mHXA@public.gmane.org > 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. Justin P. Mattock