Hi together,

today Bruno and I setup and tested the new Testcrate exflutca10 with Ubuntu 16.04 (Xenial) with Kernel 4.4.0-21 the DAMC2 Card.

It's work fine.

Best,

Frank

All eight modules in crate 6 have been upgraded to bootloader version 21688. Now it is possible to configure digitizers (load mcs file) through PCIe express. It is very important to know that any firmware change should be done in partitioned mode ( ADQUpdater switch should be -eup) otherwise bootloader will be erased.

I reseted the NAT MCH EPROM for the Switch. After the rest the eprom shows other enterys when I read out the settings.

Andreas has installed the Beckhoff Software TWINCAD 3.1 on the Service Laptop.

I changed the setting "configure pcie virtual switches" -> max link speed from 8 GT/s to 2,5 GT/s

After this, the Cards work properly.

ADQ108 firmware was corrected and uploaded into FPGA. The version is 21-01-03-00 R17736. Previous version was not correct.

What are to do on Crate upgrade detailed:

1.:            Login via ssh

2.:            sudo su –

3.:            apt-get update

4.:            apt-get upgrade

5.:           cp /doocs/exflutcaX/server/x2timer_server/x2timer_server.conf /doocs/exflutcaX/server/x2timer_server/x2timer_server.conf.org

6.:           apt-get autorevoe pciedev-dkms upciedev-dkms doocs-clientlib-18-6-6-precise1 doocs-pcie-tools doocs-serverlib-18-6-6-precise1 doocs-watchdog-server doocs-x2timer-server doocs-dirs ttf-scripts

7.:           apt-get install linux-generic-lts-trusty linux-image-generic-lts-trusty

8.:           reboot

9.:            Login via ssh.

10.:         sudo su –

11.:         apt-get install pciedev-dkms upciedev-dkms doocs-clientlib-18-6-6-precise1 doocs-pcie-tools doocs-serverlib-18-6-6-precise1 doocs-watchdog-server doocs-x2timer-server doocs-dirs ttf-scripts

12.:         vi /doocs/exflutcaX/server/x2timer_server/x2timer_server.conf

13.:         change the lines:  REG_MAP:        "x2timer_1_x_x.map" and FWU_FILE: /data/babies/x2timer_1_x_x.bin" to the right version.

14.:         cp the right map file version to /doocs/exflutcawp78/server/x2timer_server/

15.:         Download the right F/W Version from the x2timer Card to the right crate and install it with “ipmitool -H exflutcaX-mch -P "" -B 0 -b 7 -t 0x7a hpm upgrade x2timer_1_X_X.hpm”

16.:         telnet exflutcaX-mch

17.:         show_fru (look at the right FRU ID left hand)

18.:         shutdown <fru_id>

19.:         fru_start <fru_id>

20.:         “exit” from the MCH

21.:         reboot the upgraded Crate.

F/W on MCH (exflutca3-mch) cahnged from 2.16 to version 2.17

ipmiconsole -h exflutcaX-sol -I 0

disconnect the session: &.

2015-04-20 EXFLUTCAWP78

06:50      Start with the OS Update for the crate wp78.

1.     Update from round 100 Packages.

2.     Kernel upgrade from 3.5.02 to 3.13.0-45

After the Kernel update the Modules x2timer and pciedev does not work anymore. He load the wrong module from kernel 3.5 , but that’s does not work.

So I have to uninstall the Modules with “autoremove” and to reinstall both modules. Than it works.

08:00      I realized that the MCH are not reachable. So I have to do it with jddd and not via ipmi.

1.     I upgraded the x2timer card from 1.10 to 1.17.4 via jddd.

2.     To make the upgrade complete I have to pull out the xtimer Card, but I can’t do it now because the Crate are working in the experimental Hall 49D and it is not allowed to enter the Hall without a professional. Laurens Wissmann was not able to come with us at this time.

12:00      At the noon time I shutdown the Crate wp78 and Laurens pull off the Power. He changed the RTM from

the Struck Board. The bad thing was that the changing bring up a new Problem (not of course the RTM but because of the insertion). The crate does not come up again.

1.     So I  go to the Hall with my service case. But I can’t find the reason for this.

2.     In Patricks stimulus towards I remove all Cards and put it back again.

At round about two o clock Bruno start with the update on the Struck Board.

 Frank

I put in the lines:

http_proxy="http://exflwgs06.desy.de:3128"
https_proxy="http://exflwgs06.desy.de:3128"
ftp_proxy="http://exflwgs06.desy.de:3128"
 

in /etc/environment

Karabo Framework was fixed to not rely on the ICU Unicode package anymore. Therefore the following package has 
been removed:

libicu48 - International Components for Unicode

For testing karabo devices with trunk of Framework, the following additional packages have been installed on crate 4:

libicu48 - International Components for Unicode

I changed the Hostnames to your given hostnames and IP Adresses.

I upgraded the Ubuntu on exflutcadev from 12.04.04 to 12.0.4.05. Also I installed gfortran and doxygen.

-------------------------------------------------------------------------------

-- MCS file generator options

-------------------------------------------------------------------------------

In Impact, select 'Create PROM File (PROM File Formatter)' and then select:

Select Storage Target

      Xilinx Flash/PROM

Add Storage Device

      Prom Family: Platform Flash

      Device (bits): xcf32s [32M]

      Add Storage Device

Enter Data

      Select name and folder

Select bit file and generate mcs file.

-------------------------------------------------------------------------------

-- MCS programming options

-------------------------------------------------------------------------------

In Impact, right click the PROM of the DAMC2 board and select 'Set Programming

Properties..'

PROM Specific Properties

      Load Mode 'On' (optional)

      Parallel Mode 'On' (mandatory)

Advanced PROM Programming Properties

      PROM is Configuration Master 'On'

            [select clock source] 'External Clock'

The file "/etc/auo.master" included now the lines:

+auto.master
/-      /etc/auto.data
/-      /etc/auto.devhome

the new file "/etc/auto.devhome" has the line"

/devhome   -rw,soft,nfsvers=3      192.168.81.200:/devhome

inserted.

I installed on exflutcadev also nfs-kernel-server to export the Folder /devhome.

The file "/etc/exports" is configured:

/devhome        192.168.81.0/24(rw,sync,no_subtree_check)

I chnged the Kernel fom 3.5.0-23-generic to 3.13.0-45-generic.

The new dkms system can't work with the modules pciedev-dkms upciedev-dkms and spd_adq_pci. So you have to reinstall the Modules.

For Testing Karabo to TANGO Interface, I have installed a MySQL DB Server and a local TANGO control System on exflutcadev.

Here is the command:
exflutcadev:../abeckman> sudo apt-get install mysql-common mysql-server
Reading package lists... Done
Building dependency tree       
Reading state information... Done
mysql-common is already the newest version.
mysql-common set to manually installed.
The following extra packages will be installed:
  libhtml-template-perl mysql-server-5.5 mysql-server-core-5.5
Suggested packages:
  libipc-sharedcache-perl tinyca
The following NEW packages will be installed:
  libhtml-template-perl mysql-server mysql-server-5.5 mysql-server-core-5.5

exflutcadev:../abeckman> sudo apt-get install liblog4tango4 libtango-tools python-pytango tango-accesscontrol tango-common tango-db tango-icon-theme tango-starter tango-test
[sudo] password for abeckman: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  dbconfig-common libcos4-1 libjs-sphinxdoc libomniorb4-1 libomnithread3c2 libtango7
Suggested packages:
  virtual-mysql-client mysql-client postgresql-client kdelibs-data omninotify
The following NEW packages will be installed:
  dbconfig-common libcos4-1 libjs-sphinxdoc liblog4tango4 libomniorb4-1 libomnithread3c2 libtango-tools
  libtango7 python-pytango tango-accesscontrol tango-common tango-db tango-icon-theme tango-starter tango-test

 The driver is in the MTCA4U software repository under
https://svnsrv.desy.de/public/mtca4u/drivers/

It consists of two parts: The gpcieuni base driver and the pcieuni
driver. You first have to install the gpcieuni driver, otherwise the
pcieuni driver will not compile. The latest tags are
https://svnsrv.desy.de/public/mtca4u/drivers/gpcieuni/tags/0.1.1/
https://svnsrv.desy.de/public/mtca4u/drivers/pcieuni/tags/0.1.2/

Installation:
In addition to the kernel headers and the compiler you need the dkms
(dynamic kernel module support) package installed. It comes with you
distribution.

After downloading the driver just run
$ sudo make install
, first for gpcieuni and then for pcieuni.
(no need to do 'make' first because the installation is running dkms,
which does the compilation into the current kernel for you)

The driver is registering to the XILINX vendor ID 10EE and PCI Device ID
99 (and also 37, 38 and 39 which are used for DESY LLRF).

You can manually register the driver to you device, for example an
Altera FPGA (vendor id 1172) with Device ID 2407 (run as root)
# echo 1172 2407 > /sys/bus/usb/drivers/pcieuni/new_id

(IDs are in hex, you have to do this after each reboot or
loading/unloading of the driver).

You can now access the device using MTCA4U, for instance QtHardMon or
the command line tools, or from C++.

Attention: DMA transfer will probably not work because it uses the
simple implementation used at DESY. Especially the DMA of the stock
firmware for the Struck SIS8300 does not work with this driver.
But all registers of the whole PCIexpress address space is accessible
(except for bar 2, which is reserved for DMA in the DESY implementation
and intentionally not exposed to the user).

There is a driver for the SIS8300 stock firmware from the upciedev
(which is the original familiy the pciuni was forked from). But this
branch is still buggy and insecure by design and can kill your Linux kernel.

 Removed DAMC2, as cpu was not reachable.

ADQ108 firmware is upgraded to the latest version. In this version SP-Device core has been changed and some small changes in user logic part to meet timing constraints. version is 21-02-00-r17736

I attached the results.

 Installation of DOOCS related packages

• pciedev-dkms, upciedev-dkms, doocs-dirs-min, x1timer-dkms, doocs-x2timer-server, doocs-pcie-tools

Configuration of DOOCS server and portmap config files

• changes user to doocsadm: > sudo su doocsadm
• edit /export/doocs/server/x2timer_server/x2timer_server.conf

  • oper_gid:       3555

  • xpert_gid:      406

  • SVR.FACILITY:   "LAB.TEST"

  • SVR.DEVICE:     "X2TIMER.XFEL"

  • eq_fct_name:    "EXFLUTCA????.0"

    NAME: :    "EXFLUTCA????.0"

  • SLOT:   ?

• edit /export/doocs/server/watchdog_server/watchdog_server.conf

  • oper_gid:       3555

• edit (if not there create) as root (sudo) /etc/default/rpcbind

  • add line OPTIONS="-i -w"

• restart portmap: > sudo service portmap restart

Add entries to ENS server

• login as doocsadm into a doocs machine: > ssh doocsadm@doocsdev12
• edit ens configuration (be sure what you are doing, as this is the main DOOCS ENS configuration!!!) > ens -e
  • search for already existent similar entry like EXFLUTCA6 related to the X2TIMER server
  • copy the whole block and modify to new name of system to be added
  • do the same for the Watchdog entry
• save and exit
• distribute changes with ens -u
• wait.........and still wait ......

 Configuration of timing with jddd

• jddd.desy.de -> java web start -> jddd-run.jnlp
• FLASH -> Overfiew -> SubPanels -> select_apps_on_crates.xml "open"
• TAB "LAB XFEL"
• "PLEASE DO NOT TOUCH TAB 28D" !!!
• work only with AER19!!

MCH setup changes for timing

• # Params: src: source clock identifier
• # 2 - CLK1 AMC 2
• # Params: dst: destination clock identifier
• clk_phys_out = 3, 2
• clk_phys_out = 4, 2
• clk_phys_out = 5, 2
• clk_phys_out = 6, 2

The new Kernel 3.5.0-46 does not work with the ADQ driver. All other drivers are ok.

 The pacage pciedev-dkms have problems with the Kernel thats the reason for this.

CPU Test old 2. new 1.

1:

27.10.2014

Temp. Air: 19,2 C

Cooling 100%

Mon Oct 27 12:32:28 CET 2014

IDLE:

root@exflutcadev1:~# sensors

coretemp-isa-0000

Adapter: ISA adapter

Physical id 0:  +39.0°C  (high = +86.0°C, crit = +100.0°C)

Core 0:         +37.0°C  (high = +86.0°C, crit = +100.0°C)

Core 1:         +28.0°C  (high = +86.0°C, crit = +100.0°C)

Core 2:         +31.0°C  (high = +86.0°C, crit = +100.0°C)

Core 3:         +38.0°C  (high = +86.0°C, crit = +100.0°C)

Mon Oct 27 12:34:06 CET 2014

LOAD: 4 100%

root@exflutcadev1:~# sensors

coretemp-isa-0000

Adapter: ISA adapter

Physical id 0:  +80.0°C  (high = +86.0°C, crit = +100.0°C)

Core 0:         +80.0°C  (high = +86.0°C, crit = +100.0°C)

Core 1:         +78.0°C  (high = +86.0°C, crit = +100.0°C)

Core 2:         +79.0°C  (high = +86.0°C, crit = +100.0°C)

Core 3:         +77.0°C  (high = +86.0°C, crit = +100.0°C)

Mon Oct 27 12:36:38 CET 2014

LOAD: 4 100%

root@exflutcadev1:~# sensors

coretemp-isa-0000

