This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1284] New: DomU iscsi initiator crashes on login

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1284] New: DomU iscsi initiator crashes on login
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Sun, 29 Jun 2008 01:07:51 -0700
Delivery-date: Sun, 29 Jun 2008 01:07:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: DomU iscsi initiator crashes on login
           Product: Xen
           Version: 3.0.3
          Platform: Other
        OS/Version: Linux-2.6
            Status: NEW
          Severity: major
          Priority: P2
         Component: Guest-OS
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: niko.lilja@xxxxxx

I wonder if there has been any solutions for this particular problem when
mapping disk from iscsi target to DomU host.

Currently running debian etch with 2.6.18 xen kernel on DomU and when
initiating login with iscsiadmin (open-iscsi) to the iscsi target the kernel
goes oops.

stack trace:

Unable to handle kernel NULL pointer dereference at 0000000000000078 RIP: 
 [<ffffffff8807f3a2>] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49
PGD 7be38067 PUD 7ecbc067 PMD 0 
Oops: 0000 [1] SMP 
CPU 0 
Modules linked in: ipv6 ib_iser rdma_cm ib_addr ib_cm ib_sa ib_mad ib_core
iscsi_tcp libiscsi scsi_transport_iscsi scsi_mod dm_snapshot dm_mirror
dm_multipath dm_mod evdev pcspkr 8250 serial_core ext3 jbd mbcache
Pid: 1476, comm: iscsid Not tainted 2.6.18-6-xen-amd64 #1
RIP: e030:[<ffffffff8807f3a2>]  [<ffffffff8807f3a2>]
RSP: e02b:ffff88007b901c30  EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff88007db70048 RCX: 0000000000000071
RDX: 0000000000000067 RSI: 0000000000000400 RDI: ffff8800001a8800
RBP: ffff8800001a8800 R08: ffff88007d98c000 R09: 00000000000041ed
R10: ffffffff880808d0 R11: 0000000000000048 R12: ffff88007b883828
R13: ffff8800001a8800 R14: 0000000000000000 R15: ffff88007b883800
FS:  00002b4eed21c6d0(0000) GS:ffffffff804c3000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process iscsid (pid: 1476, threadinfo ffff88007b900000, task ffff88007d9c5100)
Stack:  ffffffff8807f9f2  ffff88007b881000  ffff88007b881000  ffff88007b883800 
 ffffffff88081641  ffff8800001a8968  000000018807b1fe  ffff8800001a8800 
 0000000000000000  0000000000000000 
Call Trace:
 [<ffffffff8807f9f2>] :scsi_mod:scsi_alloc_queue+0x65/0xb6
 [<ffffffff88081641>] :scsi_mod:scsi_alloc_sdev+0x12e/0x1d2
 [<ffffffff88081870>] :scsi_mod:scsi_probe_and_add_lun+0x10d/0x9c6
 [<ffffffff8808246c>] :scsi_mod:scsi_alloc_target+0x21e/0x327
 [<ffffffff880826b8>] :scsi_mod:__scsi_scan_target+0xc3/0x5e7
 [<ffffffff8020ba57>] do_page_fault+0xdce/0x112f
 [<ffffffff8024c23e>] sscanf+0x49/0x51
 [<ffffffff88082e86>] :scsi_mod:scsi_scan_target+0x6c/0x83
 [<ffffffff880a2e2a>] :scsi_transport_iscsi:iscsi_user_scan+0x65/0x94
 [<ffffffff880836f9>] :scsi_mod:store_scan+0x9b/0xc5
 [<ffffffff802da599>] sysfs_write_file+0xb4/0xe3
 [<ffffffff80216ac9>] vfs_write+0xce/0x174
 [<ffffffff802172ec>] sys_write+0x45/0x6e
 [<ffffffff8025be4a>] system_call+0x86/0x8b
 [<ffffffff8025bdc4>] system_call+0x0/0x8b

Code: 83 78 78 00 75 0c 48 8b 05 59 ea 4c f8 48 c1 e0 0c c3 48 8b 
RIP  [<ffffffff8807f3a2>] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49
 RSP <ffff88007b901c30>
CR2: 0000000000000078

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>