Re: xen on amd64 on dual core amd box

2007-04-01 Thread Jack Malmostoso
Ciao Alex Samad, nel tuo messaggio dicevi:

 I have just tried installing xen amd64 on a dual core machine, and I get timer
 error's filling up my syslog, is this normal ?

Are you using a kernel  2.6.16? It was the case a while ago, with newer
kernels it should be ok.

-- 
Best Regards, Jack
Linux User #264449
Powered by Fedora Core 6  Xubuntu (x86)
Powered by Debian Sid (ppc  AMD64)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



MSI forum runs Debian amd64

2007-04-01 Thread Stephen Olander Waters
Apparently, the MSI forum server runs Debian amd64. Cool, eh?
-s

 Forwarded Message 
 From: MSI HQ User to User Forum [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Subject: New announcement: MSI will replace all servers.
 Date: Sun, 01 Apr 2007 09:38:11 -0400
 
 Date: Sun, 01 Apr 2007 13:38:06 +
 X-Mailer: SMF
 Content-Type: text/plain; charset=ISO-8859-1
 Content-Transfer-Encoding: 7bit
 Message-Id: [EMAIL PROTECTED]
 
 Hi guys,
 
 Finally MSI and the forum team reached an agreement.
 As you know the current forum server is incredibly fast.
 
 MSI has done some testing the last few days with new fileservers for 
 LiveUpdate and downloading various stuff but they where unable to match the 
 speed of the forum server.
 
 Because they noticed we do such a good job of running the forum, they wanted 
 us to takeover all other servers and put everything on the forum server.
 
 This includes their marketting/support websites, fileservers and all other 
 forums.
 We think our server can handle all this traffic with ease.
 
 Our current traffic is between 100~200GB each month, but we think our 
 connection can handle all the traffic and should give better results.
 MSI thinks that the current server can do all their other traffic as well.
 
 It might slowdown the forum a little bit, but we expect no major problems.
 This move will happen beginning of the second quarter this year.
 
 Our forum server is build with this stuff:
 
 2x Xeon 2.8GHz
 2x 15000 RPM SCSI drive's in RAID1 (but we are going to add 2 more for RAID5 
 to gain about 275MB/s speed)
 2x 1GB memory reg ecc
 Debian AMD64 with all the latest updates.
 
 Tests so far has shown that we can handle MSI's traffic of 27TB/month isn't a 
 problem.
 So please test the speed of everything the first day of next quarter, we are 
 moving bits and pieces that day and hope to recieve reports on the speed.
 
 There might be a nice supprice for the best reporter on how the move is 
 going, but I'm not allowed what that will be.
 
 I will post shortly the email address that can be used to send in reports.
 
 [Edit]The move has been done.
 You can use this link to test the new servers: http://www.msi.eu
 Also, you can sent in speed reports here: [EMAIL PROTECTED]
 
 To unsubscribe from these announcements, login to the forum and uncheck 
 Receive forum announcements and important notifications by email. in your 
 profile.
 
 You can view the full announcement by following this link:
 
 http://forum.msi.com.tw/index.php?topic=106503.0
 
 Regards,
 The MSI HQ User to User Forum Team.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



gcc-4.1

2007-04-01 Thread Gudjon I. Gudjonsson
Hi
   Has anyone noticed that gcc is older in experimental for amd64 than for 
other architectures. It seems to me like dependencies that go in circles.
   If so, does anyone have an explanation? I wanted to compile the newest 
version of openoffice but I need this version of gcc for that.

Regards
Gudjon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



out of memory

2007-04-01 Thread Francesco Pietra
System; two dual-opteron, amd64 etch, 16GB ram, raid1.

Heavy computation (memory either 1750 mb or 3750 mb
per node) started with high % cpu usage and little
usage of memory. Then, the two factors inverted, the
HD led became lighted without interruption. The
computation then closed incomplete with the warning
message in the output file;

*** ARMCI INFO

