Failure to Sleep... HEAT build up...

I all,
I have a week 40 macbook 1.83GHz machine. This afternoon I put it to sleep (closed the lid) with a fully charged battery. Upon return from my son's Karate class the book was not sleeping, FANS WERE ROARING, heat was incredible (really really hot!!!... hotter then an MDD without a heat sink), battery was delpleted to 1.5hours (normally holds 4.5 or so). It appears that it failed to go to sleep and remained active with the lid closed (lid was fully closed and "latched"). I have not been able to reproduce this effect.
Is this a common issue with the MBs?
Is this a sign of an ill SMC (PMU)?
Is there a switch in the hinge armature or is it a super magnet like in the old PowerBook G3 Series that is failing?
Thoughts?
(The book is less then two weeks old... is this a sign of bigger issues? ).

Hi Adam,
I also had to force it to shut down and... upon reboot had the "unexpected" quit message.
So far my book has not repeated this misadventure (failure to sleep follwed by running with the lid closed and then EXCESSIVE heat and really loud fan spin). I hope it will not do so as it was terrbily alarming. It was scortching hot.
I will watch it for a bit and if it repeats it is going in for service or at least a checkup. I have owned mac laptops for years (150, 165c, PB1400, Wallstreet, Lombard and Pismo... iBook1.33 and now this mac book)... I have never had this happen before with any other book in over 12 yearrs of Mac Laptop useage. I hope it is a "one of" event. I miss my iBook1.33. it was about as fast as this macbook for day to day lite use and it never misbehaved.
Dave.

Similar Messages

MBP: Failure to sleep, leads to forced hard boot and sometimes overheating

I am new to the Mac world, but it appears as though these are both common issues. I am thinking that my problem is more about failure to sleep properly than the overheating (it wouldn't overheat if it were asleep properly!).
Situation:
1. I have a bunch or a few programs running.
2. I close the lid.
3. It looks like the display shuts down.
4. I put the machine in my bag, which has a furry inside to prevent scratches.
5. I live my life for a while.
6. Later, I find that my MBP is burning up, opening the lid doesn't get the machine to "wake up", the batteries have been drained, and I need to hard reboot to get the machine back.
Anyway, I have read on some groups that the failure to properly sleep is a hardware problem, others opt for an OS upgrade, and one promising lead that suggested I pull the power before closing the lid.
It seems that several of the conversations I've read are old, and my MBP is only 2 months old, so I think I have the latest OS builds. Pulling the power cord seems to not matter. This leaves me with the possibility of a hardware issue... My best guess is that my machine a) can't figure out if it is plugged in or not; b) can't figure out if it is asleep or awake; or c) restarts, even with the lid closed, and without displaying the display.
I suspect that when it gets running again, it heats up, burns the battery down to zero, and forces the OS to crash when the batteries run dry or nearly so.
So, I thought I'd post my dilemma here, and maybe someone who is "current" on this issue on MBP's could suggest a good course of action. I have AppleCare, so it is certainly an option to get the hardware replaced, however, is that going to actually help?
Is this as common a problem as it seems like to me (100% of my Apple MBPs have this issue, even though my sample size is small at 1)?
Are 10% of MBPs afflicted like this or more like 90%?
Will Apple take care of me or will it be a battle?
I really appreciate anyone who can help me out with suggestions on what course of action to take next.
Kevin

