<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Proliant polyserver going down without explanation in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/proliant-polyserver-going-down-without-explanation/m-p/4322007#M62799</link>
    <description>This is an explanation from one site&lt;BR /&gt;&lt;BR /&gt;HP's net official Problem Q &amp;amp; A.&lt;BR /&gt;&lt;A href="http://h50069.www5.hp.com/e-Delivery3/Forum/WebUI/Messages/ShowTopic.aspx?RID=7fdf53c6-d5ed-4e6d-904c-ffb4e11c671e" target="_blank"&gt;http://h50069.www5.hp.com/e-Delivery3/Forum/WebUI/Messages/ShowTopic.aspx?RID=7fdf53c6-d5ed-4e6d-904c-ffb4e11c671e&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Solution&lt;BR /&gt;&lt;BR /&gt;Grub.conf in lilo.conf file or add ide = nodma parameters in order to disable the DMA function. To Red Hat Linux 7.2, for example, the revised document grub.conf reads as follows:&lt;BR /&gt;&lt;BR /&gt;image=/boot/vmlinuz-2.4.2-2smp image = / boot/vmlinuz-2.4.2-2smp&lt;BR /&gt;label=linux label = linux&lt;BR /&gt;initrd=/boot/initrd-2.4.2-2smp.img initrd = / boot/initrd-2.4.2-2smp.img&lt;BR /&gt;read-only&lt;BR /&gt;root=/dev/cciss/c0d0p5 root = / dev/cciss/c0d0p5&lt;BR /&gt;append="ide=nodma" append = "ide = nodma"&lt;BR /&gt;Related systemsï¼ ProLiant DL380, ProLiant DL380 G2, ProLiant DL580, ProLiant ML330, ProLiant ML350, ProLiant ML370, ProLiant ML370 G2, ProLiant ML530, ProLiant ML570 Related systems: ProLiant DL380, ProLiant DL380 G2, ProLiant DL580, ProLiant ML330, ProLiant ML350, ProLiant ML370, ProLiant ML370 G2, ProLiant ML530, ProLiant ML570</description>
    <pubDate>Sun, 14 Dec 2008 04:08:00 GMT</pubDate>
    <dc:creator>Jeeshan</dc:creator>
    <dc:date>2008-12-14T04:08:00Z</dc:date>
    <item>
      <title>Proliant polyserver going down without explanation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-polyserver-going-down-without-explanation/m-p/4322006#M62798</link>
      <description>I have two proliant dl380 g5's running Red Hat 4, update 6, 64-bit. They're running Polyserve Matrix Server and are connected to two HP EVA's via brocade fibre switches.&lt;BR /&gt;&lt;BR /&gt;One of these servers has twice gone down without explanation. The first time was in August, the second last weekend, but both times, when I powered it back up it came back up fine and no one can figure out why it went down. I've run the Smartstart Diagnostics in a loop 5 times with no results, and there's nothing in the logs to indicate what the cause may be. The only thing I see which looks suspicious is the following entry in the messages file which seems to happen pretty frequently, though not necessarily when it went down:&lt;BR /&gt;&lt;BR /&gt;Dec  7 04:18:50 polynas1 kernel: ide-cd: cmd 0x1e timed out&lt;BR /&gt;Dec  7 04:18:50 polynas1 kernel: hda: irq timeout: status=0xd0 { Busy }&lt;BR /&gt;Dec  7 04:18:50 polynas1 kernel: hda: irq timeout: error=0x00&lt;BR /&gt;Dec  7 04:18:50 polynas1 kernel: hda: ATAPI reset complete&lt;BR /&gt;&lt;BR /&gt;HDA is the cd-rom drive; the hard drives are SATA. No cd-rom is in the drive. Anyone ever seen something like this?</description>
      <pubDate>Thu, 11 Dec 2008 21:10:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-polyserver-going-down-without-explanation/m-p/4322006#M62798</guid>
      <dc:creator>Tim Barton</dc:creator>
      <dc:date>2008-12-11T21:10:59Z</dc:date>
    </item>
    <item>
      <title>Re: Proliant polyserver going down without explanation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/proliant-polyserver-going-down-without-explanation/m-p/4322007#M62799</link>
      <description>This is an explanation from one site&lt;BR /&gt;&lt;BR /&gt;HP's net official Problem Q &amp;amp; A.&lt;BR /&gt;&lt;A href="http://h50069.www5.hp.com/e-Delivery3/Forum/WebUI/Messages/ShowTopic.aspx?RID=7fdf53c6-d5ed-4e6d-904c-ffb4e11c671e" target="_blank"&gt;http://h50069.www5.hp.com/e-Delivery3/Forum/WebUI/Messages/ShowTopic.aspx?RID=7fdf53c6-d5ed-4e6d-904c-ffb4e11c671e&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Solution&lt;BR /&gt;&lt;BR /&gt;Grub.conf in lilo.conf file or add ide = nodma parameters in order to disable the DMA function. To Red Hat Linux 7.2, for example, the revised document grub.conf reads as follows:&lt;BR /&gt;&lt;BR /&gt;image=/boot/vmlinuz-2.4.2-2smp image = / boot/vmlinuz-2.4.2-2smp&lt;BR /&gt;label=linux label = linux&lt;BR /&gt;initrd=/boot/initrd-2.4.2-2smp.img initrd = / boot/initrd-2.4.2-2smp.img&lt;BR /&gt;read-only&lt;BR /&gt;root=/dev/cciss/c0d0p5 root = / dev/cciss/c0d0p5&lt;BR /&gt;append="ide=nodma" append = "ide = nodma"&lt;BR /&gt;Related systemsï¼ ProLiant DL380, ProLiant DL380 G2, ProLiant DL580, ProLiant ML330, ProLiant ML350, ProLiant ML370, ProLiant ML370 G2, ProLiant ML530, ProLiant ML570 Related systems: ProLiant DL380, ProLiant DL380 G2, ProLiant DL580, ProLiant ML330, ProLiant ML350, ProLiant ML370, ProLiant ML370 G2, ProLiant ML530, ProLiant ML570</description>
      <pubDate>Sun, 14 Dec 2008 04:08:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/proliant-polyserver-going-down-without-explanation/m-p/4322007#M62799</guid>
      <dc:creator>Jeeshan</dc:creator>
      <dc:date>2008-12-14T04:08:00Z</dc:date>
    </item>
  </channel>
</rss>

