Bug 164784 - installer get hung after Continues APIC error
Summary: installer get hung after Continues APIC error
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Jim Paradis
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-01 12:45 UTC by eranna
Modified: 2013-08-06 01:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-03-01 00:44:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description eranna 2005-08-01 12:45:49 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; {5496F574-A294-4C6E-8957-6C10C1F8C1EF}; .NET CLR 1.1.4322)

Description of problem:
i am getting APIC error on CPU: 60(60) 

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


How reproducible:
Always

Steps to Reproduce:
1.just Load OS 
2. run Apache sever and do some load stress
3. check in Dmesg 
  

Actual Results:  seeing Continues Apic error

Additional info:

Comment 1 Suzanne Hillman 2005-08-01 19:06:29 UTC
As this appears to be a support request, please either contact Red Hat's Technical
Support line at 888-GO-REDHAT or file a web ticket at
http://www.redhat.com/apps/support/.  Bugzilla is not an official support
channel, has no response guarantees, and may not route your issue to the correct
area to assist you.  Using the official support channels above will guarantee
that your issue is handled appropriately and routed to the individual or group
which can best assist you with this issue and will also allow Red Hat to track
the issue, ensuring that any applicable bug fix is included in all releases and
is not dropped from a future update or major release.


Comment 2 Jim Paradis 2006-03-01 00:44:20 UTC
Since this should have been filed as a support request, and since there has been
no activity on it for six months, I am closing this report.


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