Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750984AbWJPN3V (ORCPT ); Mon, 16 Oct 2006 09:29:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751014AbWJPN3V (ORCPT ); Mon, 16 Oct 2006 09:29:21 -0400 Received: from gwmail.nue.novell.com ([195.135.221.19]:32672 "EHLO emea5-mh.id5.novell.com") by vger.kernel.org with ESMTP id S1750984AbWJPN3U (ORCPT ); Mon, 16 Oct 2006 09:29:20 -0400 Message-Id: <4533A5A5.76E4.0078.0@novell.com> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Date: Mon, 16 Oct 2006 15:30:45 +0200 From: "Jan Beulich" To: "Jiri Kosina" , "Andi Kleen" Cc: Subject: Re: dwarf2 stuck Re: lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans? References: <200610161231.30705.ak@suse.de> <4533991C.76E4.0078.0@novell.com> <45339E57.76E4.0078.0@novell.com> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1025 Lines: 27 >>> Jiri Kosina 16.10.06 15:08 >>> >On Mon, 16 Oct 2006, Jan Beulich wrote: > >> >Yes, it was compiled using gcc 4.0.2, specifically gcc (GCC) 4.0.2 >> >20051125 (Red Hat 4.0.2-8). I can easily reproduce this, what >> >additional information do you need? Or should I just try with newer >> >gcc? >> Two possible paths: >> a) Try with gcc 4.1.x. > >Will do probably later today. > >> b) Send me the offending .o (presumably the one containing >> dibusb_dib3000mc_tuner_attach) > >You can get it from http://www.jikos.cz/jikos/junk/dibusb-common.o Yes, unfortunately this is another instance of gcc 4.0 generating bad unwind data when optimizing and not accumulating outgoing args. Andi - did you already create a patch implementing Michael's suggestion? Jan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/