1) Message boards : Cafe LHC : Murray Gell-Mann passes (Message 38988)
Posted 28 May 2019 by Gary Charpentier
Post:
Caltech Mourns Death of Murray Gell-Mann, Nobel Prize-Winning Physicist Who Developed the Theory of Quarks
2) Message boards : News : Pausing submission of LHCb Applications (Message 37393)
Posted 21 Nov 2018 by Gary Charpentier
Post:
Just confirming, LHCb only and not the others, Sixtrack, Atlas and Theory?
3) Message boards : Number crunching : Computation errors (Message 25651)
Posted 17 Jun 2013 by Gary Charpentier
Post:
Well no code is perfect; however SixTrack MacOS executable has passed the
18 standard tests. It is rather new though. The executable is
32-bit, so 64-bit shouldn't come into it really. maybe we should build with
-g and traceback options at least to have a better idea where the crash
occurred. If you could give me a pointer to WU I could rerun the case
here at CERN or on my own MAC. Eric.

Here are a couple of the 96 ...
http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=7889834
http://lhcathomeclassic.cern.ch/sixtrack/workunit.php?wuid=7889768
4) Questions and Answers : Unix/Linux : 64 Bit Mac Bus Error (Message 25650)
Posted 16 Jun 2013 by Gary Charpentier
Post:
Is there a bug (32/64 int length) in the Mac version? Is there a spot where a pointer is cast to an int and then back? (Use size_t) That fails when run on a 64 bit Mac as the pointer is 64 bits wide but the int is 32. (The O/S intentionally writes zeros as the first four gigs of process space to force bus errors.) Could also be loading a 64 bit lib (framework) instead of a 32 bit lib. (check the link options) As these are happening with near zero run time it looks very much like a bug.

This 64 bit machine is working fine on many other projects.

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGBUS: bus error

Crashed executable name: sixtrack_apple_gen
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.7.5 build 11G63
Thu Jun 13 11:50:51 2013

0   sixtrack_apple_gen                  0x0020df9e  PrintBacktrace (in sixtrack_apple_gen) + 1022

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0xffffffe1 ebx: 0x00000003 ecx: 0xbfffa61c edx: 0x9198ec22
  edi: 0xbfffa678 esi: 0x00000003 ebp: 0xbfffa648 esp: 0xbfffa61c
   ss: 0x00000023 efl: 0x00000206 eip: 0x9198ec22  cs: 0x0000000b
   ds: 0x00000023  es: 0x00000023  fs: 0x00000000  gs: 0x0000000f

5) Message boards : Number crunching : Computation errors (Message 25646)
Posted 15 Jun 2013 by Gary Charpentier
Post:
Is there a bug (32/64 int length) in the Mac version?

This machine is working fine on many other projects.

<core_client_version>7.0.28</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGBUS: bus error

Crashed executable name: sixtrack_apple_gen
Machine type Intel 80486 (32-bit executable)
System version: Macintosh OS 10.7.5 build 11G63
Thu Jun 13 11:50:51 2013

0   sixtrack_apple_gen                  0x0020df9e  PrintBacktrace (in sixtrack_apple_gen) + 1022

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0xffffffe1 ebx: 0x00000003 ecx: 0xbfffa61c edx: 0x9198ec22
  edi: 0xbfffa678 esi: 0x00000003 ebp: 0xbfffa648 esp: 0xbfffa61c
   ss: 0x00000023 efl: 0x00000206 eip: 0x9198ec22  cs: 0x0000000b
   ds: 0x00000023  es: 0x00000023  fs: 0x00000000  gs: 0x0000000f
6) Message boards : Number crunching : lhcathome.cern.ch blacklisting IP addresses? (Message 21317)
Posted 23 Mar 2009 by Gary Charpentier
Post:
You\\\\\\\'re not the only one. Maybe you have read this thread over at E@H already.

cu,
Michael

or http://lhcathome.cern.ch/lhcathome/forum_thread.php?id=2974 here.
7) Message boards : Number crunching : Can't reach LCH@home (Message 20653)
Posted 12 Oct 2008 by Gary Charpentier
Post:
I have machines at two locations. At one I have no problem getting to LHC@home. The other can\\\'t reach it. I reach as far as dewberry-ebrc.core-net.qmul.ac.uk [138.37.3.204] as hop 19. I see my other machine gets there as hop 16. Don\\\'t know why one stops there and the other gets through.

Gary



Well, it works from Canada. connecting thru sprintlink, telia, and \\\'ja\\\'.

7]
20 194 ms 191 ms 191 ms dewberry-ebr3.core-net.qmul.ac.uk [138.37.3.204]

21 195 ms 191 ms 191 ms hepboinc.ph.qmul.ac.uk [138.37.50.115]

Trace complete.

C:\\\\Users\\\\a>When you run that tracert command, does the first line verify that IP that you\\\'re connecting to? If not, then perhaps the second computer\\\'s DNS is different.
Does your tracert have a maximum number of hops equal to where it stops?

\\\"Tracing route to hepboinc.ph.qmul.ac.uk [138.37.50.115]
over a maximum of 30 hops:\\\"
Myself, I use openDNS.

You could also make sure that your IP configuration doesn\\\'t have a TTL value set to 20.
http://secfr.nerim.net/docs/fingerprint/en/ttl_default.html



IP numbers match, not a DNS problem (my first thought)
Tracert shows 30 returns. All the rest were the * * * kind.
Only recent local change is SP3 for XP Pro. Web page you sent me to is so out of date it doesn't even list XP however another reference indicates the default is 128.
The machine is trying to report a completed work unit so it obviously has connected in the past.
8) Message boards : Number crunching : Can't reach LCH@home (Message 20643)
Posted 10 Oct 2008 by Gary Charpentier
Post:
I have machines at two locations. At one I have no problem getting to LHC@home. The other can't reach it. I reach as far as dewberry-ebrc.core-net.qmul.ac.uk [138.37.3.204] as hop 19. I see my other machine gets there as hop 16. Don't know why one stops there and the other gets through.

Gary



©2019 CERN