Hide Forgot
Description of problem: Version-Release number of selected component (if applicable): NetworkManager-glib-0.7.0-13.el5 NetworkManager-0.7.0-13.el5 How reproducible: always Steps to Reproduce: 1. get an ia64 machine where RHEL-5.7 is installed 2. log in via console 3. reboot the machine and watch the start-up messages in console Actual results: ... Setting network parameters... [ OK ] Starting NetworkManager daemon: NetworkManager(2520): unaligned access to 0x600000000002b64c, ip=0x400000000009ec30 [ OK ] NetworkManager(2520): unaligned access to 0x600000000002b654, ip=0x400000000009ec70 NetworkManager(2520): unaligned access to 0x600000000002b65c, ip=0x400000000009ec80 NetworkManager(2520): unaligned access to 0x600000000002b74c, ip=0x400000000009ec30 NetworkManager(2520): unaligned access to 0x600000000002b754, ip=0x400000000009ec70 NetworkManager (pid 2520) is running... Waiting for network... Connecting.. 27sNetworkManager(2520): unaligned access to 0x600000000004884c, ip=0x400000000009ec30 Connecting.. 26sNetworkManager(2520): unaligned access to 0x6000000000048854, ip=0x400000000009ec70 NetworkManager(2520): unaligned access to 0x600000000004885c, ip=0x400000000009ec80 NetworkManager(2520): unaligned access to 0x600000000004884c, ip=0x400000000009ec30 NetworkManager(2520): unaligned access to 0x6000000000048854, ip=0x400000000009ec70 Starting beah-beaker-backend: [ OK ] beah-beaker-backend running as process 2558 NetworkManager (pid 2520) is running... ... Expected results: no "unaligned access" messages
Is there any way to figure out whether the access is indeed in NetworkManager or a bug in a library that NM links to?
I've tested that on a ia64 machine. The problem is in libnl source code present in RHEL's NM. The libnl upstream fixed that. So, we should take the patch: http://git.kernel.org/?p=libs/netlink/libnl.git;a=patch;h=0ca291d9e4ca1a9fd75982e7edb43325b40f5f10
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Not going to happen for RHEL5 but shouldn't be an issue with RHEL6.