From owner-freebsd-scsi@FreeBSD.ORG Tue Nov 29 15:11:15 2005 Return-Path: X-Original-To: freebsd-scsi@freebsd.org Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D6BA16A41F for ; Tue, 29 Nov 2005 15:11:15 +0000 (GMT) (envelope-from rajesh_ghanekar@persistent.co.in) Received: from smtp.persistent.co.in (smtp.persistent.co.in [202.54.11.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 704AA43D46 for ; Tue, 29 Nov 2005 15:11:13 +0000 (GMT) (envelope-from rajesh_ghanekar@persistent.co.in) Received: from [10.77.196.113] ([10.77.196.113]) (authenticated bits=0) by smtp.persistent.co.in (8.12.9/) with ESMTP id jATFBJMr023361 for ; Tue, 29 Nov 2005 20:41:22 +0530 Message-ID: <438C750D.5030604@persistent.co.in> Date: Tue, 29 Nov 2005 21:04:37 +0530 From: "Rajesh S. Ghanekar" User-Agent: Mozilla Thunderbird 0.8 (X11/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAQAAAAQ= X-Whitelist: TRUE Subject: isp driver - inquiry changed X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 15:11:15 -0000 Hi, I am using FreeBSD-4.10 with isp driver on HP EVA-8k SAN box. The description of the problem is as follows: 1. Two machines are using HP EVA-8k with only single controller active. 2. Both of these machines are doing heavy IO on the their individual LUNs. 3. Now if any one of the machine is rebooted, the other machine's OS panics and reboots. Both the machines are using FreeBSD-4.10. Here is the debug info attached. ------------------------------ Debug Info -------------------------------------------------- (da0:isp0:0:2:1): (da0:isp0:0:2:1): (da0:isp0:0:2:1): (da0:isp0:0:2:1): (da0:isp0:0:2:1): (da0:isp0:0:2:1): (da 0:isp0:0:2:1): Invalidating pack (da0:isp0:0:2:1): . CDB: 1b 0 0 0 1 0 (da0:isp0:0:2:1): . CDB: 2a 0 e 40 1a 23 0 0 4 0 (da0:isp0:0:2:1): . CDB: 28 0 f 58 53 92 0 0 4 0 (da0:isp0:0:2:1): . CDB: 28 0 f 93 38 7f 0 0 4 0 (da0:isp0:0:2:1): . CDB: 2a 0 1a 6e 50 9b 0 0 4 0 (da0:isp0:0:2:1): (da0:isp0:0:2:1): (da0:isp0:0:2:1): (da0:isp0:0:2:1): . CDB: 2a 0 16 90 45 14 0 0 4 0 (da0:isp0:0:2:1): . CDB: 2a 0 1 58 a7 60 0 0 4 0 (da0:isp0:0:2:1): . CDB: 28 0 a d6 c1 9d 0 0 4 0 (probe0:isp0:0:2:1): . CDB: 1a 0 a 0 14 0 (da0:isp0:0:2:1): inquiry changed (da0:isp0:0:2:1): . CDB: 2a 0 8 9f 6d 25 0 0 4 0 Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 06000000 fault virtual address = 0x60 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01aec1b stack pointer = 0x10:0xf4f41d5c frame pointer = 0x10:0xf4f41d74 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 10750 (IOtest-static) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000002; cpuid = 1; lapic.id = 06000000 boot() called on cpu#1 Boot called at 1133184305 seconds syncing disks... (probe0:isp0:0:2:1): . CDB: 12 1 80 0 ff 0 (probe0:isp0:0:2:1): . CDB: 12 0 0 0 24 0 (probe0:isp0:0:2:1): . CDB: 12 0 0 0 fb 0 (probe0:isp0:0:2:1): . CDB: 1a 0 a 0 14 0 (probe0:isp0:0:2:1): . CDB: 12 1 80 0 ff 0 (probe0:isp0:0:2:1): . CDB: 12 0 0 0 24 0 (probe0:isp0:0:2:1): . CDB: 12 0 0 0 fb 0 (probe0:isp0:0:2:1): . CDB: 1a 0 a 0 14 0 (probe0:isp0:0:2:1): . CDB: 12 1 80 0 ff 0 (probe0:isp0:0:2:1): . CDB: 12 0 0 0 24 0 ------------------------------------------------------------------------------------------ I am confused at why these "inquiry changed" messages are getting logged. This seems to work with SAN boxes other than HP EVA-8k and EVA-6k. Any ideas on why these "inquiry changed" messages are getting created and are they cause of this kernel panic? Thanks, Rajesh