Why is /proc/interrupts corrupted when using be2net and be2iscsi modules in RHEL5?

Solution Unverified - Updated -

Issue

  • The contents of /proc/interrupts seem to be corrupted:

    Example 1:

0          0          0          0          0          0          0          0          0          0       PCI-MSI-X  80,     0x0f794366,     0x86c99402,
0x211b98bf,     0xdf8eb0e3,     0xda11d7bd,     0xd440363e,
0xa7d49f1a,     0x16dd7395,     0x5b23c2fc,     0xab93ea3c,
0x00000011,     0xf112a9c3,     0xa4bb682e,     0x58d741d3,
0x60af7dbd,     0x38b863ba,     0x2a3b61ab,     0x466b095e,


Example 2:
 51:          0          0          0          0          0          0          0          0       PCI-MSI-X 
GHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789ABC
DEFGHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789
ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456
789ABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ

Environment

  • Red Hat Enterpise Linux 5.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.