Troubleshooting Linux operating system panic treatment methods

(B) client configuration: (1). check whether the client is installed, if not installed rpm-qnetdump in CD RedFlag/RPMS/directory to find the start package, netdum execute the command: rpm-ivhnetdump-x.x.x.rpm (x is the version number) installed.

(2). edit file/etc/sysconfig/netdump, add the following line: DEV = et0 NETDUMPADDR = 172.16.81.182 NETDUMPMACADDR = 00: 0C: 29 79: F4: E0 172.16.81.182 means netdump-server address. (3). running the following command, enter the password when prompted: servicenetdumppropagate (4). the open client: chkconfignetdumpon (5). to run the client: servicenetdumpstart (6). the test to test the netdump configuration is correct, the netdump client to do the following: cp/usr/share/doc/netdump-xxxxxx/crash.c. Gcc-DKERNEL-DMODULE-I/lib/modules/$ (uname-r)/build/include-ccras.c insmod./cras.o this will crash the system, you will <客户端ip>/var/crash/netdump-Server/directory to see a core dump. When the client is to dump the data to the server, you will see a "vmcore-incomplete" file. When a dump is complete, the file is renamed into "vmcore". "Vmcore" file size will change, you may reach several GB in a memory is 512M system, the above test will produce approximately 510M of vmcore file. How to determine whether the network card support the netdump? kernel debugging tool netdump need the drivers support netpoll function. Netpoll is intended to enable the kernel on a network and i/o subsystem is not yet completely available, still be able to send and receive packets. Mainly used for the network console (netconsole) and remote kernel debugging (KGDBoE). Implementation, mainly netpoll is to implement kernel in poll_controller function which defines: void (* poll_controller) (structnet_device * dev). This function is used in the missing device interrupts, can respond to the controller. Almost all poll_controller functions are defined as follows: voidmy_poll_controller (structnet_device * dev) {disable_device_interrupt (dev); call_interrupt_handler(dev->irq,dev); enable_device_interrupt(dev); }