Sponsored Content
Operating Systems AIX Receiving: 4B436A3D 0313233216 T H fscsi0 LINK ERROR Post 302969163 by Devyn on Friday 18th of March 2016 10:32:50 PM
Old 03-18-2016
I'm compiling another targeting system. Blew away the old one. I need to get more logging at the time the Emulex / IBM system throws these and trying to eliminate some software as possible culprits.

After each failure, the LUN presented to the initiator is inaccessible until I restart SCST which in turn pulls down the QLogic drivers then brings them up again. This particular event is hinting that it isn't the IBM system or the Emulex cards, it's likely the target software, QLogic card or the PCIe bus.

I will be increasing the buffer to test with as soon as I'm done.

Cheers,
DH
 

10 More Discussions You Might Find Interesting

1. Programming

Link Edit Error, Help!!!!!

Hi, After I installed gcc on my machine and issued a command to compile a program, I did gcc -c 'prog'.c The object file was created, then I did gcc -o 'prog' 'prog'.o Then I got this error message I have been reading man pages and searching the internet but have not been able to... (1 Reply)
Discussion started by: rachael
1 Replies

2. Linux

link error problem

Dear linuxers, I'm a novice in C++ programming. I wrote a ReadFile class in file ReadFile.cpp. After that, I wrote a test.cpp, which contains a main function, to test whether my class work well. I follow the following steps to compile the ReadFile.cpp file. g++296 -c ReadFile.cpp -o... (4 Replies)
Discussion started by: niukun
4 Replies

3. UNIX for Dummies Questions & Answers

Receiving error on Unix server-- java.lang.UnsatisfiedLinkError: registerNatives

Hi all, This is my first shell script, so I'm hoping the problem is that I'm just missing something, and not something bigger. I have a Java application that I wrote in WSAD that reads data from an Excel file and inserts values into a DB2 database. I'm able to run it successfully in WSAD. I... (4 Replies)
Discussion started by: loveToBlade
4 Replies

4. Shell Programming and Scripting

Receiving error: ./ang.ksh[35]: 0403-057 Syntax error at line 116 : `done' is not expected.

Hi All I am quite new to Unix. Following is a shell script that i have written and getting the subject mentioned error. #!/bin/ksh #------------------------------------------------------------------------- # File: ang_stdnld.ksh # # Desc: UNIX shell script to extract Store information.... (3 Replies)
Discussion started by: amitsinha
3 Replies

5. Shell Programming and Scripting

Why am i receiving too many argument error with this?

#!/bin/bash while do codes done it says line 2: [: too many arguments why? (4 Replies)
Discussion started by: garfish
4 Replies

6. Programming

g++ fails to link to static library when compilation and link in single command

Hello All, I've encountered a strange behaviour from g++ that doesn't make sense to me. Maybe you can shed some light on it: I have a bunch of source files and want to compile them and link them with a static library liba.a located in /usr/local/lib64 into an executable Approach 1 works... (0 Replies)
Discussion started by: magelord
0 Replies

7. AIX

Error opening device: /dev/fscsi0

Hello, One one of my AIX boxes I'm having the following errror: fcstat fcs0: Port Speed (supported): 4 GBIT Error opening device: /dev/fscsi0 errno: 0000003d Has anyone encountered similar errors? Thank you! (1 Reply)
Discussion started by: aixn00b
1 Replies

8. UNIX for Dummies Questions & Answers

[Solved] Symbolic link not allowed or link target not accessible

Hi everybody, I read about treads realted to this issue but they did not resovle issue given below. Please help me resolve issue given below I have html file under /srv/www/htdocs/actual_folder ls actual_folder/ test.html and following link works... (0 Replies)
Discussion started by: newbielgn
0 Replies

9. Solaris

/var/adm/messages (interface turned off/restored) and link up & link down message.

Hi All I am facing an issue with our new solaris machine. in /var/adm/messages root@Prod-App1:/var/tmp# root@Prod-App1:/var/tmp# root@Prod-App1:/var/tmp# cat /var/adm//messages Apr 20 03:10:01 Prod-App1 syslogd: line 25: WARNING: loghost could not be resolved Apr 20 08:24:18 Prod-App1... (0 Replies)
Discussion started by: javeedkaleem
0 Replies

10. Solaris

/var/adm/messages (insterface turned off/restored) and link up & link down message.

Hi All I am facing an issue with our new solaris machine. in /var/adm/messages Apr 22 16:43:05 Prod-App1 in.routed: interface net0 to 172.16.101.1 turned off Apr 22 16:43:33 Prod-App1 mac: NOTICE: nxge0 link up, 1000 Mbps, full duplex Apr 22 16:43:34 Prod-App1 mac: NOTICE: nxge0 link... (2 Replies)
Discussion started by: javeedkaleem
2 Replies
BXE(4)							   BSD Kernel Interfaces Manual 						    BXE(4)

NAME
bxe -- QLogic NetXtreme II Ethernet 10Gb PCIe adapter driver SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file: device bxe Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_bxe_load="YES" DESCRIPTION
The bxe driver provides support for PCIe 10Gb Ethernet adapters based on the QLogic NetXtreme II family of 10Gb chips. The driver supports Jumbo Frames, VLAN tagging, checksum offload (IPv4, TCP, UDP, IPv6-TCP, IPv6-UDP), MSI-X interrupts, TCP Segmentation Offload (TSO), Large Receive Offload (LRO), and Receive Side Scaling (RSS). HARDWARE
The bxe driver provides support for various NICs based on the QLogic NetXtreme II family of 10Gb Ethernet controller chips, including the following: o QLogic NetXtreme II BCM57710 10Gb o QLogic NetXtreme II BCM57711 10Gb o QLogic NetXtreme II BCM57711E 10Gb o QLogic NetXtreme II BCM57712 10Gb o QLogic NetXtreme II BCM57712-MF 10Gb o QLogic NetXtreme II BCM57800 10Gb o QLogic NetXtreme II BCM57800-MF 10Gb o QLogic NetXtreme II BCM57810 10Gb o QLogic NetXtreme II BCM57810-MF 10Gb o QLogic NetXtreme II BCM57840 10Gb / 20Gb o QLogic NetXtreme II BCM57840-MF 10Gb CONFIGURATION
There a number of configuration parameters that can be set to tweak the driver's behavior. These parameters can be set via the loader.conf(5) file to take affect during the next system boot. The following parameters affect ALL instances of the driver. hw.bxe.debug DEFAULT = 0 Sets the default logging level of the driver. See the Diagnostics and Debugging section below for more details. hw.bxe.interrupt_mode DEFAULT = 2 Sets the default interrupt mode: 0=IRQ, 1=MSI, 2=MSIX. If set to MSIX and allocation fails, the driver will roll back and attempt MSI allocation. If MSI allocation fails, the driver will roll back and attempt fixed level IRQ allocation. If IRQ allocation fails, then the driver load fails. With MSI/MSIX, the driver attempts to allocate a vector for each queue in addition to one more for default processing. hw.bxe.queue_count DEFAULT = 4 Sets the default number of fast path packet processing queues. Note that one MSI/MSIX interrupt vector is allocated per-queue. hw.bxe.max_rx_bufs DEFAULT = 0 Sets the maximum number of receive buffers to allocate per-queue. Zero(0) means to allocate a receive buffer for every buffer descriptor. By default this equates to 4080 buffers per-queue which is the maximum value for this config parameter. hw.bxe.hc_rx_ticks DEFAULT = 25 Sets the number of ticks for host interrupt coalescing in the receive path. hw.bxe.hc_tx_ticks DEFAULT = 50 Sets the number of ticks for host interrupt coalescing in the transmit path. hw.bxe.rx_budget DEFAULT = 0xffffffff Sets the maximum number of receive packets to process in an interrupt. If the budget is reached then the remaining/pending packets will be processed in a scheduled taskqueue. hw.bxe.max_aggregation_size DEFAULT = 32768 Sets the maximum LRO aggregration byte size. The higher the value the more packets the hardware will aggregate. Maximum is 65K. hw.bxe.mrrs DEFAULT = -1 Sets the PCI MRRS: -1=Auto, 0=128B, 1=256B, 2=512B, 3=1KB hw.bxe.autogreeen DEFAULT = 0 Set AutoGrEEEN: 0=HW_DEFAULT, 1=FORCE_ON, 2=FORCE_OFF hw.bxe.udp_rss DEFAULT = 0 Enable/Disable 4-tuple RSS for UDP: 0=DISABLED, 1=ENABLED Special care must be taken when modifying the number of queues and receive buffers. FreeBSD imposes a limit on the maximum number of mbuf(9) allocations. If buffer allocations fail, the interface initialization will fail and the interface will not be usable. The driver does not make a best effort for buffer allocations. It is an all or nothing effort. You can tweak the mbuf(9) allocation limit using sysctl(8) and view the current usage with netstat(1) as follows: # netstat -m # sysctl kern.ipc.nmbclusters # sysctl kern.ipc.nmbclusters=<#> There are additional configuration parameters that can be set on a per-instance basis to dynamically override the default configuration. The '#' below must be replaced with the driver instance / interface unit number: dev.bxe.#.debug DEFAULT = 0 Sets the default logging level of the driver instance. See hw.bxe.debug above and the Diagnostics and Debugging section below for more details. dev.bxe.#.rx_budget DEFAULT = 0xffffffff Sets the maximum number of receive packets to process in an interrupt for the driver instance. See hw.bxe.rx_budget above for more details. Additional items can be configured using ifconfig(8): MTU - Maximum Transmission Unit DEFAULT = 1500 RANGE = 46-9184 # ifconfig bxe# mtu <n> Promiscuous Mode DEFAULT = OFF # ifconfig bxe# [ promisc | -promisc ] Rx/Tx Checksum Offload DEFAULT = RX/TX CSUM ON Note that the Rx and Tx settings are not independent. # ifconfig bxe# [ rxcsum | -rxcsum | txcsum | -txcsum ] TSO - TCP Segmentation Offload DEFAULT = ON # ifconfig bxe# [ tso | -tso | tso6 | -tso6 ] LRO - TCP Large Receive Offload DEFAULT = ON # ifconfig bxe# [ lro | -lro ] DIAGNOSTICS AND DEBUGGING
There are many statistics exposed by bxe via sysctl(8). To dump the default driver configuration: # sysctl -a | grep hw.bxe To dump every instance's configuration and detailed statistics: # sysctl -a | grep dev.bxe To dump information for a single instance (replace the '#' with the driver instance / interface unit number): # sysctl -a | grep dev.bxe.# To dump information for all the queues of a single instance: # sysctl -a | grep dev.bxe.#.queue To dump information for a single queue of a single instance (replace the additional '#' with the queue number): # sysctl -a | grep dev.bxe.#.queue.# The bxe driver has the ability to dump a ton of debug messages to the system log. The default level of logging can be set with the hw.bxe.debug sysctl(8). Take care with this setting as it can result in too many logs being dumped. Since this parameter is the default one, it affects every instance and will dramatically change the timing in the driver. A better alternative to aid in debugging is to dynami- cally change the debug level of a specific instance with the dev.bxe.#.debug sysctl(8). This allows you to turn on/off logging of various debug groups on-the-fly. The different debug groups that can be toggled are: DBG_LOAD 0x00000001 /* load and unload */ DBG_INTR 0x00000002 /* interrupt handling */ DBG_SP 0x00000004 /* slowpath handling */ DBG_STATS 0x00000008 /* stats updates */ DBG_TX 0x00000010 /* packet transmit */ DBG_RX 0x00000020 /* packet receive */ DBG_PHY 0x00000040 /* phy/link handling */ DBG_IOCTL 0x00000080 /* ioctl handling */ DBG_MBUF 0x00000100 /* dumping mbuf info */ DBG_REGS 0x00000200 /* register access */ DBG_LRO 0x00000400 /* lro processing */ DBG_ASSERT 0x80000000 /* debug assert */ DBG_ALL 0xFFFFFFFF /* flying monkeys */ For example, to debug an issue in the receive path on bxe0: # sysctl dev.bxe.0.debug=0x22 When finished turn the logging back off: # sysctl dev.bxe.0.debug=0 SUPPORT
For support questions please contact your QLogic approved reseller or QLogic Technical Support at http://support.qlogic.com, or by E-mail at <support@qlogic.com>. SEE ALSO
netstat(1), altq(4), arp(4), netintro(4), ng_ether(4), vlan(4), ifconfig(8) HISTORY
The bxe device driver first appeared in FreeBSD 9.0. AUTHORS
The bxe driver was written by Eric Davis <edavis@broadcom.com>, David Christensen <davidch@broadcom.com>, and Gary Zambrano <zambrano@broadcom.com>. BSD
April 29, 2012 BSD
All times are GMT -4. The time now is 05:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy