Fujitsu B23Q8YA-G-02-F Manuel D’Utilisation

Page de 52
 
 
 
   
27 
Message Cause 
Workaround 
 -role 
master: Communicate as Master. 
slave: Communicate as Slave. 
 
Illegal value for 
[ParameterName]. 
Error found in the parameter of 
definition file (fjgi.conf). 
Check whether the definition file is 
correct. 
fail to FragCount 
Abnormalities were found in message 
fragmentation. 
Multiple fragments in 
descriptor area 
Abnormalities were found in message 
fragmentation. 
bind to 802.2 failed 
Using protocol was different. 
Please try re-activation of interface. If 
this is not a cause, report that to your 
authorized dealer. 
pci_config_setup_failed PCI 
configuration space couldn't be 
obtained. 
Installed physical memory may be 
insufficient or hardware is failed. If 
memory insufficient is not a cause, 
report that to your authorized dealer. 
soft state alloc failed. 
Driver  internal  resources  cannot  be     
obtained. 
Allocation of descriptor 
memory failed 
Driver internal resources on DMA 
couldn't be allocated. 
fail to 
ddi_dma_bind_handle 
DMA resources couldn't be allocated. 
Could not allocate DMA 
handle 
Could not bind descriptor 
memory 
DMA resources couldn't be allocated. 
fjgiallocthings failed !! 
DMA resources couldn't be allocated. 
Unable to map adapter 
registers. 
Mapping of register went wrong. 
ddi_get_iblock_cookie-E
RROR 
Interrupt resources couldn't be 
allocated. 
Unable to install interrupt 
routine. 
Unable to install interrupt routine.   
Interrupt resources couldn't be 
allocated. 
ddi_create_minor_node 
failed 
Creation of a device file went wrong. 
ATTACH failed 
OPEN failed: ENOMEM 
Driver resources couldn't be allocated. 
CLOSE: stream==NULL 
Driver resources couldn't be freed. 
fjgi_param_register error 
The  ndd parameter couldn't be 
allocated. 
fjgi_board_alloc_mem 
failed !! 
Driver resources couldn't be allocated. 
Error filling TX ring 
Transmit 
resources 
couldn't 
be 
allocated. 
status block can't alloced !! 
Status information resources couldn't 
be allocated. 
status block can't alloced 
handle! 
Status information resources couldn't 
be allocated. 
status block can't bind 
handle! 
Status information resources couldn't 
be allocated. 
Installed physical memory may be 
insufficient. If this is not a cause, 
report them to your authorized dealer.