From owner-freebsd-bugs@freebsd.org Wed Jun 29 06:59:32 2016 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B98D4B86B69 for ; Wed, 29 Jun 2016 06:59:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A94312892 for ; Wed, 29 Jun 2016 06:59:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5T6xWrc008027 for ; Wed, 29 Jun 2016 06:59:32 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 210683] [iscsi] FreeBSD panics almost immediately after starting ctld Date: Wed, 29 Jun 2016 06:59:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: emz@norma.perm.ru X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 06:59:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D210683 Bug ID: 210683 Summary: [iscsi] FreeBSD panics almost immediately after starting ctld Product: Base System Version: 11.0-CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: emz@norma.perm.ru FreeBSD panics almost immidiately after starting ctld. FreeBSD holds 24 disks for VM resources, which are organized on zfs pools; zvols are created which are distributed via iSCSI. FreeBSD was up for sever= al days, and then (all of a sudden, after some good production use) this panic appeared. Panic screen is attached. Panic is 100% reproducible after rebooting. I can also provide the direct server access if needed. Disks: =3D=3D=3DCut=3D=3D=3D [root@san1:~]# camcontrol devlist=20 at scbus1 target 4 lun 0 (pass0,ses0) at scbus1 target 5 lun 0 (pass1,da0) at scbus1 target 6 lun 0 (pass2,da1) at scbus1 target 7 lun 0 (pass3,da2) at scbus1 target 8 lun 0 (pass4,da3) at scbus1 target 9 lun 0 (pass5,da4) at scbus1 target 10 lun 0 (pass6,da5) at scbus1 target 11 lun 0 (pass7,da6) at scbus1 target 12 lun 0 (pass8,da7) at scbus1 target 13 lun 0 (pass9,da8) at scbus1 target 14 lun 0 (pass10,da9) at scbus1 target 15 lun 0 (pass11,da10) at scbus1 target 16 lun 0 (pass12,da11) at scbus1 target 17 lun 0 (pass13,da12) at scbus1 target 18 lun 0 (pass14,da13) at scbus1 target 19 lun 0 (pass15,da14) at scbus1 target 20 lun 0 (pass16,da15) at scbus1 target 21 lun 0 (pass17,da16) at scbus1 target 22 lun 0 (pass18,da17) at scbus1 target 23 lun 0 (pass19,da18) at scbus1 target 24 lun 0 (pass20,da19) at scbus1 target 25 lun 0 (pass21,da20) at scbus1 target 26 lun 0 (pass22,da21) at scbus1 target 27 lun 0 (pass23,da22) at scbus1 target 28 lun 0 (pass24,da23) at scbus6 target 0 lun 0 (pass25,ses1) at scbus13 target 0 lun 0 (pass26,ses2) =3D=3D=3DCut=3D=3D=3D Controller: =3D=3D=3DCut=3D=3D=3D # MegaCli -CfgDsply -aAll =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D Adapter: 0 Product Name: LSI MegaRAID SAS 9341-4i Memory: 0MB BBU: Absent Serial No: SV62122829 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D Number of DISK GROUPS: 0 Exit Code: 0x00 =3D=3D=3DCut=3D=3D=3D disks are used in JBOD/Passthrough mode. I have a dumpdev configured, but savecore sayd there's no core. Either my s= wap device is smaller, or there's just no core. --=20 You are receiving this mail because: You are the assignee for the bug.=