<?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: I64 V8.2-1 update DVD gets CPUSANITY Bugcheck in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652151#M71999</link>
    <description>Jim,&lt;BR /&gt;&lt;BR /&gt;let me try to summarize this:&lt;BR /&gt;&lt;BR /&gt;OpenVMS I64 only supports the A6826A (Dual port fibre channel PCI-X HBA), also called QLogic ISP2312, which is driven by SYS$PGQDRIVER (a port driver to the existing DKDRIVER). The devices are still called FGA0, FGB0 ...&lt;BR /&gt;&lt;BR /&gt;For instructions on how to verify installation of the A6826A FC HBA see:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/A6826-96007/ch02s07.html" target="_blank"&gt;http://docs.hp.com/en/A6826-96007/ch02s07.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you've seen SYS$FGEDRIVER in one of the registers in the MACHINECHK crash, this seems to indicate, that you were using an unsupported FC HBA.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
    <pubDate>Thu, 20 Oct 2005 06:43:51 GMT</pubDate>
    <dc:creator>Volker Halle</dc:creator>
    <dc:date>2005-10-20T06:43:51Z</dc:date>
    <item>
      <title>I64 V8.2-1 update DVD gets CPUSANITY Bugcheck</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652145#M71993</link>
      <description>I am trying to update by I64 HP rx2600  (1.40GHz/1.5MB)OpenVMS V8.2 to V8.2-1.  I have updated the firmware from:&lt;BR /&gt; MP FW     : E.02.29&lt;BR /&gt; BMC FW    : 01.52&lt;BR /&gt; EFI FW    : 01.22&lt;BR /&gt; System FW : 02.31&lt;BR /&gt;to:&lt;BR /&gt; MP FW     : E.03.15&lt;BR /&gt; BMC FW    : 01.53&lt;BR /&gt; EFI FW    : 01.22&lt;BR /&gt; System FW : 02.31&lt;BR /&gt;When I boot up on the V8.2-1 CD, I get the following:&lt;BR /&gt;&lt;BR /&gt; 1)  Upgrade, install or reconfigure OpenVMS I64 Version V8.2-1&lt;BR /&gt; 2)  Display products and patches that this procedure can install&lt;BR /&gt; 3)  Install or upgrade layered products and patches&lt;BR /&gt; 4)  Show installed products&lt;BR /&gt; 5)  Reconfigure installed products&lt;BR /&gt; 6)  Remove installed products&lt;BR /&gt; 7)  Execute DCL commands and procedures&lt;BR /&gt; 8)  Shut down this system&lt;BR /&gt;Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) &lt;BR /&gt;&lt;BR /&gt;**** OpenVMS I64 Operating System V8.2-1   - BUGCHECK ****&lt;BR /&gt;** Bugcheck code = 00000774: CPUSANITY, CPU sanity timer expired&lt;BR /&gt;** Crash CPU: 01    Primary CPU: 00    Active CPUs: 00000003&lt;BR /&gt;** Current Process = NULL&lt;BR /&gt;** Current PSB ID = 00000001&lt;BR /&gt;** Image Name = &lt;BR /&gt;**** Error log buffers not dumped to SYS$ERRLOG.DMP&lt;BR /&gt;**** Canceled memory dump, no dump file available&lt;BR /&gt;&lt;BR /&gt;I do not have to select anything from the menu.  After about 30 seconds I get the bugcheck.&lt;BR /&gt;&lt;BR /&gt;Has anybody else had this problem?  If so what did you do to solve it.&lt;BR /&gt;&lt;BR /&gt;thanks&lt;BR /&gt;   Jim Amend&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Oct 2005 13:57:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652145#M71993</guid>
      <dc:creator>James Amend</dc:creator>
      <dc:date>2005-10-18T13:57:08Z</dc:date>
    </item>
    <item>
      <title>Re: I64 V8.2-1 update DVD gets CPUSANITY Bugcheck</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652146#M71994</link>
      <description>Jim,&lt;BR /&gt;&lt;BR /&gt;  This has been reported to OpenVMS engineering.&lt;BR /&gt;&lt;BR /&gt;  Since CPUSANITY is only possible with multiple CPUs, perhaps if you entered DCL and STOP/CPU 1? (though that probably won't help for an upgrade). Another thing to try is boot conversationally and:&lt;BR /&gt;&lt;BR /&gt;SYSBOOT&amp;gt; SET MULTIPROCESSING 0&lt;BR /&gt;SYSBOOT&amp;gt; CONTINUE&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Oct 2005 18:46:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652146#M71994</guid>
      <dc:creator>John Gillings</dc:creator>
      <dc:date>2005-10-18T18:46:09Z</dc:date>
    </item>
    <item>
      <title>Re: I64 V8.2-1 update DVD gets CPUSANITY Bugcheck</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652147#M71995</link>
      <description>I had that on a rx7620 with V8.2 (which is of course an unsupported config, hence why I didn't progress it with my CSC).&lt;BR /&gt;&lt;BR /&gt;John Gillings' suggestion will however mean you only use one CPU.&lt;BR /&gt;&lt;BR /&gt;What I did and what worked for me (with V8.2, which let me use all of my eight CPU's) was at SYSBOOT add six zeros onto the end of SMP_SANITY_CNT and a zero on the end of SMP_TICK_CNT.&lt;BR /&gt;&lt;BR /&gt;I had no CPUSANITY problems after that.&lt;BR /&gt;&lt;BR /&gt;Of course you will want to progress this, with your CSC for a proper resolution, but that should get you running.</description>
      <pubDate>Wed, 19 Oct 2005 08:06:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652147#M71995</guid>
      <dc:creator>Alex  Daniels</dc:creator>
      <dc:date>2005-10-19T08:06:50Z</dc:date>
    </item>
    <item>
      <title>Re: I64 V8.2-1 update DVD gets CPUSANITY Bugcheck</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652148#M71996</link>
      <description>I was able to get into DCL and stop/cpu 1.  I was able to install V8.2-1.  However, when it rebooted to do autogen, it failed with cpusanity again.  I then went into EFI and disabled 1 cpu and rebooted.  When it did the autogen, it got a machine check.&lt;BR /&gt;&lt;BR /&gt;Attached is the crash output: mancheck.txt.&lt;BR /&gt;&lt;BR /&gt;I tried the multiprocessing = 0, and changing smp* to no avail.  Guenther suggested that I pull my FC controller which is not hooked up anyway because the FGE driver is on the stack.  I am going to do that now.&lt;BR /&gt;&lt;BR /&gt;jim&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Oct 2005 10:34:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652148#M71996</guid>
      <dc:creator>James Amend</dc:creator>
      <dc:date>2005-10-19T10:34:37Z</dc:date>
    </item>
    <item>
      <title>Re: I64 V8.2-1 update DVD gets CPUSANITY Bugcheck</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652149#M71997</link>
      <description>FGEDRIVER is *not* supported on I64, so yes, the card should be pulled.</description>
      <pubDate>Wed, 19 Oct 2005 12:47:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652149#M71997</guid>
      <dc:creator>Robert Brooks_1</dc:creator>
      <dc:date>2005-10-19T12:47:26Z</dc:date>
    </item>
    <item>
      <title>Re: I64 V8.2-1 update DVD gets CPUSANITY Bugcheck</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652150#M71998</link>
      <description>Pulling the FC card took care of the problem.  I am up and running now.  Thanks for all of the input.&lt;BR /&gt;&lt;BR /&gt;jim&lt;BR /&gt;</description>
      <pubDate>Wed, 19 Oct 2005 13:14:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652150#M71998</guid>
      <dc:creator>James Amend</dc:creator>
      <dc:date>2005-10-19T13:14:25Z</dc:date>
    </item>
    <item>
      <title>Re: I64 V8.2-1 update DVD gets CPUSANITY Bugcheck</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652151#M71999</link>
      <description>Jim,&lt;BR /&gt;&lt;BR /&gt;let me try to summarize this:&lt;BR /&gt;&lt;BR /&gt;OpenVMS I64 only supports the A6826A (Dual port fibre channel PCI-X HBA), also called QLogic ISP2312, which is driven by SYS$PGQDRIVER (a port driver to the existing DKDRIVER). The devices are still called FGA0, FGB0 ...&lt;BR /&gt;&lt;BR /&gt;For instructions on how to verify installation of the A6826A FC HBA see:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/A6826-96007/ch02s07.html" target="_blank"&gt;http://docs.hp.com/en/A6826-96007/ch02s07.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If you've seen SYS$FGEDRIVER in one of the registers in the MACHINECHK crash, this seems to indicate, that you were using an unsupported FC HBA.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Thu, 20 Oct 2005 06:43:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/i64-v8-2-1-update-dvd-gets-cpusanity-bugcheck/m-p/3652151#M71999</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-10-20T06:43:51Z</dc:date>
    </item>
  </channel>
</rss>

