Ethereum pending

1. Code name: 0x0000000A

Description: incorrect environment. Shutdown code 0x0000000A: IRQL_ NOT_ LESS_ OR_ Error analysis: it is mainly caused by faulty drivers, defective or incompatible hardware and software. From a technical point of view, it shows that there is a high internal request level (IRQL) in kernel mode to access the memory address that it does not have permission to access. Example 1: when installing Windows 2000 / XP, in addition to checking whether the hardware meets the compatibility list, the following measures should also be taken 1) During the installation and startup process, when "setup is inspecting your computer & #39; When the message "s hardware configuration" appears, press F5. When prompted, specify the correct computer type and hardware abstraction layer (HAL). For general users (only one CPU is installed), please specify "standard PC Hal" 2) Turn off all cache and shadow settings, plug and play options and virus protection functions in CMOS settings 3) Disconnect the hardware that is not necessary for computer startup, including network card, built-in modem, sound card and second hard disk. At the same time, check whether the hard disk jumper is set as the main jumper, and check whether the optical drive jumper is correct 4) If you are upgrading from Windows 2000 to Windows XP, you need to uninstall all antivirus software and boot management software (such as Norton goback, etc.), remove all unnecessary hardware, and disconnect all USB devices and printers. Example 2: when using Windows 2000 / XP, (1) check the latest installed software and hardware drivers, uninstall or disable them. It is recommended to use safe mode to complete this task. If it is a driver, it is recommended to use the driver return function of Windows XP to restore the original driver 2) If windows fails to start, first try to use "last correct configuration" to solve the problem. If it is invalid, follow the method below. ★ Windows XP: use the installation CD to enter the recovery console and run% systemroot% & # 92; system32\ restore\ Rstrui. Exe command, and then follow the prompts to restore the system. Windows 2000: write down the file name shown in the blue screen information, find a computer with similar software and hardware configuration to your computer, open the "Registry Editor" and find the [H K E Y_ L O C A L _ M A C H I N E \ S Y S T E M\ CurrentControlSet\ Here is the registration information of each device and service in the system. Please check each information carefully, especially the "diskplayname" in the right pane. Some drivers will indicate the description of the device driver purpose here. In addition, there is the corresponding file name after the "imagepath" key value, which is also the key point of attention. You need to compare the file name you copied down. Use the windows 2000 installation CD to enter the recovery console, and then enter C: &# 92; WINNT\ System32 directory, enter "listsvc", press enter to list the services or devices installed in the current system, find and record the name of the service or device related to the newly installed hardware or software, and then enter "disable service or device name", press enter to stop it.

2. To avoid problems it is advisable that all network cards use the same driver. If they use different drivers, please take the following into consideration:

There are three driver-dependent methods for check whether a network card has a link or a network connection.

* MII link status detection
* Register in the driver netif_carrier
* ARP monitoring

It is very important that the used drivers support the same method. If this is not the case because e.g. the first network card driver only supports MII link status detection whereas the second driver just supports netif_carrier, the only solution is to replace the network card in order to use a different driver.

To find out what method is supported by your driver, proceed as follows:

* MII link status can be determined with the tools mii-tool or ethtool.

* In the case of netif_carrier and ARP monitoring, refer to the driver's source code to find out whether these methods are supported or not. The corresponding kernel sources must be installed for this purpose. Regarding netif_carrier, search exactly for this string in the driver's source code, e.g.

grep netif_carrier via-rhine.c

As for the ARP monitoring method, the driver must support either the register last_rx or trans_start. Thus, you can search in the driver's source code for:

grep "last_rx\|trans_start" via-rhine.c

Start with the setup only after having verified this.
Procere

In this sample scenario, two network cards will be combined by way of bonding mode=1 (active backup).

1. Configure your network cards with YaST. Allocate the IP address that must be used for the bonding device to one network card and a mmy IP address to the rest of network cards.

2. Copy the configuration of the network card with the right IP address to a file ifcfg-bond0.

cd /etc/sysconfig/network
cp ifcfg-eth-id--xx:xx:xx:xx:xx:01 ifcfg-bond0

3. Find out and write down the PCI IDs of all the involved network cards.

For example:

linux:~ # grep bus-pci ifcfg-eth-id--xx:xx:xx:xx:xx:01
_nm_name='bus-pci-0000:00:09.0'
linux:~ # grep bus-pci ifcfg-eth-id--xx:xx:xx:xx:xx:02
_nm_name='bus-pci-0000:00:0a.0'
linux:~ #

4. Edit the file ifcfg-bond0 previously created and insert the following lines.

BONDING_MASTER=yes
BONDING_SLAVE_0='bus-pci-0000:00:09.0'
BONDING_SLAVE_1='bus-pci-0000:00:0a.0'

Now insert the options for the bonding mole. Depending on what link detection method you are using, the line may look like this:
* MII link detection method
BONDING_MODULE_OPTS='miimon=100 mode=1 use_carrier=0'

* netif_carrier method
BONDING_MODULE_OPTS='miimon=100 mode=1 use_carrier=1'

* ARP monitoring method
BONDING_MODULE_OPTS='arp_interval=2500 arp_ip_target=192.168.1.1 mode=1'

5. Remove the old configuration files

linux:~ # rm ifcfg-eth-id--xx:xx:xx:xx:xx:01
linux:~ # rm ifcfg-eth-id--xx:xx:xx:xx:xx:02

6. Restart the network with

rcnetwork restart

Additional Information

Occasionally it has been experienced that not all network interfaces come up after a system reboot. To prevent this, the loading of the moles should start earlier ring the reboot process. The following procere is helpful in this case:

1. Edit the file /etc/sysconfig/kernel and add this line:

MODULES_LOADED_ON_BOOT="bcm5700"

2. Reboot the server and check the status of all network interfaces, using commands lspci and ifconfig.

3. If this method is not successful, edit the file /etc/sysconfig/kernel again and remove the line inserted at step 1. Modify the line containing the INITRD_MODULES statement; add the bcm5700 to this line. It should read like INITRD_MODULES="cdrom scsi_mod ide-cd ehci-hcd reiserfs bcm5700"

4. Call command mkinitrd

5. Reboot the server as in step 2

Another method is to delay the starting of the network interfaces after loading the moles. To do this, edit the file /etc/sysconfig/network/config and change the variable WAIT_FOR_INTERFACES to the wanted delay in seconds. To delay the interfaces 3 seconds, enter

WAIT_FOR_INTERFACES=3

Reboot the server to verify the success of this measure.

当然也可以采用一些简单的办法，例如直接修改 /etc/init.d/network 网络启动脚本
在start) 部分的结尾处添加 ipbonding 的手工脚本，例如：

ifconfig eth0 0.0.0.0
ifconfig eth1 0.0.0.0
modprobe bonding miimon=100 mode=1 use_carrier=1
ifconfig bond0 192.168.1.123 netmask 255.255.255.0
ifenslave bond0 eth0
ifenslave bond0 eth1
route add default gw 192.168.1.1

然后在 stop) 部分开始考虑添加：
ifdown bond0
rmmod bonding