Sir,
I tried settip up intiitor and target on *real machines*

initiator on fedora 8 *2.6.32.3
*target on fedora 8 *2.6.23.1*

target started using fcconf on eth0: FLOGIs
inititor started on eth0 : FIP solicitation then FLOGIs
gets a few replies then
kernel dump at target

i have attached the error log in terminal*(err_log.txt)*,
dmesg output *(syslog.txt)*
and the wireshark trace taken at the target*([email protected])*

In the quickstart , it says the target shud be started first and then the
initiator for this issue
but i have done the same still the error?

i have pause enabled only at target . the initiator machine doesn't support
pause
is this what causing the problem?

thanks
-vinvishwa


On Sun, Feb 21, 2010 at 2:31 PM, vinvishwa <[email protected]> wrote:

> Sir,
> is there any way we can start the target without setting the pause
> parameters?
> my nic doesn't support pause (autonegotiation,rx tx is not supported)
> if i try starting the target without setting pause
> the following error:
> fcconf: fcc_fcoe_config: FCoE create of eth0 failed
> fcconf: fcc_fcoe_config: error 95  (null)
> fcconf: fcc_fcoe_config: exiting at fcc_fcoe.c:142
>
> I tried commenting the code in *fcoe_if.c*
> whcih checks for pause
> but it returns a *segmentation fault.*
> and the system hangs (so cant send you the syslog)
> thank you,
> -vinvishwa
>
>
> On Fri, Feb 12, 2010 at 12:03 AM, <[email protected]> wrote:
>
>> Vishwa,
>>
>> We can help you more if you can help us with the full spec of the setup
>> that you are using.
>>
>> -Steeve
>>
>> -----Original Message-----
>> From: [email protected] [mailto:[email protected]]
>> On Behalf Of Joe Eykholt
>> Sent: Thursday, February 11, 2010 11:32 PM
>> To: vinvishwa
>> Cc: [email protected]
>> Subject: Re: [Open-FCoE] Help with FCoE login process
>>
>> vinvishwa wrote:
>> > hi Sir
>> > sorry to disturb you once again
>> >
>> > As it implies from the previous discussions that configurations in
>> > virtual environment(Sun Virtual Box) seems clumsy and unreal ,
>> >
>> > I tried to switch to real hardware
>> > wanted to get some issues answered
>> >
>> >     * I do not have a server architecture nor a scsi disk ; *so will
>> >       normal SATA disk work as target disk?*
>>
>> Yes.  SCST even has a way of using a regular file as a target LUN.
>>
>> >     * Also i have set up FCoE target on Fedora 8 and then added the
>> >       target disk, but *fcconf returns* error  as pause settings are
>> not
>> >       enabled
>> >
>> >           o linux-ihct:/home/pxe123 # ethtool -A eth0 tx on rx on
>> >             Cannot get device pause settings: *Operation not
>> supported*
>> >           o *linux-g557:/ # ethtool -a eth0*
>> >             Pause parameters for eth0:
>> >             Cannot get device pause settings: Operation not supported
>>
>> You need a different Ethernet device, one that supports pause.
>> I would think most 1 gig or 10G  NICs support pause.
>>
>>        Joe
>>
>> >
>> > Please help me with this.
>> > Thank you,
>> > -vinvishwa
>> >
>> >
>> > On Thu, Feb 11, 2010 at 1:23 AM, Joe Eykholt <[email protected]
>> > <mailto:[email protected]>> wrote:
>> >
>> >     vinvishwa wrote:
>> >
>> >            Have you tried putting both sides in promiscuous mode?
>> >
>> >
>> >         No I didn't (as i didn't know how to)
>> >         But I will surely do this
>> >
>> >            I looked at the traces.    showed FLOGIs
>> >            from both sides but no accepts from either.  I can't
>> explain
>> >         that.
>> >            The other trace showed FLOGIs only from the initiator,
>> nothing
>> >            received from the target.  Why the difference?  Was the
>> wireshark
>> >            done on the target side?  Wireshark will go promiscuous, so
>> maybe
>> >            that's the difference.
>> >
>> >
>> >         The trace
>> >         fcoe_pcap_100110.pcap is from Wireshark running on host
>> >         m/c(windows XP.)
>> >
>> >         (the target and initiator are VMs in Sun Virtual box and both
>> >         are using bridged network)
>> >
>> >         and the 2nd trace named file was taken at the *initiator side
>> >         *with the tcpdump cmd
>> >           tcpdump -p -i ethX -w /tmp/file -s 0
>> >         *Does that mean that the inititor did not receive any of the
>> >         FLOGIs sent by the target?*
>> >         (but both the initiator and target m/cs can ping each other)
>> >
>> >
>> >     One problem is that the unicast address used by the FLOGI doesn't
>> >     work on switches, it's really meant to be point-to point (no
>> switch).
>> >     The FLOGI is sent to MAC 0e:fc:00:ff:ff:fe, a unicast address.
>> >     The switch should flood that to all ports since it doesn't know
>> >     the address.  The virtual switch may not do that since it "thinks"
>> >     it knows all the MAC addresses on the guests.  That would explain
>> >     why none of the ports receive the FLOGI.
>> >
>> >     If there was a way to directly connect the NICs of the two guests,
>> >     that would be nice, but there probably isn't since this is such
>> >     a special case.
>> >
>> >         I will do the steps suggested by you and will send it to you
>> >
>> >         Thank you really very much
>> >         -vinvishwa
>> >
>> >
>> >         On Wed, Feb 10, 2010 at 11:31 PM, Joe Eykholt
>> >         <[email protected] <mailto:[email protected]>
>> >         <mailto:[email protected] <mailto:[email protected]>>>
>> wrote:
>> >
>> >            Joe Eykholt wrote:
>> >
>> >                vinvishwa wrote:
>> >
>> >                    hello Sir,
>> >
>> >
>> >                     On Mon, Feb 8, 2010 at 5:25 PM, Joe Eykholt
>> >                    <[email protected] <mailto:[email protected]>
>> >         <mailto:[email protected] <mailto:[email protected]>>
>> >                    <mailto:[email protected]
>> >         <mailto:[email protected]> <mailto:[email protected]
>> >         <mailto:[email protected]>>>> wrote:
>> >
>> >                       vinvishwa wrote:
>> >
>> >                           Thank you sir for replying
>> >                           It made many things clear and also the
>> problem
>> >         with my
>> >                           configuration.
>> >
>> >                           but the issue with my configuration still
>> remains
>> >                    unsolved.
>> >
>> >                           and you said its currently broken
>> >                           so is there any workaround to get my point
>> to
>> >         point
>> >                    setup working?
>> >
>> >
>> >
>> >                                                    * (*my setup in Sun
>> >         Virtual Box
>> >                                          *initiator*: 2.6.33-rc4 on
>> >         Fedora Core
>> >                    12 with
>> >                           fcoeadm tool
>> >                                          *target*: 2.6.23 on Suse
>> Linux
>> >                    Enterprise Server
>> >                                                  initiator-target
>> connected
>> >                    over lossless
>> >                           connection in Sun Virtual Box(intel e1000
>> :bridged
>> >                    *pause frames
>> >                           enabled*)
>> >                                       *)*
>> >
>> >
>> >                       Actually, I may have mis-spoken earlier.  I just
>> >         tried it
>> >                    and a similar
>> >                       setup just worked for me.  I'm running the same
>> >         release
>> >                    on the
>> >                       initiator,
>> >                       and the target is 2.6.23-1.  I'm running on real
>> >         servers,
>> >                    though,
>> >                       not under a virtual machine.  It really
>> shouldn't
>> >         matter,
>> >                    however,
>> >                       as long as the virtual NIC works correctly.  I'm
>> >         running
>> >                    Fedora 8
>> >                       on my target, and Fedora 10 on the initiator.
>> >
>> >                       I tried it with the initiator having the larger
>> >         WWPN and
>> >                    also with
>> >                       the target having the larger WWPN, in case there
>> >         was a bug
>> >                       related to that.
>> >
>> >                       It will take a few retries for FLOGI to go
>> through
>> >         because
>> >                       it waits to see if FIP will work first.
>> >                       If it doesn't work for you, then I don't know
>> what
>> >         it is.
>> >                       You could send me binary tcpdump capture and I
>> >         might be able
>> >                       to point out the problem.   Use
>> >
>> >                              tcpdump -p -i ethX -w /tmp/file -s 0
>> >
>> >                       before you do 'fcoeadm -c ethX' on the initiator
>> side.
>> >
>> >                     i am attaching the tcp dump file
>> >                    also the wireshark tcpdump
>> >                     please have a look and help me solve the issue.
>> >
>> >                       You could also try putting the interface on both
>> >         sides into
>> >                       promiscuous mode, in case its a MAC filter
>> problem.
>> >
>> >                       The reason I gave the -p parameter on tcpdump is
>> >         so that
>> >                       it *doesn't* go promiscuous, since it might hide
>> >         the problem.
>> >
>> >                              Good luck,
>> >                              Joe
>> >
>> >                           thank you.
>> >
>> >
>> >
>> >
>> >                           On Mon, Feb 8, 2010 at 11:39 PM, Joe Eykholt
>> >                    <[email protected] <mailto:[email protected]>
>> >         <mailto:[email protected] <mailto:[email protected]>>
>> >                           <mailto:[email protected]
>> >         <mailto:[email protected]>
>> >                    <mailto:[email protected]
>> >         <mailto:[email protected]>>> <mailto:[email protected]
>> >         <mailto:[email protected]>
>> >
>> >                    <mailto:[email protected]
>> <mailto:[email protected]>>
>> >                           <mailto:[email protected]
>> >         <mailto:[email protected]>
>> >                    <mailto:[email protected]
>> >         <mailto:[email protected]>>>>> wrote:
>> >
>> >                              vinvishwa wrote:
>> >
>> >                                  hi,
>> >                                  i am trying to figure out the fcoe
>> login
>> >                    process in a
>> >                           point to point
>> >                                  architecture
>> >
>> >                                  In my setup the *target sends out
>> FLOGIs*
>> >                    (this is right
>> >                           as per the
>> >                                  quickstart guide at open-fcoe)
>> >
>> >                                  when the initiator is started it
>> sends
>> >         an *FIP
>> >                    solicitation*
>> >                                  and then starts sending FLOGIs but is
>> *not
>> >                    able to login*
>> >
>> >                                  Can someone please elaborate the
>> *point to
>> >                    point fcoe
>> >                           login* process
>> >
>> >
>> >                              It is currently broken.  The old target
>> >         expects a
>> >                           non-standard interface
>> >                              in which the other end accepts the FLOGI
>> >         with the
>> >                    fabric flag off
>> >                              indicating
>> >                              point to point, and with the assigned
>> FC_IDs in
>> >                    the FLOGI accept.
>> >                              I'm not sure why that's been broken in
>> the
>> >                    initiator, but
>> >                           point-to-point
>> >                              mode hasn't been enough of a priority.
>> >
>> >                              The correct, standard FC way of doing it
>> is for
>> >                    both sides to
>> >                           send a
>> >                              LS_ACC for FLOGI from fffffe to 0 and
>> then
>> >         for the
>> >                    one with the
>> >                              higher WWPN
>> >                              to decide the FC_IDs and do a PLOGI.
>> >
>> >                              There's a FIP proposal (at least one) to
>> do
>> >         VN to
>> >                    VN port
>> >                           without a
>> >                              fabric,
>> >                              and I hope we'll implement that at some
>> point.
>> >
>> >                              The current initiator sends out both a
>> FIP
>> >                    solicitation and
>> >                           non-FIP
>> >                              FLOGIs
>> >                              until it receives either a FIP frame, at
>> which
>> >                    point it
>> >                           enters FIP mode,
>> >                              or an LS_ACC for the FLOGI, at which
>> point it
>> >                    continues in
>> >                           non-FIP mode.
>> >
>> >
>> >                                  Also i tried to figure out the fcoe
>> >         initiator
>> >                    code but
>> >                           couldn't
>> >                                  get the
>> >                                  starting point
>> >                                           Plz help me with the entry
>> >         point of
>> >                    the code
>> >
>> >
>> >                              The module_init fcoe_init() is one entry
>> point.
>> >                     Another is
>> >                           the code
>> >                              that handles
>> >                              the creation of an new initiator thru
>> /sys
>> >         write:
>> >                    fcoe_create().
>> >
>> >                                     Joe
>> >
>> >
>> >
>> >
>> >                           --        -vinvishwa
>> >
>> >
>> >                I don't know what the problem is.
>> >
>> >                Have you tried putting both sides in promiscuous mode?
>> >
>> >                       ifconfig ethX promisc
>> >
>> >                I don't really think that will fix it, but it is worth
>> a try.
>> >
>> >                I looked at the traces.   fcoe_pcap_100110.pcap showed
>> FLOGIs
>> >                from both sides but no accepts from either.  I can't
>> >         explain that.
>> >                The other trace showed FLOGIs only from the initiator,
>> >         nothing
>> >                received from the target.  Why the difference?  Was the
>> >         wireshark
>> >                done on the target side?  Wireshark will go
>> promiscuous,
>> >         so maybe
>> >                that's the difference.
>> >
>> >                On the initiator side, you could enable debug logging
>> and
>> >         that
>> >                might help us figure it out.  Do this as root after the
>> >                initiator is started:
>> >
>> >                       echo 15 >
>> /sys/module/libfc/parameters/debug_logging
>> >                       echo 3  >
>> /sys/module/fcoe/parameters/debug_logging
>> >
>> >
>> >            Also add:
>> >
>> >                   echo 3 >
>> /sys/module/libfcoe/parameters/debug_logging
>> >
>> >            We might as well get everything we can get!
>> >
>> >
>> >                       dmesg -n 8
>> >                       # wait at least 10 seconds with the initiator
>> >         running then:
>> >                       dmesg | tail
>> >
>> >
>> >            Make that
>> >                   dmesg | tail -100
>> >
>> >            so we get a good hunk of log.  If you could send that, it
>> may
>> >         help.
>> >
>> >
>> >                Good luck.
>> >
>> >                       Joe
>> >
>> >
>> >                _______________________________________________
>> >                devel mailing list
>> >                [email protected] <mailto:[email protected]>
>> >         <mailto:[email protected] <mailto:[email protected]>>
>> >
>> >                http://www.open-fcoe.org/mailman/listinfo/devel
>> >
>> >
>> >
>> >
>> >
>>
>> _______________________________________________
>> devel mailing list
>> [email protected]
>> http://www.open-fcoe.org/mailman/listinfo/devel
>>
>>
>
[r...@localhost ~]# modprobe openfctgt
[r...@localhost ~]# modprobe fcoe
[r...@localhost ~]# ethtool -a eth0
Pause parameters for eth0:
Autonegotiate:  off
RX:             off
TX:             off

[r...@localhost ~]# ethtool -A eth0 rx on tx on
[r...@localhost ~]# fcconf
Name          WWPN                      FC-ID   FC         Network   
eth0          20:00:00:22:15:bd:d9:32        0  No HBA     UP           
[r...@localhost ~]# fcconf eth0 enable
fcconf: device file /dev/openfc does not exist- check udev and rules
[r...@localhost ~]# 
Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: ------------[ cut here ]------------

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: invalid opcode: 0000 [#1]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: SMP 

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: CPU:    1

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: EIP:    0060:[<f8b9768b>]    Not tainted VLI

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: EFLAGS: 00010246   (2.6.23.1 #1)

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: EIP is at openfct_session_create+0x18/0xce [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: eax: f5bd4000   ebx: f5b36400   ecx: 00010101   edx: f6dac080

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: esi: f6dac080   edi: 00000000   ebp: 00000000   esp: f5bc9e00

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: Process fcoethread/1 (pid: 3050, ti=f5bc9000 task=f5d7c620 
task.ti=f5bc9000)

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: Stack: 0049474f 70736572 f5bc9e88 ffffffff f6dac080 f8ba86cc 00000002 
00000000 

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:        f6d6d02c f8ba6a50 f5b36400 f6dac080 00000000 00000000 f8b988db 
f6d6d02c 

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:        f8ba6a50 f8ba55be f5bc9e54 f8b98888 f6d6e82c f61d0e00 f5f509c0 
f8ba211a 

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: Call Trace:

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b988db>] fcs_local_port_prli_accept+0x53/0x91 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8ba55be>] sa_log+0x15/0x17 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b98888>] fcs_local_port_prli_accept+0x0/0x91 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8ba211a>] fc_sess_recv_req+0x1d9/0x98d [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8ba2e74>] fc_sess_lookup_create+0xf8/0x101 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b9e815>] fc_local_port_recv_req+0xaf/0x159 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b9adfb>] fc_exch_recv_req+0x71e/0x7da [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b9e766>] fc_local_port_recv_req+0x0/0x159 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8ba548e>] sa_hash_lookup+0x34/0x3f [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b9eb26>] fc_local_port_recv+0x267/0x326 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b9e766>] fc_local_port_recv_req+0x0/0x159 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8ba484a>] fc_port_ingress+0x61/0x67 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b8485d>] fcoe_percpu_receive_thread+0x66e/0x792 [fcoe]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<f8b841ef>] fcoe_percpu_receive_thread+0x0/0x792 [fcoe]

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<c043cf85>] kthread+0x38/0x5f

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<c043cf4d>] kthread+0x0/0x5f

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  [<c0405c0f>] kernel_thread_helper+0x7/0x10

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel:  =======================

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: Code: 6e fb ff 89 f2 89 d8 5b 5e 5f e9 e0 a5 a7 c7 5b 5e 5f c3 55 57 
56 53 83 ec 28 89 54 24 10 8b b8 04 21 00 00 8b 4a 1c 85 ff 75 04 <0f> 0b eb fe 
8b 6f 2c 8b 55 00 eb 0d 3b 4d 10 0f 84 97 00 00 00 

Message from sysl...@localhost at Feb 22 01:38:50 ...
 kernel: EIP: [<f8b9768b>] openfct_session_create+0x18/0xce [openfctgt] SS:ESP 
0068:f5bc9e00

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: ------------[ cut here ]------------

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: invalid opcode: 0000 [#2]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: SMP 

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: CPU:    0

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: EIP:    0060:[<f8b9768b>]    Tainted: G      D VLI

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: EFLAGS: 00010246   (2.6.23.1 #1)

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: EIP is at openfct_session_create+0x18/0xce [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: eax: f5bd4000   ebx: f5b36400   ecx: 00010101   edx: f6dac080

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: esi: f6dac080   edi: 00000000   ebp: 00000000   esp: f5bcae00

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: Process fcoethread/0 (pid: 3049, ti=f5bca000 task=f5d7cc40 
task.ti=f5bca000)

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: Stack: f8b850d5 f5b36a80 f5a11c00 f8b99a18 f6dac080 00000020 c05aaf73 
f5a11c00 

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:        00980000 f540042c f5b36400 f6dac080 00000000 00000000 f8b988db 
00000001 

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:        f5f509c0 f5a11c00 00000004 f8b98888 f6d6f02c f61d0e00 f5f509c0 
f8ba211a 

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: Call Trace:

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b850d5>] fcoe_frame_alloc+0x4e/0xed [fcoe]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b99a18>] fc_exch_complete_locked+0x6d/0x9e [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<c05aaf73>] __alloc_skb+0x4d/0xfb

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b988db>] fcs_local_port_prli_accept+0x53/0x91 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b98888>] fcs_local_port_prli_accept+0x0/0x91 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8ba211a>] fc_sess_recv_req+0x1d9/0x98d [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8ba2e74>] fc_sess_lookup_create+0xf8/0x101 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b9e815>] fc_local_port_recv_req+0xaf/0x159 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b9adfb>] fc_exch_recv_req+0x71e/0x7da [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b9e766>] fc_local_port_recv_req+0x0/0x159 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8ba548e>] sa_hash_lookup+0x34/0x3f [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b9eb26>] fc_local_port_recv+0x267/0x326 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b9e766>] fc_local_port_recv_req+0x0/0x159 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8ba484a>] fc_port_ingress+0x61/0x67 [openfctgt]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b8485d>] fcoe_percpu_receive_thread+0x66e/0x792 [fcoe]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<f8b841ef>] fcoe_percpu_receive_thread+0x0/0x792 [fcoe]

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<c043cf85>] kthread+0x38/0x5f

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<c043cf4d>] kthread+0x0/0x5f

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  [<c0405c0f>] kernel_thread_helper+0x7/0x10

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel:  =======================

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: Code: 6e fb ff 89 f2 89 d8 5b 5e 5f e9 e0 a5 a7 c7 5b 5e 5f c3 55 57 
56 53 83 ec 28 89 54 24 10 8b b8 04 21 00 00 8b 4a 1c 85 ff 75 04 <0f> 0b eb fe 
8b 6f 2c 8b 55 00 eb 0d 3b 4d 10 0f 84 97 00 00 00 

Message from sysl...@localhost at Feb 22 01:38:52 ...
 kernel: EIP: [<f8b9768b>] openfct_session_create+0x18/0xce [openfctgt] SS:ESP 
0068:f5bcae00


device eth0 entered promiscuous mode
 mtu 1478
eth0: link down.
eth0: link up.
[3015]: scst: scst_unregister_target_template:336:Target template openfct 
unregistered successfully
[3041]: scst: __scst_register_target_template:275:Target template openfct 
registered successfully
eth0: link up.
 mtu 1478
fc_local_port_flogi_resp: bad FLOGI response
fc_local_port_flogi_resp fffffe -> 000000 xids 0011 0001 ELS rep ELS LS_ACC
------------[ cut here ]------------
kernel BUG at /root/open-fcoe-target/openfctgt/openfc_scst_pkt.h:119!
invalid opcode: 0000 [#1]
SMP 
Modules linked in: fcoe openfctgt scst_vdisk scst_disk scst scsi_transport_fc 
fuse rfcomm l2cap bluetooth autofs4 sunrpc nf_conntrack_ipv4 ipt_REJECT 
iptable_filter ip_tables nf_conntrack_ftp nf_conntrack_ipv6 xt_state 
nf_conntrack nfnetlink xt_tcpudp ip6t_ipv6header ip6t_REJECT ip6table_filter 
ip6_tables x_tables cpufreq_ondemand acpi_cpufreq dm_mirror dm_multipath dm_mod 
ipv6 snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq 
snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm button snd_timer snd soundcore 
snd_page_alloc parport_pc forcedeth parport sg pata_amd ahci ata_generic libata 
sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd
CPU:    1
EIP:    0060:[<f8b9768b>]    Not tainted VLI
EFLAGS: 00010246   (2.6.23.1 #1)
EIP is at openfct_session_create+0x18/0xce [openfctgt]
eax: f5bd4000   ebx: f5b36400   ecx: 00010101   edx: f6dac080
esi: f6dac080   edi: 00000000   ebp: 00000000   esp: f5bc9e00
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Process fcoethread/1 (pid: 3050, ti=f5bc9000 task=f5d7c620 task.ti=f5bc9000)
Stack: 0049474f 70736572 f5bc9e88 ffffffff f6dac080 f8ba86cc 00000002 00000000 
       f6d6d02c f8ba6a50 f5b36400 f6dac080 00000000 00000000 f8b988db f6d6d02c 
       f8ba6a50 f8ba55be f5bc9e54 f8b98888 f6d6e82c f61d0e00 f5f509c0 f8ba211a 
Call Trace:
 [<f8b988db>] fcs_local_port_prli_accept+0x53/0x91 [openfctgt]
 [<f8ba55be>] sa_log+0x15/0x17 [openfctgt]
 [<f8b98888>] fcs_local_port_prli_accept+0x0/0x91 [openfctgt]
 [<f8ba211a>] fc_sess_recv_req+0x1d9/0x98d [openfctgt]
 [<f8ba2e74>] fc_sess_lookup_create+0xf8/0x101 [openfctgt]
 [<f8b9e815>] fc_local_port_recv_req+0xaf/0x159 [openfctgt]
 [<f8b9adfb>] fc_exch_recv_req+0x71e/0x7da [openfctgt]
 [<f8b9e766>] fc_local_port_recv_req+0x0/0x159 [openfctgt]
 [<f8ba548e>] sa_hash_lookup+0x34/0x3f [openfctgt]
 [<f8b9eb26>] fc_local_port_recv+0x267/0x326 [openfctgt]
 [<f8b9e766>] fc_local_port_recv_req+0x0/0x159 [openfctgt]
 [<f8ba484a>] fc_port_ingress+0x61/0x67 [openfctgt]
 [<f8b8485d>] fcoe_percpu_receive_thread+0x66e/0x792 [fcoe]
 [<f8b841ef>] fcoe_percpu_receive_thread+0x0/0x792 [fcoe]
 [<c043cf85>] kthread+0x38/0x5f
 [<c043cf4d>] kthread+0x0/0x5f
 [<c0405c0f>] kernel_thread_helper+0x7/0x10
 =======================
Code: 6e fb ff 89 f2 89 d8 5b 5e 5f e9 e0 a5 a7 c7 5b 5e 5f c3 55 57 56 53 83 
ec 28 89 54 24 10 8b b8 04 21 00 00 8b 4a 1c 85 ff 75 04 <0f> 0b eb fe 8b 6f 2c 
8b 55 00 eb 0d 3b 4d 10 0f 84 97 00 00 00 
EIP: [<f8b9768b>] openfct_session_create+0x18/0xce [openfctgt] SS:ESP 
0068:f5bc9e00
------------[ cut here ]------------
kernel BUG at /root/open-fcoe-target/openfctgt/openfc_scst_pkt.h:119!
invalid opcode: 0000 [#2]
SMP 
Modules linked in: fcoe openfctgt scst_vdisk scst_disk scst scsi_transport_fc 
fuse rfcomm l2cap bluetooth autofs4 sunrpc nf_conntrack_ipv4 ipt_REJECT 
iptable_filter ip_tables nf_conntrack_ftp nf_conntrack_ipv6 xt_state 
nf_conntrack nfnetlink xt_tcpudp ip6t_ipv6header ip6t_REJECT ip6table_filter 
ip6_tables x_tables cpufreq_ondemand acpi_cpufreq dm_mirror dm_multipath dm_mod 
ipv6 snd_hda_intel snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq 
snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm button snd_timer snd soundcore 
snd_page_alloc parport_pc forcedeth parport sg pata_amd ahci ata_generic libata 
sd_mod scsi_mod ext3 jbd mbcache uhci_hcd ohci_hcd ehci_hcd
CPU:    0
EIP:    0060:[<f8b9768b>]    Tainted: G      D VLI
EFLAGS: 00010246   (2.6.23.1 #1)
EIP is at openfct_session_create+0x18/0xce [openfctgt]
eax: f5bd4000   ebx: f5b36400   ecx: 00010101   edx: f6dac080
esi: f6dac080   edi: 00000000   ebp: 00000000   esp: f5bcae00
ds: 007b   es: 007b   fs: 00d8  gs: 0000  ss: 0068
Process fcoethread/0 (pid: 3049, ti=f5bca000 task=f5d7cc40 task.ti=f5bca000)
Stack: f8b850d5 f5b36a80 f5a11c00 f8b99a18 f6dac080 00000020 c05aaf73 f5a11c00 
       00980000 f540042c f5b36400 f6dac080 00000000 00000000 f8b988db 00000001 
       f5f509c0 f5a11c00 00000004 f8b98888 f6d6f02c f61d0e00 f5f509c0 f8ba211a 
Call Trace:
 [<f8b850d5>] fcoe_frame_alloc+0x4e/0xed [fcoe]
 [<f8b99a18>] fc_exch_complete_locked+0x6d/0x9e [openfctgt]
 [<c05aaf73>] __alloc_skb+0x4d/0xfb
 [<f8b988db>] fcs_local_port_prli_accept+0x53/0x91 [openfctgt]
 [<f8b98888>] fcs_local_port_prli_accept+0x0/0x91 [openfctgt]
 [<f8ba211a>] fc_sess_recv_req+0x1d9/0x98d [openfctgt]
 [<f8ba2e74>] fc_sess_lookup_create+0xf8/0x101 [openfctgt]
 [<f8b9e815>] fc_local_port_recv_req+0xaf/0x159 [openfctgt]
 [<f8b9adfb>] fc_exch_recv_req+0x71e/0x7da [openfctgt]
 [<f8b9e766>] fc_local_port_recv_req+0x0/0x159 [openfctgt]
 [<f8ba548e>] sa_hash_lookup+0x34/0x3f [openfctgt]
 [<f8b9eb26>] fc_local_port_recv+0x267/0x326 [openfctgt]
 [<f8b9e766>] fc_local_port_recv_req+0x0/0x159 [openfctgt]
 [<f8ba484a>] fc_port_ingress+0x61/0x67 [openfctgt]
 [<f8b8485d>] fcoe_percpu_receive_thread+0x66e/0x792 [fcoe]
 [<f8b841ef>] fcoe_percpu_receive_thread+0x0/0x792 [fcoe]
 [<c043cf85>] kthread+0x38/0x5f
 [<c043cf4d>] kthread+0x0/0x5f
 [<c0405c0f>] kernel_thread_helper+0x7/0x10
 =======================
Code: 6e fb ff 89 f2 89 d8 5b 5e 5f e9 e0 a5 a7 c7 5b 5e 5f c3 55 57 56 53 83 
ec 28 89 54 24 10 8b b8 04 21 00 00 8b 4a 1c 85 ff 75 04 <0f> 0b eb fe 8b 6f 2c 
8b 55 00 eb 0d 3b 4d 10 0f 84 97 00 00 00 
EIP: [<f8b9768b>] openfct_session_create+0x18/0xce [openfctgt] SS:ESP 
0068:f5bcae00

_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel

Reply via email to