Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[jacobsen on 2007-09-10 02:45:42] : hub 76 crashes at SPTS #40

Closed
dglo opened this issue Mar 3, 2021 · 3 comments
Closed

[jacobsen on 2007-09-10 02:45:42] : hub 76 crashes at SPTS #40

dglo opened this issue Mar 3, 2021 · 3 comments

Comments

@dglo
Copy link
Owner

dglo commented Mar 3, 2021

No associated GitHub commit

@dglo
Copy link
Owner Author

dglo commented Mar 3, 2021

[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 $Revision: 1.381 $)
/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

@dglo
Copy link
Owner Author

dglo commented Mar 3, 2021

[jacobsen on 2007-09-10 16:44:15]
Problem seen to occur during insmod -- suggests bad DOR card, possibly independent of driver?

@dglo
Copy link
Owner Author

dglo commented Mar 3, 2021

[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.

@dglo dglo closed this as completed Mar 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant