LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* Re: stuck with 2.6.23.14 on x86_64
       [not found] <fa.d3EyknDimPJIlJNA2Y25+wmntNM@ifi.uio.no>
@ 2008-02-13 16:05 ` mikem13
  2008-02-13 19:27   ` Andrew Morton
  0 siblings, 1 reply; 15+ messages in thread
From: mikem13 @ 2008-02-13 16:05 UTC (permalink / raw)
  To: linux-kernel; +Cc: linux-kernel, akpm

On Feb 12, 8:13 am, Fabio Coatti <c...@ferrara.linux.it> 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 9859http://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.
>
> --
> Fabio "Cova" Coatti    http://members.ferrara.linux.it/cova
> Ferrara Linux Users Group          http://ferrara.linux.it
> GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
> Old SysOps never die... they simply forget their password.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Fabio, Can you please post your boot messages in bug 9859.

Thanks,
mikem

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-13 16:05 ` stuck with 2.6.23.14 on x86_64 mikem13
@ 2008-02-13 19:27   ` Andrew Morton
  2008-02-14  7:49     ` Fabio Coatti
  0 siblings, 1 reply; 15+ messages in thread
From: Andrew Morton @ 2008-02-13 19:27 UTC (permalink / raw)
  To: mikem13; +Cc: linux-kernel, Fabio Coatti

On Wed, 13 Feb 2008 08:05:58 -0800 (PST)
mikem13@sbcglobal.net wrote:

> On Feb 12, 8:13 am, Fabio Coatti <c...@ferrara.linux.it> 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 9859http://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.
> >
> > --
> > Fabio "Cova" Coatti    http://members.ferrara.linux.it/cova
> > Ferrara Linux Users Group          http://ferrara.linux.it
> > GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
> > Old SysOps never die... they simply forget their password.
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majord...@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
> Fabio, Can you please post your boot messages in bug 9859.

Let's cc him..

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-13 19:27   ` Andrew Morton
@ 2008-02-14  7:49     ` Fabio Coatti
  0 siblings, 0 replies; 15+ messages in thread
From: Fabio Coatti @ 2008-02-14  7:49 UTC (permalink / raw)
  To: Andrew Morton; +Cc: mikem13, linux-kernel

Alle mercoledì 13 febbraio 2008, Andrew Morton ha scritto:

> > > 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.

> > Fabio, Can you please post your boot messages in bug 9859.
>
> Let's cc him..


No problem, I'm subscribed to the list so I've already posted boot messages; 
thanks anyway :)




-- 
Fabio "Cova" Coatti    http://members.ferrara.linux.it/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-14  5:48         ` Len Brown
@ 2008-02-14  8:03           ` Fabio Coatti
  0 siblings, 0 replies; 15+ messages in thread
From: Fabio Coatti @ 2008-02-14  8:03 UTC (permalink / raw)
  To: Len Brown; +Cc: Rafael J. Wysocki, Randy Dunlap, linux-kernel

Alle giovedì 14 febbraio 2008, Len Brown ha scritto:

> > >
> > > 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.
> >
> > Maybe it's not supposed to have this situation, but maybe you should tell
> > this to the kernel itself :)
> >
> > # zcat /proc/config.gz | egrep "PM|ACPI"
> > CONFIG_X86_64_ACPI_NUMA=y
> > # CONFIG_PM is not set
> > CONFIG_ACPI=y
> > # CONFIG_ACPI_PROCFS is not set
> >
> > # uname -rv
> > 2.6.23.12 #3 SMP Tue Feb 12 11:22:16 CET 2008
> >
> > And you can easily get this situation from menuconfig: just fire up make
> > menuconfig without any .config, go to power management options and turn
> > off "Power Management support". exit and look at .config:
> >
> > # CONFIG_PM is not set
> > CONFIG_SUSPEND_SMP_POSSIBLE=y
> > CONFIG_HIBERNATION_SMP_POSSIBLE=y
> > CONFIG_ACPI=y
> >
> > Maybe if this is not supposed to be the right situation, some
> > dependencies are not respected... (tested on .16)
>
> I think this got fixed in 2.6.24 by the X86_64_ACPI_NUMA dependencies.
> (in 2.6.23 it used to select ACPI, in 2.6.24 it depends on ACPI).
>
> So I think in 2.6.24 you should not have this trouble.


That would be great, now I'm only to wait to find a solution for E200i SCSI 
controller: http://bugzilla.kernel.org/show_bug.cgi?id=9859

In fact, I'm able to compile 2.6.24 so it seems that the CONFIG_PM bug is 
solved; now I've only to find why 2.6.24 is not willing to boot on my 
boxes :)







-- 
Fabio "Cova" Coatti    http://members.ferrara.linux.it/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-13  9:21       ` Fabio Coatti
  2008-02-13 17:15         ` Randy Dunlap
  2008-02-13 17:16         ` Randy Dunlap
@ 2008-02-14  5:48         ` Len Brown
  2008-02-14  8:03           ` Fabio Coatti
  2 siblings, 1 reply; 15+ messages in thread
From: Len Brown @ 2008-02-14  5:48 UTC (permalink / raw)
  To: Fabio Coatti; +Cc: Rafael J. Wysocki, Randy Dunlap, linux-kernel