The application attempted to allocate a shared memory
segment of 38731776 bytes in size. This might be in
addition to segments that were allocated succesfully
previously. The current system configuration does not
allow enough shared memory to be allocated to the
application.
This is most often caused by:
1) system parameter SHMMAX (largest shared memory
segment) being too small or
2) insufficient swap space.
Please ask your system administrator to verify if
SHMMAX matches the amount of memory needed by your
application and the system has sufficient amount of
swap space. Most UNIX systems can be easily
reconfigured to allow larger shared memory segments,
see http://www.emsl.pnl.gov/docs/global/support.html
In some cases, the problem might be caused by
insufficient swap space.
***
0:allocate: failed to create shared region : -1
0:allocate: failed to create shared region : -1
Last System Error Message from Task 0:: Invalid
argument
  0: ARMCI aborting -1 (0x).
  0: ARMCI aborting -1 (0x).
system error message: Invalid argument
3:SigIntHandler: interrupt signal was caught: 2
3:SigIntHandler: interrupt signal was caught: 2
Last System Error Message from Task 3:: No such file
or directory
  3: ARMCI aborting 2 (0x2).
  3: ARMCI aborting 2 (0x2).
system error message: No such file or directory
1:SigIntHandler: interrupt signal was caught: 2
1:SigIntHandler: interrupt signal was caught: 2
Last System Error Message from Task 1:: No such file
or directory
  1: ARMCI aborting 2 (0x2).
  1: ARMCI aborting 2 (0x2).
system error message: No such file or directory
2:SigIntHandler: interrupt signal was caught: 2
2:SigIntHandler: interrupt signal was caught: 2
Last System Error Message from Task 2:: No such file
or directory
  2: ARMCI aborting 2 (0x2).
  2: ARMCI aborting 2 (0x2).
system error message: No such file or directory
 Creating: host=deb64, user=francesco,
   file=/home/francesco/nwchem50/bin/nwchem,
port=57429
  4: interrupt(1)
WaitAll: No children or error in wait?

The http suggested above is of no help, referring to
Linux kernel 2)

This warning message was exaclty the same with the two
different mem allocations. With smaller matrices (ie
smaller molecules) the same type of computation ends
OK.

Thanks for suggestions how to tune the system.

francesco pietra


 

Looking for earth-friendly autos? 
Browse Top Cars by Green Rating at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: gcc-4.1

2007-04-01 Thread Kurt Roeckx
On Sun, Apr 01, 2007 at 09:52:50PM +0200, Gudjon I. Gudjonsson wrote:
 Hi
Has anyone noticed that gcc is older in experimental for amd64 than for 
 other architectures. It seems to me like dependencies that go in circles.
If so, does anyone have an explanation? I wanted to compile the newest 
 version of openoffice but I need this version of gcc for that.

gcc-4.1 is in testing and unstable for quite a while, and is the
default compiler for testing/etch.

openoffice.org is also available in testing/etch, and I have no idea why
it would suddenly require a newer gcc.

I have no idea why you have a problem with this.


Kurt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: out of memory

2007-04-01 Thread Kurt Roeckx
On Sun, Apr 01, 2007 at 01:18:07PM -0700, Francesco Pietra wrote:
 System; two dual-opteron, amd64 etch, 16GB ram, raid1.
 
 Heavy computation (memory either 1750 mb or 3750 mb
 per node) started with high % cpu usage and little
 usage of memory. Then, the two factors inverted, the
 HD led became lighted without interruption. The
 computation then closed incomplete with the warning
 message in the output file;
 
 *** ARMCI INFO
 
 The application attempted to allocate a shared memory
 segment of 38731776 bytes in size. This might be in
 addition to segments that were allocated succesfully
 previously. The current system configuration does not
 allow enough shared memory to be allocated to the
 application.
 This is most often caused by:
 1) system parameter SHMMAX (largest shared memory
 segment) being too small or
 2) insufficient swap space.
 Please ask your system administrator to verify if
 SHMMAX matches the amount of memory needed by your
 application and the system has sufficient amount of
 swap space. Most UNIX systems can be easily
 reconfigured to allow larger shared memory segments,
 see http://www.emsl.pnl.gov/docs/global/support.html
