Comments (3)
[jacobsen on 2007-09-10 15:59:00]
First look suggests this only happens with dor card 0 - on all && domterm 00A was enough to crash it. Mark is testing the other DOR cards now.
Crash signature:
[jacobsen@spts64-ichub76 ~]$ domterm 00a
connecting...Read from remote host sps-ichub76: Connection reset by peer
earlier:
[jacobsen@spts64-ichub76 ~]$ off all
on alWARNING: DOMs are not completely powered off; you must turn
the power supply off before disconnecting or connecting cables
or touching exposed hardware.
[jacobsen@spts64-ichub76 ~]$ on all
Driver V02-11-05 (dh.c
/proc/driver/domhub/card0 -- PCI=9, FW=104q, DOR=1
/proc/driver/domhub/card1 -- PCI=9, FW=104q, DOR=1
/proc/driver/domhub/card2 -- PCI=9, FW=104q, DOR=1
/proc/driver/domhub/card3 -- PCI=9, FW=104q, DOR=1
/proc/driver/domhub/card4 -- PCI=9, FW=104q, DOR=1
/proc/driver/domhub/card5 -- PCI=9, FW=104q, DOR=1
/proc/driver/domhub/card6 -- PCI=9, FW=104q, DOR=1
/proc/driver/domhub/card7 -- PCI=9, FW=104q, DOR=1
0 0 B: communicating
0 0 A: communicating
0 1 B: communicating
0 1 A: NOT communicating
0 2 B: communicating
0 2 A: communicating
0 3 B: communicating
0 3 A: communicating
7 DOMs are communicating.
[jacobsen@spts64-ichub76 ~]$ domterm 00b
connecting... OK
[jacobsen@spts64-ichub76 ~]$ cat /proc/driver/domhub/card0/pair0/domB/comstat
/dev/dhc0w0dB
RX: 114B, MSGS=15 NINQ=0 PKTS=36 ACKS=13
BADPKT=0 BADHDR=0 BADSEQ=8 NCTRL=0 NCI=2 NIC=38
TX: 9B, MSGS=9 NOUTQ=0 RESENT=4 PKTS=36 ACKS=23
NACKQ=0 NRETXB=0 RETXB_BYTES=0 NRETXQ=0 NCTRL=0 NCI=20 NIC=0
NCONNECTS=0 NHDWRTIMEOUTS=0 OPEN=FALSE CONNECTED=FALSE
RXFIFO=empty TXFIFO=almost empty,empty DOM_RXFIFO=notfull
[jacobsen@spts64-ichub76 ~]$ domterm 00b
connecting... OK
[jacobsen@spts64-ichub76 ~]$ cat /proc/driver/domhub/card0/pair0/domB/comstat
/dev/dhc0w0dB
RX: 126B, MSGS=18 NINQ=0 PKTS=42 ACKS=16
BADPKT=0 BADHDR=0 BADSEQ=8 NCTRL=0 NCI=3 NIC=39
TX: 12B, MSGS=12 NOUTQ=0 RESENT=4 PKTS=42 ACKS=26
NACKQ=0 NRETXB=0 RETXB_BYTES=0 NRETXQ=0 NCTRL=0 NCI=30 NIC=1
NCONNECTS=0 NHDWRTIMEOUTS=0 OPEN=FALSE CONNECTED=FALSE
RXFIFO=empty TXFIFO=almost empty,empty DOM_RXFIFO=notfull\n\n
from dor-driver.
[jacobsen on 2007-09-10 16:44:15]
Problem seen to occur during insmod -- suggests bad DOR card, possibly independent of driver?
from dor-driver.
[jacobsen on 2007-09-10 18:13:07]
Problem seems to be DOR card 0 - discussed w/ Kael and decided to not pursue this beyond swapping cards out and having Mark re-test the Hub.
from dor-driver.
Related Issues (20)
- [jkelley on 2017-03-03 20:41:12] : DOMCal run triggered dead DOM drop HOT 5
- [jkelley on 2017-05-22 16:22:05] : pDAQ reports device file "not found" for dropped DOMs HOT 2
- [jkelley on 2018-02-12 15:15:51] : softbooting unpowered DOMs results in unhelpful error message HOT 1
- [jkelley on 2018-02-13 20:11:20] : Calling select() on a DOM device file that has powered off hangs HOT 1
- [jkelley on 2018-09-04 14:34:26] : Typo "minimum" in maximum voltage and current firmware fuse errors HOT 1
- [jkelley on 2018-09-04 14:36:06] : DOMs come back on after firmware fuse trips HOT 3
- [jkelley on 2018-09-04 14:38:48] : Add CWD in all dor "minor" error reporting
- [jkelley on 2019-01-08 21:04:27] : Improve output of fpga-regs procfile HOT 1
- [jkelley on 2019-01-08 21:29:34] : pprintk compilation is broken HOT 1
- [jkelley on 2019-01-10 16:14:13] : Clean up print format warnings in MEGA_COMMENTS mode HOT 1
- [jkelley on 2019-11-18 18:19:49] : Dead DOM state in driver should result in prompt drops
- [jkelley on 2019-11-18 19:30:40] : Hub lockup on concurrent DOM pair power-cycles
- [jkelley on 2019-11-18 20:27:13] : Driver reload may have caused kernel oops
- [jkelley on 2019-11-19 17:27:13] : Add log message when power interlock fires
- [jkelley on 2020-02-17 22:18:35] : Error check when reading domid when power off never satisfied HOT 2
- [jkelley on 2020-02-18 01:48:54] : Port driver to 4.18 kernel HOT 2
- [jkelley on 2020-02-18 17:46:22] : Restore module parameter description HOT 1
- [jkelley on 2020-02-18 17:55:17] : Deprecate kernel 2.4 support HOT 1
- [jkelley on 2020-02-28 18:16:27] : Driver spams logfile when DOM dropped HOT 1
- [jkelley on 2020-03-12 16:29:51] : On dead DOM timeout, try FIFO dump at least once before DOM drop HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dor-driver.