On Wednesday 13 February 2008 04:21, Fabio Coatti wrote:
> Alle martedì 12 febbraio 2008, Rafael J. Wysocki ha scritto:
> > 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.
> 
> Maybe it's not supposed to have this situation, but maybe you should tell this 
> to the kernel itself :)
> 
> # zcat /proc/config.gz | egrep "PM|ACPI"
> CONFIG_X86_64_ACPI_NUMA=y
> # CONFIG_PM is not set
> CONFIG_ACPI=y
> # CONFIG_ACPI_PROCFS is not set
> 
> # uname -rv
> 2.6.23.12 #3 SMP Tue Feb 12 11:22:16 CET 2008
> 
> And you can easily get this situation from menuconfig: just fire up make 
> menuconfig without any .config, go to power management options and turn 
> off "Power Management support". exit and look at .config:
> 
> # CONFIG_PM is not set
> CONFIG_SUSPEND_SMP_POSSIBLE=y
> CONFIG_HIBERNATION_SMP_POSSIBLE=y
> CONFIG_ACPI=y
> 
> Maybe if this is not supposed to be the right situation, some dependencies are 
> not respected... (tested on .16)

I think this got fixed in 2.6.24 by the X86_64_ACPI_NUMA dependencies.
(in 2.6.23 it used to select ACPI, in 2.6.24 it depends on ACPI).

So I think in 2.6.24 you should not have this trouble.

thanks,
-Len

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-13 17:16         ` Randy Dunlap
@ 2008-02-13 17:46           ` Fabio Coatti
  0 siblings, 0 replies; 15+ messages in thread
From: Fabio Coatti @ 2008-02-13 17:46 UTC (permalink / raw)
  To: Randy Dunlap; +Cc: Rafael J. Wysocki, linux-kernel, len.brown

Alle mercoledì 13 febbraio 2008, Randy Dunlap ha scritto:

> > >
> > > 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.
> >
> > Maybe it's not supposed to have this situation, but maybe you should tell
> > this to the kernel itself :)
> >
> > # zcat /proc/config.gz | egrep "PM|ACPI"
> > CONFIG_X86_64_ACPI_NUMA=y
> > # CONFIG_PM is not set
> > CONFIG_ACPI=y
> > # CONFIG_ACPI_PROCFS is not set
> >
> > # uname -rv
> > 2.6.23.12 #3 SMP Tue Feb 12 11:22:16 CET 2008
> >
> > And you can easily get this situation from menuconfig: just fire up make
> > menuconfig without any .config, go to power management options and turn
> > off "Power Management support". exit and look at .config:
> >
> > # CONFIG_PM is not set
> > CONFIG_SUSPEND_SMP_POSSIBLE=y
> > CONFIG_HIBERNATION_SMP_POSSIBLE=y
> > CONFIG_ACPI=y
> >
> > Maybe if this is not supposed to be the right situation, some
> > dependencies are not respected... (tested on .16)
>
> Yes, this is yet another select problem.  X86_64_NUMA_ACPI
> selects ACPI, even though PM is not enabled.  :(
>
> So you have a manual fix:  just enable CONFIG_PM.
>
> Is this specific config important to you?  I.e., do you want/need
> NUMA support?  If so, you'll just need to continue enabling CONFIG_PM.

Well, I suppose that I need to activate NUMA, as I'm running a dual 
processor/dual core AMD 2216HE box... so I will go for CONFIG_PM option 
enabled, I suppose :)



-- 
Fabio "Cova" Coatti    http://members.ferrara.linux.it/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-13  9:21       ` Fabio Coatti
  2008-02-13 17:15         ` Randy Dunlap
@ 2008-02-13 17:16         ` Randy Dunlap
  2008-02-13 17:46           ` Fabio Coatti
  2008-02-14  5:48         ` Len Brown
  2 siblings, 1 reply; 15+ messages in thread
From: Randy Dunlap @ 2008-02-13 17:16 UTC (permalink / raw)
  To: Fabio Coatti; +Cc: Rafael J. Wysocki, linux-kernel, len.brown

On Wed, 13 Feb 2008 10:21:23 +0100 Fabio Coatti wrote:

> Alle martedì 12 febbraio 2008, Rafael J. Wysocki ha scritto:
> > 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.
> 
> Maybe it's not supposed to have this situation, but maybe you should tell this 
> to the kernel itself :)
> 
> # zcat /proc/config.gz | egrep "PM|ACPI"
> CONFIG_X86_64_ACPI_NUMA=y
> # CONFIG_PM is not set
> CONFIG_ACPI=y
> # CONFIG_ACPI_PROCFS is not set
> 
> # uname -rv
> 2.6.23.12 #3 SMP Tue Feb 12 11:22:16 CET 2008
> 
> And you can easily get this situation from menuconfig: just fire up make 
> menuconfig without any .config, go to power management options and turn 
> off "Power Management support". exit and look at .config:
> 
> # CONFIG_PM is not set
> CONFIG_SUSPEND_SMP_POSSIBLE=y
> CONFIG_HIBERNATION_SMP_POSSIBLE=y
> CONFIG_ACPI=y
> 
> Maybe if this is not supposed to be the right situation, some dependencies are 
> not respected... (tested on .16)


