<?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: DL140G2 + RHEL4 + SW RAID = system load never 0? in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756739#M68122</link>
    <description>I disagree with you there Alan.  Even with background processes, if the server isn't production, and isn't being tested against (in otherwords, 'Idle'), it should have 0.00/0.00/0.00.&lt;BR /&gt;&lt;BR /&gt;I have production email servers that usually stay lower than 0.35, whilst under constant load!&lt;BR /&gt;&lt;BR /&gt;Anyway.. ;)&lt;BR /&gt;&lt;BR /&gt;Figured out which kernel-config options are causing it?</description>
    <pubDate>Thu, 23 Mar 2006 16:57:42 GMT</pubDate>
    <dc:creator>Stuart Browne</dc:creator>
    <dc:date>2006-03-23T16:57:42Z</dc:date>
    <item>
      <title>DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756733#M68116</link>
      <description>Strange problem dogging me.  I have a DL140G2 system with two 80GB SATA drives and one 2.8GHz Xeon processor.  I've installed RHEL4 on the system using software RAID1 (mirroring).&lt;BR /&gt;&lt;BR /&gt;I'm booting with ide0=noprobe ide1=noprobe in order to make use of the ata_piix driver (otherwise PATA mode is used).&lt;BR /&gt;&lt;BR /&gt;There is currently _nothing_ running on this system and the weird thing is, the system load never reaches 0.00!  It's almost always around 0.10 or 0.22 and for the life of me I cannot figure out what is bumping the load up.&lt;BR /&gt;&lt;BR /&gt;Now, maybe this is not something to be concerned about, but on my DL140G1 systems I have never encountered this.  Of course these were systems using old ATA drives, but the idle load on 'em was always 0.00.&lt;BR /&gt;&lt;BR /&gt;On the new G2 boxes, while I am using the system, there is also occasional IO pauses where I'll enter in a simple command like 'uptime' and the system pauses to think for a good 5 seconds then spits back the answer.&lt;BR /&gt;&lt;BR /&gt;It all adds up to me worrying that this issue will mangify itself once the machine is in production.&lt;BR /&gt;&lt;BR /&gt;Things I have tried:&lt;BR /&gt;&lt;BR /&gt;- Booting in non-SMP mode (HT on in BIOS)&lt;BR /&gt;- Booting in SMP mode with noapic (HT on in BIOS)&lt;BR /&gt;- Booting in non-SMP mode (HT off in BIOS)&lt;BR /&gt;- Booting in SMP mode (HT off in BIOS)&lt;BR /&gt;&lt;BR /&gt;Nothing has fixed the issue.&lt;BR /&gt;&lt;BR /&gt;I've also disabled USB on the system as it appeared to be on the same IRQ as eth0.  I am using the HP bcm5700 drivers and this is with the stock RHEL 2.6.9-34 kernel.&lt;BR /&gt;&lt;BR /&gt;Any suggestions?  Should I build my own kernel and disable APIC/HT support there?&lt;BR /&gt;&lt;BR /&gt;Also wondering if perhaps the combo of SW RAID and the SATA drivers are causing the issue, but I don't know how to track this down.</description>
      <pubDate>Wed, 22 Mar 2006 12:20:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756733#M68116</guid>
      <dc:creator>Ray Van Dolson</dc:creator>
      <dc:date>2006-03-22T12:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756734#M68117</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;SATA could be conributing to the issue, but there really isn't an issue.&lt;BR /&gt;&lt;BR /&gt; I've installed RHEL4 on the system using software RAID1 (mirroring).&lt;BR /&gt;&lt;BR /&gt;If there is any activity on the system, even log entries going on, there is going to be work to keep the software mirror updated..&lt;BR /&gt;&lt;BR /&gt;You should consider using hardware raid instead, it takes the activity off the CPU leaving it free for more meaningful work.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 22 Mar 2006 13:31:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756734#M68117</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-03-22T13:31:34Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756735#M68118</link>
      <description>Thanks for the reply... I've had great experience with Linux software RAID before (no symptoms like this) on ProLiant hardware.  That's the only reason I'm puzzled by what's going on.&lt;BR /&gt;&lt;BR /&gt;In any case, I'm not going to worry about it too much.  Will see how it behaves once it's out in production.</description>
      <pubDate>Wed, 22 Mar 2006 14:42:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756735#M68118</guid>
      <dc:creator>Ray Van Dolson</dc:creator>
      <dc:date>2006-03-22T14:42:48Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756736#M68119</link>
      <description>Well, I've built a custom kernel using the latest 2.6.16 sources and no longer am having any of the symptoms I was with the Red Hat kernel.&lt;BR /&gt;&lt;BR /&gt;If I switch back however, the symptoms return.&lt;BR /&gt;&lt;BR /&gt;Guess I'll try using my .config from the .16 kernel on the RH kernel and see if that does the trick.</description>
      <pubDate>Thu, 23 Mar 2006 00:37:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756736#M68119</guid>
      <dc:creator>Ray Van Dolson</dc:creator>
      <dc:date>2006-03-23T00:37:46Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756737#M68120</link>
      <description>i wouldn't expect the system load to ever be "0".  Start "top" or "ps -ef" and you'll see lots of stuff running in the background.</description>
      <pubDate>Thu, 23 Mar 2006 11:27:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756737#M68120</guid>
      <dc:creator>Alan_152</dc:creator>
      <dc:date>2006-03-23T11:27:53Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756738#M68121</link>
      <description>This is a completely empty system right now.  Yes there are processes running, but I have plenty of other servers that are either sitting unused or only doing simple things like DNS resolution and their load is _always_ right around 0.00, 0.01.&lt;BR /&gt;&lt;BR /&gt;There is no way this server should be sitting at 0.25-0.30 load when it's running nothing but sshd and the normal OS processes all night.&lt;BR /&gt;&lt;BR /&gt;[rayvd@backup rayvd]$ uptime&lt;BR /&gt; 08:32:43  up 51 days, 20:46,  3 users,  load average: 0.00, 0.00, 0.00&lt;BR /&gt;&lt;BR /&gt;This server has a "slower" processor than mY DL140 but is idle most of the day just as my new server is.</description>
      <pubDate>Thu, 23 Mar 2006 11:34:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756738#M68121</guid>
      <dc:creator>Ray Van Dolson</dc:creator>
      <dc:date>2006-03-23T11:34:32Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756739#M68122</link>
      <description>I disagree with you there Alan.  Even with background processes, if the server isn't production, and isn't being tested against (in otherwords, 'Idle'), it should have 0.00/0.00/0.00.&lt;BR /&gt;&lt;BR /&gt;I have production email servers that usually stay lower than 0.35, whilst under constant load!&lt;BR /&gt;&lt;BR /&gt;Anyway.. ;)&lt;BR /&gt;&lt;BR /&gt;Figured out which kernel-config options are causing it?</description>
      <pubDate>Thu, 23 Mar 2006 16:57:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756739#M68122</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2006-03-23T16:57:42Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756740#M68123</link>
      <description>Well, I didn't mean to start a fight.  &lt;BR /&gt;&lt;BR /&gt;Anyway, I've just installed a max rhel4u3 config on a max-configured rx2620.  I'm accessing it through the MP, so it is as hands-off and no load as I can make it without actually turning stuff off.&lt;BR /&gt;&lt;BR /&gt;In multiuser mode, here's what I've got:&lt;BR /&gt;&lt;BR /&gt;[root@max ~]# uptime&lt;BR /&gt; 17:18:37 up 1 min,  1 user,  load average: 0.49, 0.23, 0.09&lt;BR /&gt;&lt;BR /&gt;top - 17:18:51 up 2 min,  1 user,  load average: 0.38, 0.22, 0.08&lt;BR /&gt;Tasks:  77 total,   1 running,  76 sleeping,   0 stopped,   0 zombie&lt;BR /&gt;Cpu(s):  0.0% us,  0.0% sy,  0.0% ni, 100.0% id,  0.0% wa,  0.0% hi,  0.0% s&lt;BR /&gt;Mem:  16641696k total,   417760k used, 16223936k free,    25152k buffers&lt;BR /&gt;Swap:  2031584k total,        0k used,  2031584k free,   102816k cached&lt;BR /&gt;&lt;BR /&gt;  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND&lt;BR /&gt; 3430 root      16   0  4192 2368 1840 R  0.1  0.0   0:00.01 top&lt;BR /&gt;    1 root      16   0  3440 1536 1232 S  0.0  0.0   0:02.62 init&lt;BR /&gt;    2 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/0&lt;BR /&gt;    3 root      34  19     0    0    0 S  0.0  0.0   0:00.00 ksoftirqd/0&lt;BR /&gt;    4 root      RT   0     0    0    0 S  0.0  0.0   0:00.00 migration/1&lt;BR /&gt;    5 root      34  19     0    0    0 S  0.0  0.0   0:00.00 ksoftirqd/1&lt;BR /&gt;&lt;BR /&gt;[root@max ~]# ps -eo "%C %c"&lt;BR /&gt;%CPU COMMAND&lt;BR /&gt; 0.4 init&lt;BR /&gt; 0.0 migration/0&lt;BR /&gt; 0.0 ksoftirqd/0&lt;BR /&gt; 0.0 migration/1&lt;BR /&gt; 0.0 ksoftirqd/1&lt;BR /&gt; 0.0 migration/2&lt;BR /&gt; 0.0 ksoftirqd/2&lt;BR /&gt; 0.0 migration/3&lt;BR /&gt; 0.0 ksoftirqd/3&lt;BR /&gt; 0.0 events/0&lt;BR /&gt; 0.0 events/1&lt;BR /&gt; 0.0 events/2&lt;BR /&gt; 0.0 events/3&lt;BR /&gt; 0.0 khelper&lt;BR /&gt; 0.0 kacpid&lt;BR /&gt; 0.0 kblockd/0&lt;BR /&gt; 0.0 kblockd/1&lt;BR /&gt; 0.0 kblockd/2&lt;BR /&gt; 0.0 kblockd/3&lt;BR /&gt; 0.0 khubd&lt;BR /&gt; 0.0 pdflush&lt;BR /&gt; 0.0 pdflush&lt;BR /&gt; 0.0 aio/0&lt;BR /&gt; 0.0 kswapd0&lt;BR /&gt; 0.0 aio/1&lt;BR /&gt; 0.0 aio/2&lt;BR /&gt; 0.0 aio/3&lt;BR /&gt; 0.0 kseriod&lt;BR /&gt; 0.0 scsi_eh_0&lt;BR /&gt; 0.0 qla2400_0_dpc&lt;BR /&gt; 0.0 scsi_eh_1&lt;BR /&gt; 0.0 qla2400_1_dpc&lt;BR /&gt; 0.0 scsi_eh_2&lt;BR /&gt; 0.0 scsi_eh_3&lt;BR /&gt; 0.0 kmirrord&lt;BR /&gt; 0.0 kmir_mon&lt;BR /&gt; 0.0 kjournald&lt;BR /&gt; 0.0 udevd&lt;BR /&gt; 0.0 kauditd&lt;BR /&gt; 0.0 kmpathd/0&lt;BR /&gt; 0.0 kmpathd/1&lt;BR /&gt; 0.0 kmpathd/2&lt;BR /&gt; 0.0 kmpathd/3&lt;BR /&gt; 0.0 dhclient&lt;BR /&gt; 0.0 syslogd&lt;BR /&gt; 0.0 klogd&lt;BR /&gt; 0.0 portmap&lt;BR /&gt; 0.0 rpc.statd&lt;BR /&gt; 0.0 rpc.idmapd&lt;BR /&gt; 0.0 smartd&lt;BR /&gt; 0.0 acpid&lt;BR /&gt; 0.0 cupsd&lt;BR /&gt; 0.0 sshd&lt;BR /&gt; 0.0 xinetd&lt;BR /&gt; 0.0 sendmail&lt;BR /&gt; 0.0 sendmail&lt;BR /&gt; 0.0 gpm&lt;BR /&gt; 0.0 htt&lt;BR /&gt; 0.0 htt_server&lt;BR /&gt; 0.2 cannaserver&lt;BR /&gt; 0.0 crond&lt;BR /&gt; 0.0 xfs&lt;BR /&gt; 0.0 anacron&lt;BR /&gt; 0.0 atd&lt;BR /&gt; 0.0 salinfod&lt;BR /&gt; 0.0 dbus-daemon-1&lt;BR /&gt; 0.0 cups-config-dae&lt;BR /&gt; 0.0 hald&lt;BR /&gt; 0.0 login&lt;BR /&gt; 0.0 mingetty&lt;BR /&gt; 0.0 mingetty&lt;BR /&gt; 0.0 mingetty&lt;BR /&gt; 0.0 mingetty&lt;BR /&gt; 0.0 mingetty&lt;BR /&gt; 0.0 mingetty&lt;BR /&gt; 0.0 bash&lt;BR /&gt; 0.0 ps&lt;BR /&gt;&lt;BR /&gt;If I wanted to improve my load factors, there's a bunch of stuff I could shut down there.  I suspect it is the same for the OP.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 23 Mar 2006 17:29:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756740#M68123</guid>
      <dc:creator>Alan_152</dc:creator>
      <dc:date>2006-03-23T17:29:08Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756741#M68124</link>
      <description>Interesting.  Well, I'd think that even with that many programs running, as long as nothing is running _intensively_ you should still see around 0.00 or 0.02, etc -- meaning no processes are having to wait to get CPU time.&lt;BR /&gt;&lt;BR /&gt;In any case, it seems that disabling APIC in the kernel and also disabling SMP support (I have a uniprocessor system anyways).&lt;BR /&gt;&lt;BR /&gt;The only side effect of this is that /proc/interrupts shows ERR: incrementing a _lot_, but the system load numbers are more what I'd expect and the IO "pauses" are much less frequent.&lt;BR /&gt;&lt;BR /&gt;I'll probably try this on a system without software RAID and see if the md driver is to blame or if it's ata_piix.</description>
      <pubDate>Thu, 23 Mar 2006 17:38:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756741#M68124</guid>
      <dc:creator>Ray Van Dolson</dc:creator>
      <dc:date>2006-03-23T17:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756742#M68125</link>
      <description>Kernel change fixed it. Interesting.&lt;BR /&gt;&lt;BR /&gt;Part of the standard proliant install process involves a kernel change if you have a fiber connection.&lt;BR /&gt;&lt;BR /&gt;If you'd care to share the customizations and changes, it would make this a valuable historical thread.&lt;BR /&gt;&lt;BR /&gt;You have relatively few posts so I'll ask you to assign points to responses based on usefulness. If you found my advice useless, please take the time for posting me zero points.&lt;BR /&gt;&lt;BR /&gt;TY&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 23 Mar 2006 18:00:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756742#M68125</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-03-23T18:00:49Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756743#M68126</link>
      <description>I'll probably do some more testing this evening but will definitely put together a summary of my changes -- or at least the kernel config I am using.&lt;BR /&gt;&lt;BR /&gt;I still want to test if these changes have the same effect on my stock Red Hat kernel if I rebuild it.&lt;BR /&gt;&lt;BR /&gt;And yeah, sorry I need to remember to use the points system on here :-)</description>
      <pubDate>Thu, 23 Mar 2006 18:06:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756743#M68126</guid>
      <dc:creator>Ray Van Dolson</dc:creator>
      <dc:date>2006-03-23T18:06:26Z</dc:date>
    </item>
    <item>
      <title>Re: DL140G2 + RHEL4 + SW RAID = system load never 0?</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756744#M68127</link>
      <description>Well, just a follow-up.  The issue actually hasn't completely gone away -- even with 2.6.16 like I thought it had.&lt;BR /&gt;&lt;BR /&gt;There seem to be an excessively high number of interrupts (1000/sec to the IO-APIC timer vs 100/sec on a production DL140G1).&lt;BR /&gt;&lt;BR /&gt;I've posted about this on the Red Hat mailing list:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://www.redhat.com/archives/redhat-list/2006-April/msg00112.html" target="_blank"&gt;https://www.redhat.com/archives/redhat-list/2006-April/msg00112.html&lt;/A&gt;</description>
      <pubDate>Fri, 07 Apr 2006 12:18:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl140g2-rhel4-sw-raid-system-load-never-0/m-p/3756744#M68127</guid>
      <dc:creator>Ray Van Dolson</dc:creator>
      <dc:date>2006-04-07T12:18:35Z</dc:date>
    </item>
  </channel>
</rss>

