BTW, Dell also tried to sell us the "kool-aid" that is doesn't effect
anything - we are seeing the effect (slow response, hesitation, longer
run-times) on all of our machines in this class, that we haven't tweaked
the BIOS settings to "non-latency".  Made a world of difference on my new
TSM server.


On Fri, Jun 21, 2013 at 5:11 PM, Skylar Thompson
<skylar2 AT u.washington DOT edu>wrote:

> We're seeing the same thing on some Dell m620s and r620s. It doesn't
> appear to impact our performance though, it's just log spam for us.
>
> -- Skylar Thompson (skylar2 AT u.washington DOT edu)
> -- Genome Sciences Department, System Administrator
> -- Foege Building S046, (206)-685-7354
> -- University of Washington School of Medicine
>
> On 06/21/13 11:05, Zoltan Forray wrote:
> > This is a little OT but wondering if someone could help/offer some
> > suggestions
> >
> > I was part of the way through my 5.5 -> 6.3.4 upgrade/conversion when I
> > noticed the EXTRACTDB seemed to stop in its tracks.  I am doing this on
> my
> > new server, listed above, using the latest RedHat V6 linux
> >
> > Since I tested this process on a low-power "test TSM server", I wandered
> > what was going on.
> >
> > Digging in the /var/log/messages file, I noticed these strange messages
> > that all started around the time the EXTRACTDB seemed to suddenly stop
> > (previous testing produced a 40GB extract file - this stopped at 23GB and
> > the last file update was at the time these messages were issued).
> >
> > Jun 21 12:54:44 hades kernel: CPU8: Package power limit normal
> > Jun 21 12:54:44 hades kernel: CPU10: Package power limit normal
> > Jun 21 12:54:44 hades kernel: CPU26: Package power limit normal
> > Jun 21 12:54:44 hades kernel: CPU12: Package power limit normal
> > Jun 21 12:54:44 hades kernel: CPU28: Package power limit normal
> > Jun 21 12:54:44 hades kernel: CPU14: Package power limit normal
> > Jun 21 12:54:44 hades kernel: CPU30: Package power limit normal
> >
> > My OS guys say they have been seeing these on other Dell servers in this
> > same class.  It has something to do with the (this is from Dell) hardware
> > sensing a load (seriously?   just doing an extractdb?  What happens when
> > DB2 starts running full-throttle?) and talking to the Linux kernel
> telling
> > it to throttle things down.  It seems the extractDB process didn't like
> > this and never resumed its work.
> >
> > So far Dell support can only offer "suggested BIOS changes" to see if
> might
> > help!
> >
> > Anyone else have these boxes and seen anything like this?  Any thoughts?
> >
> > --
> > *Zoltan Forray*
> > TSM Software & Hardware Administrator
> > Virginia Commonwealth University
> > UCC/Office of Technology Services
> > zforray AT vcu DOT edu - 804-828-4807
> > Don't be a phishing victim - VCU and other reputable organizations will
> > never use email to request that you reply with your password, social
> > security number or confidential personal information. For more details
> > visit http://infosecurity.vcu.edu/phishing.html
> >
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html