The error message :
[17223237.380000] ata3: command 0x25 timeout, stat 0xd0 host_stat 0x61
[17223297.380000] ata3: translated ATA stat/err 0xd0/00 to SCSI SK/ASC/ASCQ 0x47/00
Now, my server stalls at such states or so. I have no idea what it is. If any of you happens to know I would appreciate it. Meanwhile I will go onto finding the solution to the problem.
Updated : 11 April 2007
It was a problem due to the SATA - controller . It is the faulty component. It is of type 3124. Look out for this defective design.
Wednesday, March 28, 2007
Sunday, March 25, 2007
Undefined Operations in GCC
Schedules have been tight.
Recently, a friend of mine showed to me very naive code.
#include "stdio.h"
int main()
{
int count = 0;
while ( count < 8 )
{
printf("%d %d",count,count++);
}
return 0;
}
Simple, and I was tricked into answering :
0 0
1 1
2 4
...
Well, not quite true, it turned out it is evaluated from right to left in C ( printf is a procedural call, after all ). It caught me really off guard for such a problem. After researching awhile, PERL seems to react the same. But not for PHP. No tests for JAVA and javascript yet. All of the tests are done on an IntelX86 machine.
Now that makes me think what could be the cause of such eerie results. No idea. I thought it could have been compiler differences, conventions. I talked this with a friend of mine, and interesting we find that the gcc compiler with the -Wall option on, yields this :
a.c: In function `main':
a.c:8: warning: operating on `count' may be undefined
a.c:8: warning: operating on `count' may be undefined
Well, he later gave me a link of this :
http://www.ddj.com/dept/cpp/184403851/
Problem solved? Guess so...? I still cannot answer what is for PERL and PHP though.
Recently, a friend of mine showed to me very naive code.
#include "stdio.h"
{
int count = 0;
while ( count < 8 )
{
printf("%d %d",count,count++);
}
return 0;
}
Simple, and I was tricked into answering :
0 0
1 1
2 4
...
Well, not quite true, it turned out it is evaluated from right to left in C ( printf is a procedural call, after all ). It caught me really off guard for such a problem. After researching awhile, PERL seems to react the same. But not for PHP. No tests for JAVA and javascript yet. All of the tests are done on an IntelX86 machine.
Now that makes me think what could be the cause of such eerie results. No idea. I thought it could have been compiler differences, conventions. I talked this with a friend of mine, and interesting we find that the gcc compiler with the -Wall option on, yields this :
a.c: In function `main':
a.c:8: warning: operating on `count' may be undefined
a.c:8: warning: operating on `count' may be undefined
Well, he later gave me a link of this :
http://www.ddj.com/dept/cpp/184403851/
Problem solved? Guess so...? I still cannot answer what is for PERL and PHP though.
Subscribe to:
Posts (Atom)