Yes, this is yet another select problem.  X86_64_NUMA_ACPI
selects ACPI, even though PM is not enabled.  :(

So you have a manual fix:  just enable CONFIG_PM.

Is this specific config important to you?  I.e., do you want/need
NUMA support?  If so, you'll just need to continue enabling CONFIG_PM.

I made a patch that prevents the select problem (see below [now added]).

The "select PCI" in the X86_64_ACPI_NUMA config option is evil.  :(


> Anyway, with .16 and CONFIG_PM set, I get this :
> ===================
> WARNING: vmlinux.o(.text+0x1f6395): Section mismatch: reference 
> to .init.data.14:pxm_to_node_map (between 'pxm_to_node' and 'node_to_pxm')
> WARNING: vmlinux.o(.text+0x1f63a7): Section mismatch: reference 
> to .init.data.14:node_to_pxm_map (between 'node_to_pxm' 
> and '__acpi_map_pxm_to_node')
> WARNING: vmlinux.o(.text+0x1f63b2): Section mismatch: reference 
> to .init.data.14:pxm_to_node_map (between '__acpi_map_pxm_to_node' 
> and 'acpi_get_pxm')
> WARNING: vmlinux.o(.text+0x1f63bc): Section mismatch: reference 
> to .init.data.14:node_to_pxm_map (between '__acpi_map_pxm_to_node' 
> and 'acpi_get_pxm')
> WARNING: vmlinux.o(.text+0x1f6412): Section mismatch: reference 
> to .init.data.14:pxm_to_node_map (between 'acpi_map_pxm_to_node' 
> and 'acpi_get_node')
> WARNING: vmlinux.o(.text+0x1f6458): Section mismatch: reference 
> to .init.data.14:pxm_to_node_map (between 'acpi_map_pxm_to_node' 
> and 'acpi_get_node')
> WARNING: vmlinux.o(.text+0x1f645f): Section mismatch: reference 
> to .init.data.14:node_to_pxm_map (between 'acpi_map_pxm_to_node' 
> and 'acpi_get_node')
> =========================
> 
> Anyway, it booted and so far it runs without "splice" problem, thanks.


---
From: Randy Dunlap <randy.dunlap@oracle.com>

Fix a kconfig 'select' problem: X86_64_NUMA_ACPI selects ACPI,
so ACPI could be enabled even when PM is not enabled.
This causes a build failure, so make X86_64_NUMA_ACPI depend on PM.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 arch/x86_64/Kconfig |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-2.6.23.16.orig/arch/x86_64/Kconfig
+++ linux-2.6.23.16/arch/x86_64/Kconfig
@@ -367,7 +367,7 @@ config NODES_SHIFT
 
 config X86_64_ACPI_NUMA
        bool "ACPI NUMA detection"
-       depends on NUMA
+       depends on NUMA && PM
        select ACPI 
 	select PCI
        select ACPI_NUMA


^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-13  9:21       ` Fabio Coatti
@ 2008-02-13 17:15         ` Randy Dunlap
  2008-02-13 17:16         ` Randy Dunlap
  2008-02-14  5:48         ` Len Brown
  2 siblings, 0 replies; 15+ messages in thread
From: Randy Dunlap @ 2008-02-13 17:15 UTC (permalink / raw)
  To: Fabio Coatti; +Cc: Rafael J. Wysocki, linux-kernel, len.brown

On Wed, 13 Feb 2008 10:21:23 +0100 Fabio Coatti wrote:

> Alle martedì 12 febbraio 2008, Rafael J. Wysocki ha scritto:
> > 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.
> 
> Maybe it's not supposed to have this situation, but maybe you should tell this 
> to the kernel itself :)
> 
> # zcat /proc/config.gz | egrep "PM|ACPI"
> CONFIG_X86_64_ACPI_NUMA=y
> # CONFIG_PM is not set
> CONFIG_ACPI=y
> # CONFIG_ACPI_PROCFS is not set
> 
> # uname -rv
> 2.6.23.12 #3 SMP Tue Feb 12 11:22:16 CET 2008
> 
> And you can easily get this situation from menuconfig: just fire up make 
> menuconfig without any .config, go to power management options and turn 
> off "Power Management support". exit and look at .config:
> 
> # CONFIG_PM is not set
> CONFIG_SUSPEND_SMP_POSSIBLE=y
> CONFIG_HIBERNATION_SMP_POSSIBLE=y
> CONFIG_ACPI=y
> 
> Maybe if this is not supposed to be the right situation, some dependencies are 
> not respected... (tested on .16)


Yes, this is yet another select problem.  X86_64_NUMA_ACPI
selects ACPI, even though PM is not enabled.  :(

So you have a manual fix:  just enable CONFIG_PM.

Is this specific config important to you?  I.e., do you want/need
NUMA support?  If so, you'll just need to continue enabling CONFIG_PM.

I made a patch that prevents the select problem (see below).

The "select PCI" in the X86_64_ACPI_NUMA config option is evil.  :(


> Anyway, with .16 and CONFIG_PM set, I get this :
> ===================
> WARNING: vmlinux.o(.text+0x1f6395): Section mismatch: reference 
> to .init.data.14:pxm_to_node_map (between 'pxm_to_node' and 'node_to_pxm')
> WARNING: vmlinux.o(.text+0x1f63a7): Section mismatch: reference 
> to .init.data.14:node_to_pxm_map (between 'node_to_pxm' 
> and '__acpi_map_pxm_to_node')
> WARNING: vmlinux.o(.text+0x1f63b2): Section mismatch: reference 
> to .init.data.14:pxm_to_node_map (between '__acpi_map_pxm_to_node' 
> and 'acpi_get_pxm')
> WARNING: vmlinux.o(.text+0x1f63bc): Section mismatch: reference 
> to .init.data.14:node_to_pxm_map (between '__acpi_map_pxm_to_node' 
> and 'acpi_get_pxm')
> WARNING: vmlinux.o(.text+0x1f6412): Section mismatch: reference 
> to .init.data.14:pxm_to_node_map (between 'acpi_map_pxm_to_node' 
> and 'acpi_get_node')
> WARNING: vmlinux.o(.text+0x1f6458): Section mismatch: reference 
> to .init.data.14:pxm_to_node_map (between 'acpi_map_pxm_to_node' 
> and 'acpi_get_node')
> WARNING: vmlinux.o(.text+0x1f645f): Section mismatch: reference 
> to .init.data.14:node_to_pxm_map (between 'acpi_map_pxm_to_node' 
> and 'acpi_get_node')
> =========================
> 
> Anyway, it booted and so far it runs without "splice" problem, thanks.


---
~Randy

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-12 20:55     ` Rafael J. Wysocki
@ 2008-02-13  9:21       ` Fabio Coatti
  2008-02-13 17:15         ` Randy Dunlap
                           ` (2 more replies)
  0 siblings, 3 replies; 15+ messages in thread
From: Fabio Coatti @ 2008-02-13  9:21 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: Randy Dunlap, linux-kernel

Alle martedì 12 febbraio 2008, Rafael J. Wysocki ha scritto:
> 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.

Maybe it's not supposed to have this situation, but maybe you should tell this 
to the kernel itself :)

# zcat /proc/config.gz | egrep "PM|ACPI"
CONFIG_X86_64_ACPI_NUMA=y
# CONFIG_PM is not set
CONFIG_ACPI=y
# CONFIG_ACPI_PROCFS is not set

# uname -rv
2.6.23.12 #3 SMP Tue Feb 12 11:22:16 CET 2008

And you can easily get this situation from menuconfig: just fire up make 
menuconfig without any .config, go to power management options and turn 
off "Power Management support". exit and look at .config:

# CONFIG_PM is not set
CONFIG_SUSPEND_SMP_POSSIBLE=y
CONFIG_HIBERNATION_SMP_POSSIBLE=y
CONFIG_ACPI=y

Maybe if this is not supposed to be the right situation, some dependencies are 
not respected... (tested on .16)

Anyway, with .16 and CONFIG_PM set, I get this :
===================
WARNING: vmlinux.o(.text+0x1f6395): Section mismatch: reference 
to .init.data.14:pxm_to_node_map (between 'pxm_to_node' and 'node_to_pxm')
WARNING: vmlinux.o(.text+0x1f63a7): Section mismatch: reference 
to .init.data.14:node_to_pxm_map (between 'node_to_pxm' 
and '__acpi_map_pxm_to_node')
WARNING: vmlinux.o(.text+0x1f63b2): Section mismatch: reference 
to .init.data.14:pxm_to_node_map (between '__acpi_map_pxm_to_node' 
and 'acpi_get_pxm')
WARNING: vmlinux.o(.text+0x1f63bc): Section mismatch: reference 
to .init.data.14:node_to_pxm_map (between '__acpi_map_pxm_to_node' 
and 'acpi_get_pxm')
WARNING: vmlinux.o(.text+0x1f6412): Section mismatch: reference 
to .init.data.14:pxm_to_node_map (between 'acpi_map_pxm_to_node' 
and 'acpi_get_node')
WARNING: vmlinux.o(.text+0x1f6458): Section mismatch: reference 
to .init.data.14:pxm_to_node_map (between 'acpi_map_pxm_to_node' 
and 'acpi_get_node')
WARNING: vmlinux.o(.text+0x1f645f): Section mismatch: reference 
to .init.data.14:node_to_pxm_map (between 'acpi_map_pxm_to_node' 
and 'acpi_get_node')
=========================

Anyway, it booted and so far it runs without "splice" problem, thanks.


-- 
Fabio "Cova" Coatti    http://members.ferrara.linux.it/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-12 17:47   ` Fabio Coatti
  2008-02-12 20:45     ` Randy Dunlap
@ 2008-02-12 20:55     ` Rafael J. Wysocki
  2008-02-13  9:21       ` Fabio Coatti
  1 sibling, 1 reply; 15+ messages in thread
From: Rafael J. Wysocki @ 2008-02-12 20:55 UTC (permalink / raw)
  To: Fabio Coatti; +Cc: Randy Dunlap, linux-kernel

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-12 20:45     ` Randy Dunlap
@ 2008-02-12 20:52       ` Rafael J. Wysocki
  0 siblings, 0 replies; 15+ messages in thread
From: Rafael J. Wysocki @ 2008-02-12 20:52 UTC (permalink / raw)
  To: Randy Dunlap; +Cc: Fabio Coatti, linux-kernel, len.brown

On Tuesday, 12 of February 2008, Randy Dunlap wrote:
> On Tue, 12 Feb 2008 18:47:19 +0100 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
> 
> OK, quite easy to reproduce when CONFIG_PM=n.
> For a temp quick fix, you could enable CONFIG_PM.
> 
> Len, Rafael:  were there any recent patches for the split of ACPI & PM
> that need to be backported to -stable?

Not that I know of.

Actually, ACPI still depends on PM (in the current mainline as well as in
.23.x).

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-12 17:47   ` Fabio Coatti
@ 2008-02-12 20:45     ` Randy Dunlap
  2008-02-12 20:52       ` Rafael J. Wysocki
  2008-02-12 20:55     ` Rafael J. Wysocki
  1 sibling, 1 reply; 15+ messages in thread
From: Randy Dunlap @ 2008-02-12 20:45 UTC (permalink / raw)
  To: Fabio Coatti; +Cc: linux-kernel, len.brown, rjw

On Tue, 12 Feb 2008 18:47:19 +0100 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

OK, quite easy to reproduce when CONFIG_PM=n.
For a temp quick fix, you could enable CONFIG_PM.

Len, Rafael:  were there any recent patches for the split of ACPI & PM
that need to be backported to -stable?

Thanks.
---
~Randy

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-12 17:18 ` Randy Dunlap
@ 2008-02-12 17:47   ` Fabio Coatti
  2008-02-12 20:45     ` Randy Dunlap
  2008-02-12 20:55     ` Rafael J. Wysocki
  0 siblings, 2 replies; 15+ messages in thread
From: Fabio Coatti @ 2008-02-12 17:47 UTC (permalink / raw)
  To: Randy Dunlap; +Cc: linux-kernel

[-- Attachment #1: Type: text/plain, Size: 2492 bytes --]

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



-- 
Fabio "Cova" Coatti    http://members.ferrara.linux.it/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

[-- Attachment #2: config_16 --]
[-- Type: text/plain, Size: 21207 bytes --]

#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.23.16
# Tue Feb 12 18:31:34 2008
#
CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_ZONE_DMA32=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_ARCH_POPULATES_NODE_MAP=y
CONFIG_DMI=y
CONFIG_AUDIT_ARCH=y
CONFIG_GENERIC_BUG=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_SYSVIPC_SYSCTL=y
CONFIG_POSIX_MQUEUE=y
# CONFIG_BSD_PROCESS_ACCT is not set
# CONFIG_TASKSTATS is not set
# CONFIG_USER_NS is not set
# CONFIG_AUDIT is not set
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=15
# CONFIG_CPUSETS is not set
# CONFIG_SYSFS_DEPRECATED is not set
# CONFIG_RELAY is not set
# CONFIG_BLK_DEV_INITRD is not set
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_BLOCK=y
# CONFIG_BLK_DEV_IO_TRACE is not set
# CONFIG_BLK_DEV_BSG is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
CONFIG_DEFAULT_AS=y
# CONFIG_DEFAULT_DEADLINE is not set
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="anticipatory"

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VSMP is not set
CONFIG_MK8=y
# CONFIG_MPSC is not set
# CONFIG_MCORE2 is not set
# CONFIG_GENERIC_CPU is not set
CONFIG_X86_L1_CACHE_BYTES=64
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_X86_INTERNODE_CACHE_BYTES=64
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
# CONFIG_MICROCODE is not set
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_MTRR=y
CONFIG_SMP=y
# CONFIG_SCHED_SMT is not set
CONFIG_SCHED_MC=y
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
CONFIG_PREEMPT_BKL=y
CONFIG_NUMA=y
# CONFIG_K8_NUMA is not set
CONFIG_NODES_SHIFT=6
CONFIG_X86_64_ACPI_NUMA=y
# CONFIG_NUMA_EMU is not set
CONFIG_ARCH_DISCONTIGMEM_ENABLE=y
CONFIG_ARCH_DISCONTIGMEM_DEFAULT=y
CONFIG_ARCH_SPARSEMEM_ENABLE=y
CONFIG_SELECT_MEMORY_MODEL=y
# CONFIG_FLATMEM_MANUAL is not set
CONFIG_DISCONTIGMEM_MANUAL=y
# CONFIG_SPARSEMEM_MANUAL is not set
CONFIG_DISCONTIGMEM=y
CONFIG_FLAT_NODE_MEM_MAP=y
CONFIG_NEED_MULTIPLE_NODES=y
# CONFIG_SPARSEMEM_STATIC is not set
# CONFIG_MEMORY_HOTPLUG is not set
CONFIG_SPLIT_PTLOCK_CPUS=4
CONFIG_MIGRATION=y
CONFIG_RESOURCES_64BIT=y
CONFIG_ZONE_DMA_FLAG=1
CONFIG_BOUNCE=y
CONFIG_VIRT_TO_BUS=y
CONFIG_HAVE_ARCH_EARLY_PFN_TO_NID=y
CONFIG_OUT_OF_LINE_PFN_TO_PAGE=y
CONFIG_NR_CPUS=4
CONFIG_PHYSICAL_ALIGN=0x200000
# CONFIG_HOTPLUG_CPU is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_HPET_TIMER=y
# CONFIG_HPET_EMULATE_RTC is not set
CONFIG_IOMMU=y
CONFIG_CALGARY_IOMMU=y
CONFIG_CALGARY_IOMMU_ENABLED_BY_DEFAULT=y
CONFIG_SWIOTLB=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_INTEL is not set
CONFIG_X86_MCE_AMD=y
# CONFIG_KEXEC is not set
# CONFIG_CRASH_DUMP is not set
# CONFIG_RELOCATABLE is not set
CONFIG_PHYSICAL_START=0x200000
CONFIG_SECCOMP=y
# CONFIG_CC_STACKPROTECTOR is not set
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_300 is not set
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250
CONFIG_K8_NB=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_ISA_DMA_API=y
CONFIG_GENERIC_PENDING_IRQ=y

#
# Power management options
#
# CONFIG_PM is not set
CONFIG_SUSPEND_SMP_POSSIBLE=y
CONFIG_HIBERNATION_SMP_POSSIBLE=y
CONFIG_ACPI=y
# CONFIG_ACPI_PROCFS is not set
# CONFIG_ACPI_PROC_EVENT is not set
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
# CONFIG_ACPI_FAN is not set
# CONFIG_ACPI_DOCK is not set
# CONFIG_ACPI_PROCESSOR is not set
CONFIG_ACPI_NUMA=y
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_SYSTEM=y
CONFIG_X86_PM_TIMER=y
# CONFIG_ACPI_CONTAINER is not set
# CONFIG_ACPI_SBS is not set

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI etc.)
#
CONFIG_PCI=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCIEPORTBUS=y
CONFIG_PCIEAER=y
CONFIG_ARCH_SUPPORTS_MSI=y
CONFIG_PCI_MSI=y
CONFIG_HT_IRQ=y

#
# PCCARD (PCMCIA/CardBus) support
#
# CONFIG_PCCARD is not set
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats / Emulations
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_MISC is not set
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
CONFIG_COMPAT=y
CONFIG_COMPAT_FOR_U64_ALIGNMENT=y
CONFIG_SYSVIPC_COMPAT=y

#
# Networking
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
CONFIG_IP_FIB_HASH=y
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_XFRM_TUNNEL is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
CONFIG_INET_DIAG=y
CONFIG_INET_TCP_DIAG=y
# CONFIG_TCP_CONG_ADVANCED is not set
CONFIG_TCP_CONG_CUBIC=y
CONFIG_DEFAULT_TCP_CONG="cubic"
# CONFIG_TCP_MD5SIG is not set
# CONFIG_IPV6 is not set
# CONFIG_INET6_XFRM_TUNNEL is not set
# CONFIG_INET6_TUNNEL is not set
# CONFIG_NETWORK_SECMARK is not set
# CONFIG_NETFILTER is not set
# CONFIG_IP_DCCP is not set
# CONFIG_IP_SCTP is not set
# CONFIG_TIPC is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
CONFIG_VLAN_8021Q=y
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
# CONFIG_AF_RXRPC is not set

#
# Wireless
#
# CONFIG_CFG80211 is not set
# CONFIG_WIRELESS_EXT is not set
# CONFIG_MAC80211 is not set
# CONFIG_IEEE80211 is not set
# CONFIG_RFKILL is not set
# CONFIG_NET_9P is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
CONFIG_STANDALONE=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_FW_LOADER=y
# CONFIG_SYS_HYPERVISOR is not set
CONFIG_CONNECTOR=y
CONFIG_PROC_EVENTS=y
# CONFIG_MTD is not set
# CONFIG_PARPORT is not set
CONFIG_PNP=y
CONFIG_PNP_DEBUG=y

#
# Protocols
#
CONFIG_PNPACPI=y
CONFIG_BLK_DEV=y
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
CONFIG_BLK_CPQ_CISS_DA=y
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=y
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_CDROM_PKTCDVD is not set
# CONFIG_ATA_OVER_ETH is not set
# CONFIG_MISC_DEVICES is not set
# CONFIG_IDE is not set

#
# SCSI device support
#
# CONFIG_RAID_ATTRS is not set
# CONFIG_SCSI is not set
# CONFIG_SCSI_DMA is not set
# CONFIG_SCSI_NETLINK is not set
# CONFIG_ATA is not set
# CONFIG_MD is not set

#
# Fusion MPT device support
#
# CONFIG_FUSION is not set

#
# IEEE 1394 (FireWire) support
#
# CONFIG_FIREWIRE is not set
# CONFIG_IEEE1394 is not set
# CONFIG_I2O is not set
# CONFIG_MACINTOSH_DRIVERS is not set
CONFIG_NETDEVICES=y
# CONFIG_NETDEVICES_MULTIQUEUE is not set
# CONFIG_DUMMY is not set
CONFIG_BONDING=y
# CONFIG_MACVLAN is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
# CONFIG_ARCNET is not set
# CONFIG_NET_ETHERNET is not set
CONFIG_NETDEV_1000=y
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SKGE is not set
# CONFIG_SKY2 is not set
# CONFIG_SK98LIN is not set
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
CONFIG_BNX2=y
# CONFIG_QLA3XXX is not set
# CONFIG_ATL1 is not set
# CONFIG_NETDEV_10000 is not set
# CONFIG_TR is not set

#
# Wireless LAN
#
# CONFIG_WLAN_PRE80211 is not set
# CONFIG_WLAN_80211 is not set

#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET_MII is not set
# CONFIG_USB_USBNET is not set
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_ISDN is not set
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y
# CONFIG_INPUT_FF_MEMLESS is not set
# CONFIG_INPUT_POLLDEV is not set

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_KEYBOARD_STOWAWAY is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_MOUSE_PS2_ALPS=y
CONFIG_MOUSE_PS2_LOGIPS2PP=y
CONFIG_MOUSE_PS2_SYNAPTICS=y
CONFIG_MOUSE_PS2_LIFEBOOK=y
CONFIG_MOUSE_PS2_TRACKPOINT=y
# CONFIG_MOUSE_PS2_TOUCHKIT is not set
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_APPLETOUCH is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TABLET is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_VT_HW_CONSOLE_BINDING is not set
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set
CONFIG_FIX_EARLYCON_MEM=y

#
# Non-8250 serial port support
#
# CONFIG_SERIAL_JSM is not set
CONFIG_UNIX98_PTYS=y
# CONFIG_LEGACY_PTYS is not set
# CONFIG_IPMI_HANDLER is not set
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=y
# CONFIG_HW_RANDOM_INTEL is not set
CONFIG_HW_RANDOM_AMD=y
CONFIG_NVRAM=y
CONFIG_RTC=y
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
CONFIG_AGP=y
CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_PC8736x_GPIO is not set
# CONFIG_RAW_DRIVER is not set
CONFIG_HPET=y
CONFIG_HPET_RTC_IRQ=y
CONFIG_HPET_MMAP=y
# CONFIG_HANGCHECK_TIMER is not set
# CONFIG_TCG_TPM is not set
# CONFIG_TELCLOCK is not set
CONFIG_DEVPORT=y
# CONFIG_I2C is not set

#
# SPI support
#
# CONFIG_SPI is not set
# CONFIG_SPI_MASTER is not set
# CONFIG_W1 is not set
# CONFIG_POWER_SUPPLY is not set
# CONFIG_HWMON is not set

#
# Multifunction device drivers
#
# CONFIG_MFD_SM501 is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
# CONFIG_DVB_CORE is not set
# CONFIG_DAB is not set

#
# Graphics support
#
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set

#
# Display device support
#
# CONFIG_DISPLAY_SUPPORT is not set
# CONFIG_VGASTATE is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=256
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
# CONFIG_SOUND is not set
CONFIG_HID_SUPPORT=y
CONFIG_HID=y
# CONFIG_HID_DEBUG is not set

#
# USB Input Devices
#
CONFIG_USB_HID=y
# CONFIG_USB_HIDINPUT_POWERBOOK is not set
# CONFIG_HID_FF is not set
# CONFIG_USB_HIDDEV is not set
CONFIG_USB_SUPPORT=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set

#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_DEVICE_CLASS is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set

#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=y
# CONFIG_USB_EHCI_SPLIT_ISO is not set
# CONFIG_USB_EHCI_ROOT_HUB_TT is not set
# CONFIG_USB_EHCI_TT_NEWSCHED is not set
# CONFIG_USB_ISP116X_HCD is not set
CONFIG_USB_OHCI_HCD=y
# CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
# CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
CONFIG_USB_UHCI_HCD=y
# CONFIG_USB_SL811_HCD is not set
# CONFIG_USB_R8A66597_HCD is not set

#
# USB Device Class drivers
#
# CONFIG_USB_ACM is not set
# CONFIG_USB_PRINTER is not set

#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support'
#

#
# may also be needed; see USB_STORAGE Help for more information
#
# CONFIG_USB_LIBUSUAL is not set

#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MON is not set

#
# USB port drivers
#

#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set

#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_ADUTUX is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_BERRY_CHARGE is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYPRESS_CY7C63 is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGET is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_FTDI_ELAN is not set
# CONFIG_USB_APPLEDISPLAY is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_LD is not set
# CONFIG_USB_TRANCEVIBRATOR is not set
# CONFIG_USB_IOWARRIOR is not set
# CONFIG_USB_TEST is not set

#
# USB DSL modem support
#

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
# CONFIG_MMC is not set
# CONFIG_NEW_LEDS is not set
# CONFIG_INFINIBAND is not set
# CONFIG_EDAC is not set
CONFIG_RTC_LIB=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_HCTOSYS=y
CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
CONFIG_RTC_DEBUG=y

#
# RTC interfaces
#
CONFIG_RTC_INTF_SYSFS=y
CONFIG_RTC_INTF_PROC=y
CONFIG_RTC_INTF_DEV=y
CONFIG_RTC_INTF_DEV_UIE_EMUL=y
# CONFIG_RTC_DRV_TEST is not set

#
# SPI RTC drivers
#

#
# Platform RTC drivers
#
CONFIG_RTC_DRV_CMOS=y
# CONFIG_RTC_DRV_DS1553 is not set
# CONFIG_RTC_DRV_STK17TA8 is not set
# CONFIG_RTC_DRV_DS1742 is not set
# CONFIG_RTC_DRV_M48T86 is not set
# CONFIG_RTC_DRV_M48T59 is not set
# CONFIG_RTC_DRV_V3020 is not set

#
# on-CPU RTC drivers
#

#
# DMA Engine support
#
CONFIG_DMA_ENGINE=y

#
# DMA Clients
#
CONFIG_NET_DMA=y

#
# DMA Devices
#
# CONFIG_INTEL_IOATDMA is not set
# CONFIG_VIRTUALIZATION is not set

#
# Userspace I/O
#
# CONFIG_UIO is not set

#
# Firmware Drivers
#
# CONFIG_EDD is not set
# CONFIG_DELL_RBU is not set
# CONFIG_DCDBAS is not set
CONFIG_DMIID=y

#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
# CONFIG_EXT2_FS_SECURITY is not set
# CONFIG_EXT2_FS_XIP is not set
# CONFIG_EXT3_FS is not set
# CONFIG_EXT4DEV_FS is not set
CONFIG_FS_MBCACHE=y
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
CONFIG_FS_POSIX_ACL=y
CONFIG_XFS_FS=y
CONFIG_XFS_QUOTA=y
CONFIG_XFS_SECURITY=y
CONFIG_XFS_POSIX_ACL=y
# CONFIG_XFS_RT is not set
# CONFIG_GFS2_FS is not set
# CONFIG_OCFS2_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_QUOTACTL=y
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_FUSE_FS=y

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
# CONFIG_UDF_FS is not set

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_PROC_SYSCTL=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
# CONFIG_TMPFS_POSIX_ACL is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
# CONFIG_CONFIGFS_FS is not set

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
# CONFIG_NFS_V3_ACL is not set
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
# CONFIG_NFSD is not set
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
# CONFIG_SUNRPC_BIND34 is not set
CONFIG_RPCSEC_GSS_KRB5=y
# CONFIG_RPCSEC_GSS_SPKM3 is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="UTF-8"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=y
CONFIG_NLS_CODEPAGE_775=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
CONFIG_NLS_CODEPAGE_855=y
CONFIG_NLS_CODEPAGE_857=y
CONFIG_NLS_CODEPAGE_860=y
CONFIG_NLS_CODEPAGE_861=y
CONFIG_NLS_CODEPAGE_862=y
CONFIG_NLS_CODEPAGE_863=y
CONFIG_NLS_CODEPAGE_864=y
CONFIG_NLS_CODEPAGE_865=y
CONFIG_NLS_CODEPAGE_866=y
CONFIG_NLS_CODEPAGE_869=y
CONFIG_NLS_CODEPAGE_936=y
CONFIG_NLS_CODEPAGE_950=y
CONFIG_NLS_CODEPAGE_932=y
CONFIG_NLS_CODEPAGE_949=y
CONFIG_NLS_CODEPAGE_874=y
CONFIG_NLS_ISO8859_8=y
CONFIG_NLS_CODEPAGE_1250=y
CONFIG_NLS_CODEPAGE_1251=y
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=y
CONFIG_NLS_ISO8859_3=y
CONFIG_NLS_ISO8859_4=y
CONFIG_NLS_ISO8859_5=y
CONFIG_NLS_ISO8859_6=y
CONFIG_NLS_ISO8859_7=y
CONFIG_NLS_ISO8859_9=y
CONFIG_NLS_ISO8859_13=y
CONFIG_NLS_ISO8859_14=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_KOI8_R=y
CONFIG_NLS_KOI8_U=y
CONFIG_NLS_UTF8=y

#
# Distributed Lock Manager
#
# CONFIG_DLM is not set

#
# Instrumentation Support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
# CONFIG_PRINTK_TIME is not set
# CONFIG_ENABLE_MUST_CHECK is not set
# CONFIG_MAGIC_SYSRQ is not set
# CONFIG_UNUSED_SYMBOLS is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_HEADERS_CHECK is not set
# CONFIG_DEBUG_KERNEL is not set
CONFIG_DEBUG_BUGVERBOSE=y

#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
CONFIG_CRYPTO=y
CONFIG_CRYPTO_ALGAPI=y
CONFIG_CRYPTO_BLKCIPHER=y
CONFIG_CRYPTO_HASH=y
CONFIG_CRYPTO_MANAGER=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_XCBC=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_WP512=y
CONFIG_CRYPTO_TGR192=y
# CONFIG_CRYPTO_GF128MUL is not set
CONFIG_CRYPTO_ECB=y
CONFIG_CRYPTO_CBC=y
CONFIG_CRYPTO_PCBC=y
# CONFIG_CRYPTO_LRW is not set
# CONFIG_CRYPTO_CRYPTD is not set
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_FCRYPT=y
CONFIG_CRYPTO_BLOWFISH=y
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_TWOFISH_COMMON=y
CONFIG_CRYPTO_TWOFISH_X86_64=y
CONFIG_CRYPTO_SERPENT=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_AES_X86_64=y
CONFIG_CRYPTO_CAST5=y
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_TEA=y
CONFIG_CRYPTO_ARC4=y
CONFIG_CRYPTO_KHAZAD=y
CONFIG_CRYPTO_ANUBIS=y
CONFIG_CRYPTO_DEFLATE=y
CONFIG_CRYPTO_MICHAEL_MIC=y
CONFIG_CRYPTO_CRC32C=y
CONFIG_CRYPTO_CAMELLIA=y
# CONFIG_CRYPTO_HW is not set

#
# Library routines
#
CONFIG_BITREVERSE=y
CONFIG_CRC_CCITT=y
CONFIG_CRC16=y
CONFIG_CRC_ITU_T=y
CONFIG_CRC32=y
CONFIG_CRC7=y
CONFIG_LIBCRC32C=y
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_PLIST=y
CONFIG_HAS_IOMEM=y
CONFIG_HAS_IOPORT=y
CONFIG_HAS_DMA=y

^ permalink raw reply	[flat|nested] 15+ messages in thread

* Re: stuck with 2.6.23.14 on x86_64
  2008-02-12 14:03 Fabio Coatti
@ 2008-02-12 17:18 ` Randy Dunlap
  2008-02-12 17:47   ` Fabio Coatti
  0 siblings, 1 reply; 15+ messages in thread
From: Randy Dunlap @ 2008-02-12 17:18 UTC (permalink / raw)
  To: Fabio Coatti; +Cc: linux-kernel

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* stuck with 2.6.23.14 on x86_64
@ 2008-02-12 14:03 Fabio Coatti
  2008-02-12 17:18 ` Randy Dunlap
  0 siblings, 1 reply; 15+ messages in thread
From: Fabio Coatti @ 2008-02-12 14:03 UTC (permalink / raw)
  To: linux-kernel

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.


-- 
Fabio "Cova" Coatti    http://members.ferrara.linux.it/cova     
Ferrara Linux Users Group           http://ferrara.linux.it
GnuPG fp:9765 A5B6 6843 17BC A646  BE8C FA56 373A 5374 C703
Old SysOps never die... they simply forget their password.

^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, other threads:[~2008-02-14  8:03 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <fa.d3EyknDimPJIlJNA2Y25+wmntNM@ifi.uio.no>
2008-02-13 16:05 ` stuck with 2.6.23.14 on x86_64 mikem13
2008-02-13 19:27   ` Andrew Morton
2008-02-14  7:49     ` Fabio Coatti
2008-02-12 14:03 Fabio Coatti
2008-02-12 17:18 ` Randy Dunlap
2008-02-12 17:47   ` Fabio Coatti
2008-02-12 20:45     ` Randy Dunlap
2008-02-12 20:52       ` Rafael J. Wysocki
2008-02-12 20:55     ` Rafael J. Wysocki
2008-02-13  9:21       ` Fabio Coatti
2008-02-13 17:15         ` Randy Dunlap
2008-02-13 17:16         ` Randy Dunlap
2008-02-13 17:46           ` Fabio Coatti
2008-02-14  5:48         ` Len Brown
2008-02-14  8:03           ` Fabio Coatti

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).