Red Hat Bugzilla – Bug 254234
sunhme does not work
Last modified: 2008-05-21 10:53:53 EDT
Description of problem:
Sunhme does not work under RHEL5 kernel. I have a second hand Sun quad ethernet
card in my home server. It used to work before under RHEL 4 (to be honest, I
used Centos 4). It no longer works under Centos 5. The latest kernel I tried was:
When I replace the standard kernel with a Fedora 6 kernel (18.104.22.168-42.fc6), all
is fine again
Version-Release number of selected component (if applicable):
kernel-2.6.18-36.el5.jwltest.41 or kernel-2.6.18-8.1.8.el5
Steps to Reproduce:
No network connection, logfile shows:
Aug 24 20:32:20 nest kernel: eth1: transmit timed out, resetting
Aug 24 20:32:20 nest kernel: eth1: Happy Status 03010000 TX[000003ff:00000301]
Similar results are obtained for each interface used
working network connection
Created attachment 193811 [details]
Test kernels w/ the above patch available here:
Do these resolve the issue for you?
Yes, the kernel 2.6.18-47.el5.jwltest.42 does solve the problem. Thanks!
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
You can download this test kernel from http://people.redhat.com/dzickus/el5
2.6.18-61.el5 fails to read the options rom on the card (errormsg: failed to
allocat mem resouorce, once for each of the 4 chips). But as the kernel crashes
with an oops later in the boot process, I have not been able to debug further
(macaddr option probably would serve as work around). Will try again later.
2.6.18-53.el5 with the patch provided in this entry however works well
I am now running 2.6.18-75.el5xen. Solves the issues with the sun nic. Thanks!
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 the 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.