diff options
| author | Jacob Keller <jacob.e.keller@intel.com> | 2016-02-04 10:47:58 -0800 |
|---|---|---|
| committer | Jeff Kirsher <jeffrey.t.kirsher@intel.com> | 2016-04-05 12:49:22 -0700 |
| commit | c8ed563bebeabbf0b1085b52916dd2fb6e219276 (patch) | |
| tree | 0175bc76b81d2a318a518f3d5664e17453470a41 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 61e0217e83353cf895f8b2d0a187804171d119ca (diff) | |
fm10k: free MBX IRQ before clearing interrupt scheme
During fm10k_io_error_detected we were clearing the interrupt scheme
before we freed the MBX IRQ. This causes a kernel panic because the MBX
IRQ are assigned after MSI-X initialization. Clearing the interrupt
scheme results in removing the MSI-X entry table. Fix this by freeing
the MBX IRQ before we clear the interrupt scheme, as we do elsewhere in
the driver.
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
Tested-by: Krishneil Singh <Krishneil.k.singh@intel.com>
Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions