Bug 769623

Summary: kernel panic with sky2 driver
Product: Red Hat Enterprise Linux 6 Reporter: tgb <rfv781>
Component: kernelAssignee: Andy Gospodarek <agospoda>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: Jes.Sorensen, peterm, rfv781
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-03 21:36:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
crash log none

Description tgb 2011-12-21 14:07:50 UTC 
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
Comment 1 tgb 2011-12-21 14:08:26 UTC 
Created attachment 549030 [details]
crash log
Comment 3 tgb 2011-12-23 05:16:02 UTC 
I cannot reproduce the issue with "pcie_aspm=off". So it's related to https://bugzilla.redhat.com/show_bug.cgi?id=769626, maybe.
Comment 4 Andy Gospodarek 2012-01-03 21:36:23 UTC 
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 ***