Bug 58671
Summary: | Tux 2.0, Samba 2.2.x, Apache 1.3.19 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | william rose <wrose> |
Component: | kernel | Assignee: | Ingo Molnar <mingo> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-08 00:30:45 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
william rose
2002-01-22 17:13:50 UTC
The cause is not gcc 2.96. 2.96 has proven to be a very stable compiler and is even recommended (next to *one* other gcc version) by Linus Torvalds for kernel use (in fact, Linus himself uses 2.96). We released a 2.4.9 kernel for 7.1 with a much upgraded TUX, it might be worth upgrading to that... do current kernels still produce this problem? I have upgraded both machines to 7.2 and then applied the 2.4.9-31 kernel along with the needed mod utils and newer tux userspace rpms. So far, everything is fine. I would say the problem was in the older tux, this can/should be closed... |