Did this work on RHEL5.5?
It looks like a change to the size of the s2io_nic structure might be causing this, so I'll have to look at what changed in RHEL5.4 and RHEL5.5 as it doesn't look like much changed in RHEL5.5 that would cause this.

Created attachment 463650[details]
patch for fixing the s2io initialize
When the s2io initialize(s2io_init_nic), I found the sizeof(struct s2io_nic) = 73344, it is larger than NETDEV_PRIV_LEN_MAX 0X0000FFFF(64K) which compared in the alloc_netdev, so "Private data too big" is reported and device allocation failed.
NETDEV_PRIV_LEN_MAX and compared section are added by patch: linux-2.6-net-qla3xxx-fix-oops-on-too-long-netdev-priv-structure.patch
I remove some related codes for workaround, the s2io can work.
There is the file s2io_fix_init.patch in the attachment, hope it can help us fix this issue.
By the way we need take care if the changes will cause another issue.
Thanks,
Dawei

(In reply to comment #7)
> Created attachment 463650[details]
> patch for fixing the s2io initialize
>
> When the s2io initialize(s2io_init_nic), I found the sizeof(struct s2io_nic) =
> 73344, it is larger than NETDEV_PRIV_LEN_MAX 0X0000FFFF(64K) which compared in
> the alloc_netdev, so "Private data too big" is reported and device allocation
> failed.
>
> NETDEV_PRIV_LEN_MAX and compared section are added by patch:
> linux-2.6-net-qla3xxx-fix-oops-on-too-long-netdev-priv-structure.patch
>
> I remove some related codes for workaround, the s2io can work.
> There is the file s2io_fix_init.patch in the attachment, hope it can help us
> fix this issue.
>
> By the way we need take care if the changes will cause another issue.
>
> Thanks,
> Dawei
The attached patch will have other side effects, so we cannot use it.
What will need to happen is to put the s2io_nic structure on a diet and convert some of the data stored in the structure to pointers to allocated memory.
The best thing will be to load a system with crash and look at what elements are taking up the most space and can be moved around.
Reassiging to Bob as he should be able to quickly knock this out.

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.

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.

(In reply to comment #18)
> 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.
This issue is a critical problem for HP which may affect rhel5.6's LR. And since the snapshot5 is a last snapshot version, I wonder which maintenence release you are going to resolve it.
Jiayin

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2011-0017.html

Note

You need to
log in
before you can comment on or make changes to this bug.