Red Hat Bugzilla – Bug 155017
Unisys' x86_64 ES7000 loses legacy devices during boot when using latest ES7000 platform code
Last modified: 2007-11-30 17:07:17 EST
Description of problem:
During the boot sequence on the x86_64 ES7000 machine, legacy interrupts are not
configured correctly. As a result, legacy devices (ie: IDE drives, IDE CDROM,
keyboard, mouse, etc) are not usable because their legacy mappings are not
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Build a kernel image using the latest ES7000 platform code. The latest ES7000
platform code is included as part of the consolidated patch update for ES7000,
which is located here:
2. Boot the kernel image.
The CDROM driver is stuck trying to probe for devices (intermittently printing a
message that the hda device is losing interrupts). Keyboard is also not responsive.
Created attachment 113240 [details]
ES7000 Legacy Mappings Update
This update only affects Unisys' ES7000 machines.
The patch reflects a change needed to determine which generation of ES7000 is
currently running. The next generation of ES7000s will have conventional legacy
support so the patch accommodates for this. This patch has been tested and
verified on both an authentic 5xx ES7000 box and the next generation x86-64
ES7000 box. This patch has already been accepted into the upstream LK tree.
This patch is included in 2.6.12-rc2. It's documented in
"[PATCH] ES7000 Legacy Mappings Update"
Do we have the hardware required to test this patch?
Unfortunately you do not yet have this hardware. We are trying to get some for
you as quickly as possible. We're keeping Andrius Benokraitis
(email@example.com) up-to-date on the status.
Hardware is now onsite in Westford.
Created attachment 118272 [details]
ES7000 Legacy Mappings Update for U2 Kernel
Updated for U2 kernel as requested by Andrius on IT.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.