From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 15 20:03:27 2010 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 72A301065676; Mon, 15 Mar 2010 20:03:27 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id ED6FE8FC17; Mon, 15 Mar 2010 20:03:26 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Mon, 15 Mar 2010 16:03:26 -0400 Message-ID: <4B9E928B.2070409@greatbaysoftware.com> Date: Mon, 15 Mar 2010 16:03:23 -0400 From: Charles Owens MIME-Version: 1.0 To: John Baldwin References: <4B75AB2D.2090306@greatbaysoftware.com> <201002181023.08131.jhb@freebsd.org> <4B7ED202.2030901@greatbaysoftware.com> <201002191315.13796.jhb@freebsd.org> In-Reply-To: <201002191315.13796.jhb@freebsd.org> X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: mptutil(8) segfault on IBM xSeries 3550 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, 15 Mar 2010 20:03:27 -0000 John Baldwin wrote: > On Friday 19 February 2010 1:01:38 pm Charles Owens wrote: > >> John Baldwin wrote: >> >>> On Monday 15 February 2010 5:25:15 pm Charles Owens wrote: >>> >>>> Charles Owens wrote: >>>> >>>>> Howdy, >>>>> >>>>> We're working with IBM hardware (xSeries 3550) that has an >>>>> mpt-based RAID controller... after initial success with testing the >>>>> mptutil utility, now operations other than "show adapter" and "show >>>>> volume" are resulting in segfaults. >>>>> >>>>> While it was working properly we created and removed volumes several >>>>> times, force-failed drives, and just generally put it through its >>>>> paces... and all seemed fine. Then, after a reboot, it suddenly started >>>>> failing with segfault as described, and nothing we do has helped to get >>>>> it out of this state (including trying to use the LSI in-BIOS manager to >>>>> create/delete volumes -- which in and of itself works fine). >>>>> >>>>> We found recent thread >>>>> http://docs.freebsd.org/cgi/mid.cgi?4B56CD4C.80503 and hoped that it >>>>> might somehow relate... and even tried the patch that John Baldwin >>>>> posted, but to no avail. >>>>> >>>>> Has anyone seen this behavior and/or have a suggested fix or workaround? >>>>> >>>>> >>>>> Here's the output of "mptutil show adapter": >>>>> >>>>> mpt0 Adapter: >>>>> Board Name: SR-BR10i >>>>> Board Assembly: L3-25116-01H >>>>> Chip Name: C1068E >>>>> Chip Revision: UNUSED >>>>> RAID Levels: RAID0, RAID1, RAID1E >>>>> RAID0 Stripes: 64K >>>>> RAID1E Stripes: 64K >>>>> RAID0 Drives/Vol: 1-10 >>>>> RAID1 Drives/Vol: 2 >>>>> RAID1E Drives/Vol: 3-10 >>>>> >>>>> >>>>> This work is being done using FreeBSD 8.0-RELEASE-p2 + PAE. >>>>> >>>>> >>>> I should add that the RAID controller in question is the IBM >>>> ServeRAID-BR10i SAS/SATA Controller which is based on the LSI 1068E >>>> processor, as described here: >>>> http://www-01.ibm.com/common/ssi/rep_ca/4/872/ENUSAG09-0104/index.html >>>> >>> Try this updated patch. It should fix the problems with 'mptutil show drives' >>> displaying all daX devices in the system rather than just the ones for the >>> mptX bus. I had incorrectly interpreted the XPT matches as being an AND >>> rather than an OR. This changes the code to first do a lookup for the logical >>> "path" (SCSI bus) for mptX devices and then do a second lookup to fetch any >>> daX devices on that path. I tested it on a machine with an mpt controller and >>> a USB disk. Unfortunately I wasn't able to test any of the RAID stuff, just >>> 'show drives'. This mpt(4) controller doesn't support RAID either, so I was >>> also able to verify the fix you had already tested for cleaning up 'show >>> adapter' output in that case. >>> >>> [patch omitted] >>> >> John, >> >> The patch appears to have resolved the problem. We're still banging on >> it, but so far it looks very good! >> >> Thanks very much! >> > > Excellent, thanks! I've committed it to HEAD and will MFC it in a week or > so. It is probably too late to make 7.3 however. > Again, thanks for the patch... overall it is working well... we're now able to successively do what we need to do with RAID system. We are, though, seeing some sor of error messages: # mptutil show volumes mpt0 Volumes: Id Size Level Stripe State Write-Cache Name mptutil: mpt_query_disk got 4 matches, expected 2 0 ( 279G) RAID-1 OPTIMAL Disabled # mptutil show config mpt0 Configuration: 1 volumes, 2 drives mptutil: mpt_query_disk got 4 matches, expected 2 volume 0 (279G) RAID-1 OPTIMAL spans: drive 1 (279G) ONLINE SATA drive 0 (279G) ONLINE SATA spare pools: 0 We can certainly live with this, but I wanted to let you know in case you thought it was worth digging into. Let me know if you need any additional debug info beyond this: # camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus1 target 1 lun 0 (pass1) at scbus2 target 0 lun 0 (pass2,cd0) at scbus3 target 0 lun 0 (da1,pass3) at scbus3 target 0 lun 1 (da2,pass4) Thanks, Charles From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 15 20:52:11 2010 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 43D53106566B for ; Mon, 15 Mar 2010 20:52:11 +0000 (UTC) (envelope-from mayo@oyam.ca) Received: from mail-fx0-f215.google.com (mail-fx0-f215.google.com [209.85.220.215]) by mx1.freebsd.org (Postfix) with ESMTP id D6C408FC08 for ; Mon, 15 Mar 2010 20:52:10 +0000 (UTC) Received: by fxm7 with SMTP id 7so655925fxm.3 for ; Mon, 15 Mar 2010 13:52:09 -0700 (PDT) Received: by 10.102.129.7 with SMTP id b7mr412390mud.11.1268684597719; Mon, 15 Mar 2010 13:23:17 -0700 (PDT) Received: from [192.168.167.108] (a221-smpafs01.blockb-142.stargate.ca [208.118.142.221]) by mx.google.com with ESMTPS id t10sm22796114muh.29.2010.03.15.13.23.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Mar 2010 13:23:16 -0700 (PDT) From: Mayo Jordanov Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 15 Mar 2010 13:23:12 -0700 Message-Id: To: freebsd-hardware@freebsd.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: read timeouts on a drive 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, 15 Mar 2010 20:52:11 -0000 Hello, I'm hitting some problems with a Toshiba drive (MK3263GSX).=20 When I boot from a cd during installation, it installs on it fine, and = there are no issues or errors on the consoles. When it comes to booting from the drive, it's geometry is detected as 0 = sectors, 0 heads, 0 cylynders, 0 mb and of course failts to boot. = (Geometry during install is correct). If I then boot off a cd or usb and = mount the drive, it works just fine, and everything from the = installation is on it, similarly copy to/from the drive is fine as well. I've had other OS installed on the drive (same system) no problem, and = it seems it's only having issues on FreeBSD during boot. Any ideas, = pointers? I don't know if it makes any difference, but the CD I install = from is a USB cdrom. I've also tried playing with ata timeouts, but it = didn't seem to help. There is no raid involved. I have two machines like = this, and both behave identically. The errors from dmesg during boot are: ad0: 0MB at ata0-master SATA150 ad0: FAILURE - READ_DMA48 status=3D51 = error=3D10 LBA=3D18446744073709551613 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551613 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551599 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551612 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551615 ad0: FAILURE - READ_DMA48 status=3D51 = error=3D10 LBA=3D18446744073709551553 Thank you, Mayo Jordanov= From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 15 22:56:20 2010 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 80A961065672 for ; Mon, 15 Mar 2010 22:56:20 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 2F9E98FC19 for ; Mon, 15 Mar 2010 22:56:19 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Mon, 15 Mar 2010 18:56:19 -0400 Message-ID: <4B9EBB10.5050804@greatbaysoftware.com> Date: Mon, 15 Mar 2010 18:56:16 -0400 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Subject: ttyu1 stuck at 115200 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, 15 Mar 2010 22:56:20 -0000 Hello, Working with pretty vanilla hardware running 8.0-RELEASE-p2, I find that ttyu0 works just fine as a serial console, but ttyu1 wants to default to 115200 baud (ttyu0 defaults to 9600 as expected). I'm used having details like baud-rate handled by argument given to getty via the respective line in /etc/ttys... but that doesn't seem to be the behavior I'm seeing. I couldn't get a login prompt at 9600 baud until I added the following line to /boot/device.hints and rebooted: hint.uart.1.baud="9600" Is this supposed to be how this is done now, or is there something else going on here? Any thoughts as to why the two ports behave differently? This is a Xeon-based system with the Intel S5000PAL motherboard... running GENERIC kernel. Here are related boot messages (with device.hints tuning in place): uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 uart0: [FILTER] uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 uart1: [FILTER] uart1: console (9600,n,8,1) Thanks very much, Charles -- Charles Owens Great Bay Software, Inc. From owner-freebsd-hardware@FreeBSD.ORG Mon Mar 15 23:18:45 2010 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 B8B581065670 for ; Mon, 15 Mar 2010 23:18:45 +0000 (UTC) (envelope-from mayo@oyam.ca) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id 5A0C88FC0A for ; Mon, 15 Mar 2010 23:18:44 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so306339eyf.3 for ; Mon, 15 Mar 2010 16:18:44 -0700 (PDT) Received: by 10.213.2.75 with SMTP id 11mr2736579ebi.14.1268695124086; Mon, 15 Mar 2010 16:18:44 -0700 (PDT) Received: from [192.168.167.108] (a221-smpafs01.blockb-142.stargate.ca [208.118.142.221]) by mx.google.com with ESMTPS id 14sm2924318ewy.14.2010.03.15.16.18.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Mar 2010 16:18:43 -0700 (PDT) From: Mayo Jordanov Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Mon, 15 Mar 2010 16:18:38 -0700 Message-Id: <81119F7B-E414-456F-A41C-BA5DE1EF8425@oyam.ca> To: freebsd-hardware@freebsd.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: read timeouts on a drive 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, 15 Mar 2010 23:18:45 -0000 Hello, I'm hitting some problems with a Toshiba drive (MK3263GSX).=20 When I boot from a cd during installation, it installs on it fine, and = there are no issues or errors on the consoles. When it comes to booting from the drive, it's geometry is detected as 0 = sectors, 0 heads, 0 cylynders, 0 mb and of course failts to boot. = (Geometry during install is correct). If I then boot off a cd or usb and = mount the drive, it works just fine, and everything from the = installation is on it, similarly copy to/from the drive is fine as well. I've had other OS installed on the drive (same system) no problem, and = it seems it's only having issues on FreeBSD during boot. Any ideas, = pointers? I don't know if it makes any difference, but the CD I install = from is a USB cdrom. I've also tried playing with ata timeouts, but it = didn't seem to help. There is no raid involved. I have two machines like = this, and both behave identically. The errors from dmesg during boot are: ad0: 0MB at ata0-master SATA150 ad0: FAILURE - READ_DMA48 status=3D51 = error=3D10 LBA=3D18446744073709551613 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551613 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551599 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551612 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551615 ad0: FAILURE - READ_DMA48 status=3D51 = error=3D10 LBA=3D18446744073709551553 Thank you, Mayo Jordanov= From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 16 01:39:34 2010 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 2AFEA1065676 for ; Tue, 16 Mar 2010 01:39:34 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 8C04D8FC16 for ; Tue, 16 Mar 2010 01:39:33 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id o2G1SXWB003915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 16 Mar 2010 02:28:33 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.3/8.14.3) with ESMTP id o2G1SRuj065587 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Mar 2010 02:28:27 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id o2G1SRDY067311; Tue, 16 Mar 2010 02:28:27 +0100 (CET) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id o2G1SRNN067310; Tue, 16 Mar 2010 02:28:27 +0100 (CET) (envelope-from ticso) Date: Tue, 16 Mar 2010 02:28:27 +0100 From: Bernd Walter To: Charles Owens Message-ID: <20100316012827.GN39056@cicely7.cicely.de> References: <4B9EBB10.5050804@greatbaysoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B9EBB10.5050804@greatbaysoftware.com> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-hardware@freebsd.org Subject: Re: ttyu1 stuck at 115200 X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2010 01:39:34 -0000 On Mon, Mar 15, 2010 at 06:56:16PM -0400, Charles Owens wrote: > Hello, > > Working with pretty vanilla hardware running 8.0-RELEASE-p2, I find that > ttyu0 works just fine as a serial console, but ttyu1 wants to default to > 115200 baud (ttyu0 defaults to 9600 as expected). I'm used having > details like baud-rate handled by argument given to getty via the > respective line in /etc/ttys... but that doesn't seem to be the behavior > I'm seeing. I couldn't get a login prompt at 9600 baud until I added > the following line to /boot/device.hints and rebooted: > > hint.uart.1.baud="9600" > > Is this supposed to be how this is done now, or is there something else > going on here? Any thoughts as to why the two ports behave differently? This is automatically passed from earlier bootcode, but as long as this code isn't compiled for uart1 it setups uart0. Previously the kernel default was 9600, but it seems this has changed. If you use boot2 with serial you need to recompile and reinstall it with BOOT_COMCONSOLE_PORT and BOOT_COMCONSOLE_SPEED setup. You need to recompile loader with at least BOOT_COMCONSOLE_PORT to handle a different port instead, but you can change the speed with comconsole_speed in loader.conf - nevertheless the default is also set with BOOT_COMCONSOLE_SPEED at compiletime. You should have at least the loader on serial as well - otherwise you can't change boot parameters or boot another kernel. I even prefer running boot2 on serial so I can switch loader in case something breaks loader with an update. > This is a Xeon-based system with the Intel S5000PAL motherboard... > running GENERIC kernel. Here are related boot messages (with > device.hints tuning in place): > > uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 on acpi0 > uart0: [FILTER] > uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 flags 0x10 on acpi0 > uart1: [FILTER] > uart1: console (9600,n,8,1) > > > Thanks very much, > > Charles > > -- > Charles Owens > Great Bay Software, Inc. > > > > _______________________________________________ > 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" -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 16 13:22:32 2010 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 C45D31065673 for ; Tue, 16 Mar 2010 13:22:32 +0000 (UTC) (envelope-from agh@coolrhaug.com) Received: from mail5.qnetau.com (mail5.qnetau.com [202.146.209.190]) by mx1.freebsd.org (Postfix) with ESMTP id 1B31D8FC17 for ; Tue, 16 Mar 2010 13:22:31 +0000 (UTC) Received: (qmail 35119 invoked by uid 399); 16 Mar 2010 13:22:29 -0000 Received: from unknown (HELO madcat.localnet) (203.59.9.21) by mail5.qnetau.com with ESMTPM; 16 Mar 2010 13:22:29 -0000 X-Originating-IP: 203.59.9.21 From: Alastair Hogge To: John Baldwin Date: Tue, 16 Mar 2010 21:22:28 +0800 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.5; i386; ; ) References: <201002212231.12018.agh@coolrhaug.com> <201002271530.05185.agh@coolrhaug.com> <201003011154.00827.jhb@freebsd.org> In-Reply-To: <201003011154.00827.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201003162122.28370.agh@coolrhaug.com> Cc: kochetkov.andrew@gmail.com, Randy Chou , freebsd-hardware@freebsd.org Subject: Re: Intel DP45SG motherboard problem (amd64) X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: agh@coolrhaug.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2010 13:22:32 -0000 On Tue March 2 2010 00:54:00 John Baldwin wrote: > On Saturday 27 February 2010 2:30:05 am Alastair Hogge wrote: > > On Sat February 27 2010 00:29:13 John Baldwin wrote: > > > On Friday 26 February 2010 6:15:28 am Alastair Hogge wrote: > > > > On Thu February 25 2010 21:02:58 John Baldwin wrote: > > > > > On Wednesday 24 February 2010 6:32:21 pm Alastair Hogge wrote: > > > > > > On Wed February 24 2010 22:46:29 John Baldwin wrote: > > > > > > > On Tuesday 23 February 2010 5:40:31 pm Alastair Hogge wrote: > > > > > > > > On Wed February 24 2010 00:14:00 John Baldwin wrote: > > > > > > > > > On Tuesday 23 February 2010 8:51:04 am Alastair Hogge wrote: > > > > > > > > > > > > Hello John, > > > > > > > > > > > > > > > > > > > > > > > > In regards to an old email thread: > > > > > > > > > > > > http://lists.freebsd.org/pipermail/freebsd- > > hardware/2009- > > > > > > > > > > > > June/thread.html#5887 > > > > > > > > > > > > > > > > > > > > > > > I've attached the i386 dmesg & "mptable device" from > > > > > > > > > > > > a 9.0-CURRENT -r204168 system which still fails on > > > > > > > > > > > > booting an amd64 CD. > > > > > > > > > > > > > > > > > > > > > > You need to build a custom amd64 kernel which includes > > > > > > > > > > > "device > > > > > > > > > > > > > > mptable" > > > > > > > > > > > > > > > > > > and use that. You may need to set > > 'hint.acpi.0.disabled=1' > > > > > > > > > > > > as well to force ACPI to be disabled. > > > > > > > > > > > > > > > > > > > > OK, I've cross built an amd64 system and installed it on > > > > > > > > > > a spare HDD. Once it booted I ran "mptable -verbose > > > > > > > > > > -dmesg -grope" Here is the > > > > > > > > > > > > > > output: > > > > > > > > > It appears that the new kernel works, yes? > > > > > > > > > > > > > > > > Yes > > > > > > > > > > > > > > > > > That should at least get you a > > > > > > > > > working system now. > > > > > > > > > > > > > > > > Pretty exciting, however, it looks like that booting from an > > > > > > > > installation CD is still problematic. > > > > > > > > > > > > > > Yes, but it is really odd that you do not have any ACPI tables. > > > > > > > All 64-bit machines should have ACPI. > > > > > > > > > > > > > > > > I have no idea why the system does not provide ACPI > > > > > > > > > tables. Is there a BIOS option to enable/disable ACPI > > perhaps? > > > > > > > > > I can't find anything . > > > > > > > > > > > > > > Can you save the output of 'acpidump -d -t' to a file and post > > > > > > > the > > > > > > URL? > > > > > > > > > > If the output is very short, you can just paste it inline into > > > > > > > a reply. > > > > > > > > > > > > # acpidump -d -t > > > > > > /* > > > > > > RSD PTR: OEM=INTEL, ACPI_Rev=2.0x (2) > > > > > > XSDT=0xcfd62e18, length=36, cksum=1 > > > > > > */ > > > > > > acpidump: XSDT is corrupted > > > > > > > > > > Hmm, the checksum for the XSDT is bad. You can try hacking > > > > > src/usr.sbin/acpi/acpidump/acpi.c to disable the checksum check for > > the > > > > > > XSDT. Just look for the 'XSDT is corrupted' string in that source > > file > > > > and > > > > > > > > comment out the call to acpi_checksum(). Something like this: > > > > > > > > > > rsdp = (ACPI_TABLE_HEADER *)acpi_map_sdt(rp- > > > > > >XsdtPhysicalAddress); > > > > > > > > if (memcmp(rsdp->Signature, "XSDT", 4) != 0 /* || > > > > > acpi_checksum(rsdp, rsdp->Length) != 0 */) > > > > > errx(1, "XSDT is corrupted"); > > > > > addr_size = sizeof(uint64_t); > > > > > > > > > > Then see if acpidump -d -t gets any further. > > > > > > > > Pleas see http://pastebin.ca/1811641 > > > > You might noticed a different XSDT in the lastest dump. This is > > > > because > > I > > > > > moved the amd64 hdd to the other system and booted it from there. > > > > Both > > > > > > systems > > > > > > > are identical except for the video cards. > > > > > > > > > I would also look for a BIOS > > > > > update perhaps, > > > > > > > > I've updated the BIOS, but still no luck. > > > > > > > > > and/or complain to your motherboard vendor that their BIOS > > > > > is broken. > > > > > > > > Complaining has begun. > > > > > > Hmm, it looks like it is a common problem with this board actually. > > > Try editing src/contrib/dev/acpica/include/acconfig.h and changing > > > ACPI_CHECKSUM_ABORT to 0 instead of FALSE. > > > > acpidump output doesn't change & the system still fails to boot with ACPI > > enabled. > > This would not change acpidump output, just the kernel. Are you able to > capture the boot messages with this kernel? Full log: http://codepad.org/96PT5OO8 > Specifically, do you get any > error messages from ACPI? Also, what happens if you find the code that > uses ACPI_CHECKSUM_ABORT (I think in sys/contrib/acpica/tables/tbutils.c) > and put #if 0 around that block? Full log with changes: http://codepad.org/QPmK0m9f Not much difference from the first log. From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 16 20:11:43 2010 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 2E273106566C for ; Tue, 16 Mar 2010 20:11:43 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id DFC978FC13 for ; Tue, 16 Mar 2010 20:11:42 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Tue, 16 Mar 2010 16:11:41 -0400 Message-ID: <4B9FE5FB.8010201@greatbaysoftware.com> Date: Tue, 16 Mar 2010 16:11:39 -0400 From: Charles Owens MIME-Version: 1.0 To: ticso@cicely.de References: <4B9EBB10.5050804@greatbaysoftware.com> <20100316012827.GN39056@cicely7.cicely.de> In-Reply-To: <20100316012827.GN39056@cicely7.cicely.de> X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hardware@freebsd.org Subject: Re: ttyu1 stuck at 115200 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, 16 Mar 2010 20:11:43 -0000 Bernd Walter wrote: > On Mon, Mar 15, 2010 at 06:56:16PM -0400, Charles Owens wrote: > >> Hello, >> >> Working with pretty vanilla hardware running 8.0-RELEASE-p2, I find that >> ttyu0 works just fine as a serial console, but ttyu1 wants to default to >> 115200 baud (ttyu0 defaults to 9600 as expected). I'm used having >> details like baud-rate handled by argument given to getty via the >> respective line in /etc/ttys... but that doesn't seem to be the behavior >> I'm seeing. I couldn't get a login prompt at 9600 baud until I added >> the following line to /boot/device.hints and rebooted: >> >> hint.uart.1.baud="9600" >> >> Is this supposed to be how this is done now, or is there something else >> going on here? Any thoughts as to why the two ports behave differently? >> > > This is automatically passed from earlier bootcode, but as long as > this code isn't compiled for uart1 it setups uart0. > Previously the kernel default was 9600, but it seems this has changed. > If you use boot2 with serial you need to recompile and reinstall it > with BOOT_COMCONSOLE_PORT and BOOT_COMCONSOLE_SPEED setup. > You need to recompile loader with at least BOOT_COMCONSOLE_PORT to > handle a different port instead, but you can change the speed with > comconsole_speed in loader.conf - nevertheless the default is also > set with BOOT_COMCONSOLE_SPEED at compiletime. > You should have at least the loader on serial as well - otherwise > you can't change boot parameters or boot another kernel. > I even prefer running boot2 on serial so I can switch loader in case > something breaks loader with an update. > That's helpful, thanks. The funny thing is that, with some systems (VMware, for example), both ports stay at 9600 baud (unlike this Intel server I'm wrestling with). Makes me think that maybe there's some kind of capabilities negotiation going on between the hardware and the driver. In any case, you've confirmed some things for me that hadn't quite sunk in. Thanks, Charles From owner-freebsd-hardware@FreeBSD.ORG Tue Mar 16 20:19:41 2010 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 5D8CD106564A for ; Tue, 16 Mar 2010 20:19:41 +0000 (UTC) (envelope-from lists@oyam.ca) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 3E9C38FC1B for ; Tue, 16 Mar 2010 20:19:40 +0000 (UTC) Received: by pwj4 with SMTP id 4so328174pwj.13 for ; Tue, 16 Mar 2010 13:19:40 -0700 (PDT) Received: by 10.114.119.12 with SMTP id r12mr2639wac.386.1268769016055; Tue, 16 Mar 2010 12:50:16 -0700 (PDT) Received: from [192.168.167.128] (a221-smpafs01.blockb-142.stargate.ca [208.118.142.221]) by mx.google.com with ESMTPS id 22sm1504718pzk.1.2010.03.16.12.50.14 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 16 Mar 2010 12:50:15 -0700 (PDT) Sender: Mayo Jordanov From: Mayo Jordanov Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 16 Mar 2010 12:50:13 -0700 Message-Id: To: freebsd-hardware@freebsd.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: read timeouts on a drive 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, 16 Mar 2010 20:19:41 -0000 Hello, I'm hitting some problems with a Toshiba drive (MK3263GSX).=20 When I boot from a cd during installation, it installs on it fine, and = there are no issues or errors on the consoles. When it comes to booting from the drive, it's geometry is detected as 0 = sectors, 0 heads, 0 cylynders, 0 mb and of course failts to boot. = (Geometry during install is correct). If I then boot off a cd or usb and = mount the drive, it works just fine, and everything from the = installation is on it, similarly copy to/from the drive is fine as well. I've had other OS installed on the drive (same system) no problem, and = it seems it's only having issues on FreeBSD during boot. Any ideas, = pointers? I don't know if it makes any difference, but the CD I install = from is a USB cdrom. I've also tried playing with ata timeouts, but it = didn't seem to help. There is no raid involved. I have two machines like = this, and both behave identically. The errors from dmesg during boot are: ad0: 0MB at ata0-master SATA150 ad0: FAILURE - READ_DMA48 status=3D51 = error=3D10 LBA=3D18446744073709551613 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551613 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551599 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551612 ad0: FAILURE - READ_DMA status=3D51 = error=3D10 LBA=3D18446744073709551615 ad0: FAILURE - READ_DMA48 status=3D51 = error=3D10 LBA=3D18446744073709551553 Thank you, Mayo Jordanov= From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 17 15:27:54 2010 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 99FF01065679 for ; Wed, 17 Mar 2010 15:27:54 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6A84D8FC19 for ; Wed, 17 Mar 2010 15:27:54 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 17E9B46B7E; Wed, 17 Mar 2010 11:27:54 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 4B33C8A025; Wed, 17 Mar 2010 11:27:53 -0400 (EDT) From: John Baldwin To: Charles Owens Date: Wed, 17 Mar 2010 11:14:11 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <4B75AB2D.2090306@greatbaysoftware.com> <201002191315.13796.jhb@freebsd.org> <4B9E928B.2070409@greatbaysoftware.com> In-Reply-To: <4B9E928B.2070409@greatbaysoftware.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201003171114.11601.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 17 Mar 2010 11:27:53 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-hardware@freebsd.org Subject: Re: mptutil(8) segfault on IBM xSeries 3550 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, 17 Mar 2010 15:27:54 -0000 On Monday 15 March 2010 4:03:23 pm Charles Owens wrote: > John Baldwin wrote: > > On Friday 19 February 2010 1:01:38 pm Charles Owens wrote: > > > >> John Baldwin wrote: > >> > >>> On Monday 15 February 2010 5:25:15 pm Charles Owens wrote: > >>> > >>>> Charles Owens wrote: > >>>> > >>>>> Howdy, > >>>>> > >>>>> We're working with IBM hardware (xSeries 3550) that has an > >>>>> mpt-based RAID controller... after initial success with testing the > >>>>> mptutil utility, now operations other than "show adapter" and "show > >>>>> volume" are resulting in segfaults. > >>>>> > >>>>> While it was working properly we created and removed volumes several > >>>>> times, force-failed drives, and just generally put it through its > >>>>> paces... and all seemed fine. Then, after a reboot, it suddenly started > >>>>> failing with segfault as described, and nothing we do has helped to get > >>>>> it out of this state (including trying to use the LSI in-BIOS manager to > >>>>> create/delete volumes -- which in and of itself works fine). > >>>>> > >>>>> We found recent thread > >>>>> http://docs.freebsd.org/cgi/mid.cgi?4B56CD4C.80503 and hoped that it > >>>>> might somehow relate... and even tried the patch that John Baldwin > >>>>> posted, but to no avail. > >>>>> > >>>>> Has anyone seen this behavior and/or have a suggested fix or workaround? > >>>>> > >>>>> > >>>>> Here's the output of "mptutil show adapter": > >>>>> > >>>>> mpt0 Adapter: > >>>>> Board Name: SR-BR10i > >>>>> Board Assembly: L3-25116-01H > >>>>> Chip Name: C1068E > >>>>> Chip Revision: UNUSED > >>>>> RAID Levels: RAID0, RAID1, RAID1E > >>>>> RAID0 Stripes: 64K > >>>>> RAID1E Stripes: 64K > >>>>> RAID0 Drives/Vol: 1-10 > >>>>> RAID1 Drives/Vol: 2 > >>>>> RAID1E Drives/Vol: 3-10 > >>>>> > >>>>> > >>>>> This work is being done using FreeBSD 8.0-RELEASE-p2 + PAE. > >>>>> > >>>>> > >>>> I should add that the RAID controller in question is the IBM > >>>> ServeRAID-BR10i SAS/SATA Controller which is based on the LSI 1068E > >>>> processor, as described here: > >>>> http://www-01.ibm.com/common/ssi/rep_ca/4/872/ENUSAG09-0104/index.html > >>>> > >>> Try this updated patch. It should fix the problems with 'mptutil show drives' > >>> displaying all daX devices in the system rather than just the ones for the > >>> mptX bus. I had incorrectly interpreted the XPT matches as being an AND > >>> rather than an OR. This changes the code to first do a lookup for the logical > >>> "path" (SCSI bus) for mptX devices and then do a second lookup to fetch any > >>> daX devices on that path. I tested it on a machine with an mpt controller and > >>> a USB disk. Unfortunately I wasn't able to test any of the RAID stuff, just > >>> 'show drives'. This mpt(4) controller doesn't support RAID either, so I was > >>> also able to verify the fix you had already tested for cleaning up 'show > >>> adapter' output in that case. > >>> > >>> [patch omitted] > >>> > >> John, > >> > >> The patch appears to have resolved the problem. We're still banging on > >> it, but so far it looks very good! > >> > >> Thanks very much! > >> > > > > Excellent, thanks! I've committed it to HEAD and will MFC it in a week or > > so. It is probably too late to make 7.3 however. > > > > Again, thanks for the patch... overall it is working well... we're now > able to successively do what we need to do with RAID system. We are, > though, seeing some sor of error messages: > > # mptutil show volumes > mpt0 Volumes: > Id Size Level Stripe State Write-Cache Name > mptutil: mpt_query_disk got 4 matches, expected 2 > 0 ( 279G) RAID-1 OPTIMAL Disabled > > # mptutil show config > mpt0 Configuration: 1 volumes, 2 drives > mptutil: mpt_query_disk got 4 matches, expected 2 > volume 0 (279G) RAID-1 OPTIMAL spans: > drive 1 (279G) ONLINE SATA > drive 0 (279G) ONLINE SATA > spare pools: 0 Are you sure this is a fixed binary? The new binary doesn't print out that message anymore, it only ways 'got %d matches, expected 1'. Also, the 4 instead of 2 is consistent with the old bug in that the two Linux virtual floppies (da1 and da2) would be reported as extra for 'mptutil show drives' in this case I think. > We can certainly live with this, but I wanted to let you know in case > you thought it was worth digging into. Let me know if you need any > additional debug info beyond this: > > # camcontrol devlist > at scbus0 target 0 lun 0 (pass0,da0) > at scbus1 target 1 lun 0 (pass1) > at scbus2 target 0 lun 0 (pass2,cd0) > at scbus3 target 0 lun 0 (da1,pass3) > at scbus3 target 0 lun 1 (da2,pass4) -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 17 15:27:55 2010 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 C76F6106564A for ; Wed, 17 Mar 2010 15:27:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 983C78FC0A for ; Wed, 17 Mar 2010 15:27:55 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 4A94446B81; Wed, 17 Mar 2010 11:27:55 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 439A58A01F; Wed, 17 Mar 2010 11:27:54 -0400 (EDT) From: John Baldwin To: agh@coolrhaug.com Date: Wed, 17 Mar 2010 11:23:03 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <201002212231.12018.agh@coolrhaug.com> <201003011154.00827.jhb@freebsd.org> <201003162122.28370.agh@coolrhaug.com> In-Reply-To: <201003162122.28370.agh@coolrhaug.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201003171123.03817.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 17 Mar 2010 11:27:54 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: kochetkov.andrew@gmail.com, Randy Chou , freebsd-hardware@freebsd.org Subject: Re: Intel DP45SG motherboard problem (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: Wed, 17 Mar 2010 15:27:55 -0000 On Tuesday 16 March 2010 9:22:28 am Alastair Hogge wrote: > On Tue March 2 2010 00:54:00 John Baldwin wrote: > > This would not change acpidump output, just the kernel. Are you able to > > capture the boot messages with this kernel? > Full log: > http://codepad.org/96PT5OO8 Oh! ACPI is working, but the MADT is not so it's trying to mix and match mptable (for SMP) with ACPI. Odd that you didn't get a warning message about the checksum failing from boot -v. Try this patch: Index: amd64/acpica/acpi_machdep.c =================================================================== --- amd64/acpica/acpi_machdep.c (revision 205249) +++ amd64/acpica/acpi_machdep.c (working copy) @@ -627,8 +627,10 @@ if (ACPI_FAILURE(AcpiTbChecksum(table, length))) { if (bootverbose) printf("ACPI: Failed checksum for table %s\n", sig); +#if (ACPI_CHECKSUM_ABORT) table_unmap(table, length); return (NULL); +#endif } return (table); } Index: i386/acpica/acpi_machdep.c =================================================================== --- i386/acpica/acpi_machdep.c (revision 205249) +++ i386/acpica/acpi_machdep.c (working copy) @@ -641,8 +641,10 @@ if (ACPI_FAILURE(AcpiTbChecksum(table, length))) { if (bootverbose) printf("ACPI: Failed checksum for table %s\n", sig); +#if (ACPI_CHECKSUM_ABORT) table_unmap(table, length); return (NULL); +#endif } return (table); } -- John Baldwin From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 17 15:57:55 2010 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 15B251065670 for ; Wed, 17 Mar 2010 15:57:55 +0000 (UTC) (envelope-from mayo@oyam.ca) Received: from mail-yx0-f185.google.com (mail-yx0-f185.google.com [209.85.210.185]) by mx1.freebsd.org (Postfix) with ESMTP id D61398FC13 for ; Wed, 17 Mar 2010 15:57:54 +0000 (UTC) Received: by yxe15 with SMTP id 15so558500yxe.7 for ; Wed, 17 Mar 2010 08:57:54 -0700 (PDT) MIME-Version: 1.0 Sender: mayo@oyam.ca Received: by 10.101.184.29 with SMTP id l29mr1447374anp.55.1268841473917; Wed, 17 Mar 2010 08:57:53 -0700 (PDT) Date: Wed, 17 Mar 2010 08:57:53 -0700 X-Google-Sender-Auth: ccbec50df3dee2d3 Message-ID: <2dd037201003170857u621dec6fka8b8e2d7df145c4f@mail.gmail.com> From: Mayo Jordanov To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Problems with drive 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, 17 Mar 2010 15:57:55 -0000 Hello, I'm hitting some problems with a Toshiba drive (MK3263GSX). When I boot from a cd during installation, it installs on it fine, and there are no issues or errors on the consoles. When it comes to booting from the drive, it's geometry is detected as 0 sectors, 0 heads, 0 cylynders, 0 mb and of course failts to boot. (Geometry during install is correct). If I then boot off a cd or usb and mount the drive, it works just fine, and everything from the installation is on it, similarly copy to/from the drive is fine as well. I've had other OS installed on the drive (same system) no problem, and it seems it's only having issues on FreeBSD during boot. Any ideas, pointers? I don't know if it makes any difference, but the CD I install from is a USB cdrom. I've also tried playing with ata timeouts, but it didn't seem to help. There is no raid involved. I have two machines like this, and both behave identically. The errors from dmesg during boot are: ad0: 0MB at ata0-master SATA150 ad0: FAILURE - READ_DMA48 status=51 error=10 LBA=18446744073709551613 ad0: FAILURE - READ_DMA status=51 error=10 LBA=18446744073709551613 ad0: FAILURE - READ_DMA status=51 error=10 LBA=18446744073709551599 ad0: FAILURE - READ_DMA status=51 error=10 LBA=18446744073709551612 ad0: FAILURE - READ_DMA status=51 error=10 LBA=18446744073709551615 ad0: FAILURE - READ_DMA48 status=51 error=10 LBA=18446744073709551553 Thank you, Mayo Jordanov From owner-freebsd-hardware@FreeBSD.ORG Wed Mar 17 20:43:14 2010 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 D7AC91065672; Wed, 17 Mar 2010 20:43:14 +0000 (UTC) (envelope-from cowens@greatbaysoftware.com) Received: from portcityhosting.com (bayringfw.portcityweb.com [64.140.243.92]) by mx1.freebsd.org (Postfix) with ESMTP id 7D43D8FC0C; Wed, 17 Mar 2010 20:43:13 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Wed, 17 Mar 2010 16:43:12 -0400 Message-ID: <4BA13EDF.8040909@greatbaysoftware.com> Date: Wed, 17 Mar 2010 16:43:11 -0400 From: Charles Owens MIME-Version: 1.0 To: John Baldwin References: <4B75AB2D.2090306@greatbaysoftware.com> <201002191315.13796.jhb@freebsd.org> <4B9E928B.2070409@greatbaysoftware.com> <201003171114.11601.jhb@freebsd.org> In-Reply-To: <201003171114.11601.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-WatchGuard-AntiVirus: part scanned. clean action=allow X-ME-Bayesian: 0.000000 Cc: freebsd-hardware@freebsd.org Subject: Re: mptutil(8) segfault on IBM xSeries 3550 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, 17 Mar 2010 20:43:14 -0000 On 3/17/2010 11:14 AM, John Baldwin wrote: > On Monday 15 March 2010 4:03:23 pm Charles Owens wrote: > >> John Baldwin wrote: >> >>> On Friday 19 February 2010 1:01:38 pm Charles Owens wrote: >>> >>> >>>> John Baldwin wrote: >>>> >>>> >>>>> On Monday 15 February 2010 5:25:15 pm Charles Owens wrote: >>>>> >>>>> >>>>>> Charles Owens wrote: >>>>>> >>>>>> >>>>>>> Howdy, >>>>>>> >>>>>>> We're working with IBM hardware (xSeries 3550) that has an >>>>>>> mpt-based RAID controller... after initial success with testing the >>>>>>> mptutil utility, now operations other than "show adapter" and "show >>>>>>> volume" are resulting in segfaults. >>>>>>> >>>>>>> While it was working properly we created and removed volumes several >>>>>>> times, force-failed drives, and just generally put it through its >>>>>>> paces... and all seemed fine. Then, after a reboot, it suddenly >>>>>>> > started > >>>>>>> failing with segfault as described, and nothing we do has helped to >>>>>>> > get > >>>>>>> it out of this state (including trying to use the LSI in-BIOS manager >>>>>>> > to > >>>>>>> create/delete volumes -- which in and of itself works fine). >>>>>>> >>>>>>> We found recent thread >>>>>>> http://docs.freebsd.org/cgi/mid.cgi?4B56CD4C.80503 and hoped that it >>>>>>> might somehow relate... and even tried the patch that John Baldwin >>>>>>> posted, but to no avail. >>>>>>> >>>>>>> Has anyone seen this behavior and/or have a suggested fix or >>>>>>> > workaround? > >>>>>>> >>>>>>> Here's the output of "mptutil show adapter": >>>>>>> >>>>>>> mpt0 Adapter: >>>>>>> Board Name: SR-BR10i >>>>>>> Board Assembly: L3-25116-01H >>>>>>> Chip Name: C1068E >>>>>>> Chip Revision: UNUSED >>>>>>> RAID Levels: RAID0, RAID1, RAID1E >>>>>>> RAID0 Stripes: 64K >>>>>>> RAID1E Stripes: 64K >>>>>>> RAID0 Drives/Vol: 1-10 >>>>>>> RAID1 Drives/Vol: 2 >>>>>>> RAID1E Drives/Vol: 3-10 >>>>>>> >>>>>>> >>>>>>> This work is being done using FreeBSD 8.0-RELEASE-p2 + PAE. >>>>>>> >>>>>>> >>>>>>> >>>>>> I should add that the RAID controller in question is the IBM >>>>>> ServeRAID-BR10i SAS/SATA Controller which is based on the LSI 1068E >>>>>> processor, as described here: >>>>>> http://www-01.ibm.com/common/ssi/rep_ca/4/872/ENUSAG09-0104/index.html >>>>>> >>>>>> >>>>> Try this updated patch. It should fix the problems with 'mptutil show >>>>> > drives' > >>>>> displaying all daX devices in the system rather than just the ones for >>>>> > the > >>>>> mptX bus. I had incorrectly interpreted the XPT matches as being an AND >>>>> rather than an OR. This changes the code to first do a lookup for the >>>>> > logical > >>>>> "path" (SCSI bus) for mptX devices and then do a second lookup to fetch >>>>> > any > >>>>> daX devices on that path. I tested it on a machine with an mpt >>>>> > controller and > >>>>> a USB disk. Unfortunately I wasn't able to test any of the RAID stuff, >>>>> > just > >>>>> 'show drives'. This mpt(4) controller doesn't support RAID either, so I >>>>> > was > >>>>> also able to verify the fix you had already tested for cleaning up 'show >>>>> adapter' output in that case. >>>>> >>>>> [patch omitted] >>>>> >>>>> >>>> John, >>>> >>>> The patch appears to have resolved the problem. We're still banging on >>>> it, but so far it looks very good! >>>> >>>> Thanks very much! >>>> >>>> >>> Excellent, thanks! I've committed it to HEAD and will MFC it in a week or >>> so. It is probably too late to make 7.3 however. >>> >>> >> Again, thanks for the patch... overall it is working well... we're now >> able to successively do what we need to do with RAID system. We are, >> though, seeing some sor of error messages: >> >> # mptutil show volumes >> mpt0 Volumes: >> Id Size Level Stripe State Write-Cache Name >> mptutil: mpt_query_disk got 4 matches, expected 2 >> 0 ( 279G) RAID-1 OPTIMAL Disabled >> >> # mptutil show config >> mpt0 Configuration: 1 volumes, 2 drives >> mptutil: mpt_query_disk got 4 matches, expected 2 >> volume 0 (279G) RAID-1 OPTIMAL spans: >> drive 1 (279G) ONLINE SATA >> drive 0 (279G) ONLINE SATA >> spare pools: 0 >> > Are you sure this is a fixed binary? The new binary doesn't print out that > message anymore, it only ways 'got %d matches, expected 1'. Also, the 4 > instead of 2 is consistent with the old bug in that the two Linux virtual > floppies (da1 and da2) would be reported as extra for 'mptutil show drives' in > this case I think. You're right! It appears on one of my two devel systems I misapplied the patch somehow. Much better now... thanks! From owner-freebsd-hardware@FreeBSD.ORG Thu Mar 18 16:12:01 2010 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 8D4C6106566B for ; Thu, 18 Mar 2010 16:12:01 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f224.google.com (mail-fx0-f224.google.com [209.85.220.224]) by mx1.freebsd.org (Postfix) with ESMTP id 1CF318FC21 for ; Thu, 18 Mar 2010 16:12:00 +0000 (UTC) Received: by fxm24 with SMTP id 24so1734207fxm.3 for ; Thu, 18 Mar 2010 09:12:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=8Os8qDstdhscL/GQn6vO+XYTOOiWxAiw2I7O4i+wBEs=; b=cd6RQOkBs/jdNkuSIf4R+PZnCQoSB8cjNpedMbzF2N69H+eoadKV9oGC9O94Ydg2Au v6SUgkMYeWbs44GAOIh8PXNJuDRTFmB3fxbdMvH+Am0jC58+nD2817tOz7J/scOv+Xza cY1unU0+uMhvM3XicnIrWW6UJ7lR6l5qsGVqQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ECz2G/jx9dZI4nY9ExV6TykmLt4Ve9CKy1KkXp6GGCczY6NWig7dxKkcFFABrCpStb 1qNv8cnv5gNnJSpwZRf2RdT06x+je9v1+Lth88NwE3gBYkjKboGxzpuIi5nNvSHfoNvF /oDaCE74JIuWaP0cPLx8fqP0mDidK0+VtoBA4= Received: by 10.223.18.132 with SMTP id w4mr1776677faa.30.1268928719727; Thu, 18 Mar 2010 09:11:59 -0700 (PDT) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 15sm105733fxm.8.2010.03.18.09.11.58 (version=SSLv3 cipher=RC4-MD5); Thu, 18 Mar 2010 09:11:59 -0700 (PDT) Sender: Alexander Motin Message-ID: <4BA250CD.1050301@FreeBSD.org> Date: Thu, 18 Mar 2010 18:11:57 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: freebsd@sopwith.solgatos.com References: <1268122982.00227551.1268112003@10.7.7.3> In-Reply-To: <1268122982.00227551.1268112003@10.7.7.3> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: siis(4) questions 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, 18 Mar 2010 16:12:01 -0000 Dieter wrote: > The siis(4) man page promises a ada(4) man page, but > I can't find it. Even tried the online man page tool. > > dmesg says: > > ada0 at siisch0 bus 0 target 0 lun 0 > ada0: ATA/ATAPI-8 SATA 2.x device > ada0: 300.000MB/s transfers > ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) > ada0: Native Command Queueing enabled Looking on this you are probably using 8.0-RELEASE or quite old 8-STABLE. Try to update your system. -- Alexander Motin