Scratch - Revision history

129.57.167.199 at 16:08, 31 August 2011

2011-08-31T16:08:44Z

← Older revision		Revision as of 12:08, 31 August 2011
Line 1:		Line 1:
			test setup error aug 31, 2011:
			...
			0x9478760 (ROLS_LOOP): INFO: User Go ...
			proc_thread: waiting= 31106 processing= 234 microsec per event (nev=59)
			net_thread: waiting= 21361 sending= 2 microsec per event (nev=108)
			proc_thread: waiting= 12613 processing= 106 microsec per event (nev=66)
			proc_thread: waiting= 13237 processing= 137 microsec per event (nev=66)
			net_thread: waiting= 13001 sending= 1 microsec per event (nev=129)
			proc_thread: waiting= 12753 processing= 110 microsec per event (nev=65)
			proc_thread: waiting= 13227 processing= 106 microsec per event (nev=66)
			0x9478760 (ROLS_LOOP): tdc1190ReadBoardDmaDone: WRONG: nbytes_save[4]=176, res=0 => mbytes=176
			0x9478760 (ROLS_LOOP): [ 4] ERROR: tdc1190ReadEvent[Dma] returns -2
			0x9478760 (ROLS_LOOP): [ 5] ERROR: tdc1190ReadEvent[Dma] returns 0
			0x9478760 (ROLS_LOOP): [ 6] ERROR: tdc1190ReadEvent[Dma] returns 0
			0x9478760 (ROLS_LOOP): [ 7] ERROR: tdc1190ReadEvent[Dma] returns 0
			0x9478760 (ROLS_LOOP): [ 8] ERROR: tdc1190ReadEvent[Dma] returns 0
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 0] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 1] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 2] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 3] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 4] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 5] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 6] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 7] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): tdc1190ReadStart: [ 8] not ready ! (nev=0)
			0x9478760 (ROLS_LOOP): [ 0] ERROR: tdc1190ReadEvent[Dma] returns 0
			0x9478760 (ROLS_LOOP): [ 1] ERROR: tdc1190ReadEvent[Dma] returns 0
			0x9478760 (ROLS_LOOP): [ 2] ERROR: tdc1190ReadEvent[Dma] returns 0
			...............

	Sergey Kuleshov Aug 15 2011: send Ben's schematic for DC TDC, and mentioned young engineers from Chile for CLAS disassemble/CLAS12 assemble		Sergey Kuleshov Aug 15 2011: send Ben's schematic for DC TDC, and mentioned young engineers from Chile for CLAS disassemble/CLAS12 assemble

98.166.92.51 at 19:54, 14 August 2011

2011-08-14T19:54:26Z

← Older revision		Revision as of 15:54, 14 August 2011
Line 1:		Line 1:
			Sergey Kuleshov Aug 15 2011: send Ben's schematic for DC TDC, and mentioned young engineers from Chile for CLAS disassemble/CLAS12 assemble

	timeout 2: 9599514 + 64 = 9599578		timeout 2: 9599514 + 64 = 9599578
	timeout: 9599579 9599578		timeout: 9599579 9599578
	SEND_BUFFER_ROC 4		SEND_BUFFER_ROC 4

129.57.76.91 at 14:18, 20 June 2011

2011-06-20T14:18:52Z

← Older revision		Revision as of 10:18, 20 June 2011
Line 1:		Line 1:

			timeout 2: 9599514 + 64 = 9599578
			timeout: 9599579 9599578
			SEND_BUFFER_ROC 4
			timeout 2: 9599579 + 64 = 9599643
			timeout: 9599644 9599643
			SEND_BUFFER_ROC 4
			interrupt: SEND_BUFFER_ROL1
			timeout 2: 9599644 + 64 = 9599708
			timeout: 9599709 9599708
			SEND_BUFFER_ROC 4
			interrupt: SEND_BUFFER_ROL1
			attempt to send short buffer failed !!!
			timeout 2: 9599709 + 64 = 9599773
			timeout: 9599774 9599773
			SEND_BUFFER_ROC 4
			timeout 2: 9599774 + 64 = 9599838
			ERROR1: LINK_sized_write() returns errno=851971 (cc=-1, sizeof(nbytes)=4(104040), netlong=104040)
			ERROR: net_thread failed (in LINK_sized_write).
			timeout: 9599839 9599838
			SEND_BUFFER_ROC 4
			ERROR: big0.failure=0, big1.failure=1
			interrupt: SEND_BUFFER_ROL1
			0x9247630 (coda_proc): timer: 2 microsec (min=0 max=601 rms**2=1)
			0x9247630 (coda_proc): timer: 2 microsec (min=0 max=601 rms**2=6)
			interrupt: SEND_BUFFER_ROL1


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

	Quota check:		Quota check:

129.57.76.91 at 14:28, 18 September 2009

2009-09-18T14:28:51Z

← Older revision		Revision as of 10:28, 18 September 2009
Line 1:		Line 1:
			Quota check:

			http://cc.jlab.org/cgi-bin/quotacheck.cgi

	Nerses:		Nerses:

98.166.91.3 at 03:31, 29 April 2009

