<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: SERR/PERR errors on IBM&#8217;s System x3650</title>
	<atom:link href="http://projectdream.org/wordpress/2007/05/14/serrperr-errors-on-ibms-system-x3650/feed/" rel="self" type="application/rss+xml" />
	<link>http://projectdream.org/wordpress/2007/05/14/serrperr-errors-on-ibms-system-x3650/</link>
	<description>The experiences of an SMB IT technician</description>
	<lastBuildDate>Fri, 30 Jul 2010 04:17:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Anonymous</title>
		<link>http://projectdream.org/wordpress/2007/05/14/serrperr-errors-on-ibms-system-x3650/comment-page-1/#comment-3502</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Mon, 20 Apr 2009 13:21:07 +0000</pubDate>
		<guid isPermaLink="false">http://projectdream.org/wordpress/2007/05/14/serrperr-errors-on-ibms-system-x3650/#comment-3502</guid>
		<description>http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5073434&amp;brandind=5000008

Symptom

If the System x3650 on-board SAS controller is disabled and a warm-reset occurs, the following events will be logged by the Baseboard Management Controller (BMC):

    Timestamp: OEM Message-No Timestamp Available
    Entry Details: OEM SEL DATA 00 00 00 00 00 E3 25 86 80 00 00 FF 00
    Timestamp: OEM Message-No Timestamp Available
    Entry Details: OEM SEL DATA 02 00 00 FF 00 00 00 00 20 00 00 00 00 

If a Remote Supervisor Adapter (RSA) II is installed, the same error will be logged with the following events:

    Software NMI
    Unknown SERR/PERR detected on PCI bus Chassis#=NA Slot#=0 Bus#=0 Dev.ID=0x25e3 Vend.ID=0x8086 Status=0x0 DevFun#=0xff
    SMI handler reporting PCIE Industry Standard Register Dump: Industry Standard ID = 0x02, 0x00, 0x00, 0xff, 0x00, 0x00, 0x00, 0x00, 0x20, 0x00, 0x00, 0x00 

Affected configurations

The system may be any of the following IBM servers:

    * System x3650, Type 1914, any model
    * System x3650, Type 7979, any model

The system is configured with one or more of the following IBM Options:

    * ServeRAID-8k SAS Controller, Option 25R8064, replacement part number 25R8076
    * ServeRAID-8k-l SAS Controller, Option 39R8729, replacement part number 25R8079

This tip is not software specific.
Workaround

When disabling the SAS controller, save BIOS changes and perform a cold reset.
Additional information

The SAS controller completes POST and is active before F1 BIOS settings can be modified to disable the SAS controller. When a warm reset occurs, SAS controller activity during PCI bus re-initialization results in the logged errors. When a cold reset is performed, there is no SAS controller activity during PCI bus initialization.</description>
		<content:encoded><![CDATA[<p><a href="http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5073434&amp;brandind=5000008" rel="nofollow">http://www-947.ibm.com/systems/support/supportsite.wss/docdisplay?lndocid=MIGR-5073434&amp;brandind=5000008</a></p>
<p>Symptom</p>
<p>If the System x3650 on-board SAS controller is disabled and a warm-reset occurs, the following events will be logged by the Baseboard Management Controller (BMC):</p>
<p>    Timestamp: OEM Message-No Timestamp Available<br />
    Entry Details: OEM SEL DATA 00 00 00 00 00 E3 25 86 80 00 00 FF 00<br />
    Timestamp: OEM Message-No Timestamp Available<br />
    Entry Details: OEM SEL DATA 02 00 00 FF 00 00 00 00 20 00 00 00 00 </p>
<p>If a Remote Supervisor Adapter (RSA) II is installed, the same error will be logged with the following events:</p>
<p>    Software NMI<br />
    Unknown SERR/PERR detected on PCI bus Chassis#=NA Slot#=0 Bus#=0 Dev.ID=0x25e3 Vend.ID=0&#215;8086 Status=0&#215;0 DevFun#=0xff<br />
    SMI handler reporting PCIE Industry Standard Register Dump: Industry Standard ID = 0&#215;02, 0&#215;00, 0&#215;00, 0xff, 0&#215;00, 0&#215;00, 0&#215;00, 0&#215;00, 0&#215;20, 0&#215;00, 0&#215;00, 0&#215;00 </p>
<p>Affected configurations</p>
<p>The system may be any of the following IBM servers:</p>
<p>    * System x3650, Type 1914, any model<br />
    * System x3650, Type 7979, any model</p>
<p>The system is configured with one or more of the following IBM Options:</p>
<p>    * ServeRAID-8k SAS Controller, Option 25R8064, replacement part number 25R8076<br />
    * ServeRAID-8k-l SAS Controller, Option 39R8729, replacement part number 25R8079</p>
<p>This tip is not software specific.<br />
Workaround</p>
<p>When disabling the SAS controller, save BIOS changes and perform a cold reset.<br />
Additional information</p>
<p>The SAS controller completes POST and is active before F1 BIOS settings can be modified to disable the SAS controller. When a warm reset occurs, SAS controller activity during PCI bus re-initialization results in the logged errors. When a cold reset is performed, there is no SAS controller activity during PCI bus initialization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bibekananda Ghosh</title>
		<link>http://projectdream.org/wordpress/2007/05/14/serrperr-errors-on-ibms-system-x3650/comment-page-1/#comment-3236</link>
		<dc:creator>Bibekananda Ghosh</dc:creator>
		<pubDate>Thu, 22 Jan 2009 09:25:10 +0000</pubDate>
		<guid isPermaLink="false">http://projectdream.org/wordpress/2007/05/14/serrperr-errors-on-ibms-system-x3650/#comment-3236</guid>
		<description>Hi,

use Nero for burning the cd. Go to copy and backup option-&gt; then select Burn image to disc. select the iso image you want to burn. on Files of type select All files.

Hope it will solve the issue... happy installation.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>use Nero for burning the cd. Go to copy and backup option-&gt; then select Burn image to disc. select the iso image you want to burn. on Files of type select All files.</p>
<p>Hope it will solve the issue&#8230; happy installation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kohl</title>
		<link>http://projectdream.org/wordpress/2007/05/14/serrperr-errors-on-ibms-system-x3650/comment-page-1/#comment-1481</link>
		<dc:creator>kohl</dc:creator>
		<pubDate>Fri, 21 Sep 2007 09:17:34 +0000</pubDate>
		<guid isPermaLink="false">http://projectdream.org/wordpress/2007/05/14/serrperr-errors-on-ibms-system-x3650/#comment-1481</guid>
		<description>I have an IBM Server eServer Xseries 206. I have downloaded serverguide and installation cd with a .iso extension, however when I burn it to cd it still remains in that format and is not bootable. Please can anyone help on how I can convert it to normal file type and make it bootable. Thank you.</description>
		<content:encoded><![CDATA[<p>I have an IBM Server eServer Xseries 206. I have downloaded serverguide and installation cd with a .iso extension, however when I burn it to cd it still remains in that format and is not bootable. Please can anyone help on how I can convert it to normal file type and make it bootable. Thank you.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
