Re: stuck with 2.6.23.14 on x86_64

On Tuesday, 12 of February 2008, Fabio Coatti wrote:
Alle martedì 12 febbraio 2008, Randy Dunlap ha scritto:
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?


full tarball from kernel.org (.16), tried also applying patches to 2.6.23
vanilla.(.15,.16) Same process leads to successful compilation for .14

You're not supposed to have CONFIG_PM unset and CONFIG_ACPI set at the same
time. The oldconfig generation must have gone wrong at one point.

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/

Relevant Pages

  • Re: automated test? (was Re: Linux 2.6.17.7)
    ... a bug report may not convey the hint "look at this NOW, ... what I was intending with my origional question was a series of simple 'does it compile' tests that try all the config options that are affected by the patchset in question. ... obviously such a test can't be done on the huge -rc patches, but for -stable patches ... Given a patch that modifies file X is it possible to know what config options could be affected? ...
    (Linux-Kernel)
  • Re: stuck with 2.6.23.14 on x86_64
    ... to fix the splice bug I've had to apply by hand the patch. ... the lastest that I can compile is 2.6.23.14; ... All .config are the same, ... SCSI controller: ...
    (Linux-Kernel)
  • Re: stuck with 2.6.23.14 on x86_64
    ... fix the splice bug I've had to apply by hand the patch. ... the lastest that I can compile is 2.6.23.14; ... SCSI controller: ... If patches, what base tree are they applied to? ...
    (Linux-Kernel)
  • Re: stuck with 2.6.23.14 on x86_64
    ... fix the splice bug I've had to apply by hand the patch. ... the lastest that I can compile is 2.6.23.14; ... SCSI controller: ... If patches, what base tree are they applied to? ...
    (Linux-Kernel)
  • stuck with 2.6.23.14 on x86_64
    ... the splice bug I've had to apply by hand the patch. ... the lastest that I can compile is 2.6.23.14; ... SCSI controller: ... Right now, on AMD64 machines, I'm forced to patch by hand the kernel, that's ...
    (Linux-Kernel)