Eve, I think you are having the same problem I had. Basically, sleep seems to not be very resilient, and in my case I think it was partially because the machine kept running and then entered a semi-failure state when the battery finally drained out. I think the machine just can't handle running out of power, which is somewhat reasonable. I'd like to see Apple make the machine recognize that it is sleeping, and running out of power, and then automatically deep sleep itself to protect your session...
You can test to see if we had the same problem by doing this when the machine "won't wake back up":
- make sure the power cable is in
- depress the power button for a long time, like 10 seconds to force a hard reboot (it seems weird, because the machine looks like it is off already)
- you may "feel" the machine shut down (I don't know how else to describe it, but you can "tell" that it shut down).
- release the power button
- then, press the power again, as if to turn on
- I think you will find that your MBP has now started back up
So, if you see this problem when your MBP has been sleeping for a while, I think you have the same problem I did. Now, if you deep sleep it (using the widget referred to above) every time you put it away, and wake it up with the power button, I think you will have very few problems.
The only problems I've had since starting this process was that a couple of times, the MBP didn't realize it was quite awake and feel back into deep sleep. This wasn't so bad as you just had to hit the power button to wake it up again. I'm also not 100% sure that there wasn't user error (me!) that caused that problem...
Anyway, give this widget a try and see if your problem goes away. I think you will find that it does.

Week 25 Whine, Heat, Build Issues Finally Fixed!

I received a week 25 MBP yesterday and I can say that Apple has finally got it right.
I have had numerous problems with previous machines ranging from bad video cards, dropped wifi connections, broken latches and the infamous heat and whine problems.
This new machine is absolutely perfect. Here are my observations:
- Absolutely no whine under battery or while plugged in (even when the machine is idle)
- Heat does not exceed 42c on normal tasks and the machine idles at 37c-40c.
- The case is barley warm to the touch.
- Wifi range and performance is excellent.
- No cosmetic build issues such as warped lid or broken latch.
I wholehartedly recommdend people who have been waiting to go ahead and make your purchases.

it appears apple has fianlly figured out new power cicutry for the mobo to cpu that no longer whines. there's an article about a macintouch editor (or writer i forget, he works for them) who just got it back with a letter, and no longer has any whine, at all.
I'm going to talk to my apple place this week adn see if i can get htem to replace it again, its clearly a whine on my new logic board, so i don't see why they wouldnt - i'll jsut tell them ti is loud as they know, just hopw they wont say something like 'no, we already did it'.
anyway, good luck everyone ill wait a week ro so to try to help get the very newest rev of mobo
edit: forgot the link! http://macdailynews.com/index.php/weblog/comments/10076/

10.4.9 - Delays in Terminal, Wake From Sleep, XCode Build

Hi,
Since I've updated my Intel iMac to 10.4.9 I'm experiencing some delays in certain actions. The most bothersome being in Terminal. Every time I open a new session (window/shell) I get the spinning beach ball for about 10 seconds before the new window appears. I also get the same delay when building in Xcode and getting the login prompt after waking from sleep.
Looking at the activity monitor, it doesn't look like there is a spike in CPU usage. Any ideas?
Thanks.
Intel iMac Mac OS X (10.4.6)

Nothing interesting as far as I can tell. I checked system.log and windowserver.log as well as console.log. I watched the console as I opened terminal and nothing was written before, during or after the delay.
If I open terminal, wait through the delay, then quit terminal and open it right away, it sometimes it opens a terminal window without delay. It also sometimes opens a new terminal window right away and displays the line "Last login: Fri Mar 23 13:20:52 on ttyp1", but then I have to wait a good 5-10 seconds for the "Welcome to Darwin!" message and the prompt.
Weird...

Failure of Background Ant Build

Hi
I'm implementing the CreditFlow example from the quick start tutorial.
I've got an error during the deployment.
Error during parsing of the deployment-descriptor: build.xml. reason:"unknown protocol:c"
Check the deployment descriptor.
<?xml version="1.0"?>
<BPELSuitcase>
     <BPELProcess id="CreditFlow" src="CreditFlow.bpel">
          <partnerLinkBindings>
               <partnerLinkBinding name="client">
                    <property name="wsdlLocation">CreditFlow.wsdl</property>
               </partnerLinkBinding>
               <partnerLinkBinding name="creditRatingService">
                    <property name="wsdlLocation">http://localhost:9700/orabpel/default/CreditRatingService/1.0/CreditRatingService?wsdl</property>
               </partnerLinkBinding>
          </partnerLinkBindings>
     </BPELProcess>
</BPELSuitcase>
Thanks for your help

HI,
can you elaborate how you invoke the compiliation..
using obant.bat/sh? or using eclipse to build and compile?
thx clemens

Build failure when trying to build haproxy with SSL support.

Hello everybody,
I don't know if this is the right "context" to submit this question.
How ever I'm having problem with building haproxy 1.5.5 with SSL support.
I'm running SLES 11 SP3 with the latest updates via YAST2.
Building without SSL support works fine.
I use the syntax:
make TARGET=linux2628 USE_OPENSSL=1
And here is the output:
gcc -Iinclude -Iebtree -Wall -O2 -g -fno-strict-aliasing -DCONFIG_HAP_LINUX_SPLICE -DTPROXY -DCONFIG_HAP_LINUX_TPROXY -DCONFIG_HAP_CRYPT -DENABLE_POLL -DENABLE_EPOLL -DUSE_CPU_AFFINITY -DASSUME_SPLICE_WORKS -DUSE_ACCEPT4 -DNETFILTER -DUSE_GETSOCKNAME -DUSE_OPENSSL -DUSE_SYSCALL_FUTEX -DCONFIG_HAPROXY_VERSION=\"1.5.5\" -DCONFIG_HAPROXY_DATE=\"2014/10/07\" \
-DBUILD_TARGET='"linux2628"' \
-DBUILD_ARCH='""' \
-DBUILD_CPU='"generic"' \
-DBUILD_CC='"gcc"' \
-DBUILD_CFLAGS='"-O2 -g -fno-strict-aliasing"' \
-DBUILD_OPTIONS='"USE_OPENSSL=1"' \
-c -o src/haproxy.o src/haproxy.c
In file included from include/types/acl.h:33,
from include/types/proxy.h:40,
from include/proto/log.h:32,
from includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
from src/haproxy.c:61:
include/types/server.h:29:25: error: openssl/ssl.h: No such file or directory
In file included from include/types/connection.h:30,
from include/types/server.h:36,
from include/types/acl.h:33,
from include/types/proxy.h:40,
from include/proto/log.h:32,
from includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
from src/haproxy.c:61:
include/types/listener.h:127: error: expected specifier-qualifier-list before SSL_CTX
In file included from include/types/acl.h:33,
from include/types/proxy.h:40,
from include/proto/log.h:32,
from includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
from src/haproxy.c:61:
include/types/server.h:207: error: expected specifier-qualifier-list before SSL_CTX
In file included from src/haproxy.c:90:
include/proto/listener.h: In function bind_conf_alloc:
include/proto/listener.h:130: error: struct bind_conf has no member named file
include/proto/listener.h:131: error: struct bind_conf has no member named line
include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
include/proto/listener.h:133: error: struct bind_conf has no member named by_fe
include/proto/listener.h:135: error: struct bind_conf has no member named arg
include/proto/listener.h:137: error: struct bind_conf has no member named ux
include/proto/listener.h:138: error: struct bind_conf has no member named ux
include/proto/listener.h:139: error: struct bind_conf has no member named ux
include/proto/listener.h:141: error: struct bind_conf has no member named listeners
include/proto/listener.h:141: error: struct bind_conf has no member named listeners
include/proto/listener.h:141: error: struct bind_conf has no member named listeners
In file included from src/haproxy.c:107:
include/proto/ssl_sock.h: At top level:
include/proto/ssl_sock.h:46: error: expected declaration specifiers or ... before SSL_CTX
src/haproxy.c: In function display_build_opts:
src/haproxy.c:272: error: expected ) before OPENSSL_VERSION_TEXT
src/haproxy.c:274: warning: implicit declaration of function SSLeay_version
src/haproxy.c:274: error: SSLEAY_VERSION undeclared (first use in this function)
src/haproxy.c:274: error: (Each undeclared identifier is reported only once
src/haproxy.c:274: error: for each function it appears in.)
src/haproxy.c:275: error: OPENSSL_VERSION_NUMBER undeclared (first use in this function)
src/haproxy.c:275: warning: implicit declaration of function SSLeay
src/haproxy.c:275: warning: format %s expects type char *, but argument 2 has type int
src/haproxy.c: In function deinit:
src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
src/haproxy.c:1188: warning: left-hand operand of comma expression has no effect
src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
src/haproxy.c:1188: error: struct bind_conf has no member named by_fe
src/haproxy.c:1196: error: struct bind_conf has no member named file
src/haproxy.c:1197: error: struct bind_conf has no member named arg
src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
src/haproxy.c:1198: warning: type defaults to int in declaration of __ret
src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
src/haproxy.c:1198: error: struct bind_conf has no member named by_fe
make: *** [src/haproxy.o] Error 1
I'm I missing some libs or sources from OpenSSL ?
And/or need to point them out so that make/gcc can find them?
I have copy haproxy from another machine where I did the build process on.
But I would like to be able to build it on my SLES 11 SP3 installation.
Thank you in advance.

