LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Fabio Coatti <cova@ferrara.linux.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: stuck with 2.6.23.14 on x86_64
Date: Tue, 12 Feb 2008 09:18:55 -0800	[thread overview]
Message-ID: <20080212091855.d43d7926.randy.dunlap@oracle.com> (raw)
In-Reply-To: <200802121503.41328.cova@ferrara.linux.it>

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

  reply	other threads:[~2008-02-12 17:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 14:03 Fabio Coatti
2008-02-12 17:18 ` Randy Dunlap [this message]
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
     [not found] <fa.d3EyknDimPJIlJNA2Y25+wmntNM@ifi.uio.no>
2008-02-13 16:05 ` mikem13
2008-02-13 19:27   ` Andrew Morton
2008-02-14  7:49     ` Fabio Coatti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080212091855.d43d7926.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=cova@ferrara.linux.it \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: stuck with 2.6.23.14 on x86_64' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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