Bug 615061 - hald hangs only with MRG and the Sealevel 5102 present on an x86 platform
Summary: hald hangs only with MRG and the Sealevel 5102 present on an x86 platform
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel
Version: 1.3
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: John Kacur
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-15 20:48 UTC by davaid.pierce@delphiresearch.com
Modified: 2013-02-27 14:25 UTC (History)
4 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2013-02-27 14:25:56 UTC


Attachments (Terms of Use)
An excerpt from the /var/log/messages file. search on "ttySM0" (the Sealevel device) and occurrences of "Critical error" (588.25 KB, application/octet-stream)
2010-07-15 20:48 UTC, davaid.pierce@delphiresearch.com
no flags Details

Description davaid.pierce@delphiresearch.com 2010-07-15 20:48:50 UTC
Created attachment 432224 [details]
An excerpt from the /var/log/messages file.  search on "ttySM0" (the Sealevel device) and occurrences of "Critical error"

Description of problem:
With the realtime kernel (MRG) on an x86 platform and a Sealevel 5102 communications card inserted into a regular PCI slot (not PCI express) the platform hangs without recovery during boot when the HAL daemon is being loaded.

Version-Release number of selected component (if applicable):
Linux 2.6.24.7-149.el5rt
hal-0.5.8.1-59.el5.i386

How reproducible:
Reboot the system

Steps to Reproduce:
1.Press reset button on system
2.
3.
  
Actual results:
HAL daemon hangs indefinitely


Expected results:
Boot successful


Additional info:
See attachment of the /var/log/messages file showing exception in the boot process.

Comment 1 Steven Rostedt 2013-02-27 14:08:14 UTC
This goes against the MRG product.

Comment 2 John Kacur 2013-02-27 14:25:56 UTC
This bug is for a kernel version that is no-longer supported. If you have any problems with the supported versions, then please open a new bug for that.


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