Originally Posted by smflood
On 17/10/2014 15:36, mattias bjork wrote:
> I don't know if this is the right "context" to submit this question.
>
> How ever I'm having problem with building haproxy 1.5.5 with SSL
> support.
>
> I'm running SLES 11 SP3 with the latest updates via YAST2.
>
> Building without SSL support works fine.
>
> I use the syntax:
>
> make TARGET=linux2628 USE_OPENSSL=1
>
> And here is the output:
>
> gcc -Iinclude -Iebtree -Wall -O2 -g -fno-strict-aliasing
> -DCONFIG_HAP_LINUX_SPLICE -DTPROXY -DCONFIG_HAP_LINUX_TPROXY
> -DCONFIG_HAP_CRYPT -DENABLE_POLL -DENABLE_EPOLL -DUSE_CPU_AFFINITY
> -DASSUME_SPLICE_WORKS -DUSE_ACCEPT4 -DNETFILTER -DUSE_GETSOCKNAME
> -DUSE_OPENSSL -DUSE_SYSCALL_FUTEX -DCONFIG_HAPROXY_VERSION=\"1.5.5\"
> -DCONFIG_HAPROXY_DATE=\"2014/10/07\" \
> -DBUILD_TARGET='"linux2628"' \
> -DBUILD_ARCH='""' \
> -DBUILD_CPU='"generic"' \
> -DBUILD_CC='"gcc"' \
> -DBUILD_CFLAGS='"-O2 -g -fno-strict-aliasing"' \
> -DBUILD_OPTIONS='"USE_OPENSSL=1"' \
> -c -o src/haproxy.o src/haproxy.c
> In file included from include/types/acl.h:33,
> from include/types/proxy.h:40,
> from include/proto/log.h:32,
> from
> includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
> from src/haproxy.c:61:
> include/types/server.h:29:25: error: openssl/ssl.h: No such file or
> directory
> In file included from include/types/connection.h:30,
> from include/types/server.h:36,
> from include/types/acl.h:33,
> from include/types/proxy.h:40,
> from include/proto/log.h:32,
> from
> includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
> from src/haproxy.c:61:
> include/types/listener.h:127: error: expected specifier-qualifier-list
> before �SSL_CTX�
> In file included from include/types/acl.h:33,
> from include/types/proxy.h:40,
> from include/proto/log.h:32,
> from
> includehttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.comhttps://www.novell.com/common/cfgparse.h:29,
> from src/haproxy.c:61:
> include/types/server.h:207: error: expected specifier-qualifier-list
> before �SSL_CTX�
> In file included from src/haproxy.c:90:
> include/proto/listener.h: In function �bind_conf_alloc�:
> include/proto/listener.h:130: error: �struct bind_conf� has no member
> named �file�
> include/proto/listener.h:131: error: �struct bind_conf� has no member
> named �line�
> include/proto/listener.h:133: error: �struct bind_conf� has no member
> named �by_fe�
> include/proto/listener.h:133: error: �struct bind_conf� has no member
> named �by_fe�
> include/proto/listener.h:133: error: �struct bind_conf� has no member
> named �by_fe�
> include/proto/listener.h:133: error: �struct bind_conf� has no member
> named �by_fe�
> include/proto/listener.h:133: error: �struct bind_conf� has no member
> named �by_fe�
> include/proto/listener.h:135: error: �struct bind_conf� has no member
> named �arg�
> include/proto/listener.h:137: error: �struct bind_conf� has no member
> named �ux�
> include/proto/listener.h:138: error: �struct bind_conf� has no member
> named �ux�
> include/proto/listener.h:139: error: �struct bind_conf� has no member
> named �ux�
> include/proto/listener.h:141: error: �struct bind_conf� has no member
> named �listeners�
> include/proto/listener.h:141: error: �struct bind_conf� has no member
> named �listeners�
> include/proto/listener.h:141: error: �struct bind_conf� has no member
> named �listeners�
> In file included from src/haproxy.c:107:
> include/proto/ssl_sock.h: At top level:
> include/proto/ssl_sock.h:46: error: expected declaration specifiers or
> �...� before �SSL_CTX�
> src/haproxy.c: In function �display_build_opts�:
> src/haproxy.c:272: error: expected �)� before �OPENSSL_VERSION_TEXT�
> src/haproxy.c:274: warning: implicit declaration of function
> �SSLeay_version�
> src/haproxy.c:274: error: �SSLEAY_VERSION� undeclared (first use in this
> function)
> src/haproxy.c:274: error: (Each undeclared identifier is reported only
> once
> src/haproxy.c:274: error: for each function it appears in.)
> src/haproxy.c:275: error: �OPENSSL_VERSION_NUMBER� undeclared (first use
> in this function)
> src/haproxy.c:275: warning: implicit declaration of function �SSLeay�
> src/haproxy.c:275: warning: format �%s� expects type �char *�, but
> argument 2 has type �int�
> src/haproxy.c: In function �deinit�:
> src/haproxy.c:1188: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1188: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1188: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1188: warning: left-hand operand of comma expression has
> no effect
> src/haproxy.c:1188: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1188: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1188: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1196: error: �struct bind_conf� has no member named
> �file�
> src/haproxy.c:1197: error: �struct bind_conf� has no member named �arg�
> src/haproxy.c:1198: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1198: warning: type defaults to �int� in declaration of
> �__ret�
> src/haproxy.c:1198: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1198: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1198: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1198: error: �struct bind_conf� has no member named
> �by_fe�
> src/haproxy.c:1198: error: �struct bind_conf� has no member named
> �by_fe�
> make: *** [src/haproxy.o] Error 1
>
>
> I'm I missing some libs or sources from OpenSSL ?
>
> And/or need to point them out so that make/gcc can find them?
>
> I have copy haproxy from another machine where I did the build process
> on.
>
> But I would like to be able to build it on my SLES 11 SP3 installation.
So you're trying to build HAProxy 1.5.5 from source?
Do you have libopenssl and libopenssl-devel installed? What does "rpm
-qa | grep ssl" report?
You might have better luck installing HAProxy 1.5.5 already built for
SLES11 SP3 via the openSUSE Build Service @
https://build.opensuse.org/package/s...ackage=haproxy
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
Hello Simon,
Yes I'm trying to build it from source.
Unfortunately I don't have them installed.
Here is the output:
sudo -i rpm -qa | grep -i ssl
openssl-0.9.8j-0.62.1
libopenssl0_9_8-0.9.8j-0.62.1
libopenssl0_9_8-32bit-0.9.8j-0.62.1
perl-IO-Socket-SSL-1.38-5.2.2
perl-Net-SSLeay-1.35-2.14
openssl-certs-1.97-0.3.1
Thank you for your speedy reply.

