From: Doug Ledford <dledford@redhat.com>
To: Jeff Merkey <jmerkey@timpanogas.org>
Cc: arjan@fenrus.demon.nl, linux-kernel@vger.kernel.org
Subject: Re: [VM/MEMORY-SICKNESS] 2.4.15-pre7 kmem_cache_create invalid opcode
Date: Wed, 21 Nov 2001 14:06:55 -0500 [thread overview]
Message-ID: <3BFBFB4F.8090403@redhat.com> (raw)
In-Reply-To: <E166S8l-0007hs-00@fenrus.demon.nl> <002401c172ba$b46bed20$f5976dcf@nwfs>
Jeff Merkey wrote:
> ----- Original Message -----
> From: <arjan@fenrus.demon.nl>
> To: "Jeff Merkey" <jmerkey@timpanogas.org>
> Cc: <linux-kernel@vger.kernel.org>
> Sent: Wednesday, November 21, 2001 12:49 AM
> Subject: Re: [VM/MEMORY-SICKNESS] 2.4.15-pre7 kmem_cache_create invalid
> opcode
>
>
>
>>In article <003401c1725a$975ad4e0$f5976dcf@nwfs> you wrote:
>>
>>
>>>OK. Cool. Now we are making progress. I think this is a nasty
>>>
> problem.
>
>>>There are numerous RPMs that will build against the kernel tree and be
>>>busted. I would expect an rpm -ba on your DEFAULT kernel in Redhat with
>>>the sources contained in the kernel.rpm files to also be broken unless
>>>someone has done this.
>>>
>>That's why Red Hat ships the kernel-source RPM; you can build external
>>modules against that and it has the "make dep" information for all kernels
>>Red Hat ships for that platform (with a smart "if" that selects the
>>currently running one)........... But note the word "external". You build
>>
> in
>
>>another directory and don't touch the original .config file or tree......
>>Unless you need core changes, that's perfectly possible for almost all
>>modules....
>>
>>
>
> I would anticipate seeing this problem with their kernel source RPM. In
> fact, I do,
> you have to do a make distclean before you can use it because of the way
> their rpm
> script munges all the versioned trees into a tmp area during RPM creation.
This is not true at all. To see what I'm referring to, download the
module build kit from my website (http://people.redhat.com/dledford) and
see how it uses box stock kernel include files from our kernel-source
package to build *all* of the needed modules from one source tree (i386,
i386smp, i386BOOT, i586, i586SMP, i686, i686SMP, i686enterprise).
> There's only
> one source tree (usually the last one they built) and lots of binary rpm
> versions from the
> one tree (i.e. i386, i686, etc.).
If you look in the linux/include/linux/modversions/*.h files, you will
see that the different RPM build package versions have all their symbols
in those files #ifdef'ed so that you get the ones you need to match the
running kernel (or if you trick the rhversion.h file, whichever version
you request, see my Makefile).
> Jeff
>
>
>>Greetings,
>> Arjan van de Ven
>>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
--
Doug Ledford <dledford@redhat.com> http://people.redhat.com/dledford
Please check my web site for aic7xxx updates/answers before
e-mailing me about problems
next prev parent reply other threads:[~2001-11-21 19:07 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <davem@redhat.com>
2001-11-21 7:16 ` [VM/MEMORY-SICKNESS] 2.4.15-pre7 kmem_cache_create invalid opcode Jeff V. Merkey
2001-11-21 6:22 ` David S. Miller
2001-11-21 7:33 ` Jeff V. Merkey
2001-11-21 6:47 ` Kai Henningsen
2001-11-21 18:28 ` Jeff Merkey
2001-11-21 6:47 ` David S. Miller
2001-11-21 6:54 ` Jeff Merkey
2001-11-21 6:56 ` David S. Miller
2001-11-21 7:03 ` Jeff Merkey
2001-11-21 7:09 ` David S. Miller
2001-11-21 7:14 ` Jeff Merkey
2001-11-21 7:28 ` Stuart Young
2001-11-21 7:49 ` arjan
2001-11-21 18:31 ` Jeff Merkey
2001-11-21 19:06 ` Doug Ledford [this message]
2001-11-21 19:51 ` Jeff Merkey
2001-11-21 19:58 ` J Sloan
2001-11-21 20:38 ` Doug Ledford
2001-11-21 21:17 ` Jeff Merkey
2001-11-21 19:16 ` Arjan van de Ven
2001-11-21 19:53 ` Jeff Merkey
2001-11-21 20:36 ` Doug Ledford
2001-11-21 21:16 ` Jeff Merkey
2001-11-21 21:28 ` Robert Love
2001-11-21 6:54 ` Chris Abbey
2001-11-21 7:05 ` Jeff Merkey
2001-11-21 8:49 ` Alan Cox
2001-11-21 18:28 ` Jeff Merkey
2001-11-21 6:59 Jeff Merkey
-- strict thread matches above, loose matches on Subject: below --
2001-05-06 21:08 page_launder() bug BERECZ Szabolcs
2001-05-06 21:08 ` BERECZ Szabolcs
2001-05-06 21:59 ` Jonathan Morton
2001-05-06 21:59 ` Jonathan Morton
2001-05-06 22:07 ` BERECZ Szabolcs
2001-05-06 22:07 ` BERECZ Szabolcs
2001-05-07 4:55 ` David S. Miller
2001-05-07 4:55 ` David S. Miller
2001-05-07 5:19 ` Aaron Lehmann
2001-05-07 5:19 ` Aaron Lehmann
2001-05-07 6:26 ` Tobias Ringstrom
2001-05-07 6:26 ` Tobias Ringstrom
2001-05-07 8:54 ` David S. Miller
2001-05-07 8:54 ` David S. Miller
2001-05-07 15:12 ` Tobias Ringstrom
2001-05-07 15:12 ` Tobias Ringstrom
2001-05-07 8:59 ` Helge Hafting
2001-05-07 19:02 ` J . A . Magallon
2001-05-08 7:52 ` Helge Hafting
2001-05-10 12:19 ` Ingo Oeser
2001-05-10 10:51 ` Anuradha Ratnaweera
2001-05-07 10:52 ` Alan Cox
2001-05-07 10:52 ` Alan Cox
2001-05-07 13:49 ` Daniel Phillips
2001-05-07 13:49 ` Daniel Phillips
2001-05-07 13:53 ` H. Peter Anvin
2001-05-07 14:52 ` Horst von Brand
2001-05-07 14:52 ` Horst von Brand
2001-05-08 17:59 ` Kai Henningsen
2001-05-09 2:32 ` Rusty Russell
2001-05-09 2:32 ` Rusty Russell
2001-05-09 8:43 ` Martin Dalecki
2001-05-09 8:43 ` Martin Dalecki
2001-05-09 3:36 ` Jonathan Morton
2001-05-09 3:36 ` Jonathan Morton
2001-05-07 17:59 ` Linus Torvalds
2001-05-07 21:22 ` Marcelo Tosatti
2001-05-07 23:23 ` Linus Torvalds
2001-05-07 21:50 ` Marcelo Tosatti
2001-05-07 23:52 ` Linus Torvalds
2001-05-07 22:26 ` Marcelo Tosatti
2001-05-08 0:16 ` David S. Miller
2001-05-08 2:34 ` Linus Torvalds
2001-05-08 1:40 ` Marcelo Tosatti
2001-05-08 3:22 ` David S. Miller
2001-05-08 3:26 ` Linus Torvalds
2001-05-08 3:46 ` Linus Torvalds
2001-05-08 2:37 ` Marcelo Tosatti
2001-05-08 6:50 ` David S. Miller
2001-05-08 7:40 ` Linus Torvalds
2001-05-08 8:29 ` David S. Miller
2001-05-08 18:53 ` Marcelo Tosatti
2001-05-08 21:16 ` Marcelo Tosatti
2001-05-08 23:38 ` Linus Torvalds
2001-05-08 23:53 ` Marcelo Tosatti
2001-05-09 2:13 ` David S. Miller
2001-05-09 17:38 ` Marcelo Tosatti
2001-05-09 20:05 ` David S. Miller
2001-05-09 18:40 ` Marcelo Tosatti
2001-05-09 21:08 ` David S. Miller
2001-05-09 19:50 ` Marcelo Tosatti
2001-05-13 16:34 ` Rik van Riel
2001-05-13 17:52 ` David S. Miller
2001-05-13 17:55 ` Rik van Riel
2001-05-13 18:00 ` David S. Miller
2001-05-13 19:34 ` Linus Torvalds
2001-05-13 19:39 ` Rik van Riel
2001-05-13 20:42 ` Linus Torvalds
2001-05-14 7:05 ` Kai Henningsen
2001-05-08 2:47 ` David S. Miller
2001-05-08 1:34 ` Marcelo Tosatti
2001-05-08 3:18 ` David S. Miller
2001-05-08 1:47 ` Marcelo Tosatti
2001-05-08 3:29 ` David S. Miller
2001-05-08 10:36 ` BERECZ Szabolcs
2001-05-08 3:24 ` Linus Torvalds
2001-05-08 12:33 ` Mikulas Patocka
2001-05-13 16:24 ` Rik van Riel
2001-05-13 21:02 ` Another VM race? (was: page_launder() bug) Mikulas Patocka
2001-05-13 23:04 ` Rik van Riel
2001-05-14 9:53 ` Mikulas Patocka
2001-05-08 2:29 ` page_launder() bug Linus Torvalds
2001-05-13 16:08 ` Rik van Riel
2001-05-13 19:29 ` Linus Torvalds
2001-05-14 22:05 ` Marcelo Tosatti
2001-05-08 0:06 ` David S. Miller
2001-05-07 23:31 ` David S. Miller
2001-05-07 22:44 ` David S. Miller
2001-05-08 1:00 ` Horst von Brand
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=3BFBFB4F.8090403@redhat.com \
--to=dledford@redhat.com \
--cc=arjan@fenrus.demon.nl \
--cc=jmerkey@timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.