Bug 137029
Summary: | Freeze with Fedora kernels | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thierry Chantry <thierry.chantry> |
Component: | kernel | Assignee: | Dave Jones <davej> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2 | CC: | pfrields, thierry.chantry, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-12-03 18:06:59 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Thierry Chantry
2004-10-25 12:02:35 UTC
Be advised that 358 is very old news, and no further work will be done on any kernel even remotely near it. You may want to retest your application with the current 640 kernel that will be in FC3's release, and similar to the RHEL4 kernel. Hi,
Ok, I will test with the 640 kernel, I'll post a conclusion later.
However, could you please answer to my first question:
>1- Is there a release note that gives differences between the Fedora
>kernel and the corresponding official kernels version (I mean
>diffrences between the 2.6.5-1.358 and the 2.6.5, for exemple) ?
I understand that you cannot support old product. The goal of my post
is more to figure out how deep are the changes that you apply to the
official kernel.
Regards.
Thierry
The changes are very minor, because whenever possible we try to integrate changes into the upstream kernel in order to make it less of a long term maintenance burden for everyone. To be honest, I feel your question is unfair because the source is available. You can see for yourself. Hi,
I have downloaded the kernel-2.6.9-1.643.src.rpm ( I didn't find the
kernel-source-2.6.9-1.643.rpm).
To make my tests, I need to rebuild the kernel.
So, is there an easy way to build kernel-source-2.6.9-1.643.rpm from
the kernel-2.6.9-1.643.src.rpm package?
>a long term maintenance burden for everyone. To be honest, I feel
>your question is unfair because the source is available. You can see
>for yourself.
Sorry but I don't think that my question is unfair (as you said). It
is pretty difficult to compare to kernel versions (even with sources
and even if there are close). The kernel source tree contains many
sub-directories and tons of files... I was only looking for a file
that gives changes that you apply in the kernel. I'll not complain if
such kind of file doesn't exit.
Any way, I trust you when you say that changes are minor. But, with
this information, once again, I don't figure out why I had a freeze
whith the 2.6.5-1.358 and not whith the 2.6.5. I don't want that you
loose your time with old kernel versions. So, I'll will try the 2.6.9-
1.643 and pray to never see again my problem with it and the next
fedora kernel versions.
Regards,
Thierry
1) kernel-sourcecode is NO LONGER DISTRIBUTED because it is LESS USEFUL than the .src.rpm. In the .src.rpm you can directly look at the patches before they are applied to the vanilla source. 2) Please learn how to use diff. 3) Is it the kernel (the entire system) or your application that freezes? Please test both 2.6.9 vanilla and 2.6.9-1.643. 1- I'm suprised that you'll no longer provide the kernel-source package. How people will be able to customize the kernel ? 2- With my .src.rpm package, what is the easiest way to get the complete source code of the 2.6.9-1.643 kernel (I mean where any necessary patches are applied and so on...: the equivalent of the kernel-source package) . As I told you in my previous post, I need to customise the kernel to make my application working correctly. 3- To answer to your third question, the entire system is frozen. Keyboard and mouse don't work. I can ping that machine any more. 4- I'll start my test this afternoon on the 2.6.9 vanilla. As soon as I will be able to customise the 2.6.9-1.643, I will test it. The 2.6.9 vanilla works perfectly. is this still causing problems with todays errata kernel ? can you post the source of the problematic module ? As I didn't reproduce this problem with the Fedora Core (kernel 2.6.9- 1.667), we can close this bug... Thanks for your help |