Re: RedHat 7.2 Kernel inconsistencies...
Rick Warner <[email protected]>
| Newsgroups | gmane.linux.redhat.release.enigma |
|---|---|
| Message-ID | <Pine.LNX.4.44.0303071435270.15696-100000@aligote.inviosoftware.com> |
You can check what options are used in each build. Get the kernel-source RPM for that particular kernel, install it, then grab the appropriate config file for your processor from /usr/src/linux/configs. Do a diff on the configs from various releases of the kernel. My suspicion is that you will find them amazingly consistent; the builds of the kernels are automated with source code control so it is easy to be consistent but difficult to be inconsistent. The kernel upgrades that have been coming out are for the most fixes to security or other issues usually related to one or more device drivers. Best guess is the problem is really a problem in Kylix that is being triggered by certain conditions. - rick - On Fri, 7 Mar 2003, Hebert, Fred wrote: > I am seeing problems in RedHat kernels, where previously fixed bugs are > reappearing. One annoying one is the KYLIX "file open" dialog lock up > problem that comes and goes. > > The original kernel that shipped with 7.2 worked fine. Then after upgrading > the kernel, I encountered this lockup problem. Falling back to the old > kernel got me going again. > > When the next kernel came out (sorry but I don't remember the version), it > worked fine (no lockup). I assumed we were past the "problem". > > Along comes the next kernel, and the lockup problem is back. It seems that > every new kernel fixes or breaks the KYLIX "file open" dialog. > > On Borland's site their solution is to use the older kernel, but I would > really like to have the latest kernel, and figure out what is causing the > problem. > > I am suspecting that the kernels are being built by different people within > RedHat and the kernel options or libraries are not always consistent. This > also concerns me because other, previously fixed, bugs or vulnerabilities > may reappear? > > Does anyone have any ideas about this problem? > > Fred Hebert > [email protected] > >