Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 162735 - LTC8356-LSB runtime testcase T.c_oflag_X failed [PATCH]
Summary: LTC8356-LSB runtime testcase T.c_oflag_X failed [PATCH]
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: powerpc
OS: Linux
Target Milestone: ---
Assignee: David Howells
QA Contact: Brian Brock
Depends On:
Blocks: 168424 173579
TreeView+ depends on / blocked
Reported: 2005-07-08 06:06 UTC by Issue Tracker
Modified: 2007-11-30 22:07 UTC (History)
5 users (show)

Fixed In Version: RHSA-2006-0144
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-03-15 16:12:48 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0144 qe-ready SHIPPED_LIVE Moderate: Updated kernel packages available for Red Hat Enterprise Linux 3 Update 7 2006-03-15 05:00:00 UTC

Description Issue Tracker 2005-07-08 06:06:40 UTC
Escalated to Bugzilla from IssueTracker

Comment 18 Ernie Petrides 2005-07-14 20:17:53 UTC
Correcting "hardware" field -- this is ppc64-specific according to Issue Tracker.

Comment 22 Ernie Petrides 2005-11-18 04:48:57 UTC
A fix for this problem has just been committed to the RHEL3 U7
patch pool this evening (in kernel version 2.4.21-37.9.EL).

These changes will also need to be propagated to the
"glibc-kernheaders" component in a separate commit.

Comment 26 Red Hat Bugzilla 2006-03-15 16:12:49 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.