<?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 Test Method for HP Drivers? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/test-method-for-hp-drivers/m-p/3312430#M12788</link>
    <description>The binary CCISS (Smart Array 5i) driver in the latest Support Pack, 7.10, isn't supported on the RedHat Enterprise 3 kernel I want to use:  2.4.21-15EL.  Plus I want to tweak that kernel further (disable Out of Memory killer).&lt;BR /&gt;&lt;BR /&gt;Yes I know that HP and RedHat both recommend not doing that.&lt;BR /&gt;&lt;BR /&gt;But good advice aside, if I end up using the kernel I want with the HP CCISS driver I want (2.4.48-12 from Support Pack 7.10), what's the best way for me to validate how robust it is (rather than waiting for a production failure)?&lt;BR /&gt;&lt;BR /&gt;In other words, I want to know what HP's test suite is for that component.&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;Mark&lt;BR /&gt;</description>
    <pubDate>Tue, 22 Jun 2004 18:23:28 GMT</pubDate>
    <dc:creator>Mark Travis</dc:creator>
    <dc:date>2004-06-22T18:23:28Z</dc:date>
    <item>
      <title>Test Method for HP Drivers?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/test-method-for-hp-drivers/m-p/3312430#M12788</link>
      <description>The binary CCISS (Smart Array 5i) driver in the latest Support Pack, 7.10, isn't supported on the RedHat Enterprise 3 kernel I want to use:  2.4.21-15EL.  Plus I want to tweak that kernel further (disable Out of Memory killer).&lt;BR /&gt;&lt;BR /&gt;Yes I know that HP and RedHat both recommend not doing that.&lt;BR /&gt;&lt;BR /&gt;But good advice aside, if I end up using the kernel I want with the HP CCISS driver I want (2.4.48-12 from Support Pack 7.10), what's the best way for me to validate how robust it is (rather than waiting for a production failure)?&lt;BR /&gt;&lt;BR /&gt;In other words, I want to know what HP's test suite is for that component.&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;Mark&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jun 2004 18:23:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/test-method-for-hp-drivers/m-p/3312430#M12788</guid>
      <dc:creator>Mark Travis</dc:creator>
      <dc:date>2004-06-22T18:23:28Z</dc:date>
    </item>
    <item>
      <title>Re: Test Method for HP Drivers?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/test-method-for-hp-drivers/m-p/3312431#M12789</link>
      <description>If HP has anything like what you wish I don't think(could be wrong) they would unleash it on an unwary public.&lt;BR /&gt;&lt;BR /&gt;A better test anyway would be to put the change on a test server thats used heavily and watch for instability.&lt;BR /&gt;&lt;BR /&gt;Test tools don't do real life so well.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 22 Jun 2004 19:39:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/test-method-for-hp-drivers/m-p/3312431#M12789</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-06-22T19:39:29Z</dc:date>
    </item>
  </channel>
</rss>