2009-04-29T03:31:12Z

← Older revision		Revision as of 23:31, 28 April 2009
Line 1:		Line 1:
	Nerses:		Nerses:

	Home number is +374 10 425049		Home number is +374 10 425049

	Cell phone +374 91 206 217		Cell phone +374 91 206 217

98.166.91.3 at 03:30, 29 April 2009

2009-04-29T03:30:26Z

← Older revision		Revision as of 23:30, 28 April 2009
Line 1:		Line 1:
			Nerses:
			Home number is +374 10 425049
			Cell phone +374 91 206 217

			-----------

	clon02:/etc> ifconfig -a		clon02:/etc> ifconfig -a
	lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1		lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

Boiarino at 23:30, 8 March 2009

2009-03-08T23:30:56Z

← Older revision		Revision as of 19:30, 8 March 2009
Line 1:		Line 1:
	clon02:/etc> ifconfig -a		clon02:/etc> ifconfig -a
	lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1		lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
	inet 131.225.70.20 netmask ff000000		inet 131.225.70.20 netmask ff000000
	age0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2		age0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
	inet 131.225.70.20 netmask fffffc00 broadcast 131.225.255.255		inet 131.225.70.20 netmask fffffc00 broadcast 131.225.255.255
	ether 0:a0:80:0:52:e5		ether 0:a0:80:0:52:e5
	eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3		eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
	inet 129.57.167.2 netmask ffffff00 broadcast 129.57.167.255		inet 129.57.167.2 netmask ffffff00 broadcast 129.57.167.255
	ether 0:3:ba:1d:9b:c0		ether 0:3:ba:1d:9b:c0
	clon02:/etc>		clon02:/etc>

Boiarino at 23:23, 8 March 2009

2009-03-08T23:23:56Z

← Older revision		Revision as of 19:23, 8 March 2009
Line 1:		Line 1:
			clon02:/etc> ifconfig -a
			lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
			inet 131.225.70.20 netmask ff000000
			age0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
			inet 131.225.70.20 netmask fffffc00 broadcast 131.225.255.255
			ether 0:a0:80:0:52:e5
			eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
			inet 129.57.167.2 netmask ffffff00 broadcast 129.57.167.255
			ether 0:3:ba:1d:9b:c0
			clon02:/etc>


			-------

	SUNW-MSG-ID: ZFS-8000-HC, TYPE: Error, VER: 1, SEVERITY: Major		SUNW-MSG-ID: ZFS-8000-HC, TYPE: Error, VER: 1, SEVERITY: Major
	EVENT-TIME: Thu Mar 5 17:41:00 EST 2009		EVENT-TIME: Thu Mar 5 17:41:00 EST 2009

Boiarino at 22:54, 5 March 2009

2009-03-05T22:54:44Z

← Older revision		Revision as of 18:54, 5 March 2009
Line 1:		Line 1:
			SUNW-MSG-ID: ZFS-8000-HC, TYPE: Error, VER: 1, SEVERITY: Major
			EVENT-TIME: Thu Mar 5 17:41:00 EST 2009
			PLATFORM: SUNW,Netra-240, CSN: -, HOSTNAME: clon10
			SOURCE: zfs-diagnosis, REV: 1.0
			EVENT-ID: 2f3d5430-2bbb-c8aa-87d5-f79b44f89edf
			DESC: The ZFS pool has experienced currently unrecoverable I/O failures. Refer to http://sun.com/msg/ZFS-8000-HC for more information.
			AUTO-RESPONSE: No automated response will be taken.
			IMPACT: Read and write I/Os cannot be serviced.
			REC-ACTION:

			The pool has experienced I/O failures. Since the ZFS pool property 'failmode'
			is set to 'wait', all I/Os (reads and writes) are blocked. See the zpool(1M)
			manpage for more information on the 'failmode' property. Manual intervention
			is required for I/Os to be serviced. You can see which devices are
			affected by running 'zpool status -x':



			# zpool status -x
			pool: test
			state: FAULTED
			status: There are I/O failures.
			action: Make sure the affected devices are connected, then run 'zpool clear'.
			see: http://www.sun.com/msg/ZFS-8000-HC
			scrub: none requested
			config:

			NAME STATE READ WRITE CKSUM
			test FAULTED 0 13 0 insufficient replicas
			c0t0d0 FAULTED 0 7 0 experienced I/O failures
			c0t1d0 ONLINE 0 0 0

			errors: 1 data errors, use '-v' for a list



			After you have made sure the affected devices are connected, run 'zpool clear'
			to allow I/O to the pool again:



			# zpool clear test



			If I/O failures continue to happen, then applications and commands for the
			pool may hang. At this point, a reboot may be necessary to allow I/O to the
			pool again.


			----

	mgetty		mgetty

Boiarino at 16:15, 18 February 2009

2009-02-18T16:15:11Z

← Older revision		Revision as of 12:15, 18 February 2009
Line 1:		Line 1:
			mgetty

	Sergey --- does this help you ? Today marked the 3rd week since this		Sergey --- does this help you ? Today marked the 3rd week since this