Adapter: ISA adapter

Physical id 0:  +90.0°C  (high = +86.0°C, crit = +100.0°C)

Core 0:         +90.0°C  (high = +86.0°C, crit = +100.0°C)

Core 1:         +89.0°C  (high = +86.0°C, crit = +100.0°C)

Core 2:         +88.0°C  (high = +86.0°C, crit = +100.0°C)

Core 3:         +87.0°C  (high = +86.0°C, crit = +100.0°C)

Mon Oct 27 12:40:03 CET 2014

LOAD: 4 100%

root@exflutcadev1:~# sensors

coretemp-isa-0000

Adapter: ISA adapter

Physical id 0:  +93.0°C  (high = +86.0°C, crit = +100.0°C)

Core 0:         +93.0°C  (high = +86.0°C, crit = +100.0°C)

Core 1:         +92.0°C  (high = +86.0°C, crit = +100.0°C)

Core 2:         +91.0°C  (high = +86.0°C, crit = +100.0°C)

Core 3:         +91.0°C  (high = +86.0°C, crit = +100.0°C)

Fanunit chanced (old Version)

max:

root@exflutcadev1:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +84.0°C  (high = +86.0°C, crit = +100.0°C)
Core 0:         +84.0°C  (high = +86.0°C, crit = +100.0°C)
Core 1:         +81.0°C  (high = +86.0°C, crit = +100.0°C)
Core 2:         +80.0°C  (high = +86.0°C, crit = +100.0°C)
Core 3:         +80.0°C  (high = +86.0°C, crit = +100.0°C)
 

2:

Temp. Air: 19,2 C

Cooling 90%

Adapter: ISA adapter

Physical id 0:  +38.0°C  (high = +86.0°C, crit = +100.0°C)

Core 0:         +37.0°C  (high = +86.0°C, crit = +100.0°C)

Core 1:         +28.0°C  (high = +86.0°C, crit = +100.0°C)

Core 2:         +29.0°C  (high = +86.0°C, crit = +100.0°C)

Core 3:         +37.0°C  (high = +86.0°C, crit = +100.0°C)

After 100sec. Load 12.0

Adapter: ISA adapter

Physical id 0:  +95.0°C  (high = +86.0°C, crit = +100.0°C)

Core 0:         +94.0°C  (high = +86.0°C, crit = +100.0°C)

Core 1:         +95.0°C  (high = +86.0°C, crit = +100.0°C)

Core 2:         +91.0°C  (high = +86.0°C, crit = +100.0°C)

Core 3:         +91.0°C  (high = +86.0°C, crit = +100.0°C)

Temp. Air 19,2 C

Cooling 100%

Adapter: ISA adapter

Physical id 0:  +38.0°C  (high = +86.0°C, crit = +100.0°C)

Core 0:         +37.0°C  (high = +86.0°C, crit = +100.0°C)

Core 1:         +27.0°C  (high = +86.0°C, crit = +100.0°C)

Core 2:         +29.0°C  (high = +86.0°C, crit = +100.0°C)

Core 3:         +37.0°C  (high = +86.0°C, crit = +100.0°C)

After 100sec. Load 12.0

Adapter: ISA adapter

Physical id 0:  +97.0°C  (high = +86.0°C, crit = +100.0°C)

Core 0:         +97.0°C  (high = +86.0°C, crit = +100.0°C)

Core 1:         +97.0°C  (high = +86.0°C, crit = +100.0°C)

Core 2:         +96.0°C  (high = +86.0°C, crit = +100.0°C)

Core 3:         +92.0°C  (high = +86.0°C, crit = +100.0°C)

MCH Configuration:

nat> mch

INFO - MCH configuration CFG V2.15 for V2.15f Engineering (15:04:42 Sep  9 2014) ok

MCH global parameter:

---------------------

remote interfaces:

  RMCP access:                         enabled

  telnet access:                       enabled

  WEB access:                          enabled

IP address source Mgmt:                board configuration

RMCP session activity timeout minutes: 0 min

RMCP session activity timeout seconds: 60 sec

default fan level:                     100 percent

MCH configuration flags:

  Enable backward compatibility V2.4:  yes

  Enable alternative cooling scheme:   no

  Control rear transition module fans: yes

  Enable Telnet inact timeout (600s):  no

Shelf manager parameter:

------------------------

ShM configuration flags:

  allow shelf FRU invalid:             yes

  temperature management:              enabled

  emergency shutdown:                  disabled

  send SEND_MSG confirmation to SMS:   no

  use external shelf manager:          no

Carrier manager parameter:

--------------------------

carrier number default:                0

quiesced event timeout:                10 sec

CM configuration flags:

  allow carrier FRU invalid:           yes

  overrule carrier FRU:                no

  shutdown system if MCH goes down:    no

  enable Clock E-keying:               no

CM debug:

  IPMI:                                disabled

  FRU:                                 disabled

  E-keying:                            disabled

  sensor:                              disabled

  event:                               disabled

  power module:                        disabled

  cooling unit:                        disabled

  CM/ShM interface:                    disabled

  debugging FRU:                       0

SEL parameter:

--------------

SEL configuration flags:

  'keep on read':                      disabled

  allocate SEL in non-volatile RAM:    yes

  ignore 'version change' sensor:      yes

Ethernet switch parameter:

--------------------------

 configuration source:  load from FLASH

 ignore backplane FRU info:            no

CLK module parameter:

---------------------

 CLK module configuration source:      load from FLASH

PCIe parameter:

---------------

PCIe Virtual Switch configuration

change via web-interface

 VS # | Host   | NT-Host | Members

  0     AMC01_4  none      AMC01_4 AMC02_4 AMC03_4 AMC04_4 AMC05_4

  1

  2

  3

  4

  5

Upstream slot power up delay:          15 sec

PCIe hot plug delay for AMCs:          10 sec

PCIe configuration flags:

  100 MHz spread spectrum:             disabled

  hot plug support:                    enabled

  PCIe early ekey (before payload):    enabled

  'no ekey' for PCIe:                  disabled

  PCIe clustering:                     enabled

Time Protocol/SNTP parameter:

--------------

Time server IP:                        131.169.40.65

'Check for Time' delay minutes:        0 min

'Check for Time' delay hours:          0 h

local time offset:                     2 h

Configuration flags:

  Time client:                         enabled

  Time client protocol:                Time Protocol

DHCP Configuration:

-------------------

host name:                             ▒

flags:                                 0x00

nat>

FRU Information:

----------------

 FRU  Device  State  Name

==========================================

  0   MCH      M4    NMCH-CM

  3   mcmc1    M4    NAT-MCH-MCMC

  6   AMC2     M4    VT AMC725

 40   CU1      M4    Schroff uTCA CU

 50   PM1      M4    PM1 GW V20

 60   Clk1     M4    MCH-Clock

 61   Hub1     M4    MCH-PCIe

==========================================

---------------------------------------

FRU Info for device 6:

---------------------------------------

Common Header    : 0x01 0x00 0x00 0x01 0x11 0x21 0x00 0xcc

---------------------------------------

Internal Use Area : -

---------------------------------------

Chassis Info Area : -

---------------------------------------

Board Info Area          : at offs=8, len=128

Manufacturer(08)         : VadaTech

Board Name(03)           : AMC

Serial Number(07)        : 1940445

Part Number(06)          : AMC725

FRU file ID(11)          : MgtCtrl.bin

Customer Info-0 (04)     : 3725

---------------------------------------

Product Info Area        : at offs=136, len=128

Manufacturer(08)         : VadaTech

Product Name(03)         : AMC

Product Number(06)       : AMC725

Part Version(05)         : 03.40

Product Serial Number(07): 1940445

Asset Tag(00)            :  -

FRU file ID(00)          :  -

Customer Info-0 (04)     : 5D32

---------------------------------------

Multi Record Area  : at offs=264

Record(0): Type ID=0xc0, PICMG Record ID=0x01, offset=0x000, len=42

Header=buf 0x41c2bdd8 len 5

 c0 02 25 80 99

Data  =buf 0x41c2bddd len 37

 32 5d 00 01 00 ff ee dd   cc bb aa 99 88 77 66 55

 44 33 22 11 00 00 11 22   33 44 55 66 77 88 99 aa

 bb cc dd ee ff

Record(1): Type ID=0xc0, PICMG Record ID=0x16, offset=0x02a, len=11

Module Current Requirements Record:

    Current Draw: 5.5 A

Record(2): Type ID=0xc0, PICMG Record ID=0x19, offset=0x035, len=37

AMC Point-to-Point record:

AMC Slot  2, OEM GUID Count = 0

    Record Type = AMC, len=37

    Channel Descriptor count = 8

    Channel(0): Port[0 1 - -]

    Channel(1): Port[4 5 6 7]

    Channel(2): Port[4 5 - -]

    Channel(3): Port[4 - - -]

    Channel(4): Port[8 9 10 11]

    Channel(5): Port[8 9 - -]

    Channel(6): Port[8 - - -]

    Channel(7): Port[2 3 - -]

    Link Descriptors: size=0

Record(3): Type ID=0xc0, PICMG Record ID=0x19, offset=0x05a, len=18

AMC Point-to-Point record:

AMC Slot  2, OEM GUID Count = 0

    Record Type = AMC, len=18

    Channel Descriptor count = 0

    Link Descriptors: size=5

    Link 0 of Channel 0: lanes[0..3]=[1000], Eth ,  1000Base-BX, Grp=0x0, Match=0x0

Record(4): Type ID=0xc0, PICMG Record ID=0x19, offset=0x06c, len=18

AMC Point-to-Point record:

AMC Slot  2, OEM GUID Count = 0

    Record Type = AMC, len=18

    Channel Descriptor count = 0

    Link Descriptors: size=5

    Link 0 of Channel 0: lanes[0..3]=[0100], Eth ,  1000Base-BX, Grp=0x0, Match=0x0

Record(5): Type ID=0xc0, PICMG Record ID=0x19, offset=0x07e, len=73

AMC Point-to-Point record:

AMC Slot  2, OEM GUID Count = 0

    Record Type = AMC, len=73

    Channel Descriptor count = 0

    Link Descriptors: size=60

    Link 0 of Channel 1: lanes[0..3]=[1111], PCIe,  Gen 2, no SSC, Grp=0x0, Match=0x2

    Link 1 of Channel 1: lanes[0..3]=[1111], PCIe,  Gen 2, SSC, Grp=0x0, Match=0x2

    Link 2 of Channel 1: lanes[0..3]=[1111], PCIe,  Gen 1, no SSC, Grp=0x0, Match=0x2

    Link 3 of Channel 1: lanes[0..3]=[1111], PCIe,  Gen 1, SSC, Grp=0x0, Match=0x2

    Link 4 of Channel 2: lanes[0..3]=[1100], PCIe,  Gen 2, no SSC, Grp=0x0, Match=0x2

    Link 5 of Channel 2: lanes[0..3]=[1100], PCIe,  Gen 2, SSC, Grp=0x0, Match=0x2

    Link 6 of Channel 2: lanes[0..3]=[1100], PCIe,  Gen 1, no SSC, Grp=0x0, Match=0x2

    Link 7 of Channel 2: lanes[0..3]=[1100], PCIe,  Gen 1, SSC, Grp=0x0, Match=0x2

    Link 8 of Channel 3: lanes[0..3]=[1000], PCIe,  Gen 2, no SSC, Grp=0x0, Match=0x2

    Link 9 of Channel 3: lanes[0..3]=[1000], PCIe,  Gen 2, SSC, Grp=0x0, Match=0x2

    Link 10 of Channel 3: lanes[0..3]=[1000], PCIe,  Gen 1, no SSC, Grp=0x0, Match=0x2

    Link 11 of Channel 3: lanes[0..3]=[1000], PCIe,  Gen 1, SSC, Grp=0x0, Match=0x2

Record(6): Type ID=0xc0, PICMG Record ID=0x19, offset=0x0c7, len=73

AMC Point-to-Point record:

AMC Slot  2, OEM GUID Count = 0

    Record Type = AMC, len=73

    Channel Descriptor count = 0

    Link Descriptors: size=60

    Link 0 of Channel 4: lanes[0..3]=[1111], PCIe,  Gen 2, no SSC, Grp=0x0, Match=0x2

    Link 1 of Channel 4: lanes[0..3]=[1111], PCIe,  Gen 2, SSC, Grp=0x0, Match=0x2

    Link 2 of Channel 4: lanes[0..3]=[1111], PCIe,  Gen 1, no SSC, Grp=0x0, Match=0x2

    Link 3 of Channel 4: lanes[0..3]=[1111], PCIe,  Gen 1, SSC, Grp=0x0, Match=0x2

    Link 4 of Channel 5: lanes[0..3]=[1100], PCIe,  Gen 2, no SSC, Grp=0x0, Match=0x2

    Link 5 of Channel 5: lanes[0..3]=[1100], PCIe,  Gen 2, SSC, Grp=0x0, Match=0x2

    Link 6 of Channel 5: lanes[0..3]=[1100], PCIe,  Gen 1, no SSC, Grp=0x0, Match=0x2

    Link 7 of Channel 5: lanes[0..3]=[1100], PCIe,  Gen 1, SSC, Grp=0x0, Match=0x2

    Link 8 of Channel 6: lanes[0..3]=[1000], PCIe,  Gen 2, no SSC, Grp=0x0, Match=0x2

    Link 9 of Channel 6: lanes[0..3]=[1000], PCIe,  Gen 2, SSC, Grp=0x0, Match=0x2

    Link 10 of Channel 6: lanes[0..3]=[1000], PCIe,  Gen 1, no SSC, Grp=0x0, Match=0x2

    Link 11 of Channel 6: lanes[0..3]=[1000], PCIe,  Gen 1, SSC, Grp=0x0, Match=0x2

