From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1K3bff-0003pW-Ff for garchives@archives.gentoo.org; Tue, 03 Jun 2008 18:55:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CCB4FE04CB; Tue, 3 Jun 2008 18:55:45 +0000 (UTC) Received: from rv-out-0708.google.com (rv-out-0708.google.com [209.85.198.247]) by pigeon.gentoo.org (Postfix) with ESMTP id 8D65DE04CB for ; Tue, 3 Jun 2008 18:55:45 +0000 (UTC) Received: by rv-out-0708.google.com with SMTP id b17so1457180rvf.46 for ; Tue, 03 Jun 2008 11:55:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=14P9PlniZzfWE7ZvkY/QKZlxPSHimpsqMja1sLuc1ec=; b=iD6IvahJKfiz/SiKipEFraACOiImWS+w/vdUTifIt3gLy2E6hKZOd2xhPHu8KXEvNHEuoh09Tf4bpp501Qze/LvVSInLr1T6F8QliWTWJ/SAZ3pfjW+BwUCenB7RSoy+WgNObpB9blcvvz5bbpU9JLBjOisz4RsiW2UWiWofJL8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=h/Jt6VaMcR8CUF4cWWutaRoi5qQ5sAo8cY4GK2Msiwvnn6sZzyfn4aS4d0Vn8accqUY6X+pjG+odmXTv6fqLxDWGOypcKN+Zyi8igGmBL5QAhXFh/H2mZhGEuXHwWNDsng/skC9C+DgKrxoBtDefkfXhO/lW4wftOU8qMnn0Hd8= Received: by 10.141.137.8 with SMTP id p8mr5624128rvn.163.1212519345138; Tue, 03 Jun 2008 11:55:45 -0700 (PDT) Received: by 10.141.196.18 with HTTP; Tue, 3 Jun 2008 11:55:45 -0700 (PDT) Message-ID: Date: Tue, 3 Jun 2008 20:55:45 +0200 From: "Konrad Okurowski" To: gentoo-amd64@lists.gentoo.org Subject: Re: [gentoo-amd64] Re: multicore strange issue In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_22986_13603461.1212519345111" References: X-Archives-Salt: ae6a20ef-4e49-4636-8f24-11bdd6e985db X-Archives-Hash: ac95ea4a502be630dafefa508aec4115 ------=_Part_22986_13603461.1212519345111 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, IMO when performing "make" after make clean and make menuconfig (assuming you want to change something in kernel) builds kernel image and modules as well. After that I run rm -rf /lib/modules/ and make && make modules_install. Then there shouldn't be any problem. (also [emerge -av $(qdepends -CNQ virtual/linux-sources)] would be nice). Kfiaciarka 2008/6/3 Duncan <1i5t5.duncan@cox.net>: > Beso posted > d257c3560806030201y23df89fdy1cf12ae0bb3b772a@mail.gmail.com, excerpted > below, on Tue, 03 Jun 2008 09:01:04 +0000: > > > the problem is that with the old normal config the kernel detects one > > processor and one core and it works, loading the modules, but when > > enabling simetric multiprocessing the kernel detects just one processor > > and one core and then it fails to load modules because of a different > > executable format in the modules. > > This indicates that the modules and the kernel aren't matched. IOW, you > apparently compiled the new kernel but failed to compile the matching > modules, so it's trying to use the old ones, which don't match the new > kernel, so it won't load them. > > Even if it's the exact same kernel you compiled, if you change options, > particularly something as big as SMP, you'll need to recompile the kernel > modules as well. > > Also note that if you use an initrd/initramfs, you'll need to redo it, > loading the new modules as appropriate into it as well as placing them in > the normal /lib/modules// dir. I don't run an initramfs/ > initrd, so have never learned the technical intricacies thereof, but > wherever it's trying to load them from, you don't have the right ones > there for it to load. > > One way or the other, with or without the initrd/initramfs, the kernel is > trying to load modules that don't match the kernel, and failing. Correct > that, and you will have fixed at least that problem, altho it's possible > you'll then have others to fix as well. > > -- > Duncan - List replies preferred. No HTML msgs. > "Every nonfree program has a lord, a master -- > and if you use the program, he is your master." Richard Stallman > > -- > gentoo-amd64@lists.gentoo.org mailing list > > -- pozdrawiam Konrad Okurowski Key Fingerprint = D993 3823 F20D 3B8D 2719 3012 2FE8 ------=_Part_22986_13603461.1212519345111 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi,
IMO when performing "make" after make clean and make menuconfig (assuming you want to change something in kernel) builds kernel image and modules as well. After that I run rm -rf /lib/modules/<kernel dir> and make && make modules_install. Then there shouldn't be any problem. (also [emerge -av $(qdepends -CNQ virtual/linux-sources)] would be nice).

Kfiaciarka

2008/6/3 Duncan <1i5t5.duncan@cox.net>:
Beso <givemesugarr@gmail.com> posted
d257c3560806030201y23df89fdy1cf12ae0bb3b772a@mail.gmail.com, excerpted
below, on  Tue, 03 Jun 2008 09:01:04 +0000:

> the problem is that with the old normal config the kernel detects one
> processor and one core and it works, loading the modules, but when
> enabling simetric multiprocessing the kernel detects just one processor
> and one core and then it fails to load modules because of a different
> executable format in the modules.

This indicates that the modules and the kernel aren't matched.  IOW, you
apparently compiled the new kernel but failed to compile the matching
modules, so it's trying to use the old ones, which don't match the new
kernel, so it won't load them.

Even if it's the exact same kernel you compiled, if you change options,
particularly something as big as SMP, you'll need to recompile the kernel
modules as well.

Also note that if you use an initrd/initramfs, you'll need to redo it,
loading the new modules as appropriate into it as well as placing them in
the normal /lib/modules/<kern-ver>/ dir.  I don't run an initramfs/
initrd, so have never learned the technical intricacies thereof, but
wherever it's trying to load them from, you don't have the right ones
there for it to load.

One way or the other, with or without the initrd/initramfs, the kernel is
trying to load modules that don't match the kernel, and failing.  Correct
that, and you will have fixed at least that problem, altho it's possible
you'll then have others to fix as well.

--
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



--
pozdrawiam
Konrad Okurowski <dm.konrad@gmail.com>
Key Fingerprint = D993 3823 F20D 3B8D 2719 3012 2FE8 ------=_Part_22986_13603461.1212519345111-- -- gentoo-amd64@lists.gentoo.org mailing list