On Tue, 12 Feb 2008 15:03:41 +0100 Fabio Coatti wrote: > Hi all, > I'm stuck in a weird situation: I'm unable to go beyond 2.6.23.14, so to fix > the splice bug I've had to apply by hand the patch. (x86_64) > > Basically, with 2.6.24.2 (the same with 2.6.24 and .1), tha machine won't > boot > due to a problem with cciss driver, that prevents to find the / partition. > (bug described here: Kernel Bug Tracker Bug 9859 > http://bugzilla.kernel.org/show_bug.cgi?id=9859 ); > > With kernels 2.6.23, the lastest that I can compile is 2.6.23.14; starting > from .15 (and .16) I get this message: > > ====================== > UPD include/linux/compile.h > CC init/version.o > LD init/built-in.o > LD .tmp_vmlinux1 > drivers/built-in.o: In function `acpi_init': > bus.c:(.init.text+0x1713): undefined reference to `pm_flags' > bus.c:(.init.text+0x1756): undefined reference to `pm_flags' > ====================== > > All .config are the same, (make oldconfig) beside the obvious differences > between .23 and .24 > > Hardware: x86_64 AMD 2216HE > SCSI controller: HP Smart Array E200i Controller > Compiler: gcc (GCC) 4.1.1 > binutils: 2.16.1 > > On a x86 machine, Intel(R) Xeon(TM) CPU 3.20GHz > with a cciss0: HP Smart Array 6i Controller, > the 2.6.24.2 compiles just fine and works, so the cciss problems seems > related > only to E200i controller. > > Right now, on AMD64 machines, I'm forced to patch by hand the kernel, that's > quite uncomfortable :) > > Can someone point me in the right direction to get out of this situation? Of > course I can provide any further information. (.config not inlcuded now to > avoid cluttering ) > > Thanks for any answer.
a/ send .config file for the build problem above b/ How do you download and/or apply 2.6.23.{15,16} ? Full tarball or base tarball + patches? If patches, what base tree are they applied to? --- ~Randy -- 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/