<?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 dmesg error: Failing bind request to disabled processor 2. in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-error-failing-bind-request-to-disabled-processor-2/m-p/3543366#M223682</link>
    <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;I was getting file table full error for that i had modified the kernel parameter nfile to 50% more. After the reboot i am getting the below error message in dmesg.&lt;BR /&gt;Please let me know why this occured. Is this related to the change in kernel parameter or some thing else?&lt;BR /&gt;&lt;BR /&gt;It is a superdome partition and 2 CPU are being used for this partition.&lt;BR /&gt;mpc_kernel_bind (2): Failing bind request to disabled processor 2.&lt;BR /&gt;mpc_kernel_bind (2): for pid 1624 tid 1890 (sdci)&lt;BR /&gt;mpc_kernel_bind (2): Failing bind request to disabled processor 2.&lt;BR /&gt;mpc_kernel_bind (2): for pid 1624 tid 1890 (sdci)&lt;BR /&gt;mpc_kernel_bind (2): Failing bind request to disabled processor 2.&lt;BR /&gt;mpc_kernel_bind (2): for pid 1624 tid 1890 (sdci)&lt;BR /&gt;</description>
    <pubDate>Thu, 12 May 2005 10:15:03 GMT</pubDate>
    <dc:creator>Jagadesh_2</dc:creator>
    <dc:date>2005-05-12T10:15:03Z</dc:date>
    <item>
      <title>dmesg error: Failing bind request to disabled processor 2.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-error-failing-bind-request-to-disabled-processor-2/m-p/3543366#M223682</link>
      <description>Dear All,&lt;BR /&gt;&lt;BR /&gt;I was getting file table full error for that i had modified the kernel parameter nfile to 50% more. After the reboot i am getting the below error message in dmesg.&lt;BR /&gt;Please let me know why this occured. Is this related to the change in kernel parameter or some thing else?&lt;BR /&gt;&lt;BR /&gt;It is a superdome partition and 2 CPU are being used for this partition.&lt;BR /&gt;mpc_kernel_bind (2): Failing bind request to disabled processor 2.&lt;BR /&gt;mpc_kernel_bind (2): for pid 1624 tid 1890 (sdci)&lt;BR /&gt;mpc_kernel_bind (2): Failing bind request to disabled processor 2.&lt;BR /&gt;mpc_kernel_bind (2): for pid 1624 tid 1890 (sdci)&lt;BR /&gt;mpc_kernel_bind (2): Failing bind request to disabled processor 2.&lt;BR /&gt;mpc_kernel_bind (2): for pid 1624 tid 1890 (sdci)&lt;BR /&gt;</description>
      <pubDate>Thu, 12 May 2005 10:15:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-error-failing-bind-request-to-disabled-processor-2/m-p/3543366#M223682</guid>
      <dc:creator>Jagadesh_2</dc:creator>
      <dc:date>2005-05-12T10:15:03Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg error: Failing bind request to disabled processor 2.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-error-failing-bind-request-to-disabled-processor-2/m-p/3543367#M223683</link>
      <description>Jagadesh,&lt;BR /&gt;&lt;BR /&gt;I think may be processor 2 is in differed state . ie processor disabled .&lt;BR /&gt;&lt;BR /&gt;Check Chasis logs in GSP.&lt;BR /&gt;&lt;BR /&gt;Better log a support call with HP.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;BR /&gt;BL</description>
      <pubDate>Thu, 12 May 2005 14:05:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-error-failing-bind-request-to-disabled-processor-2/m-p/3543367#M223683</guid>
      <dc:creator>baiju_3</dc:creator>
      <dc:date>2005-05-12T14:05:38Z</dc:date>
    </item>
    <item>
      <title>Re: dmesg error: Failing bind request to disabled processor 2.</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-error-failing-bind-request-to-disabled-processor-2/m-p/3543368#M223684</link>
      <description>For 11.11, this message was a known issue fixed originally in PHKL_24578 and PHKL_26405.&lt;BR /&gt;&lt;BR /&gt;It probably has nothing to do with the nfile change, but everything to do with the reboot.&lt;BR /&gt;&lt;BR /&gt;One of two things happened on this reboot.&lt;BR /&gt;&lt;BR /&gt;a) Either, processor 2 failed self test and is now disabled.&lt;BR /&gt;&lt;BR /&gt;b) Prior to the boot someone set up a process to be bound to CPU 2 without knowing that CPU 2 was not available on this machine.&lt;BR /&gt;&lt;BR /&gt;If you don't think that you should have a processor disabled on this machine, then you may need to run diagnostics or look at the top of syslog.log to see how many CPUs you are running on after the boot versus how many you expect to be running on.&lt;BR /&gt;&lt;BR /&gt;Best regards,&lt;BR /&gt;&lt;BR /&gt;Kent M. Ostby&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 12 May 2005 14:59:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/dmesg-error-failing-bind-request-to-disabled-processor-2/m-p/3543368#M223684</guid>
      <dc:creator>Kent Ostby</dc:creator>
      <dc:date>2005-05-12T14:59:18Z</dc:date>
    </item>
  </channel>
</rss>

