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 -- Jiri Kosina - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
- From: Jiri Kosina <[email protected]>
- dwarf2 stuck Re: lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
- From: Andi Kleen <[email protected]>
- dwarf2 stuck Re: lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
- From: "Jan Beulich" <[email protected]>
- Re: dwarf2 stuck Re: lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
- From: Jiri Kosina <[email protected]>
- Re: dwarf2 stuck Re: lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
- From: "Jan Beulich" <[email protected]>
- lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
- Prev by Date: RE: Ondemand/Conservative not working with 2.6.18
- Next by Date: [PATCH] FRV: Use the correct preemption primitives in kmap_atomic() and co [try #2]
- Previous by thread: Re: dwarf2 stuck Re: lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
- Next by thread: Re: dwarf2 stuck Re: lockdep warning in i2c_transfer() with dibx000 DVB - input tree merge plans?
- Index(es):
 |