[...]

 The http suggested above is of no help, referring to
 Linux kernel 2)
 
 This warning message was exaclty the same with the two
 different mem allocations. With smaller matrices (ie
 smaller molecules) the same type of computation ends
 OK.
 
 Thanks for suggestions how to tune the system.

Did you read about how to increate the shmmax parameter, and did you
change it?  It actually tells you how to change that setting.  It still
defaults to 32 MB, and you tried to allocate more (36 MB).

Anyway, use /etc/sysctl.conf to set it.


Kurt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: xen on amd64 on dual core amd box

2007-04-01 Thread Alex Samad
On Sun, Apr 01, 2007 at 10:29:40AM +0200, Jack Malmostoso wrote:
 Ciao Alex Samad, nel tuo messaggio dicevi:
 
  I have just tried installing xen amd64 on a dual core machine, and I get 
  timer
  error's filling up my syslog, is this normal ?
 
 Are you using a kernel  2.6.16? It was the case a while ago, with newer
 kernels it should be ok.
nope 2.6.18
debxen:~# COLUMNS=150 dpkg -l '*xen*' | grep ^ii
ii  linux-image-2.6-xen-amd64   2.6.18+6Linux
kernel 2.6 image on AMD64
ii  linux-image-2.6.18-4-xen-amd64  2.6.18.dfsg.1-12Linux
2.6.18 image on AMD64
ii  linux-modules-2.6.18-4-xen-amd6 2.6.18.dfsg.1-12Linux
2.6.18 modules on AMD64
ii  xen-hypervisor-3.0.3-1-amd643.0.3-0-2   The Xen
Hypervisor on AMD64
ii  xen-linux-system-2.6.18-4-xen-a 2.6.18.dfsg.1-12XEN system
with Linux 2.6.18 image on AMD64
ii  xen-tools   3.1-1   Tools to
manage debian XEN virtual servers
ii  xen-utils-3.0.3-1   3.0.3-0-2   XEN
administrative tools
ii  xen-utils-common3.0.3-0-2   XEN
administrative tools - common files



Apr  2 06:48:15 debxen kernel: Timer ISR/3: Time went backwards:
delta=-63867412 delta_cpu=1824132588 shadow=536987137206 off=781032024
 processed=53783200 cpu_processed=53594400
Apr  2 06:48:15 debxen kernel:  0: 53783200
Apr  2 06:48:15 debxen kernel:  1: 53588400
Apr  2 06:48:15 debxen kernel:  2: 53775200
Apr  2 06:48:15 debxen kernel:  3: 53594400
Apr  2 06:48:21 debxen kernel: printk: 7 messages suppressed.
A
 
 -- 
 Best Regards, Jack
 Linux User #264449
 Powered by Fedora Core 6  Xubuntu (x86)
 Powered by Debian Sid (ppc  AMD64)
 
 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 
 


signature.asc
Description: Digital signature


Re: gcc-4.1

2007-04-01 Thread Rob Andrews
On 01-Apr-2007 20:52.50 (BST), Gudjon I. Gudjonsson wrote:
 Has anyone noticed that gcc is older in experimental for amd64 than for 
  other architectures. It seems to me like dependencies that go in circles.
 If so, does anyone have an explanation? I wanted to compile the newest 
  version of openoffice but I need this version of gcc for that.

The packages in experimental don't seem to build for all architectures -
another example is gnome-applets, which has been built for i386 only.

Sometimes it is because of failure to build on that architecture. Sometimes
it just doesn't build.

Look at the per-package build logs at buildd.debian.org for more information.

-- 
rob andrews   :: pgp 0x01e00563 :: [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]