Record(7): Type ID=0xc0, PICMG Record ID=0x19, offset=0x110, len=18

AMC Point-to-Point record:

AMC Slot  2, OEM GUID Count = 0

    Record Type = AMC, len=18

    Channel Descriptor count = 0

    Link Descriptors: size=5

    Link 0 of Channel 7: lanes[0..3]=[1000], SATA,  LinkTExt=[1000], Grp=0x0, Match=0x2

Record(8): Type ID=0xc0, PICMG Record ID=0x19, offset=0x122, len=18

AMC Point-to-Point record:

AMC Slot  2, OEM GUID Count = 0

    Record Type = AMC, len=18

    Channel Descriptor count = 0

    Link Descriptors: size=5

    Link 0 of Channel 7: lanes[0..3]=[0100], SATA,  LinkTExt=[1000], Grp=0x0, Match=0x2

---------------------------------------

1.  IPMI tool cannot write fru file from the same exflutca3 but from all the other PC's.

2. Only NATview 2.4  fru editor is compatible.

jddd.desy.de -> java web start -> jddd-run.jnlp

FLASH -> Overfiew -> SubPanels -> select_apps_on_crates.xml "open"

TAB "LAB XFEL"

"PLEASE DO NOT TOUCH TAB 28D"

work only with AER19!!

lterm is  a tool for ssh, scp, telnet and ftp. It shows all sessions in one Terminal with reiter. If change some thing on a hidden window he change the colure from the window name.

Next feature are that you does not need e second window for sftp. This lterm can also start all connections at startup again.

ADQ108 is upgraded to latest version of firmware which is 21-01-03-00 R15644. In this version new feature which is trigger counter is added. this counter counts triggers and updates reg10 with this number. It is possible to reset this counter.

exflutca6 shows at the base consumption

355W include PS, MCH,  CPU (SSD)  Fan's (default fan level 30%)

376W includes PS, MCH, (CPU (100%)), Fans's 100% level.

380W includes PS, MCH, (CPU, SSD (100%)), Fan's 100% level.

515W inclues PS, MCH, (CPU, SSD (100%)), Fan's 100% level and 8x ADQ412-4G-MTCA.

 exflutcawp74

109W includes PS, MCH (SSD) Fan' (default fan level 60%)

All modules are upgraded to latest version. In this version only SP-Devices core is changed. Version is 16600 which DRAM writting problem is solved.

BIOS Version 3.06.01

CPU: I7-3555LE

Boot Features

Delay Before Boot <5 Seconds>

Avanced -> IPMI -> IPMI LAN

Enabled

ETH2

192.168.81.xxx

Static

Mask 3x 255, 1x 0

Gatew. 192.168.81.16

IPMI SOL <Enabled>

Terminal Type <PC_ANSI>

Boud Rate <115200>

Data Bits <8>

Partity <None>

Stop Bits <1>

Flow Control <None>

Boot

Boot Type <Legacy Boot Type>

USB Boot <Enabled>

Legacy

Boot Type Order

USB

Hard Disk Drive

INFO - MCH configuration CFG V2.14 for V2.14.1 Final (15:39:47 Jul 25 2013) ok

MCH global parameter:
---------------------
remote interfaces:
  RMCP access:                         enabled
  telnet access:                       enabled
  WEB access:                          enabled
IP address source Mgmt:                board configuration
RMCP session activity timeout minutes: 0 min
RMCP session activity timeout seconds: 60 sec
default fan level:                     30 percent
MCH configuration flags:
  Enable backward compatibility V2.4:  no
  Enable alternative cooling scheme:   no
  Control rear transition module fans: no
  Enable Telnet inact timeout (600s):  no

Shelf manager parameter:
------------------------
ShM configuration flags:
  allow shelf FRU invalid:             yes
  temperature management:              enabled
  emergency shutdown on critical ev.:  disabled
  emergency shutdown on non recov ev.: disabled
  send SEND_MSG confirmation to SMS:   no
  use external shelf manager:          no

Carrier manager parameter:
--------------------------
carrier number default:                0
quiesced event timeout:                10 sec
CM configuration flags:
  allow carrier FRU invalid:           yes
  overrule carrier FRU:                no
  shutdown system if MCH goes down:    no
  enable Clock E-keying:               no

CM debug:
  IPMI:                                disabled
  FRU:                                 disabled
  E-keying:                            disabled
  sensor:                              disabled
  event:                               disabled
  power module:                        disabled
  cooling unit:                        disabled
  CM/ShM interface:                    disabled
  debugging FRU:                       0

SEL parameter:
--------------
SEL configuration flags:
  'keep on read':                      disabled
  allocate SEL in non-volatile RAM:    yes
  ignore 'version change' sensor:      yes

Ethernet switch parameter:
--------------------------
 configuration source:  load from FLASH
 ignore backplane FRU info:            no

CLK module parameter:
---------------------
 CLK module configuration source:      load from FLASH

PCIe parameter:
---------------
PCIe Virtual Switch configuration
change via web-interface
 VS # | Host | NT-Host | AMC1 AMC2 AMC3 AMC4 AMC5 AMC6 AMC7 AMC8 AMC9 AMC10 AMC11 AMC12
  0     01     none        X    X    X    X    X    X    X    X    X    X     X     X
  1
  2
  3
  4
  5
Upstream slot power up delay:          15 sec
PCIe power up delay for AMC:           10 sec
PCIe configuration flags:
  100 MHz spread spectrum:             disabled
  hot plug support:                    enabled
  PCIe early ekey (before payload):    enabled
  PCIe clustering:                     enabled

NTP parameter:
--------------
NTP server IP:                         131.169.40.65
NTP 'check for time' delay minutes:    0 min
NTP 'check for time' delay hours:      0 h
NTP local time offset:                 2 h
NTP configuration flags:
  NTP client:                          enabled
  NTP client protocol:                 Time Protocol

DHCP Configuration:
-------------------
host name:                             <empty>
flags:                                 0x00
 

One module inside crate is upgraded to new version of SP-Devices firmware. There was a noise on ADC data which is solved in latest version of firmware.

All seven borads inside crate are upgraded to version 21-01-03-A R14958

final the setup and configuration on exflutcawp74 are done.

"hddtemp" does not work with the new drive from SAMSUNG.

sudo echo '"Samsung SSD 840 EVO 120G B" 190 C "Samsung SSD 840 EVO 120GB"' >> /etc/hddtemp.db

clear_measuring_20140901.sh

#!/bin/bash
/usr/bin/find /measuring_20140901/ -cmin -60 -cmin +50 -type f -print | /usr/bin/xargs /bin/rm -f
 

script measuring-sync on exflutca4 installed and started 5 seconds after a boot.

#!/bin/bash
while :
do
/usr/bin/nice -n 19 /usr/bin/rsync -rlpgoDu --exclude="*.part" /measuring_20140901/ -e ssh exflserv04:/diskmnt/b/scratch/utcaadm/exflutca4/measuring_20140901
sleep 5
done
 

Now ntp and Hotplug looks like good.

Upstream slot power up delay:          15 sec

PCIe power up delay for AMC:           10 sec

PCIe configuration flags:

   100 MHz spread spectrum:             disabled

   hot plug support:                    enabled

   PCIe early ekey (before payload):    enabled

   PCIe clustering:                     enabled

DOOCS server for x2timer has been updated to 2.10 by Chr. Stechmann.

I attached a list from apparent what tools will be needed for a laser measuring setup.

I installed the NAT View 2.16 on the exflutcadev. If you want to work with natview please open a terminal (xwindows) and type in "natview.sh".

Frank

License Key:

032837242611146e050c11004f162223240c105e4f0c0504014653435f646c717f5f505d5d6472777d5f50434012066c0f39355f27040e6c1e2a223c4210160c1d

exflutca3: The DMA Resets floating the root Disk it was no space left.

ToDo:

Ssh connect to the client.

df –h ….    /dev/sda1  /  100%    (no Space left)

search the biggest Files with: du –sh /tmp or du –sh /var/ and so on

you find (explain) /var/log/messages 36GB.

You cannot delete this file because for this he also need a little bit space.

The next step is to shrink the reserved space.

sudo tune2fs –m 1 /dev/sda1

this will shrink the reserved space from 5% to 1% now you have enough space to delete the file messages.

After this you should reserve the space again from 1 to 5% (sudo tune2fs –m 2 /dev/sda1).

All ADQ boards are upgraded to new Firmware. The version is 01.01.00-R14958 . R14958 is the version of SP-Devices core. In this firmware some error reporting flags are added and some measuring values are added to protocol header. Inside register(2) three flags are added for LVDS_Clk, TID and Trigger signal persence. When each of them is high that means the corresponding signal exists. Inside the packet other flags such as TID Error, TID packet Frame error, TID packet parity error and TID packet CRC error are added. Three different measurment counters are added one of them is 32-bit counter that counts number of processing clock cycles between two consecutive trigger signal. Second counter which is 32-bit counter  counts number of processing clock cycles between each TID signal and following Trigger signals. This counter starts from zero after each TID valid signals. Third and last counter is eight-bit counter that counts number of trigger signals between each two consecutive TID signals.

The FLASH of the DAMC2 could be upgraded via different ways:

1. JTAG Cable

2. MMC via IPMI and HPM

3. JTAG Player through the FPGA

4. JTAG Interface on the Backplane

In order to upgrade the f/w via the JTAG Player (3), the MMC has to configure the JTAG chain in order to connect the JTAG Player of the FPGA to the chain. This is acomplished by using the impmitool in the following way:

ipmitool -I lan -H exflutca7-mch.desy.de -P "" -t 0x7A raw 0x30 0x03 0x01

(some fields have to be replaced by the correct mch address and the slot fru number - see other log entry about this)

Now the pcie_jtag_player tool could be used.

Independent of the method used, the FLASH memory supports up to two f/w revisions in one image. A nice side effect is, that revision 1 could be erased and reprogrammed without touching the revision 0. It could therefore serve as a failsave version after a broken f/w upgrade of revision 1. In order to select the desired one, the ipmitool again could be used. In this case the command is for revision 0:

ipmitool -I lan -H exflutca7-mch.desy.de -P "" -t 0x7A raw 0x30 0x01 0x03

And for revision 1 it is:

ipmitool -I lan -H exflutca7-mch.desy.de -P "" -t 0x7A raw 0x30 0x01 0x02

After upgrades and switching revisions a could reset of the AMC is required!

I upgraded the Power Supply from 2.17 to 2.19.

I bring up MCH FW to 2.14.3 Final to utcafxe.

I bring up MCH FW to 2.14.3 Final to utca7

I bring up MCH FW to 2.14.3 Final to utca5

I bring up MCH FW to 2.14.3 Final to utca4

I bring up MCH FW to 2.14.3 Final to utca3

I bring up MCH FW to 2.14.3 Final to utca1

This version fixes issues with the bunch pattern generation and decoding

In order to upgrade x2timer f/w, the s/w had to be upgraded to latest version

x11vnc-server installed and started with"x11vnc -find -forever &" It comes up with default port 5900

client started on windows whit "exflpcx18801::5900"

The setup and configuration from exflutca1 are done.

config added in /etc/samba/smb.conf

[exfllabpc1]
path = /devhome/exfllabpc1
public = yes
writable = yes
 

user added for samba:

smbpasswd -a utcaadm

I see man i/o waits on exflutca6 at the test time:

Tasks: 118 total,   2 running, 116 sleeping,   0 stopped,   0 zombie
Cpu0  :  0.0%us,  0.3%sy,  0.0%ni, 25.7%id, 74.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu1  :  0.7%us,  0.3%sy,  0.0%ni, 99.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu2  :  0.0%us,  0.7%sy,  0.0%ni, 99.3%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Cpu3  :  0.3%us,  0.0%sy,  0.0%ni, 99.7%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0%st
Mem:   3970748k total,  3761900k used,   208848k free,   177372k buffers
Swap:  4114428k total,        0k used,  4114428k free,  3046240k cached
 

I changed the nice value from (ganglia) gmond + gmeta from "0" to "-10" and stoped the irqbalancer.

Updated ADQ drivers from ADQ_SDK_linux_r15020.

Commands to install were:

1. dpkg -i spd-adq-pci-dkms-...deb
2. dpkg -i libadq0_...deb
3. dpkg -i adqupdater...deb
4. reboot

Updated ADQ drivers from ADQ_SDK_linux_r15020.

Commands to install were:

1. dpkg -i spd-adq-pci-dkms-...deb
2. dpkg -i libadq0_...deb
3. dpkg -i adqupdater...deb
4. chgrp adq /dev/adq*
5. chmod g+rw /dev/adq*
6. reboot
7. adduser abeckman adq

Step 7 needs only to be done once, so if you did this already before for your account, you can leave it out here.

Steps 4 and 5 is only necessary, if dpkg does not handle this correctly. Pls check file permissions of /dev/adq* after installation..

After full power cut, the MCH had no PCIe communication enabled. It has to be checked, if this is always the case and then to be seen why this is the case.

I added the DOOCS watchdog to the central ENS servers and set X2Timer Server to online state in order to automatically start the x2timer server after reboot/

TDC core is attached to the project and a simple protocol implemented inside the hardware to transmit data via PCIe to PC.

It is possible to set device in interleaved or non-interleaved mode.

I upgraded the x2timer_server to the latest version to make sure it is compatible with the latest f/w version (see other entry). It is now started and running fine and enabled in watchdog.

Upgraded x2timer module to latest version (1.9.1) via the DOOCS control system device server. Afterwards I shut it down and restarted it via the MCH. Works fine.

Power Supply on exflutca5 changed SN: old 0713001 (1KW) new: 03140021 (1KW)

New PS has the new F/W Version 2.17 old 2.0

Power Supply on exflutca5 changed SN: old 0713018 (600W) new: 03140019 (1KW)

New PS has the new F/W Version 2.17

ipmitool -H exflutca5-mch -P "" -t 0xc4 fru read 0 telkoor-900-1142-0000.hex

ipmitool -H exflutca5-mch -P "" -t 0xc4 hpm upgrade Telkoor_PM_V217_woCurrent.hpm

PM1: 0xc2

PM2: 0xc4

PM3: 0xc6

PM4: 0xc8

(ipmitool -H exflutca5-mch -P "" -t 0xc4 fru write 0 telkoor-900-1142-0000.hex)

ipmitool -H exflutca5-mch -P "" -t 0xc4 hpm activate

ipmitool -H exflutca5-mch1 -P "" -t 0xc4 mc info

MCH:

show_fru

show_fruinfo 51

show_sensorinfo 51

In order to debug Karabo devices during development, the following package has been installed:

• GNU debugger (gdb)

exflutcafxe are on the same level as the other crates.

I replaced monitorix by ganglia on all crates (exflutca3, 4, 5, 6, wp78 and fxe).

In the configfile "/etc/init/portmap.conf" I change the option from "-w" to "-i -w" on all crates, now the x2timer comes up.

I corrected the restict to:

"restrict 127.0.0.1"
"restrict ::1"
 

Apr 11 06:03:50 exflutcadev dhclient: DHCPREQUEST of 192.168.81.200 on eth0 to 131.169.40.232 port 67
Apr 11 06:03:50 exflutcadev dhclient: DHCPACK of 192.168.81.200 from 131.169.40.232
Apr 11 06:03:50 exflutcadev ntpd[17718]: ntpd exiting on signal 15
Apr 11 06:03:52 exflutcadev ntpd[23012]: ntpd 4.2.6p3@1.2290-o Tue Jun  5 20:12:08 UTC 2012 (1)
Apr 11 06:03:52 exflutcadev ntpd[23013]: proto: precision = 0.163 usec
Apr 11 06:03:52 exflutcadev ntpd[23013]: line 37 column 13 syntax error, unexpected T_Ignore, expecting T_String
Apr 11 06:03:52 exflutcadev ntpd[23013]: syntax error in /var/lib/ntp/ntp.conf.dhcp line 37, column 13
Apr 11 06:03:52 exflutcadev ntpd[23013]: line 38 column 13 syntax error, unexpected T_Ignore, expecting T_String
Apr 11 06:03:52 exflutcadev ntpd[23013]: syntax error in /var/lib/ntp/ntp.conf.dhcp line 38, column 13
Apr 11 06:03:52 exflutcadev ntpd[23013]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Apr 11 06:03:52 exflutcadev ntpd[23013]: Listen and drop on 1 v6wildcard :: UDP 123
Apr 11 06:03:52 exflutcadev ntpd[23013]: Listen normally on 2 lo 127.0.0.1 UDP 123
Apr 11 06:03:52 exflutcadev ntpd[23013]: Listen normally on 3 eth0 192.168.81.200 UDP 123
Apr 11 06:03:52 exflutcadev ntpd[23013]: peers refreshed
Apr 11 06:03:52 exflutcadev ntpd[23013]: Listening on routing socket on fd #20 for interface updates
Apr 11 06:03:52 exflutcadev dhclient: bound to 192.168.81.200 -- renewal in 300948 seconds.
Apr 11 06:08:00 exflutcadev ntpd[23013]: ntpd exiting on signal 15
Apr 11 06:08:02 exflutcadev ntpd[24562]: ntpd 4.2.6p3@1.2290-o Tue Jun  5 20:12:08 UTC 2012 (1)
Apr 11 06:08:02 exflutcadev ntpd[24563]: proto: precision = 0.105 usec
Apr 11 06:08:02 exflutcadev ntpd[24563]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123
Apr 11 06:08:02 exflutcadev ntpd[24563]: Listen and drop on 1 v6wildcard :: UDP 123
Apr 11 06:08:02 exflutcadev ntpd[24563]: Listen normally on 2 lo 127.0.0.1 UDP 123
Apr 11 06:08:02 exflutcadev ntpd[24563]: Listen normally on 3 eth0 192.168.81.200 UDP 123
Apr 11 06:08:02 exflutcadev ntpd[24563]: peers refreshed
Apr 11 06:08:02 exflutcadev ntpd[24563]: Listening on routing socket on fd #20 for interface updates
 

On exflutca 3, 4, 5, 6 and 7 I put in the line:

/dev/sda -a -o on -S on -s (S/../.././03|L/../../6/03) -m root -M exec /usr/share/smartmontools/smartd-runner

to /etc/smartd.conf and started the smartd server.

and coment out the line:  start_smartd=yes

in: /etc/defaults/smartmontools

Messages from today.

Apr  8 11:01:13 frank-pczW0712 kernel: [86807.520045] EXT4-fs (sdc1): error count: 13

Apr  8 11:01:13 frank-pczW0712 kernel: [86807.520052] EXT4-fs (sdc1): initial error at 1396349073: ext4_reserve_inode_write:4483

Apr  8 11:01:13 frank-pczW0712 kernel: [86807.520057] EXT4-fs (sdc1): last error at 1396353000: ext4_remount:4576

Smartmontools shows a lot of read and ECC failures, but after one hour self test it shows  no error.

.......

SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE

  1 Raw_Read_Error_Rate     0x000f   074   063   044    Pre-fail  Always       -       156219000

  3 Spin_Up_Time            0x0003   099   099   000    Pre-fail  Always       -       0

  4 Start_Stop_Count        0x0032   100   100   020    Old_age   Always       -       62

  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0

  7 Seek_Error_Rate         0x000f   070   060   030    Pre-fail  Always       -       34453485116

  9 Power_On_Hours          0x0032   090   090   000    Old_age   Always       -       9002

 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail  Always       -       0

 12 Power_Cycle_Count       0x0032   100   037   020    Old_age   Always       -       62

184 End-to-End_Error        0x0032   100   100   099    Old_age   Always       -       0

187 Reported_Uncorrect      0x0032   098   098   000    Old_age   Always       -       2

188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       0

189 High_Fly_Writes         0x003a   100   100   000    Old_age   Always       -       0

190 Airflow_Temperature_Cel 0x0022   067   064   045    Old_age   Always       -       33 (Min/Max 25/34)

194 Temperature_Celsius     0x0022   033   040   000    Old_age   Always       -       33 (0 20 0 0)

195 Hardware_ECC_Recovered  0x001a   021   016   000    Old_age   Always       -       156219000

197 Current_Pending_Sector  0x0012   100   100   000    Old_age   Always       -       0

198 Offline_Uncorrectable   0x0010   100   100   000    Old_age   Offline      -       0

199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age   Always       -       0

SMART Error Log Version: 1

ATA Error Count: 2

        CR = Command Register [HEX]

        FR = Features Register [HEX]

        SC = Sector Count Register [HEX]

        SN = Sector Number Register [HEX]

        CL = Cylinder Low Register [HEX]

        CH = Cylinder High Register [HEX]

        DH = Device/Head Register [HEX]

        DC = Device Command Register [HEX]

        ER = Error register [HEX]

        ST = Status register [HEX]

Powered_Up_Time is measured from power on, and printed as

DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,

SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 2 occurred at disk power-on lifetime: 6383 hours (265 days + 23 hours)

  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 00 d7 b0 a4 00  Error: UNC at LBA = 0x00a4b0d7 = 10793175

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  25 d0 f8 80 b0 a4 e0 00  20d+08:56:43.218  READ DMA EXT

  25 d0 f8 88 af a4 e0 00  20d+08:56:43.210  READ DMA EXT

  25 d0 10 78 b3 a4 e0 00  20d+08:56:43.195  READ DMA EXT

  25 d0 f8 80 b2 a4 e0 00  20d+08:56:43.136  READ DMA EXT

  25 d0 f8 88 b1 a4 e0 00  20d+08:56:43.010  READ DMA EXT

Error 1 occurred at disk power-on lifetime: 6383 hours (265 days + 23 hours)

  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  40 51 00 d2 b0 a4 00  Error: UNC at LBA = 0x00a4b0d2 = 10793170

  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  25 d0 f8 80 e8 95 e0 00  20d+08:56:31.300  READ DMA EXT

  25 d0 f8 88 e7 95 e0 00  20d+08:56:31.267  READ DMA EXT

  25 d0 10 78 df c0 e0 00  20d+08:56:27.840  READ DMA EXT

  25 d0 f8 80 de c0 e0 00  20d+08:56:27.831  READ DMA EXT

  25 d0 f8 80 e8 b0 e0 00  20d+08:56:23.092  READ DMA EXT

SMART Self-test log structure revision number 1

Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error

# 1  extended offline    completed without error       00%      9002         -

# 2  Short offline       Completed without error       00%      9001         -

# 3  Short offline       Interrupted (host reset)      00%      8834         -

SMART Selective self-test log data structure revision number 1

 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS

    1        0        0  Not_testing

    2        0        0  Not_testing

    3        0        0  Not_testing

    4        0        0  Not_testing

    5        0        0  Not_testing

Selective self-test flags (0x0):

  After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

The epics and doocs package from Karabo requires some Debian packages in order to compile.

• OpenLDAP development (libldap2-dev) [for doocs]
• Readline development (libreadline-dev) [for epics]

Since these are not (yet) part of the Karabo binary release (see bugs #579 and #585), I installed them on the host itself.

the new version 3.5 look's like better to install. Changes to configure are minimal the only "show stopper" -> all collected measurements are gone.

The Master HD (/dev/sda) died with too many bad blocks. I setup and configured a new SSD (SAMSUNG 120GB EVO).

exflutcadev run again.

I installed on the crates 3, 4, 5, 6 and 7 the follow 3 packages:

adqupdater_0.13437_amd64.deb
libadq0_0.13437_amd64.deb
spd-adq-pci-dkms_1.5_all.deb

comment in: udp();
 

put in the follow Lines:
destination d_email_notification { program("/usr/local/bin/logalarm-mail.sh"); };

filter f_exflutca_1 { match("Failed"); };
filter f_exflutca_2 { match("failed"); };
filter f_exflutca_3 { match("ERROR"); };
filter f_exflutca_4 { match("Error"); };
filter f_exflutca_5 { match("error"); };


log { source(s_all); filter(f_exflutca_1); destination(d_email_notification); };
log { source(s_all); filter(f_exflutca_2); destination(d_email_notification); };
log { source(s_all); filter(f_exflutca_3); destination(d_email_notification); };
log { source(s_all); filter(f_exflutca_4); destination(d_email_notification); };
log { source(s_all); filter(f_exflutca_5); destination(d_email_notification); };


cat of logalarm-mail.sh shows:

#!/bin/bash

subject="SYSLOG ALARM from exflutcadev"
email="frank.babies@xfel.eu"

while read event;
do
  echo ${event} | mail -s "${subject}" ${email}
done
 

Installed ADQ drivers from package ADQ_SDK_linux_r13437.tgz

Commands to install were:

1. dpkg -i spd-adq-pci-dkms-...deb
2. dpkg -i adqupdater...deb
3. reboot
4. adduser abeckman adq

"emacs and nedit" installed on all crates.

Now the exflutca4 crate is on the same level as all.

exflutca5 are on the new Ubuntu Version 12.04. Monitoring are also successful installed and configured.

exflutca6 are on the new Ubuntu Version 12.04. Monitoring are also successful installed and configured.

acpi lm-sensors rrdtool perl libwww-perl libmailtools-perl libmime-lite-perl librrds-perl libdbi-perl libxml-simple-perl libhttp-server-simple-perl libconfig-general-perl

and monitorix.

monitorix has been configured on exflpcx18814.desy.de, exflutcadev and exflutca7. Next step is to setup and configure exflutcadev as mail master.

Follow setups has been changed in the /etc/monitorix.conf from:

exflpcx18814.desy.de

************************************************************

title = vm-monster
hostname = frank-pczW0712

<httpd_builtin>
        enabled = y
        user = root
        group = root
        hosts_deny = all
        hosts_allow = all
</httpd_builtin>

# Graphs (de)activation  (ALL OTHER ENTRIES ARE "N")
# -----------------------------------------------------------------------------
<graph_enable>
        system          = y
        kern            = y
        proc            = y
        hptemp          = n
        lmsens          = y
        nvidia          = n
        disk            = y
        fs              = y
        net             = y
        ntp             = y
        int             = y
</graph_enable>

# KERN graph (ALL OTHER ENTRIES ARE "N")

# -----------------------------------------------------------------------------
<kern>
        graph_mode = r
        <list>
                steal   = n
                guest   = n
        </list>
        rigid = 2
        limit = 100
</kern>


# PROC graph (ALL OTHER ENTRIES ARE OUT COMMENTED OUT)
# -----------------------------------------------------------------------------
<proc>
        max = 4
</proc>

<lmsens>
        <list>
                core0   = Core 0
                core1   = Core 1
                core2   = Core 2
                core3   = Core 3
        </list>
</lmsens>
# DISK graph
# -----------------------------------------------------------------------------
<disk>
        <list>
                0 = /dev/sda, /dev/sdb
        </list>

# Multihost
# -----------------------------------------------------------------------------
<multihost>
        enabled = y
        footer_url = y
        graphs_per_row = 2
        remotehost_list = exflutcadev, vm-monster, exflutca7
        <remotehost_desc>
                0 = http://exflutcadev:8080,/monitorix,/monitorix-cgi
                1 = http://131.169.212.245:8080,/monitorix,/monitorix-cgi
                2 = http://exflutca7:8080,/monitorix,/monitorix-cgi
        </remotehost_desc>
        groups = n
        remotegroup_list = My Group
        <remotegroup_desc>
                0 = server 2, server 3
        </remotegroup_desc>
</multihost>

exflutca7.desy.de:

title = exflutca7
hostname = exflutca7

<httpd_builtin>
        enabled = y
        user = root
        group = root
        hosts_deny = all
        hosts_allow = all
</httpd_builtin>

<graph_enable> (ALL OTHER ENTRIES ARE "N")
        system          = y
        kern            = y
        proc            = y
        lmsens          = y
        disk            = y
        fs              = y
        net             = y
        nfss            = y
        nfsc            = y
        ntp             = y
        int             = y
</graph_enable>

# KERN graph (ALL OTHER ENTRIES ARE "Y")
# -----------------------------------------------------------------------------
<kern>
        graph_mode = r
        <list>
                steal   = n
                guest   = n
        </list>
        rigid = 2
        limit = 100
</kern>


# PROC graph
# -----------------------------------------------------------------------------
<proc>
        max = 4
</proc>

<lmsens>  (ALL OTHER ENTRIES ARE OUT COMMENTED OUT)

        <list>
                core0   = Core 0
                core1   = Core 1
                core2   = Core 2
                core3   = Core 3
        </list>
</lmsens>

# DISK graph
# -----------------------------------------------------------------------------
<disk>
        <list>
                0 = /dev/sda
        </list>
        <alerts>
                realloc_enabled = y
                pendsect_enabled = y
        </alerts>
</disk>

 

I found the monitoring tool "monitorix v/3.4.0" and installed them to my work station also on exflutcadev.

http://www.monitorix.org/

This tool shows all information that we needed.

I installed the autofs on Crate 3 + 7 and commented the nfsmount out in the fstab.

I tested the crate 7.

write performance ~ 400MB/s ~52°C

read performance ~ 420MB/s ~47°C

Temp ~ 60°C

root@exflutca7:~# dd if=/dev/zero of=testing.image bs=2MB count=30000
30000+0 records in
30000+0 records out
60000000000 bytes (60 GB) copied, 164.263 s, 365 MB/s
root@exflutca7:~# rm testing.image
root@exflutca7:~# dd if=/dev/zero of=testing.image bs=2MB count=30000
30000+0 records in
30000+0 records out
60000000000 bytes (60 GB) copied, 166.174 s, 361 MB/s
root@exflutca7:~# rm testing.image
root@exflutca7:~# dd if=/dev/zero of=testing.image bs=2MB count=30000
30000+0 records in
30000+0 records out
60000000000 bytes (60 GB) copied, 130.975 s, 458 MB/s
 

05:20:02 PM  CPU    %usr   %nice    %sys %iowait    %irq   %soft  %steal  %guest   %idle
05:20:02 PM  all    6.82    0.00    0.11    0.01    0.00    0.02    0.00    0.00   93.03
Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda              12.15        25.13      5780.36     168959   38861277
/dev/sda1           83G   40G   39G  52% /
190 Airflow_Temperature_Cel 0x0032   051   051   000    Old_age   Always       -       49
Thermal 0: ok, 60.0 degrees C
Thermal 1: ok, 60.0 degrees C

05:25:03 PM  CPU    %usr   %nice    %sys %iowait    %irq   %soft  %steal  %guest   %idle
05:25:03 PM  all   10.52    0.00    0.34    0.01    0.00    0.13    0.00    0.00   89.01
Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda              41.26        37.92     20616.66     266327  144792022
/dev/sda1           83G   31G   48G  39% /
190 Airflow_Temperature_Cel 0x0032   048   048   000    Old_age   Always       -       52
Thermal 0: ok, 60.0 degrees C
Thermal 1: ok, 60.0 degrees C

 

root@exflutca7:~# dd if=testing.image of=/dev/null bs=2MB
30000+0 records in
30000+0 records out
60000000000 bytes (60 GB) copied, 142.503 s, 421 MB/s
root@exflutca7:~# dd if=testing.image of=/dev/null bs=2MB
30000+0 records in
30000+0 records out
60000000000 bytes (60 GB) copied, 142.476 s, 421 MB/s
root@exflutca7:~# dd if=testing.image of=/dev/null bs=2MB
30000+0 records in
30000+0 records out
60000000000 bytes (60 GB) copied, 142.535 s, 421 MB/s
root@exflutca7:~# rm testing.image
 

05:30:01 PM  CPU    %usr   %nice    %sys %iowait    %irq   %soft  %steal  %guest   %idle
05:30:01 PM  all   14.04    0.00    0.42    0.01    0.00    0.18    0.00    0.00   85.35
Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda              48.01        36.92     23833.62     270323  174506440
/dev/sda1           83G   58G   21G  74% /
190 Airflow_Temperature_Cel 0x0032   055   048   000    Old_age   Always       -       45
Thermal 0: ok, 60.0 degrees C
Thermal 1: ok, 60.0 degrees C

Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
sda             167.49     15408.74     22894.91  117446679  174506801
/dev/sda1           83G   58G   21G  74% /
190 Airflow_Temperature_Cel 0x0032   053   048   000    Old_age   Always       -       47
Thermal 0: ok, 60.0 degrees C
Thermal 1: ok, 60.0 degrees C

 

The sshd configuration has been changed about the X forwarding over ssh.

"AddressFamily inet" added to "/etc/ssh/sshd_config".

To gave all exfl_jet Group Members the sudo rights Patrick puted in the Group exfl_jet to the soudoers file.

# All members of the exfl_jet

%exfl_jet            ALL=(ALL:ALL) ALL

I tested the Hardware from "exflutca3" SSD with "dd" and CPU's with "stress"

CPU max 52°C

SSD write 45 C read 42 C

==============================================================

root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   065   063   000    Old_age   Always       -       35
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   065   063   000    Old_age   Always       -       35
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   065   063   000    Old_age   Always       -       35
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   063   063   000    Old_age   Always       -       37
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   062   062   000    Old_age   Always       -       38
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   060   060   000    Old_age   Always       -       40
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   060   060   000    Old_age   Always       -       40
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   059   059   000    Old_age   Always       -       41
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   058   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   057   057   000    Old_age   Always       -       43
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   057   057   000    Old_age   Always       -       43
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   056   056   000    Old_age   Always       -       44
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   056   056   000    Old_age   Always       -       44
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   059   055   000    Old_age   Always       -       41
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   057   055   000    Old_age   Always       -       43
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   056   055   000    Old_age   Always       -       44
190 Airflow_Temperature_Cel 0x0032   056   056   000    Old_age   Always       -       44
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   059   055   000    Old_age   Always       -       41
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   057   055   000    Old_age   Always       -       43
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   056   055   000    Old_age   Always       -       44
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   055   055   000    Old_age   Always       -       45
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   056   055   000    Old_age   Always       -       44
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel

root@exflutca3:~# dd if=/dev/zero of=test-dump.img bs=1M count=50000
50000+0 records in
50000+0 records out
52428800000 bytes (52 GB) copied, 129.748 s, 404 MB/s
root@exflutca3:~# rm test-dump.img
root@exflutca3:~# dd if=/dev/zero of=test-dump.img bs=1M count=50000
50000+0 records in
50000+0 records out
52428800000 bytes (52 GB) copied, 118.758 s, 441 MB/s

190 Airflow_Temperature_Cel 0x0032   060   055   000    Old_age   Always       -       40
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   059   055   000    Old_age   Always       -       41
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   059   055   000    Old_age   Always       -       41
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   059   055   000    Old_age   Always       -       41
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~# smartctl -a /dev/sda | grep Airflow_Temperature_Cel
190 Airflow_Temperature_Cel 0x0032   058   055   000    Old_age   Always       -       42
root@exflutca3:~#

root@exflutca3:~# dd if=test-dump.img of=/dev/null bs=1M
50000+0 records in
50000+0 records out
52428800000 bytes (52 GB) copied, 127.548 s, 411 MB/s
root@exflutca3:~# rm test-dump.img

root@exflutca3:~# fstrim -v /
/: 115965321216 bytes were trimmed
root@exflutca3:~#

CPU bleib bei ~50 . 52C.

 

BIOS settings and HW settings on utca3 cahnged to get a ipmi serial console on the crate.

All other Ubuntu 12.04 settings that are change is documented on ID 59.

I intsalled and setup the gkrellmd to monitoring the exflutca3.

also put in "/etc/gkrellmd.conf" host-allow 192.168.81.* and host-allow 131.169.212.*

smartmontools on crate 3 install to monitoring the ssd.

the SAMSUNG SSD has 128GB with 512 Bit Blocksize MLC Chips. 1 Block of this 25 nano Meter production can be written 3000 times.

It is round about 380TB over 5 Years or 213GB per Day. It should be enough for our projects.

added Groups and users:

groupadd -g 3555 exfel, 5478 exfl_jet

adduser --home /home/username --uid xxx --gid 3555 username

added all or some of them to the group 5478 exfl_jet   "adduser username exfl_jet"

Install:

apt-get install krb5-user libpam-krb5

change the "/etc/krb5.conf"

put in:

[libdefaults]
        default_realm = DESY.DE
        clockskew = 300
        v4_instance_resolve = true
        default_etypes = des-cbc-crc
        default_etypes_des = des-cbc-crc
        krb4_get_tickets = true
        v4_name_convert = {
                host = {
                        rcmd = host
                        ftp  = ftp
                        pop  = pop
                        ldap = ldap
                        imap = imap
                        ldapserver = ldapserver
                }
        }

[realms]
        DESY.DE = {
                kdc = netra32.desy.de
                kdc = netra33.desy.de
                kdc = netra34.desy.de
                admin_server = netra32.desy.de
                default_domain = desy.de
        }
        WIN.DESY.DE = {
                krb4_get_tickets = false
                kdc = adc11.win.desy.de
                kdc = adc12.win.desy.de
                kdc = adc13.win.desy.de
                kdc = adc14.win.desy.de
                kdc = adc15.win.desy.de
                admin_server = adc11.win.desy.de
                default_domain = WIN.DESY.DE
                v4_instance_convert = {
                        desy = desy.de
                        win.desy = win.desy.de
                }
        }
        NAF.DESY.DE = {
                kdc = tcdc1.naf.desy.de
                kdc = tcdc2.naf.desy.de
                kdc = tcdc3.naf.desy.de
                default_domain = naf.desy.de
        }
        IFH.DE = {
                kdc = kdc1.ifh.de
                kdc = kdc2.ifh.de
                kdc = kdc3.ifh.de
                admin_server = kdc1.ifh.de
                default_domain = ifh.de
        }

[domain_realm]
        .desy.de = DESY.DE
        .win.desy.de = WIN.DESY.DE
        .naf.desy.de = NAF.DESY.DE
        .ifh.de = IFH.DE

[appdefaults]

sshd = {
        ticket_lifetime = 86400
        renew_lifetime = 172800
        forwardable = true
        krb4_convert = true
        afs_cells = desy.de
        validate = false
        proxiable = false
        retain_after_close = false
        minimum_uid = 0
}

pam = {
        ticket_lifetime = 86400
        renew_lifetime = 172800
        forwardable = true
        krb4_convert = true
        afs_cells = desy.de
        validate = false
        proxiable = false
        retain_after_close = false
        minimum_uid = 0
}

kinit = {
        ticket_lifetime = 86400
        renew_lifetime = 172800
        forwardable = true
        krb4_convert = true
        afs_cells = desy.de
        validate = false
        proxiable = false
}

 

I tested the autofs (automount) for Ubuntu 12.04 Server.

mkdir /incoming-nfs

chmod 777 /incoming-nfs

put the next line in to "/etc/auto.master"

/-    /etc/auto.incoming-nfs

put the next line in to "/etc/auto.incoming-nfs"

/incoming-nfs   -rw,soft,nfsvers=3   131.169.247.61:/data

and the last is:

change the timeout to 60 seconds if you want in "/etc/default/autofs"

restart the autofs "/etc/init.d/autofs restart"

exflutca3. The Hard-Drive has been changed to the new SAMSUNG 128 GB Pro SSD.

On exflutcadev do the following:

> ssh-keygen

(the key file should point automatically to /data/USERNAME/.ssh/id_rsa - USERNAME is you user name, empty passphrase)

> cp .ssh/id_rsa.pub .ssh/authorized_keys

That's it.

exflutcadev is up again 12:15 19-Feb-2014

Last night exflutcadev died. I will copy all datas to exflwgs06.

We can't upgrade the Digitizer Board on Slot 6 so we do it on Slot 4.

the exflutca78 installation and configuration has been done.

exflutca1 do not comes up. The last message was that he has Problems to read 5 or 6 blocks. After this he swapped the hdd to readonly. After a reboot the system hung.

 The fs fixed the bad blocks. Now the System is running and fine.

swapping problems during the measurements on Friday 20.Dec.2013.

The fdisk tool the reason for this:

root@exflutca6:~# fdisk -l

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00096fb5

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          32      248832   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/sda2              32       30402   243947521    5  Extended
/dev/sda5              32       30402   243947520   8e  Linux LVM
root@exflutca6:~#

We will reinstall the exflutca6 next time (KW4-5).

 Updated firmware on x2timer boards to version 1.7.0 on utca6 and utca5. 

Puppet Setup in a XFEL environment:

Basics: -     Change BIOS Settings to boot via PXE (now USB)
-    Install Ubuntu 12.04.04-server-amd64
-    Setup Lang: EN, Keyb. EN (US)
-    /etc/fstab "/ option = discard,noatime,errors=remount-ro"

-    Network: 192.168.81.xx/24 gw. 192.168.81.16
-    DNS 131.169.40.200 131.169.194.200
-    Partition: sda1 / 86GB, Partition2: sda5 / 8GB swap, option = discard,noatime
-    Enable sshd
-    Disable ipv6

net.ipv6.conf.all.disable_ipv6=1
net.ipv6.conf.default.disable_ipv6=1
net.ipv6.conf.lo.disable_ipv6=1

-    Deinstall irqbalance
-    change swappines from 60% to10% (echo "vm.swappiness=10" >> /etc/sysctl.conf)
-    User:Passwd – utcaadm:xxxxx
-     %exfl_jet            ALL=(ALL:ALL) ALL  >>  /etc/sudoers
-    nagios  ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/

-     AddressFamily inet   >>  /etc/ssh/sshd_config

Blacklist Modules:

 -    lp
-    ppdev
-    parport_pc
-    parport
-    pcmouse
-    soundcore
-    snd
-    snd_page_alloc
-    snd_timer
-    snd_pmc
-    snd_hwdep
-    snd_hda_codec
-    snd_hda_intel

After reboot setup the Sourcen configuration:

             Change the entry in the /etc/apt/sources.list:
-    deb http://doocspkgs.desy.de/pub/doocs precise main
-    deb-src http://doocspkgs.desy.de/pub/doocs precise main
-    # DESY Ubuntu Repository
-    deb  http://nims.desy.de/ubuntu precise main restricted universe multiverse
-    deb  http://nims.desy.de/ubuntu precise-updates main restricted universe multiverse
-    deb   http://nims.desy.de/ubuntu precise-security main restricted universe multiverse
-    deb-src  http://nims.desy.de/ubuntu precise main restricted universe multiverse
-    deb-src  http://nims.desy.de/ubuntu precise-updates main restricted universe multiverse
-    deb-src  http://nims.desy.de/ubuntu precise-security main restricted universe multiverse

Install other packages:
-    ntp, rsyslog, pciedev-dkms, upciedev-dkms, doocs-dirs-min, x1timer-dkms, doocs-x2timer-server, doocs-pcie-tools, build-essential, dkms, module-assistant, locate, postfix, nedit, emacs, [spd-adq-pci-dkms*.deb, adqupdater_0.13437_amd64.deb,libadq0_0.13437_amd64.deb]
-   nagios-nrpe-server nagios-plugins, autofs, subversion, libnss3-dev, pkg-config, smartmontools, hddtemp, sysstat, postfix, python-qt4, hwinfo, mc, ipmitool
-   preload, ethtool, nfs-common, openssh-server, openssh-client, krb5-user, libpam-krb5, acpi, lm-sensors, rrdtool, perl, gmetad_3.6.0-1ubuntu2_amd64.deb, ganglia-monitor-python_3.6.0-1ubuntu2_all.deb, ganglia-monitor_3.6.0-1ubuntu2_amd64.deb, libganglia1_3.6.0-1ubuntu2_amd64.deb, libconfuse0

 
Configure the packages:

HOSTS
-127.0.0.1       localhost
#-127.0.1.1       exflutca3
#-192.168.81.106  exflutca3.desy.de       exflutca3
#-192.168.81.107  exflutca3-mch.desy.de   exflutca3-mch
-192.168.81.200  exflutcadev.desy.de     exflutcadev
# The following lines are desirable for IPv6 capable hosts
-#::1     ip6-localhost ip6-loopback
-#fe00::0 ip6-localnet
-#ff00::0 ip6-mcastprefix
-#ff02::1 ip6-allnodes
-#ff02::2 ip6-allrouters

NTP
-    Configuration from  "/etc/ntp.conf" change:
-    server ntp.desy.de
-    server ntp1.desy.de
-    server ntp2.desy.de
-    server ntp3.desy.de
-    fudge 127.127.1.0 stratum 13
-    restrict 127.0.0.1
-    restrict ::1
     STOP NTP -> ntpdate -> start ntp: "/usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:113"

nagios:

-   Copy attached file nrpe.cfg to /etc/nagios

-   Copy rest of attached files to /usr/lib/nagios/plugins

-   Make them executable

-   run visudo and add that line:

-   nagios  ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/

-   service nagios-nrpe-server restart

change setup in ceck_temp.sh:

# Warning threshold
thresh_warn=80
# Critical threshold
thresh_crit=90
# Hardware to monitor
sensor=Core

!!! Make sure that the right values are placed for the HDD (SDD) in /etc/nagios/nrpe.cfg

command[check_hddtemp]=sudo /usr/lib/nagios/plugins/check_hddtemp.sh /dev/sda 45 60

autofs:
-     mkdir /data /devhome
-     chmod 777 /data /devhome
-    put the next line in to "/etc/auto.master"
-     /-    /etc/auto.data
-    /-   /etc/auto.devhome

-    put the next line in to "/etc/auto.devhome

-    /devhome    -rw,soft,nfsvers=3  192.168.81.200:/devhome

-    put the next line in to "/etc/auto.data"
-    /data   -rw,soft,nfsvers=3   131.169.247.61:/data

-    and the last is:
-    change the timeout to 60 seconds if you want in "/etc/default/autofs"
-    restart the autofs "/etc/init.d/autofs restart"

Syslog-ng
-    Configuration from “/etc/syslog-ng/syslog-ng.conf” change
-    Put in: udp();
 

rsyslog

- *.* @192.168.81.200 >> /etc/rsyslog.d/50-default.conf

on Craits:

-   destination d_exflutcadev { udp("192.168.81.200" port(514)); };
-   log { source(s_src); filter(f_messages); destination (d_exflutcadev); };

Grub
-    /etc/default/grub
-    #GRUB_CMDLINE_LINUX_DEFAULT="pciehp.pciehp_force=1 pciehp.pciehp_debug=1"
  -    GRUB_CMDLINE_LINUX="pciehp.pciehp_force=1 pciehp.pciehp_debug=1 pcie_ports=native console=tty0 console=ttyS0,115200 rootwait rootdelay=90"
-      GRUB_TERMINAL="console"
-      GRUB_SERIAL_COMMAND="serial --unit=0"


---------
-    commands:
-    update-grub  update-grub2
-    grub-install /dev/sda
----------

PROXY

put in the lines:

http_proxy="http://exflwgs06.desy.de:3128"
https_proxy="http://exflwgs06.desy.de:3128"
ftp_proxy="http://exflwgs06.desy.de:3128"
 

in /etc/environment

 
Modules
-    /etc/modules
-    insert the modules:
-    pciedev
-    upciedev

-    x1timer

-    spd_adq_pci

--------------
-    command: depmod –a

NEW:  /etc/init/tty0.conf
# tty0 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[2345] and (
            not-container or
            container CONTAINER=lxc or
            container CONTAINER=lxc-libvirt)

stop on runlevel [!2345]

respawn
exec /sbin/getty -8 115200 tty0

NEW: /etc/init/ttyS0.conf
# ttyS0 - getty
#
# This service maintains a getty on tty1 from the point the system is
# started until it is shut down again.

start on stopped rc RUNLEVEL=[2345] and (
            not-container or
            container CONTAINER=lxc or
            container CONTAINER=lxc-libvirt)

stop on runlevel [!2345]

respawn
exec /sbin/getty -8 115200 ttyS0

/etc/smartd.conf:

/dev/sda -a -o on -S on -s (S/../.././03|L/../../6/03) -m root -M exec /usr/share/smartmontools/smartd-runner

to /etc/smartd.conf and started the smartd server.

and coment out the line:  start_smartd=yes

in: /etc/defaults/smartmontools

/etc/hddtemp:

Put in the Line:

sudo echo '"Samsung SSD 840 EVO 120G B" 190 C "Samsung SSD 840 EVO 120GB"' >> /etc/hddtemp.db

sudo echo "Samsung SSD 840 PRO Serise" 190  C  "Samsung SSD 840 PRO Serise" >> /etc/hddtemp.db

===============================================
Home
-    mkdir /data
-      command: tune2fs -e remount-ro /dev/sda1
 

Group's added:
-  3555 exfel
-  5478 exfl_jet

users added:
- 23081 exfel babies
- 21502 exfel ballakk
- 21370 exfel baskaran
- 8323  exfel coppola
- 19134 exfel emotuk
- 2512  exfel esenov
- 19446 exfel fernands
- 19499 exfel gessler
- 21126 exfel mdonato
- 23421 exfel sotoudin
- 23972 exfel utcaadm
- 20145 exfel abeckman

Networkcard driver “e1000e”

-    driver with tar and gzip unpacking, make and makeinstall.

Install scripts:
-    /usr/local/bin/myri-irq-bind.sh

Configure scripts:
 
-    myri-irq-bind.sh:
-    “crontab –e” insert the line “@reboot sleep 120 && /usr/local/bin/myri-irq-bind.sh eth0 8”
-    “crontab –e” insert the line “@reboot sleep 120 && /usr/local/bin/x2timer-task-bind.sh"
-    “crontab –e” insert the line “@reboot sleep 120 && /usr/local/bin/eth_push.sh"
-    “crontab –e” insert the line “2 0 * * 7 /sbin/fstrim -v /"
-    “chmod 755 /usr/local/bin/myri-irq-bind.sh
-    “chmod 755 /usr/local/bin/x2timer-task-bind.sh"
-    “chmod 755 /usr/local/bin/eth_push.sh"
 

x2timer-task-bind.sh

#!/bin/bash
taskset -p 04 `cat /export/doocs/server/x2timer_server/x2timer_server.PID`

In the configfile "/etc/init/portmap.conf" I change the option from "-w" to "-i -w" on all crates, now the x2timer comes up.

eth_push.sh

#!/bin/bash
/sbin/ethtool -G eth0 rx 4096 tx 4096

Power supply on exflutca6 changed:

OLD:

Power supply VB Mod: uTCA 1KW (with Debug Con. on Front)

PN: 900-1142-0000

SN: 0813021

HW REV.A

SW REV.02

NEW:

Power supply HB Mod: uTCA 600W

PN: 900-1138-0000

SN: 0213006

HW REV.B

SW REV.04

New from Uros:

Power supply VB Mod: uTCA 1KW (with Debug Con. on Front)

PN: 900-1142-0000

SN: 0713001

HW REV.A

SW REV.02

old FW.

I installed preload on utca6 and exflutcadev for test.

On SN00005 to mmc x2timerv1_ipmi.hex loaded and v/w to Version 1.6.02 changed!

The MCH has been repaired and Vollrath (by NAT) bring to FeC. The repaired board has been tested.

put in:

net.ipv6.conf.all.disable_ipv6=1 

net.ipv6.conf.default.disable_ipv6=1 

net.ipv6.conf.lo.disable_ipv6=1

to /etc/sysctl.conf

also I commenting out all ipv6 lines in /etc/hosts

I installed the short Software procinfo on both machines. It show all Information just like this:

Memory:        Total           Used             Free             Buffers                       
RAM:        24731244     6503164    18228080      167508                       
Swap:      16771820        116260    16655560                                   

Bootup: Tue Aug 13 08:48:36 2013   Load average: 0.10 0.20 0.20 1/749 24829    

user  :             1w 1d 00:42:17.75   0.7%  page in :        214446122               
nice  :                         20:27:59.75   0.1%  page out:       1132670220               
system:               4d 06:10:07.10   0.4%  page act:        126542438               
IOwait:                       08:45:49.66   0.0%  page dea:          6519910               
hw irq:                       00:02:53.97   0.0%  page flt:       6598962323               
sw irq:                       00:57:15.80   0.0%  swap in :           652949               
idle  :       169w 1d 21:00:25.43  98.9%  swap out:          1993272               
uptime:             3m 1w 07:18:48.52         context :      19961682596               

irq   0:      28630  timer                          irq  21:                    0  uhci_hcd:usb4    
irq   1:               2  i8042                         irq  22:               251                   
irq   8:           514  rtc0                            irq  23:   12399381  ehci_hcd:usb2, uh
irq   9:               0  acpi                            irq  24:                   0  aerdrv           
irq  12:             4  i8042                          irq  25:                   0  aerdrv           
irq  16:           32  uhci_hcd:usb3, xh   irq  26:                   0  aerdrv           
irq  17:         111                                      irq  30:  731148326  eth0             
irq  18:             0  ehci_hcd:usb1, uh  irq  31:  139386550  ahci             
irq  19:             3  uhci_hcd:usb5, uh                                         

sda         19880581r        13658647w   sdb          9377037r        12097526w

eth0        TX 108.04GiB     RX 580.64GiB     vboxnet0    TX 87.49KiB      RX 0.00B        
lo            TX   42.77GiB      RX   42.77GiB                                       

 

/proc/sys/vm/swappiness from 60 to 10 changed.

I put a script "swappiness" to /usr/sbin/.

#!/bin/bash
echo "swappiness betraegt im Moment `cat /proc/sys/vm/swappiness`%"
echo "swappiness wird auf 10% gestellt"
echo "10" > /proc/sys/vm/swappiness
echo "Swappines ist nun auf `cat /proc/sys/vm/swappiness`% gestellt!"

To replace the default config put in this:

echo "vm.swappiness=10" >> /etc/sysctl.conf

to your sysctl.conf.

Configfile: /etc/logrotate.d/syslog-ng

Put in:

/var/log/exfl/utcaX.log {

   rotate 4

   missingok

   notifempty

   weekly

   compress

}

I changed the Software package rsyslog to syslog-ng and also the configuration from the /etc/syslog-ng/syslog-ng.conf file:

apt-get autoremove rsyslog

dpkg –P rsyslog

apt-get install syslog-ng.

change the configuration at the configfile:

/etc/syslog-ng/syslog-ng.conf

Put in:

source s_udp { udp( ip(192.168.81.200) port(514) ); };

destination d_exflutcaX { file("/var/log/exfl/utcaX.log"); };

log { source(s_udp); destination(d_exflutcaX); };

I changed the logging package from rsyslog to syslog-ng and the configuration to a master - client.

Now sends all the utcaX clients her log Infomation to the exflutcadev Master.

apt-get autoremove rsyslog

dpkg –P rsyslog

apt-get install syslog-ng.

change the configuration at the configfile:

/etc/syslog-ng/syslog-ng.conf

Put in:

destination d_exflutcadev { udp("192.168.81.200" port(514)); };

log { source(s_src); filter(f_messages); destination (d_exflutcadev); };

The original MCH has a problem: the PCIe BUS was not working.

Vollrath Dirksen by N.A.T. tested and confirmed the problem, so borrow another MCH. Now both DAMCv2 and RTM are recognized.

When the webupdate of the MCH fails during upload of the image, the MCH might be in a kind of emergency state. In this case only the bootloader is started, where access only via the serial connection is possible. The reason for this is, that the webupdater will set the boot string to be 0, what means, that after the boot loader no firmware is loaded. After successfull upload and installation of the new f/w, the webupdater would change back to the correct boot string (0xd0100008) and do re reboot.

In case of a broken update, the only way out is to upgrade the f/w via the command line on the serial port. The update_firmware command has to be used. Then it will ask for the IP address and file name. For this purpose a tftp had been installed and started on exflutcadev (192.168.81.200). So the procedure works as follows:

Connect to serial port via the USB cable on the front on the MCH.

> update_firmware

> 192.168.81.200:mch_fw_214_1.bin

The the upload and upgrade will be done. If it was successfull:

> bs

> 0xd0100008

> yes (if it is asked for it)

Finally do a power cut

FW upgraded to 2.14_1 MCH and PCIe to 1.05.

I can't login via telnet from utca5 the the mch board.
If I take the option -a it works. It seems as if a Kerberos problem.

-a      Attempt automatic login.  Currently, this sends the user name via
             the USER variable of the ENVIRON option if supported by the
             remote system. The username is retrieved via getlogin(3).

There is Voltage at the LED but the LED do not work.

NOTE:

 AMC 900 & MCH are unplugged. 

They are in Christoph Stechmann office.

Access Configuration:

Eth2 IP: 131.169.101.80 (name: dsscmtca01)

USERNAME: dsscmctauser (sorry for the "c" and "t" swapped I will correct soon!)

PASSWORD: ask me or Patrick

At the moment:

• Slot 0: power supply
• Slot 1: NAT MCH
• Slot 2: CPU AMC900
• Slot 3: -
• Slot 4: DAMCv2

NOTE:

A USB-2-JTAG adapter is linked from the CPU to the DAMCv2.

To program run impact: IMPACT (as user, avoid superuser if possible)

$ . /opt/Xilinx/14.4/LabTools/settings64.sh

$ impact &

(The last firmware is available in the home folder.)

TIPS:

To have access to the MCH activate the eth0 with the command

sudo ifconfig eth0 192.168.1.30

and then you can have access at the MCH via

telnet 192.168.1.41

or

by tunneling the port 192.168.1.41:80 via SSH!

Gave DAMC2v2 module with S/N 1057 and the Ericson Power Module + 48V external power supply to Mattia to be installed in MTCA crate at FEC at DESY. The Power modules will be given back, after their order power modules arrived.

Plus

- a PC-power supply used as +12V for the PPT.

- then mini JTAG-USB programmer

Some Problems Fixed the puppet and on the learning dokumentation.

Puppet Enterprise 3.0.1 after Install the Agent you must remove the file "/etc/puppetlabs/mcollective/server.cfg"

After this the Agent run without problems.

#!/bin/bash
while :
do
      /usr/bin/nice -n 19 /bin/cat /proc/meminfo | grep "MemFree:" >> /home/utcaadmin/mem.txt
      /usr/bin/nice -n 19 /bin/cat /proc/meminfo | grep "Active:" >> /home/utcaadmin/mem.txt
      /usr/bin/nice -n 19 /bin/cat /proc/meminfo | grep "Inactive:" >> /home/utcaadmin/mem.txt
      /usr/bin/nice -n 19 /bin/echo . >> /home/utcaadmin/mem.txt
      sleep 300
done

 

/usr/local/bin

#!/bin/bash
while :
do
      /usr/bin/nice -n 19 /usr/bin/rsync -auv /home/utcaadmin/data/ /data/triest/
      sleep 1
done


 

I changed the ssh configuration on both devices.

as root:

if you need, change the entry "PubkeyAuthentication no" in /etc/ssh/ssd_config" from no to yes.

generate the keys:

ssh-keygen -t rsa

copy the key:

cat .ssh/id_rsa.pub | ssh utcaadmin@10.131.169.110 'cat >> .ssh/authorized_keys'

The changed configurattion files (ntp.config, sshh and so on) are saved in \\win.desy.de\group\babies\Eigene Dokumente\Backup\.

I changed the configuration on utca6:

# You do need to talk to an NTP server or two (or three).
#server 131.169.40.65
#server 131.169.194.85
#server 131.169.194.86
server 10.131.169.100

and the new ntp configuration on 18911 is:

#server 131.169.40.65
#server 131.169.194.85
#server 131.169.194.86
server ntp.ubuntu.com
server ptbtime3.ptb.de
server pool.ntp.org

# Use Ubuntu's ntp server as a fallback.
server 127.127.1.0

# Local users may interrogate the ntp server more closely.
restrict 127.127.1.0
fudge 127.127.1.0 stratum 13

# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
restrict 10.131.169.0 mask 255.255.255.0


# If you want to provide time to your local subnet, change the next line.
# (Again, the address is an example only.)
broadcast 10.131.169.255

# If you want to listen to time broadcasts on your local subnet, de-comment the
# next lines.  Please do this only if you trust everybody on the network!
disable auth
broadcastclient

• Reconfigured the exflutca6 entry in the qip to use now the front pannel network interfaces.
• The new MAC address is now 00:40:9e:02:ba:0f
• The /etc/network/interfaces had been adjusted to
  • eth0 is as before (DHCP), which is the network to the MCH
  • eth2 is the new one and configured for DHCP

Downloaded, compiled and replaced the e1000e network card driver. The version now is 2.5.4-NAPI.

Reason was the not detected network adapter on the front pannel.

Upgraded the digitizer Modules with the following serial numbers to the MMC firmware version svn revision 11619):

The FLASH module used on the SP Devices digitizers is:

SPI based

Part number S25FL256S

The new MMC chip on our AMC Test Module had been programmed with the dowloaded images of the borrowd working module from the LLRF group. This includes EEPROM and FLASH data.

ZE replaced the MMC chip on our AMC Test Module with the AT MEGA 1281 and also swapped the V5 and V6 LEDs. Board had been tested and is working fine.

While setting up the exflutca6 system, an ADQ412 module had been replaced in the crate, so that now the follwoing modules are present:

Inserted now all required eight ADQ412 modules into the crate for the PES experiment. The modules with the follwoing serial numbers are present in the following positions:

The experience was, that the x2timer software is not working anymore, if PCIe hotplugging is enabled in the MCH. It should be checked, if this is still the case and then clarified with the responsible DESY people (Arthur, Lyudvig). Hotplugging is currently disabled, but it would be important to avoid reboots after FPGA reprogramming.

I corrected the PCIe configuration of the exflutca5-mch. It was configured for PCIe on only the first 6 AMCs. Now it supports all 12 slots.

I kept the PCIe Hotplug = disabled, as the hotplugging produced errors with the timing module software --> this has to be checked!

Due to the power module replacement, I had to power cycle the crate

I removed the old DC/DC power module from Emerson with the new AC 600W Tekoor power module. Main resons were, that the old module does not allow control of Power module and Fans via the MCH and that the provided maxiumum power is limited to 350W.

Upgraded the digitizer Modules with the following serial numbers to the MMC firmware version 2.0 (svn revision 11472) and enabled the save EEProm fuse (SSAVE):

Settings for IMPACT to program the Platform FLASH:

• FLASH is Master
• Clock is external
• Parallel Mode

chmod 622 /dev/console

chmod 622 /dev/tty1

chmod 666 /dev/ttyS1

-----------------

change the /etc/init/tty1.

from: exec /sbin/getty -8 38400 tty1

to:exec /sbin/getty -L ttyS1 38400 vt100

---------------

change grub config file: /etc/default/grub

from: GRUB_CMDLINE_LINUX="pciehp.pciehp_force=1 pciehp.pciehp_debug=1"

to: GRUB_CMDLINE_LINUX="condole=ttyS1,38400 console=tty1 pciehp.pciehp_force=1 pciehp.pciehp_debug=1"

-----------------

update-grub

install-grub /dev/sda

1: change the entry from the /etc/apt/sources.list:

# managed by FAI ( hooks/updatebase.DEFAULT )
#
########################################################
# Do NOT edit this files, changes will be overwritten! #
# Use /etc/apt/sources.list.d/ instead.                #
########################################################

# DES
deb http://fai.desy.de/pub/desy precise desy
deb-src http://fai.desy.de/pub/desy precise desy
deb http://doocspkgs.desy.de/pub/doocs precise main
deb-src http://doocspkgs.desy.de/pub/doocs precise main

# DESY Ubuntu Repository
deb http://fai.desy.de/pub/repository/mirror/archive.ubuntu.com/ubuntu precise main restricted universe multiverse
deb http://fai.desy.de/pub/repository/mirror/archive.ubuntu.com/ubuntu precise-updates main restricted universe multiverse
deb http://fai.desy.de/pub/repository/mirror/archive.ubuntu.com/ubuntu precise-security main restricted universe multiverse

deb-src http://fai.desy.de/pub/repository/mirror/archive.ubuntu.com/ubuntu precise main restricted universe multiverse
deb-src http://fai.desy.de/pub/repository/mirror/archive.ubuntu.com/ubuntu precise-updates main restricted universe multiverse
deb-src http://fai.desy.de/pub/repository/mirror/archive.ubuntu.com/ubuntu precise-security main restricted universe multiverse
 
then you should send the comand:

wget -O - http://doocs.desy.de/pub/doocs/DESY-Debian-key.asc | apt-key add -
apt-get update

apt-get upgrade

apt-get install build-essential dkms module-assistant pciedev upciedev nfs-common openssh-server openssh-client ntp ntpdate doocs-pcie-tools doocs-x2timer-server subversion libnss3-dev pkg-config

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

2.: change some configs:

/etc/default/grub

#GRUB_CMDLINE_LINUX_DEFAULT="pciehp.pciehp_force=1 pciehp.pciehp_debug=1"
GRUB_CMDLINE_LINUX="pciehp.pciehp_force=1 pciehp.pciehp_debug=1"

---------

commands:

update-grub

grub-install /dev/sda

------------

/etc/modules

insert the modules:

pciedev

upciedev

--------------

command: depmod -a

change the configuration to:

# /etc/ntp.conf, configuration for ntpd
#
# managed by FAI ( scripts/NTP/50-setup )

driftfile /var/lib/ntp/ntp.drift

statsdir /var/log/ntpstats/

statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable

server ntp.desy.de
server ntp1.desy.de
server ntp2.desy.de

server ntp3.desy.de

# ... and use the local system clock as a reference if all else fails
# NOTE: in a local network, set the local stratum of *one* stable server
# to 10; otherwise your clocks will drift apart if you lose connectivity.
server 127.127.1.0
fudge 127.127.1.0 stratum 13

# See /usr/share/doc/ntp-doc/html/accopt.html for details.
restrict -4 ignore
restrict -6 ignore

---------------

command: ntpdate ntp.desy.de
restart the ntp deamon: service ntp start

+++++++++++++++++++++++++++++++++++++++++++++++++++

mkdir /devhome

chmod 777 /devhome

insert in /etc/fstab:

192.168.81.200:/    /devhome    nfs4    rw,soft,users,noauto    0 0

