public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mikem13@sbcglobal.net
Cc: linux-kernel@vger.kernel.org, Fabio Coatti <cova@ferrara.linux.it>
Subject: Re: stuck with 2.6.23.14 on x86_64
Date: Wed, 13 Feb 2008 11:27:13 -0800	[thread overview]
Message-ID: <20080213112713.e028075f.akpm@linux-foundation.org> (raw)
In-Reply-To: <04a37899-eb7b-43ae-a7ab-1928ca1a0e35@s12g2000prg.googlegroups.com>

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

  reply	other threads:[~2008-02-13 19:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
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

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=20080213112713.e028075f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=cova@ferrara.linux.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikem13@sbcglobal.net \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox