summaryrefslogtreecommitdiffstats
path: root/net/sctp
diff options
context:
space:
mode:
authorBaoquan He <bhe@redhat.com>2016-09-09 22:43:12 +0800
committerDavid S. Miller <davem@davemloft.net>2016-09-13 11:24:29 -0400
commit3e1be7ad2d38c6bd6aeef96df9bd0a7822f4e51c (patch)
tree5366887061f90211d05d1a35d5b588fb21375dd1 /net/sctp
parent67b9f0b737a41b8e10bcc3568830d546e6b9a68f (diff)
downloadop-kernel-dev-3e1be7ad2d38c6bd6aeef96df9bd0a7822f4e51c.zip
op-kernel-dev-3e1be7ad2d38c6bd6aeef96df9bd0a7822f4e51c.tar.gz
bnx2: Reset device during driver initialization
When system enters into kdump kernel because of kernel panic, it won't shutdown devices. On-flight DMA will continue transferring data until device driver initializes. All devices are supposed to reset during driver initialization. And this property is used to fix the kdump failure in system with intel iommu. Other systems with hardware iommu should be similar. Please check commit 091d42e ("iommu/vt-d: Copy translation tables from old kernel") and those commits around. But bnx2 driver doesn't reset device during driver initialization. The device resetting is deferred to net device up stage. This will cause hardware iommu handling failure on bnx2 device. And its resetting relies on firmware. So in this patch move the firmware requesting code to earlier bnx2_init_one(), then next call bnx2_reset_chip to reset device. Signed-off-by: Baoquan He <bhe@redhat.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/sctp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud