From owner-freebsd-current Thu Feb 17 12: 4:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id E68B537B7DC; Thu, 17 Feb 2000 12:04:48 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id PAA39252; Thu, 17 Feb 2000 15:04:47 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000217150221.0161fcb0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 17 Feb 2000 15:02:21 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: MegaRAID 428 vs 466 and a way to wedge the controller Cc: current@freebsd.org In-Reply-To: <200002171959.LAA00438@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:59 AM 2/17/00 -0800, Mike Smith wrote: >> OK, >> I seem to have my 466 (aka Perc 2/SC) working somewhat as expected once I >> flashed to BIOS to the latest rev from AMI. However, I can now more >> reliably wedge the controller where as with the 428 this would only happen >> on occasion. > >When you say "wedge", are you referring to the "controller wedged" >message? If so, can you increase the 10000 on line 1129 of sys/dev/amr/amr.c >to 100000 and try again? I'm fairly sure that this is just my sloppy >programming giving you a bad time; I need a better timeout for this. Actually, in this case, I dont get that message. Just the same 'effect'. iostat shows no activity, although the bonnies are still running, just doing nothing. If there is there some extra information I can provide you with, let me know what you want me to do. STATE and WCHAN show D and getblk iostat -c 100 shows newmail# iostat -c 100 tty amrd0 ad0 fd0 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 10 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 1 0 0 0 99 0 76 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 76 0.00 0 0.00 7.00 2 0.01 0.00 0 0.00 1 0 0 0 99 0 76 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 76 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 even though they are still running. #!/bin/sh /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & is all I did. How long do I have to wait normally for the wedged message to show up ? The last time I saw it was with the 428, but I seem to recall the message showing up fairly quickly e.g. Feb 11 02:02:57 newmail /kernel: amr0: controller wedged (not taking commands) Feb 11 02:02:57 newmail /kernel: amr0: I/O error - dead Feb 11 02:02:57 newmail /kernel: amr0: cmd 2 ident 3 drive 0 Feb 11 02:02:57 newmail /kernel: amr0: blkcount 16 lba 16580735 Feb 11 02:02:57 newmail /kernel: amr0: virtaddr 0xc9a02000 length 8192 Feb 11 02:02:57 newmail /kernel: amr0: physaddr 00001100 nsg 2 Feb 11 02:02:57 newmail /kernel: amr0: 26da000/4096 Feb 11 02:02:57 newmail /kernel: amr0: 55db000/4096 ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message