From owner-freebsd-current@FreeBSD.ORG Fri Apr 2 11:07:13 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DA4E16A4CE; Fri, 2 Apr 2004 11:07:13 -0800 (PST) Received: from siamese.3ware.com (siamese.3ware.com [67.122.122.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id C383F43D2F; Fri, 2 Apr 2004 11:07:12 -0800 (PST) (envelope-from vkashyap@3WARE.com) Received: by siamese with Internet Mail Service (5.5.2653.19) id <2DS0AAJN>; Fri, 2 Apr 2004 11:11:04 -0800 Message-ID: From: Vinod Kashyap To: 'Artem Koutchine' , freebsd-current@freebsd.org Date: Fri, 2 Apr 2004 11:10:46 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="koi8-r" cc: freebsd-bugs@freebsd.org Subject: RE: there is a bug in twe driver or disk subsystem for sure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Apr 2004 19:07:13 -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). Every time you try deleting a unit with mounted filesystems, or shutdown the system with mounted filesystems on 3ware units, you will see the message you mention, since the driver tries to delete the unit, but finds it to be busy. Don't let the system panic, and simply shut it down. You should still see the message. -Vinod. -----Original Message----- From: Artem Koutchine [mailto:matrix@itlegion.ru] Sent: Friday, April 02, 2004 9:05 AM To: freebsd-current@freebsd.org Subject: there is a bug in twe driver or disk subsystem for sure I am running 5.2-CURRENT. The box has 3w 8506-4LP SATA raid controller and freebsd is install onto raid5 array. Almost everytime i pull a hotswap disk (one out of four) or when very heavy disk activity (like background fsck after crashing on a 310GB label) i get the following after 10 or so minutes of uptime: 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: the system started to shutdown and here is what i saw: twe0: failed to delete unit 0 stray irq9 The box is: permicro X5DPE-G2 motherboard DUAL XEON 2.66Ghz (HT enabled) 533Mhz bus 2GB RAM 4 SATA SEAGTE 120GB DRIVES 3WARE 8506-4LP SATA RAID5 CONTROLLER _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" DISCLAIMER: The information contained in this electronic mail transmission is intended by 3ware for the use of the named individual or entity to which it is directed and may contain information that is confidential or privileged and should not be disseminated without prior approval from 3ware