Bug 659480 – UV: WAR for interrupt-IOPort deadlock

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 659480 - UV: WAR for interrupt-IOPort deadlock

Summary:	UV: WAR for interrupt-IOPort deadlock

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	kernel (Show other bugs)
Sub Component:
Version:	6.0
Hardware:	x86_64 Linux

Priority	urgent Severity urgent
Target Milestone:	rc
Target Release:	---
Assigned To:	George Beshers
QA Contact:	Red Hat Kernel QE team
Docs Contact:

URL:
Whiteboard:
Keywords:	ZStream

Depends On:
Blocks:	662543 661953 662921
	Show dependency tree / graph

Reported:	2010-12-02 16:24 EST by George Beshers
Modified:	2011-05-19 08:04 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:	kernel-2.6.32-92.el6
Doc Type:	Bug Fix
Doc Text:	Prior to this update, running the hwclock --systohc command could halt a running system. This was due to the interrupt transactions being looped back from a local IOH (Input/Output Hub), through the IOH to a local CPU (erroneously), which caused a conflict with I/O port operations and other transactions. With this update, the conflicts are avoided and the system continues to run after executing the hwclock --systohc command.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2011-05-19 08:04:24 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Tested patch (7.01 KB, patch) 2010-12-02 16:24 EST, George Beshers	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2011:0542	normal	SHIPPED_LIVE	Important: Red Hat Enterprise Linux 6.1 kernel security, bug fix and enhancement update	2011-05-19 07:58:07 EDT

Groups: None (edit)

Description George Beshers 2010-12-02 16:24:51 EST

Created attachment 464378 [details]
Tested patch

Description of problem:
  Problem originally noticed when
  'hwclock --systohc' halted a running system.



Version-Release number of selected component (if applicable):
  kernel-2.6.32-71


How reproducible:
  Easily, but not 100%.


Steps to Reproduce:
1. boot system on UV hardware
2. hwclock --systohc    ## ususally sufficient
3. hwclock

On one system also had to do the following before running it:
	echo 4 >/proc/irq/8/smp_affinity
then run hwclock.



  
Actual results:

  System halts with CATERR.


Expected results:
  System continues to run.


Additional info:
  The attached patch has been tested inside SGI on multiple systems.

PV# 1012363

Comment 3 George Beshers 2010-12-03 16:19:15 EST

Went ahead and posted as this was seen at a customer site.

Comment 4 George Beshers 2010-12-13 13:18:46 EST

Reposted per Don's and Aristeu's request.

George

Comment 7 Aristeu Rozanski 2010-12-16 15:54:21 EST

Patch(es) available on kernel-2.6.32-92.el6

Comment 9 George Beshers 2010-12-22 12:43:48 EST

This has been tested on both UV100 and a very large UV1000
system inside SGI; the problem is solved :).

George

Comment 11 Martin Prpič 2011-02-23 10:12:02 EST

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Prior to this update, running the hwclock --systohc command could halt a running system. This was due to the interrupt transactions being looped back from a local IOH (Input/Output Hub), through the IOH to a local CPU (erroneously), which caused a conflict with I/O port operations and other transactions. With this update, the conflicts are avoided and the system continues to run after executing the hwclock --systohc command.

Comment 12 errata-xmlrpc 2011-05-19 08:04:24 EDT

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 therefore 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.

http://rhn.redhat.com/errata/RHSA-2011-0542.html

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