Dell PowerVault 51F Dell PowerVault 51F 8-Port Fibre Channel Switch Insta - Page 145

MQ-QWRITE Error, Table A-2., Panic Errors

Page 145 highlights

Table A-2. Panic Errors (continued) Error Severity Explanation TASKSPAWN (0) A task could not be created. TIMEUSECNT (0) A timer was not released after expiration. ZOMTIMKILL (0) An attempt was made to kill a timer that was in 'zombie' state. ZOMTIMSET (0) An attempt was made to set a timer that was in 'zombie' state. Action Issue the traceShow command. Contact customer support. Issue the traceShow command. Contact customer support. Issue the traceShow command. Contact customer support. Issue the traceShow command. Contact customer support. MQ-QWRITE Error The software includes several message queues that are used for inter-task communication. Each queue holds a maximum of 64 messages. Under normal operations, a task sends a message to another task on a queue, and occupies a slot in the queue. After the message is received, its slot in the queue is open for another message. If the receiving task does not run for a period of time, and the sender task sends more than 64 messages to the same queue before the first message is processed by the receiving task, the queue overflows and the message is discarded. This event causes the MQ-QWRITE error to be printed on the display, as well as on the Telnet window, if open. The error is also stored in the error log which can be viewed with the errShow command. NOTE: The error log is cleared upon reboot. There may be several reasons for this error. In some cases, the system may recover without human intervention, however in most cases it will not. In some cases, the error can even indicate a task crash. These problems can be diagnosed by technical support provided enough information is collected to allow a detailed analysis of the specific case. The MQ-QWRITE error message is shown in Figure A-2 (the front panel displays an abridged version of the message). support.dell.com Error Messages A-7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156

support.dell.com
Error Messages
A-7
MQ-QWRITE Error
The software includes several message queues that are used for inter-task communi-
cation. Each queue holds a maximum of 64 messages. Under normal operations, a
task sends a message to another task on a queue, and occupies a slot in the queue.
After the message is received, its slot in the queue is open for another message.
If the receiving task does not run for a period of time, and the sender task sends more
than 64 messages to the same queue before the first message is processed by the
receiving task, the queue overflows and the message is discarded. This event causes
the
MQ-QWRITE
error to be printed on the display, as well as on the Telnet window, if
open. The error is also stored in the error log which can be viewed with the
errShow
command.
NOTE: The error log is cleared upon reboot.
There may be several reasons for this error. In some cases, the system may recover
without human intervention, however in most cases it will not. In some cases, the
error can even indicate a task crash.
These problems can be diagnosed by technical support provided enough information
is collected to allow a detailed analysis of the specific case.
The MQ-QWRITE error message is shown in Figure A-2 (the front panel displays an
abridged version of the message).
TASKSPAWN (0)
A task could not be
created.
Issue the
traceShow
command.
Contact customer support.
TIMEUSECNT (0)
A timer was not
released after
expiration.
Issue the
traceShow
command.
Contact customer support.
ZOMTIMKILL (0)
An attempt was
made to kill a timer
that was in ‘zombie’
state.
Issue the
traceShow
command.
Contact customer support.
ZOMTIMSET (0)
An attempt was
made to set a timer
that was in ‘zombie’
state.
Issue the
traceShow
command.
Contact customer support.
Table A-2.
Panic Errors
(continued)
Error
Severity
Explanation
Action