From: Jeff Moyer <jmoyer> Date: Thu, 19 May 2005 10:57:15 -0400 Subject: [taroon patch] Add docs detailing which drivers support netconsole Tracking: 0982.jmoyer.netconsole-drvrs-doc.patch Archives: 2005-May/msg00359.html Status: committed in -32.5.EL ------------------------------------------------------------------------ Hi, Currently, our support staff tell customers that they can determine which adapters support netconsole by doing the following: "A simple way to check what drivers have this capability is to install the kernel-source package and search the source code in /usr/src/kernel-<version> for the definition HAVE_POLL_CONTROLLER." This is so incredibly poor it hurts. Here is a patch that will add the supported driver list to the Documentation/networking directory, which in turn gets put into the kernel-doc package. Please ACK. -Jeff [updated by petrides on 19-May-2005] --- linux-2.4.21/Documentation/networking/netconsole.txt.orig +++ linux-2.4.21/Documentation/networking/netconsole.txt @@ -0,0 +1,26 @@ +The netconsole module provides 3 pieces of functionality: + + 1) generation of syslog messages which are delivered to a remote syslog + server + 2) generation of netconsole messages which are delivered to a remote + netdump server + 3) a network kernel crash dump facility + +The configuration for the module is specified in the /etc/sysconfig/netdump +file, which is self-documented. Once the parameters are specified in that +provided you have installed the netdump rpm. + +Network drivers must implement a special hook in order to work with +netconsole. The following drivers implement this functionality, and thus +can be used in conjunction with netconsole: + + 3c59x + b44 + e100 + e1000 + eepro100 + pcnet32 + tg3 + tlan + tulip
A fix for this problem was committed to the RHEL3 U6 patch pool on 26-May-2005 (in kernel version 2.4.21-32.5.EL).
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2005-663.html