command: mount /devhome

The last one..........

command: tune2fs -e remount-ro /dev/sda1

The ipmitool is a software, which allows to use ipmi commands via network with the MCH. One possibility is top use the HMP.1 standard in order to upgrade f/w of modules, which support it. The syntax is the following (if MCH Backward compatibility to 2.4 is disabled):

ipmitool -H exflutcaX-mch -P "" -T 0x82 -B 0 -b 7 -t 0xTT hpm upgrade [filename.hpm]

otherwise use:

ipmitool -H exflutcaX-mch -P "" -t 0xTT hpm upgrade [filename.hpm]

Upgraded MMC and tried upgrade of FPGA of ADQ412 in Slot 12:

First upgraded the MMC firmware via TigerDragon cable to the f/w provided by SP Devices, which supports now HPM f/w upgrade for the FPGA/FLASH. After MMC f/w upgrade, the EEPROM data had to be restored.
Then the FPGA was updated via ipmitool through the MCH via network. The description of the tool is described in a separate entry ("Upgrade via IMPMI and HPM").

The first upgrade attempt failed with the following print out:

gessler@exflutcadev:~/firmware/ADQ_fw_updater$ ipmitool -H exflutca6-mch -P "" -T 0x82 -B 0 -b 7 -t 0x88 hpm upgrade top_adq412.hpm

PICMG HPM.1 Upgrade Agent 1.0.2:

Validating firmware image integrity...OK
Performing preparation stage...OK

Performing upgrade stage:

-------------------------------------------------------------------------------
|ID | Name      |    Versions           |    Upload Progress  | Upload| Image |
|   |           | Active| Backup| File  |0%       50%     100%| Time  | Size  |
|---|-----------|-------|-------|-------||----+----+----+----||-------|-------|
|*1 |FPGA-ADQ-V6|  0.05 | --.-- |  0.06 ||...................|| 91.28 | 8ce00c |
Error finishing firmware upload, compcode = 81

-------------------------------------------------------------------------------

(*) Component requires Payload Cold Reset
Firmware upgrade procedure failed

Mitten im Betrieb glaubt die Anlage das die Processor Karte (Slot 3) mit dem Powerdown Button ausgeschaltet wird.

Frank

Fr: xflutca4 running out of space and killed other PID's.

NTP mittels "apt-get install ntp" nach installiert!

Konfiguration der "/etc/ntp.conf" wie folgt geaendert:

server 131.169.40.65

server 131.169.194.85

server 131.169.194.86

server 127.127.1.0

fudge 127.127.1.0 stratum 13

Nachgetragen und

restrict -4 ignore

restrict -6 ignore

geändert.

ntpd mittels kill -9 "PID" gestopt und mittels:

"/usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 106:113" neu gestartet.

Frank

Umcompilieren der Kernelmodule.

Frank

Die Lösung ist das die Festplatte selbst so eingestellt sein muss das sie nach einem Crash im RO Modus wieder hoch kommt:

"tune2fs -e remount-ro /dev/sd...."

 ---------------------------------------

Nach einem Stromausfall hängt die Festplatte, da sie auf eine Eingabe wartet am Prompt.

Bei Autonomen Systemen kommt man auch nicht per Netzwerk wieder an die Anlage.

in der Datei: /etc/apt/sources.list

sind die Einträge: deb http://doocspkgs.desy.de/pub/doocs lucid main     #nur für die Distribution "lucid" 10.4 "precise" 12.4

und deb-src http://doocspkgs.desy.de/pub/doocs lucid main  #nur für die Distribution "lucid" 10.4 "precise" 12.4

vor zu nehmen.

########################
#apt-get Wichtigsten Befehle#
########################

apt-get update #Datenbanken neu einlesen
apt-get install locate  #locate installieren
 "updatedb" Ausführen!
 

update

aktualisiert die übersicht der verügbaren Pakete, liest also die Informationen aus den Dateien Packages.gz der jeweiligen Distribution ein. Sie sollten update immer ausführen,

wenn Sie wissen, dass sich die Inhalte der Paketdateien beziehungsweise die vergbaren Pakete auf dem Server geändert haben. Auf jeden Fall sollten Sie update vor dem Aufruf von upgrade oder dist-upgrade aufrufen.

    Eine neue Fähigkeit von apt seit Debian 4.0 ist die Möglichkeit, lediglich die Änderungen der Packages-Dateien seit ihrer letzten Aktualisierung herunterzuladen.


upgrade

    Um alle auf dem System installierten Pakete auf die aktuelle Version zu bringen, können Sie upgrade benutzen. Alle bereits installierten Pakete, von denen eine neuere Version verfügbar ist, werden aktualisiert. Es werden keine Pakete gelöscht, die bereits installiert sind (und in den neuen Paketdateien nicht mehr enthalten sind), oder Pakete installiert, die noch nicht auf dem System vorhanden sind. Pakete, die bereits installiert sind und es bei einem Upgrade erforderlich machen, den Status anderer Pakete zu verändern, werden nicht aktualisiert. apt-get update muss vorab ausgeführt werden, so dass sichergestellt ist, dass die Paketinformationen auf dem neuesten Stand sind.


dist-upgrade

    ist eigentlich eine Ergänzung oder Erweiterung zu upgrade. Es wird hierbei dafür Sorge getragen, dass für das System wichtigere Pakete zuerst installiert werden. Hierbei werden in engen Grenzen auch Abhängigkeiten verändert, um ein Paket installieren zu können. Dies ist dann notwendig, wenn ein System komplett auf eine neue Version umgestellt werden soll und kein sanfter Übergang gewährleistet werden kann.
 

dselect-upgrade

    Mit dieser Option werden auch die Paketinformationen recommends und suggests ausgewertet. Dies ist sonst nur mit dselect möglich. Diese Vorschläge für weitere Pakete sind zur Funktion des gewünschten Pakets nicht zwingend erforderlich, können aber durchaus sinnvoll sein.


install

    Diese Option benötigt noch einen oder mehrere Paketnamen. Jedes dieser Pakete (der Paketname, also beispielsweise sendmail, reicht hierbei aus) sowie die noch benötigten Pakete (diese werden automatisch ermittelt) werden auf Basis der Informationen in /etc/apt/sources.list geholt und installiert. Wenn Sie hinter den Namen des Pakets ein Minuszeichen (-) setzen, wird das Paket aus dem System entfernt, wenn es bereits installiert ist. Achten Sie darauf, dass das Minuszeichen (ohne ein Leerzeichen dazwischen) unmittelbar nach dem Paketnamen steht. Diese Funktion kann auch bei Konflikten bei der Installation einzelner Pakete sehr nützlich sein: Sie können so Pakete in einem Vorgang löschen und installieren. Die Option install wählt immer die aktuellste verügbare Version eines Pakets aus. Es kann jedoch sinnvoll sein, auch Zugriff auf ältere Programmversionen zu haben. Hierzu kann ab der Version 0.5.3 von apt folgende Syntax verwendet werden: apt-get install sane/unstable. Durch einen Slash (/) getrennt, kann hinter dem Paketnamen das gewünschte Release eines Pakets angegeben werden.

    Eine weitere Möglichkeit ist es, falls verschiedene Versionen eines Pakets verügbar sind, direkt die gewünschte Versionsnummer anzugeben. Zunächst sollte man mit apt-cache prüfen, welche Versionen eines Pakets verfügbar sind. Mit apt-get install vim=6.0.093-2 kann dann ganz gezielt die gewünschte Version installiert werden.


--reinstall

    Diese Option installiert das gewünschte Paket komplett neu, auch wenn es bereits installiert ist. Beachten Sie, dass hierbei auch die Option install anzugeben ist!


remove

    Diese Funktion ist analog zu install, nur mit dem Unterschied, dass die Pakete standardmäsig entfernt werden, anstatt sie zu installieren. Analog zu dem eben Beschriebenen können Sie hier ein Pluszeichen (+) verwenden, um Pakete zu installieren.


check

    dient lediglich zur Diagnose. Es wird überprüft, ob sich irgendwelche Unstimmigkeiten in den Paketen finden.
 

--purge remove

    Löscht das gewünschte Paket und alle weiteren Pakete, die direkt von diesem Paket abhängig sind. Weiterhin werden alle zu den Paketen gehörenden Konfigurationsdateien gelöscht.


clean

    Dies löscht das lokale Verzeichnis, in dem sich die zu installierenden Pakete befinden. Alles, mit Ausnahme der lock-Datei, wird aus /var/cache/apt/archives/ und /var/cache/apt/archives/partial/ gelöscht.


source

    Dieses Kommando holt die notwendigen Dateien zur Erzeugung eines Binärpakets. Es können so angepasste Pakete erzeugt werden oder aber Pakete auf einer anderen Architektur übersetzt werden. Wichtig ist hierbei ein entsprechender deb-src-Eintrag in der Datei sources.list. Um alle zu einem Paket gehörenden Dateien von einem Server zu holen, reicht das Kommando apt-get source paketname. Es werden die aktuellen Versionen der Dateien paketname.orig.tar.gz, paketname.dsc und paketname.diff.gz im aktuellen Verzeichnis gespeichert.

    Um aus den Quellen direkt ein Binärpaket zu erzeugen, kann die Option -b angegeben werden. Das komplette Kommando lautet dann apt-get source -b paketname. Wenn die benötigten Source-Pakete bereits vorliegen, kann das Binärpaket auch direkt mit dem Kommando dpkg-buildpackage -rfakeroot -us -uc erzeugt werden.


build-dep

    Die meisten Software-Pakete benötigen bei der Übersetzung aus den Quellpaketen weitere Entwicklungspakete wie Libraries und Header-Dateien. Diese werden häufig nicht mitgeliefert und liegen in gesonderten Paketen vor. Das Debian Paketsystem sieht so genannte build dependencies vor, in denen alle Abhängigkeiten zur Erzeugung eines Pakets beschrieben sind.

    Das Kommando apt-get build-dep paketname sorgt dafür, dass alle zur Übersetzung eines Pakets benötigten Dateien auf dem System vorhanden sind.
 

moo

    Als kleine versteckte Option haben die Entwickler auch noch ein so genanntes ′Easter-Egg“ eingebaut:


    fr@sushi:~$ apt-get moo
             (__)
             (oo)
       /------\/
      / |    ||   
     *  /\---/\
        ~~   ~~   
    ...."Have you mooed today?"...


apt-cache search mc | grep Midnight #sucht in der DB nach MC.
      show

dpkg -S mc #suche nach mc mit dpkg
     -l mc #Liste das installierte Packet mc auf.

#######################################
#export DEBIAN_FRONTEND=noninteractive#
#######################################

--force-yes
 

Force yes; This is a dangerous option that will cause apt to continue without prompting if it is doing something potentially harmful. It should not be used except in very special situations. Using force-yes can
potentially destroy your system! Configuration Item: APT::Get::force-yes.


die Einträge force-confold (alte Konfiguration bevorzugen) bzw. force-confnew (neue Konfiguration bevorzugen) und force-confdef (Standard-aktion) in der /etc/dpkg/dpkg.cfg eingetragen werden und damit jegliche Nachfrage unterdrücken

 

#################
#Repos hinzufügen#
###################

sudo add-apt-repository ppa:marko-techytalk.info/light-themes
sudo apt-get update && sudo apt-get upgrade

Frank

#########################################################
#Grub Eintragungen um Parameter beim booten mit zu geben#
#########################################################

vi /etc/default/grub

(Ältere Systeme nehmen auch:(defoptions="pciehp.pciehp_force=1 pciehp.pciehp_debug=1 quiet"))

GRUB_GFXMODE=1600x1200

Speichern

update-grub

/etc/default/grub
GRUB_GFXMODE=1024x768
#######################

diese Änderung permanent:

/etc/grub.d/00_header/
if loadfont `make_system_path_relative_to_its_root "${GRUB_FONT_PATH}"` ; then
set gfxmode=${GRUB_GFXMODE}
set gfxpayload=keep
load_video
insmod gfxterm
fi


# update-grub
# reboot


fi

ACHTUNG!!!
Manchmal werden die Eintragungen in der Grub config zwar übernommen und sind auch eingetragen, sie werden aber nicht beim Start aktiviert. In diesem Fall hilft ein:

"update-initramfs -u"


 

Installiert sein müssen die Pakete:
build-essential, dkms und module-assistant.
Neue Module werden in der:
/usr/share/modass/compliant.list
per Hand eingetragen.

Wichtig!!

Um den Module Assistenten auch mit einem Kernelupgrade nutzen zu können ist es zwingend notwendig auch das Paket dkms installiert zu haben!!

 

Beim Blacklisten der Module ist in der Namensgebung darauf zu achten,

dass sie immer mit "blacklist-" beginnen.

z.B. "blacklist-nvidia.."

2tens trotz einem nachfolgenden:  "depmode -a" kommt es vor das auch hier wie bei grub eintragungen die selbstgemachten eintragungen nicht aktiviert sind.

Auch hier hilft ein "update-iniramfs -u"

Frank

Um das Keyboard mapping zu ändern muss ein entsprechender

Eintrag in der /etc/default/keyboard auf "us" oder "de" usw. gemacht werden.

Frank

FAI erlaubt es einen neuen Rechner über Netzwerk, USB oder auch CD/DVD, kommplet zu Installieren und konfigurieren.

Die gewünschten Voreinstellungen der neuen PC's werden in sogenannten Classen eingestellt.

Frank