From owner-freebsd-hardware@FreeBSD.ORG Sun Nov 22 02:44:06 2009 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 79F3A106566C for ; Sun, 22 Nov 2009 02:44:06 +0000 (UTC) (envelope-from rebotados@exemys.com) Received: from web.hostmailing.com (web.hostmailing.com [200.110.145.34]) by mx1.freebsd.org (Postfix) with ESMTP id 881008FC19 for ; Sun, 22 Nov 2009 02:44:05 +0000 (UTC) Received: from web.hostmailing.com ([200.110.145.34] helo=www.hostmailing.com) by web.hostmailing.com with esmtpa (Exim 4.63) (envelope-from ) id 1NC2Kf-0004XP-Kh for freebsd-hardware@freebsd.org; Sat, 21 Nov 2009 23:37:45 -0300 Date: Sat, 21 Nov 2009 23:37:45 -0300 To: freebsd-hardware@freebsd.org From: Exemys Message-ID: <35b847f35e5c94844d073655cec88ea7@www.hostmailing.com> X-Priority: 3 X-Mailer: wh4535 [version 4.1] X-Fid: eGZpZC1mcmVlYnNkLWhhcmR3YXJlQGZyZWVic2Qub3JnLTIzMjc0LTczMTgtNjg2MQ== MIME-Version: 1.0 Content-Type: text/plain; charset = "iso-8859-1" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Pulse Meter with Cellular communication X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: exemys@exemys.com List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2009 02:44:06 -0000 This is a message in multipart MIME format. Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly. From owner-freebsd-hardware@FreeBSD.ORG Mon Nov 23 16:46:12 2009 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 6B163106566C for ; Mon, 23 Nov 2009 16:46:12 +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 20E408FC14 for ; Mon, 23 Nov 2009 16:46:11 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Mon, 23 Nov 2009 11:46:08 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4B0ABD27.2080501@greatbaysoftware.com> Date: Mon, 23 Nov 2009 11:49:43 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@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 Subject: No "boot0" menu on Soekris, net5501 vs net4521 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, 23 Nov 2009 16:46:12 -0000 Hello, We're working with two different Soekris models (net5501 and net4521), working withFreeBSD 7.1 (nanobsd). We've found that the two models exhibit different boot behavior. Summary: the 4521 works fine, and the 5501 doesn't seem right. Here's what we see when we boot either: net4521 (BIOS ver 1.33) -- * "boot0" menu appears (letting you pick either of two FreeBSD slices) * OS loads properly from chosen or default slice net5501 (BIOS ver 1.33c) -- * "boot0" menu does _not_ appear. * system boots directly to slice 1 or 2, as chosen via BIOS option BootPartition Have others seen this behavior? For our application, we really need the 5501 to boot just like the 4521. Is this a bug (in BIOS, I'm guessing), or am I doing something wrong? It seems like there should be a way to clear the BootPartition setting, or set it to "MBR" or somesuch. Thanks very much, Charles -- **Charles Owens** *Great Bay Software******* From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 24 05:14:34 2009 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 BD011106566B for ; Tue, 24 Nov 2009 05:14:34 +0000 (UTC) (envelope-from freebsd@sopwith.solgatos.com) Received: from sopwith.solgatos.com (pool-98-108-131-11.ptldor.fios.verizon.net [98.108.131.11]) by mx1.freebsd.org (Postfix) with ESMTP id 329AA8FC08 for ; Tue, 24 Nov 2009 05:14:30 +0000 (UTC) Received: by sopwith.solgatos.com (Postfix, from userid 66) id 84ED2B64F; Mon, 23 Nov 2009 20:56:11 -0800 (PST) Received: from localhost by sopwith.solgatos.com (8.8.8/6.24) id CAA21330; Tue, 24 Nov 2009 02:57:51 GMT Message-Id: <200911240257.CAA21330@sopwith.solgatos.com> To: freebsd-hardware@freebsd.org In-reply-to: Your message of "Tue, 17 Nov 2009 12:34:38 +0200." <4B027C3E.7020700@FreeBSD.org> Date: Mon, 23 Nov 2009 18:57:51 PST From: Dieter Subject: PCIe-x1 SATA controllers (was: Re: Adaptec 1405 on FreeBSD ) 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, 24 Nov 2009 05:14:34 -0000 In message <4B027C3E.7020700@FreeBSD.org>, Alexander Motin writes: > >>>>> - SiI3124-based - fast and functional. It is actually PCI-X one, but > >>>>> there are many boards with built-in PCIe bridges. > >>> Do any of these fit in a x1 slot? > >> I was surprised, but yes. > > > > My google-fu fails me. Any make/model, URLs, or keywords? > > Syba PCI Express SATA II 4 x Ports RAID Controller Card SY-PEX40008 Does anyone other than Syba make these? I'm a bit leery of Syba after my experience with some of their other fine products. Reviews on newegg say it "Gets a bit hot" and "gets quite hot under load", despite that big heatsink. http://www.newegg.com/Product/ProductReview.aspx?Item=N82E16816124027 ---------- > The interesting fact I have seen yesterday, SiI3132 is able to read > 150MB/s, but write 170MB/s. I am not PCIe expert, but looks like > transfer capabilities could be asymmetric. Also, and as soon as PCIe is > duplex, I've also seen 110MB/s read from one drive, plus 100MB/s write > to another, running at the same time. Seems odd. ---------- >From what I can see, FreeBSD does not support the Marvell 88SE61xx SATA controllers? For example, the SATA2-PCIE1x12 has 4 SATA ports + 1 PATA channel, for US$30.13 http://www.span.com/product_info.php?cPath=24_714_2502&products_id=16957 There is a similar SATA2-PCIE1X11 board with all ports internal. http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets points to a patch for OpenBSD: http://www.webservertalk.com/message2133676.html and apparently penguinix supports them. ---------- Then we have this oddball, 2 SATA-300 ports + 2 SATA-150 ports: SYBA SY-PEX40013 http://www.newegg.com/Product/Product.aspx?Item=N82E16816124029 From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 24 09:00:15 2009 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 46B54106566B for ; Tue, 24 Nov 2009 09:00:15 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-bw0-f220.google.com (mail-bw0-f220.google.com [209.85.218.220]) by mx1.freebsd.org (Postfix) with ESMTP id C79B78FC0A for ; Tue, 24 Nov 2009 09:00:14 +0000 (UTC) Received: by bwz20 with SMTP id 20so4745071bwz.14 for ; Tue, 24 Nov 2009 01:00:13 -0800 (PST) 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=ynSOuqK5WLDjXVPdr+fZN8nhu5vup65Mok5TNtOL/Tg=; b=TgJ1kRliFBjeimFO0HjM3FnBztp7QEryZoOqW1z/7AyW7QVw6UinRYhxw6sSIJ7GXe m5EQtGsTHE1YVVj3gcAavMEVBS4KL0y1tLu203+EAllWiFLHMnBJzEcvEkBFw4hYLNN4 nfZhHrfaxue9/FluJnotzlFBT4CBzkmkv2zaQ= 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=SrmfS/EuOad+/NuF4VGnz8N7crYHprvgE/SghChlp8SPLyqAsIUt0mwxXjkOnbedqb XICWEidHDl7P1IkGNvqD0IEi9T/oJEs0uV5akCkxFl7Jlh6DDD3eL0vbfF4GJAuaGxx/ uamJtZyvk85yPWVzlM8HfhHHc9GFhFdfzdMvY= Received: by 10.204.157.26 with SMTP id z26mr3048343bkw.124.1259053213687; Tue, 24 Nov 2009 01:00:13 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 15sm1695660fxm.6.2009.11.24.01.00.12 (version=SSLv3 cipher=RC4-MD5); Tue, 24 Nov 2009 01:00:13 -0800 (PST) Sender: Alexander Motin Message-ID: <4B0BA09A.2070301@FreeBSD.org> Date: Tue, 24 Nov 2009 11:00:10 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Dieter References: <1259050982.00186650.1259040002@10.7.7.3> In-Reply-To: <1259050982.00186650.1259040002@10.7.7.3> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-hardware@freebsd.org Subject: Re: PCIe-x1 SATA controllers (was: Re: Adaptec 1405 on FreeBSD ) 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, 24 Nov 2009 09:00:15 -0000 Dieter wrote: >>From what I can see, FreeBSD does not support the Marvell 88SE61xx > SATA controllers? > > For example, the SATA2-PCIE1x12 has 4 SATA ports + 1 PATA channel, > for US$30.13 > http://www.span.com/product_info.php?cPath=24_714_2502&products_id=16957 > There is a similar SATA2-PCIE1X11 board with all ports internal. > > http://en.wikipedia.org/wiki/List_of_Marvell_Technology_Group_chipsets > points to a patch for OpenBSD: > http://www.webservertalk.com/message2133676.html > and apparently penguinix supports them. I have merged support for 88SE61xx SATA to 8-STABLE last days. I have no plans to merge it lower. -- Alexander Motin From owner-freebsd-hardware@FreeBSD.ORG Tue Nov 24 17:53:31 2009 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 B58A1106568F for ; Tue, 24 Nov 2009 17:53:31 +0000 (UTC) (envelope-from korvus@comcast.net) Received: from QMTA13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [76.96.59.243]) by mx1.freebsd.org (Postfix) with ESMTP id 64CC78FC13 for ; Tue, 24 Nov 2009 17:53:31 +0000 (UTC) Received: from OMTA14.westchester.pa.mail.comcast.net ([76.96.62.60]) by QMTA13.westchester.pa.mail.comcast.net with comcast id 91851d01g1HzFnQ5D5gGTF; Tue, 24 Nov 2009 17:40:16 +0000 Received: from [192.168.2.164] ([206.210.89.202]) by OMTA14.westchester.pa.mail.comcast.net with comcast id 95g31d0034Mx3R23a5g5lE; Tue, 24 Nov 2009 17:40:14 +0000 Message-ID: <4B0C1A72.3000301@comcast.net> Date: Tue, 24 Nov 2009 12:40:02 -0500 From: Steve Polyack User-Agent: Thunderbird 2.0.0.23 (X11/20090902) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org, freebsd-stable , freebsd-geom@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Panic possibly related to glabel/geom and siis(4) 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, 24 Nov 2009 17:53:31 -0000 I have a system running 8.0-PRERELEASE with multiple drives and SATA port multipliers (siis controllers and PMPs). All of the attached drives are labeled via glabel(8) and then included into a ZFS pool. During some testing to determine how the system would react to a dead drive (simulated by physically removing a drive during operation), I was able to produce a panic. Now, I know that the SATA PMP and siis(4) code to handle and recover from device errors is incomplete, but I believe the crash may be particular to using glabel'd drives. Basically, after removing a drive while the zpool is in use and issues 'camcontrol reset' and 'rescan' on the appropriate bus, the physical device associated with the drive disappears. In this case: (pass5:siisch7:0:15:0): lost device (pass5:siisch7:0:15:0): removing device entry (ada2:siisch7:0:0:0): lost device and /dev/ada2 disappears. However, the associated glabel /dev/label/bigdisk07 remains. Since my ZFS pool is created based on the drive glabels, I believe this is why ZFS never notices the drives disappear either. Do glabels typically go away after a physical device is lost? Should this not be the case? After some runtime with the physical device missing, a kernel panic is produced: ada2:siisch7:0:0:0): Synchronize cache failed (ada2:siisch7:0:0:0): removing device entry Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 14 fault virtual address = 0x48 fault code = supervisor write data, page not present instruction pointer = 0x20:0xffffffff8035f375 stack pointer = 0x28:0xffffff800006db60 frame pointer = 0x28:0xffffff800006db70 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 2 (g_event) [thread pid 2 tid 100014 ] Stopped at _mtx_lock_flags+0x15: lock cmpxchgq %rsi,0x18(%rdi) db> bt Tracing pid 2 tid 100014 td 0xffffff00014d4ab0 _mtx_lock_flags() at _mtx_lock_flags+0x15 vdev_geom_release() at vdev_geom_release+0x33 vdev_geom_orphan() at vdev_geom_orphan+0x15c g_run_events() at g_run_events+0x104 g_event_procbody() at g_event_procbody+0x55 fork_exit() at fork_exit+0x118 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff800006dd30, rbp = 0 --- I'm open to try patches and other suggestions. Thanks. From owner-freebsd-hardware@FreeBSD.ORG Wed Nov 25 11:24:42 2009 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 9D74C106568D for ; Wed, 25 Nov 2009 11:24:42 +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 3B1A98FC22 for ; Wed, 25 Nov 2009 11:24:41 +0000 (UTC) Received: from [127.0.0.1] ([173.14.128.81]) by portcityhosting.com with MailEnable ESMTP; Wed, 25 Nov 2009 06:24:37 -0500 X-WatchGuard-Mail-Exception: Allow Message-ID: <4B0D14CB.1010000@greatbaysoftware.com> Date: Wed, 25 Nov 2009 06:28:11 -0500 From: Charles Owens MIME-Version: 1.0 To: freebsd-hardware@freebsd.org References: <4B070F07.8010600@greatbaysoftware.com> In-Reply-To: <4B070F07.8010600@greatbaysoftware.com> 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: Re: USB keyboard flaky with PAE kernel, 7.1 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, 25 Nov 2009 11:24:42 -0000 Charles Owens wrote: > Howdy, > > I'm still digging into it, put preliminary testing is showing that with > a PAE-enabled 7.1-RELEASE-p8 kernel a USB keyboard functions only > occasionally, if you're lucky. This flakiness is being seen with > several different server models that we support (HP and IBM, all Xeon > based). If we boot a non-PAE kernel then the USB keyboard is rock solid. > > For what it's worth (probably little) I can run the same PAE kernel on > an old Pentium II system and a USB keyboard works fine. > > What is the best way to dig into this? Any and all assistance greatly > appreciated. I can provide remote access to a testbed of these systems > if useful. > Following is some detail for one of the systems, an IBM System x3550 M2. >From dmidecode: System Information Manufacturer: IBM Product Name: IBM System x -[7946AC1]- Version: 00 [root@dmz55 ~]# usbdevs -v Controller /dev/usb0: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 addr 2: low speed, power 100 mA, config 1, Comfort Curve Keyboard 2000(0x00dd), Microsoft(0x045e), rev 1.73 Controller /dev/usb1: addr 1: full speed, self powered, config 1, UHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered Controller /dev/usb2: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 powered port 2 powered port 3 powered port 4 powered port 5 powered port 6 powered usbdevs: /dev/usb3: Input/output error usbdevs: /dev/usb4: Input/output error usbdevs: /dev/usb5: Input/output error Controller /dev/usb6: addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00 port 1 addr 2: high speed, power 2 mA, config 2, IBM Composite Device-0(0x4012), IBM(0x04b3), rev 0.00 port 2 powered port 3 powered port 4 powered port 5 powered port 6 addr 3: high speed, power 450 mA, config 1, product 0x1a00(0x1a00), vendor 0x2001(0x2001), rev 10.01 Copyright (c) 1992-2009 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.1-RELEASE-p8 #3: Thu Nov 19 15:24:03 EST 2009 muck@dmz55.greatbaysoftware.com:/usr/obj/usr/src/sys/DMZ55 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU E5504 @ 2.00GHz (2000.08-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Stepping = 5 Features=0xbfebfbff Features2=0x9ce3bd AMD Features=0x28100000 AMD Features2=0x1 Cores per package: 8 Logical CPUs per core: 2 real memory = 6442450944 (6144 MB) avail memory = 4150349824 (3958 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x588-0x58b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 28 at device 1.0 on pci0 pci11: on pcib1 pci11: at device 0.0 (no driver attached) pci11: at device 0.1 (no driver attached) pcib2: irq 29 at device 2.0 on pci0 pci16: on pcib2 pci16: at device 0.0 (no driver attached) pci16: at device 0.1 (no driver attached) pcib3: irq 24 at device 3.0 on pci0 pci21: on pcib3 pcib4: irq 30 at device 7.0 on pci0 pci26: on pcib4 pci0: at device 16.0 (no driver attached) pci0: at device 16.1 (no driver attached) pci0: at device 17.0 (no driver attached) pci0: at device 17.1 (no driver attached) pci0: at device 20.0 (no driver attached) pci0: at device 20.1 (no driver attached) pci0: at device 20.2 (no driver attached) pci0: at device 20.3 (no driver attached) pci0: at device 22.0 (no driver attached) pci0: at device 22.1 (no driver attached) pci0: at device 22.2 (no driver attached) pci0: at device 22.3 (no driver attached) pci0: at device 22.4 (no driver attached) pci0: at device 22.5 (no driver attached) pci0: at device 22.6 (no driver attached) pci0: at device 22.7 (no driver attached) uhci0: port 0x20a0-0x20bf irq 17 at device 26.0 on pci0 uhci0: [GIANT-LOCKED] uhci0: [ITHREAD] usb0: on uhci0 usb0: USB revision 1.0 uhub0: on usb0 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x2080-0x209f irq 18 at device 26.1 on pci0 uhci1: [GIANT-LOCKED] uhci1: [ITHREAD] usb1: on uhci1 usb1: USB revision 1.0 uhub1: on usb1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0x9ba21400-0x9ba217ff irq 19 at device 26.7 on pci0 ehci0: [GIANT-LOCKED] ehci0: [ITHREAD] usb2: EHCI version 1.0 usb2: wrong number of companions (3 != 2) usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: on usb2 uhub2: 6 ports with 6 removable, self powered pcib5: irq 16 at device 28.0 on pci0 pci1: on pcib5 mpt0: port 0x1000-0x10ff mem 0x9b910000-0x9b913fff,0x9b900000-0x9b90ffff irq 16 at device 0.0 on pci1 mpt0: [ITHREAD] mpt0: MPI Version=1.5.20.0 mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 ) mpt0: 0 Active Volumes (2 Max) mpt0: 0 Hidden Drive Members (14 Max) pcib6: irq 16 at device 28.4 on pci0 pci6: on pcib6 pcib7: irq 16 at device 0.0 on pci6 pci7: on pcib7 vgapci0: mem 0x9a000000-0x9affffff,0x9b800000-0x9b803fff,0x9b000000-0x9b7fffff irq 16 at device 0.0 on pci7 uhci2: port 0x2060-0x207f irq 17 at device 29.0 on pci0 uhci2: [GIANT-LOCKED] uhci2: [ITHREAD] usb3: on uhci2 usb3: USB revision 1.0 usb3: root hub problem, error=4 uhci3: port 0x2040-0x205f irq 18 at device 29.1 on pci0 uhci3: [GIANT-LOCKED] uhci3: [ITHREAD] usb4: on uhci3 usb4: USB revision 1.0 usb4: root hub problem, error=4 uhci4: port 0x2020-0x203f irq 19 at device 29.2 on pci0 uhci4: [GIANT-LOCKED] uhci4: [ITHREAD] usb5: on uhci4 usb5: USB revision 1.0 usb5: root hub problem, error=4 ehci1: mem 0x9ba21000-0x9ba213ff irq 17 at device 29.7 on pci0 ehci1: [GIANT-LOCKED] ehci1: [ITHREAD] usb6: EHCI version 1.0 usb6: companion controllers, 2 ports each: usb3 usb4 usb5 usb6: on ehci1 usb6: USB revision 2.0 uhub3: on usb6 uhub3: 6 ports with 6 removable, self powered ukbd0: on uhub3 kbd2 at ukbd0 uhid0: on uhub3 uhid1: on uhub3 umass0: on uhub3 umass1: on uhub3 axe0: on uhub3 axe0: AX88172, bufsz 1536, boundary 64 miibus0: on axe0 rlphy0: PHY 3 on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto axe0: WARNING: using obsoleted if_watchdog interface axe0: WARNING: using obsoleted IFF_NEEDSGIANT flag axe0: Ethernet address: 00:80:c8:38:15:ff pcib8: at device 30.0 on pci0 pci31: on pcib8 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x20f0-0x20ff,0x20e0-0x20ef irq 16 at device 31.2 on pci0 ata0: on atapci0 ata0: [ITHREAD] ata1: on atapci0 ata1: [ITHREAD] pci0: at device 31.3 (no driver attached) atapci1: port 0x2108-0x210f,0x2124-0x2127,0x2100-0x2107,0x2120-0x2123,0x20d0-0x20df,0x20c0-0x20cf irq 21 at device 31.5 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio0: [FILTER] sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A sio1: [FILTER] cpu0: on acpi0 est0: on cpu0 p4tcc0: on cpu0 cpu1: on acpi0 est1: on cpu1 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 p4tcc2: on cpu2 cpu3: on acpi0 est3: on cpu3 p4tcc3: on cpu3 cpu3: on acpi0 est3: on cpu3 p4tcc3: on cpu3 pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ukbd1: on uhub0 kbd3 at ukbd1 uhid2: on uhub0 Timecounters tick every 1.000 msec da0 at mpt0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-5 device da0: 300.000MB/s transfers da0: Command Queueing Enabled da0: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) cd0 at umass-sim0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 40.000MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present da1 at mpt0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-5 device da1: 300.000MB/s transfers da1: Command Queueing Enabled da1: 286102MB (585937500 512 byte sectors: 255H 63S/T 36472C) SMP: AP CPU #1 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #2 Launched! da2 at umass-sim1 bus 1 target 0 lun 0 da2: Removable Direct Access SCSI-0 device da2: 40.000MB/s transfers da2: Attempt to query device size failed: NOT READY, Medium not present da3 at umass-sim1 bus 1 target 0 lun 1 da3: Removable Direct Access SCSI-0 device da3: 40.000MB/s transfers da3: Attempt to query device size failed: NOT READY, Medium not present Trying to mount root from ufs:/dev/da0s1a Charles Owens Great Bay Software From owner-freebsd-hardware@FreeBSD.ORG Thu Nov 26 18:52:37 2009 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 EDD30106566C for ; Thu, 26 Nov 2009 18:52:37 +0000 (UTC) (envelope-from patpro@patpro.net) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5]) by mx1.freebsd.org (Postfix) with ESMTP id 6467D8FC17 for ; Thu, 26 Nov 2009 18:52:35 +0000 (UTC) Received: from smtp5-g21.free.fr (localhost [127.0.0.1]) by smtp5-g21.free.fr (Postfix) with ESMTP id 9F81FD48213 for ; Thu, 26 Nov 2009 19:52:32 +0100 (CET) Received: from boleskine.patpro.net (boleskine.patpro.net [82.230.142.222]) by smtp5-g21.free.fr (Postfix) with ESMTP id BD7C2D481E8 for ; Thu, 26 Nov 2009 19:52:29 +0100 (CET) Received: from [192.168.0.2] (unknown [192.168.0.2]) by boleskine.patpro.net (Postfix) with ESMTP id 1777D1CD0E for ; Thu, 26 Nov 2009 19:52:29 +0100 (CET) Message-Id: <97F2DB2A-6515-4B0F-9146-A2059748A8B3@patpro.net> From: Patrick Proniewski To: freebsd-hardware@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Thu, 26 Nov 2009 19:52:29 +0100 X-Mailer: Apple Mail (2.936) Subject: ATA check power status? 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, 26 Nov 2009 18:52:38 -0000 Hi all, I'm still playing with my WD Hard Drive WD10EADS (Caviar Green 1TB): > === START OF INFORMATION SECTION === > Device Model: WDC WD10EADS-00M2B0 > Serial Number: WD-WCAV51538624 > Firmware Version: 01.00A01 > User Capacity: 1,000,204,886,016 bytes > Device is: Not in smartctl database [for details use: -P > showall] > ATA Version is: 8 > ATA Standard is: Exact ATA specification draft version not indicated > Local Time is: Thu Nov 26 18:50:44 2009 CET > SMART support is: Available - device has SMART capability. > SMART support is: Enabled I'm trying to configure smartctl so that it won't wake the HD up for testing, using "-n standby": > /dev/ad6 -H -m root -a -n standby -o on -S on -s (S/../.././02| > L/../../6/03) But smartd won't accept: > smartd[94230]: Device: /dev/ad6, no ATA CHECK POWER STATUS support, > ignoring -n Directive I just don't know why. Is it: - the HD that doesn't support ata check power status? - the FreeBSD ata driver? - smartd that is too old for this new HD? regards, patpro From owner-freebsd-hardware@FreeBSD.ORG Fri Nov 27 01:08:55 2009 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 65D5C1065679 for ; Fri, 27 Nov 2009 01:08:55 +0000 (UTC) (envelope-from jguojun@sbcglobal.net) Received: from web82207.mail.mud.yahoo.com (web82207.mail.mud.yahoo.com [209.191.86.102]) by mx1.freebsd.org (Postfix) with SMTP id 2861F8FC0C for ; Fri, 27 Nov 2009 01:08:54 +0000 (UTC) Received: (qmail 52252 invoked by uid 60001); 27 Nov 2009 01:08:54 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sbcglobal.net; s=s1024; t=1259284134; bh=6lFUGoGhB+fcyhs2+19dxnApaA11+ts97M7pKDQBk4A=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=hCKseKODsUjCfV9v2SuA0x18e6ZaCTIJf19oPEsF9YsjJqKGWBUbekT5BCWB+QRB4CACYwjEByorl+RkmR5xROiG88XGRCAzJ7ZR5fGgpirmfiUlMsxZGWU80Ez7/shRAISnPWbPDlbiwK1uQP1osscftvtYSQ41yhw7ls2y75U= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=sbcglobal.net; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=cgvayEKjh6pO6i7XeGK6tVso9FZnmtdu62Mb0WHwZG59TjZbyBuNrgQdGpsqzhlQtteejlqOWZkX/nU4LT1+PMTiop3TImoV+LkJxXsTqCE+xvV7rFU6d8KPOYXs27UbP2p8u4ry+JO3pemXrBpmT/YzdDavHRIv8IiqHv4vrh0=; Message-ID: <390534.50689.qm@web82207.mail.mud.yahoo.com> X-YMail-OSG: a9J_QQoVM1n9d82zsK0YeYguKE1e_hx2p6BCo6Qr1NUnbHovZkU4dtHQCaCPmBcOj9hNpXUkDpOlSs9dMTVKX2krs.Zd36jPx9EWV82n32LLF_d3cX4K7q_fCx2iZcxV.zRsZkLMDqMBfVkfa0gBOemDreXeAwMDAy0djkqApyNL4eamskDFwoel05TwZ0QOcseFEQnbmfSbRH1JFBiFdrVb4Hds_OHVe91a6RjxMqhNpLiDdCmi_8oVUcJaOTEOLiCJtUpUSImaiYGhg1FMVmxuT0ak5dOZoO7.f8TxdZWrh.k3LiauZuoGLwEeTPlMbS.Vhh30lJ1QcR.H1N3KKwPv Received: from [76.202.192.211] by web82207.mail.mud.yahoo.com via HTTP; Thu, 26 Nov 2009 17:08:54 PST X-Mailer: YahooMailClassic/8.1.6 YahooMailWebService/0.8.100.260964 Date: Thu, 26 Nov 2009 17:08:54 -0800 (PST) From: Jin Guojun To: freebsd-hardware@freebsd.org, freebsd-stable , Steve Polyack In-Reply-To: <4B0C1A72.3000301@comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Subject: Re: Panic possibly related to glabel/geom and siis(4) 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, 27 Nov 2009 01:08:55 -0000 This is similar to what I have fight on last two weeks (was 8.0-RC USB/FS). My back trace from the panic is some different from yours, but the behave is the same. When access USB drives from 8.0-RC and 8.0-R will cause drives dead, vanish or reset, thus causing panic. >From both cases, it looks like a hotplug/automount related problem. --- On Tue, 11/24/09, Steve Polyack wrote: > From: Steve Polyack > Subject: Panic possibly related to glabel/geom and siis(4) > To: freebsd-hardware@freebsd.org, "freebsd-stable" , freebsd-geom@FreeBSD.org > Date: Tuesday, November 24, 2009, 5:40 PM > I have a system running > 8.0-PRERELEASE with multiple drives and SATA port > multipliers (siis controllers and PMPs). All of the > attached drives are labeled via glabel(8) and then included > into a ZFS pool. During some testing to determine how > the system would react to a dead drive (simulated by > physically removing a drive during operation), I was > able to produce a panic. > > Now, I know that the SATA PMP and siis(4) code to handle > and recover from device errors is incomplete, but I believe > the crash may be particular to using glabel'd drives. > Basically, after removing a drive while the zpool is in use > and issues 'camcontrol reset' and 'rescan' on the > appropriate bus, the physical device associated with the > drive disappears. In this case: > (pass5:siisch7:0:15:0): lost device > (pass5:siisch7:0:15:0): removing device entry > (ada2:siisch7:0:0:0): lost device > > and /dev/ada2 disappears. However, the associated > glabel /dev/label/bigdisk07 remains. Since my ZFS pool > is created based on the drive glabels, I believe this is why > ZFS never notices the drives disappear either. > > Do glabels typically go away after a physical device is > lost? Should this not be the case? > > > After some runtime with the physical device missing, a > kernel panic is produced: > > ada2:siisch7:0:0:0): Synchronize cache failed > (ada2:siisch7:0:0:0): removing device entry > > > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 14 > fault virtual address = 0x48 > fault code > = supervisor write data, page not present > instruction pointer = > 0x20:0xffffffff8035f375 > stack pointer > = 0x28:0xffffff800006db60 > frame pointer > = 0x28:0xffffff800006db70 > code segment = > base 0x0, limit 0xfffff, type 0x1b > > = DPL 0, pres 1, long 1, > def32 0, gran 1 > processor eflags = interrupt > enabled, resume, IOPL = 0 > current process = 2 > (g_event) > [thread pid 2 tid 100014 ] > Stopped at > _mtx_lock_flags+0x15: lock > cmpxchgq %rsi,0x18(%rdi) > db> bt > Tracing pid 2 tid 100014 td 0xffffff00014d4ab0 > _mtx_lock_flags() at _mtx_lock_flags+0x15 > vdev_geom_release() at vdev_geom_release+0x33 > vdev_geom_orphan() at vdev_geom_orphan+0x15c > g_run_events() at g_run_events+0x104 > g_event_procbody() at g_event_procbody+0x55 > fork_exit() at fork_exit+0x118 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff800006dd30, rbp = 0 --- > > > I'm open to try patches and other suggestions. > Thanks. > _______________________________________________ > 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" >