Load rule failure in ASO cube building

Hi
I have an ASO cube and I'm trying to use a load rule to build my entire Measures dimension. Everything seemed to be working fine before, I had about 7,000 measures tagged with a particular UDA, however, now when I do the build, only about 2,200 of the members are getting tagged with the UDA, although there is no error file. There doesn't seem to be any rhyme or reason as to why some members are successfully getting the UDA assigned to them and some aren't. I even tried creating a new load rule and using a text file with the particular accounts, and again, it says everything was fine, but when I go back and look at the outline it's hit and miss. Any thoughts?

Hi,
I dont see any reason ,why it add UDA's for few and does not for few.
I request you to do the following
1. Check the data file
2. Check the rule file
3. and as per the definitions of the rule file ( i.e build properties, data source options ..etc.
see ,whether the data file is in harmony.
Sandeep Reddy Enti
HCC

Sleep heat fan

Last night I put my MBP to sleep just before I went to sleep. In the morning, the MBP was still asleep but super hot and the fan whirling. Is this normal? Should it get hot in the sleep mode?
thanks
Rick

I just experienced the same thing. Here's the crash log that was generated. I can't make heads or tails of it.
panic(cpu 0 caller 0x2AF6520D): AppleAHCI: slot (0) reused, newFIS = 0x00358027 : 0x409fed89 : 0x00000000 : 0x00000100, currentFIS = 0x08618027 : 0x40de4ac8 : 0x00000005 : 0x00000000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x14ebb668 : 0x128d1f (0x3c9540 0x14ebb68c 0x131df4 0x0)
0x14ebb6a8 : 0x2af6520d (0x2af664ec 0x0 0x358027 0x409fed89)
0x14ebb728 : 0x399338 (0x33c0c00 0x33e3900 0x20 0x0)
0x14ebb768 : 0x2af63e64 (0x3265c80 0x2af65052 0x33e3900 0x20)
0x14ebb7d8 : 0x2af4f4e6 (0x33c0c00 0x33e3900 0x14ebb818 0x2af5005f)
0x14ebb818 : 0x2b15c423 (0x33c0c00 0x33e3900 0x0 0x37a9dc)
0x14ebb8b8 : 0x2b15cd10 (0x33e8d00 0x3 0x3fd4480 0x0)
0x14ebb938 : 0x37aa8a (0x33bc5e0 0x1 0x0 0x3fdb1200)
0x14ebb9b8 : 0x37b4e5 (0x335ac200 0x1 0x20000 0x0)
0x14ebba38 : 0x37d1ad (0x0 0x0 0x14ebbd20 0x6)
0x14ebbd48 : 0x1aa1aa (0x3209680 0x0 0x14ebbd88 0x24bbba3f)
0x14ebbd68 : 0x1ab0e7 (0x14ebbdb8 0x1 0x3099c00 0x14ebbd98)
0x14ebbd98 : 0x1aa280 (0x1aa18b 0x14ebbdb8 0x0 0x120)
0x14ebbdc8 : 0x24baef2a (0x24baed14 0x3 0x24bdf480 0x0)
0x14ebbe28 : 0x24ba4446 (0x3099c00 0x2 0x14ebbdfc 0x397f4a0)
0x14ebbe48 : 0x3a93fd (0x3209c00 0x4ac634 0x3 0x66e000) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAHCIBlockStorage(1.0.3)@0x2b154000
dependency: com.apple.iokit.IOStorageFamily(1.5.1)@0x2aa70000
dependency: com.apple.iokit.IOAHCIFamily(1.0.2)@0x2af4d000
com.apple.driver.AppleAHCIPort(1.0.5)@0x2af61000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x24b3a000
dependency: com.apple.iokit.IOAHCIFamily(1.0.2)@0x2af4d000
com.apple.iokit.IOAHCIFamily(1.0.2)@0x2af4d000
com.apple.driver.AppleACPIPlatform(1.0.5)@0x24ba3000
dependency: com.apple.iokit.IOPCIFamily(2.1)@0x24b3a000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x24b50000
Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006; root:xnu-792.13.8.obj~1/RELEASE_I386
Model: MacBookPro1,2, BootROM MBP12.0061.B00, 2 processors, Intel Core Duo, 2.16 GHz, 1 GB
Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
Memory Module: BANK 1/DIMM1, 1 GB, DDR2 SDRAM, 667 MHz
AirPort: spairportwireless_card_type_airportextreme (0x168C, 0x86), 0.1.27
Bluetooth: Version 1.7.9f12, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Network Service: Parallels Host-Guest, Ethernet, en2
Network Service: Parallels NAT, Ethernet, en3
Serial ATA Device: ST9120821AS, 111.79 GB
Parallel ATA Device: MATSHITADVD-R UJ-846
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
iMac G4/17" MacBook Pro Mac OS X (10.4.8) 30GB iPod w/video

Failure to sleep

I have got my iMac preferences set to sleep after 10 minutes, but nothing happens. Can anyone suggest a possible cause please.

I resolved a sleep problem with the Mac Mini. My symptoms were that I could not sleep the computer with the pull-down menu. It would enter sleep for a few seconds then wake right up again. So, I started to Hibernate the computer. That worked for a while but eventually I could not Hibernate either.
After looking at .plist's, energy saver, wake on network - all the usual suspects, I dug into my logs to find the cause of the wake. The command is
syslog |grep -i "Wake reason ="
I was seeing all the wake reasons was EHC2 - which was appearing my console log as well but I didn't know what it meant. After more digging I concluded that EHC2 was device #2 on the USB bus. Anything looking like OHC, EHC, or USB would likely be an external device while LID0 is the "lid" on a laptop, PWRB is the power button, and RTC is the clock.
Once had a clue that device#2 was causing the wake, I used a USB sniffer app. One is provided in Apple's developer software, USB Prober. From here, it got a little hazy as the output wasn't exactly easy to follow. But, it appeared that something with a description of a "4 port hub" woke up my computer. This turned out to be an internal hub in the case of my external Newertech HD - the stackable HD provides additional USB and firewire ports. The kicker is that I had the USB hub connected but all the ports were empty.
I switched the HD to firewire only and unplugged the USB cable entirely. That was the end of my sleep problems. I didn't seem to have this problem with my old Mini running Tiger, only the new Mini running SL.
Hopefully anyone else having sleep problems in Snow Leopard can find some useful information in all of this.

Broadband failure in the heat

My broadband has failed mid to late afternoon on 6 occasions since 15 July. Each time I have spoken with the very polite helpdesk who have elevated the issue through level 1 to level 2. However, this has involved 1 hour on the phone and then a 24-48 hour wait for an engineer who informs me that the problem is with the local exchange - no fault found on my line. I have written to the Customer Service Director in Durham, but no reply. In the meantime I am sent glossy literature telling me that 'I'm important' and that I should take advantage of BT Sports and Infinity. Problem is BT has not invested any money in the local exchange and Infinity remains unobtainable.
My frustration is that there is a very friendly remote helpdesk who follow a set protocol - level 1, level 2, engineer - but above this sits a anonymous (un-contactable) and detached level of management. As a result, time is lost and money expended on nugatory engineer visits.
Can anyone give me the name and address of someone who I can discuss this issue with please? Many thanks

is there any problems listed for your exchange http://usertools.plus.net/exchanges/mso.php
http://usertools.plus.net/exchanges/?
http://btbusiness.custhelp.com/app/service_status
http://bt.custhelp.com/app/answers/detail/a_id/15036
there is no uk helpdesk number
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Reporting success or failure of labview command line build

We've set up a nightly build for our project, using a batch file for compiling the C++ code in our project on Windows. Thanks to some other posts on this subject, we've gotten the command-line build to work in Labview 8.2. I'd like to add the Labview build command to same batch file as the C++ build. We found how to check within Labview if the project built or failed; however, I didn't see a way to report the success or failure status of the build from the Labview environment back up into the calling batch file (as/just before Labview exits).
One option is to have the batch file check for the existence of the Labview output executable file(s). Does anyone have a more elegant solution?
Thanks,
Adam

Hello Adam,
Based on what you have described, your method seems to be the simplest way to do it. You can not only check whether the executable files were created, but you can also check to see the modification dates to make sure that they are from the latest build.
body { margin: 0 0 0 0; padding:0 0 0 0 }
td,div { font-family:Arial;font-size:10pt;vertical-align:top }
body { margin: 0 0 0 0; padding:0 0 0 0 }
.transcript { background-color:#d2d2d2; }
.messageBlock { margin-left:4px; margin-bottom:3px }
.message { margin-left:100px; word-wrap:break-word; white-space:-moz-pre-wrap; _white-spacere; }
.messageCont { margin-left:100px; word-wrap:break-word; white-space:-moz-pre-wrap; _white-spacere;}
.other { color:#39577a;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.myself { color:#da8103;font-style:normal;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont { font-size:8px;text-align:right; color:#39577a;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.myselfCont { font-size:8px;text-align:right; color:#da8103;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.system { margin-left:4px; word-wrap:break-word;color:#da8103;font-style:normal;font-weight:normal; white-space:-moz-pre-wrap; _white-spacere; }
.showTimestamp { margin-right:3px; float:right; color:#999999;font-style:normal;font-weight:normal; }
.other1 { color:#ac2000;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont1 { font-size:8px;text-align:right; color:#ac2000;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other2 { color:#3c9fa8;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont2 { font-size:8px;text-align:right; color:#3c9fa8;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other3 { color:#e25614;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont3 { font-size:8px;text-align:right; color:#e25614;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other4 { color:#0b6ac8;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont4 { font-size:8px;text-align:right; color:#0b6ac8;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other5 { color:#b23290;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont5 { font-size:8px;text-align:right; color:#b23290;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other6 { color:#02e7c7;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont6 { font-size:8px;text-align:right; color:#02e7c7;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.other7 { color:#5b3284;vertical-align:top;font-weight:bold;font-style:normal;float:left; width:95px; }
.otherCont7 { font-size:8px;text-align:right; color:#5b3284;font-family:Arial,Lucida Grande;font-style:normal;vertical-align:top;font-weight:bold;float:left; width:95px; }
.tsDisplay { display:block }To check if they exist, you can use the following batch command to check if a file exists:
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
IF EXIST some.txt DOSOMETHING
Good luck!
Kameralina
Ask NI (ni.com/ask)
Search The KnowledgeBase
NI Developer Zone
Measure It. Fix It. ni.com/greenengineering/
NI Vision ni.com/vision/

Failure FRM-32029 while compiling Form with Forms Builder

Hi.
I have problem. I compile a form with Forms Builder from DevSuiteHome and get the failure:
"FRM-32029 Window WINDOW not found; canvas-section CG$LOVCAN" (I translate it, it´s not the original terms).
I google and search the forum and oracle page, but found nothing about this failure. In Forms-Builder itself is also nothing recorded about this problem.
Do someone know more about this error?
Thanks.

Thanks inolau for answering.
The problem is, that I don´t have a documentation about the sourcecode and these forms worked under from 6i to 9i upgraded Oracle AS and DB servers. So the problem is not only "where is the WINDOW", than more "why doesn´t works it under a new 10g version and how get it working?".
That´s why I was searching for this not recorded error.
And I´m worry about that searching for the part of the sourcecode where I found the "WINDOW" is like looking for a needle in a haystack. ;)

Trials and Tribulations of a First Time MSI Builder

I'll try to keep this short and sweet (IMPOSSIBLE!), but hopefully this may make sense to some of you out there who have sought and found solice here on the MSI boards....
First off....I'm a first-time MSI MB user.....my system specs are as follows:
Voyeurmods Verge X case
MGE Vigor 500 PS
Athlon 64 2800
MSI K8T Neo FSRII
1 gig Kingston 400DDR (KVR400X64)
1- 80 gig Barracuda SATA
Thermalright SLK948U and TT UFO fan
Aopen DVD/CDR combo drive
TT Hardcano 12
Enermax 6 fan controller
Asus 9800xt
Audigy Platinum
and assorted other fans, belts, and whistles......
Now...the story and the point behind this post:
I have only built one other comp....2.4 Pentium Platform......nice, stable rig.....a few extra goodies to qualify it as a "semi-mod"...but it was a great system to cut my teeth on, and in all fairness, I had a lot of extra help with cables/bios/cpu install, etc. I wouldnt call it a "from-scratch" set up...Never one to NOT jump into the deep end of the pool, I decided to move up a bit and try a new build from scratch....I wanted a decent rig...strictly gaming......as close to state of the art as my budget would allow, but I was prepared to make exceptions......
My original MB of choice once I settled on an Athlon 64 was the Abit KV8. It was a great-looking MB; I thought the OATES cooling system was a significant upgrade from a lot of others...and I liked their "UGURU" system management tool...unfortunately, the Abit MB is now sitting in a trash bin....I have to say that, all emotion aside, Abit wont be seeing my cash any time in the future.....to call the OATES system a total failure would be an understatement...only AFTER I started reading the Abit boards did I realize that virtually every builder was removing the plastic OATES shroud and tossing it away.......the screw alignment in the OATES portion of the board, coupled with almost any aftermarket HS/fan alignment warps the board slightly and doesnt allow multiple sticks of memory to sit properly in the slots......if you folks think thats a joke, just check out the Abit forums.....I'd say that right now, the negative reviews of the KV8 boards are surpassing the "positive" reviews by a ratio of 2 or 3 to 1. And then try RMA'ing the board once its warped!
Now granted, the Thermalright SLK puts a hell of a stress load on the CPU section of the MB through sheer weight alone, but the MSI board, TO ME, seems to be a bit "beefier"....a tad thicker in construction. I dunno...maybe its the layout, or weight distribution. But I digress and this was "supposed" to be short and sweet....
Many hours of bareboning the build with the Abit board resulted in me switching manufacturers and trying MSI. Everything I tried....all the tech support....all the forums and Abit messageboards.....litterally swapping out every piece of equipment....nothing got that Abit board to boot up. I was getting error messages that werent even acknowledged by the manufacturer! Folks, you have NO idea how much better a product MSI is putting out compared to Abit.
For starters.....the board sits damned near perfectly on the standoffs.....one does NOT have to remove the video card to get at the memory slots (the Abit board requires MOST if not all video cards to be removed if swapping memory in slot 1)...the layout of the SATA and IDE brackets seemed a bit more ergonamically proficient on the MSI board.....about the only thing that appealed to me (initially)more on the Abit board was an "on board" LCD error check system that seemed to be a bit easier to use than the MSI D Bracket system. I say "seemed to be", but again, going back to basic board layout and design, the LCD's are virtually covered by the IDE cables that have to sit over the LCD's because of their close proximity to each other. Nice idea. Poorly executed.
So....if any of you first-timers have concerns about choosing the MSI board, start breathing easier.....once I switched boards, and used the exact same components as my first try with the Abit board, the K8T Neo started up first time out of the box.....everything about this board (knock wood), so far, has been great, and I also have to say that the help that all of you here dish out has made this experience nothing short of amazing.
Jocko, whoever the hell you are, you are my new Obi Wan Kenobi! Your advice in a few threads to newbies like myself was so damned "dead-on" ....so accurate...its like you know these boards and systems from the circuit on up! And I have to thank you right now for helping me even though we never exchanged emails or posts......many, many, many thanks!
Also, Mike...your thread for first-timers......it should be part of the itinerary for ALL newbies. Thanks for taking the time to share....
Finally...some additional thoughts that may help others ( or may not):
1. Configuring the BIOS is, to me anyway, always a bit scary. I like pointing and clicking...I hate pressing enter and using arrow keys...there are just too many damned choices and I'll always wonder if I made the right ones......scan back a few threads and search out any of Jocko's advice regarding the initial load of Windows and SATA drives...he makes this part easy. Also, there are several websites that give advice on optimum BIOS configs....you can find many links here on these forums.
2. If any of you want custom modded cases at decent pricing, dont be afraid to use Voyeurmods. Everything about Brian and his crew is top notch.....the customer service....the shipping.....the Verge X case is simply perfection.....I cant say enough nice things about them.
3. Kingston memory can be purchased directly from their USA website at fairly discounted pricing from just about anyone else on the web.....I paid $139.00 for 2 512 sticks of 400 DDR(not per stick...$139.00 total) a while back...pricing changes weekly so if you like Kingston product, check them weekly for specials...so far it has worked perfectly in my rig, and because you are buying direct, the warranty is as good as it gets.
4. The Thermalright SLK 948 is one hell of a heatsink, and the TT UFO fan that sits on top of it makes for one nice combo! My CPU refuses to overheat under load, and I cant say enough about how easy it was to install on the board. If any of you want a superb aftermarket product this does the trick nicely.
5. Any idea why the 2 power slots on the MSI MB are on opposite sides of the board? That was the one glitch I found on these boards that Abit did right...place the 2 power connections side by side for better cable management.
6. If on the first power up the entire system stays dark, chances are it AINT a bad Power supply...more than likely its front panel headers in the wrong slots..check your wiring. If there is just a slight glimpse of power and it cuts out immediately, its almost assuredly wrong wiring....the PS is shorting itself out.
7. On the HOT topic of power supplies....my MGE has 20 amps on the 12 volt line...I know, I know....its barely adequate to some of you....but I have to say this in as nice a way as possible: folks, it AINT always the power supply when a problem develops. I have read countless.....COUNTLESS posts/threads on both Board forums where a problem is "diagnosed" as being a crappy power supply. Some folks wont even discuss any other issue until a different PS is installed. The sad/funny thing is....if you read back through the threads here, as well as the Abit boards, I'd say 90% of the solutions to the problems didnt end up being the PS at all! Its more like: 30% user error....20% memory...10% CMOS clearing....20% component failure(including MB)....10% CPU seating.....10% PS.
8. Do....regardless of how much extra work is involved here....DO utilize a barebones build BEFORE you install in the case and hook up all the peripherals.....it cuts out SO many potential problems before they happen, and just makes so damned much sense. I know its extra effort, but if youre a first timer, and you want that first boot to take place; you want that main screen once you press "DELETE", this is the way to go.
9. Clearing CMOS. LOL! Yup......oh the errors of first- timers like myself!!!!!! Dont even bother posting here until you make sure you cleared the CMOS properly, and if youre not sure how, dont be afraid to ask stupid questions like I did here.
10. Dont be afraid to use cardboard as your anti-static material under a barebones...it works well...costs nothing...and your only potential issue is heat build up if your CPU freaks out.
11. DONT overuse your Artic Silver 5 on the CPU.....forget all the advice about "spreading out evenly" a thin layer of silver all over the CPU cover.....use the "grain of rice" method in the center.....a very small amount spreads out like you cant imagine! After I removed the HS from the CPU on the Abit board, I couldnt believe how thoroughly well the paste had spread over the CPU cover. If I had used more, or spread it out, the TR SLK would have forced it well over the sides of the CPU.
12. DONT be afraid of the BIOS. The MSI manual actually does a pretty decent job of guiding one through the initial set up, and YES...do NOT forget to press F10 to save all your changes.....it took me a couple of tries to make sure the changes "took".
13. DONT panic if you miss the F6 move on Windows install for SATA drivers.....it seems that on XP home, pressing F6 when prompted to made no difference.....30 seconds later the "add 3rd party drivers" screen comes up anyway.....for reference sake, my total Windows XP install took 16 minutes from start to finish.
14. Loading the VIA SATA drivers at that point in Windows is tricky for one very simple reason: the floppy doesnt have any "scroll down" arrows for multiple driver install. They are hidden UNDER the initial screen....press "S" when prompted for the initial driver....and then scroll down under the first batch to find the second one...highlight it and press "S"....dont panic if the screen doesnt change immediately...it "feels" like Windows lags a bit but the screen DOES change.
15. SATA cables dont always "sit" snugly in Barracuda drives...I tried 3 different cables from legit manufacturers in 2 different Seagates....they all fit...they all work...but just a tiny amount of pressure unseats them....use caution and try to keep any other cables from pressing OVER the SATA near the HD.
16. Bench test your system for at least 24 hours of continuous useage before you move it or do anything else with it......it just makes sense to see if anything shorts out or heats up......
Feel Free to email me ([email protected]) if you have any questions or want any ideas.....MSI has made my first real build a blast!
JJ

Hi
Welcome, glad you got some benefit from the threads, it all so easy once you've done it a few times, aint it.
Glad your going well, now you can help others
you could also join the folding team and help medical research.
enjoy
cheers
jocko

Macbook pro screen freezing/flickering peripheral failure

Hey guys
I use my Macbook Pro both at home for music production and live as an instrument. Recently I have been having problems, but for some reason these have never materialised at home - only in the live situation. I shall try to give as much info as possible, but I'm no use with Macs having been raised with windows machines.
Mac OS X 10.6.8
2.5 GHz Intel Core 2 Duo
4GB 667 MHz DDR2 SDRAM
I have around 13GB free HD space
It is second hand and therefore I have no idea about warranty. I have had the machine for over a year.
I THINK it's a 2008 17" model, although I am not sure.
Peripherals at home:
Digidesign Mbox 2 - USB
USB Mouse (third party)
M audio Oxygen 8 V2 keyboard - USB
HD TV as a second screen - DVI - VGA adapter
Live:
Novation Nio 2|4 uadio interface - USB
Novation Launchpad - USB
M audio Oxygen 8 V2 - USB
(Software wise I a running ableton 8 suite with izotope stutter edit. I average about 6% cpu usage)
Recently, my audio interfaces have begun to fail, but only in the live environment. I can switch the Mbox for the Nio at home and there are no problems whatsoever. 2 shows in a row this had failed, so I made sure to test all the equipment extensively. After 2 days of using the Nio as my soundcard using a different USB cable and slot, I assumed the problem was fixed.
On friday night we were playing a show, and mid set the screen froze with glitchy sections - looked like someone had broken the matrix. The screen began flickering in and out very fast in a strobe like fashion. My peripherals were still working fine, so I continued with the show in the hope that I could just control the session from them. Moments later, the audio failed, ad the system eventually cut out. I attempted to buy time and boot up again, but the same thing happened almost instantly.
Now that i've had a chance to get home and try it out, it has been working for hours at a time until eventually doing the same thing. I have found that most the time my usb mouse will remain responsive, yet I am unable to click on anything. Again, the sound generally keeps working, but one by one the peripherals fail. The screen flickering has only been temporary in the home setting, and does not sustain throughout the failure.
I'm generally poor with electronics, but the general consensus seems to be that it may be some kind of electro magnetism/static/I don't know effecting it live? I have never had a single problem with the machine until now. These failures have occured both running on battery and from mains power.

You may be right that a part of the problem is due to external electro-magnetic interference, but could also be heat build up, and the fact that at home it runs for hours before an issue starts, heat is probably a part of the problem. If you can, stop by an Apple store genius bar and let the techs run some diagnostics, explain what is happening and see if they can isolate the issue. You may want to leave it with them for a few hours and let it sit there and run to see if heat is an issue.

Turn of the sleep option

Can i turn of the sleep option when i close the display?
i want to keep running mi itunes after i close the display completely

Welcome to Apple Discussions
The machine is automatically programmed to go to sleep mode when the lid is shut. If it were left on with the lid close, I believe the heat build-up would create internal problems.

Failure to Sleep... HEAT build up...

Similar Messages

Maybe you are looking for