Bug 197580
| Summary: | Installation doesn't work on s390 (using hercules) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Matthias Saou <matthias> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | hannsj_uhl, jarod, jglauber, karsten, triage, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | s390 | ||
| OS: | Linux | ||
| Whiteboard: | bzcl34nup | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-06-04 19:36:38 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 200020 | ||
|
Description
Matthias Saou
2006-07-04 10:22:52 UTC
doesn't work on 'real' hardware either. tested with rawhide-20060703/s390. s390 and s390x both fail with these messages FWIW, I've just tried an installation of RHEL4u3 and right after : [...] Select which protocol should be used for the CTC interface 0 for compatibility with p.e. VM TCP service machine (default) 1 for enhanced package checking for Linux peers 3 for compatibility with OS/390 or z/OS peers .1 1 which is when the above runaway loop appears, it continues fine with : CTC driver Version: 1.63 initialized divert: not allocating divert_blk for non-ethernet device ctc0 ctc0: read: ch-0.0.0600, write: ch-0.0.0601, proto: 1 Enter your DNS server(s), separated by colons (:): .192.168.1.1:192.168.1.2 192.168.1.1:192.168.1.2 Enter your DNS search domain(s) (if any), separated by colons (:): [...] not sure what code runs right before the ctc device initialization, but that's where it fails. Punting to kernel for now. Jan, any news here ? This still happens with 2.6.17-1.2432.el5.s390x An error like: "request_module: runaway loop modprobe" usually means that it was tried to load a 32 bit module under a 64 bit kernel or a 64 bit module in a 64 bit kernel. Can you check if kernel and modules fit together? I will try to recreate the problem, but the installation will take me some time... Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. FWIW, RHEL4.6 s390x installs just fine under current rawhide x86_64 hercules. Will put trying RHEL5 s390x on the TODO list... Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Given we're not doing builds for s390 in Fedora right now, keeping two year old bugs open seems pointless with the amount of change that occurs upstream. |