yeah, it certainly could be an issue, Andy, stack traces look simmilar. Do you have references to the RHEL4 changes. They should apply pretty easily I think.
I think there is some confusion, Neil. I thought I saw that you posted some RHEL4 changes for netpoll recently. This one specifically was the one I was thinking about: commit fafe89a87140f78499ccb487ab26f2c4345a785b Author: Neil Horman <nhorman> Date: Wed Jan 13 11:08:08 2010 -0500 netpoll: fix more local_bh_enable() related badness warnings and infinite loop That was for bug 516076. I was curious if it would resolve the same issue.
No, we're talking about the same thing. I'm sorry, I should have been more clear. There was that patch, and then a follow on patch that went straight to rhkl (vivek asked me to fix it up in line with that one). If you look up the thread on rhkl you'll find the subsequent patch as well as the one in the bug.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Gary, could you have the reporter check against the lastest RHEL4 development kernel? Bug 516076 may have actually resolved this already. The fix for bug 516076 went in 2.6.9-89.19.EL, so any kernel at least that new (as of right now http://people.redhat.com/vgoyal/rhel4/ shows that 2.6.9-89.23.EL is available) would be fine.
No feedback. Closing.