Documentation/kmsg/s390/qeth

   1 /*?
   2  * Text: "%s: The LAN is offline\n"
   3  * Severity: Warning
   4  * Parameter:
   5  *   @1: bus ID of the qeth device
   6  * Description:
   7  * A start LAN command was sent by the qeth device driver but the physical or
   8  * virtual adapter has not started the LAN. The LAN might take a few seconds
   9  * to become available.
  10  * User action:
  11  * Check the status of the qeth device, for example, with the lsqeth command.
  12  * If the device does not become operational within a few seconds, initiate a
  13  * recovery process, for example, by writing '1' to the 'recover' sysfs
  14  * attribute of the device.
  15  */
  16
  17 /*?
  18  * Text: "%s: A recovery process has been started for the device\n"
  19  * Severity: Warning
  20  * Parameter:
  21  *   @1: bus ID of the qeth device
  22  * Description:
  23  * A recovery process was started either by the qeth device driver or through
  24  * a user command.
  25  * User action:
  26  * Wait until a message indicates the completion of the recovery process.
  27  */
  28
  29 /*?
  30  * Text: "%s: The qeth device driver failed to recover an error on the device\n"
  31  * Severity: Warning
  32  * Parameter:
  33  *   @1: bus ID of the qeth device
  34  * Description:
  35  * The qeth device driver performed an automatic recovery operation to recover
  36  * an error on a qeth device. The recovery operation failed.
  37  * User action:
  38  * Try the following actions in the given order: i) Check the status of the
  39  * qeth device, for example, with the lsqeth command. ii) Initiate a recovery
  40  * process by writing '1' to the 'recover' sysfs attribute of the device.
  41  * iii) Ungroup and regroup the subchannel triplet of the device. vi) Reboot
  42  * Linux. v) If the problem persists, gather Linux debug data and report the
  43  * problem to your support organization.
  44  */
  45
  46 /*?
  47  * Text: "%s: Device recovery failed to restore all offload features\n"
  48  * Severity: Warning
  49  * Parameter:
  50  *   @1: bus ID of the qeth device
  51  * Description:
  52  * The qeth device driver performed a recovery operation on a qeth device. Part
  53  * of the recovery is to restore the offload features that were enabled before
  54  * the recovery. At least one of those offload features could not be restored.
  55  * User action:
  56  * Check which offload features are enabled on the device, for example with
  57  * the "ethtool -k" command. Try to explicitly re-enable the missing offload
  58  * features for the device, for example with the "ethtool -K" command.
  59  */
  60
  61 /*?
  62  * Text: "%s: The link for interface %s on CHPID 0x%X failed\n"
  63  * Severity: Warning
  64  * Parameter:
  65  *   @1: bus ID of the qeth device
  66  *   @2: network interface name
  67  *   @3: CHPID
  68  * Description:
  69  * A network link failed. A possible reason for this error is that a physical
  70  * network cable has been disconnected.
  71  * User action:
  72  * Ensure that the network cable on the adapter hardware is connected properly.
  73  * If the connection is to a guest LAN, ensure that the device is still coupled
  74  * to the guest LAN.
  75  */
  76
  77 /*?
  78  * Text: "%s: The link for %s on CHPID 0x%X has been restored\n"
  79  * Severity: Informational
  80  * Parameter:
  81  *   @1: bus ID of the qeth device
  82  *   @2: network interface name
  83  *   @3: CHPID
  84  * Description:
  85  * A failed network link has been re-established. A device recovery is in
  86  * progress.
  87  * User action:
  88  * Wait until a message indicates the completion of the recovery process.
  89  */
  90
  91 /*?
  92  * Text: "%s: A hardware operation timed out on the device\n"
  93  * Severity: Warning
  94  * Parameter:
  95  *   @1: bus ID of the qeth device
  96  * Description:
  97  * A hardware operation timed out on the qeth device.
  98  * User action:
  99  * Check the status of the qeth device, for example, with the lsqeth command.
 100  * If the device is not operational, initiate a recovery process, for example,
 101  * by writing '1' to the 'recover' sysfs attribute of the device.
 102  */
 103
 104 /*?
 105  * Text: "%s: The adapter hardware is of an unknown type\n"
 106  * Severity: Error
 107  * Parameter:
 108  *   @1: bus ID of the qeth device
 109  * Description:
 110  * The qeth device driver does not recognize the adapter hardware. The cause
 111  * of this problem could be a hardware error or a Linux level that does not
 112  * support your adapter hardware.
 113  * User action:
 114  * i) Investigate if your adapter hardware is supported by your Linux level.
 115  * Consider using hardware that is supported by your Linux level or upgrading
 116  * to a Linux level that supports your hardware. ii) Install the latest
 117  * firmware on your adapter hardware. iii) If the problem persists and is not
 118  * caused by a version mismatch, contact IBM support.
 119  */
 120
 121 /*?
 122  * Text: "%s: The adapter is used exclusively by another host\n"
 123  * Severity: Error
 124  * Parameter:
 125  *   @1: bus ID of the qeth device
 126  * Description:
 127  * The qeth adapter is exclusively used by another host.
 128  * User action:
 129  * Use another qeth adapter or configure this one not exclusively to a
 130  * particular host.
 131  */
 132
 133 /*?
 134  * Text: "%s: QDIO reported an error, rc=%i\n"
 135  * Severity: Warning
 136  * Parameter:
 137  *   @1: bus ID of the qeth device
 138  *   @2: return code
 139  * Description:
 140  * The QDIO subsystem reported an error.
 141  * User action:
 142  * Check for related QDIO errors. Check the status of the qeth device, for
 143  * example, with the lsqeth command. If the device is not operational, initiate
 144  * a recovery process, for example, by writing '1' to the 'recover' sysfs
 145  * attribute of the device.
 146  */
 147
 148 /*?
 149  * Text: "%s: There is no kernel module to support discipline %d\n"
 150  * Severity: Error
 151  * Parameter:
 152  *   @1: bus ID of the qeth device
 153  *   @2: discipline
 154  * Description:
 155  * The qeth device driver or a user command requested a kernel module for a
 156  * particular qeth discipline. Either the discipline is not supported by the
 157  * qeth device driver or the requested module is not available to your Linux
 158  * system.
 159  * User action:
 160  * Check if the requested discipline module has been compiled into the kernel
 161  * or is present in /lib/modules/<version>/kernel/drivers/s390/net.
 162  */
 163
 164 /*?
 165  * Text: "Initializing the qeth device driver failed\n"
 166  * Severity: Error
 167  * Parameter:
 168  * Description:
 169  * The base module of the qeth device driver could not be initialized.
 170  * User action:
 171  * See errno.h to determine the reason for the error.
 172  * i) Reboot Linux. ii) If the problem persists, gather Linux debug data and
 173  * report the problem to your support organization.
 174  */
 175
 176 /*?
 177  * Text: "%s: Registering IP address %s failed\n"
 178  * Severity: Warning
 179  * Parameter:
 180  *   @1: bus ID of the qeth device
 181  *   @2: IP address
 182  * Description:
 183  * An IP address could not be registered with the network adapter.
 184  * User action:
 185  * Check if another operating system instance has already registered the
 186  * IP address with the same network adapter or at the same logical IP subnet.
 187  */
 188
 189 /*?
 190  * Text: "%s: Reading the adapter MAC address failed\n"
 191  * Severity: Warning
 192  * Parameter:
 193  *   @1: bus ID of the qeth device
 194  * Description:
 195  * The qeth device driver could not read the MAC address from the network
 196  * adapter.
 197  * User action:
 198  * Ungroup and regroup the subchannel triplet of the device. If this does not
 199  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 200  * debug data and report the problem to your support organization.
 201  */
 202
 203 /*?
 204  * Text: "%s: Starting ARP processing support for %s failed\n"
 205  * Severity: Warning
 206  * Parameter:
 207  *   @1: bus ID of the qeth device
 208  *   @2: network interface name
 209  * Description:
 210  * The qeth device driver could not start ARP support on the network adapter.
 211  * User action:
 212  * Ungroup and regroup the subchannel triplet of the device. If this does not
 213  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 214  * debug data and report the problem to your support organization.
 215  */
 216
 217 /*?
 218  * Text: "%s: Starting IP fragmentation support for %s failed\n"
 219  * Severity: Warning
 220  * Parameter:
 221  *   @1: bus ID of the qeth device
 222  *   @2: network interface name
 223  * Description:
 224  * The qeth device driver could not start IP fragmentation support on the
 225  * network adapter.
 226  * User action:
 227  * Ungroup and regroup the subchannel triplet of the device. If this does not
 228  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 229  * debug data and report the problem to your support organization.
 230  */
 231
 232 /*?
 233  * Text: "%s: Starting VLAN support for %s failed\n"
 234  * Severity: Warning
 235  * Parameter:
 236  *   @1: bus ID of the qeth device
 237  *   @2: network interface name
 238  * Description:
 239  * The qeth device driver could not start VLAN support on the network adapter.
 240  * User action:
 241  * None if you do not require VLAN support. If you need VLAN support,
 242  * ungroup and regroup the subchannel triplet of the device. If this does not
 243  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 244  * debug data and report the problem to your support organization.
 245  */
 246
 247 /*?
 248  * Text: "%s: Starting multicast support for %s failed\n"
 249  * Severity: Warning
 250  * Parameter:
 251  *   @1: bus ID of the qeth device
 252  *   @2: network interface name
 253  * Description:
 254  * The qeth device driver could not start multicast support on the network
 255  * adapter.
 256  * User action:
 257  * Ungroup and regroup the subchannel triplet of the device. If this does not
 258  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 259  * debug data and report the problem to your support organization.
 260  */
 261
 262 /*?
 263  * Text: "%s: Activating IPv6 support for %s failed\n"
 264  * Severity: Error
 265  * Parameter:
 266  *   @1: bus ID of the qeth device
 267  *   @2: network interface name
 268  * Description:
 269  * The qeth device driver could not activate IPv6 support on the network
 270  * adapter.
 271  * User action:
 272  * None if you do not require IPv6 communication. If you need IPv6 support,
 273  * ungroup and regroup the subchannel triplet of the device. If this does not
 274  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 275  * debug data and report the problem to your support organization.
 276  */
 277
 278 /*?
 279  * Text: "%s: Enabling the passthrough mode for %s failed\n"
 280  * Severity: Warning
 281  * Parameter:
 282  *   @1: bus ID of the qeth device
 283  *   @2: network interface name
 284  * Description:
 285  * The qeth device driver could not enable the passthrough mode on the
 286  * network adapter. The passthrough mode is required for all network traffic
 287  * other than IPv4. In particular, the passthrough mode is required for IPv6
 288  * traffic.
 289  * User action:
 290  * None if all you want to support is IPv4 communication. If you want to support
 291  * IPv6 or other network traffic apart from IPv4, ungroup and regroup the
 292  * subchannel triplet of the device. If this does not resolve the problem,
 293  * reboot Linux. If the problem persists, gather Linux debug data and report
 294  * the problem to your support organization.
 295  */
 296
 297 /*?
 298  * Text: "%s: Enabling broadcast filtering for %s failed\n"
 299  * Severity: Warning
 300  * Parameter:
 301  *   @1: bus ID of the qeth device
 302  *   @2: network interface name
 303  * Description:
 304  * The qeth device driver could not enable broadcast filtering on the network
 305  * adapter.
 306  * User action:
 307  * Ungroup and regroup the subchannel triplet of the device. If this does not
 308  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 309  * debug data and report the problem to your support organization.
 310  */
 311
 312 /*?
 313  * Text: "%s: Setting up broadcast filtering for %s failed\n"
 314  * Severity: Warning
 315  * Parameter:
 316  *   @1: bus ID of the qeth device
 317  *   @2: network interface name
 318  * Description:
 319  * The qeth device driver could not set up broadcast filtering on the network
 320  * adapter.
 321  * User action:
 322  * Ungroup and regroup the subchannel triplet of the device. If this does not
 323  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 324  * debug data and report the problem to your support organization.
 325  */
 326
 327 /*?
 328  * Text: "%s: Setting up broadcast echo filtering for %s failed\n"
 329  * Severity: Warning
 330  * Parameter:
 331  *   @1: bus ID of the qeth device
 332  *   @2: network interface name
 333  * Description:
 334  * The qeth device driver could not set up broadcast echo filtering on the
 335  * network adapter.
 336  * User action:
 337  * Ungroup and regroup the subchannel triplet of the device. If this does not
 338  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 339  * debug data and report the problem to your support organization.
 340  */
 341
 342 /*?
 343  * Text: "%s: Starting HW checksumming for %s failed, using SW checksumming\n"
 344  * Severity: Warning
 345  * Parameter:
 346  *   @1: bus ID of the qeth device
 347  *   @2: network interface name
 348  * Description:
 349  * The network adapter supports hardware checksumming for IP packages
 350  * but the qeth device driver could not start hardware checksumming on the
 351  * adapter. The qeth device driver continues to use software checksumming for
 352  * IP packages.
 353  * User action:
 354  * None if you do not require hardware checksumming for network
 355  * traffic. If you want to enable hardware checksumming, ungroup and regroup
 356  * the subchannel triplet of the device. If this does not resolve the problem,
 357  * reboot Linux. If the problem persists, gather Linux debug data and report
 358  * the problem to your support organization.
 359  */
 360
 361 /*?
 362  * Text: "%s: Enabling HW checksumming for %s failed, using SW checksumming\n"
 363  * Severity: Warning
 364  * Parameter:
 365  *   @1: bus ID of the qeth device
 366  *   @2: network interface name
 367  * Description:
 368  * The network adapter supports hardware checksumming for IP packages
 369  * but the qeth device driver could not enable hardware checksumming on the
 370  * adapter. The qeth device driver continues to use software checksumming for
 371  * IP packages.
 372  * User action:
 373  * None if you do not require hardware checksumming for network
 374  * traffic. If you want to enable hardware checksumming, ungroup and regroup
 375  * the subchannel triplet of the device. If this does not resolve the problem,
 376  * reboot Linux. If the problem persists, gather Linux debug data and report
 377  * the problem to your support organization.
 378  */
 379
 380 /*?
 381  * Text: "%s: Starting outbound TCP segmentation offload for %s failed\n"
 382  * Severity: Warning
 383  * Parameter:
 384  *   @1: bus ID of the qeth device
 385  *   @2: network interface name
 386  * Description:
 387  * The network adapter supports TCP segmentation offload, but the qeth device
 388  * driver could not start this support on the adapter.
 389  * User action:
 390  * None if you do not require TCP segmentation offload. If you want to
 391  * enable TCP segmentation offload, ungroup and regroup the subchannel triplet
 392  * of the device. If this does not resolve the problem, reboot Linux. If the
 393  * problem persists, gather Linux debug data and report the problem to your
 394  * support organization.
 395  */
 396
 397 /*?
 398  * Text: "%s: The network adapter failed to generate a unique ID\n"
 399  * Severity: Warning
 400  * Parameter:
 401  *   @1: bus ID of the qeth device
 402  * Description:
 403  * In IBM mainframe environments, network interfaces are not identified by
 404  * a specific MAC address. Therefore, the network adapters provide the network
 405  * interfaces with unique IDs to be used in their IPv6 link local addresses.
 406  * Without such a unique ID, duplicate addresses might be assigned in other
 407  * LPARs.
 408  * User action:
 409  * Install the latest firmware on the adapter hardware. Manually, configure
 410  * an IPv6 link local address for this device.
 411  */
 412
 413 /*?
 414  * Text: "There is no IPv6 support for the layer 3 discipline\n"
 415  * Severity: Warning
 416  * Description:
 417  * If you want to use IPv6 with the layer 3 discipline, you need a Linux kernel
 418  * with IPv6 support. Because your Linux kernel has not been compiled with
 419  * IPv6 support, you cannot use IPv6 with the layer 3 discipline, even if your
 420  * adapter supports IPv6.
 421  * User action:
 422  * Use a Linux kernel that has been complied to include IPv6 support if you
 423  * want to use IPv6 with layer 3 qeth devices.
 424  */
 425
 426 /*?
 427  * Text: "%s: The qeth device is not configured for the OSI layer required by z/VM\n"
 428  * Severity: Error
 429  * Parameter:
 430  *   @1: bus ID of the qeth device
 431  * Description:
 432  * A qeth device that connects to a virtual network on z/VM must be configured for the
 433  * same Open Systems Interconnection (OSI) layer as the virtual network. An ETHERNET
 434  * guest LAN or VSWITCH uses the data link layer (layer 2) while an IP guest LAN
 435  * or VSWITCH uses the network layer (layer 3).
 436  * User action:
 437  * If you are connecting to an ETHERNET guest LAN or VSWITCH, set the layer2 sysfs
 438  * attribute of the qeth device to 1. If you are connecting to an IP guest LAN or
 439  * VSWITCH, set the layer2 sysfs attribute of the qeth device to 0.
 440  */
 441
 442 /*?
 443  * Text: "%s: Starting source MAC-address support for %s failed\n"
 444  * Severity: Warning
 445  * Parameter:
 446  *   @1: bus ID of the qeth device
 447  *   @2: network interface name
 448  * Description:
 449  * The qeth device driver could not enable source MAC-address on the network
 450  * adapter.
 451  * User action:
 452  * Ungroup and regroup the subchannel triplet of the device. If this does not
 453  * resolve the problem, reboot Linux. If the problem persists, gather Linux
 454  * debug data and report the problem to your support organization.
 455  */
 456
 457 /*?
 458  * Text: "%s: MAC address %pM already exists\n"
 459  * Severity: Warning
 460  * Parameter:
 461  *   @1: bus ID of the qeth device
 462  *   @2: MAC-address
 463  * Description:
 464  * Setting the MAC address for the qeth device fails, because this
 465  * MAC address is already defined on the OSA CHPID.
 466  * User action:
 467  * Use a different MAC address for this qeth device.
 468  */
 469
 470 /*?
 471  * Text: "%s: MAC address %pM is not authorized\n"
 472  * Severity: Warning
 473  * Parameter:
 474  *   @1: bus ID of the qeth device
 475  *   @2: MAC-address
 476  * Description:
 477  * This qeth device is a virtual network interface card (NIC), to which z/VM
 478  * has already assigned a MAC address. z/VM MAC address verification does
 479  * not allow you to change this predefined address.
 480  * User action:
 481  * None; use the MAC address that has been assigned by z/VM.
 482  */
 483
 484 /*?
 485  * Text: "%s: The HiperSockets network traffic analyzer is activated\n"
 486  * Severity: Informational
 487  * Parameter:
 488  *   @1: bus ID of the qeth device
 489  * Description:
 490  * The sysfs 'sniffer' attribute of the HiperSockets device has the value '1'.
 491  * The corresponding HiperSockets interface has been switched into promiscuous mode.
 492  * As a result, the HiperSockets network traffic analyzer is started on the device.
 493  * User action:
 494  * None.
 495  */
 496
 497  /*?
 498   * Text: "%s: The HiperSockets network traffic analyzer is deactivated\n"
 499   * Severity: Informational
 500   * Parameter:
 501   *   @1: bus ID of the qeth device
 502   * Description:
 503   * The sysfs 'sniffer' attribute of the HiperSockets device has the value '1'.
 504   * Promiscuous mode has been switched off for the corresponding HiperSockets interface
 505   * As a result, the HiperSockets network traffic analyzer is stopped on the device.
 506   * User action:
 507   * None.
 508   */
 509
 510 /*?
 511  * Text: "%s: The device is not authorized to run as a HiperSockets network traffic analyzer\n"
 512  * Severity: Warning
 513  * Parameter:
 514  *   @1: bus ID of the qeth device
 515  * Description:
 516  * The sysfs 'sniffer' attribute of the HiperSockets device has the value '1'.
 517  * The corresponding HiperSockets interface is switched into promiscuous mode
 518  * but the network traffic analyzer (NTA) rules configured at the Support Element (SE)
 519  * do not allow tracing. Possible reasons are:
 520  * - Tracing is not authorized for all HiperSockets LANs in the mainframe system
 521  * - Tracing is not authorized for this HiperSockets LAN
 522  * - LPAR is not authorized to enable an NTA
 523  * User action:
 524  * Configure appropriate HiperSockets NTA rules at the SE.
 525  */
 526
 527 /*?
 528  * Text: "%s: A HiperSockets network traffic analyzer is already active in the HiperSockets LAN\n"
 529  * Severity: Warning
 530  * Parameter:
 531  *   @1: bus ID of the qeth device
 532  * Description:
 533  * The sysfs 'sniffer' attribute of the HiperSockets device has the value '1'.
 534  * The HiperSockets interface is switched into promiscuous mode but another
 535  * HiperSockets device on the same HiperSockets LAN is already running as
 536  * a network traffic analyzer.
 537  * A HiperSockets LAN can only have one active network traffic analyzer.
 538  * User action:
 539  * Do not configure multiple HiperSockets devices in the same HiperSockets LAN as
 540  * tracing devices.
 541  */
 542
 543 /*?
 544  * Text: "%s: Enabling HW TX checksumming for %s failed, using SW TX checksumming\n"
 545  * Severity: Warning
 546  * Parameter:
 547  *   @1: bus ID of the qeth device
 548  *   @2: network interface name
 549  * Description:
 550  * The network adapter supports hardware checksumming for outgoing IP packages
 551  * but the qeth device driver could not enable hardware TX checksumming on the
 552  * adapter. The qeth device driver continues to use software checksumming for
 553  * outgoing IP packages.
 554  * User action:
 555  * None if you do not require hardware checksumming for outgoing network
 556  * traffic. If you want to enable hardware checksumming, ungroup and regroup
 557  * the subchannel triplet of the device. If this does not resolve the problem,
 558  * reboot Linux. If the problem persists, gather Linux debug data and report
 559  * the problem to your support organization.
 560  */
 561
 562 /*?
 563  * Text: "%s: A connection could not be established because of an OLM limit\n"
 564  * Severity: Error
 565  * Parameter:
 566  *   @1: bus ID of the qeth device
 567  * Description:
 568  * z/OS has activated Optimized Latency Mode (OLM) for a connection through an OSA Express3 adapter.
 569  * This reduces the maximum number of concurrent connections per physical port for shared adapters.
 570  * The new connection would exceed the maximum. Linux cannot establish further connections using
 571  * this adapter.
 572  * User action:
 573  * If possible, deactivate an existing connection that uses this adapter and try again to establish
 574  * the new connection. If you cannot free an existing connection, use a different adapter for the
 575  * new connection.
 576  */
 577
 578 /*?
 579  * Text: "%s: Setting the device online failed because of insufficient authorization\n"
 580  * Severity: Error
 581  * Parameter:
 582  *   @1: bus ID of the qeth device
 583  * Description:
 584  * The qeth device is configured with OSX CHPIDs. An OSX CHPID cannot be activated unless the LPAR is explicitly authorized to access it.
 585  * For z/VM guest operating systems, the z/VM user ID must be explicitly authorized in addition to the LPAR.
 586  * You grant these authorizations through the Service Element.
 587  * User action:
 588  * At the Service Element, authorize the LPAR and, if applicable, the z/VM user ID for using the OSX CHPIDs with which the qeth device has been configured.
 589  * Then try again to set the device online.
 590  */
 591
 592 /*?
 593  * Text: "%s: portname is deprecated and is ignored\n"
 594  * Severity: Warning
 595  * Parameter:
 596  *   @1: bus ID of the qeth device
 597  * Description:
 598  * An OSA-Express port name was required to identify a shared OSA port.
 599  * All operating system instances that shared the port had to use the same port name.
 600  * This requirement no longer applies, and the specified portname attribute is ignored.
 601  * User action:
 602  * For future upgrades, remove OSA port name specifications from your
 603  * network configuration.
 604  */
 605
 606 /*? Text: "core functions removed\n" */
 607 /*? Text: "%s: Device is a%s card%s%s%s\nwith link type %s.\n" */
 608 /*? Text: "%s: issue_next_read failed: no iob available!\n" */
 609 /*? Text: "%s: Priority Queueing not supported\n" */
 610 /*? Text: "%s: sense data available. cstat 0x%X dstat 0x%X\n" */
 611 /*? Text: "loading core functions\n" */
 612 /*? Text: "%s: MAC address %pM successfully registered on device %s\n" */
 613 /*? Text: "%s: Device successfully recovered!\n" */
 614 /*? Text: "register layer 2 discipline\n" */
 615 /*? Text: "unregister layer 2 discipline\n" */
 616 /*? Text: "%s: Hardware IP fragmentation not supported on %s\n" */
 617 /*? Text: "%s: IPv6 not supported on %s\n" */
 618 /*? Text: "%s: VLAN not supported on %s\n" */
 619 /*? Text: "%s: Inbound source MAC-address not supported on %s\n" */
 620 /*? Text: "%s: IPV6 enabled\n" */
 621 /*? Text: "%s: ARP processing not supported on %s!\n" */
 622 /*? Text: "%s: Hardware IP fragmentation enabled \n" */
 623 /*? Text: "%s: set adapter parameters not supported.\n" */
 624 /*? Text: "%s: VLAN enabled\n" */
 625 /*? Text: "register layer 3 discipline\n" */
 626 /*? Text: "%s: Outbound TSO enabled\n" */
 627 /*? Text: "%s: Broadcast not supported on %s\n" */
 628 /*? Text: "%s: Outbound TSO not supported on %s\n" */
 629 /*? Text: "%s: Inbound HW Checksumming not supported on %s,\ncontinuing using Inbound SW Checksumming\n" */
 630 /*? Text: "%s: Using no checksumming on %s.\n" */
 631 /*? Text: "%s: Broadcast enabled\n" */
 632 /*? Text: "%s: Multicast not supported on %s\n" */
 633 /*? Text: "%s: Using SW checksumming on %s.\n" */
 634 /*? Text: "%s: HW Checksumming (%sbound) enabled\n" */
 635 /*? Text: "unregister layer 3 discipline\n" */
 636 /*? Text: "%s: Multicast enabled\n" */
 637 /*? Text: "%s: QDIO data connection isolation is deactivated\n" */
 638 /*? Text: "%s: QDIO data connection isolation is activated\n" */
 639 /*? Text: "%s: Adapter does not support QDIO data connection isolation\n" */
 640 /*? Text: "%s: Adapter is dedicated. QDIO data connection isolation not supported\n" */
 641 /*? Text: "%s: TSO does not permit QDIO data connection isolation\n" */
 642 /*? Text: "%s: HW TX Checksumming enabled\n" */
 643 /*? Text: "netif_stop_queue() cannot be called before register_netdev()\n" */
 644 /*? Text: "qeth_l3: ignoring TR device\n" */
 645 /*? Text: "flen=%u proglen=%u pass=%u image=%pK from=%s pid=%d\n" */
 646 /*? Text: "%s selects TX queue %d, but real number of TX queues is %d\n" */
 647
 648 /*?
 649  * Text: "%s: Turning off reflective relay mode at the adjacent switch failed\n"
 650  * Severity: Warning
 651  * Parameter:
 652  *   @1: bus ID of the qeth device
 653  * Description:
 654  * The policy for the QDIO data connection isolation was
 655  * changed successfully, and communications are now handled according to the
 656  * new policy. The ISOLATION_FORWARD policy is no longer used, but the qeth
 657  * device driver could not turn off the reflective relay mode on the adjacent
 658  * switch port.
 659  * User action:
 660  * Check the adjacent switch for errors and correct the problem.
 661  */
 662
 663 /*?
 664  * Text: "%s: The adjacent switch port does not support reflective relay mode\n"
 665  * Severity: Error
 666  * Parameter:
 667  *   @1: bus ID of the qeth device
 668  * Description:
 669  * The 'isolation' sysfs attribute of the qeth device could not be set to 'forward'.
 670  * This setting selects the ISOLATION_FORWARD policy for the QDIO data connection
 671  * isolation. The ISOLATION_FORWARD policy requires a network adapter in Virtual
 672  * Ethernet Port Aggregator (VEPA) mode with an adjacent switch port in reflective
 673  * relay mode.
 674  * User action:
 675  * Use a switch port that supports reflective relay mode if you want to use the
 676  * ISOLATION_FORWARD policy for the qeth device.
 677  */
 678
 679 /*?
 680  * Text: "%s: The reflective relay mode cannot be enabled at the adjacent switch port"
 681  * Severity: Error
 682  * Parameter:
 683  *   @1: bus ID of the qeth device
 684  * Description:
 685  * The 'isolation' sysfs attribute of the qeth device could not be set to 'forward'.
 686  * This setting selects the ISOLATION_FORWARD policy for the QDIO data connection
 687  * isolation. The ISOLATION_FORWARD policy requires a network adapter in Virtual
 688  * Ethernet Port Aggregator (VEPA) mode with an adjacent switch port in reflective relay
 689  * mode. The qeth device driver failed to enable the required reflective relay mode on
 690  * the adjacent switch port although the switch port supports this mode.
 691  * User action:
 692  * Enable reflective relay mode on the switch for the adjacent port and try again.
 693  */
 694
 695 /*?
 696  * Text: "%s: Interface %s is down because the adjacent port is no longer in reflective relay mode\n"
 697  * Severity: Error
 698  * Parameter:
 699  *   @1: bus ID of the qeth device
 700  *   @2: interface name
 701  * Description:
 702  * The ISOLATION_FORWARD policy is active for the QDIO data connection isolation
 703  * of the qeth device. This policy requires a network adapter in Virtual Ethernet
 704  * Port Aggregator (VEPA) mode with an adjacent switch port in reflective relay mode.
 705  * The reflective relay mode on the adjacent switch port was disabled. The qeth device
 706  * was set offline and the interface was deactivated to prevent any unintended network traffic.
 707  * User action:
 708  * Enable the reflective relay mode again on the adjacent port or use the 'isolation'
 709  * sysfs attribute of the qeth device to set a different policy for the QDIO data connection
 710  * isolation. You can then resume operations by setting the qeth device back
 711  * online and activating the interface.
 712  */
 713
 714 /*?
 715  * Text: "%s: Failed to create completion queue\n"
 716  * Severity: Error
 717  * Parameter:
 718  *   @1: bus ID of the qeth device
 719  * Description:
 720  * The HiperSockets device could not be configured with a completion queue.
 721  * A completion queue is required to operate AF_IUCV communication in an LPAR.
 722  * User action:
 723  * i) Investigate if you have the latest firmware level in place.
 724  * ii) If the problem persists and is not caused by a version mismatch, contact IBM
 725  * support.
 726  */
 727
 728 /*?
 729  * Text: "%s: Completion Queueing supported\n"
 730  * Severity: Informational
 731  * Parameter:
 732  *   @1: bus ID of the qeth device
 733  * Description:
 734  * The HiperSockets device supports completion queueing. This is required to
 735  * set up AF_IUCV communication in an LPAR.
 736  */
 737
 738 /*?
 739  * Text: "%s: Completion Queue support enabled"
 740  * Severity: Informational
 741  * Parameter:
 742  *   @1: bus ID of the qeth device
 743  * Description:
 744  * The HiperSockets device is enabled for completion queueing. This is part of
 745  * the process to set up AF_IUCV communication in an LPAR.
 746  */
 747
 748 /*?
 749  * Text: "%s: Completion Queue support disabled"
 750  * Severity: Informational
 751  * Parameter:
 752  *   @1: bus ID of the qeth device
 753  * Description:
 754  * The HiperSockets device is disabled for completion queueing. This device
 755  * cannot or no longer be used to set up AF_IUCV communication in an LPAR.
 756  */
 757
 758 /*?
 759  * Text: "%s: The device represents a Bridge Capable Port\n"
 760  * Severity: Informational
 761  * Parameter:
 762  *   @1: bus ID of the qeth device
 763  * Description:
 764  * You can configure this device as a Bridge Port.
 765  * User action:
 766  * None.
 767  */
 768
 769 /*?
 770  * Text: "%s: The device is not configured as a Bridge Port\n"
 771  * Severity: Error
 772  * Parameter:
 773  *   @1: bus ID of the qeth device
 774  * Description:
 775  * The Bridge Port role cannot be withdrawn from a device
 776  * that is not configured as a Bridge Port.
 777  * User action:
 778  * None.
 779  */
 780
 781 /*?
 782  * Text: "%s: The LAN already has a primary Bridge Port\n"
 783  * Severity: Error
 784  * Parameter:
 785  *   @1: bus ID of the qeth device
 786  * Description:
 787  * A LAN can have multiple secondary Bridge Ports, but only
 788  * one primary Bridge Port. Configuring the device as a
 789  * primary Bridge Port failed because another port on the
 790  * LAN has been configured as the primary Bridge Port.
 791  * User action:
 792  * Find out which operating system instance has configured the primary
 793  * Bridge Port. Assure that the primary role for this port is withdrawn
 794  * before trying again to configure your device as the primary Bridge
 795  * Port. Alternatively, consider configuring your device as a secondary
 796  * Bridge Port.
 797  */
 798
 799 /*?
 800  * Text: "%s: The device is already a secondary Bridge Port\n"
 801  * Severity: Error
 802  * Parameter:
 803  *   @1: bus ID of the qeth device
 804  * Description:
 805  * A device cannot be configured as a primary or secondary
 806  * Bridge Port if it is already configured as a secondary Bridge Port.
 807  * User action:
 808  * None, if you want the device to be a secondary Bridge Port.
 809  * If you want to configure the device as the primary Bridge Port,
 810  * withdraw the secondary role by writing 'none' to the 'bridgeport_role'
 811  * sysfs attribute of the device. Then try again to configure the
 812  * device as the primary Bridge Port.
 813  */
 814
 815 /*?
 816  * Text: "%s: The LAN cannot have more secondary Bridge Ports\n"
 817  * Severity: Error
 818  * Parameter:
 819  *   @1: bus ID of the qeth device
 820  * Description:
 821  * A LAN can have up to five secondary Bridge Ports.
 822  * You cannot configure a further device as a secondary
 823  * Bridge Port unless the Bridge Ports role is withdrawn from one of
 824  * the existing secondary Bridge Ports.
 825  * User action:
 826  * Assure that the Bridge Port role is withdrawn from one of the
 827  * existing secondary Bridge Ports before trying again to configure your
 828  * device as a secondary Bridge Port.
 829  */
 830
 831 /*?
 832  * Text: "%s: The device is already a primary Bridge Port\n"
 833  * Severity: Error
 834  * Parameter:
 835  *   @1: bus ID of the qeth device
 836  * Description:
 837  * A device cannot be configured as a primary or secondary
 838  * Bridge Port if it is already configured as a primary Bridge Port.
 839  * User action:
 840  * None, if you want the device to be a primary Bridge Port.
 841  * If you want to configure the device as a secondary Bridge Port,
 842  * withdraw the primary role by writing 'none' to the 'bridgeport_role'
 843  * sysfs attribute of the device. Then try again to configure the
 844  * device as the secondary Bridge Port.
 845  */
 846
 847 /*?
 848  * Text: "%s: The device is not authorized to be a Bridge Port\n"
 849  * Severity: Error
 850  * Parameter:
 851  *   @1: bus ID of the qeth device
 852  * Description:
 853  * The device cannot be configured as a Bridge Port because
 854  * the required authorizations in the hardware are not in place.
 855  * User action:
 856  * See your hardware documentation about how to authorize
 857  * ports for becoming a Bridge Port.
 858  */
 859
 860 /*?
 861  * Text: "%s: A Bridge Port is already configured by a different operating system\n"
 862  * Severity: Error
 863  * Parameter:
 864  *   @1: bus ID of the qeth device
 865  * Description:
 866  * Linux instances cannot configure the target port as a Bridge Port.
 867  * Another operating system already uses a Bridge Port on the HiperSockets
 868  * or on the OSA adapter. For example, a z/VM instance might be using
 869  * a port in a VSWITCH configuration. Multiple Bridge Ports on the same
 870  * HiperSockets or OSA adapter must be configured by instances of the same
 871  * operating system, for example, all Linux or all z/VM.
 872  * User action:
 873  * Reconsider your network topology. Configure Bridge Ports only for ports
 874  * on adapters where any other Bridge Ports are configured by other Linux
 875  * instances.
 876  */
 877
 878 /*?
 879  * Text: "%s: Setting address notification failed\n"
 880  * Severity: Error
 881  * Parameter:
 882  *   @1: bus ID of the qeth device
 883  * Description:
 884  * Enabling or disabling the address notification feature of a
 885  * HiperSockets device failed. The device might not be configured as a
 886  * Bridge Port.
 887  * User action:
 888  * None, unless you need address notifications for this device.
 889  * If you need notifications, confirm that your device is attached to a
 890  * HiperSockets LAN that supports Bridge Capable Ports and that your
 891  * device is configured as a Bridge Port. If the 'bridgeport_role'
 892  * sysfs attribute of the device contains, one of the values 'primary'
 893  * or 'secondary' and you cannot set the address notification, contact
 894  * your support organization.
 895  */
 896
 897 /*?
 898  * Text: "%s: Address notification from the Bridge Port stopped %s (%s)\n"
 899  * Severity: Informational
 900  * Parameter:
 901  *   @1: bus ID of the qeth device
 902  *   @2: network interface name
 903  *   @3: error reported by the hardware
 904  * Description:
 905  * A Bridge Port no longer provides address notifications.
 906  * Possible reasons include traffic overflow and that the device is no
 907  * longer configured as a Bridge Port. A udev event with
 908  * BRIDGEDHOST=abort was emitted to alert applications that rely on the
 909  * address notifications.
 910  * User action:
 911  * None.
 912  */
 913
 914 /*?
 915  * Text: "%s: The qeth driver ran out of channel command buffers\n"
 916  * Severity: Warning
 917  * Parameter:
 918  *   @1: bus ID of the qeth device
 919  * Description:
 920  * Command buffers can temporarily run out during periods of
 921  * intense network configuration activities.
 922  * The device driver recovers from this condition as outstanding
 923  * commands are completed.
 924  * User action:
 925  * Wait for a short time. If the problem persists,
 926  * initiate a recovery process by writing '1' to the 'recover'
 927  * sysfs attribute of the device.
 928  */
 929 /*? Text: "%s: %d output lines suppressed due to ratelimiting\n" */