This bug has been copied from bug #549460 and has been proposed to be backported to 5.4 z-stream (EUS).
Created attachment 390211 [details] SymbolError.jpg Hi Jiri， show symbol resolving error on Alt+F4 when do DUD( USB flash driver) test, see attachment. ---------------------------------------------------------------------------- CONTEXT: ISO: rhel5.4-x86_64 DUD ISO Image: http://people.redhat.com/jolsa/dup/be2net-lpfc/dd-be2net-rhel5u4-2.101.377r-1.0el5.x86_64.iso.gz
Created attachment 394166 [details] be2net x86 network results
Created attachment 394167 [details] be2net x64 network results
set status to ON_DEV according to comment #4. Hi Jiri, could you please have a look? thanks.
(In reply to comment #4) > Created an attachment (id=390211) [details] > SymbolError.jpg > > Hi Jiri， > show symbol resolving error on Alt+F4 when do DUD( USB flash driver) test, > see attachment. > > ---------------------------------------------------------------------------- > CONTEXT: > ISO: rhel5.4-x86_64 > DUD ISO Image: > http://people.redhat.com/jolsa/dup/be2net-lpfc/dd-be2net-rhel5u4-2.101.377r-1.0el5.x86_64.iso.gz hi, thats strange, what kernel RHEL version are you installing? The DUP disk was made for kernel 2.6.18-164.el5 when you install the system, can you install the rpm itself? I haven't tried the DUP disk installation for be2net just for lpfc, but the pure rpm installation passes: [root@localhost test]# wget http://people.redhat.com/jolsa/dup/be2net-lpfc/dd-be2net-rhel5u4-2.101.377r-1.0el5.x86_64.iso.gz SNIP [root@localhost test]# sudo mount -o loop ./dd-be2net-rhel5u4-2.101.377r-1.0el5.x86_64.iso ./mnt/ [root@localhost test]# find mnt/ -name *.rpm mnt/rpms/2.6.18-164.el5/x86_64/kmod-be2net-rhel5u4-2.101.377r-1.0el5.x86_64.rpm mnt/rpms/2.6.18-164.el5/x86_64/kmod-be2net-xen-rhel5u4-2.101.377r-1.0el5.x86_64.rpm [root@localhost test]# rpm -ivh mnt/rpms/2.6.18-164.el5/x86_64/kmod-be2net-rhel5u4-2.101.377r-1.0el5.x86_64.rpm Preparing... ########################################### [100%] 1:kmod-be2net-rhel5u4 ########################################### [100%] [root@localhost test]# uname -a Linux localhost.localdomain 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux please verify the kernel version, if it is correct one, I'd need access to the machine you are trying this on, and hopefully it has some management console attached... (thats the reason I haven't tried the DUP disk installation test case for be2net, since I haven't found machine with management console and the be2net card) let me know, thanks jirka
I tested DUD with usb and CD today, did not met the problem that Alex described in comment #4. will wait for Alex come back and to see whether can reproduce it.
Hi Gregg, when I restart be2net network service by issuing "/etc/init.d/network restart", it reports Error in console: [root@hp-xw9400-03 ~]# be2net 0001:58:00.1: Error in cmd completion - opcode 73, compl 1, extd 0 Is this a problem? thanks.
This is the get tranciever data command failing. It can fail in some board skews. This message can be ignored. Subbu
Hi, can reproduce this symbol error bug during DUD loading stage by using : RHEL ISO( MD5SUM: 04fe3c10202402d7b389528d2bad0210 ): http://mohe.nay.redhat.com/share/iso/rhel5.4/x86_64/rhel-server-5.4-x86_64-dvd.iso DUD ISO: http://people.redhat.com/jolsa/dup/be2net-lpfc/dd-be2net-rhel5u4-2.101.377r-1.1el5.x86_64.iso.gz (In reply to comment #4) > Created an attachment (id=390211) [details] > SymbolError.jpg > > Hi Jiri， > show symbol resolving error on Alt+F4 when do DUD( USB flash driver) test, > see attachment. > > ---------------------------------------------------------------------------- > CONTEXT: > ISO: rhel5.4-x86_64 > DUD ISO Image: > http://people.redhat.com/jolsa/dup/be2net-lpfc/dd-be2net-rhel5u4-2.101.377r-1.0el5.x86_64.iso.gz
Per Jiri: the issue is sorted out.. missing dependency I've updated DUP disks in http://people.redhat.com/jolsa/dup/be2net-lpfc/ hence move back to ON_QA
Created attachment 397944 [details] Logs from HP on x64 DUP
Created attachment 397945 [details] Logs from HP on x86 DUP
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/RHEA-2010-0136.html
Created attachment 400542 [details] Final DUPs Logs Output for x86 and x86_64 systems with DUP installed and be2net/lpfc/rpm/etc. cmds executed.
Would you please help us understand if bugs and fixes referenced in this thread exhibit the issue below and resolve them? Problem Description: 10G NICs occasional stop passing traffic until we do ifdown and ifup on the interface. This issue is noted on several hosts. Nothing shows up in the logs :(. The setup: RHEL5u4 x86_64 with stock be2net on DL385G7 server with 10G emulex oneconnect NIC. Our farm consists of identical 7 x DL385G7, the 10G NICs are connected to a non routable 10G switch. They are used used for high speed communication of back end db processes. lspci output: 0f:00.0 Ethernet controller: ServerEngines Corp. Emulex OneConnect 10Gb NIC (rev 02) 0f:00.1 Ethernet controller: ServerEngines Corp. Emulex OneConnect 10Gb NIC (rev 02) [root@vrtdb05l-con-08 be2net]# modinfo be2net filename: /lib/modules/2.6.18-164.el5/kernel/drivers/net/benet/be2net.ko license: GPL author: ServerEngines Corporation description: ServerEngines BladeEngine2 10Gbps NICDriver 2.0.348 version: 2.0.348 srcversion: 016190A49C5F24C800E2E8F alias: pci:v000019A2d00000701sv*sd*bc*sc*i* alias: pci:v000019A2d00000700sv*sd*bc*sc*i* alias: pci:v000019A2d00000211sv*sd*bc*sc*i* depends: vermagic: 2.6.18-164.el5 SMP mod_unload gcc-4.1 parm: rx_frag_size:Size of a fragment that holds rcvd data. (uint) parm: lro:Configure LRO. 1 = ON (Default), 0 = OFF (uint) module_sig: 883f3504a8b7cb4bd273d74512bb11247ee09c843ba4e7c7cd0d249b1ad642c291cc3b455c4409f5ec2ae20f488b130345624c9ae9f7ce2752872b Logs: Nothing at all referenced :( We would like to understand if deploying a fix will help us address this issue and if any of the bugs fixed - could cause the problem we are experiencing. Would it be possible to enable logging for this module? I have trouble finding a good reference documents for be2net. Thanks ilya
Ilya, this bug isn't actually providing an updated kernel. It is providing a special updated driver that those using RHEL5.4 can use (usually for installation). I seem to recall hearing about this problem on be2net, but I do not know for sure if it has been fixed. I would suggest opening a ticket with our support organization or creating a new bugzilla with the contents of comment #33. If you open a new bug, assign it to ivecera and add me to the cc-list.
Andy, thanks for your response, new bug is opened, bug ID 727669 Unable to assign to ivecera as i have no permissions (i think). https://bugzilla.redhat.com/show_bug.cgi?id=727669