From owner-freebsd-hardware@FreeBSD.ORG Sun Nov 11 13:01:28 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2943016A419 for ; Sun, 11 Nov 2007 13:01:28 +0000 (UTC) (envelope-from james@mansionfamily.plus.com) Received: from pih-relay08.plus.net (pih-relay08.plus.net [212.159.14.134]) by mx1.freebsd.org (Postfix) with ESMTP id E65F713C4B6 for ; Sun, 11 Nov 2007 13:01:27 +0000 (UTC) (envelope-from james@mansionfamily.plus.com) Received: from [80.229.150.39] (helo=mansionfamily.plus.com) by pih-relay08.plus.net with esmtp (Exim) id 1IrC6t-0004vn-IE for freebsd-hardware@freebsd.org; Sun, 11 Nov 2007 12:40:19 +0000 Received: from [192.168.0.120] ([192.168.0.120]:1956) by mansionfamily.plus.com with [XMail 1.22 ESMTP Server] id for from ; Sun, 11 Nov 2007 12:44:50 -0000 Message-ID: <4736F88D.1020701@mansionfamily.plus.com> Date: Sun, 11 Nov 2007 12:41:49 +0000 From: James Mansion User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-embedded@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: eWay 2300 CF boot problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Nov 2007 13:01:28 -0000 Hi, I'm trying to get 6.2R to install onto an eWay 2300 (a little system using a Vortex86 CPU, also available from Norhtec and a few other places as a thin client or PuppyLinux system). It has a number of oddities it seems. I'm trying to use a compact flash. I have a bootable CF, and I managed to get an installation of NetBSD 3.0 to run fine. With FreeBSD, I run the installation under VMWare and set up the CF. The CF will boot in VMWare. The process I used is essentially that from http://typosubmonkey.net/articles/2006/04/13/installing-freebsd-on-usb-stick-episode-2. However, I specify the root directly, not trying to use the ufs label. (Well, I tried with the label too but couldn't get that to wor) The drive is different for me since I have it in a CF-to-IDE adapter. Anyway, all seems to go well with the F1 prompt for the bootable IDE drive, then the kernel loads quite happily, loads the acpi module etc and all is well until it wants to mount the root file system. At that point, it fails after: Trying to mount root from ufs:/dev/ad0s1a. IThe weird thing is that if I type '?' then the 'List of GEOM managed disk devices:' is empty (or shows cd0 if I have the USB CD plugged in). Its clearly come up from the CF disk, but it doesn't seem to recognise that there is anything attaached to ata0 or ata1. The hardware quirk is that the CF is the secondary on the first channel. Is it possible to convince it to probe the secondary? Installation also fails if I try to use a USB stick, claiming there is no kernel. If I press '?' it lists the directories OK. This may be down to a furter quirk - it shows USB sticks as USB floppy devices. A standard Ubuntu install goes OK (but slowly) and on reboot halts after showing 'GRUB '. To get it running with PuppyLinux its necessary to use a 'superfloppy' installation with no pertitions. I have yet to try a siilar FreeBSD installation by installing directly to sd0 (ie dd over the drive and disklabel sd0 rather than fdisk and disklabel in sd0s1). Is that likely to work? I'd rather get running from the CF. And I'd rather use FreeBSD than NetBSD since the readonly root support is handy and the Java support seems to be better, Any ideas? Thanks! James From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 12 19:34:28 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B81D216A469; Mon, 12 Nov 2007 19:34:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 18D3C13C4BA; Mon, 12 Nov 2007 19:34:22 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 218938194-1834499 for multiple; Mon, 12 Nov 2007 13:53:08 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lACIqII8042270; Mon, 12 Nov 2007 13:52:19 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hardware@freebsd.org Date: Mon, 12 Nov 2007 13:51:57 -0500 User-Agent: KMail/1.9.6 References: <4A5A9C78-22AC-4480-BDEB-A72F6CF472DB@fnop.net> <473232A8.3080105@samsco.org> <5A4AF64C-D70A-4303-8116-D13718EE8BCC@FreeBSD.org> In-Reply-To: <5A4AF64C-D70A-4303-8116-D13718EE8BCC@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711121351.58616.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 12 Nov 2007 13:52:20 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/4756/Mon Nov 12 10:28:55 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Maxim Sobolev , Scott Long , Rink Springer , Rui Paulo , freebsd-current@freebsd.org, freebsd-i386@freebsd.org Subject: Re: MacBook users: possible fix for the SMP problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2007 19:34:28 -0000 On Friday 09 November 2007 06:40:48 am Rui Paulo wrote: > On 7 Nov 2007, at 21:48, Scott Long wrote: > > > Rui Paulo wrote: > >> On Nov 7, 2007 7:50 PM, Maxim Sobolev wrote: > >>> I don't really like the fact that it has to be turned on manually. > >>> Is it > >>> possible to make this automatic based on BIOS Id or something like > >>> this? > >> Yes, I can turn this on for MacBooks. > > > > Yeah, at least have it on by default for the systems that we know have > > the problem. I still think that it needs wider application, but as > > long > > as the immediate and identifiable issue is addressed, I'm happy. > > > Ok, if there are no objections, I plan to request approval from my > mentor and from re@ for the following patch: > > Index: clock.c > =================================================================== > RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v > retrieving revision 1.240 > diff -u -p -r1.240 clock.c > --- clock.c 26 Oct 2007 03:23:54 -0000 1.240 > +++ clock.c 9 Nov 2007 11:34:56 -0000 > @@ -130,6 +130,9 @@ static u_char rtc_statusb = RTCSB_24HR; > #define ACQUIRED 2 > #define ACQUIRE_PENDING 3 > > +/* Intel ICH register */ > +#define ICH_PMBASE 0x400 > + > static u_char timer2_state; > > static unsigned i8254_get_timecount(struct timecounter *tc); > @@ -616,11 +619,31 @@ i8254_init(void) > void > startrtclock() > { > + char *ichenv, *sysenv; > u_int delta, freq; > > writertc(RTC_STATUSA, rtc_statusa); > writertc(RTC_STATUSB, RTCSB_24HR); > > + /* > + * On some systems, namely MacBooks, we need to disallow the > + * legacy USB circuit to generate an SMI# because this can > + * cause several problems, namely: incorrect CPU frequency > + * detection and failure to start the APs. > + */ > + ichenv = getenv("hw.ich.disable_legacy_usb"); > + sysenv = getenv("smbios.system.product"); > + if ((ichenv != NULL) || (sysenv != NULL && > + strncmp(sysenv, "MacBook", 7) == 0)) { > + if (bootverbose) > + printf("Disabling LEGACY_USB_EN bit on Intel ICH.\n"); > + outl(ICH_PMBASE + 0x30, inl(ICH_PMBASE + 0x30) & ~0x8); > + if (ichenv) > + freeenv(ichenv); > + if (sysenv) > + freeenv(sysenv); > + } > + This is missing a freeenv(sysenv) in the case that ichenv is NULL and sysenv != "MacBook". Perhaps move the freeenv()'s out of the if statement. -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 12 20:19:34 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE2B516A419 for ; Mon, 12 Nov 2007 20:19:33 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 899DD13C4CA for ; Mon, 12 Nov 2007 20:19:33 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so1547818pyb for ; Mon, 12 Nov 2007 12:19:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=cwtkvAa3KRugUle3sikVwZvRfYEcse0jYQVYlnFFvNU=; b=FCDkrRgsTOA2G1X+n7CMyKRIV8XlB9xc5sOoH0eOoUG6A8gE5atMEIqSIKj02/N1KbPagp2wt39ZWscM82DBS9Vb4RBrdKe8jHf5hJs5JrvvKniTitHjgk+k8J52zzYBMu9CAYycpm4gqgPUrzspvI/PiHBlkaO5TAFTGIGLxZY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=dX5PQ8jR35Eixk/uS6MTZZGeTIKpVPnm9W3f9x9zb8i7ekf++DBZsUjGzs7CT6RaZPbrBnxcNtJ1j9bUPLI5urSgi0eV4tIvqEssT3Z3ZTZo4oMxPTPowtCPbQuw/ByXu7J9jDt9N65MuyLHTtPOJS+6IiB5nhmfalzi4WCP0mY= Received: by 10.35.78.9 with SMTP id f9mr2701326pyl.1194898763111; Mon, 12 Nov 2007 12:19:23 -0800 (PST) Received: by 10.35.76.2 with HTTP; Mon, 12 Nov 2007 12:19:23 -0800 (PST) Message-ID: Date: Mon, 12 Nov 2007 20:19:23 +0000 From: "Rui Paulo" Sender: rpaulo@gmail.com To: "John Baldwin" In-Reply-To: <200711121351.58616.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4A5A9C78-22AC-4480-BDEB-A72F6CF472DB@fnop.net> <473232A8.3080105@samsco.org> <5A4AF64C-D70A-4303-8116-D13718EE8BCC@FreeBSD.org> <200711121351.58616.jhb@freebsd.org> X-Google-Sender-Auth: fb8e40cb068bdcdc Cc: freebsd-current@freebsd.org, freebsd-i386@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: MacBook users: possible fix for the SMP problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2007 20:19:34 -0000 On Nov 12, 2007 6:51 PM, John Baldwin wrote: > > On Friday 09 November 2007 06:40:48 am Rui Paulo wrote: > > On 7 Nov 2007, at 21:48, Scott Long wrote: > > > > > Rui Paulo wrote: > > >> On Nov 7, 2007 7:50 PM, Maxim Sobolev wrote: > > >>> I don't really like the fact that it has to be turned on manually. > > >>> Is it > > >>> possible to make this automatic based on BIOS Id or something like > > >>> this? > > >> Yes, I can turn this on for MacBooks. > > > > > > Yeah, at least have it on by default for the systems that we know have > > > the problem. I still think that it needs wider application, but as > > > long > > > as the immediate and identifiable issue is addressed, I'm happy. > > > > > > Ok, if there are no objections, I plan to request approval from my > > mentor and from re@ for the following patch: > > > > Index: clock.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v > > retrieving revision 1.240 > > diff -u -p -r1.240 clock.c > > --- clock.c 26 Oct 2007 03:23:54 -0000 1.240 > > +++ clock.c 9 Nov 2007 11:34:56 -0000 > > @@ -130,6 +130,9 @@ static u_char rtc_statusb = RTCSB_24HR; > > #define ACQUIRED 2 > > #define ACQUIRE_PENDING 3 > > > > +/* Intel ICH register */ > > +#define ICH_PMBASE 0x400 > > + > > static u_char timer2_state; > > > > static unsigned i8254_get_timecount(struct timecounter *tc); > > @@ -616,11 +619,31 @@ i8254_init(void) > > void > > startrtclock() > > { > > + char *ichenv, *sysenv; > > u_int delta, freq; > > > > writertc(RTC_STATUSA, rtc_statusa); > > writertc(RTC_STATUSB, RTCSB_24HR); > > > > + /* > > + * On some systems, namely MacBooks, we need to disallow the > > + * legacy USB circuit to generate an SMI# because this can > > + * cause several problems, namely: incorrect CPU frequency > > + * detection and failure to start the APs. > > + */ > > + ichenv = getenv("hw.ich.disable_legacy_usb"); > > + sysenv = getenv("smbios.system.product"); > > + if ((ichenv != NULL) || (sysenv != NULL && > > + strncmp(sysenv, "MacBook", 7) == 0)) { > > + if (bootverbose) > > + printf("Disabling LEGACY_USB_EN bit on Intel ICH.\n"); > > + outl(ICH_PMBASE + 0x30, inl(ICH_PMBASE + 0x30) & ~0x8); > > + if (ichenv) > > + freeenv(ichenv); > > + if (sysenv) > > + freeenv(sysenv); > > + } > > + > > This is missing a freeenv(sysenv) in the case that ichenv is NULL and > sysenv != "MacBook". Perhaps move the freeenv()'s out of the if statement. Yeah, Nate already pointed that out. Could you check your inbox, please? Nate asked you if this was the proper place to add this code. Regards. -- Rui Paulo From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 12 21:20:55 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 232A716A46B; Mon, 12 Nov 2007 21:20:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.freebsd.org (Postfix) with ESMTP id 85FD313C4E5; Mon, 12 Nov 2007 21:20:53 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.8p) with ESMTP id 218966963-1834499 for multiple; Mon, 12 Nov 2007 16:21:14 -0500 Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id lACLKQj9043273; Mon, 12 Nov 2007 16:20:26 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Rui Paulo" Date: Mon, 12 Nov 2007 16:11:36 -0500 User-Agent: KMail/1.9.6 References: <4A5A9C78-22AC-4480-BDEB-A72F6CF472DB@fnop.net> <200711121351.58616.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711121611.37781.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Mon, 12 Nov 2007 16:20:26 -0500 (EST) X-Virus-Scanned: ClamAV 0.91.2/4757/Mon Nov 12 12:20:27 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: freebsd-current@freebsd.org, freebsd-i386@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: MacBook users: possible fix for the SMP problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Nov 2007 21:20:55 -0000 On Monday 12 November 2007 03:19:23 pm Rui Paulo wrote: > On Nov 12, 2007 6:51 PM, John Baldwin wrote: > > > > On Friday 09 November 2007 06:40:48 am Rui Paulo wrote: > > > On 7 Nov 2007, at 21:48, Scott Long wrote: > > > > > > > Rui Paulo wrote: > > > >> On Nov 7, 2007 7:50 PM, Maxim Sobolev wrote: > > > >>> I don't really like the fact that it has to be turned on manually. > > > >>> Is it > > > >>> possible to make this automatic based on BIOS Id or something like > > > >>> this? > > > >> Yes, I can turn this on for MacBooks. > > > > > > > > Yeah, at least have it on by default for the systems that we know have > > > > the problem. I still think that it needs wider application, but as > > > > long > > > > as the immediate and identifiable issue is addressed, I'm happy. > > > > > > > > > Ok, if there are no objections, I plan to request approval from my > > > mentor and from re@ for the following patch: > > > > > > Index: clock.c > > > =================================================================== > > > RCS file: /home/ncvs/src/sys/i386/isa/clock.c,v > > > retrieving revision 1.240 > > > diff -u -p -r1.240 clock.c > > > --- clock.c 26 Oct 2007 03:23:54 -0000 1.240 > > > +++ clock.c 9 Nov 2007 11:34:56 -0000 > > > @@ -130,6 +130,9 @@ static u_char rtc_statusb = RTCSB_24HR; > > > #define ACQUIRED 2 > > > #define ACQUIRE_PENDING 3 > > > > > > +/* Intel ICH register */ > > > +#define ICH_PMBASE 0x400 > > > + > > > static u_char timer2_state; > > > > > > static unsigned i8254_get_timecount(struct timecounter *tc); > > > @@ -616,11 +619,31 @@ i8254_init(void) > > > void > > > startrtclock() > > > { > > > + char *ichenv, *sysenv; > > > u_int delta, freq; > > > > > > writertc(RTC_STATUSA, rtc_statusa); > > > writertc(RTC_STATUSB, RTCSB_24HR); > > > > > > + /* > > > + * On some systems, namely MacBooks, we need to disallow the > > > + * legacy USB circuit to generate an SMI# because this can > > > + * cause several problems, namely: incorrect CPU frequency > > > + * detection and failure to start the APs. > > > + */ > > > + ichenv = getenv("hw.ich.disable_legacy_usb"); > > > + sysenv = getenv("smbios.system.product"); > > > + if ((ichenv != NULL) || (sysenv != NULL && > > > + strncmp(sysenv, "MacBook", 7) == 0)) { > > > + if (bootverbose) > > > + printf("Disabling LEGACY_USB_EN bit on Intel ICH. \n"); > > > + outl(ICH_PMBASE + 0x30, inl(ICH_PMBASE + 0x30) & ~0x8); > > > + if (ichenv) > > > + freeenv(ichenv); > > > + if (sysenv) > > > + freeenv(sysenv); > > > + } > > > + > > > > This is missing a freeenv(sysenv) in the case that ichenv is NULL and > > sysenv != "MacBook". Perhaps move the freeenv()'s out of the if statement. > > Yeah, Nate already pointed that out. Could you check your inbox, > please? Nate asked you if this was the proper place to add this code. I'm not sure where exactly one would add it, but I don't think the RTC clock routine is the right place. Maybe do it at the start of cpu_startup() in machdep.c instead? -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 00:56:14 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6891A16A473 for ; Tue, 13 Nov 2007 00:56:14 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 1DAEB13C4BC for ; Tue, 13 Nov 2007 00:56:13 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Irk3r-0002VW-0R for freebsd-hardware@freebsd.org; Tue, 13 Nov 2007 00:55:27 +0000 Received: from brist1-dhcp-137.greenmountainaccess.net ([69.54.15.137]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Nov 2007 00:55:27 +0000 Received: from scott by brist1-dhcp-137.greenmountainaccess.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Nov 2007 00:55:27 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: "Scott I. Remick" Date: Tue, 13 Nov 2007 00:55:08 +0000 (UTC) Lines: 15 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: brist1-dhcp-137.greenmountainaccess.net X-Archive: encrypt User-Agent: Pan/0.132 (Waxed in Black) Sender: news Subject: Re: acd0: FAILURE - READ_BIG timed out X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 00:56:14 -0000 On Fri, 02 Nov 2007 13:57:42 -0500, Sean Farley wrote: > > I noticed the same issue with two different SATA drives (LITE-ON > LH-20A1S and HL-DT-ST GCC-H10N (in a Dell)). Ok, so I'm not alone and am not an isolated case. This is a problem other people are experiencing. Does anyone have any ideas what's going on, or a suggestion for a fix? I put in a PR already but nothing has been commented on it and it could be months/years before it catches someone's eye on there. I've now purchased 2 CDRW/DVD drives, neither work. If I have to buy a 3rd one, I'd like some sort of assurances as to what to buy that would work. Preferably SATA but I'll settle for PATA if I have to, but I don't want to have to buy a 4th. From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 00:58:08 2007 Return-Path: Delivered-To: hardware@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1308916A419 for ; Tue, 13 Nov 2007 00:58:08 +0000 (UTC) (envelope-from www-data@web-client.czechbone.net) Received: from web-client.czechbone.net (web-client.czechbone.net [212.96.160.137]) by mx1.freebsd.org (Postfix) with ESMTP id D087413C4BE for ; Tue, 13 Nov 2007 00:58:07 +0000 (UTC) (envelope-from www-data@web-client.czechbone.net) Received: from www-data by web-client.czechbone.net with local (Exim 4.50) id 1Irgs6-0005pU-KQ for hardware@FreeBSD.ORG; Mon, 12 Nov 2007 22:31:06 +0100 To: hardware@FreeBSD.ORG From: Mrs. Stella Alice MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Message-Id: Date: Mon, 12 Nov 2007 22:31:06 +0100 Cc: Subject: Online Promo Programme X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: billywatt01@yahoo.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 00:58:08 -0000 This is to inform you that you have been selected for a cash prize of £1,500,000 (One Million Five Hundred Thousand Pounds Sterling ) held on the 10th of November 2007 in London UK.The selection process was carried out through random selection in our computerized email selection system(ess) from a database of over 250,000 email addresses drawn from which you were selected. To file for your claim, please contact our fiduciary agent by E-mail:billywatt01@yahoo.com Mr.Bills Watt. Phone Number:+44 704 5708 897 With the feed Verification/Fund Release Form Below. 1.Full Name: 2.Full Address: 3.Marital Status: 4.Occupation: 5.Age: 6.Sex: 7.Nationality: 8.Country Of Residence: 9.Telephone Number: Yours Truly, Mrs. Stella Alice. Co-ordinator(Online Promo Programme) From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 03:03:41 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DCFA16A417 for ; Tue, 13 Nov 2007 03:03:41 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.179]) by mx1.freebsd.org (Postfix) with ESMTP id F009A13C48E for ; Tue, 13 Nov 2007 03:03:40 +0000 (UTC) (envelope-from bahamasfranks@gmail.com) Received: by wa-out-1112.google.com with SMTP id k17so1898148waf for ; Mon, 12 Nov 2007 19:03:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=SsrL+OEll6pEoIPAKhGltYVDfJdTzqWG5rvDdRhuzy0=; b=TQ1Gp3UP7VDMoYINuOPD6wHyVRR35D15PX0RflMq71n3AgRxPbtIc7lMNUXJEryPu0i8UuHwujL6qNxHWHQRLpEDnbS44oxDd4rKy/Y/0rkUP6laU8NKoe2/rpcz4r6aERXCJJ/V8xgDCYCz4dsrbDY+0/f+f31f5b/KabtT8+w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:reply-to:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=al537aYVZfc9VlreWuEqEX3NyKINKQzLUmgGGnb0X2pGCDhAI+TvfzdeiosZwN0qlE7YHkTSIUwDxXEkiaBq1VfnV7o/kkQyiasS5gv0z+5MwA3teLFh8+6fMNduyxBK/0WRHFLUKt5dvoaVyarJn2n7yvSUJ6OD5tE2Qc8dvHI= Received: by 10.114.169.2 with SMTP id r2mr871821wae.1194921479367; Mon, 12 Nov 2007 18:37:59 -0800 (PST) Received: by 10.114.209.8 with HTTP; Mon, 12 Nov 2007 18:37:59 -0800 (PST) Message-ID: <539c60b90711121837k3f37cebcm5dae75d04acb13c1@mail.gmail.com> Date: Mon, 12 Nov 2007 19:37:59 -0700 From: "Steve Franks" Sender: bahamasfranks@gmail.com To: "Scott I. Remick" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: 99de016a61368638 Cc: freebsd-hardware@freebsd.org Subject: Re: acd0: FAILURE - READ_BIG timed out X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: stevefranks@ieee.org List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 03:03:41 -0000 I'm sure it doesn't help, but I've got a system with a cd-r drive that's on it's way to dead (but not quite there), and I get the exact same errors. I've also had it on bad harddisks...must be a pretty non-specific error. Steve On Nov 12, 2007 5:55 PM, Scott I. Remick wrote: > On Fri, 02 Nov 2007 13:57:42 -0500, Sean Farley wrote: > > > > I noticed the same issue with two different SATA drives (LITE-ON > > LH-20A1S and HL-DT-ST GCC-H10N (in a Dell)). > > Ok, so I'm not alone and am not an isolated case. This is a problem other > people are experiencing. Does anyone have any ideas what's going on, or a > suggestion for a fix? I put in a PR already but nothing has been > commented on it and it could be months/years before it catches someone's > eye on there. > > I've now purchased 2 CDRW/DVD drives, neither work. If I have to buy a > 3rd one, I'd like some sort of assurances as to what to buy that would > work. Preferably SATA but I'll settle for PATA if I have to, but I don't > want to have to buy a 4th. > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" > -- Steve Franks, KE7BTE Staff Engineer La Palma Devices, LLC http://www.lapalmadevices.com (520) 312-0089 From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 03:15:23 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A79DE16A418 for ; Tue, 13 Nov 2007 03:15:23 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 38B0B13C4C6 for ; Tue, 13 Nov 2007 03:15:22 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1169855nfb for ; Mon, 12 Nov 2007 19:15:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; bh=ZR7aGGxSMfviJ0oY6vomLY494KqetFQHVsoV2MGfLRQ=; b=Pad1X3qPnvYZxLZ3xUswSBbgkUOWI85BpxwvvFwmIRQ6vloiOvqbS51jqgkpZXycFIB2y3efy0um4clYzJ4DB2NnXLjmK1x7lQTq9UFcPg7q7v/UZy4lIJ77DGmqKU29Mixnt9gvDN5Z2p0VsjdI+NVKnPVio7PlbNsWGOfreEo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=qUfi3Z2xw7dJ62fhA1FvUZmxi6tOJ8U0zUYkigV9BH/BnvtL1sqWj4vW3RLMZXPImOpBmm8rg08n3weDZGs7Di3DSRi6bE+8DLn3Vj/dA+8BBcfqY2Igk4/s4Ag/ktLs10iKZWCaVnow2PfFmUTLuu27ifA9UgDoYOsBHtIN8iU= Received: by 10.70.72.11 with SMTP id u11mr455746wxa.1194923710039; Mon, 12 Nov 2007 19:15:10 -0800 (PST) Received: from ?192.168.2.2? ( [67.85.89.184]) by mx.google.com with ESMTPS id s30sm5582188elf.2007.11.12.19.15.08 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 12 Nov 2007 19:15:08 -0800 (PST) Message-ID: <473916B7.1050905@gmail.com> Date: Mon, 12 Nov 2007 22:15:03 -0500 From: "Aryeh M. Friedman" User-Agent: Thunderbird 2.0.0.6 (X11/20071111) MIME-Version: 1.0 To: stevefranks@ieee.org References: <539c60b90711121837k3f37cebcm5dae75d04acb13c1@mail.gmail.com> In-Reply-To: <539c60b90711121837k3f37cebcm5dae75d04acb13c1@mail.gmail.com> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Scott I. Remick" , freebsd-hardware@freebsd.org Subject: Re: acd0: FAILURE - READ_BIG timed out X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 03:15:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Steve Franks wrote: > I'm sure it doesn't help, but I've got a system with a cd-r drive > that's on it's way to dead (but not quite there), and I get the > exact same errors. I've also had it on bad harddisks...must be a > pretty non-specific error. This is a SATA issue... one of the developers involved in fixing this just sent me a "known" to work drive to see if we can narrow the problem some more. - -- Aryeh M. Friedman Developer, not business, friendly http://www.flosoft-systems.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHORa3J9+1V27SttsRAufGAJ9rDDumwrqHze3EQrTF63ZMrcNtLgCfXfZH TX9sWGcHV6QvQQ5I9k9ktzc= =e3hT -----END PGP SIGNATURE----- From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 03:18:40 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4EEE716A417 for ; Tue, 13 Nov 2007 03:18:40 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 0B0D913C4A5 for ; Tue, 13 Nov 2007 03:18:39 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IrmIA-0000MN-Ja for freebsd-hardware@freebsd.org; Tue, 13 Nov 2007 03:18:22 +0000 Received: from brist1-dhcp-137.greenmountainaccess.net ([69.54.15.137]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Nov 2007 03:18:22 +0000 Received: from scott by brist1-dhcp-137.greenmountainaccess.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 13 Nov 2007 03:18:22 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: "Scott I. Remick" Date: Tue, 13 Nov 2007 03:18:17 +0000 (UTC) Lines: 7 Message-ID: References: <539c60b90711121837k3f37cebcm5dae75d04acb13c1@mail.gmail.com> <473916B7.1050905@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: brist1-dhcp-137.greenmountainaccess.net X-Archive: encrypt User-Agent: Pan/0.132 (Waxed in Black) Sender: news Subject: Re: acd0: FAILURE - READ_BIG timed out X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 03:18:40 -0000 On Mon, 12 Nov 2007 22:15:03 -0500, Aryeh M. Friedman wrote: > > This is a SATA issue... one of the developers involved in fixing this > just sent me a "known" to work drive to see if we can narrow the problem > some more. Except I have a PATA drive right now doing the exact same thing. From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 11:59:07 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 040B816A419 for ; Tue, 13 Nov 2007 11:59:07 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id AA3CD13C4B0 for ; Tue, 13 Nov 2007 11:59:06 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from [192.18.98.63] (brmea-proxy-2.Sun.COM [192.18.98.63]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTP id 42B8F13DFE9 for ; Tue, 13 Nov 2007 14:44:45 +0300 (MSK) Message-ID: <47398DB8.1050105@FreeBSD.org> Date: Tue, 13 Nov 2007 14:42:48 +0300 From: Lev Serebryakov Organization: FreeBSD Project User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.13) Gecko/20070809 Thunderbird/1.5.0.13 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: Is Adaptec RAID 1430SA supported by FreeBSD? Or suggest another 4xSATA-II PCI-E controller, please X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 11:59:07 -0000 Is Adaptec RAID 1430SA supported by FreeBSD? I can not find mentions about it in HARDWARE.TXT or man pages (aac(4)). If it is not supported, please, suggest me simple and not expensive PCE-E SATA-II controller for 4 or more (6, 8) ports. As far as I know, SiliconImage controllers is total crap, and Areca/3Ware is too expensive for me (and my tasks). I don't need RAID functionality. -- // Lev Serebryakov From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 12:09:00 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CB0916A469 for ; Tue, 13 Nov 2007 12:09:00 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from ftp.translate.ru (ftp.translate.ru [195.131.4.140]) by mx1.freebsd.org (Postfix) with ESMTP id 080E013C4B0 for ; Tue, 13 Nov 2007 12:08:59 +0000 (UTC) (envelope-from lev@serebryakov.spb.ru) Received: from [192.18.98.63] (brmea-proxy-2.Sun.COM [192.18.98.63]) (Authenticated sender: lev@serebryakov.spb.ru) by ftp.translate.ru (Postfix) with ESMTP id C45EA13DF94 for ; Tue, 13 Nov 2007 14:52:27 +0300 (MSK) Message-ID: <47398F86.3090304@serebryakov.spb.ru> Date: Tue, 13 Nov 2007 14:50:30 +0300 From: "Lev A. Serebryakov" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.13) Gecko/20070809 Thunderbird/1.5.0.13 Mnenhy/0.7.4.0 MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 13 Nov 2007 12:30:14 +0000 Subject: Is Adaptec RAID 1430SA supported by FreeBSD? Or suggest another 4xSATA-II PCI-E controller, please X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 12:09:00 -0000 Is Adaptec RAID 1430SA supported by FreeBSD? I can not find mentions about it in HARDWARE.TXT or man pages (aac(4)). If it is not supported, please, suggest me simple and not expensive PCE-E SATA-II controller for 4 or more (6, 8) ports. As far as I know, SiliconImage controllers is total crap, and Areca/3Ware is too expensive for me (and my tasks). I don't need RAID functionality. -- // Lev Serebryakov From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 18:01:58 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DB2C16A468 for ; Tue, 13 Nov 2007 18:01:58 +0000 (UTC) (envelope-from freebsd@akruijff.dds.nl) Received: from hpsmtp-eml18.kpnxchange.com (hpsmtp-eml18.KPNXCHANGE.COM [213.75.38.118]) by mx1.freebsd.org (Postfix) with ESMTP id 4D5EF13C4A5 for ; Tue, 13 Nov 2007 18:01:56 +0000 (UTC) (envelope-from freebsd@akruijff.dds.nl) Received: from cpsmtp-eml108.kpnxchange.com ([213.75.84.108]) by hpsmtp-eml18.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 18:49:15 +0100 Received: from ip51cc8423.speed.planet.nl ([81.204.132.35]) by cpsmtp-eml108.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 18:49:15 +0100 Received: from Alex1.kruijff.org (localhost [127.0.0.1]) by ip51cc8423.speed.planet.nl (8.13.8/8.13.8) with ESMTP id lADHnErE002428; Tue, 13 Nov 2007 18:49:14 +0100 (CET) (envelope-from freebsd@akruijff.dds.nl) Received: (from akruijff@localhost) by Alex1.kruijff.org (8.13.8/8.13.8/Submit) id lADHnEj1002427; Tue, 13 Nov 2007 18:49:14 +0100 (CET) (envelope-from freebsd@akruijff.dds.nl) X-Authentication-Warning: Alex1.kruijff.org: akruijff set sender to freebsd@akruijff.dds.nl using -f Date: Tue, 13 Nov 2007 18:49:14 +0100 From: Alex de Kruijff To: FreeBSD Daemon Message-ID: <20071113174914.GA1188@Alex1.kruijff.org> References: <4725AAF2.10405@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4725AAF2.10405@gmx.net> User-Agent: Mutt/1.4.2.3i X-OriginalArrivalTime: 13 Nov 2007 17:49:15.0480 (UTC) FILETIME=[81DE5D80:01C8261D] Cc: "freebsd-hardware@freebsd.org" Subject: Re: 3ware 9550XU-4LP X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@akruijff.dds.nl List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 18:01:58 -0000 On Mon, Oct 29, 2007 at 05:42:10PM +0800, FreeBSD Daemon wrote: > dear list, > > i the 3ware 9550SXU-4LP controller supported in 6.2R? > > tia > > zheyu > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" You can also try to download a kernel module or sources from the site. I have the 9650 and have a special kernel module for 6.1. -- Alex Please copy the original recipients, otherwise I may not read your reply. Howtos based on my personal use, including information about setting up a firewall and creating traffic graphs with MRTG http://alex.kruijff.org/FreeBSD/ From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 18:10:40 2007 Return-Path: Delivered-To: hardware@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5E4516A41B for ; Tue, 13 Nov 2007 18:10:40 +0000 (UTC) (envelope-from freebsd@akruijff.dds.nl) Received: from hpsmtp-eml11.kpnxchange.com (hpsmtp-eml11.kpnxchange.com [213.75.38.111]) by mx1.freebsd.org (Postfix) with ESMTP id 3D36D13C4C4 for ; Tue, 13 Nov 2007 18:10:39 +0000 (UTC) (envelope-from freebsd@akruijff.dds.nl) Received: from cpsmtp-eml109.kpnxchange.com ([213.75.84.109]) by hpsmtp-eml11.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 18:58:06 +0100 Received: from ip51cc8423.speed.planet.nl ([81.204.132.35]) by cpsmtp-eml109.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Nov 2007 18:58:05 +0100 Received: from Alex1.kruijff.org (localhost [127.0.0.1]) by ip51cc8423.speed.planet.nl (8.13.8/8.13.8) with ESMTP id lADHw4b4002458 for ; Tue, 13 Nov 2007 18:58:04 +0100 (CET) (envelope-from freebsd@akruijff.dds.nl) Received: (from akruijff@localhost) by Alex1.kruijff.org (8.13.8/8.13.8/Submit) id lADHw4ei002457 for hardware@FreeBSD.ORG; Tue, 13 Nov 2007 18:58:04 +0100 (CET) (envelope-from freebsd@akruijff.dds.nl) X-Authentication-Warning: Alex1.kruijff.org: akruijff set sender to freebsd@akruijff.dds.nl using -f Date: Tue, 13 Nov 2007 18:58:04 +0100 From: Alex de Kruijff To: hardware@FreeBSD.ORG Message-ID: <20071113175804.GB1188@Alex1.kruijff.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-OriginalArrivalTime: 13 Nov 2007 17:58:05.0633 (UTC) FILETIME=[BDDD4B10:01C8261E] Cc: Subject: Kernel modules for 6.1 not build? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@akruijff.dds.nl List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 18:10:40 -0000 Hi, I have downloaded the latest sources for 6.1. and found that lots of kernel modules are missing. I am worried about this and I do not dare to install this (I installed a test kernel first), but am clueless. Can anyone give me any pointers? I have used the same kernel config file. M edited kernel config file as GENERIC give the same 'problem'. #ls *.ko | wc (kernel with outdated 6.1 sources) 449 449 5187 #ls *.ko (kernel with latest 6.1 sources) acpi.ko* acpi_ibm.ko* acpi_toshiba.ko* ntfs.ko* acpi_asus.ko* acpi_panasonic.ko* acpi_video.ko* snd_ds1.ko* acpi_fujitsu.ko* acpi_sony.ko* linux.ko* sound.ko* I downloaded twa.ko from the 3ware site and need this to be loaded at the start. I also like cpufreq.ko to be loaded at the start, but I could also build this in the kernel. P.S. I considered posting this to questions@ but thought this might be to complex for that list. -- Alex From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 22:44:02 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DC1E16A468 for ; Tue, 13 Nov 2007 22:44:02 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id E202213C448 for ; Tue, 13 Nov 2007 22:44:01 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 86383 invoked by uid 110); 13 Nov 2007 21:43:46 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 13 Nov 2007 21:43:46 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" , "Sean McAfee" Date: Tue, 13 Nov 2007 16:45:38 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: <47016605.1000003@collaborativefusion.com> MIME-Version: 1.0 Message-Id: <20071113224401.E202213C448@mx1.freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 22:44:02 -0000 Hello, I'm just wondering, was this ever resolved? I was about to start using new 2950 with Perc5 in it, but now I'm afraid to as I cannot afford downtime. Why this is still a linux hack is beyond me. The way Dell is doing, they ought to have a port specifically for FreeBSD If I disable PR altogether (not sure if this is possible, yet), although I don't see why it wouldn't be, would the mentioned problem go away? Thank you, Simon On Mon, 01 Oct 2007 17:26:29 -0400, Sean McAfee wrote: >John Baldwin wrote: >> On Saturday 29 September 2007 09:18:17 pm Benjie Chen wrote: >> >> Hmm, I haven't tried with megacli, but an internal tool at work is able to >> start manual patrol reads w/o causing a crash, and I've also seen production >> boxes running automatic patrol reads w/o causing crashes. Do you have to >> have a certain load before it will crash? >The crashes that we've seen in production have occurred while patrol >reads kick off under moderate-high load, but in testing, an automatic >read will complete fine. Even with maxed-out I/O*, we haven't been able >to come up with reliable testing scenario to trigger crashes on >automatic patrol reads. >(*My base testing scenario involved running a pretty heavy stress [as in >the program available in ports], while repeatedly copying ports & src >from an NFS mount to another local mountpoint and SCPing a large file in >a loop from another machine.) >Sean McAfee >Collaborative Fusion, Inc. > smcafee@collaborativefusion.com > 412-422-3463 x 4025 >1710 Murray Avenue, Suite 320 >Pittsburgh, PA 15217 >**************************************************************** >IMPORTANT: This message contains confidential information >and is intended only for the individual named. If the reader of >this message is not an intended recipient (or the individual >responsible for the delivery of this message to an intended >recipient), please be advised that any re-use, dissemination, >distribution or copying of this message is prohibited. Please >notify the sender immediately by e-mail if you have received >this e-mail by mistake and delete this e-mail from your system. >E-mail transmission cannot be guaranteed to be secure or >error-free as information could be intercepted, corrupted, lost, >destroyed, arrive late or incomplete, or contain viruses. The >sender therefore does not accept liability for any errors or >omissions in the contents of this message, which arise as a >result of e-mail transmission. >**************************************************************** >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 23:17:19 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6D6116A41B for ; Tue, 13 Nov 2007 23:17:19 +0000 (UTC) (envelope-from benjie@addgene.org) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id CCDEA13C4D3 for ; Tue, 13 Nov 2007 23:17:19 +0000 (UTC) (envelope-from benjie@addgene.org) Received: by wa-out-1112.google.com with SMTP id k17so2272686waf for ; Tue, 13 Nov 2007 15:17:14 -0800 (PST) Received: by 10.115.46.9 with SMTP id y9mr89871waj.1194994241992; Tue, 13 Nov 2007 14:50:41 -0800 (PST) Received: by 10.114.15.16 with HTTP; Tue, 13 Nov 2007 14:50:41 -0800 (PST) Message-ID: Date: Tue, 13 Nov 2007 17:50:41 -0500 From: "Benjie Chen" To: Simon In-Reply-To: <20071113224401.E202213C448@mx1.freebsd.org> MIME-Version: 1.0 References: <47016605.1000003@collaborativefusion.com> <20071113224401.E202213C448@mx1.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Sean McAfee , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 23:17:20 -0000 If you disable PR, the problem will go away. Below are some useful commands. Sean mentioned that you could disable it, then set it to do an automatic PR 1 hour after you restart the automatic PR. automatic PR does not crash the system definitively, but manual PR does. So during your downtime, you could try to do an automatic PR... # Disables patrol reads on all adapters megacli -AdpPR -Dsbl -aALL # Enables automatic patrol reads megacli -AdpPR -EnblAuto -aALL # Sets the interval for automatic reads to 1 hour - it only # accepts whole numbers so that's the lowest you can go megacli -AdpPR -SetDelay 1 -aALL Some other useful ones: # Patrol read settings and information megacli -AdpPR -Info -aALL # Extended information megacli -AdpAllInfo -aALL # Export controller's event log to file megacli -AdpEventLog -IncludeDeleted -f -aALL # More logging megacli -FwTermLog -Dsply -aALL On 11/13/07, Simon wrote: > > Hello, > > I'm just wondering, was this ever resolved? I was about to start using > new 2950 with Perc5 in it, but now I'm afraid to as I cannot afford > downtime. Why this is still a linux hack is beyond me. The way Dell > is doing, they ought to have a port specifically for FreeBSD > > If I disable PR altogether (not sure if this is possible, yet), although I > don't see why it wouldn't be, would the mentioned problem go away? > > Thank you, > Simon > > > On Mon, 01 Oct 2007 17:26:29 -0400, Sean McAfee wrote: > > >John Baldwin wrote: > >> On Saturday 29 September 2007 09:18:17 pm Benjie Chen wrote: > >> > >> Hmm, I haven't tried with megacli, but an internal tool at work is able > to > >> start manual patrol reads w/o causing a crash, and I've also seen > production > >> boxes running automatic patrol reads w/o causing crashes. Do you have > to > >> have a certain load before it will crash? > > >The crashes that we've seen in production have occurred while patrol > >reads kick off under moderate-high load, but in testing, an automatic > >read will complete fine. Even with maxed-out I/O*, we haven't been able > >to come up with reliable testing scenario to trigger crashes on > >automatic patrol reads. > > > >(*My base testing scenario involved running a pretty heavy stress [as in > >the program available in ports], while repeatedly copying ports & src > >from an NFS mount to another local mountpoint and SCPing a large file in > >a loop from another machine.) > > > >Sean McAfee > >Collaborative Fusion, Inc. > > smcafee@collaborativefusion.com > > 412-422-3463 x 4025 > > >1710 Murray Avenue, Suite 320 > >Pittsburgh, PA 15217 > > >**************************************************************** > >IMPORTANT: This message contains confidential information > >and is intended only for the individual named. If the reader of > >this message is not an intended recipient (or the individual > >responsible for the delivery of this message to an intended > >recipient), please be advised that any re-use, dissemination, > >distribution or copying of this message is prohibited. Please > >notify the sender immediately by e-mail if you have received > >this e-mail by mistake and delete this e-mail from your system. > >E-mail transmission cannot be guaranteed to be secure or > >error-free as information could be intercepted, corrupted, lost, > >destroyed, arrive late or incomplete, or contain viruses. The > >sender therefore does not accept liability for any errors or > >omissions in the contents of this message, which arise as a > >result of e-mail transmission. > >**************************************************************** > > > >_______________________________________________ > >freebsd-hardware@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > >To unsubscribe, send any mail to " > freebsd-hardware-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org > " > -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 13 23:43:35 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 017EC16A418 for ; Tue, 13 Nov 2007 23:43:35 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 920B213C442 for ; Tue, 13 Nov 2007 23:43:34 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 14615 invoked by uid 110); 13 Nov 2007 23:43:32 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 13 Nov 2007 23:43:32 -0000 From: "Simon" To: "Benjie Chen" Date: Tue, 13 Nov 2007 18:45:28 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: MIME-Version: 1.0 Message-Id: <20071113234334.920B213C442@mx1.freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Sean McAfee , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Nov 2007 23:43:35 -0000 So everyone that uses Dell servers with Perc5 and 6.x disables automatic PR? -Simon --Original Message Text--- From: Benjie Chen Date: Tue, 13 Nov 2007 17:50:41 -0500 If you disable PR, the problem will go away. Below are some useful commands. Sean mentioned that you could disable it, then set it to do an automatic PR 1 hour after you restart the automatic PR. automatic PR does not crash the system definitively, but manual PR does. So during your downtime, you could try to do an automatic PR... # Disables patrol reads on all adapters megacli -AdpPR -Dsbl -aALL # Enables automatic patrol reads megacli -AdpPR -EnblAuto -aALL # Sets the interval for automatic reads to 1 hour - it only # accepts whole numbers so that's the lowest you can go megacli -AdpPR -SetDelay 1 -aALL Some other useful ones: # Patrol read settings and information megacli -AdpPR -Info -aALL # Extended information megacli -AdpAllInfo -aALL # Export controller's event log to file megacli -AdpEventLog -IncludeDeleted -f -aALL # More logging megacli -FwTermLog -Dsply -aALL On 11/13/07, Simon wrote: Hello, I'm just wondering, was this ever resolved? I was about to start using new 2950 with Perc5 in it, but now I'm afraid to as I cannot afford downtime. Why this is still a linux hack is beyond me. The way Dell is doing, they ought to have a port specifically for FreeBSD If I disable PR altogether (not sure if this is possible, yet), although I don't see why it wouldn't be, would the mentioned problem go away? Thank you, Simon On Mon, 01 Oct 2007 17:26:29 -0400, Sean McAfee wrote: >John Baldwin wrote: >> On Saturday 29 September 2007 09:18:17 pm Benjie Chen wrote: >> >> Hmm, I haven't tried with megacli, but an internal tool at work is able to >> start manual patrol reads w/o causing a crash, and I've also seen production >> boxes running automatic patrol reads w/o causing crashes. Do you have to >> have a certain load before it will crash? >The crashes that we've seen in production have occurred while patrol >reads kick off under moderate-high load, but in testing, an automatic >read will complete fine. Even with maxed-out I/O*, we haven't been able >to come up with reliable testing scenario to trigger crashes on >automatic patrol reads. >(*My base testing scenario involved running a pretty heavy stress [as in >the program available in ports], while repeatedly copying ports & src >from an NFS mount to another local mountpoint and SCPing a large file in >a loop from another machine.) >Sean McAfee >Collaborative Fusion, Inc. > smcafee@collaborativefusion.com > 412-422-3463 x 4025 >1710 Murray Avenue, Suite 320 >Pittsburgh, PA 15217 >**************************************************************** >IMPORTANT: This message contains confidential information >and is intended only for the individual named. If the reader of >this message is not an intended recipient (or the individual >responsible for the delivery of this message to an intended >recipient), please be advised that any re-use, dissemination, >distribution or copying of this message is prohibited. Please >notify the sender immediately by e-mail if you have received >this e-mail by mistake and delete this e-mail from your system. >E-mail transmission cannot be guaranteed to be secure or >error-free as information could be intercepted, corrupted, lost, >destroyed, arrive late or incomplete, or contain viruses. The >sender therefore does not accept liability for any errors or >omissions in the contents of this message, which arise as a >result of e-mail transmission. >**************************************************************** >_______________________________________________ > freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to " freebsd-hardware-unsubscribe@freebsd.org" _______________________________________________ freebsd-hardware@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hardware To unsubscribe, send any mail to " freebsd-hardware-unsubscribe@freebsd.org" -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 14 05:28:40 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC44716A419 for ; Wed, 14 Nov 2007 05:28:40 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 8BF9D13C459 for ; Wed, 14 Nov 2007 05:28:39 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 78958 invoked by uid 110); 14 Nov 2007 05:28:38 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 14 Nov 2007 05:28:38 -0000 From: "Simon" To: "Benjie Chen" Date: Wed, 14 Nov 2007 00:30:33 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: <20071113234334.920B213C442@mx1.freebsd.org> MIME-Version: 1.0 Message-Id: <20071114052840.8BF9D13C459@mx1.freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Sean McAfee , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2007 05:28:41 -0000 On that note, I tried to start Consistency Check using megacli and it resulted in the same problem you reported while starting Patrol Read Other megacli commands also create problems both soft and hard. Is anything being done to correct this? PS: how do other people perform CC? Thank you, Simon On Tue, 13 Nov 2007 18:45:28 -0500, Simon wrote: >So everyone that uses Dell servers with Perc5 and 6.x disables automatic PR? >-Simon >--Original Message Text--- >From: Benjie Chen >Date: Tue, 13 Nov 2007 17:50:41 -0500 >If you disable PR, the problem will go away. Below are some useful commands. Sean mentioned that you could disable it, then set it to do an automatic PR 1 hour after you restart the automatic PR. automatic PR does not crash the system >definitively, but manual PR does. So during your downtime, you could try to do an automatic PR... ># Disables patrol reads on all adapters >megacli -AdpPR -Dsbl -aALL ># Enables automatic patrol reads >megacli -AdpPR -EnblAuto -aALL ># Sets the interval for automatic reads to 1 hour - it only ># accepts whole numbers so that's the lowest you can go >megacli -AdpPR -SetDelay 1 -aALL >Some other useful ones: ># Patrol read settings and information >megacli -AdpPR -Info -aALL ># Extended information >megacli -AdpAllInfo -aALL ># Export controller's event log to file >megacli -AdpEventLog -IncludeDeleted -f -aALL ># More logging >megacli -FwTermLog -Dsply -aALL >On 11/13/07, Simon wrote: Hello, >I'm just wondering, was this ever resolved? I was about to start using >new 2950 with Perc5 in it, but now I'm afraid to as I cannot afford >downtime. Why this is still a linux hack is beyond me. The way Dell >is doing, they ought to have a port specifically for FreeBSD >If I disable PR altogether (not sure if this is possible, yet), although I >don't see why it wouldn't be, would the mentioned problem go away? >Thank you, >Simon >On Mon, 01 Oct 2007 17:26:29 -0400, Sean McAfee wrote: >>John Baldwin wrote: >>> On Saturday 29 September 2007 09:18:17 pm Benjie Chen wrote: >>> >>> Hmm, I haven't tried with megacli, but an internal tool at work is able to >>> start manual patrol reads w/o causing a crash, and I've also seen production >>> boxes running automatic patrol reads w/o causing crashes. Do you have to >>> have a certain load before it will crash? >>The crashes that we've seen in production have occurred while patrol >>reads kick off under moderate-high load, but in testing, an automatic >>read will complete fine. Even with maxed-out I/O*, we haven't been able >>to come up with reliable testing scenario to trigger crashes on >>automatic patrol reads. >>(*My base testing scenario involved running a pretty heavy stress [as in >>the program available in ports], while repeatedly copying ports & src >>from an NFS mount to another local mountpoint and SCPing a large file in >>a loop from another machine.) >>Sean McAfee >>Collaborative Fusion, Inc. >> smcafee@collaborativefusion.com >> 412-422-3463 x 4025 >>1710 Murray Avenue, Suite 320 >>Pittsburgh, PA 15217 >>**************************************************************** >>IMPORTANT: This message contains confidential information >>and is intended only for the individual named. If the reader of >>this message is not an intended recipient (or the individual >>responsible for the delivery of this message to an intended >>recipient), please be advised that any re-use, dissemination, >>distribution or copying of this message is prohibited. Please >>notify the sender immediately by e-mail if you have received >>this e-mail by mistake and delete this e-mail from your system. >>E-mail transmission cannot be guaranteed to be secure or >>error-free as information could be intercepted, corrupted, lost, >>destroyed, arrive late or incomplete, or contain viruses. The >>sender therefore does not accept liability for any errors or >>omissions in the contents of this message, which arise as a >>result of e-mail transmission. >>**************************************************************** >>_______________________________________________ >> freebsd-hardware@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >>To unsubscribe, send any mail to " freebsd-hardware-unsubscribe@freebsd.org" >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to " freebsd-hardware-unsubscribe@freebsd.org" >-- >Benjie Chen, Ph.D. >Addgene, a better way to share plasmids >www.addgene.org >_______________________________________________ >freebsd-hardware@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >To unsubscribe, send any mail to "freebsd-hardware-unsubscribe@freebsd.org" From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 14 09:59:36 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F24AB16A417 for ; Wed, 14 Nov 2007 09:59:36 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.183]) by mx1.freebsd.org (Postfix) with ESMTP id 6456413C469 for ; Wed, 14 Nov 2007 09:59:36 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by el-out-1112.google.com with SMTP id s27so38932ele for ; Wed, 14 Nov 2007 01:59:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; bh=NMqmJVf8MgjKddkc2QMmTwn5f2TfyFnWAELbuZ3Yf8Y=; b=RkPbdzJy+R0mAHdYQGQYFzZS9+6becUHCHA1soRU0UUYC3qDfoonhVDCxBfVdbBfz3JTLG3dMqd4pEL7dwY7ixV9mfwCcpAtYUgstFQkTl9/rtpuDIB3Z6AdEVsYVsqBJFNJ0pxh0JnIjjBRRcggcK0lOtETOxSw8+SpY/L2Fek= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=b92VpWRCid1kUatv6JfdIL8s47f4aewYkQX+grrvgSCTp7cSNRIPHcaTR3/8shLf63xz7wK6eHuKEEMB8Asn0Bpe0Ca/48IXFwRIe2EYgJB/C8iQpr9zxHxDrc5FyJ7nPYTChxV7IRnoDVVbx2SjS0W24QuSwUwCe3LuOqrLDSg= Received: by 10.70.72.11 with SMTP id u11mr2956318wxa.1195034375661; Wed, 14 Nov 2007 01:59:35 -0800 (PST) Received: by 10.70.40.8 with HTTP; Wed, 14 Nov 2007 01:59:35 -0800 (PST) Message-ID: Date: Wed, 14 Nov 2007 09:59:35 +0000 From: "Rui Paulo" Sender: rpaulo@gmail.com To: "John Baldwin" In-Reply-To: <200711121611.37781.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_5658_19956574.1195034375670" References: <4A5A9C78-22AC-4480-BDEB-A72F6CF472DB@fnop.net> <200711121351.58616.jhb@freebsd.org> <200711121611.37781.jhb@freebsd.org> X-Google-Sender-Auth: 2fdb38528703c2d6 Cc: freebsd-current@freebsd.org, freebsd-i386@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: MacBook users: possible fix for the SMP problem X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2007 09:59:37 -0000 ------=_Part_5658_19956574.1195034375670 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Nov 12, 2007 9:11 PM, John Baldwin wrote: > I'm not sure where exactly one would add it, but I don't think the RTC clock > routine is the right place. Maybe do it at the start of cpu_startup() in > machdep.c instead? That works for me. See the attached patch. Regards. -- Rui Paulo ------=_Part_5658_19956574.1195034375670 Content-Type: application/octet-stream; name=machdep.c.diff Content-Transfer-Encoding: base64 X-Attachment-Id: f_f8zolsu10 Content-Disposition: attachment; filename=machdep.c.diff SW5kZXg6IGkzODYvbWFjaGRlcC5jCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3Jj L3N5cy9pMzg2L2kzODYvbWFjaGRlcC5jLHYKcmV0cmlldmluZyByZXZpc2lvbiAxLjY2MApkaWZm IC11IC1wIC1yMS42NjAgbWFjaGRlcC5jCi0tLSBpMzg2L21hY2hkZXAuYwk1IE5vdiAyMDA3IDEx OjM2OjExIC0wMDAwCTEuNjYwCisrKyBpMzg2L21hY2hkZXAuYwkxNCBOb3YgMjAwNyAwOTo1Nzow OSAtMDAwMApAQCAtMTc0LDYgKzE3NCw5IEBAIFNZU0lOSVQoY3B1LCBTSV9TVUJfQ1BVLCBTSV9P UkRFUl9GSVJTVCwKIGV4dGVybiB2bV9vZmZzZXRfdCBrc3ltX3N0YXJ0LCBrc3ltX2VuZDsKICNl bmRpZgogCisvKiBJbnRlbCBJQ0ggcmVnaXN0ZXIgKi8KKyNkZWZpbmUgSUNIX1BNQkFTRSAgICAg MHg0MDAKKwogaW50CV91ZGF0YXNlbCwgX3Vjb2Rlc2VsOwogdV9pbnQJYmFzZW1lbTsKIApAQCAt MjE5LDYgKzIyMiwyNyBAQCBzdGF0aWMgdm9pZAogY3B1X3N0YXJ0dXAoZHVtbXkpCiAJdm9pZCAq ZHVtbXk7CiB7CisJY2hhciAqaWNoZW52LCAqc3lzZW52OworCQorCS8qCisJICogT24gc29tZSBz eXN0ZW1zLCBuYW1lbHkgTWFjQm9va3MsIHdlIG5lZWQgdG8gZGlzYWxsb3cgdGhlCisJICogbGVn YWN5IFVTQiBjaXJjdWl0IHRvIGdlbmVyYXRlIGFuIFNNSSMgYmVjYXVzZSB0aGlzIGNhbgorCSAq IGNhdXNlIHNldmVyYWwgcHJvYmxlbXMsIG5hbWVseTogaW5jb3JyZWN0IENQVSBmcmVxdWVuY3kK KwkgKiBkZXRlY3Rpb24gYW5kIGZhaWx1cmUgdG8gc3RhcnQgdGhlIEFQcy4KKwkgKi8KKwlpY2hl bnYgPSBnZXRlbnYoImh3LmljaC5kaXNhYmxlX2xlZ2FjeV91c2IiKTsKKwlzeXNlbnYgPSBnZXRl bnYoInNtYmlvcy5zeXN0ZW0ucHJvZHVjdCIpOworCWlmICgoaWNoZW52ICE9ICBOVUxMKSB8fCAo c3lzZW52ICE9IE5VTEwgJiYKKwkgICAgc3RybmNtcChzeXNlbnYsICJNYWNCb29rIiwgNykgPT0g MCkpIHsKKwkJaWYgKGJvb3R2ZXJib3NlKQorCQkJcHJpbnRmKCJEaXNhYmxpbmcgTEVHQUNZX1VT Ql9FTiBiaXQgb24gSW50ZWwgSUNILlxuIik7CisJCW91dGwoSUNIX1BNQkFTRSArIDB4MzAsIGlu bChJQ0hfUE1CQVNFICsgMHgzMCkgJiB+MHg4KTsKKwl9CisJaWYgKGljaGVudikKKwkJZnJlZWVu dihpY2hlbnYpOworCWlmIChzeXNlbnYpCisJCWZyZWVlbnYoc3lzZW52KTsKKwogCS8qCiAJICog R29vZCB7bW9ybmluZyxhZnRlcm5vb24sZXZlbmluZyxuaWdodH0uCiAJICovCg== ------=_Part_5658_19956574.1195034375670-- From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 14 10:27:50 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7B6F16A41A for ; Wed, 14 Nov 2007 10:27:49 +0000 (UTC) (envelope-from jason.thomson@mintel.com) Received: from s200aog11.obsmtp.com (s200aog11.obsmtp.com [207.126.144.125]) by mx1.freebsd.org (Postfix) with SMTP id 8E77713C4C4 for ; Wed, 14 Nov 2007 10:27:47 +0000 (UTC) (envelope-from jason.thomson@mintel.com) Received: from source ([217.206.187.80]) by eu1sys200aob011.postini.com ([207.126.147.11]) with SMTP; Wed, 14 Nov 2007 10:27:43 UTC Received: from [10.0.62.5] (unknown [10.0.62.5]) by rodney.mintel.co.uk (Postfix) with ESMTP id CE81C18141F; Wed, 14 Nov 2007 10:09:55 +0000 (GMT) Message-ID: <473AC973.70509@mintel.com> Date: Wed, 14 Nov 2007 10:09:55 +0000 From: Jason Thomson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Simon References: <20071113234334.920B213C442@mx1.freebsd.org> In-Reply-To: <20071113234334.920B213C442@mx1.freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Sean McAfee , Benjie Chen , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2007 10:27:50 -0000 We have ~20 Dell servers with 6.x and Perc5. Automatic PR is enabled on all of them, and happens once a week without any problems (so far - since July). Obviously, from the thread, manual Patrol Reads cause a definite problem, but it's not clear that the initial problem had the same symptoms - just that there was a correlation between the automatic Patrol Reads and the server lockup? I guess it may be that under heavy load (exacerbated by PR) something else gets screwed up and causes the machine lockup? Simon wrote: > So everyone that uses Dell servers with Perc5 and 6.x disables automatic PR? > > -Simon > > --Original Message Text--- > From: Benjie Chen > Date: Tue, 13 Nov 2007 17:50:41 -0500 > > If you disable PR, the problem will go away. Below are some useful commands. Sean mentioned that you could disable it, then set it to do an automatic PR 1 hour after you restart the automatic PR. automatic PR does not crash the system > definitively, but manual PR does. So during your downtime, you could try to do an automatic PR... > > # Disables patrol reads on all adapters > megacli -AdpPR -Dsbl -aALL > > # Enables automatic patrol reads > megacli -AdpPR -EnblAuto -aALL > > # Sets the interval for automatic reads to 1 hour - it only > > # accepts whole numbers so that's the lowest you can go > megacli -AdpPR -SetDelay 1 -aALL > > > Some other useful ones: > > # Patrol read settings and information > megacli -AdpPR -Info -aALL > > # Extended information > > megacli -AdpAllInfo -aALL > > # Export controller's event log to file > megacli -AdpEventLog -IncludeDeleted -f -aALL > > # More logging > megacli -FwTermLog -Dsply -aALL > > > On 11/13/07, Simon wrote: Hello, > > I'm just wondering, was this ever resolved? I was about to start using > new 2950 with Perc5 in it, but now I'm afraid to as I cannot afford > downtime. Why this is still a linux hack is beyond me. The way Dell > is doing, they ought to have a port specifically for FreeBSD > > If I disable PR altogether (not sure if this is possible, yet), although I > don't see why it wouldn't be, would the mentioned problem go away? > > Thank you, > Simon > > > On Mon, 01 Oct 2007 17:26:29 -0400, Sean McAfee wrote: > > >>John Baldwin wrote: >> >>>On Saturday 29 September 2007 09:18:17 pm Benjie Chen wrote: >>> >>>Hmm, I haven't tried with megacli, but an internal tool at work is able to >>>start manual patrol reads w/o causing a crash, and I've also seen production >>>boxes running automatic patrol reads w/o causing crashes. Do you have to >>>have a certain load before it will crash? > > >>The crashes that we've seen in production have occurred while patrol >>reads kick off under moderate-high load, but in testing, an automatic >>read will complete fine. Even with maxed-out I/O*, we haven't been able >>to come up with reliable testing scenario to trigger crashes on >>automatic patrol reads. > > > >>(*My base testing scenario involved running a pretty heavy stress [as in >>the program available in ports], while repeatedly copying ports & src > >>from an NFS mount to another local mountpoint and SCPing a large file in > >>a loop from another machine.) > > > >>Sean McAfee >>Collaborative Fusion, Inc. >> smcafee@collaborativefusion.com >> 412-422-3463 x 4025 > > >>1710 Murray Avenue, Suite 320 >>Pittsburgh, PA 15217 > > >>**************************************************************** >>IMPORTANT: This message contains confidential information >>and is intended only for the individual named. If the reader of >>this message is not an intended recipient (or the individual >>responsible for the delivery of this message to an intended >>recipient), please be advised that any re-use, dissemination, >>distribution or copying of this message is prohibited. Please >>notify the sender immediately by e-mail if you have received >>this e-mail by mistake and delete this e-mail from your system. >>E-mail transmission cannot be guaranteed to be secure or >>error-free as information could be intercepted, corrupted, lost, >>destroyed, arrive late or incomplete, or contain viruses. The >>sender therefore does not accept liability for any errors or >>omissions in the contents of this message, which arise as a >>result of e-mail transmission. >>**************************************************************** > > > >>_______________________________________________ >>freebsd-hardware@freebsd.org mailing list >>http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >>To unsubscribe, send any mail to " freebsd-hardware-unsubscribe@freebsd.org" > > > > > _______________________________________________ > freebsd-hardware@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hardware > To unsubscribe, send any mail to " freebsd-hardware-unsubscribe@freebsd.org" > > > > > From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 14 12:22:10 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9756416A4DC for ; Wed, 14 Nov 2007 12:22:10 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 42E8613C4BB for ; Wed, 14 Nov 2007 12:22:10 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 4648 invoked by uid 110); 14 Nov 2007 12:22:07 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 14 Nov 2007 12:22:07 -0000 From: "Simon" To: "Jason Thomson" Date: Wed, 14 Nov 2007 07:23:52 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: <473AC973.70509@mintel.com> MIME-Version: 1.0 Message-Id: <20071114122210.42E8613C4BB@mx1.freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Sean McAfee , Benjie Chen , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Nov 2007 12:22:10 -0000 Do you guys perform consistency checks on your RAID5 or other redundant arrays? -Simon On Wed, 14 Nov 2007 10:09:55 +0000, Jason Thomson wrote: >We have ~20 Dell servers with 6.x and Perc5. >Automatic PR is enabled on all of them, and happens once a week >without any problems (so far - since July). >Obviously, from the thread, manual Patrol Reads cause a definite >problem, but it's not clear that the initial problem had the same >symptoms - just that there was a correlation between the automatic >Patrol Reads and the server lockup? >I guess it may be that under heavy load (exacerbated by PR) something >else gets screwed up and causes the machine lockup? >Simon wrote: >> So everyone that uses Dell servers with Perc5 and 6.x disables automatic PR? >> >> -Simon >> >> --Original Message Text--- >> From: Benjie Chen >> Date: Tue, 13 Nov 2007 17:50:41 -0500 >> >> If you disable PR, the problem will go away. Below are some useful commands. Sean mentioned that you could disable it, then set it to do an automatic PR 1 hour after you restart the automatic PR. automatic PR does not crash the system >> definitively, but manual PR does. So during your downtime, you could try to do an automatic PR... >> >> # Disables patrol reads on all adapters >> megacli -AdpPR -Dsbl -aALL >> >> # Enables automatic patrol reads >> megacli -AdpPR -EnblAuto -aALL >> >> # Sets the interval for automatic reads to 1 hour - it only >> >> # accepts whole numbers so that's the lowest you can go >> megacli -AdpPR -SetDelay 1 -aALL >> >> >> Some other useful ones: >> >> # Patrol read settings and information >> megacli -AdpPR -Info -aALL >> >> # Extended information >> >> megacli -AdpAllInfo -aALL >> >> # Export controller's event log to file >> megacli -AdpEventLog -IncludeDeleted -f -aALL >> >> # More logging >> megacli -FwTermLog -Dsply -aALL >> >> >> On 11/13/07, Simon wrote: Hello, >> >> I'm just wondering, was this ever resolved? I was about to start using >> new 2950 with Perc5 in it, but now I'm afraid to as I cannot afford >> downtime. Why this is still a linux hack is beyond me. The way Dell >> is doing, they ought to have a port specifically for FreeBSD >> >> If I disable PR altogether (not sure if this is possible, yet), although I >> don't see why it wouldn't be, would the mentioned problem go away? >> >> Thank you, >> Simon >> >> >> On Mon, 01 Oct 2007 17:26:29 -0400, Sean McAfee wrote: >> >> >>>John Baldwin wrote: >>> >>>>On Saturday 29 September 2007 09:18:17 pm Benjie Chen wrote: >>>> >>>>Hmm, I haven't tried with megacli, but an internal tool at work is able to >>>>start manual patrol reads w/o causing a crash, and I've also seen production >>>>boxes running automatic patrol reads w/o causing crashes. Do you have to >>>>have a certain load before it will crash? >> >> >>>The crashes that we've seen in production have occurred while patrol >>>reads kick off under moderate-high load, but in testing, an automatic >>>read will complete fine. Even with maxed-out I/O*, we haven't been able >>>to come up with reliable testing scenario to trigger crashes on >>>automatic patrol reads. >> >> >> >>>(*My base testing scenario involved running a pretty heavy stress [as in >>>the program available in ports], while repeatedly copying ports & src >> >>>from an NFS mount to another local mountpoint and SCPing a large file in >> >>>a loop from another machine.) >> >> >> >>>Sean McAfee >>>Collaborative Fusion, Inc. >>> smcafee@collaborativefusion.com >>> 412-422-3463 x 4025 >> >> >>>1710 Murray Avenue, Suite 320 >>>Pittsburgh, PA 15217 >> >> >>>**************************************************************** >>>IMPORTANT: This message contains confidential information >>>and is intended only for the individual named. If the reader of >>>this message is not an intended recipient (or the individual >>>responsible for the delivery of this message to an intended >>>recipient), please be advised that any re-use, dissemination, >>>distribution or copying of this message is prohibited. Please >>>notify the sender immediately by e-mail if you have received >>>this e-mail by mistake and delete this e-mail from your system. >>>E-mail transmission cannot be guaranteed to be secure or >>>error-free as information could be intercepted, corrupted, lost, >>>destroyed, arrive late or incomplete, or contain viruses. The >>>sender therefore does not accept liability for any errors or >>>omissions in the contents of this message, which arise as a >>>result of e-mail transmission. >>>**************************************************************** >> >> >> >>>_______________________________________________ >>>freebsd-hardware@freebsd.org mailing list >>>http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >>>To unsubscribe, send any mail to " freebsd-hardware-unsubscribe@freebsd.org" >> >> >> >> >> _______________________________________________ >> freebsd-hardware@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hardware >> To unsubscribe, send any mail to " freebsd-hardware-unsubscribe@freebsd.org" >> >> >> >> >> From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 15 00:20:32 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0E7516A417 for ; Thu, 15 Nov 2007 00:20:32 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 8B41A13C45D for ; Thu, 15 Nov 2007 00:20:32 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 86451 invoked by uid 110); 15 Nov 2007 00:20:31 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 15 Nov 2007 00:20:31 -0000 From: "Simon" To: "freebsd-hardware@freebsd.org" Date: Wed, 14 Nov 2007 19:22:34 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: <20071114122210.42E8613C4BB@mx1.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20071115002032.8B41A13C45D@mx1.freebsd.org> Subject: ASR (adaptec 2015s) AMD64 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2007 00:20:32 -0000 Does anyone know the current status of asr driver under AMD64? All information I find leads to posts talking about asr broken under amd64. When I try to boot amd64 installation disc it doesn't see the logical drive. i386 setup sees it just fine. Thank you -Simon From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 15 20:55:19 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC3AF16A4A0 for ; Thu, 15 Nov 2007 20:55:19 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id 62D4613C478 for ; Thu, 15 Nov 2007 20:55:18 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from [192.168.2.62] (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (AUTH: LOGIN seklecki, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Thu, 15 Nov 2007 15:55:18 -0500 id 0005641B.473CB236.00007C17 From: "Brian A Seklecki (Mobile)" To: Simon In-Reply-To: <20071114122210.42E8613C4BB@mx1.freebsd.org> References: <20071114122210.42E8613C4BB@mx1.freebsd.org> Organization: Collaborative Fusion, Inc. Date: Thu, 15 Nov 2007 15:55:14 -0500 Message-Id: <1195160114.4042.154.camel@new-host> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.12.1 (2.12.1-3.fc8) Cc: Sean McAfee , Jason Thomson , Benjie Chen , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2007 20:55:19 -0000 On Wed, 2007-11-14 at 07:23 -0500, Simon wrote: > Do you guys perform consistency checks on your RAID5 > or other redundant arrays? > > -Simon > > > On Wed, 14 Nov 2007 10:09:55 +0000, Jason Thomson wrote: Normally I'd be praising Dell, but I think a little vendor bashing is due here. Its a software bug (driver). It can probably be easily fixed. I think there's a PR on it somewhere (will check). We eliminated firmware bugs through P.O.L. I suspect, but haven't confirmed, that the driver developer used a reference platform w/ the "Patrol Reads" disabled. Maybe that platform was provided by the employer, having already passed through the hands of wise administrators who saw through the marketing _BULLSHIT_ that "Patrol Reads" really are. The linux beast-crew on poweredge-linux@ claims that it doesn't happen on RHEL. But wow would they really be able to differentiate a PERC5-related crash from any other inexplicable Linux kernel panic? Well, there's a lot of them and they like to whine a lot, so I imagine Dell would have done something. The whole thing is a UGLY UGLY hack. Needing Linux 32-bit compat support just to monitor and administer your RAID controller? Might as well just install Redhat and send your root password to misc@openbsd.org. All of that functionality really should be tied into an out-of-band system like the LOM. The problem is that the DRAC5 is crap too, crap customized for Windows users. The PERC5 is OEM crappy closed source hardware, and Dell should know better. The Broadcom NICS (bge(4)) are crap. Let's not forget the HA NIC features that only work in select OSs. The only praise Dell gets is that the IPMI on the integrated IPMI/DRAC5 card is faster. It's all subtle vendor lock-in crap. As if no one remembers the 90s and the fall of UNIX? Dell selectively uses aspects of F/OSS methodology to suit their needs. If you think back, 18 months after the 8th gen was release, FreeBSD was rock-solid on that platform. Intel NICs and PERC4. AMI/LSI even released the source code to the MegArc CLI. Anyway, Dell really screwed up on the 9th gen. ~BAS (Likes to do his vendor bashing _before_ lunch, but sometimes takes a late one) From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 15 21:20:26 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4DA816A417 for ; Thu, 15 Nov 2007 21:20:26 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 5C3E613C45A for ; Thu, 15 Nov 2007 21:20:25 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 61824 invoked by uid 110); 15 Nov 2007 21:20:24 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 15 Nov 2007 21:20:24 -0000 From: "Simon" To: "Brian A Seklecki (Mobile)" Date: Thu, 15 Nov 2007 16:22:28 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: <1195160114.4042.154.camel@new-host> MIME-Version: 1.0 Message-Id: <20071115212026.5C3E613C45A@mx1.freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Sean McAfee , Jason Thomson , Benjie Chen , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Nov 2007 21:20:26 -0000 I don't find this as bashing, rather as valuable input, which I always welcome and appreciate! If nobody brings out the problems then how is one to know other than thru hard hands-on experience. Problem I see there is nothing better which works with FreeBSD when it comes to new servers. Even older ASR driver is not supported under amd64 Older LSI MegaRAIDs are same crap with half functionality malfunctioning or not supported. So what works better than Dell PERC5+DARC5+Broadcom NICs? I have been using Supermicro + LSI controllers and that is also a bunch of hack. HP servers any better? If Patrol Reads are marketing bullshit, what do you use? consistency checking? How do you insure integrity of your RAID5 arrays without either? should parity get screwed up or drives develop bad blocks and a drive fails, the array will either not have enough parity to rebuilt replaced drive or the entire array will get hosed. Happened at least few times to me during the last few years. The way I see it, until manufacturers such as Dell and HP start fully supporting FreeBSD, the mentioned problems will never go away and FreeBSD will always be a bunch of hack when it comes to supporting hardware such as RAID and or NIC cards. This is why partly many companies prefer Linux or even Windows. -Simon On Thu, 15 Nov 2007 15:55:14 -0500, Brian A Seklecki (Mobile) wrote: >On Wed, 2007-11-14 at 07:23 -0500, Simon wrote: >> Do you guys perform consistency checks on your RAID5 >> or other redundant arrays? >> >> -Simon >> >> >> On Wed, 14 Nov 2007 10:09:55 +0000, Jason Thomson wrote: >Normally I'd be praising Dell, but I think a little vendor bashing is >due here. >Its a software bug (driver). It can probably be easily fixed. I think >there's a PR on it somewhere (will check). >We eliminated firmware bugs through P.O.L. I suspect, but haven't >confirmed, that the driver developer used a reference platform w/ the >"Patrol Reads" disabled. Maybe that platform was provided by the >employer, having already passed through the hands of wise administrators >who saw through the marketing _BULLSHIT_ that "Patrol Reads" really are. >The linux beast-crew on poweredge-linux@ claims that it doesn't happen >on RHEL. But wow would they really be able to differentiate a >PERC5-related crash from any other inexplicable Linux kernel panic? >Well, there's a lot of them and they like to whine a lot, so I imagine >Dell would have done something. >The whole thing is a UGLY UGLY hack. Needing Linux 32-bit compat >support just to monitor and administer your RAID controller? Might as >well just install Redhat and send your root password to >misc@openbsd.org. >All of that functionality really should be tied into an out-of-band >system like the LOM. >The problem is that the DRAC5 is crap too, crap customized for Windows >users. >The PERC5 is OEM crappy closed source hardware, and Dell should know >better. >The Broadcom NICS (bge(4)) are crap. Let's not forget the HA NIC >features that only work in select OSs. >The only praise Dell gets is that the IPMI on the integrated IPMI/DRAC5 >card is faster. >It's all subtle vendor lock-in crap. As if no one remembers the 90s and >the fall of UNIX? >Dell selectively uses aspects of F/OSS methodology to suit their needs. >If you think back, 18 months after the 8th gen was release, FreeBSD was >rock-solid on that platform. Intel NICs and PERC4. AMI/LSI even >released the source code to the MegArc CLI. >Anyway, Dell really screwed up on the 9th gen. >~BAS (Likes to do his vendor bashing _before_ lunch, but sometimes takes >a late one) From owner-freebsd-hardware@FreeBSD.ORG Fri Nov 16 12:54:39 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 480D516A41A for ; Fri, 16 Nov 2007 12:54:39 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from mx00.pub.collaborativefusion.com (mx00.pub.collaborativefusion.com [206.210.89.199]) by mx1.freebsd.org (Postfix) with ESMTP id EDD1A13C46A for ; Fri, 16 Nov 2007 12:54:38 +0000 (UTC) (envelope-from bseklecki@collaborativefusion.com) Received: from [192.168.2.62] (pr40.pitbpa0.pub.collaborativefusion.com [206.210.89.202]) (AUTH: LOGIN seklecki, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by wingspan with esmtp; Fri, 16 Nov 2007 07:54:37 -0500 id 0005641B.473D930D.00015434 From: "Brian A Seklecki (Mobile)" To: Simon In-Reply-To: <20071115212026.5C3E613C45A@mx1.freebsd.org> References: <20071115212026.5C3E613C45A@mx1.freebsd.org> Organization: Collaborative Fusion, Inc. Date: Fri, 16 Nov 2007 07:53:24 -0500 Message-Id: <1195217644.4042.199.camel@new-host> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Evolution 2.12.1 (2.12.1-3.fc8) Cc: Sean McAfee , Jason Thomson , Benjie Chen , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2007 12:54:39 -0000 > If Patrol Reads are marketing bullshit, what do you use? consistency If a block is bad, a block is bad. The disk has a certain number of spares. Those are automatically allocated by the disk underneath the controller. When that compliment is exhausted, then _THE DISK IS BAD_. A single bad sector on a RAID volume component disk means that you need to _REPLACE THE DISK_. When a controller finds a bad sector, that disk should be moved to degraded state. Period. As for the idea of randomly finding and fixing parity errors while the OS is running... hardware or otherwise related, that just sounds like a bad idea to me. I prefer the CMU RAIDFrame / GMirror approach: You check the volume at start-up. You search for records of a graceful shutdown on both components. If you _don't_ find them, you run a full parity check. The volume is then parity-clean until it is shutdown ungracefully. How could the parity be found to be bad while the OS is running if there are no bad components or other hardware events?? ( And why does the PERC5 (and for that matter, the PERC4) never scan parity at startup? ) I asked Dell two year ago and never got an answer. Until then, FreeBSD Gmirror is still a perfectly valid option. > The way I see it, until manufacturers such as Dell and HP start fully > supporting FreeBSD, the mentioned problems will never go away They don't have to "Support FreeBSD". Thats our job. What they need to do is work with OEM component vendors who don't consider kernel-hardware interface I.P. See OpenBSD. From owner-freebsd-hardware@FreeBSD.ORG Fri Nov 16 16:18:31 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5FEA16A41A for ; Fri, 16 Nov 2007 16:18:31 +0000 (UTC) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.freebsd.org (Postfix) with SMTP id 49FBE13C4B8 for ; Fri, 16 Nov 2007 16:18:30 +0000 (UTC) (envelope-from simon@optinet.com) Received: (qmail 7958 invoked by uid 110); 16 Nov 2007 16:18:20 -0000 Received: from unknown (HELO desktop1) (simon%optinet.com@69.112.29.182) by cobra.acceleratedweb.net with SMTP; 16 Nov 2007 16:18:20 -0000 From: "Simon" To: "Brian A Seklecki (Mobile)" Date: Fri, 16 Nov 2007 11:20:24 -0500 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2717) For Windows 2000 (5.1.2600;2) In-Reply-To: <1195217644.4042.199.camel@new-host> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <20071116161831.49FBE13C4B8@mx1.freebsd.org> Cc: Sean McAfee , Jason Thomson , Benjie Chen , "freebsd-hardware@freebsd.org" Subject: Re: PERC5 (LSI MegaSAS) Patrol Read crashes X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2007 16:18:31 -0000 LSI recommends consistency checks at least once a month. This is what I was told: should a block where parity is become bad, on the next read during consistency check this parity will be recalculated and rewritten elsewhere on the disk. This cannot happen on its own without a consistency check. The drive will try to remap bad blocks but it cannot do this unless the block is either read from or written to. It won't know there is a bad block until then. So if you develop bad blocks and a drive fails, you will have missing parity. Many times, there are places on the disks that are written to once and are then not used, so the disk never reads those blocks. When you run Patrol Read, it goes thru entire disk and even those parts that are otherwise not read from until you need to rebuilt. This is why both Patrol Reads and Consistency Checks are important. Please correct me if I'm wrong. -Simon On Fri, 16 Nov 2007 07:53:24 -0500, Brian A Seklecki (Mobile) wrote: >> If Patrol Reads are marketing bullshit, what do you use? consistency >If a block is bad, a block is bad. The disk has a certain number of >spares. Those are automatically allocated by the disk underneath the >controller. >When that compliment is exhausted, then _THE DISK IS BAD_. A single bad >sector on a RAID volume component disk means that you need to _REPLACE >THE DISK_. When a controller finds a bad sector, that disk should be >moved to degraded state. Period. >As for the idea of randomly finding and fixing parity errors while the >OS is running... hardware or otherwise related, that just sounds like a >bad idea to me. >I prefer the CMU RAIDFrame / GMirror approach: >You check the volume at start-up. You search for records of a graceful >shutdown on both components. If you _don't_ find them, you run a full >parity check. >The volume is then parity-clean until it is shutdown ungracefully. >How could the parity be found to be bad while the OS is running if there >are no bad components or other hardware events?? ( And why does the >PERC5 (and for that matter, the PERC4) never scan parity at startup? ) >I asked Dell two year ago and never got an answer. Until then, FreeBSD >Gmirror is still a perfectly valid option. >> The way I see it, until manufacturers such as Dell and HP start fully >> supporting FreeBSD, the mentioned problems will never go away >They don't have to "Support FreeBSD". Thats our job. What they need to >do is work with OEM component vendors who don't consider kernel-hardware >interface I.P. See OpenBSD.