linux-kernel - stuck with 2.6.23.14 on x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200802121503.41328.cova@ferrara.linux.it>
Date:	Tue, 12 Feb 2008 15:03:41 +0100
From:	Fabio Coatti <cova@...rara.linux.it>
To:	linux-kernel@...r.kernel.org
Subject: stuck with 2.6.23.14 on x86_64

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/