firmware

t4fwdebugtool flowc 10000

xxd -s 0x80000 -l 512 /sys/kernel/debug/cxgb4/0002\:01\:00.4/flash

WHQL

reinstall

provide IPV6 address of PEER in the test GUI when it asked.
disable all NDIS interfaces and run the test.

Enable flow control under debuuger

NDIS registry key to enable flowcontrol in the presence of Debug enabled:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NDIS\Parameters\[DWORD]AllowFlowControlUnderDebugger.

Set this key to 1 and reboot the machine to enable Tx-Flow control with debugger enabled.

REG

which bit we want to set select that in binary mode
convert it to hex
add to the existing value



original : 0x10002
mod : 0x1000a
 cxgbtool eth0 reg 0x7d8c=0x1000a

[root@t6fpga5 ~]# reg6.py -f TP_ERR_CONFIG
[0x07d8c] TP_ERR_CONFIG                                 0x0001000a [     65546]
  [31:31]   TnlErrorFPMA                                0x0        [         0]
  [30:30]   TnlErrorPing                                0x0        [         0]
  [29:29]   TnlErrorCsum                                0x0        [         0]
  [28:28]   TnlErrorCsumIP                              0x0        [         0]
  [27:27]   TnlErrorOpaque                              0x0        [         0]
  [26:26]   TnlErrorIp6Opt                              0x0        [         0]
  [25:25]   TnlErrorTcpOpt                              0x0        [         0]
  [24:24]   TnlErrorPktLen                              0x0        [         0]
  [23:23]   TnlErrorTcpHdrLen                           0x0        [         0]
  [22:22]   TnlErrorIpHdrLen                            0x0        [         0]
  [21:21]   TnlErrorEthHdrLen                           0x0        [         0]
  [20:20]   TnlErrorAttack                              0x0        [         0]
  [19:19]   TnlErrorFrag                                0x0        [         0]
  [18:18]   TnlErrorIpVer                               0x0        [         0]
  [17:17]   TnlErrorMac                                 0x0        [         0]
  [16:16]   TnlErrorAny                                 0x1        [         1]
  [15:15]   DropErrorFPMA                               0x0        [         0]
  [14:14]   DropErrorPing                               0x0        [         0]
  [13:13]   DropErrorCsum                               0x0        [         0]
  [12:12]   DropErrorCsumIP                             0x0        [         0]
  [11:11]   DropErrorOpaque                             0x0        [         0]
  [10:10]   DropErrorIp6Opt                             0x0        [         0]
  [ 9: 9]   DropErrorTcpOpt                             0x0        [         0]
  [ 8: 8]   DropErrorPktLen                             0x0        [         0]
  [ 7: 7]   DropErrorTcpHdrLen                          0x0        [         0]
  [ 6: 6]   DropErrorIpHdrLen                           0x0        [         0]
  [ 5: 5]   DropErrorEthHdrLen                          0x0        [         0]
  [ 4: 4]   DropErrorAttack                             0x0        [         0]
  [ 3: 3]   DropErrorFrag                               0x1        [         1]
  [ 2: 2]   DropErrorIpVer                              0x0        [         0]
  [ 1: 1]   DropErrorMac                                0x1        [         1]
  [ 0: 0]   DropErrorAny                                0x0        [         0]


[root@t6fpga5 ~]# reg6.py -f TP_ERR_CONFIG[DropErrorFrag]=0
0x10002 [65538]

[root@t6fpga5 ~]# reg6.py -f TP_ERR_CONFIG[DropErrorFrag]=1
0x1000a [65546]


working
=======

[root@t6fpga5 t5tools]# reg6.py -f TP_ERR_CONFIG[DropErrorFrag]=1
0x1000a [65546]
[root@t6fpga5 t5tools]# reg6.py tp_eside_config[FragmentDrop]=1
0x2086666 [34104934]

Linux bonding

Linux Network bonding – setup

Linux network Bonding is a creation of a single bonded interface by combining 2 or more Ethernet interfaces. This helps in high availability of your network interface and offers performance improvements on your data traffic flow. Bonding is also referred as nic trunking or teaming.

Bonding allows you to aggregate multiple ports into a single group, effectively combining the bandwidth into a single connection. Bonding also allows you to create multi-gigabit pipes to transport traffic through the highest traffic areas of your network. For example, you can aggregate three megabits ports into a three-megabits trunk port. That is equivalent with having one interface with three megabytes speed

Steps for bonding in Oracle Enterprise Linux and Redhat Enterprise Linux are as follows..

Step 1.

Create the file ifcfg-bond0 with the IP address, netmask and gateway. Shown below is my test bonding config file.

# cat /etc/sysconfig/network-scripts/ifcfg-bond0
DEVICE=bond0 
IPADDR=192.168.1.12 
NETMASK=255.255.255.0 
GATEWAY=192.168.1.1 
USERCTL=no 
BOOTPROTO=none 
ONBOOT=yes

Step 2.
Modify eth0, eth1 and eth2 configuration as shown below. Comment out, or remove the ip address, netmask, gateway and hardware address from each one of these files, since settings should only come from the ifcfg-bond0 file above. Make sure you add the MASTER and SLAVE configuration in these files.

# cat /etc/sysconfig/network-scripts/ifcfg-eth0
DEVICE=eth0 
BOOTPROTO=none 
ONBOOT=yes 
# Settings for Bond 
MASTER=bond0 
SLAVE=yes

# cat /etc/sysconfig/network-scripts/ifcfg-eth1
DEVICE=eth1 
BOOTPROTO=none  
ONBOOT=yes 
USERCTL=no 
# Settings for bonding 
MASTER=bond0 
SLAVE=yes

# cat /etc/sysconfig/network-scripts/ifcfg-eth2
DEVICE=eth2 
BOOTPROTO=none 
ONBOOT=yes 
MASTER=bond0 
SLAVE=yes

Step 3.
Set the parameters for bond0 bonding kernel module. Select the network bonding mode based on you need. The modes are

• mode=0 (Balance Round Robin)
• mode=1 (Active backup)
• mode=2 (Balance XOR)
• mode=3 (Broadcast)
• mode=4 (802.3ad)
• mode=5 (Balance TLB)
• mode=6 (Balance ALB)

Add the following lines to /etc/modprobe.conf

# bonding commands 
alias bond0 bonding 
options bond0 mode=1 miimon=100

Step 4.

Load the bond driver module from the command prompt.

# modprobe bonding

Step 5.

Restart the network, or restart the computer.

# service network restart # Or restart computer

When the machine boots up check the proc settings.

# cat /proc/net/bonding/bond0 
Ethernet Channel Bonding Driver
Bonding Mode: adaptive load balancing 
Primary Slave: None 
Currently Active Slave: eth2 
MII Status: up 
MII Polling Interval (ms): 100 
Up Delay (ms): 0 
Down Delay (ms): 0
Slave Interface: eth2 
MII Status: up 
Link Failure Count: 0 
Permanent HW addr: 00:13:72:80: 62:f0

Look at ifconfig -a and check that your bond0 interface is active. You are done!.

To verify whether the failover bonding works..

• Do an ifdown eth0 and check /proc/net/bonding/bond0 and check the “Current Active slave”.
• Do a continuous ping to the bond0 ipaddress from a different machine and do a ifdown the active interface. The ping should not break.

start netconsole

DUT:

modprobe netconsole netconsole=20000@10.192.193.105/br0,20000@10.192.193.26/00:25:90:52:03:74

local Ip and interface name, remote interface ip and mac

PEER:

nc -dul 20000 | tee t6fpga5.txt &

getting details on system freeze:

1) Please enable NMI watchdog in the BIOS settings.

2) Add below line to sysctl.conf

kernel.unknown_nmi_panic = 1

3) Append nmi_watchdog=1 to kernel command line

title Red Hat Enterprise Linux Server (2.6.18-128.el5)

        root (hd0,0)

        kernel /vmlinuz-2.6.18-128.el5 ro root=/dev/sda nmi_watchdog=1

        initrd /initrd-2.6.18-128.el5.img

4) Enable kdump

5) Try to get the crash logs from netconsole or serial console.

virt-manager

Change default storage path:

virsh
pool-destroy default
pool-undefine default
pool-define-as --name default --type dir --target /rum/media/user1/partition1
pool-autostart default
pool-build default
pool-start default

workbench GUI

localhost:~ # cat .vnc/xstartup
#!/bin/sh

#xrdb $HOME/.Xresources
#xsetroot -solid grey
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#twm &

unset SESSION_MANAGER
 exec /etc/X11/xinit/xinitrc
xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &