Does anyone have similar issues like this?

On Nov 22, 9:58 am, Kenny Kang Sun <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I'm running a SLES 10 SP2 box and encountered a kernel bug during
> iSCSI login process.
>
> The kernel version I'm running is 2.6.16.60-0.21-smp, and the open-
> iscsi I'm using is open-iscsi-2.0.707-0.44
>
> I used two hosts and two eth ports on each. The two hosts have shared
> access to the same volumes.
>
> Multipath is used via Ifaces.
>
> Target: iqn.2001-05.com.equallogic:0-8a0906-a40362403-566a3b6d36848feb-
> lxrt-48
>         Current Portal: 192.168.0.2:3260,1
>         Persistent Portal: 192.168.0.18:3260,1
>                 **********
>                 Interface:
>                 **********
>                 Iface Name: eth1
>                 Iface Transport: tcp
>                 Iface Initiatorname: iqn.1996-04.de.suse:
> 01:34abf45cafd4
>                 Iface IPaddress: 192.168.0.4
>                 Iface HWaddress: 00:1A:A0:2B:7A:75
>                 Iface Netdev: eth0
>                 SID: 31
>                 iSCSI Connection State: LOGGED IN
>                 iSCSI Session State: Unknown
>                 Internal iscsid Session State: NO CHANGE
>         Current Portal: 192.168.0.12:3260,1
>         Persistent Portal: 192.168.0.18:3260,1
>                 **********
>                 Interface:
>                 **********
>                 Iface Name: eth2
>                 Iface Transport: tcp
>                 Iface Initiatorname: iqn.1996-04.de.suse:
> 01:34abf45cafd4
>                 Iface IPaddress: 192.168.0.3
>                 Iface HWaddress: 00:1A:A0:2B:7A:73
>                 Iface Netdev: eth4
>                 SID: 32
>                 iSCSI Connection State: LOGGED IN
>                 iSCSI Session State: Unknown
>                 Internal iscsid Session State: NO CHANGE
>
> The problem is during reboot, kernel bug is seen while the initiator
> tries to login to the targets.
>
> here's some information at the scene:
>
> ------------cut from here---------------------
> Kernel BUG at drivers/scsi/libiscsi.c:353
> invalid opcode: 0000 [1] SMP
> last sysfs file: /class/iscsi_connection/connection77:0/exp_statsn
>
> Entering kdb (current=0xffffffff80374320, pid 0) on processor 0 Oops:
> <NULL>
> due to oops @ 0xffffffff8857ce9d
>     r15 = 0x0000000000000000      r14 = 0x0000000000000000
>     r13 = 0xffffffff80490908      r12 = 0xffff810122204a50
>     rbp = 0x0000000000000000      rbx = 0x0000000000000000
>     r11 = 0xffff810122cfc180      r10 = 0xffff81012964f500
>      r9 = 0xffffffff80490a84       r8 = 0xffff810120602c90
>     rax = 0x0000000000000002      rcx = 0x0000000000000000
>     rdx = 0xffff810120602c90      rsi = 0xffffffff80490908
>     rdi = 0xffff810122204a50 orig_rax = 0xffffffffffffffff
>     rip = 0xffffffff8857ce9d       cs = 0x0000000000000010
>  eflags = 0x0000000000010246      rsp = 0xffffffff804908c8
>      ss = 0x0000000000000018 &regs = 0xffffffff80490818
> [0]kdb> bt
> Stack traceback for pid 0
> 0xffffffff80374320        0        0  1    0   R  0xffffffff80374660
> *swapper
> RSP           RIP                Function (args)
> 0xffffffff804908c8 0xffffffff8857ce9d [libiscsi]__iscsi_conn_send_pdu
> +0x58 (0x8040, 0x0, 0x2f006a00ffffffff, 0x0, 0x0)
> 0xffffffff80490908 0xffffffff8857d5ff [libiscsi]iscsi_send_nopout+0x7c
> (0xffff81012964f000, 0xffff810128a6e800, 0x0, 0xf)
> 0xffffffff80490958 0xffffffff8857dfad [libiscsi]__iscsi_complete_pdu
> +0x341 (0x200021a72aa0, 0xffff81011033a820, 0xffff81)
> 0xffffffff804909d8 0xffffffff8857e1bb [libiscsi]iscsi_complete_pdu
> +0x36 (0x0, 0x0, 0x0, 0xffff810122cfc180, 0xffff810122)
> 0xffffffff80490a08 0xffffffff88593f9d
> [iscsi_tcp]iscsi_tcp_hdr_recv_done+0x72a (0xffff81012964f000,
> 0xffff81011033a820, )
> 0xffffffff80490a88 0xffffffff802aa189 __qdisc_run+0x36 (0x3000000000,
> 0xffff81010d34ac54, 0x3000000000, 0x0, 0xffff81012)
> 0xffffffff80490ac8 0xffffffff8859382a [iscsi_tcp]iscsi_tcp_recv+0x3c0
> (0x22d27cf0, 0xffff810122cfc180, 0x20, 0xffff81010)
> 0xffffffff80490b78 0xffffffff802c418e tcp_read_sock+0xa9
> (0xffff8101086ae0c0, 0x1, 0xffff810122204a50, 0xffffffff802cd08)
> 0xffffffff80490bc8 0xffffffff88594251 [iscsi_tcp]iscsi_tcp_data_ready
> +0x47 (0xffff81010d34ac20, 0xffff810122cfc280, 0xff)
> 0xffffffff80490d28 0xffffffff802b8d61 ip_local_deliver+0x1b3
> (0xffff810122cfc280, 0xffffffff803bcb40, 0x23089770, 0x72, )
> 0xffffffff80490d88 0xffffffff8029935d netif_receive_skb+0x425
> (0xffff81012aa25870, 0x72)
> 0xffffffff80490dc8 0xffffffff881c8003 [e1000]e1000_receive_skb+0x1c1
> (0x4000000001, 0xffffffff80490ebc, 0xffff81012b278c)
> 0xffffffff80490de8 0xffffffff881ce502 [e1000]e1000_clean_rx_irq_ps
> +0x517 (0x82, 0x46, 0x82, 0x0, 0xffffffffffffffff)
> 0xffffffff80490f38 0xffffffff80138b8d __do_softirq+0x55
> (0xffffffff80490f70)
> 0xffffffff80490f68 0xffffffff8010c00e call_softirq+0x1e
> 0xffffffff80490f78 0xffffffff8010d05c do_softirq+0x2c (0x0)
> 0xffffffff80490f88 0xffffffff80138ce4 irq_exit+0x48
> (0xffffffff8044feb8)
> 0xffffffff80490f98 0xffffffff8010d426 do_IRQ+0x40
> 0xffffffff80490fb8 0xffffffff8010b36c ret_from_intr
> [0]more>
> Only 'q' or 'Q' are processed at more prompt, input ignored
> Interrupt registers:
>     r15 = 0xffffffff8044feb8      r14 = 0x0000000000000000
>     r13 = 0x0000000000000000      r12 = 0x0000000000000000
>     rbp = 0x0000000000000000      rbx = 0x0000000000000000
>     r11 = 0x0000000000000000      r10 = 0x0000000000000000
>      r9 = 0x0000000000000000       r8 = 0x0000000000000000
>     rax = 0x0000000000000000      rcx = 0x0000000000000000
>     rdx = 0x0000000000000000      rsi = 0x0000000000000000
>     rdi = 0x0000000000000000 orig_rax = 0x0000000000000000
>     rip = 0x0000000000000000       cs = 0x0000000000000000
>  eflags = 0x0000000000000000      rsp = 0x0000000000000000
>      ss = 0x0000000000000000 &regs = 0xffffffff80490fb8
> Interrupt from user space, end of kernel trace
>
> Does anyone have any idea?
>
> Best,
> Kenny
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"open-iscsi" group.
To post to this group, send email to open-iscsi@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/open-iscsi
-~----------~----~----~----~------~----~------~--~---

Reply via email to