<?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: Server hangs with VBDA error in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/server-hangs-with-vbda-error/m-p/4696303#M61069</link>
    <description>:Bump:&lt;BR /&gt;&lt;BR /&gt;Can anybody help me please.</description>
    <pubDate>Thu, 07 Oct 2010 09:49:19 GMT</pubDate>
    <dc:creator>Kesava</dc:creator>
    <dc:date>2010-10-07T09:49:19Z</dc:date>
    <item>
      <title>Server hangs with VBDA error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/server-hangs-with-vbda-error/m-p/4696302#M61068</link>
      <description>&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Hello all,&lt;BR /&gt;&lt;BR /&gt;We have a server with below details.&lt;BR /&gt;Hardware: DL385 G2/DC AMD OPTERON 2218 2GB &lt;BR /&gt;OS:  RHEL 5.5 (64B)&lt;BR /&gt;HP insight: hpsmh 3.0.2-77 hp-snmp-agents 8.3.0.27-25&lt;BR /&gt;&lt;BR /&gt;I dont know if this is a hardware or software error. Is it related to ASR?&lt;BR /&gt;&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel: INFO: task vbda:26672 blocked for more than 120 seconds.&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel: "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel: vbda          D ffff81000237eaa0     0 26672   2965 26675               (NOTLB)&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  ffff81000a8b1bf8 0000000000000082 0000000000000086 ffffffff8003da83&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  0000000000000000 0000000000000007 ffff8100571940c0 ffff8101026af860&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  00006c6cd7eb54a0 0000000000039934 ffff8100571942a8 000000027f8306b0&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel: Call Trace:&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8003DA83&gt;] lock_timer_base+0x1b/0x3c&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8006E1DB&gt;] do_gettimeofday+0x40/0x90&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8001552B&gt;] sync_buffer+0x0/0x3f&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF800637EA&gt;] io_schedule+0x3f/0x67&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF80015566&gt;] sync_buffer+0x3b/0x3f&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF80063A16&gt;] __wait_on_bit+0x40/0x6e&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8001552B&gt;] sync_buffer+0x0/0x3f&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF80063AB0&gt;] out_of_line_wait_on_bit+0x6c/0x78&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF800A0A06&gt;] wake_bit_function+0x0/0x23&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF80017549&gt;] ll_rw_block+0x8c/0xab&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8804FC57&gt;] :ext3:ext3_bread+0x54/0x76&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF88053579&gt;] :ext3:htree_dirblock_to_tree+0x33/0x13e&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF88053700&gt;] :ext3:ext3_htree_fill_tree+0x7c/0x1cb&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8012AB42&gt;] inode_has_perm+0x56/0x63&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8002588D&gt;] filldir+0x0/0xb7&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8804BE31&gt;] :ext3:ext3_readdir+0x1a5/0x514&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8002588D&gt;] filldir+0x0/0xb7&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8002588D&gt;] filldir+0x0/0xb7&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8003522D&gt;] vfs_readdir+0x77/0xa9&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF80038AE2&gt;] sys_getdents+0x75/0xbd&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8005D229&gt;] tracesys+0x71/0xe0&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:  [&lt;FFFFFFFF8005D28D&gt;] tracesys+0xd5/0xe0&lt;BR /&gt;Oct  6 19:14:08 Server_name kernel:&lt;BR /&gt;&lt;BR /&gt;Any help would be highly appreciated. &lt;BR /&gt;&lt;BR /&gt;Kesava&lt;/FFFFFFFF8005D28D&gt;&lt;/FFFFFFFF8005D229&gt;&lt;/FFFFFFFF80038AE2&gt;&lt;/FFFFFFFF8003522D&gt;&lt;/FFFFFFFF8002588D&gt;&lt;/FFFFFFFF8002588D&gt;&lt;/FFFFFFFF8804BE31&gt;&lt;/FFFFFFFF8002588D&gt;&lt;/FFFFFFFF8012AB42&gt;&lt;/FFFFFFFF88053700&gt;&lt;/FFFFFFFF88053579&gt;&lt;/FFFFFFFF8804FC57&gt;&lt;/FFFFFFFF80017549&gt;&lt;/FFFFFFFF800A0A06&gt;&lt;/FFFFFFFF80063AB0&gt;&lt;/FFFFFFFF8001552B&gt;&lt;/FFFFFFFF80063A16&gt;&lt;/FFFFFFFF80015566&gt;&lt;/FFFFFFFF800637EA&gt;&lt;/FFFFFFFF8001552B&gt;&lt;/FFFFFFFF8006E1DB&gt;&lt;/FFFFFFFF8003DA83&gt;</description>
      <pubDate>Thu, 07 Oct 2010 06:00:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/server-hangs-with-vbda-error/m-p/4696302#M61068</guid>
      <dc:creator>Kesava</dc:creator>
      <dc:date>2010-10-07T06:00:46Z</dc:date>
    </item>
    <item>
      <title>Re: Server hangs with VBDA error</title>
      <link>https://community.hpe.com/t5/operating-system-linux/server-hangs-with-vbda-error/m-p/4696303#M61069</link>
      <description>:Bump:&lt;BR /&gt;&lt;BR /&gt;Can anybody help me please.</description>
      <pubDate>Thu, 07 Oct 2010 09:49:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/server-hangs-with-vbda-error/m-p/4696303#M61069</guid>
      <dc:creator>Kesava</dc:creator>
      <dc:date>2010-10-07T09:49:19Z</dc:date>
    </item>
  </channel>
</rss>

