Bug 586352
Summary: | oops in cnic when running on xen and disable_lro | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Stanislaw Gruszka <sgruszka> | ||||||
Component: | kernel | Assignee: | Stanislaw Gruszka <sgruszka> | ||||||
Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 5.5 | CC: | mchan | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2010-08-02 09:24:56 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 595548 | ||||||||
Attachments: |
|
Description
Stanislaw Gruszka
2010-04-27 11:37:51 UTC
Created attachment 409446 [details]
proposed workaround/fix
This patch prevent oops, I'm pretty sure it is not right fix just workaround.
Created attachment 409449 [details]
packed addional patches
Patches for 2.6.18-194.el5 kernel which make this bug reproducible.
Michael, Problem is that we get interrupt when cnic driver is not ready for it. On xen we have legacy INT# interrupt. This happens when we reset device during bnx2x_nic_load(). Do you have any ideas about better fix? I think this upstream patch should fix it. http://git.kernel.org/?p=linux/kernel/git/davem/net-2.6.git;a=commit;h=94824f3dbe0d3f62470603bbb18efb5510aaf07c We saw a similar issue during MTU change and fixed it with the above patch. Thanks. Yes, patch fix problem. Thanks Michael. This patch was applied with patch series for bug 582367 . *** This bug has been marked as a duplicate of bug 582367 *** |