Bug 974608

Summary:

Panic on HP BL460c G1 with 3.8 debug kernel

Product:

Red Hat Enterprise MRG

Reporter:

Clark Williams <williams>

Component:

realtime-kernel

Assignee:

John Kacur <jkacur>

Status:

CLOSED ERRATA

QA Contact:

MRG Quality Engineering <mrgqe-bugs>

Severity:

high

Docs Contact:

Priority:

unspecified

Version:

Development

CC:

bhu, davids, jkacur, jkastner, lgoncalv

Target Milestone:

2.4

Target Release:

---

Hardware:

x86_64

OS:

Linux

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Cause: acpi_glb_hardware_lock was converted to sleeping spinlock (rt_mutex_t) by RT patchset Consequence: Panic due to sleeping in atomic context Fix: Convert back to raw_spinlock_t Result: No panic, correct operation.

Story Points:

---

Clone Of:

Environment:

Last Closed:

2013-10-01 16:43:47 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
Boot log of kernel panic	none

Description Clark Williams 2013-06-14 15:02:10 UTC

Created attachment 761313 [details]
Boot log of kernel panic

Description of problem:
Panic observed on debug kernel running on HP BL460c G1

Version-Release number of selected component (if applicable):
kernel-rt-3.8.13-rt10.4.el6rt.x86_64.debug

beaker job: https://beaker.engineering.redhat.com/jobs/434497

Comment 1 John Kacur 2013-06-14 17:26:44 UTC

Steven Rostedt suggests 3de16f6802b0df5eedaf3042800e289154f78e7b
so, forward porting that.

Comment 2 Beth Uptagrafft 2013-06-19 13:53:50 UTC

Sucessfully re-ran the tier1 tests on all kernel variants using 3.8.13-rt11.6, which contians this patch. No panics.

See beaker job: https://beaker.engineering.redhat.com/jobs/436875

Comment 6 errata-xmlrpc 2013-10-01 16:43:47 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1398.html