From owner-freebsd-bugs@FreeBSD.ORG Sat Apr 3 01:09:05 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E87BA16A4CF; Sat, 3 Apr 2004 01:09:05 -0800 (PST) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41B7F43D2F; Sat, 3 Apr 2004 01:09:05 -0800 (PST) (envelope-from matrix@itlegion.ru) Received: from WINXP ([212.248.52.91]) by osiris.ipform.ru (8.12.6/8.12.6) with SMTP id i3395LXg007900; Sat, 3 Apr 2004 13:06:14 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <00c401c4195b$53c2cc10$0105a8c0@WINXP> From: "Artem Koutchine" To: "Vinod Kashyap" , References: Date: Sat, 3 Apr 2004 13:05:08 +0400 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-bugs@freebsd.org Subject: Re: there is a bug in twe driver or disk subsystem for sure X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Apr 2004 09:09:06 -0000 > The 3ware (twe) driver is obviously not causing this panic. > It's something else (at line 128 in file /usr/src/sys/udm_dbg.c). I do not insist on driver causing the panic. I may or maynot be related to twe driver but it seems like it is related to the disk io subsystem (which includes the driver, kernel stuff and the hardware and maybe something else). It think so because it happens ONLY when some heavy disk usage is happenning or when hot swap disk is pull out of the bay. The box has ONLY hotswap disk and all of them connected to 8506-4LP in hot swap bays. FreeBSD is installed on that array (is is RAID 5). I unsterstand that error message related to ot being able to delete a busy unit is okay. However nobody explained why 'stray irq9'. Anyhow, that is no the main problem. IT is not a problem at all because it happenes only when i shutdown the system and i do not want it be shutdown ever :) It is supposed to be run forever and ever. Which i cannot get from it yet. Currently I am running GENERIC kernel. If DIAGNOSTIC is ON there then i have it ON. Otherweise it is off and i will try truning it on on monday. I will gladly send you the mentioned stack trace if you explain to me what i must do in the debugger to obtain it. I am not good at the kernel debugger. I know C and for the last 5 years i am mostly perl programmer. :) And what is this udm_dbg.c file? Is it really related to the problem? What is it for? What is UDM anyway? And why udm_dbg.c and not just udm.c ? Is it this a debug version? I just want to know. Best regards and i hope we all will figure this problem out and make FreeBSD 5.2 STABLE :) > Memory modified after free 0x788f400(508) val=20202020 @ 0xe788f400 > panic: Most recently used by devbuf > at line 128 in file /usr/src/sys/udm_dbg.c > cpu=0; > Debugger ("panic") > Stopped at Debugger +0.46: xchgl %ebx, in_Debugger.0 > and i typed 'c' in debugger: