No modules found in kernel26 package compiled via ABS

ssri · 2010-12-30 02:18:19

Hi,

I have been experiencing problems building kernels recently. I've used ABS and AUR pkgbuilds to build kernels since 2.6.30, mostly to enable the proper USB scheduler for my hub and to try outside kernel patches, see kernel26-ck. However, since the release of 2.6.35.2, more likely a mere coincidence, I've been compiling small kernels (~4MB) from the default .configs without any modifcations to the PKGBUILDs or the config files. Looking at the compiled packages, I noticed the omission of the kernel modules that are normally located in /lib/modules/[kernelname]/kernel. The missing kernel modules obviously causes my machine to be unable to boot (https://bbs.archlinux.org/viewtopic.php … 15#p872215). My makepkg.conf is below. Any explanation on what is going on? Thanks

~$ cat /etc/makepkg.conf
#
# /etc/makepkg.conf
#

#########################################################################
# SOURCE ACQUISITION
#########################################################################
#
#-- The download utilities that makepkg should use to acquire sources
#  Format: 'protocol::agent'
DLAGENTS=('ftp::/usr/bin/wget -c --passive-ftp -t 3 --waitretry=3 -O %o %u'
          'http::/usr/bin/wget -c -t 3 --waitretry=3 -O %o %u'
          'https::/usr/bin/wget -c -t 3 --waitretry=3 --no-check-certificate -O %o %u'
          'rsync::/usr/bin/rsync -z %u %o'
          'scp::/usr/bin/scp -C %u %o')

# Other common tools:
# /usr/bin/snarf
# /usr/bin/lftpget -c
# /usr/bin/curl

#########################################################################
# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="x86_64"
CHOST="x86_64-unknown-linux-gnu"

#-- Exclusive: will only run on x86_64
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe"
CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe"
LDFLAGS="-Wl,--hash-style=gnu -Wl,--as-needed"
#-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j2"

#########################################################################
# BUILD ENVIRONMENT
#########################################################################
#
# Defaults: BUILDENV=(fakeroot !distcc color !ccache)
#  A negated environment option will do the opposite of the comments below.
#
#-- fakeroot: Allow building packages as a non-root user
#-- distcc:   Use the Distributed C/C++/ObjC compiler
#-- color:    Colorize output messages
#-- ccache:   Use ccache to cache compilation
#
BUILDENV=(fakeroot !distcc color !ccache)
#
#-- If using DistCC, your MAKEFLAGS will also need modification. In addition,
#-- specify a space-delimited list of hosts running in the DistCC cluster.
#DISTCC_HOSTS=""

#########################################################################
# GLOBAL PACKAGE OPTIONS
#   These are default values for the options=() settings
#########################################################################
#
# Default: OPTIONS=(strip docs libtool emptydirs zipman purge)
#  A negated option will do the opposite of the comments below.
#
#-- strip:     Strip symbols from binaries/libraries in STRIP_DIRS
#-- docs:      Save doc directories specified by DOC_DIRS
#-- libtool:   Leave libtool (.la) files in packages
#-- emptydirs: Leave empty directories in packages
#-- zipman:    Compress manual (man and info) pages in MAN_DIRS with gzip
#-- purge:     Remove files specified by PURGE_TARGETS
#
OPTIONS=(strip docs libtool emptydirs zipman purge)

#-- File integrity checks to use. Valid: md5, sha1, sha256, sha384, sha512
INTEGRITY_CHECK=(md5)
#-- Options to be used when stripping binaries. See `man strip' for details.
STRIP_BINARIES="--strip-all"
#-- Options to be used when stripping shared libraries. See `man strip' for details.
STRIP_SHARED="--strip-unneeded"
#-- Options to be used when stripping static libraries. See `man strip' for details.
STRIP_STATIC="--strip-debug"
#-- Manual (man and info) directories to compress (if zipman is specified)
MAN_DIRS=({usr{,/local}{,/share},opt/*}/{man,info})
#-- Doc directories to remove (if !docs is specified)
DOC_DIRS=(usr/{,local/}{,share/}{doc,gtk-doc} opt/*/{doc,gtk-doc})
#-- Directories to be searched for the strip option (if strip is specified)
STRIP_DIRS=(bin lib sbin usr/{bin,lib,sbin,local/{bin,lib,sbin}} opt/*/{bin,lib,sbin})
#-- Files to be removed from all packages (if purge is specified)
PURGE_TARGETS=(usr/{,share}/info/dir .packlist *.pod)

#########################################################################
# PACKAGE OUTPUT
#########################################################################
#
# Default: put built package and cached source in build directory
#
#-- Destination: specify a fixed directory where all packages will be placed
#PKGDEST=/home/packages
#-- Source cache: specify a fixed directory where source files will be cached
#SRCDEST=/home/sources
#-- Source packages: specify a fixed directory where all src packages will be placed
#SRCPKGDEST=/home/srcpackages
#-- Packager: name/email of the person or organization building packages
#PACKAGER="John Doe <john@doe.com>"

#########################################################################
# EXTENSION DEFAULTS
#########################################################################
#
# WARNING: Do NOT modify these variables unless you know what you are
#          doing.
#
PKGEXT='.pkg.tar.xz'
SRCEXT='.src.tar.gz'

# vim: set ft=sh ts=2 sw=2 et:

Last edited by ssri (2011-01-15 05:56:17)

graysky · 2010-12-30 10:49:37

graysky wrote:

I'm beginning to wonder if your machine is stable... you might want to try a stability test using either mprime or linpack. Both of which are in the AUR - click the link in my sig,

I'm still wondering about the stability of your machine... build up linpack and since you have 4 gigs, change the /etc/linpack.conf accordingly, then run it for 20 or 30 iterations. Keep an eye on your temps with sensors.

Sample Intel(R) LINPACK data file
Intel(R) LINPACK data
1 # number of tests
21000 # problem sizes
21000 # leading dimensions
100 # times to run a test
4 # alignment values (in KBytes)
# Change the problem sizes and leading dimensions to suite your free physical memory
#
# Memory use = 8 x (problem size)^2
# or
# Problem size = sqrt (memory use / 8)
#
# For 1 GB use a problem size and leading dimensions of 7000
# For 2 GB use a problem size and leading dimensions of 13700
# For 4 GB use a problem size and leading dimensions of 21000
# For 8 GB use a problem size and leading dimensions of 29600

Last edited by graysky (2010-12-30 10:51:41)

ssri · 2011-01-01 06:00:24

Ran linpack and noticed that my CPU temp peaked at 74C, well below the critical threshold of 100C (according to intel). Usually, my CPU runs at arounr 48-55C unless I am doing some CPU-intensive task. When that happens, it will run up to the upper 70s.

~ $ cat /etc/lininput_xeon64 
Sample Intel(R) LINPACK data file
Intel(R) LINPACK data
1 # number of tests
21000 # problem sizes
21000 # leading dimensions
20   # times to run a test
4   # alignment values (in KBytes)

# Change the problem sizes and leading dimensions to suite your free physical memory
#
# Memory use = 8 x (problem size)^2
#           or
# Problem size = sqrt (memory use / 8)
#
# For 1 GB use a problem size and leading dimensions of 7000
# For 2 GB use a problem size and leading dimensions of 13700
# For 4 GB use a problem size and leading dimensions of 21000
# For 8 GB use a problem size and leading dimensions of 29600

~ $ cat lin_xeon64.txt 
Fri Dec 31 21:30:38 PST 2010
Intel(R) LINPACK data

Current date/time: Fri Dec 31 21:30:38 2010

CPU frequency:    1.800 GHz
Number of CPUs: 1
Number of cores: 2
Number of threads: 2

Parameters are set to:

Number of tests                             : 1
Number of equations to solve (problem size) : 21000
Leading dimension of array                  : 21000
Number of trials to run                     : 20   
Data alignment value (in Kbytes)            : 4    

Maximum memory requested that can be used = 3528424096, at the size = 21000

============= Timing linear equation system solver =================

Size   LDA    Align. Time(s)    GFlops   Residual     Residual(norm)
21000  21000  4      666.408    9.2659   3.591869e-10 2.884103e-02

graysky · 2011-01-01 12:44:14

Right, it is the most stressing thing I've found for CPU stability testing - more so than mprime. Anyway, you need to let it run for 10-20 iterations. The key to understanding stability is to compare the "Residual" results - they should be identical. If they are not, you have a stability problem...

ssri · 2011-01-25 17:41:02

Well, at least I'm not the only one experiencing the kworker bug that I saw from my chroot built kernel26-ck:

https://bbs.archlinux.org/viewtopic.php?id=109371

What baffles me is that whenever I compile kernels (MAKEFLAGS="-j2", using the latest makepkg.conf.pacnew), the compiler cc1 (from "top") barely rises about 60% or so. I have been accustomed to seeing two instances of it hovering around 90% or more. Everything else I compile from AUR or ABS seems okay (thunderbird-branded, clementine-git, etc). Anyways, I'm giving up since I do not really have too much time to messing around with it these days. I'll just be using the mainline kernel from now on.

graysky · 2011-01-25 20:43:38

@ssri - I am maintaining a kernel26-ck repo if you wish. See, https://bbs.archlinux.org/viewtopic.php?id=111715 and https://wiki.archlinux.org/index.php/Kernel26-ck

ssri · 2011-01-26 03:31:08

graysky wrote:

@ssri - I am maintaining a kernel26-ck repo if you wish. See, https://bbs.archlinux.org/viewtopic.php?id=111715 and https://wiki.archlinux.org/index.php/Kernel26-ck

Wow, thanks graysky! I am pretty much inundated with work these days and I don't have as much free time to tinker anymore.

graysky · 2011-01-26 21:07:12

ssri wrote:

Wow, thanks graysky! I am pretty much inundated with work these days and I don't have as much free time to tinker anymore.

You and me both, busy is good though

Arch Linux

#1 2010-12-30 02:18:19

No modules found in kernel26 package compiled via ABS

#2 2010-12-30 10:49:37

Re: No modules found in kernel26 package compiled via ABS

#3 2011-01-01 06:00:24

Re: No modules found in kernel26 package compiled via ABS

#4 2011-01-01 12:44:14

Re: No modules found in kernel26 package compiled via ABS

#5 2011-01-25 17:41:02

Re: No modules found in kernel26 package compiled via ABS

#6 2011-01-25 20:43:38

Re: No modules found in kernel26 package compiled via ABS

#7 2011-01-26 03:31:08

Re: No modules found in kernel26 package compiled via ABS

#8 2011-01-26 21:07:12

Re: No modules found in kernel26 package compiled via ABS

Board footer