Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:


Version-Release number of selected component (if applicable):
kernel-2.6.32-220.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
Something like
iperf -c <ip> -b 80M -t 1000
  
Actual results:
Kernel panic

Expected results:


Additional info:
Crash log and backtrace in attachment.
kernel-2.6.32-131.21.1.el6.x86_64 is fine

Created attachment 549030 [details]
crash log

I cannot reproduce the issue with "pcie_aspm=off". So it's related to https://bugzilla.redhat.com/show_bug.cgi?id=769626, maybe.

I see there are a bunch of errors reported right before the panic:

sky2 0000:07:00.0: error interrupt status=0xffffffff
sky2 0000:07:00.0: PCI hardware error (0xffff)
sky2 0000:07:00.0: PCI Express error (0xffffffff)
sky2 eth1: hw error interrupt status 0xffffffff
sky2 eth1: ram data read parity error
sky2 eth1: ram data write parity error
sky2 eth1: MAC parity error
sky2 eth1: RX parity error
sky2 eth1: TCP segmentation error
sky2 (null): hw error interrupt status 0xffffff
BUG: unable to handle kernel NULL pointer dereference at 00000000000006d5

So I bet you are correct that this is a duplicate of bug 769626.  I will close as a duplicate, but please reopen if the updated errata kernel that contains the fix from bug 769626 does not resolve the issue.

*** This bug has been marked as a duplicate of bug 769626 ***