From owner-freebsd-bugs@FreeBSD.ORG Sun Apr 4 23:26:14 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 F292F16A4CE for ; Sun, 4 Apr 2004 23:26:13 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31AAA43D39 for ; Sun, 4 Apr 2004 23:26:11 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i356Q5Xi019779; Mon, 5 Apr 2004 10:26:07 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <006001c41ad6$58f76bb0$0c00a8c0@artem> From: "Artem Koutchine" To: "Vinod Kashyap" References: Date: Mon, 5 Apr 2004 10:22:15 +0400 Organization: IT Legion 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: Mon, 05 Apr 2004 06:26:14 -0000 Hello Vinod and everybody I am not pretty good at reproducing the problem. I THINK (not sure) that it might be related to 3dm software because when i do very fast (i click reload page as fast as i can) MONITOR page reloads in 3dm i will get kernel panic within 1-2 minutes. However, panic happened by itself a couple of time during havy disk load. I did 'tr' while in debugger and wrote down the output on a paper. Belows - is the reproduction of that outout. However, it might contain some typos, because it is very hard to reproduce such info by hand. here is 'tr' output: __panic(c07d482d, 8a, c07d4847,c07b9714,c07d47fe) at __panic+0x13d mtrash_ctor(c7ac9e00,200,0) at mtrash_ctor+0x59 uma_zalloc_arg(c1038e00,0,1) at uma_zalloc_arg+0x169 malloc(200,c0815c20,1,c74da4c0,e5614c60) at malloc+0xb7 twe_get_param(c74be000,200,2,4,0) at twe_get_param+0x3f twe_ioctl(c74be00,800c5469,e5614c60,e5614b70,c05b0a9e) at twe_ioctl+0x25a twe_ioctl_wrapper(c087a1b8,800c5469,e5614c60,3,c78e83f0) at twe_ioctl_wrapper+0x14 spec_ioctl (e5614b88,e5614c34,c063682f,e5614b88,c085dbc0) at spec_ioctl+0x15a spec_vnoperate(e5614b88) at spec_vnoperate+0x13 vn_ioctl(c7900198,800c5469,e5614c60,c3477600,c78e83f0) at vn_ioctl+0x17f ioctl(c78e83f0,e5614d14,3,9d4,297) at ioctl+0x37c syscall(2f,2f,2f,800c5469,200) at syscall+0x217 Xint0x80_syscall() at Xint0x80_syscall+0x1d ---syscall (54,FreeBSD ELF32, ioctl), eip=0x806cae0 esp=0xbfbfdc34 ebp=0xbfbfdc70 I hope this will help figure out what is causing the panic. Regards, Artem > 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