From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 00:39:59 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 087E3106567B for ; Sun, 2 Nov 2008 00:39:59 +0000 (UTC) (envelope-from jille@quis.cx) Received: from istud.quis.cx (ip83-113-174-82.adsl2.static.versatel.nl [82.174.113.83]) by mx1.freebsd.org (Postfix) with ESMTP id A99018FC1A for ; Sun, 2 Nov 2008 00:39:58 +0000 (UTC) (envelope-from jille@quis.cx) Received: from [192.168.1.4] (ille [192.168.1.4]) by istud.quis.cx (Postfix) with ESMTP id 4AD795C85; Sat, 1 Nov 2008 16:30:46 +0100 (CET) Message-ID: <490C7625.6060608@quis.cx> Date: Sat, 01 Nov 2008 16:30:45 +0100 From: Jille Timmermans User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Alexey Dokuchaev References: <20081101061930.GA34365@regency.nsu.ru> In-Reply-To: <20081101061930.GA34365@regency.nsu.ru> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: device snp build broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 00:39:59 -0000 Hello, snp(4) in -CURRENT is currently not supported. Ed made a patch for it; which worked for me. You can get the latest version from: http://people.freebsd.org/~ed/mpsafetty/ (The patch-set also includes other things; like a new /dev/console) -- Jille Alexey Dokuchaev schreef: > Hi there, > > Looks like device snp is broken on recent -CURRENT. Is it being > supported at all? How useful it is in modern environment? > > Thanks. Relevant part of build log attached. > > ./danfe > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 05:46:20 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9B29A1065697 for ; Sun, 2 Nov 2008 05:46:20 +0000 (UTC) (envelope-from jbolivar@cantv.net) Received: from rs25s3.datacenter.cha.cantv.net (rs25s3.datacenter.cha.cantv.net [200.11.173.13]) by mx1.freebsd.org (Postfix) with ESMTP id 36C838FC19 for ; Sun, 2 Nov 2008 05:46:20 +0000 (UTC) (envelope-from jbolivar@cantv.net) X-DNSBL-MILTER: Passed Received: from [127.0.0.1] (dbec61b89.dslam-172-17-160-245-0126-313.dsl.cantv.net [190.198.27.137] (may be forged)) by rs25s3.datacenter.cha.cantv.net (8.14.3/8.14.3/3.0) with ESMTP id mA25YvZg025771 for ; Sun, 2 Nov 2008 01:05:00 -0430 X-Matched-Lists: [] Message-ID: <490D3C00.4040708@cantv.net> Date: Sun, 02 Nov 2008 01:04:56 -0430 From: Julian Bolivar User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 081101-0, 11/01/2008), Outbound message X-Antivirus-Status: Clean X-Virus-Scanned: ClamAV version 0.94, clamav-milter version 0.94 on 10.128.1.88 X-Virus-Status: Clean Subject: /stand/sysinstall freezed on FreeBSD 7.1 install X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 05:46:20 -0000 Dear Friends, I try to install FreeBSD 7.1 AMD64 beta 2 in an Intel Core 2 Duo and motherboard MSI 975X Platinum V.2m, but when /stand/sysinstall try to start from the installation CD, the system freezed and don't continue the install process. Anyone know how to solved this problem to install it Thanks and regards, Julian Bolivar From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 08:04:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EF891065679 for ; Sun, 2 Nov 2008 08:04:38 +0000 (UTC) (envelope-from kerneljack@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by mx1.freebsd.org (Postfix) with ESMTP id D22618FC08 for ; Sun, 2 Nov 2008 08:04:37 +0000 (UTC) (envelope-from kerneljack@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1974699wfg.7 for ; Sun, 02 Nov 2008 01:04:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=xOJeFT7o6+BClwjUhopxu3CV4+3FldTBNrVJQAKXoiQ=; b=NYhJMab7edQPPAgkoCcA4Po+HYSPHX5ej5/hFVZ9acSXNvD5KKnEjVUzphHjNsl1pP dUMhk7pigmNQ/e46fqA4vxKEpf7Xebfx2orRh2+jFk3frc0VXkHB9RLaJ2ViFLQkrHI1 C76sVPz8XKTLLX+16G9snJ17LqaVjKp55bOrI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=nSPwIbBqT7CTIh6ACpgLfHmk/JwrbJnT2Uc/Nv15MbZRp5QJ2eA4vqUBqR1J7BKgmz XL1IARhYCWQxp85p7z9THqgBZyv0P4WQ4+75OZTuIoA6Xjm0DVNSHF6gRdjqD1ioptks ktGL0kM5o5tcyjeA+W5rDNxyLQ/L5fzutCea8= Received: by 10.142.242.11 with SMTP id p11mr2206489wfh.28.1225613077413; Sun, 02 Nov 2008 01:04:37 -0700 (PDT) Received: by 10.142.156.8 with HTTP; Sun, 2 Nov 2008 01:04:37 -0700 (PDT) Message-ID: Date: Sun, 2 Nov 2008 08:04:37 +0000 From: "Khusro Jaleel" To: freebsd-current@freebsd.org, current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kerneljack@kerneljack.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 08:04:38 -0000 Hi, I'm new to FreeBSD-CURRENT and am having problems getting my wireless to work on my laptop. It is an old Centrino ASUS laptop with built-in IPW2200 wireless. I've had no problems getting wireless to work on this for the past few years now with many flavors of linux and of course Windows so I'm sure it should also work in FreeBSD without any issues. However, I'm not having much luck. I've followed the instructions in the Handbook's Wireless page and read the iwi(4) man page and added the following to my /boot/loader.conf: ------------- legal.intel_iwi.license_ack=1 if_iwi_load="YES" wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" hw.psm.synaptics_support=1 -------------- When I reboot and do a "dmesg | grep iwi" I get: ---------- iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Am I forgetting to load the firmware somehow? In /boot/kernel, I see the following files: ----------- [root@asus ~]# ls -l /boot/kernel/iwi_* -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko ----------- ifconfig: bge0: flags=8843 metric 0 mtu 1500 options=9b ether 00:11:2f:0c:e8:7f inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:e0:18:1b:1f:63 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 iwi0: flags=8803 metric 0 mtu 2290 ether 00:0e:35:0d:7c:65 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier plip0: flags=108810 metric 0 mtu 1500 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 But if I try to do "ifconfig iwi0 up" I get: ---------- iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Any help appreciated. Thanks. From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 08:26:02 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6635106564A for ; Sun, 2 Nov 2008 08:26:02 +0000 (UTC) (envelope-from kerneljack@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by mx1.freebsd.org (Postfix) with ESMTP id AC6FD8FC13 for ; Sun, 2 Nov 2008 08:26:02 +0000 (UTC) (envelope-from kerneljack@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so1978542wfg.7 for ; Sun, 02 Nov 2008 01:26:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=xOJeFT7o6+BClwjUhopxu3CV4+3FldTBNrVJQAKXoiQ=; b=NYhJMab7edQPPAgkoCcA4Po+HYSPHX5ej5/hFVZ9acSXNvD5KKnEjVUzphHjNsl1pP dUMhk7pigmNQ/e46fqA4vxKEpf7Xebfx2orRh2+jFk3frc0VXkHB9RLaJ2ViFLQkrHI1 C76sVPz8XKTLLX+16G9snJ17LqaVjKp55bOrI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=nSPwIbBqT7CTIh6ACpgLfHmk/JwrbJnT2Uc/Nv15MbZRp5QJ2eA4vqUBqR1J7BKgmz XL1IARhYCWQxp85p7z9THqgBZyv0P4WQ4+75OZTuIoA6Xjm0DVNSHF6gRdjqD1ioptks ktGL0kM5o5tcyjeA+W5rDNxyLQ/L5fzutCea8= Received: by 10.142.242.11 with SMTP id p11mr2206489wfh.28.1225613077413; Sun, 02 Nov 2008 01:04:37 -0700 (PDT) Received: by 10.142.156.8 with HTTP; Sun, 2 Nov 2008 01:04:37 -0700 (PDT) Message-ID: Date: Sun, 2 Nov 2008 08:04:37 +0000 From: "Khusro Jaleel" To: freebsd-current@freebsd.org, current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kerneljack@kerneljack.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 08:26:03 -0000 Hi, I'm new to FreeBSD-CURRENT and am having problems getting my wireless to work on my laptop. It is an old Centrino ASUS laptop with built-in IPW2200 wireless. I've had no problems getting wireless to work on this for the past few years now with many flavors of linux and of course Windows so I'm sure it should also work in FreeBSD without any issues. However, I'm not having much luck. I've followed the instructions in the Handbook's Wireless page and read the iwi(4) man page and added the following to my /boot/loader.conf: ------------- legal.intel_iwi.license_ack=1 if_iwi_load="YES" wlan_load="YES" firmware_load="YES" iwi_bss_load="YES" iwi_ibss_load="YES" iwi_monitor_load="YES" hw.psm.synaptics_support=1 -------------- When I reboot and do a "dmesg | grep iwi" I get: ---------- iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) iwi0: mem 0xff9de000-0xff9defff irq 4 at device 2.0 on pci2 iwi0: [ITHREAD] iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Am I forgetting to load the firmware somehow? In /boot/kernel, I see the following files: ----------- [root@asus ~]# ls -l /boot/kernel/iwi_* -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko ----------- ifconfig: bge0: flags=8843 metric 0 mtu 1500 options=9b ether 00:11:2f:0c:e8:7f inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active fwe0: flags=8802 metric 0 mtu 1500 options=8 ether 02:e0:18:1b:1f:63 ch 1 dma -1 fwip0: flags=8802 metric 0 mtu 1500 lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 iwi0: flags=8803 metric 0 mtu 2290 ether 00:0e:35:0d:7c:65 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier plip0: flags=108810 metric 0 mtu 1500 lo0: flags=8049 metric 0 mtu 16384 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet6 ::1 prefixlen 128 inet 127.0.0.1 netmask 0xff000000 But if I try to do "ifconfig iwi0 up" I get: ---------- iwi0: timeout waiting for (null) firmware initialization to complete iwi0: could not load boot firmware (null) ---------- Any help appreciated. Thanks. From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 09:58:04 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9297F1065676 for ; Sun, 2 Nov 2008 09:58:04 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from fish.ish.com.au (eth5921.nsw.adsl.internode.on.net [59.167.240.32]) by mx1.freebsd.org (Postfix) with ESMTP id 4F0268FC12 for ; Sun, 2 Nov 2008 09:58:04 +0000 (UTC) (envelope-from ari@ish.com.au) Received: from [10.29.62.12] (port=57946) by fish.ish.com.au with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from ) id 1KwZy4-0007fK-0S; Sun, 02 Nov 2008 21:14:00 +1100 Message-Id: From: Aristedes Maniatis To: Nicolas Martyanoff In-Reply-To: <20081101114717.0ffc2ec8@valhala> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Sun, 2 Nov 2008 20:46:25 +1100 References: <20081101114717.0ffc2ec8@valhala> X-Mailer: Apple Mail (2.929.2) Cc: current@freebsd.org Subject: Re: ZFS for a desktop computer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 09:58:04 -0000 On 01/11/2008, at 9:47 PM, Nicolas Martyanoff wrote: > - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD > since Xen, NVidia drivers and wine don't work on it; but ZFS is said > to be unsuitable for i386. ZFS will run on i386, however since ZFS requires lots of RAM it has been said that it doesn't make sense to run it on systems with less than 1Gb of RAM dedicated to ZFS. I believe the requirement for large amounts of RAM will be slightly eased in later versions of ZFS (well, it still like RAM but will not hang your system when it runs out quite so easily). Read these instructions on how to get i386 to play with ZFS: http://wiki.freebsd.org/ZFSTuningGuide > - It's said you can't boot from a ZFS pool. Miroslav has answered this one with a couple of useful links (including one I co-wrote :-) Ari Maniatis --------------------------> ish http://www.ish.com.au Level 1, 30 Wilson Street Newtown 2042 Australia phone +61 2 9550 5001 fax +61 2 9550 4001 GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 09:30:44 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2DC4F1065672 for ; Sun, 2 Nov 2008 09:30:44 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id DE8DE8FC1B for ; Sun, 2 Nov 2008 09:30:43 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1KwZ2Z-0002Q0-Ed>; Sun, 02 Nov 2008 10:14:35 +0100 Received: from e178040129.adsl.alicedsl.de ([85.178.40.129] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1KwZ2Z-0005ge-C3>; Sun, 02 Nov 2008 10:14:35 +0100 Message-ID: <490D6F88.4050609@mail.zedat.fu-berlin.de> Date: Sun, 02 Nov 2008 10:14:48 +0100 From: "O. Hartmann" User-Agent: Thunderbird 2.0.0.17 (X11/20081101) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.40.129 X-Mailman-Approved-At: Sun, 02 Nov 2008 12:10:20 +0000 Subject: GPT(8): gone in FreeBSD 8.0-CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 09:30:44 -0000 Hello, I'm looking for the gpt(8) tool, found in FreeBSD 7. When switching to FreeBSD 8-CUR I missed it. Has it been dumped? Why, how to handle GUID partitions in FBSD8? Regards, Oliver -- From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 12:19:58 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 947DC1065670 for ; Sun, 2 Nov 2008 12:19:58 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 209738FC19 for ; Sun, 2 Nov 2008 12:19:57 +0000 (UTC) (envelope-from rpaulo@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so1468220ugs.39 for ; Sun, 02 Nov 2008 04:19:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer:sender; bh=Fnwy1bkhMC09/Lg5u7dn2xJZ2N83wxixEc9R09RnuT4=; b=Y0Pa+tlD5elQXnx8hbdJpPouDv8ceYk7KLBi87AlbUeOCU9GL/iQS75ntatVyEWerE wMnZK6NM3TQ8vIGWreF70qu7iGXJFJa5FcIgys/NEXdGgjLa/9oZ/chLLFRGITBPnubw 1jlq8myFpctx3xSXnChMlknX9WdY8pPIW1YvI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer:sender; b=EjZWWDdrP0ydgYYlw3Yp4Fwb3w31q7USZt3IwpJPNCHKvw9Pn22yh+ebJWuiNjk2hu 8RWkKizdBT00pUufqyYOPNFpvMM/X4z+dVduY98DZXWXwl3b9XA59BSuXgMLU9GnmxRi pOYnI/8z74KJxrCXuXlbSy3HPls5qhvWwI3p4= Received: by 10.210.21.6 with SMTP id 6mr6684881ebu.18.1225628397826; Sun, 02 Nov 2008 04:19:57 -0800 (PST) Received: from ?10.0.1.30? ([92.250.66.213]) by mx.google.com with ESMTPS id 2sm30040071nfv.5.2008.11.02.04.19.55 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Nov 2008 04:19:56 -0800 (PST) Message-Id: <22FEED13-2E4B-4873-B1A5-EA841369E3AE@freebsd.org> From: Rui Paulo To: O. Hartmann In-Reply-To: <490D6F88.4050609@mail.zedat.fu-berlin.de> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Sun, 2 Nov 2008 12:19:52 +0000 References: <490D6F88.4050609@mail.zedat.fu-berlin.de> X-Mailer: Apple Mail (2.929.2) Sender: Rui Paulo Cc: freebsd-current@freebsd.org Subject: Re: GPT(8): gone in FreeBSD 8.0-CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 12:19:58 -0000 On 2 Nov 2008, at 09:14, O. Hartmann wrote: > Hello, > I'm looking for the gpt(8) tool, found in FreeBSD 7. When switching to > FreeBSD 8-CUR I missed it. Has it been dumped? Why, how to handle GUID > partitions in FBSD8? Yes, gpt is gone. We now use gpart. Regards, -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 12:59:25 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 65D671065675 for ; Sun, 2 Nov 2008 12:59:25 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id DF0798FC12 for ; Sun, 2 Nov 2008 12:59:24 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so654641eyi.7 for ; Sun, 02 Nov 2008 04:59:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received :x-authentication-warning:date:from:to:subject:message-id :mime-version:content-type:content-disposition:user-agent; bh=CirElK5eZNAWvFmn03LU3lpbWdqVi1nsPH9c8Pqe+lI=; b=km9rWhtdAb3Tv4gT3G9p7VrEOcwdL64IqJVmHyYZArEY3iRW3a+hnP+XHQ3+qWKRzE cGjaDJ7vN4k+msDe9MDmPHXdb/hYoYva0b+m64NNj3B5/jhYVLTDIqCZDo8S6LQexVJN cbh+iLYJrG7kM7QFBAzHHzZEEd5/3SSklo06g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-authentication-warning:date:from:to:subject:message-id :mime-version:content-type:content-disposition:user-agent; b=Jl1YhCcXsdQLMqxmQAC3iyzhuAhK0VcuvoO0eo6hXGw+wKv8yLWqbi1E0zLOQKg6vV XS/8FRxO/zKmicv89PDJczO+y2xjdGRsg6w6hGlaF5Wi6Kyu8/qriPTj4glaynXXvrm8 5teIY67Ych4u/A5yVIJelQJUlmCrG6AG44vf8= Received: by 10.210.25.18 with SMTP id 18mr16169984eby.14.1225629064491; Sun, 02 Nov 2008 04:31:04 -0800 (PST) Received: from darklight.homeunix.org ([85.175.24.53]) by mx.google.com with ESMTPS id u14sm11309722gvf.6.2008.11.02.04.31.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Nov 2008 04:31:03 -0800 (PST) Received: from darklight.homeunix.org (yuri@darklight.homeunix.org [127.0.0.1]) by darklight.homeunix.org (8.14.3/8.14.3) with ESMTP id mA2CV0YG001995 for ; Sun, 2 Nov 2008 15:31:00 +0300 (MSK) (envelope-from yuri.pankov@gmail.com) Received: (from yuri@localhost) by darklight.homeunix.org (8.14.3/8.14.3/Submit) id mA2CV0fk001994 for freebsd-current@freebsd.org; Sun, 2 Nov 2008 15:31:00 +0300 (MSK) (envelope-from yuri.pankov@gmail.com) X-Authentication-Warning: darklight.homeunix.org: yuri set sender to yuri.pankov@gmail.com using -f Date: Sun, 2 Nov 2008 15:31:00 +0300 From: Yuri Pankov To: freebsd-current@freebsd.org Message-ID: <20081102123100.GA1434@darklight.homeunix.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.18 (2008-05-17) Subject: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 12:59:25 -0000 Hi, Trying to mount nonexistent smb share with mount_smbfs leads to following panic: # mount_smbfs //yuri@lifebane/blahblah /mnt Unread portion of the kernel message buffer: smb_co_lock: recursive lock for object 1 panic: Lock (lockmgr) smb_vc not locked @ /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a panic() at panic+0x182 witness_assert() at witness_assert+0x21a __lockmgr_args() at __lockmgr_args+0x17a smb_co_put() at smb_co_put+0x76 smb_sm_lookup() at smb_sm_lookup+0xfe smb_usr_lookup() at smb_usr_lookup+0xcd nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 giant_ioctl() at giant_ioctl+0x75 devfs_ioctl_f() at devfs_ioctl_f+0x76 kern_ioctl() at kern_ioctl+0x92 ioctl() at ioctl+0xfd syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = 0x7fffffffe038, rbp = 0x7fffffffe450 --- Uptime: 6m46s Physical memory: 2032 MB Dumping 148 MB: 133 117 101 85 69 53 37 21 5 #0 doadump () at pcpu.h:196 #1 0xffffffff804ea413 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:420 #2 0xffffffff804ea89c in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:576 #3 0xffffffff8052afea in witness_assert (lock=Variable "lock" is not available. ) at /usr/src/sys/kern/subr_witness.c:2199 #4 0xffffffff804d6b4a in __lockmgr_args (lk=0xffffff004a5bf408, flags=1048832, ilk=0xffffff004a5bf430, wmesg=Variable "wmesg" is not available. ) at /usr/src/sys/kern/kern_lock.c:659 #5 0xffffffff81023536 in smb_co_put (cp=0xffffff004a5bf400, scred=0xfffffffe7fd879b0) at lockmgr.h:93 #6 0xffffffff81023fce in smb_sm_lookup (vcspec=0xfffffffe7fd87890, shspec=0xfffffffe7fd87900, scred=0xfffffffe7fd879b0, vcpp=0xfffffffe7fd87928) at /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:222 #7 0xffffffff8102995d in smb_usr_lookup (dp=0xffffff0003738000, scred=0xfffffffe7fd879b0, vcpp=0xfffffffe7fd879c8, sspp=0xfffffffe7fd879c0) at /usr/src/sys/modules/smbfs/../../netsmb/smb_usr.c:154 #8 0xffffffff81024386 in nsmb_dev_ioctl (dev=Variable "dev" is not available. ) at /usr/src/sys/modules/smbfs/../../netsmb/smb_dev.c:285 #9 0xffffffff804b6375 in giant_ioctl (dev=0xffffff004a5bf800, cmd=2198367850, data=0xffffff0003738000 "\002", fflag=3, td=0xffffff004a5c7370) at /usr/src/sys/kern/kern_conf.c:407 #10 0xffffffff8047a636 in devfs_ioctl_f (fp=0xffffff0003e14870, com=2198367850, data=Variable "data" is not available. ) at /usr/src/sys/fs/devfs/devfs_vnops.c:588 #11 0xffffffff8052e9c2 in kern_ioctl (td=0xffffff004a5c7370, fd=Variable "fd" is not available. ) at file.h:262 #12 0xffffffff8052ec2d in ioctl (td=0xffffff004a5c7370, uap=0xfffffffe7fd87c00) at /usr/src/sys/kern/sys_generic.c:676 #13 0xffffffff807c081f in syscall (frame=0xfffffffe7fd87c90) at /usr/src/sys/amd64/amd64/trap.c:898 #14 0xffffffff807a32db in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:338 #15 0x0000000800939aec in ?? () Previous frame inner to this frame (corrupt stack?) FreeBSD 8.0-CURRENT amd64 World and kernel are built from sources synced on Nov, 1. Yuri From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 12:19:51 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5862106567B for ; Sun, 2 Nov 2008 12:19:51 +0000 (UTC) (envelope-from some.else@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.175]) by mx1.freebsd.org (Postfix) with ESMTP id 648F08FC16 for ; Sun, 2 Nov 2008 12:19:51 +0000 (UTC) (envelope-from some.else@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so1468220ugs.39 for ; Sun, 02 Nov 2008 04:19:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:content-type :content-transfer-encoding; bh=KCxG2KxOd2+Cr1m6wjIDz4oyxV+GvlyLu3FTMwfVgIU=; b=b46Ibm4/t9ULH99/4BTfOAkk2O7nLvS14uJaWgelO3cXqdZz5ua6OxGCOi3Vlhjr5T hv3xF8GQ9JdSWJ2DfFlrNaeNjyaxN9pJm1CvFfbCkdFM8hF4saty2cOYDJ8gGZe76jhl LntwcwZwuZ2peSvbMpK94btPKXm3GQmZGAlJI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; b=dJE9XltG+4/Oit5BGmxNEU4k2Oj42DdIk4RfgnQyHnhiav+/v4udGm8D0xRubwIF3M tFxT0W37RRHe6SoYaYHPQExXZoNH+YVNPGM4oBQLB/s3254z+G4KlxaviARb4LWGxLMK PzISJhKS9ozl6H/Zxg7qrGisZhtH/APpsgy6Q= Received: by 10.66.239.16 with SMTP id m16mr1278286ugh.9.1225626499089; Sun, 02 Nov 2008 03:48:19 -0800 (PST) Received: from konstig.hippie (c-0692e255.13-501-64736c14.cust.bredbandsbolaget.se [85.226.146.6]) by mx.google.com with ESMTPS id s1sm7661813uge.27.2008.11.02.03.48.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Nov 2008 03:48:18 -0800 (PST) Message-ID: <490D937A.8020103@gmail.com> Date: Sun, 02 Nov 2008 12:48:10 +0100 From: Annan User-Agent: Thunderbird 2.0.0.17 (X11/20081026) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 02 Nov 2008 13:03:05 +0000 Cc: Subject: Trouble installing FreeBSD on ASUS M3A78-EM with firewire enabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 12:19:51 -0000 When trying to install FreeBSD 7.1-BETA2 (amd64) on a computer with the motherboard ASUS M3A78-EM, the installation freezes with the error message: run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config Booting without ACPI, it still freezes, right after: Trying to mount root from ufs:/ufs/md0. I also tried 8.0-HEAD from http://pub.allbsd.org/FreeBSD-snapshots/amd64/8.0-HEAD-20081101-JPSNAP/cdrom/, which resulted in the same error messages. To get it to boot (7.1-BETA2, though I assume 8.0-HEAD will also boot :-)), deactivate firewire in BIOS (discovered after trying all sorts of things). I have no use for firewire so it's not a problem, but maybe it is for someone else. If you want to install 7.0-RELEASE, you also have to deactivate USB (as pointed out by this comment: http://www.vanutsteen.nl/2008/07/21/new-virtualization-server-htpc-machine/#comment-315). I found it to be true for M3A78-EM too. From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 12:26:13 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5309E1065675 for ; Sun, 2 Nov 2008 12:26:13 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 0F2EA8FC13 for ; Sun, 2 Nov 2008 12:26:12 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtp (envelope-from ) id <1Kwc20-0007OD-0a>; Sun, 02 Nov 2008 13:26:12 +0100 Received: from e178040129.adsl.alicedsl.de ([85.178.40.129] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@freebsd.org with esmtpsa (envelope-from ) id <1Kwc1z-0005BU-To>; Sun, 02 Nov 2008 13:26:12 +0100 Message-ID: <490D9C71.1050401@mail.zedat.fu-berlin.de> Date: Sun, 02 Nov 2008 13:26:25 +0100 From: "O. Hartmann" User-Agent: Thunderbird 2.0.0.17 (X11/20081101) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.40.129 X-Mailman-Approved-At: Sun, 02 Nov 2008 13:18:29 +0000 Subject: OpenLDAP 2.4.11: won't work anymore, crashes with SIGNAL 11 after start X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 12:26:13 -0000 Hello, I migrtaed this day to FreeBSD 8.0-CURRENT, most recent buildworld since last night. I'm about reinstalling everything I need from scratch, so OpenLDAP 2.4.11 (with SASL support). After pulling back the backup of the LDAP configurations and assuring that access rights etc. is in the right place, I tried starting openldap-2.4.11 and witnessed a crash. Immediately after the slapd-daemon starts it suffers from SIGNAL 11: Starting slapd. @(#) $OpenLDAP: slapd 2.4.11 (Nov 2 2008 11:42:11) $ root@foo.org:/usr/ports/net/openldap24-server/work/openldap-2.4.11/servers/slapd Segmentation fault /usr/local/etc/rc.d/slapd: WARNING: failed to start slapd Well, removing all of my configurations (especially schemata, the slapd.d-directory) and replacing everything needed by those files coming with the installation package and trying starting this results in an 'Abort trap': Starting slapd. @(#) $OpenLDAP: slapd 2.4.11 (Nov 2 2008 11:42:11) $ root@foo.org:/usr/ports/net/openldap24-server/work/openldap-2.4.11/servers/slapd Assertion failed: (schema_init_done == 1), function slap_schema_check, file schema_prep.c, line 1340. Abort trap /usr/local/etc/rc.d/slapd: WARNING: failed to start slapd The used configuration and installation works fine with FreeBSD 7.1-PRE (exactly the same way installed ports, used the same make.conf!). Well, before submitting a PR or investigating deeper, please can someone using LDAP 2.4.11 (from ports) on FBSD 8.0-CUR report whether he is successfully using LDAP or not? If there is more than a stupid config-error I will investigate deeper with all the debugging facilities switched on. Regards, thanks in advance, oliver From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 12:27:01 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5F501065670 for ; Sun, 2 Nov 2008 12:27:01 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 902D38FC16 for ; Sun, 2 Nov 2008 12:27:01 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1Kwc2m-0007Uf-My>; Sun, 02 Nov 2008 13:27:00 +0100 Received: from e178040129.adsl.alicedsl.de ([85.178.40.129] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1Kwc2m-0005Bq-KK>; Sun, 02 Nov 2008 13:27:00 +0100 Message-ID: <490D9CA2.6050006@mail.zedat.fu-berlin.de> Date: Sun, 02 Nov 2008 13:27:14 +0100 From: "O. Hartmann" User-Agent: Thunderbird 2.0.0.17 (X11/20081101) MIME-Version: 1.0 To: Rui Paulo References: <490D6F88.4050609@mail.zedat.fu-berlin.de> <22FEED13-2E4B-4873-B1A5-EA841369E3AE@freebsd.org> In-Reply-To: <22FEED13-2E4B-4873-B1A5-EA841369E3AE@freebsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.40.129 X-Mailman-Approved-At: Sun, 02 Nov 2008 13:18:39 +0000 Cc: freebsd-current@freebsd.org Subject: Re: GPT(8): gone in FreeBSD 8.0-CURRENT? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 12:27:01 -0000 Rui Paulo wrote: > > On 2 Nov 2008, at 09:14, O. Hartmann wrote: > >> Hello, >> I'm looking for the gpt(8) tool, found in FreeBSD 7. When switching to >> FreeBSD 8-CUR I missed it. Has it been dumped? Why, how to handle GUID >> partitions in FBSD8? > > Yes, gpt is gone. > We now use gpart. > > Regards, > -- > Rui Paulo > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" all right, thanks a lot. oliver From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 14:48:45 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5A2B106567D for ; Sun, 2 Nov 2008 14:48:45 +0000 (UTC) (envelope-from scode@hyperion.scode.org) Received: from hyperion.scode.org (cl-1361.ams-04.nl.sixxs.net [IPv6:2001:960:2:550::2]) by mx1.freebsd.org (Postfix) with ESMTP id 67CF48FC28 for ; Sun, 2 Nov 2008 14:48:45 +0000 (UTC) (envelope-from scode@hyperion.scode.org) Received: by hyperion.scode.org (Postfix, from userid 1001) id CF0A523C424; Sun, 2 Nov 2008 15:48:43 +0100 (CET) Date: Sun, 2 Nov 2008 15:48:43 +0100 From: Peter Schuller To: John Nielsen Message-ID: <20081102144842.GA59552@hyperion.scode.org> References: <20081101114717.0ffc2ec8@valhala> <200811011517.37640.lists@jnielsen.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline In-Reply-To: <200811011517.37640.lists@jnielsen.net> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Nicolas Martyanoff , freebsd-current@freebsd.org Subject: Re: ZFS for a desktop computer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 14:48:45 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable > There are patches available to allow this but frankly I don't see the=20 > appeal. I think it makes much more sense to have / (including /boot) be a= =20 > regular UFS2 filesystem on a small partition. If something goes wrong you= =20 > can boot from a CD or single-user and not have to worry about getting you= r=20 > ZFS pools back online before you can even start troubleshooting the syste= m.=20 FWIW let me just put the vote in there that to me, personally, there is a lot of appeal. For recovery, I don't find minimalistic /:s or fixit CD:s very useful anyway (in fact I don't think I have ever fixed a system that way; if there is some trouble that prevents booting, I tend to end up booting a separate fully installed system from another drive or similar to have full flexibility). If you're using ZFS because you want to avoid certain failure conditions (such as "oh, there was a bad block during reconstruction and my mirror got blown away even though it was a 4-way mirror"), it is nice to have that applied to your *entire* system instead of having a small root partition or boot partition that is somehow exempted. Especially since these are the ones you really need to boot the system. I appreciate that supporting direct booting off of ZFS is not easy to implement, and this is not any kind of complaint. I just want to respond to the claim that there is no appeal to having it supported. I doubt I am alone in thinking it would be great to boot natively off ZFS, even if not every one under the sun agrees :) -- / Peter Schuller PGP userID: 0xE9758B7D or 'Peter Schuller ' Key retrieval: Send an E-Mail to getpgpkey@scode.org E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkNvcoACgkQDNor2+l1i303eACdGdJPz0xdMIcZRJACgB26uPT2 Ck0An2m1mYGV0lFZeNLRdZBPJEWifcbd =109P -----END PGP SIGNATURE----- --huq684BweRXVnRxX-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 15:16:28 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB60E106567C for ; Sun, 2 Nov 2008 15:16:28 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from megatron.madpilot.net (megatron.madpilot.net [88.149.173.206]) by mx1.freebsd.org (Postfix) with ESMTP id 6E5B58FC1F for ; Sun, 2 Nov 2008 15:16:28 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from localhost (localhost [127.0.0.1]) by megatron.madpilot.net (Postfix) with ESMTP id 07E11130C08; Sun, 2 Nov 2008 15:58:57 +0100 (CET) X-Virus-Scanned: amavisd-new at madpilot.net Received: from megatron.madpilot.net ([127.0.0.1]) by localhost (megatron.madpilot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fEc30RbEDKX7; Sun, 2 Nov 2008 15:58:54 +0100 (CET) Received: from wedge.madpilot.net (wedge.madpilot.net [172.24.42.11]) by megatron.madpilot.net (Postfix) with ESMTP; Sun, 2 Nov 2008 15:58:54 +0100 (CET) Message-ID: <490DC02E.7020701@madpilot.net> Date: Sun, 02 Nov 2008 15:58:54 +0100 From: Guido Falsi User-Agent: Thunderbird 2.0.0.17 (X11/20080927) MIME-Version: 1.0 To: Peter Schuller References: <20081101114717.0ffc2ec8@valhala> <200811011517.37640.lists@jnielsen.net> <20081102144842.GA59552@hyperion.scode.org> In-Reply-To: <20081102144842.GA59552@hyperion.scode.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Nicolas Martyanoff , freebsd-current@freebsd.org, John Nielsen Subject: Re: ZFS for a desktop computer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 15:16:28 -0000 Peter Schuller wrote: > I appreciate that supporting direct booting off of ZFS is not easy to > implement, and this is not any kind of complaint. I just want to > respond to the claim that there is no appeal to having it supported. I > doubt I am alone in thinking it would be great to boot natively off > ZFS, even if not every one under the sun agrees :) > Just to cast a "vote" I subscribe to this opinion. It would be great...In fact if direct boot from ZFS was supported I'd convert my work PC to AMD64+ZFS immediately. At home it would be hardware since my PCs have at most 512 Mb ram, which is more than enough for what I do here. -- Guido Falsi From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 16:05:10 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6117A106564A for ; Sun, 2 Nov 2008 16:05:10 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.185]) by mx1.freebsd.org (Postfix) with ESMTP id 329AD8FC19 for ; Sun, 2 Nov 2008 16:03:47 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by mu-out-0910.google.com with SMTP id i2so2131818mue.3 for ; Sun, 02 Nov 2008 08:03:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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=LT5dNGkZQ+4MP582TSUWXiFjMZWtCaSCeuIj4a+Irc0=; b=ohTTz9L40DoVQ4rLLZy/09zUEd2h2NZIwtX5FikT683JJlWd9H6gaDFetP7KQbESyS v/o8a5+Qa9gRNcZof4uWymkGQGqKyB5Yw4KTsXdvWBlOaHaRpPA/25Qt4ZiOEt4EAW5F IlE1tUwHWXrAWQfs/Y3pzk3n54OGWlYVDS6rQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=DRoLWXO+jS1g7d3bEPD2Oz/VySMnckfJJs7xdjlDoW/46vXi24jcESYDFIS5ww3uAX HBXtClziY6vDO+ECM7TkGFcvV+eAde2FN7Eu8Ka6ctG3DhEQheylX5Ddh5PPt64Cll5u rZ50xoGX9UYo3cOET8gaGa60kA8ObE0zdTJ6I= Received: by 10.103.22.16 with SMTP id z16mr4275515mui.78.1225640244103; Sun, 02 Nov 2008 07:37:24 -0800 (PST) Received: by 10.103.239.14 with HTTP; Sun, 2 Nov 2008 07:37:24 -0800 (PST) Message-ID: <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> Date: Sun, 2 Nov 2008 16:37:24 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yuri Pankov" In-Reply-To: <20081102123100.GA1434@darklight.homeunix.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081102123100.GA1434@darklight.homeunix.org> X-Google-Sender-Auth: 47038d8779c02b0d Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, developers@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 16:05:10 -0000 2008/11/2, Yuri Pankov : > Hi, > > Trying to mount nonexistent smb share with mount_smbfs leads to > following panic: > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > Unread portion of the kernel message buffer: > smb_co_lock: recursive lock for object 1 > panic: Lock (lockmgr) smb_vc not locked @ > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > cpuid = 0 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > panic() at panic+0x182 > witness_assert() at witness_assert+0x21a > __lockmgr_args() at __lockmgr_args+0x17a > smb_co_put() at smb_co_put+0x76 > smb_sm_lookup() at smb_sm_lookup+0xfe > smb_usr_lookup() at smb_usr_lookup+0xcd > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > giant_ioctl() at giant_ioctl+0x75 > devfs_ioctl_f() at devfs_ioctl_f+0x76 > kern_ioctl() at kern_ioctl+0x92 > ioctl() at ioctl+0xfd > syscall() at syscall+0x1bf > Xfast_syscall() at Xfast_syscall+0xab > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > Uptime: 6m46s > Physical memory: 2032 MB So, what is happening here is that smb_co_lock() is AFU. Infact looking at the code: int smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) { ... if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && (flags & LK_CANRECURSE) == 0) { SMBERROR("recursive lock for object %d\n", cp->co_level); return 0; } ... from that it is obvious that smb_co_lock() won't recurse the lock really, but will let believe the consumer it acquired the lock successfully without panicking at all (the printf is like a little joke there). I think that we don't panic here mainly because these are "user driver" events and we want avoid to get a DoS for the kernel but it is an unacceptable code also. This can be fixed by allowing recuring lockmgr by default but the problem is more vaste. For example, it would be very nice to drop the LK_DRAIN support from netsmb in order to completely remove it from the 8.0 kernel serie and kill a bogus / dangerous option for lockmgr. It would be a cornerstone for lockmgr wealth really. What really is missing here is a valid netsmb maintainer, someone that knows well the layers involved, is motivated to work on it and can take advantage from the other kernel developer experience on the most hardcore parts. It would be also nice, for example, to bring in some Apple's changes (like the crypto support). Someone willing to step in would be very appreciated. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 16:11:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 09B21106564A for ; Sun, 2 Nov 2008 16:11:03 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id DC1648FC18 for ; Sun, 2 Nov 2008 16:11:02 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id mA2GAvHi028213; Sun, 2 Nov 2008 10:10:58 -0600 (CST) (envelope-from stephen@math.missouri.edu) Message-ID: <490DD114.3000901@math.missouri.edu> Date: Sun, 02 Nov 2008 10:11:00 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.17) Gecko/20081023 SeaMonkey/1.1.12 MIME-Version: 1.0 To: kerneljack@kerneljack.com References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 16:11:03 -0000 FreeBSD CURRENT has a different approach to wireless cards. Somewhere in /etc/rc.conf you need lines like wlans_iwi0="wlan0" and then all future ifconfig command should refer to wlan0 instead of iwi0. I am not sure if this will fix your problem or not, but you must have not done this somewhere, otherwise ifconfig would have listed wlan0 as well as iwi0. If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. I think iwi is already a part of that. Khusro Jaleel wrote: > Hi, > > I'm new to FreeBSD-CURRENT and am having problems getting my wireless > to work on my laptop. It is an old Centrino ASUS laptop with built-in > IPW2200 wireless. I've had no problems getting wireless to work on > this for the past few years now with many flavors of linux and of > course Windows so I'm sure it should also work in FreeBSD without any > issues. > > However, I'm not having much luck. I've followed the instructions in > the Handbook's Wireless page and read the iwi(4) man page and added > the following to my /boot/loader.conf: > > ------------- > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES" > hw.psm.synaptics_support=1 > -------------- > > When I reboot and do a "dmesg | grep iwi" I get: > > ---------- > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > ---------- > > Am I forgetting to load the firmware somehow? In /boot/kernel, I see > the following files: > > ----------- > [root@asus ~]# ls -l /boot/kernel/iwi_* > -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko > -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko > -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko > ----------- > > ifconfig: > bge0: flags=8843 metric 0 mtu 1500 > options=9b > ether 00:11:2f:0c:e8:7f > inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > fwe0: flags=8802 metric 0 mtu 1500 > options=8 > ether 02:e0:18:1b:1f:63 > ch 1 dma -1 > fwip0: flags=8802 metric 0 mtu 1500 > lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 > iwi0: flags=8803 metric 0 mtu 2290 > ether 00:0e:35:0d:7c:65 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > plip0: flags=108810 metric 0 mtu 1500 > lo0: flags=8049 metric 0 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > > But if I try to do "ifconfig iwi0 up" I get: > > ---------- > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > ---------- > > Any help appreciated. Thanks. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 16:17:21 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2FE5106568D; Sun, 2 Nov 2008 16:17:21 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.158]) by mx1.freebsd.org (Postfix) with ESMTP id E2DBF8FC26; Sun, 2 Nov 2008 16:17:20 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1729054fgb.35 for ; Sun, 02 Nov 2008 08:17:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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=tRR41TuxcmwWr1fcdySQEGfSm/5CQFtJbjUdzVtpAPg=; b=dXULrz6xkB50Z9hJU94kOB63yA18mTCuKRHVHZ7QXPqfxFQNKzr1gAxDCQsKDvaNdZ ng4bVlkBUs4ifXgmPu1+CXxYYQK9Ca/zmLlXXreC4l3nghI6fhU2/zSvhzoBXeaB0mEv k23MHGpnALbifNuzF8KBK6SOt9Bu1u6WTjuuQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=plix37eFrJOyuKwTjC+ajo1VL2acsGo57sVFNiijDgxf0e+uygqQEaM0qodm62nISR irlcH291as9iVUEmdLCRjlM5oi6GKf12QCRTwIkSsHgSoINoMgoucUQNhAS6+N7jxHW2 c78qxoL1+RWH++xwZX1cBA3f53ye3QS6hVikQ= Received: by 10.86.66.19 with SMTP id o19mr10091634fga.64.1225642638896; Sun, 02 Nov 2008 08:17:18 -0800 (PST) Received: by 10.86.78.14 with HTTP; Sun, 2 Nov 2008 08:17:18 -0800 (PST) Message-ID: <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> Date: Sun, 2 Nov 2008 17:17:18 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yuri Pankov" In-Reply-To: <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> X-Google-Sender-Auth: b35bc9f364f79055 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, developers@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 16:17:21 -0000 2008/11/2, Attilio Rao : > 2008/11/2, Yuri Pankov : > > > Hi, > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > following panic: > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > Unread portion of the kernel message buffer: > > smb_co_lock: recursive lock for object 1 > > panic: Lock (lockmgr) smb_vc not locked @ > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > cpuid = 0 > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > panic() at panic+0x182 > > witness_assert() at witness_assert+0x21a > > __lockmgr_args() at __lockmgr_args+0x17a > > smb_co_put() at smb_co_put+0x76 > > smb_sm_lookup() at smb_sm_lookup+0xfe > > smb_usr_lookup() at smb_usr_lookup+0xcd > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > giant_ioctl() at giant_ioctl+0x75 > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > kern_ioctl() at kern_ioctl+0x92 > > ioctl() at ioctl+0xfd > > syscall() at syscall+0x1bf > > Xfast_syscall() at Xfast_syscall+0xab > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > Uptime: 6m46s > > Physical memory: 2032 MB > > > So, what is happening here is that smb_co_lock() is AFU. > Infact looking at the code: > int > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > { > ... > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > (flags & LK_CANRECURSE) == 0) { > SMBERROR("recursive lock for object %d\n", cp->co_level); > return 0; > } > ... Yuri, could you please test this fix: http://www.freebsd.org/~attilio/netsmb.diff and report if it works? You could get a KASSERT running but this is expected as I want to identify on the callers who passes a malformed request and fix it. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 16:33:14 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 298B71065678 for ; Sun, 2 Nov 2008 16:33:14 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 7460F8FC16 for ; Sun, 2 Nov 2008 16:33:12 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: by nf-out-0910.google.com with SMTP id h3so853695nfh.33 for ; Sun, 02 Nov 2008 08:33:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received :x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=mEWkKJ+xT6SaSwxwFmAFVQXYON1G240N6q3FCSrZxjQ=; b=vn1xBsnFqfLj9sWahXdJCdabqhfHfq/i/c1ssVlE26LYlEJNujzSOOeh+gHNDi6/8C SKSsf3N5scRyTrFXJEHuxRKnCGl8fDG/bex+NDGlPTd1TL2vl4NNxJE0Hct2na4O44mY gfcqQEdV0Fa7RM4y17OAQq6HFvUhh9d5Np2DQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; b=RXgCAvk0cVZkFPprwFcpC0fBBQ/6gk/OMAiokJ8TnHTgQ6XiFuPNMFrKNUhkWrQuPe B6u0wlMhB6pywdHdKHbV1W0cAHmiCVPJgu57udcwKPcp5gELxCxGkO/P7193wxC/sb0d sj/F15zuzewHCrvfqL5OCZF3/Flc+SqmgcXNQ= Received: by 10.210.127.13 with SMTP id z13mr7413463ebc.11.1225643591692; Sun, 02 Nov 2008 08:33:11 -0800 (PST) Received: from darklight.homeunix.org ([85.175.24.53]) by mx.google.com with ESMTPS id g9sm11790271gvc.0.2008.11.02.08.33.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Nov 2008 08:33:11 -0800 (PST) Received: from darklight.homeunix.org (yuri@darklight.homeunix.org [127.0.0.1]) by darklight.homeunix.org (8.14.3/8.14.3) with ESMTP id mA2GX7v2071530; Sun, 2 Nov 2008 19:33:07 +0300 (MSK) (envelope-from yuri.pankov@gmail.com) Received: (from yuri@localhost) by darklight.homeunix.org (8.14.3/8.14.3/Submit) id mA2GX7S1071529; Sun, 2 Nov 2008 19:33:07 +0300 (MSK) (envelope-from yuri.pankov@gmail.com) X-Authentication-Warning: darklight.homeunix.org: yuri set sender to yuri.pankov@gmail.com using -f Date: Sun, 2 Nov 2008 19:33:07 +0300 From: Yuri Pankov To: Attilio Rao Message-ID: <20081102163307.GB1434@darklight.homeunix.org> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org, developers@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 16:33:14 -0000 On Sun, Nov 02, 2008 at 05:17:18PM +0100, Attilio Rao wrote: > 2008/11/2, Attilio Rao : > > 2008/11/2, Yuri Pankov : > > > > > Hi, > > > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > > following panic: > > > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > > > Unread portion of the kernel message buffer: > > > smb_co_lock: recursive lock for object 1 > > > panic: Lock (lockmgr) smb_vc not locked @ > > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > > cpuid = 0 > > > KDB: stack backtrace: > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > panic() at panic+0x182 > > > witness_assert() at witness_assert+0x21a > > > __lockmgr_args() at __lockmgr_args+0x17a > > > smb_co_put() at smb_co_put+0x76 > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > > smb_usr_lookup() at smb_usr_lookup+0xcd > > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > > giant_ioctl() at giant_ioctl+0x75 > > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > > kern_ioctl() at kern_ioctl+0x92 > > > ioctl() at ioctl+0xfd > > > syscall() at syscall+0x1bf > > > Xfast_syscall() at Xfast_syscall+0xab > > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > > Uptime: 6m46s > > > Physical memory: 2032 MB > > > > > > So, what is happening here is that smb_co_lock() is AFU. > > Infact looking at the code: > > int > > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > > { > > ... > > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > > (flags & LK_CANRECURSE) == 0) { > > SMBERROR("recursive lock for object %d\n", cp->co_level); > > return 0; > > } > > ... > > Yuri, > could you please test this fix: > http://www.freebsd.org/~attilio/netsmb.diff > > and report if it works? > You could get a KASSERT running but this is expected as I want to > identify on the callers who passes a malformed request and fix it. > > Thanks, > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein Thanks, Attilio. With this patch system doesn't panic anymore with nonexistent share names (though I had to comment out smb_co_lockstatus prototype and function to get rid of -Werror complaints). Still getting a LOR: netsmb_dev: loaded lock order reversal: 1st 0xffffff0021644008 smb_vc (smb_vc) @ /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:332 2nd 0xffffffff81037368 smbsm (smbsm) @ /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:348 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e witness_checkorder() at witness_checkorder+0x81e __lockmgr_args() at __lockmgr_args+0xc2a smb_co_lock() at smb_co_lock+0x38 smb_co_gone() at smb_co_gone+0x38 smb_sm_lookup() at smb_sm_lookup+0xfe smb_usr_lookup() at smb_usr_lookup+0xcd nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 giant_ioctl() at giant_ioctl+0x75 devfs_ioctl_f() at devfs_ioctl_f+0x76 kern_ioctl() at kern_ioctl+0x92 ioctl() at ioctl+0xfd syscall() at syscall+0x1bf Xfast_syscall() at Xfast_syscall+0xab --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = 0x7fffffffe048, rbp = 0x7fffffffe460 --- Thanks, Yuri From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 16:35:21 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE2E81065677 for ; Sun, 2 Nov 2008 16:35:21 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 8D1E98FC0A for ; Sun, 2 Nov 2008 16:35:21 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id mA2GAvHi028213; Sun, 2 Nov 2008 10:10:58 -0600 (CST) (envelope-from stephen@math.missouri.edu) Message-ID: <490DD114.3000901@math.missouri.edu> Date: Sun, 02 Nov 2008 10:11:00 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.8.1.17) Gecko/20081023 SeaMonkey/1.1.12 MIME-Version: 1.0 To: kerneljack@kerneljack.com References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 16:35:21 -0000 FreeBSD CURRENT has a different approach to wireless cards. Somewhere in /etc/rc.conf you need lines like wlans_iwi0="wlan0" and then all future ifconfig command should refer to wlan0 instead of iwi0. I am not sure if this will fix your problem or not, but you must have not done this somewhere, otherwise ifconfig would have listed wlan0 as well as iwi0. If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. I think iwi is already a part of that. Khusro Jaleel wrote: > Hi, > > I'm new to FreeBSD-CURRENT and am having problems getting my wireless > to work on my laptop. It is an old Centrino ASUS laptop with built-in > IPW2200 wireless. I've had no problems getting wireless to work on > this for the past few years now with many flavors of linux and of > course Windows so I'm sure it should also work in FreeBSD without any > issues. > > However, I'm not having much luck. I've followed the instructions in > the Handbook's Wireless page and read the iwi(4) man page and added > the following to my /boot/loader.conf: > > ------------- > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES" > hw.psm.synaptics_support=1 > -------------- > > When I reboot and do a "dmesg | grep iwi" I get: > > ---------- > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > iwi0: mem 0xff9de000-0xff9defff irq 4 > at device 2.0 on pci2 > iwi0: [ITHREAD] > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > ---------- > > Am I forgetting to load the firmware somehow? In /boot/kernel, I see > the following files: > > ----------- > [root@asus ~]# ls -l /boot/kernel/iwi_* > -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko > -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko > -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko > ----------- > > ifconfig: > bge0: flags=8843 metric 0 mtu 1500 > options=9b > ether 00:11:2f:0c:e8:7f > inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 > media: Ethernet autoselect (100baseTX ) > status: active > fwe0: flags=8802 metric 0 mtu 1500 > options=8 > ether 02:e0:18:1b:1f:63 > ch 1 dma -1 > fwip0: flags=8802 metric 0 mtu 1500 > lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 > iwi0: flags=8803 metric 0 mtu 2290 > ether 00:0e:35:0d:7c:65 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > plip0: flags=108810 metric 0 mtu 1500 > lo0: flags=8049 metric 0 mtu 16384 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 > inet6 ::1 prefixlen 128 > inet 127.0.0.1 netmask 0xff000000 > > But if I try to do "ifconfig iwi0 up" I get: > > ---------- > iwi0: timeout waiting for (null) firmware initialization to complete > iwi0: could not load boot firmware (null) > ---------- > > Any help appreciated. Thanks. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 17:53:29 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 438FC1065693; Sun, 2 Nov 2008 17:53:29 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id 3F47E8FC1F; Sun, 2 Nov 2008 17:53:27 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so1757078fgb.35 for ; Sun, 02 Nov 2008 09:53:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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=7XyW/KnpcXkLJ0hL7US7oXjKvf5F9PDjfzskb0rbiYQ=; b=AMRFkcTRrYt/IO90t5p/JXyq6SoET57EbUYzKzdK3TZhM+xswCLg36j1trmjlc/ZmA D1nPxVYuAxl5UL7CcWMHR3BdN+LeJzMWiq0reZ0eoz619afzNObewT5zCeCA/QY+T34K ls2kmW5k5w47vlTZqNXH81uPTgsWOUYEC9dB4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=xrLhQ2LWnk3TATlKDLbbxq5WslZTx/LgdSBnu0Rdgz1SAPgUKgEmQwLJ/MyU7Lw/qv x+w9xgK+4EpT5iV/YTvwq8FP3ZOBQJWL9JjaWu/REOXNMdVhBdnqHx73Piukn6x2xrWn T0nxNJ+DiT1VlRtk0NnwsNZu/D59sVBVbrMqQ= Received: by 10.86.66.19 with SMTP id o19mr10178116fga.18.1225648405145; Sun, 02 Nov 2008 09:53:25 -0800 (PST) Received: by 10.86.78.14 with HTTP; Sun, 2 Nov 2008 09:53:25 -0800 (PST) Message-ID: <3bbf2fe10811020953l29f1a7eesa4f4eeb49f0a2eba@mail.gmail.com> Date: Sun, 2 Nov 2008 18:53:25 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Yuri Pankov" In-Reply-To: <20081102163307.GB1434@darklight.homeunix.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <20081102163307.GB1434@darklight.homeunix.org> X-Google-Sender-Auth: 5dc9fe2f9ed1fc7a Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 17:53:29 -0000 2008/11/2, Yuri Pankov : > On Sun, Nov 02, 2008 at 05:17:18PM +0100, Attilio Rao wrote: > > 2008/11/2, Attilio Rao : > > > 2008/11/2, Yuri Pankov : > > > > > > > Hi, > > > > > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > > > following panic: > > > > > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > > > > > Unread portion of the kernel message buffer: > > > > smb_co_lock: recursive lock for object 1 > > > > panic: Lock (lockmgr) smb_vc not locked @ > > > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > > > cpuid = 0 > > > > KDB: stack backtrace: > > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > > panic() at panic+0x182 > > > > witness_assert() at witness_assert+0x21a > > > > __lockmgr_args() at __lockmgr_args+0x17a > > > > smb_co_put() at smb_co_put+0x76 > > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > > > smb_usr_lookup() at smb_usr_lookup+0xcd > > > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > > > giant_ioctl() at giant_ioctl+0x75 > > > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > > > kern_ioctl() at kern_ioctl+0x92 > > > > ioctl() at ioctl+0xfd > > > > syscall() at syscall+0x1bf > > > > Xfast_syscall() at Xfast_syscall+0xab > > > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > > > Uptime: 6m46s > > > > Physical memory: 2032 MB > > > > > > > > > So, what is happening here is that smb_co_lock() is AFU. > > > Infact looking at the code: > > > int > > > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > > > { > > > ... > > > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > > > (flags & LK_CANRECURSE) == 0) { > > > SMBERROR("recursive lock for object %d\n", cp->co_level); > > > return 0; > > > } > > > ... > > > > Yuri, > > could you please test this fix: > > http://www.freebsd.org/~attilio/netsmb.diff > > > > and report if it works? > > You could get a KASSERT running but this is expected as I want to > > identify on the callers who passes a malformed request and fix it. > > > > Thanks, > > Attilio > > > > > > -- > > Peace can only be achieved by understanding - A. Einstein > > > Thanks, Attilio. > > With this patch system doesn't panic anymore with nonexistent share > names (though I had to comment out smb_co_lockstatus prototype and > function to get rid of -Werror complaints). Still getting a LOR: > > netsmb_dev: loaded > lock order reversal: > 1st 0xffffff0021644008 smb_vc (smb_vc) @ > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:332 > 2nd 0xffffffff81037368 smbsm (smbsm) @ > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:348 > > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > _witness_debugger() at _witness_debugger+0x2e > witness_checkorder() at witness_checkorder+0x81e > __lockmgr_args() at __lockmgr_args+0xc2a > smb_co_lock() at smb_co_lock+0x38 > smb_co_gone() at smb_co_gone+0x38 > > smb_sm_lookup() at smb_sm_lookup+0xfe > smb_usr_lookup() at smb_usr_lookup+0xcd > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > giant_ioctl() at giant_ioctl+0x75 > devfs_ioctl_f() at devfs_ioctl_f+0x76 > kern_ioctl() at kern_ioctl+0x92 > ioctl() at ioctl+0xfd > syscall() at syscall+0x1bf > Xfast_syscall() at Xfast_syscall+0xab > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > 0x7fffffffe048, rbp = 0x7fffffffe460 --- I've updated the patch in order to fix smb_co_lockstatus problem. Could you please stress test it while I investigate the LOR problem? Are you running with INVARIANTS? Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 19:26:00 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 364D81065672; Sun, 2 Nov 2008 19:26:00 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.freebsd.org (Postfix) with ESMTP id D92238FC27; Sun, 2 Nov 2008 19:25:59 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.14.3/8.14.3) with ESMTP id mA2JPvn1098513; Sun, 2 Nov 2008 14:25:57 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA2JPvJB083984; Sun, 2 Nov 2008 14:25:57 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id DEE7A73039; Sun, 2 Nov 2008 14:25:56 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20081102192556.DEE7A73039@freebsd-current.sentex.ca> Date: Sun, 2 Nov 2008 14:25:56 -0500 (EST) X-Virus-Scanned: ClamAV 0.94/8554/Sat Nov 1 23:28:42 2008 clamav-milter version 0.94 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 19:26:00 -0000 TB --- 2008-11-02 18:11:26 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-02 18:11:26 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2008-11-02 18:11:26 - cleaning the object tree TB --- 2008-11-02 18:11:56 - cvsupping the source tree TB --- 2008-11-02 18:11:56 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2008-11-02 18:12:05 - building world (CFLAGS=-O -pipe) TB --- 2008-11-02 18:12:05 - cd /src TB --- 2008-11-02 18:12:05 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 2 18:12:06 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 2 19:25:55 UTC 2008 TB --- 2008-11-02 19:25:55 - generating LINT kernel config TB --- 2008-11-02 19:25:55 - cd /src/sys/powerpc/conf TB --- 2008-11-02 19:25:55 - /usr/bin/make -B LINT TB --- 2008-11-02 19:25:55 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-02 19:25:55 - cd /src TB --- 2008-11-02 19:25:55 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 2 19:25:55 UTC 2008 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/powerpc/conf; PATH=/obj/powerpc/src/tmp/legacy/usr/sbin:/obj/powerpc/src/tmp/legacy/usr/bin:/obj/powerpc/src/tmp/legacy/usr/games:/obj/powerpc/src/tmp/usr/sbin:/obj/powerpc/src/tmp/usr/bin:/obj/powerpc/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/powerpc/src/sys/LINT /src/sys/powerpc/conf/LINT WARNING: duplicate option `GEOM_PART_APM' encountered. WARNING: duplicate option `GEOM_PART_MBR' encountered. WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. /src/sys/powerpc/conf/LINT: unknown option "RL_TWISTER_ENABLE" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-02 19:25:56 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-02 19:25:56 - ERROR: failed to build lint kernel TB --- 2008-11-02 19:25:56 - tinderbox aborted TB --- 3170.28 user 368.91 system 4470.08 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 20:18:59 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9E6810656B2; Sun, 2 Nov 2008 20:18:59 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 9668D8FC14; Sun, 2 Nov 2008 20:18:59 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA2KIu8d017876; Sun, 2 Nov 2008 15:18:56 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA2KIuNI023785; Sun, 2 Nov 2008 15:18:56 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1C6FF73039; Sun, 2 Nov 2008 15:18:56 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20081102201856.1C6FF73039@freebsd-current.sentex.ca> Date: Sun, 2 Nov 2008 15:18:56 -0500 (EST) X-Virus-Scanned: ClamAV 0.94/8554/Sat Nov 1 23:28:42 2008 clamav-milter version 0.94 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 20:19:00 -0000 TB --- 2008-11-02 19:09:11 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-02 19:09:11 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-02 19:09:11 - cleaning the object tree TB --- 2008-11-02 19:09:41 - cvsupping the source tree TB --- 2008-11-02 19:09:41 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-02 19:09:48 - building world (CFLAGS=-O -pipe) TB --- 2008-11-02 19:09:48 - cd /src TB --- 2008-11-02 19:09:48 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 2 19:09:50 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 2 20:18:55 UTC 2008 TB --- 2008-11-02 20:18:55 - generating LINT kernel config TB --- 2008-11-02 20:18:55 - cd /src/sys/sparc64/conf TB --- 2008-11-02 20:18:55 - /usr/bin/make -B LINT TB --- 2008-11-02 20:18:55 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-02 20:18:55 - cd /src TB --- 2008-11-02 20:18:55 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 2 20:18:55 UTC 2008 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/sparc64/conf; PATH=/obj/sparc64/src/tmp/legacy/usr/sbin:/obj/sparc64/src/tmp/legacy/usr/bin:/obj/sparc64/src/tmp/legacy/usr/games:/obj/sparc64/src/tmp/usr/sbin:/obj/sparc64/src/tmp/usr/bin:/obj/sparc64/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/sparc64/src/sys/LINT /src/sys/sparc64/conf/LINT WARNING: duplicate option `GEOM_BSD' encountered. WARNING: duplicate option `GEOM_SUNLABEL' encountered. WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. WARNING: duplicate option `SUNKBD_EMULATE_ATKBD' encountered. /src/sys/sparc64/conf/LINT: unknown option "RL_TWISTER_ENABLE" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-02 20:18:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-02 20:18:55 - ERROR: failed to build lint kernel TB --- 2008-11-02 20:18:55 - tinderbox aborted TB --- 2970.84 user 364.32 system 4184.88 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 20:32:17 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8D541065672; Sun, 2 Nov 2008 20:32:17 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 8EE0C8FC0A; Sun, 2 Nov 2008 20:32:17 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA2KWFYR018851; Sun, 2 Nov 2008 15:32:15 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA2KWFOX033011; Sun, 2 Nov 2008 15:32:15 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 60C4173039; Sun, 2 Nov 2008 15:32:15 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20081102203215.60C4173039@freebsd-current.sentex.ca> Date: Sun, 2 Nov 2008 15:32:15 -0500 (EST) X-Virus-Scanned: ClamAV 0.94/8554/Sat Nov 1 23:28:42 2008 clamav-milter version 0.94 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sun4v X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 20:32:17 -0000 TB --- 2008-11-02 19:25:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-02 19:25:56 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-02 19:25:56 - cleaning the object tree TB --- 2008-11-02 19:26:22 - cvsupping the source tree TB --- 2008-11-02 19:26:22 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-02 19:26:30 - building world (CFLAGS=-O -pipe) TB --- 2008-11-02 19:26:30 - cd /src TB --- 2008-11-02 19:26:30 - /usr/bin/make -B buildworld >>> World build started on Sun Nov 2 19:26:31 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Nov 2 20:32:15 UTC 2008 TB --- 2008-11-02 20:32:15 - generating LINT kernel config TB --- 2008-11-02 20:32:15 - cd /src/sys/sun4v/conf TB --- 2008-11-02 20:32:15 - /usr/bin/make -B LINT TB --- 2008-11-02 20:32:15 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-02 20:32:15 - cd /src TB --- 2008-11-02 20:32:15 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 2 20:32:15 UTC 2008 >>> stage 1: configuring the kernel -------------------------------------------------------------- cd /src/sys/sun4v/conf; PATH=/obj/sun4v/src/tmp/legacy/usr/sbin:/obj/sun4v/src/tmp/legacy/usr/bin:/obj/sun4v/src/tmp/legacy/usr/games:/obj/sun4v/src/tmp/usr/sbin:/obj/sun4v/src/tmp/usr/bin:/obj/sun4v/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d /obj/sun4v/src/sys/LINT /src/sys/sun4v/conf/LINT WARNING: duplicate option `GEOM_BSD' encountered. WARNING: duplicate option `GEOM_SUNLABEL' encountered. WARNING: duplicate option `DEV_MEM' encountered. WARNING: duplicate device `mem' encountered. /src/sys/sun4v/conf/LINT: unknown option "RL_TWISTER_ENABLE" *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-02 20:32:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-02 20:32:15 - ERROR: failed to build lint kernel TB --- 2008-11-02 20:32:15 - tinderbox aborted TB --- 2957.13 user 363.23 system 3978.42 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 20:45:49 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 71AE1106567B for ; Sun, 2 Nov 2008 20:45:49 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id EEF768FC1B for ; Sun, 2 Nov 2008 20:45:46 +0000 (UTC) (envelope-from yuri.pankov@gmail.com) Received: by ey-out-2122.google.com with SMTP id 6so689715eyi.7 for ; Sun, 02 Nov 2008 12:45:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received :x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=Fga0IzX4kjY+1XdCszPCJSpPVQwmaqWDh9rRpUh6Zg0=; b=kDCDcVNQvanMcDePQB0yUW2fwUScgwLvmzcjrHB9kER+iwMPzJnILMT5YcrZBRq6y0 YH5ggDqpx/WPAwy8E8YVdZNdfmo2a4wfGcpH2siHcCe4OUA2txrMupa/7a8efYwbOhoH 6yhQaHvq7aGcyzmkZbEGVGjn2zQI/MDjLLOdg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=x-authentication-warning:date:from:to:cc:subject:message-id :references:mime-version:content-type:content-disposition :in-reply-to:user-agent; b=g5upUqeFJ7/B2I4HWhG9Qd1Nb386CAiYb878hvLSkeOoqNl53PvZwRVflFUTncw0cq ZpZJEI1IL7/Qnq8r/x/3p0hLkQ5xat1lf1IaGIfKHkTJMsTBb21P5FN19R+krO4X5IWY oNe+eMCVrf7TP7rIAgxdMQjX+5o10vQDGD9AA= Received: by 10.210.22.16 with SMTP id 16mr3599199ebv.132.1225657340829; Sun, 02 Nov 2008 12:22:20 -0800 (PST) Received: from darklight.homeunix.org ([85.175.24.53]) by mx.google.com with ESMTPS id u14sm12348777gvf.6.2008.11.02.12.22.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 02 Nov 2008 12:22:20 -0800 (PST) Received: from darklight.homeunix.org (yuri@darklight.homeunix.org [127.0.0.1]) by darklight.homeunix.org (8.14.3/8.14.3) with ESMTP id mA2KMChr006700; Sun, 2 Nov 2008 23:22:17 +0300 (MSK) (envelope-from yuri.pankov@gmail.com) Received: (from yuri@localhost) by darklight.homeunix.org (8.14.3/8.14.3/Submit) id mA2KMB3n006698; Sun, 2 Nov 2008 23:22:11 +0300 (MSK) (envelope-from yuri.pankov@gmail.com) X-Authentication-Warning: darklight.homeunix.org: yuri set sender to yuri.pankov@gmail.com using -f Date: Sun, 2 Nov 2008 23:22:11 +0300 From: Yuri Pankov To: Attilio Rao Message-ID: <20081102202211.GA1549@darklight.homeunix.org> References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <20081102163307.GB1434@darklight.homeunix.org> <3bbf2fe10811020953l29f1a7eesa4f4eeb49f0a2eba@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3bbf2fe10811020953l29f1a7eesa4f4eeb49f0a2eba@mail.gmail.com> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 20:45:49 -0000 On Sun, Nov 02, 2008 at 06:53:25PM +0100, Attilio Rao wrote: > 2008/11/2, Yuri Pankov : > > On Sun, Nov 02, 2008 at 05:17:18PM +0100, Attilio Rao wrote: > > > 2008/11/2, Attilio Rao : > > > > 2008/11/2, Yuri Pankov : > > > > > > > > > Hi, > > > > > > > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > > > > following panic: > > > > > > > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > > > > > > > Unread portion of the kernel message buffer: > > > > > smb_co_lock: recursive lock for object 1 > > > > > panic: Lock (lockmgr) smb_vc not locked @ > > > > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > > > > cpuid = 0 > > > > > KDB: stack backtrace: > > > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > > > panic() at panic+0x182 > > > > > witness_assert() at witness_assert+0x21a > > > > > __lockmgr_args() at __lockmgr_args+0x17a > > > > > smb_co_put() at smb_co_put+0x76 > > > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > > > > smb_usr_lookup() at smb_usr_lookup+0xcd > > > > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > > > > giant_ioctl() at giant_ioctl+0x75 > > > > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > > > > kern_ioctl() at kern_ioctl+0x92 > > > > > ioctl() at ioctl+0xfd > > > > > syscall() at syscall+0x1bf > > > > > Xfast_syscall() at Xfast_syscall+0xab > > > > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > > > > Uptime: 6m46s > > > > > Physical memory: 2032 MB > > > > > > > > > > > > So, what is happening here is that smb_co_lock() is AFU. > > > > Infact looking at the code: > > > > int > > > > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > > > > { > > > > ... > > > > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > > > > (flags & LK_CANRECURSE) == 0) { > > > > SMBERROR("recursive lock for object %d\n", cp->co_level); > > > > return 0; > > > > } > > > > ... > > > > > > Yuri, > > > could you please test this fix: > > > http://www.freebsd.org/~attilio/netsmb.diff > > > > > > and report if it works? > > > You could get a KASSERT running but this is expected as I want to > > > identify on the callers who passes a malformed request and fix it. > > > > > > Thanks, > > > Attilio > > > > > > > > > -- > > > Peace can only be achieved by understanding - A. Einstein > > > > > > Thanks, Attilio. > > > > With this patch system doesn't panic anymore with nonexistent share > > names (though I had to comment out smb_co_lockstatus prototype and > > function to get rid of -Werror complaints). Still getting a LOR: > > > > netsmb_dev: loaded > > lock order reversal: > > 1st 0xffffff0021644008 smb_vc (smb_vc) @ > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:332 > > 2nd 0xffffffff81037368 smbsm (smbsm) @ > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:348 > > > > KDB: stack backtrace: > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > > _witness_debugger() at _witness_debugger+0x2e > > witness_checkorder() at witness_checkorder+0x81e > > __lockmgr_args() at __lockmgr_args+0xc2a > > smb_co_lock() at smb_co_lock+0x38 > > smb_co_gone() at smb_co_gone+0x38 > > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > smb_usr_lookup() at smb_usr_lookup+0xcd > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > giant_ioctl() at giant_ioctl+0x75 > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > kern_ioctl() at kern_ioctl+0x92 > > ioctl() at ioctl+0xfd > > syscall() at syscall+0x1bf > > Xfast_syscall() at Xfast_syscall+0xab > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > > 0x7fffffffe048, rbp = 0x7fffffffe460 --- > > I've updated the patch in order to fix smb_co_lockstatus problem. > Could you please stress test it while I investigate the LOR problem? Not sure what do you mean by "stress test". I've tried mounting several different shares and copied ~100Gb from them, hope this should suffice. > Are you running with INVARIANTS? Yes. > > Thanks, > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein Thanks, Yuri From owner-freebsd-current@FreeBSD.ORG Sun Nov 2 23:15:03 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57362106568D for ; Sun, 2 Nov 2008 23:15:03 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 066678FC0A for ; Sun, 2 Nov 2008 23:15:02 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so831418ywe.13 for ; Sun, 02 Nov 2008 15:15:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=d393E+xO+lGYAZDvqHlD7aTZJA9kktJpVfmg6H/IrBE=; b=x6as4v/Xnh8UbFRrw5Fn4P9QX5ZTQ8n1SFmaMPdbL9fz/qigf0aYgL35AVNocykzVV /LkTUKF75SoXoHiZe3i2A6foeUEsu0f3dcbYu876REChF8ooRg1LSrvZdRlSmR289Ue8 IiAGTeT2OqifXNjlvBek9jXF+TYmYi3hZv1Ps= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=LZzNgSAFICTJH7QY4KMPJ+5z8xc4Os+7WdV3woXjZHcKCM5XX57r+IZbRp9ndaWvmG ZthiGhSSKczDBYrtEeOUUMgvk7xrKjOWRi42+6MlMbYDvx7O85rKDUFakG0yMMb24sHn Trd4NzqVL4yqXUOylUqJsCRYw1VuVTFDgslk8= Received: by 10.150.155.4 with SMTP id c4mr2038761ybe.107.1225667702162; Sun, 02 Nov 2008 15:15:02 -0800 (PST) Received: from ?10.0.3.231? (pool-70-111-21-88.nwrk.east.verizon.net [70.111.21.88]) by mx.google.com with ESMTPS id 7sm5679905ywo.7.2008.11.02.15.15.00 (version=SSLv3 cipher=RC4-MD5); Sun, 02 Nov 2008 15:15:01 -0800 (PST) From: "Alexandre \"Sunny\" Kovalenko" To: John Nielsen In-Reply-To: <200811011517.37640.lists@jnielsen.net> References: <20081101114717.0ffc2ec8@valhala> <200811011517.37640.lists@jnielsen.net> Content-Type: text/plain; charset=utf-8 Date: Sun, 02 Nov 2008 18:14:30 -0500 Message-Id: <1225667670.12521.7.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: Nicolas Martyanoff , freebsd-current@freebsd.org Subject: Re: ZFS for a desktop computer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Nov 2008 23:15:03 -0000 On Sat, 2008-11-01 at 15:17 -0400, John Nielsen wrote: > On Saturday 01 November 2008, Nicolas Martyanoff wrote: > > I'm thinking about switching my main desktop to FreeBSD for various > > reasons (main one, I love it on my laptop and server), and I've been > > considering using ZFS. I'd like to have a disk-modular system, ie.: > > > > - Being able to have mirroring. > > - Being able to add new disks without effort. > > - Being able to add new disks AND mirroring disks (spare disks ?) at > > the same time. > > > > I'm gonna begin with 2x 1TB disks with mirroring, and I'd like to be > > able to add, if needed, new disks, for example 2x 1.5TB to get 2.5TB > > diskspace fully mirrored. The whole process shouldn't need to reinstall > > the system, or to change the slice/partition layout, ie. be totally > > transparent for the data. > > And for this particular need, ZFS seems to be the way to go. > > I'm happily using ZFS on a 32-bit FreeBSD desktop system (that also plays a > home server role). It should meet your disk-modularity requirements above, > with the exception that it's not possible to add disks to a raidZ set > (though it is possible to add additional sets to the same zpool). > > > However, I'm a bit worried about FreeBSD's ZFS implementation: > > > > - I've got a 64bits dual core 2GHz CPU, but can't use an amd64 FreeBSD > > since Xen, NVidia drivers and wine don't work on it; but ZFS is said > > to be unsuitable for i386. > > That's overstating the case. The extra memory headroom on amd64 may make > things simpler, but it's certianly possible to run ZFS on FreeBSD i386 as > long as you have a couple gigs of RAM (I actually only have 1.5 GB) and > follow the tuning guidelines. You should also be willing to monitor your > system and go through one or two fine-tuning cycles Just a "me too". I am using ZFS on my i386 (Core Duo) laptop: / and /boot are UFS2, /usr and /home are ZFS. Main appeal in my case was the startup time after the panic -- doing fsck on 120GB /home was not fun. I have to admit that machine has 3GB of real memory in it, though. -- Alexandre "Sunny" Kovalenko (Олександр Коваленко) From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 01:49:48 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74EDE1065674; Mon, 3 Nov 2008 01:49:48 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmmtao102.cox.net (eastrmmtao102.cox.net [68.230.240.8]) by mx1.freebsd.org (Postfix) with ESMTP id 124618FC13; Mon, 3 Nov 2008 01:49:47 +0000 (UTC) (envelope-from conrads@cox.net) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmmtao102.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20081103014947.USUP19960.eastrmmtao102.cox.net@eastrmimpo02.cox.net>; Sun, 2 Nov 2008 20:49:47 -0500 Received: from serene.no-ip.org ([72.204.148.162]) by eastrmimpo02.cox.net with bizsmtp id aRpn1a0043WU3WG02RpnSc; Sun, 02 Nov 2008 20:49:47 -0500 X-Authority-Analysis: v=1.0 c=1 a=JnPxh0cO4EMMECSa5rUA:9 a=O0Mn-W00xr2zs9R1FeO5LOKUvJ8A:4 a=4vB-4DCPJfMA:10 a=gi0PWCVxevcA:10 X-CM-Score: 0.00 Date: Sun, 2 Nov 2008 19:49:47 -0600 From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Message-ID: <20081102194947.031d6896@serene.no-ip.org> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.14.4; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: sos@freebsd.org Subject: More on non-recognized SATA hardware X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 01:49:48 -0000 I just noticed something today in the boot messages that I hadn't noticed before: it appears that my SATA controller is being probed as a RAID controller, but without any driver being attached. Booting a CURRENT snapshot from 11/02, I'm seeing something like: pci0: at PCI 9.0 (no driver attached) Would it be a simple matter of patching one of the existing RAID hardware drivers (ahci, perhaps?) to recognize my specific device? And if so, how can I go about doing this with no existing FreeBSD installation? Or, could somebody do this for me and create a mini-iso, just enough to get me started with a minimal base system? For what it's worth, here's the relevant info from Ubuntu's lspci command: 00:09.0 RAID bus controller: nVidia Corporation Device 0ad8 (rev a2) Subsystem: Hewlett-Packard Company Device 2a6e Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [b0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/3 Enable+ Address: 00000000fee0f00c Data: 41a9 Capabilities: [ec] HyperTransport: MSI Mapping Enable+ Fixed+ Kernel driver in use: ahci Kernel modules: ahci Please help! I've got a serious FreeBSD jones going on here! It's been about two months now since my last computer died and I've been without FreeBSD ever since. Ubuntu is an OK temporary substitute, but I want my FreeBSD back! :-) Thanks! -- Conrad J. Sabatier From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 03:00:20 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30318106568B; Mon, 3 Nov 2008 03:00:20 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id AB84D8FC21; Mon, 3 Nov 2008 03:00:19 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA330Fd9038981; Sun, 2 Nov 2008 22:00:17 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id mA330FoV060561; Sun, 2 Nov 2008 22:00:15 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 4D73273039; Sun, 2 Nov 2008 22:00:15 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20081103030015.4D73273039@freebsd-current.sentex.ca> Date: Sun, 2 Nov 2008 22:00:15 -0500 (EST) X-Virus-Scanned: ClamAV 0.94/8556/Sun Nov 2 18:57:48 2008 clamav-milter version 0.94 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 03:00:20 -0000 TB --- 2008-11-03 01:49:36 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-03 01:49:36 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2008-11-03 01:49:36 - cleaning the object tree TB --- 2008-11-03 01:49:58 - cvsupping the source tree TB --- 2008-11-03 01:49:58 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2008-11-03 01:50:04 - building world (CFLAGS=-O -pipe) TB --- 2008-11-03 01:50:04 - cd /src TB --- 2008-11-03 01:50:04 - /usr/bin/make -B buildworld >>> World build started on Mon Nov 3 01:50:09 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Nov 3 03:00:13 UTC 2008 TB --- 2008-11-03 03:00:13 - generating LINT kernel config TB --- 2008-11-03 03:00:13 - cd /src/sys/sparc64/conf TB --- 2008-11-03 03:00:13 - /usr/bin/make -B LINT TB --- 2008-11-03 03:00:13 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-03 03:00:13 - cd /src TB --- 2008-11-03 03:00:13 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 3 03:00:13 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] ===> aio (cleandir) rm -f export_syms aio.ko aio.kld vfs_aio.o opt_vfs_aio.h vnode_if.h vnode_if_newproto.h vnode_if_typedef.h rm -f @ machine rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> amr (cleandir) rm -f export_syms amr.ko amr.kld amr.o amr_pci.o amr_disk.o pci_if.h bus_if.h device_if.h ===> amr/amr_cam (clean) cd: can't cd to /src/sys/modules/amr/amr_cam *** Error code 2 Stop in /src/sys/modules/amr. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-03 03:00:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-03 03:00:15 - ERROR: failed to build lint kernel TB --- 2008-11-03 03:00:15 - tinderbox aborted TB --- 2972.62 user 362.02 system 4238.88 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 03:35:09 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DCDF1065686; Mon, 3 Nov 2008 03:35:09 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id 1A64E8FC1D; Mon, 3 Nov 2008 03:35:08 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA33Z7LQ040708; Sun, 2 Nov 2008 22:35:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.14.3/8.14.3) with ESMTP id mA33Z6Gf038789; Sun, 2 Nov 2008 22:35:06 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id E3E2473039; Sun, 2 Nov 2008 22:35:06 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20081103033506.E3E2473039@freebsd-current.sentex.ca> Date: Sun, 2 Nov 2008 22:35:06 -0500 (EST) X-Virus-Scanned: ClamAV 0.94/8556/Sun Nov 2 18:57:48 2008 clamav-milter version 0.94 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sun4v X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 03:35:09 -0000 TB --- 2008-11-03 02:33:11 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-03 02:33:11 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2008-11-03 02:33:11 - cleaning the object tree TB --- 2008-11-03 02:33:28 - cvsupping the source tree TB --- 2008-11-03 02:33:28 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2008-11-03 02:33:36 - building world (CFLAGS=-O -pipe) TB --- 2008-11-03 02:33:36 - cd /src TB --- 2008-11-03 02:33:36 - /usr/bin/make -B buildworld >>> World build started on Mon Nov 3 02:33:38 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Mon Nov 3 03:35:05 UTC 2008 TB --- 2008-11-03 03:35:05 - generating LINT kernel config TB --- 2008-11-03 03:35:05 - cd /src/sys/sun4v/conf TB --- 2008-11-03 03:35:05 - /usr/bin/make -B LINT TB --- 2008-11-03 03:35:05 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-03 03:35:05 - cd /src TB --- 2008-11-03 03:35:05 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 3 03:35:05 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] ===> aio (cleandir) rm -f export_syms aio.ko aio.kld vfs_aio.o opt_vfs_aio.h vnode_if.h vnode_if_newproto.h vnode_if_typedef.h rm -f @ machine sparc64 rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> amr (cleandir) rm -f export_syms amr.ko amr.kld amr.o amr_pci.o amr_disk.o pci_if.h bus_if.h device_if.h ===> amr/amr_cam (clean) cd: can't cd to /src/sys/modules/amr/amr_cam *** Error code 2 Stop in /src/sys/modules/amr. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sun4v/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-03 03:35:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-03 03:35:06 - ERROR: failed to build lint kernel TB --- 2008-11-03 03:35:06 - tinderbox aborted TB --- 2936.71 user 358.66 system 3715.55 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 05:25:48 2008 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02DC6106568F; Mon, 3 Nov 2008 05:25:48 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.freebsd.org (Postfix) with ESMTP id BD0B08FC0A; Mon, 3 Nov 2008 05:25:47 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA35Pja5045007; Mon, 3 Nov 2008 00:25:45 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.14.3/8.14.3) with ESMTP id mA35PiQr016997; Mon, 3 Nov 2008 00:25:44 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id C884573039; Mon, 3 Nov 2008 00:25:44 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20081103052544.C884573039@freebsd-current.sentex.ca> Date: Mon, 3 Nov 2008 00:25:44 -0500 (EST) X-Virus-Scanned: ClamAV 0.94/8556/Sun Nov 2 18:57:48 2008 clamav-milter version 0.94 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 05:25:48 -0000 TB --- 2008-11-03 03:40:01 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2008-11-03 03:40:01 - starting HEAD tinderbox run for amd64/amd64 TB --- 2008-11-03 03:40:01 - cleaning the object tree TB --- 2008-11-03 03:40:48 - cvsupping the source tree TB --- 2008-11-03 03:40:48 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/HEAD/amd64/amd64/supfile TB --- 2008-11-03 03:40:56 - building world (CFLAGS=-O -pipe) TB --- 2008-11-03 03:40:56 - cd /src TB --- 2008-11-03 03:40:56 - /usr/bin/make -B buildworld >>> World build started on Mon Nov 3 03:40:58 UTC 2008 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Nov 3 05:25:41 UTC 2008 TB --- 2008-11-03 05:25:41 - generating LINT kernel config TB --- 2008-11-03 05:25:41 - cd /src/sys/amd64/conf TB --- 2008-11-03 05:25:41 - /usr/bin/make -B LINT TB --- 2008-11-03 05:25:42 - building LINT kernel (COPTFLAGS=) TB --- 2008-11-03 05:25:42 - cd /src TB --- 2008-11-03 05:25:42 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 3 05:25:42 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree [...] ===> aio (cleandir) rm -f export_syms aio.ko aio.kld vfs_aio.o opt_vfs_aio.h vnode_if.h vnode_if_newproto.h vnode_if_typedef.h rm -f @ machine rm -f .depend GPATH GRTAGS GSYMS GTAGS ===> amr (cleandir) rm -f export_syms amr.ko amr.kld amr.o amr_pci.o amr_disk.o pci_if.h bus_if.h device_if.h ===> amr/amr_cam (clean) cd: can't cd to /src/sys/modules/amr/amr_cam *** Error code 2 Stop in /src/sys/modules/amr. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-11-03 05:25:44 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-11-03 05:25:44 - ERROR: failed to build lint kernel TB --- 2008-11-03 05:25:44 - tinderbox aborted TB --- 4543.31 user 566.83 system 6343.48 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 10:22:13 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05ACB1065673 for ; Mon, 3 Nov 2008 10:22:13 +0000 (UTC) (envelope-from kerneljack@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by mx1.freebsd.org (Postfix) with ESMTP id C99088FC1B for ; Mon, 3 Nov 2008 10:22:12 +0000 (UTC) (envelope-from kerneljack@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2308209rvf.43 for ; Mon, 03 Nov 2008 02:22:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=wT0Zpv9rDAW0IloOGrpF8WMw9d6p0ulXwpfMXVyqlxA=; b=B7Dy31AQMjQvBIgzgukqY37E/Q9ca/6cYuilICFtfYaKHI0EdKhZnOaRop/VUkmL6h 4hSE4R0fEPX56Rxt8qgGBgNhsKASNTveBgpIIQ9mwstVzVsn2eqUoyseErYhpOC8yEsa Yimt8CYqv7vcPRUiLwBZTksMvhio/02Iylths= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=DG3vnQYn8dIQW8rKe0fQJY1zpTSeSzAqxZXhEhGjI6rAkgj1j/LMl7cvdUpqNwACA1 LKsgx1HsHrQQcJ9uBssQBmAY1tUFdDc0+pShRqn/43D3MfXR+hjxWtiNXUUbdvtdIcbC iAAmyepZDpmig7MDKYGUin6ILxX2ZVta7M5l0= Received: by 10.142.44.11 with SMTP id r11mr1756535wfr.178.1225707732524; Mon, 03 Nov 2008 02:22:12 -0800 (PST) Received: by 10.142.156.8 with HTTP; Mon, 3 Nov 2008 02:22:12 -0800 (PST) Message-ID: Date: Mon, 3 Nov 2008 10:22:12 +0000 From: "Khusro Jaleel" To: "Stephen Montgomery-Smith" In-Reply-To: <490DD114.3000901@math.missouri.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <490DD114.3000901@math.missouri.edu> Cc: freebsd-current@freebsd.org Subject: Re: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kerneljack@kerneljack.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 10:22:13 -0000 Thanks for your reply, Stephen, just a few other questions: Am I supposed to download the firmware from somewhere or not? I tried going to /usr/ports/net/iwi-firmware/ and iwi-firmware-kmod and running "make install" but both of them error out saying something about "please run make rmconfig and remove CONTROL" but when I run "make rmconfig" I get "No user-configurable ...." something like that. I'm still not sure whether I need to get the firmware from somewhere or not? I hope you can clarify this. My /boot/kernel has those iwi_bss.ko etc files that I mentioned, but I'm not sure if those are firmware or not? Should I get the firmware from somewhere and put it in /boot/firmware instead? I will try putting those lines /etc/rc.conf tonight and will see what happens. Thanks again. On Sun, Nov 2, 2008 at 4:11 PM, Stephen Montgomery-Smith wrote: > FreeBSD CURRENT has a different approach to wireless cards. Somewhere in > /etc/rc.conf you need lines like > wlans_iwi0="wlan0" > and then all future ifconfig command should refer to wlan0 instead of iwi0. > > I am not sure if this will fix your problem or not, but you must have not > done this somewhere, otherwise ifconfig would have listed wlan0 as well as > iwi0. > > If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. > I think iwi is already a part of that. > > > Khusro Jaleel wrote: >> >> Hi, >> >> I'm new to FreeBSD-CURRENT and am having problems getting my wireless >> to work on my laptop. It is an old Centrino ASUS laptop with built-in >> IPW2200 wireless. I've had no problems getting wireless to work on >> this for the past few years now with many flavors of linux and of >> course Windows so I'm sure it should also work in FreeBSD without any >> issues. >> >> However, I'm not having much luck. I've followed the instructions in >> the Handbook's Wireless page and read the iwi(4) man page and added >> the following to my /boot/loader.conf: >> >> ------------- >> legal.intel_iwi.license_ack=1 >> if_iwi_load="YES" >> wlan_load="YES" >> firmware_load="YES" >> iwi_bss_load="YES" >> iwi_ibss_load="YES" >> iwi_monitor_load="YES" >> hw.psm.synaptics_support=1 >> -------------- >> >> When I reboot and do a "dmesg | grep iwi" I get: >> >> ---------- >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> ---------- >> >> Am I forgetting to load the firmware somehow? In /boot/kernel, I see >> the following files: >> >> ----------- >> [root@asus ~]# ls -l /boot/kernel/iwi_* >> -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko >> -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko >> -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko >> ----------- >> >> ifconfig: >> bge0: flags=8843 metric 0 mtu 1500 >> options=9b >> ether 00:11:2f:0c:e8:7f >> inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 >> media: Ethernet autoselect (100baseTX ) >> status: active >> fwe0: flags=8802 metric 0 mtu 1500 >> options=8 >> ether 02:e0:18:1b:1f:63 >> ch 1 dma -1 >> fwip0: flags=8802 metric 0 mtu 1500 >> lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 >> iwi0: flags=8803 metric 0 mtu 2290 >> ether 00:0e:35:0d:7c:65 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> plip0: flags=108810 metric 0 mtu >> 1500 >> lo0: flags=8049 metric 0 mtu 16384 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 >> inet6 ::1 prefixlen 128 >> inet 127.0.0.1 netmask 0xff000000 >> >> But if I try to do "ifconfig iwi0 up" I get: >> >> ---------- >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> ---------- >> >> Any help appreciated. Thanks. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> >> > > From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 12:40:40 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BA961065670 for ; Mon, 3 Nov 2008 12:40:40 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from hs-out-0708.google.com (hs-out-0708.google.com [64.233.178.251]) by mx1.freebsd.org (Postfix) with ESMTP id 317CE8FC12 for ; Mon, 3 Nov 2008 12:40:40 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by hs-out-0708.google.com with SMTP id 54so1001134hsz.11 for ; Mon, 03 Nov 2008 04:40:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ait3o06GRHgOYShLyxqQwXVMVqf8VDazzK7Xj961krk=; b=pWzhZzOwL/Rd745ATEGhjowHY1YOuIDVlzWWbKS2oieUaTCZr+3vqVarwhnMKUmDXU Y0aIqvxi4rL1VKN74HcRQoQx5zI1J63IlsE0OjK3d87eOE4ZUwSQakFH/sCehKZGner3 LGOfxQyWQ+2Ya468tW8GYmO/LnY4awIzPCeY0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=PdpFmeGLvy3dXbh40HX8d0KATPBSsPiUSgM8Y+P419F/Vfpjc8twwYtEyxTmTvlsHI EuQAIM10bnVA7rj2LpWNe5JaRmcJeL9jgZsjBMiEiYDPTNAnY98m0n3ka9CupG5SP+4D JxuGUz+2fL6gaHODvEje32EEoLeh+999ikQjw= Received: by 10.231.15.205 with SMTP id l13mr514iba.0.1225716038971; Mon, 03 Nov 2008 04:40:38 -0800 (PST) Received: by 10.231.11.72 with HTTP; Mon, 3 Nov 2008 04:40:38 -0800 (PST) Message-ID: <3a142e750811030440u66c6e320sd2f1a414480d27d9@mail.gmail.com> Date: Mon, 3 Nov 2008 13:40:38 +0100 From: "Paul B. Mahol" To: kerneljack@kerneljack.com In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <490DD114.3000901@math.missouri.edu> Cc: Stephen Montgomery-Smith , freebsd-current@freebsd.org Subject: Re: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 12:40:40 -0000 On 11/3/08, Khusro Jaleel wrote: > Thanks for your reply, Stephen, just a few other questions: > > Am I supposed to download the firmware from somewhere or not? > > I tried going to /usr/ports/net/iwi-firmware/ and iwi-firmware-kmod > and running "make install" but both of them error out saying something > about "please run make rmconfig and remove CONTROL" but when I run > "make rmconfig" I get "No user-configurable ...." something like that. > > I'm still not sure whether I need to get the firmware from somewhere > or not? I hope you can clarify this. My /boot/kernel has those > iwi_bss.ko etc files that I mentioned, but I'm not sure if those are > firmware or not? Should I get the firmware from somewhere and put it > in /boot/firmware instead? iwi_bss.ko module and others are firmware for iwi and their Makefiles are located in /sys/modules/iwifw Firmware files are located in: /sys/contrib/dev/iwi/ > I will try putting those lines /etc/rc.conf tonight and will see what > happens. > > Thanks again. > > On Sun, Nov 2, 2008 at 4:11 PM, Stephen Montgomery-Smith > wrote: >> FreeBSD CURRENT has a different approach to wireless cards. Somewhere in >> /etc/rc.conf you need lines like >> wlans_iwi0="wlan0" >> and then all future ifconfig command should refer to wlan0 instead of >> iwi0. >> >> I am not sure if this will fix your problem or not, but you must have not >> done this somewhere, otherwise ifconfig would have listed wlan0 as well as >> iwi0. >> >> If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. >> I think iwi is already a part of that. >> >> >> Khusro Jaleel wrote: >>> >>> Hi, >>> >>> I'm new to FreeBSD-CURRENT and am having problems getting my wireless >>> to work on my laptop. It is an old Centrino ASUS laptop with built-in >>> IPW2200 wireless. I've had no problems getting wireless to work on >>> this for the past few years now with many flavors of linux and of >>> course Windows so I'm sure it should also work in FreeBSD without any >>> issues. >>> >>> However, I'm not having much luck. I've followed the instructions in >>> the Handbook's Wireless page and read the iwi(4) man page and added >>> the following to my /boot/loader.conf: >>> >>> ------------- >>> legal.intel_iwi.license_ack=1 >>> if_iwi_load="YES" >>> wlan_load="YES" >>> firmware_load="YES" >>> iwi_bss_load="YES" >>> iwi_ibss_load="YES" >>> iwi_monitor_load="YES" >>> hw.psm.synaptics_support=1 >>> -------------- >>> >>> When I reboot and do a "dmesg | grep iwi" I get: >>> >>> ---------- >>> iwi0: mem 0xff9de000-0xff9defff irq 4 >>> at device 2.0 on pci2 >>> iwi0: [ITHREAD] >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: mem 0xff9de000-0xff9defff irq 4 >>> at device 2.0 on pci2 >>> iwi0: [ITHREAD] >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: mem 0xff9de000-0xff9defff irq 4 >>> at device 2.0 on pci2 >>> iwi0: [ITHREAD] >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> iwi0: mem 0xff9de000-0xff9defff irq 4 >>> at device 2.0 on pci2 >>> iwi0: [ITHREAD] >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> ---------- >>> >>> Am I forgetting to load the firmware somehow? In /boot/kernel, I see >>> the following files: >>> >>> ----------- >>> [root@asus ~]# ls -l /boot/kernel/iwi_* >>> -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko >>> -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko >>> -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 >>> /boot/kernel/iwi_monitor.ko >>> ----------- >>> >>> ifconfig: >>> bge0: flags=8843 metric 0 mtu >>> 1500 >>> options=9b >>> ether 00:11:2f:0c:e8:7f >>> inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 >>> media: Ethernet autoselect (100baseTX ) >>> status: active >>> fwe0: flags=8802 metric 0 mtu 1500 >>> options=8 >>> ether 02:e0:18:1b:1f:63 >>> ch 1 dma -1 >>> fwip0: flags=8802 metric 0 mtu 1500 >>> lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 >>> iwi0: flags=8803 metric 0 mtu 2290 >>> ether 00:0e:35:0d:7c:65 >>> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >>> status: no carrier >>> plip0: flags=108810 metric 0 >>> mtu >>> 1500 >>> lo0: flags=8049 metric 0 mtu 16384 >>> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 >>> inet6 ::1 prefixlen 128 >>> inet 127.0.0.1 netmask 0xff000000 >>> >>> But if I try to do "ifconfig iwi0 up" I get: >>> >>> ---------- >>> iwi0: timeout waiting for (null) firmware initialization to complete >>> iwi0: could not load boot firmware (null) >>> ---------- >>> >>> Any help appreciated. Thanks. >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to >>> "freebsd-current-unsubscribe@freebsd.org" >>> >>> >> >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 12:49:27 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5EE71065672 for ; Mon, 3 Nov 2008 12:49:27 +0000 (UTC) (envelope-from jonathan@onegoodidea.com) Received: from mailhost.significant-whitespace.com (mailhost.significant-whitespace.com [217.155.157.131]) by mx1.freebsd.org (Postfix) with ESMTP id 8D7508FC19 for ; Mon, 3 Nov 2008 12:49:27 +0000 (UTC) (envelope-from jonathan@onegoodidea.com) Received: from [192.168.150.20] (82-69-101-63.dsl.in-addr.zen.co.uk [82.69.101.63]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jonathan) by mailhost.significant-whitespace.com (Postfix) with ESMTPSA id 15D167FC1F7 for ; Mon, 3 Nov 2008 12:30:48 +0000 (GMT) Message-Id: <3BB3B5B4-D3A7-4A1E-A5F5-3B33B6479154@onegoodidea.com> From: Jonathan Hogg To: FreeBSD Current In-Reply-To: <1225667670.12521.7.camel@RabbitsDen> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 3 Nov 2008 12:30:43 +0000 References: <20081101114717.0ffc2ec8@valhala> <200811011517.37640.lists@jnielsen.net> <1225667670.12521.7.camel@RabbitsDen> X-Mailer: Apple Mail (2.929.2) Subject: Re: ZFS for a desktop computer X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 12:49:27 -0000 On 2 Nov 2008, at 23:14, Alexandre Sunny Kovalenko wrote: > Just a "me too". I am using ZFS on my i386 (Core Duo) laptop: / > and /boot are UFS2, /usr and /home are ZFS. Main appeal in my case was > the startup time after the panic -- doing fsck on 120GB /home was not > fun. I have to admit that machine has 3GB of real memory in it, > though. I have everything except /boot on ZFS on an i386 machine with 2GB of RAM. I've not had any problems. Being able to snapshot the whole system before doing an installworld is a major plus in my view. Not to mention the warm fuzzy feeling one gets from doing a full scrub of 1.5TB of RAIDZ data and knowing it's all clean on disk. I'd be happier still if the more recent ZFS patch had made it into 7.1. It'd be nice for it to make it into CURRENT at least. Is there any news on that? Jonathan From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 16:37:15 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 624141065673 for ; Mon, 3 Nov 2008 16:37:15 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id 0BCF08FC2C for ; Mon, 3 Nov 2008 16:37:14 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Subject:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender; b=IpogtgJi7eXwhj5KZMhcPIkN8ljpcUBLmlnhs/8IQcTfPF15JlW+H49PohnGvy1VbbOY4Gd0jud0R+6gGXDN7ylpOQhwEQJK1OwiHDGmIP+TkQcg9IIofaUxq484To1XfAhXOraaGZ+Uz/viACUSJhzs4XGV6zaAgpw2a1H79pA=; Received: from amnesiac.at.no.dns (dns.ccsem.infn.it [192.135.15.3]) by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1Kx2QS-0002gb-Rm; Mon, 03 Nov 2008 19:37:13 +0300 Date: Mon, 3 Nov 2008 19:37:13 +0300 From: Eygene Ryabinkin To: kerneljack@kerneljack.com Message-ID: <3q3LHpRtXrg+xqcqNOM7j33dNpE@Nxyl89WskzuM4RJ7pF/cdJZbOMo> References: <490DD114.3000901@math.missouri.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="r5Pyd7+fXNt84Ff3" Content-Disposition: inline In-Reply-To: Sender: rea-fbsd@codelabs.ru Cc: Stephen Montgomery-Smith , freebsd-current@freebsd.org Subject: Re: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 16:37:15 -0000 --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Mon, Nov 03, 2008 at 10:22:12AM +0000, Khusro Jaleel wrote: > Am I supposed to download the firmware from somewhere or not? It should be built as a kernel module. In 7.x it is already included to the base system, so there is no need for the port. As written in iwi(4), include the following devices to the kernel configuration, ----- device iwi device pci device wlan device firmware ----- and make sure that the iwifw module is built. If you have no 'makeoptions MODULES_OVERRIDE=3D""' directives in the kernel configuration, then you should already have the module. If not, add the 'iwifw' to the MODULES_OVERRIDE contents. The actual module should be in the /boot/kernel, named iwifw.ko. Your error messages indicate that you likely have no /boot/kernel/iwifw.ko. Of course, your actual mileage may vary. For the custom kernels, make sure that you have some 802.11 stuff included: ----- device wlan_wep # 802.11 WEP support device wlan_ccmp # 802.11 CCMP support device wlan_tkip # 802.11 TKIP support ----- The actual devices depend on your needs, but it is safe to include them all -- you can never know what encryption you'll be using. --=20 Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual =20 )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook=20 {_.-``-' {_/ # --r5Pyd7+fXNt84Ff3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkPKLkACgkQthUKNsbL7YhozwCZAVlxj1lSuPHVDLWhq/9TDT85 BtIAmwaFhOYQbNVIMZ5VW7eio4rRERqJ =uff+ -----END PGP SIGNATURE----- --r5Pyd7+fXNt84Ff3-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 17:23:05 2008 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDD511065718 for ; Mon, 3 Nov 2008 17:23:05 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id A502F8FC08 for ; Mon, 3 Nov 2008 17:23:05 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from bb.ipt.ru ([194.62.233.89]) by services.ipt.ru with esmtp (Exim 4.54 (FreeBSD)) id 1Kx38p-0006n1-VD; Mon, 03 Nov 2008 20:23:04 +0300 To: pyunyh@gmail.com References: <20081030040637.GA78796@cdnetworks.co.kr> <20081030114845.GE78796@cdnetworks.co.kr> From: Boris Samorodov Date: Mon, 03 Nov 2008 20:22:51 +0300 In-Reply-To: <20081030114845.GE78796@cdnetworks.co.kr> (Pyun YongHyeon's message of "Thu\, 30 Oct 2008 20\:48\:45 +0900") Message-ID: <14721476@bb.ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@FreeBSD.org Subject: Re: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 17:23:06 -0000 Pyun YongHyeon writes: > As bruffer pointed out the device name chosen conflicts with other > driver in tree so I renamed it to ale(4).The URL for the driver is > http://people.freebsd.org/~yongari/ale/if_ale.c > http://people.freebsd.org/~yongari/ale/if_alereg.h > http://people.freebsd.org/~yongari/ale/if_alevar.h > http://people.freebsd.org/~yongari/ale/Makefile > or > http://people.freebsd.org/~yongari/ale/ale.20081030.tar.gz > Sorry for confusion. Tested at EeePC-1000, works fine. BIG thank you, much appreciated. Here is some additional info. -- dmesg -- ale0: port 0xec80-0xecff mem 0xfbfc0000-0xfbffffff irq 17 at device 0.0 on pci4 ale0: Reserved 0x40000 bytes for rid 0x10 type 3 at 0xfbfc0000 ale0: PCI device revision : 0x00b0 ale0: Chip id/revision : 0xb002 ale0: 960 Tx FIFO, 1024 Rx FIFO ale0: MSIX count : 0 ale0: MSI count : 1 ale0: attempting to allocate 1 MSI vectors (1 supported) ale0: using IRQ 256 for MSI ale0: Using 1 MSI messages. ale0: Read request size : 512 bytes. ale0: TLP payload size : 128 bytes. ale0: bpf attached ale0: Ethernet address: 00:22:15:91:e7:98 ale0: [MPSAFE] ale0: [FILTER] ale0: link state changed to DOWN ale0: interrupt moderation is 100 us. ale0: link state changed to UP -- pciconf -- ale0@pci0:4:0:0: class=0x020000 card=0x83241043 chip=0x10261969 rev=0xb0 hdr=0x00 vendor = 'Attansic (Now owned by Atheros)' class = network subclass = ethernet -- devinfo -- pci4 ale0 pnpinfo vendor=0x1969 device=0x1026 subvendor=0x1043 subdevice=0x8324 class=0x020000 at slot=0 function=0 Interrupt request lines: 256 I/O ports: 0xec80-0xecff I/O memory addresses: 0xfbfc0000-0xfbffffff miibus0 atphy0 pnpinfo oui=0x1374 model=0x1 rev=0x9 at phyno=0 ----- WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 17:30:51 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B4565106564A for ; Mon, 3 Nov 2008 17:30:51 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id 62E638FC08 for ; Mon, 3 Nov 2008 17:30:51 +0000 (UTC) (envelope-from onemda@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so953347yxb.13 for ; Mon, 03 Nov 2008 09:30:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=g6Ap+NYVP6zth0OkzlOiAtx8AXVMv9mcQjRZq7lKYEI=; b=bwVPvJo2OG4dqW4M1qZcDzGwD3le8qk3HkKIjhhgoJ1JtCGA71szxBRBShf2QEiD8/ 3dMz8DgBuTlcjfh4/X2dZ8MOgaa2kVGe/yi6YUSC5pCvr6EIr+jRouJ9og45+EKqGPz+ +v19tZABcDWoi8ZeZBI9Dwl7GS93r2Wpm7uxc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=sm+ZuI6x7tBl1bfsBnr4EBznLGzp1rIo1r4xbMasl5Cb6C7u6WEqR07sKnLkevQsio uP0qtff3232i8GhNPz2BoOqKzNZbbnmvhpy67Lf+/wSVurvt+w9G2ZL4D35l6gFkQNuO XHrnlc8YWtlV9p0HWRpOoaVEXkHY2BzxTxmoM= Received: by 10.231.38.1 with SMTP id z1mr2931ibd.33.1225733450178; Mon, 03 Nov 2008 09:30:50 -0800 (PST) Received: by 10.231.11.72 with HTTP; Mon, 3 Nov 2008 09:30:50 -0800 (PST) Message-ID: <3a142e750811030930j7916137drfe0c72dc4dfd873a@mail.gmail.com> Date: Mon, 3 Nov 2008 18:30:50 +0100 From: "Paul B. Mahol" To: "Eygene Ryabinkin" In-Reply-To: <3q3LHpRtXrg+xqcqNOM7j33dNpE@Nxyl89WskzuM4RJ7pF/cdJZbOMo> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <490DD114.3000901@math.missouri.edu> <3q3LHpRtXrg+xqcqNOM7j33dNpE@Nxyl89WskzuM4RJ7pF/cdJZbOMo> Cc: kerneljack@kerneljack.com, Stephen Montgomery-Smith , freebsd-current@freebsd.org Subject: Re: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 17:30:51 -0000 On 11/3/08, Eygene Ryabinkin wrote: > Mon, Nov 03, 2008 at 10:22:12AM +0000, Khusro Jaleel wrote: >> Am I supposed to download the firmware from somewhere or not? > > It should be built as a kernel module. In 7.x it is already included > to the base system, so there is no need for the port. > > As written in iwi(4), include the following devices to the kernel > configuration, > ----- > device iwi > device pci > device wlan > device firmware > ----- > and make sure that the iwifw module is built. If you have no > 'makeoptions MODULES_OVERRIDE=""' directives in the kernel > configuration, then you should already have the module. If not, add the > 'iwifw' to the MODULES_OVERRIDE contents. The actual module should be > in the /boot/kernel, named iwifw.ko. OP is using CURRENT where iwifw.ko is split in several files. It is not required to build custom kernel just to have iwi support. > Your error messages indicate that you likely have no /boot/kernel/iwifw.ko. > Of course, your actual mileage may vary. > > For the custom kernels, make sure that you have some 802.11 stuff > included: > ----- > device wlan_wep # 802.11 WEP support > device wlan_ccmp # 802.11 CCMP support > device wlan_tkip # 802.11 TKIP support > ----- > The actual devices depend on your needs, but it is safe to include them > all -- you can never know what encryption you'll be using. > -- More debug output from iwi would be more useful. Something like: # sysctl dev.iwi.0.debug=1 From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 18:35:57 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D83A8106567E for ; Mon, 3 Nov 2008 18:35:57 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (mailrelay.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id 606928FC1C for ; Mon, 3 Nov 2008 18:35:57 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id CDFFDA06B7; Mon, 3 Nov 2008 19:35:54 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id C15DBA06B3; Mon, 3 Nov 2008 19:35:54 +0100 (CET) Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id A368EA0690; Mon, 3 Nov 2008 19:35:54 +0100 (CET) Received: from localhost.my.domain ([132.187.37.59]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.2) with ESMTP id 2008110319355330-11240 ; Mon, 3 Nov 2008 19:35:53 +0100 Received: by localhost.my.domain (sSMTP sendmail emulation); Mon, 3 Nov 2008 19:35:56 +0100 Date: Mon, 3 Nov 2008 19:35:56 +0100 From: Alexey Shuvaev To: Pyun YongHyeon Message-ID: <20081103183556.GA2009@localhost.my.domain> References: <20081015003745.GG14769@cdnetworks.co.kr> MIME-Version: 1.0 In-Reply-To: <20081015003745.GG14769@cdnetworks.co.kr> Organization: Universitaet Wuerzburg User-Agent: Mutt/1.5.18 (2008-05-17) X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.2|August 07, 2008) at 11/03/2008 07:35:53 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.2|August 07, 2008) at 11/03/2008 07:35:54 PM, Serialize complete at 11/03/2008 07:35:54 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Cc: freebsd-current@freebsd.org Subject: Re: Call for testers: fxp(4) WOL X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 18:35:58 -0000 On Wed, Oct 15, 2008 at 09:37:45AM +0900, Pyun YongHyeon wrote: > I've implemented WOL for fxp(4) and it works ok to me. Because > there too many variants of fxp(4) hardwares I'd like to hear > success/failure report before committing attached patch to tree. > It seems that the following Intel 8255x supports WOL. Apparently > 82557 lacks WOL capabillity. > > 82558 > 82559 > 82550 > 82551 > How can one figure out which chip he has? I have relative old Toshiba notebook with integrated intel network card. The system is: FreeBSD localhost.my.domain 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Oct 27 01:25:54 CET 2008 root@localhost.my.domain:/usr/obj/usr/src/sys/GENERIC i386 Here are relevant messages from the verbose boot: fxp0: port 0xdf40-0xdf7f mem 0xfceff000-0xfcefffff irq 11 at device 8.0 on pci2 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfceff000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1031 1179 0001 0042 fxp0: Dynamic Standby mode is disabled miibus0: on fxp0 fxp0: XXX: driver didn't set ifq_maxlen ^^^ Is this something to fix? fxp0: bpf attached fxp0: Ethernet address: xx:xx:xx:xx:xx:xx fxp0: [MPSAFE] fxp0: [ITHREAD] and this is the output from pciconv -lvc: fxp0@pci0:2:8:0: class=0x020000 card=0x00011179 chip=0x10318086 rev=0x42 hdr=0x00 vendor = 'Intel Corporation' device = '82801CAM (ICH3) PRO/100 VE (LOM) Network Connection' class = network subclass = ethernet cap 01[dc] = powerspec 2 supports D0 D1 D2 D3 current D0 It seems that driver changes something, after boot or 'ifconfig fxp0 wol': fxp0: flags=8843 metric 0 mtu 1500 options=2008 and after 'ifconfig fxp0 -wol': fxp0: flags=8843 metric 0 mtu 1500 options=8 However the system seems to honors only the BIOS settings, if I enable WOL in the BIOS the system wakes up from power-down or suspend (to ram) states regardless of fxp settings and with disabled WOL in BIOS it never wakes up. The worse thing I have noticed is if I send WOL packet while the system is running it reliably hangs. It does not panic and switching virtual consoles works (and typing/deleting something in the shell prompt too), but the cooler runs at full power and you can't do anything else. This is both with patched fxp and that from -CURRENT. > If your suspend/resume works on your system you can also wake up > your system in suspend by WOL. > Actually, the system does not wake up from suspended mode properly, either by power button or by WOL packet, but it tries. > Thanks. Thank you, if you need something more (debugging output, testing new patches, digging deeper...) just let me know. Alexey. From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 19:04:46 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 61D2D1065674 for ; Mon, 3 Nov 2008 19:04:46 +0000 (UTC) (envelope-from me@janh.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.freebsd.org (Postfix) with ESMTP id E97C68FC0A for ; Mon, 3 Nov 2008 19:04:45 +0000 (UTC) (envelope-from me@janh.de) Received: from janh.freebsd (f054104127.adsl.alicedsl.de [78.54.104.127]) by mrelayeu.kundenserver.de (node=mrelayeu7) with ESMTP (Nemesis) id 0ML2xA-1Kx4UV3Tuv-00046U; Mon, 03 Nov 2008 19:49:32 +0100 Message-ID: <490F47BE.9080205@janh.de> Date: Mon, 03 Nov 2008 19:49:34 +0100 From: Jan Henrik Sylvester User-Agent: Thunderbird 2.0.0.17 (X11/20080927) MIME-Version: 1.0 To: current-list freebsd References: 20081030114845.GE78796@cdnetworks.co.kr Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+mfqDgJU4hv8L2UbkBlZ26ButKAHQxlBd4lRE UME32TakS/LU0zA9GttvuNwtO37yEf63sfV5Y/yjFWEWmvF6Nh wpO9YGv+O/5SU2Tfvhxgg== X-Mailman-Approved-At: Mon, 03 Nov 2008 19:41:29 +0000 Cc: Boris Samorodov , Pyun YongHyeon Subject: Re: Call for testers: Atheros AR8121(L1E)/AR8113/AR8114(L2E) ethernet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 19:04:46 -0000 Boris wrote: >Pyun YongHyeon writes: > >> As bruffer pointed out the device name chosen conflicts with other >> driver in tree so I renamed it to ale(4).The URL for the driver is >> http://people.freebsd.org/~yongari/ale/if_ale.c >> http://people.freebsd.org/~yongari/ale/if_alereg.h >> http://people.freebsd.org/~yongari/ale/if_alevar.h >> http://people.freebsd.org/~yongari/ale/Makefile >> or >> http://people.freebsd.org/~yongari/ale/ale.20081030.tar.gz >> Sorry for confusion. > >Tested at EeePC-1000, works fine. BIG thank you, much appreciated. I got an Eee PC 1000H, too, with 7.1-BETA2 and just used scp to copy with 11.5MB/s -- much better than wlan for big files. Great! This will probably not go into 7.1-RELEASE, will it? Thanks! Jan Henrik From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 20:56:07 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B61AD1065670 for ; Mon, 3 Nov 2008 20:56:07 +0000 (UTC) (envelope-from rohit.x.tripathi@jpmchase.com) Received: from sj1.jpmchase.com (sj1.jpmchase.com [159.53.110.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7C4BB8FC16 for ; Mon, 3 Nov 2008 20:56:07 +0000 (UTC) (envelope-from rohit.x.tripathi@jpmchase.com) Received: from sj4.svr.bankone.net (sj4.svr.bankone.net [155.180.102.138]) by sj1.jpmchase.com (Switch-3.3.2/Switch-3.3.2) with ESMTP id mA3Kv12g011761 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 3 Nov 2008 15:57:01 -0500 Received: from se8.svr.bankone.net (se8.svr.bankone.net [155.180.234.130]) by sj4.svr.bankone.net (Switch-3.3.2/Switch-3.3.2) with ESMTP id mA3KsuLR007302 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL) for ; Mon, 3 Nov 2008 15:54:56 -0500 Received: from svr.bankone.net (imj1.svr.bankone.net [155.180.50.145]) by se8.svr.bankone.net (Switch-3.1.8/Switch-3.1.7) with ESMTP id mA3Ku0xI014715 for ; Mon, 3 Nov 2008 15:56:01 -0500 Received: from ([169.81.34.42]) by imj1.svr.bankone.net with ESMTP id KP-BRADY.76476477; Mon, 03 Nov 2008 14:55:37 -0600 In-Reply-To: <490F47BE.9080205@janh.de> To: freebsd-current@freebsd.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.4 CCH5 September 12, 2005 Message-ID: From: rohit.x.tripathi@jpmchase.com Date: Mon, 3 Nov 2008 15:55:36 -0500 X-MIMETrack: Serialize by Router on PHLMS133/JPMCHASE(Release 6.5.6FP2|October 17, 2007) at 11/03/2008 15:55:37, Serialize complete at 11/03/2008 15:55:37 Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: ndis fix near? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 20:56:07 -0000 I was quite happy with 7.0 until I found that it doesn't support 4965 AGN card and then switched to CURRENT. Now that ndis isn't working, I want to offer help but know very little about wifi devices and freebsd code to contribute anything. If someone's already working on it, it'll be great to let us know. regards, Rohit P.S. please pardon the lengthy disclaimer below my email..its appended automatically by outgoing servers at my company. ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities. From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 21:03:55 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C58C51065672; Mon, 3 Nov 2008 21:03:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4ED0B8FC12; Mon, 3 Nov 2008 21:03:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [IPv6:::1]) (authenticated bits=0) by server.baldwin.cx (8.14.3/8.14.3) with ESMTP id mA3L3mHm092949; Mon, 3 Nov 2008 16:03:49 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Attilio Rao" Date: Mon, 3 Nov 2008 14:58:42 -0500 User-Agent: KMail/1.9.7 References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> In-Reply-To: <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811031458.42549.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:::1]); Mon, 03 Nov 2008 16:03:49 -0500 (EST) X-Virus-Scanned: ClamAV 0.93.1/8560/Mon Nov 3 14:20:13 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Yuri Pankov , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, developers@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 21:03:55 -0000 On Sunday 02 November 2008 11:17:18 am Attilio Rao wrote: > 2008/11/2, Attilio Rao : > > 2008/11/2, Yuri Pankov : > > > > > Hi, > > > > > > Trying to mount nonexistent smb share with mount_smbfs leads to > > > following panic: > > > > > > # mount_smbfs //yuri@lifebane/blahblah /mnt > > > > > > Unread portion of the kernel message buffer: > > > smb_co_lock: recursive lock for object 1 > > > panic: Lock (lockmgr) smb_vc not locked @ > > > /usr/src/sys/modules/smbfs/../../netsmb/smb_conn.c:329. > > > cpuid = 0 > > > KDB: stack backtrace: > > > db_trace_self_wrapper() at db_trace_self_wrapper+0x2a > > > panic() at panic+0x182 > > > witness_assert() at witness_assert+0x21a > > > __lockmgr_args() at __lockmgr_args+0x17a > > > smb_co_put() at smb_co_put+0x76 > > > smb_sm_lookup() at smb_sm_lookup+0xfe > > > smb_usr_lookup() at smb_usr_lookup+0xcd > > > nsmb_dev_ioctl() at nsmb_dev_ioctl+0x1f6 > > > giant_ioctl() at giant_ioctl+0x75 > > > devfs_ioctl_f() at devfs_ioctl_f+0x76 > > > kern_ioctl() at kern_ioctl+0x92 > > > ioctl() at ioctl+0xfd > > > syscall() at syscall+0x1bf > > > Xfast_syscall() at Xfast_syscall+0xab > > > --- syscall (54, FreeBSD ELF64, ioctl), rip = 0x800939aec, rsp = > > > 0x7fffffffe038, rbp = 0x7fffffffe450 --- > > > Uptime: 6m46s > > > Physical memory: 2032 MB > > > > > > So, what is happening here is that smb_co_lock() is AFU. > > Infact looking at the code: > > int > > smb_co_lock(struct smb_connobj *cp, int flags, struct thread *td) > > { > > ... > > if (smb_co_lockstatus(cp, td) == LK_EXCLUSIVE && > > (flags & LK_CANRECURSE) == 0) { > > SMBERROR("recursive lock for object %d\n", cp->co_level); > > return 0; > > } > > ... > > Yuri, > could you please test this fix: > http://www.freebsd.org/~attilio/netsmb.diff > > and report if it works? > You could get a KASSERT running but this is expected as I want to > identify on the callers who passes a malformed request and fix it. This allows all smb locks to recurse unlike the original code I think. It may be better if smb_vclist was initialized with LK_RECURSE, but not all the other smb locks. Also, in smb_co_addchild() I think you should just replace the existing asserts with appropriate lockmgr_assert() (you could add a smb_co_assert() to preserve the layering) rather than removing assertions altogether. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 21:07:28 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4A1B106564A; Mon, 3 Nov 2008 21:07:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 9BAAB8FC1C; Mon, 3 Nov 2008 21:07:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id 3098B46B03; Mon, 3 Nov 2008 16:07:28 -0500 (EST) Date: Mon, 3 Nov 2008 21:07:28 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: John Baldwin In-Reply-To: <200811031458.42549.jhb@freebsd.org> Message-ID: References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Attilio Rao , Yuri Pankov , freebsd-current@freebsd.org, freebsd-fs@freebsd.org, developers@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 21:07:28 -0000 On Mon, 3 Nov 2008, John Baldwin wrote: >> Yuri, could you please test this fix: >> http://www.freebsd.org/~attilio/netsmb.diff >> >> and report if it works? You could get a KASSERT running but this is >> expected as I want to identify on the callers who passes a malformed >> request and fix it. > > This allows all smb locks to recurse unlike the original code I think. It > may be better if smb_vclist was initialized with LK_RECURSE, but not all the > other smb locks. Also, in smb_co_addchild() I think you should just replace > the existing asserts with appropriate lockmgr_assert() (you could add a > smb_co_assert() to preserve the layering) rather than removing assertions > altogether. My general feeling is that the locking in netsmb needs a bit of cleanup, updating, etc. I'm reluctant to change the underlying primitives (as this patch does) without first clarifying what's going on in the code a layer or two above. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 21:20:06 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DA20106567A; Mon, 3 Nov 2008 21:20:06 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 0E65D8FC14; Mon, 3 Nov 2008 21:20:04 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so2333526fgb.35 for ; Mon, 03 Nov 2008 13:20:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; 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=TA8VijrUjPMwnow6ltL/iEf838fcTkqmMcT11ctPE5s=; b=dw4JktMRvmXUhousKiX2YsaudebigugenOz5Jv5y3eq9jC+BUNpfeLzHfRWpL+pdp7 cuh4iF8Ra0+LpPRkVksVS0/jygjNF7C3uaxmPfKpaOfWyN1thXCP022vmsriwOZAeKCm xk55v2RCuWyWj9o6qIMTIhkoEGY9ZiM5lUy70= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=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=tz9CX3/hdkWTxeISgfoOYqnbSt4luzLJau/CrhGO9wTYkNKeHb4ie5FPNfCLBZUjwW 40mCYKp16qavI8QRM/dMUJHN+xO/y3E6m7TrrVdFpYpKa8BUPEi00loNsgOOs5U+pIID Wy4uUyCG0r7zmQT45KJTrXNN7tkF9VwzE4P3s= Received: by 10.86.23.17 with SMTP id 17mr527417fgw.0.1225747203803; Mon, 03 Nov 2008 13:20:03 -0800 (PST) Received: by 10.86.2.18 with HTTP; Mon, 3 Nov 2008 13:20:03 -0800 (PST) Message-ID: <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> Date: Mon, 3 Nov 2008 22:20:03 +0100 From: "Attilio Rao" Sender: asmrookie@gmail.com To: "Robert Watson" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> X-Google-Sender-Auth: 86ce34cb774d5f9b Cc: Yuri Pankov , freebsd-fs@freebsd.org, freebsd-current@freebsd.org, developers@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 21:20:06 -0000 2008/11/3, Robert Watson : > On Mon, 3 Nov 2008, John Baldwin wrote: > > > > > > > Yuri, could you please test this fix: > http://www.freebsd.org/~attilio/netsmb.diff > > > > > > and report if it works? You could get a KASSERT running but this is > expected as I want to identify on the callers who passes a malformed request > and fix it. > > > > > > > This allows all smb locks to recurse unlike the original code I think. It > may be better if smb_vclist was initialized with LK_RECURSE, but not all the > other smb locks. Also, in smb_co_addchild() I think you should just replace > the existing asserts with appropriate lockmgr_assert() (you could add a > smb_co_assert() to preserve the layering) rather than removing assertions > altogether. > > > > My general feeling is that the locking in netsmb needs a bit of cleanup, > updating, etc. I'm reluctant to change the underlying primitives (as this > patch does) without first clarifying what's going on in the code a layer or > two above. I agree with Robert. We need to make an upper layers analysis and decide what is the best solution for locks. This was a quick hack just to let it not panic when mounting. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 21:23:19 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14DB01065674 for ; Mon, 3 Nov 2008 21:23:19 +0000 (UTC) (envelope-from kerneljack@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.30]) by mx1.freebsd.org (Postfix) with ESMTP id BA7F58FC13 for ; Mon, 3 Nov 2008 21:23:18 +0000 (UTC) (envelope-from kerneljack@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so1005445yxb.13 for ; Mon, 03 Nov 2008 13:23:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=dm6HG7OOpVm4DEXrOXbpMpLKKOmxUt6qjvALUd+KOwU=; b=Ww55S9Cb9eU4LBIP1RgiBVADyFwg1VuqgKxyoErNSvLUrMjrlmDBey+8QnJ43+6mIY 3Bv+dOxdtOiChP7xbAhtQFopYN0UsvhaOWg6Ys34aovs1efCSxaxP2Nl1H1h0EUVEwlr usNli54dfIil8HZnhFOvU1hGpyltbRyek/RpM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=j8KwEYETfSNQu7wKQpJj25E+TZWiHIhyXm6KGJAMPZD2XnCPdZFTNtYT9eeBVKEprq O3KkSkybhcBLoCn09JPxMiQzqcqenpr88liuBmqo4kY2lQX+h2OKL9yvVT/4oSY+GrXD Sek3pctXsHroppX9GPvd49CIWmW9r62JoNTmc= Received: by 10.142.139.14 with SMTP id m14mr297857wfd.207.1225747397563; Mon, 03 Nov 2008 13:23:17 -0800 (PST) Received: by 10.142.156.8 with HTTP; Mon, 3 Nov 2008 13:23:17 -0800 (PST) Message-ID: Date: Mon, 3 Nov 2008 21:23:17 +0000 From: "Khusro Jaleel" To: "Stephen Montgomery-Smith" In-Reply-To: <490DD114.3000901@math.missouri.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <490DD114.3000901@math.missouri.edu> Cc: freebsd-current@freebsd.org Subject: Re: problems configuring wireless using iwi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: kerneljack@kerneljack.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 21:23:19 -0000 Thanks for all your kind replies, Stephen got it right! All I needed to do was add a line like he suggested in /etc/rc.conf and everything just worked straight away after that. No need to get firmware or anything else. I did however manage to completely spontaneously rebooot my laptop by trying to run "/etc/rc.d/netif restart" a few too many times, which I thought should never happen in FreeBSD ... but anyway, all is fine now. Thanks for all your help. On Sun, Nov 2, 2008 at 4:11 PM, Stephen Montgomery-Smith wrote: > FreeBSD CURRENT has a different approach to wireless cards. Somewhere in > /etc/rc.conf you need lines like > wlans_iwi0="wlan0" > and then all future ifconfig command should refer to wlan0 instead of iwi0. > > I am not sure if this will fix your problem or not, but you must have not > done this somewhere, otherwise ifconfig would have listed wlan0 as well as > iwi0. > > If you are new to FreeBSD, you might prefer to use FreeBSD-STABLE instead. > I think iwi is already a part of that. > > > Khusro Jaleel wrote: >> >> Hi, >> >> I'm new to FreeBSD-CURRENT and am having problems getting my wireless >> to work on my laptop. It is an old Centrino ASUS laptop with built-in >> IPW2200 wireless. I've had no problems getting wireless to work on >> this for the past few years now with many flavors of linux and of >> course Windows so I'm sure it should also work in FreeBSD without any >> issues. >> >> However, I'm not having much luck. I've followed the instructions in >> the Handbook's Wireless page and read the iwi(4) man page and added >> the following to my /boot/loader.conf: >> >> ------------- >> legal.intel_iwi.license_ack=1 >> if_iwi_load="YES" >> wlan_load="YES" >> firmware_load="YES" >> iwi_bss_load="YES" >> iwi_ibss_load="YES" >> iwi_monitor_load="YES" >> hw.psm.synaptics_support=1 >> -------------- >> >> When I reboot and do a "dmesg | grep iwi" I get: >> >> ---------- >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> iwi0: mem 0xff9de000-0xff9defff irq 4 >> at device 2.0 on pci2 >> iwi0: [ITHREAD] >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> ---------- >> >> Am I forgetting to load the firmware somehow? In /boot/kernel, I see >> the following files: >> >> ----------- >> [root@asus ~]# ls -l /boot/kernel/iwi_* >> -r-xr-xr-x 1 root wheel 197996 Oct 31 23:56 /boot/kernel/iwi_bss.ko >> -r-xr-xr-x 1 root wheel 190182 Oct 31 23:56 /boot/kernel/iwi_ibss.ko >> -r-xr-xr-x 1 root wheel 194760 Oct 31 23:56 /boot/kernel/iwi_monitor.ko >> ----------- >> >> ifconfig: >> bge0: flags=8843 metric 0 mtu 1500 >> options=9b >> ether 00:11:2f:0c:e8:7f >> inet 192.168.1.70 netmask 0xffffff00 broadcast 192.168.1.255 >> media: Ethernet autoselect (100baseTX ) >> status: active >> fwe0: flags=8802 metric 0 mtu 1500 >> options=8 >> ether 02:e0:18:1b:1f:63 >> ch 1 dma -1 >> fwip0: flags=8802 metric 0 mtu 1500 >> lladdr 0.e0.18.0.3.1b.1f.63.a.2.ff.fe.0.0.0.0 >> iwi0: flags=8803 metric 0 mtu 2290 >> ether 00:0e:35:0d:7c:65 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> plip0: flags=108810 metric 0 mtu >> 1500 >> lo0: flags=8049 metric 0 mtu 16384 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 >> inet6 ::1 prefixlen 128 >> inet 127.0.0.1 netmask 0xff000000 >> >> But if I try to do "ifconfig iwi0 up" I get: >> >> ---------- >> iwi0: timeout waiting for (null) firmware initialization to complete >> iwi0: could not load boot firmware (null) >> ---------- >> >> Any help appreciated. Thanks. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> >> > > From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 22:31:22 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CAAEF1065670 for ; Mon, 3 Nov 2008 22:31:22 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from hpsmtp-eml12.kpnxchange.com (hpsmtp-eml12.KPNXCHANGE.COM [213.75.38.112]) by mx1.freebsd.org (Postfix) with ESMTP id 525538FC14 for ; Mon, 3 Nov 2008 22:31:22 +0000 (UTC) (envelope-from nick@van-laarhoven.org) Received: from hpsmtp-eml06.kpnxchange.com ([213.75.38.106]) by hpsmtp-eml12.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 3 Nov 2008 23:31:20 +0100 Received: from uitsmijter.van-laarhoven.org ([81.207.207.222]) by hpsmtp-eml06.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 3 Nov 2008 23:31:20 +0100 Received: (qmail 14139 invoked by uid 98); 3 Nov 2008 22:31:32 -0000 Received: from 10.251.2.191 (nick@10.251.2.191) by uitsmijter.van-laarhoven.org (envelope-from , uid 82) with qmail-scanner-2.01 (clamdscan: 0.92/5270. f-prot: 4.6.7/3.16.15. spamassassin: 3.2.3. Clear:RC:0(10.251.2.191):SA:0(-1.1/5.0):. Processed in 2.663026 secs); 03 Nov 2008 22:31:32 -0000 X-Spam-Status: No, score=-1.1 required=5.0 X-Spam-Level: Received: from unknown (HELO van-laarhoven.org) (nick@10.251.2.191) by uitsmijter.van-laarhoven.org with SMTP; 3 Nov 2008 22:31:29 -0000 Received: (nullmailer pid 2467 invoked by uid 1001); Mon, 03 Nov 2008 22:31:15 -0000 From: Nick Hibma To: freebsd-current@freebsd.org, kerneljack@kerneljack.com Date: Mon, 3 Nov 2008 23:31:13 +0100 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200811032331.14854.nick@van-laarhoven.org> X-OriginalArrivalTime: 03 Nov 2008 22:31:20.0649 (UTC) FILETIME=[E51D3390:01C93E03] Cc: Subject: Re: problems with wireless using iwi drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 22:31:22 -0000 > ------------- > legal.intel_iwi.license_ack=1 > if_iwi_load="YES" > wlan_load="YES" > firmware_load="YES" > iwi_bss_load="YES" > iwi_ibss_load="YES" > iwi_monitor_load="YES" > hw.psm.synaptics_support=1 > -------------- I don't have any of the iwi_*_load="YES" in my kernel config and it still has loaded the firmware alright. Loading 3 different ones looks wrong to me. 100%|nick@hind:/usr/home/nick % kldstat |grep iwi 16 1 0xc4088000 30000 iwi_bss.ko iwi is in the kernel, as is firmware. Have you installed the iwi-firmware port? I guess you have. Nick From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 22:48:18 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B66D1065673; Mon, 3 Nov 2008 22:48:18 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) Received: from outbound.icp-qv1-irony-out3.iinet.net.au (outbound.icp-qv1-irony-out3.iinet.net.au [203.59.1.148]) by mx1.freebsd.org (Postfix) with ESMTP id D4F898FC08; Mon, 3 Nov 2008 22:48:16 +0000 (UTC) (envelope-from fbsd-fs@mawer.org) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AioBACsHD0nLzq3r/2dsb2JhbAAIzBKDUg X-IronPort-AV: E=Sophos;i="4.33,538,1220198400"; d="scan'208";a="347147185" Received: from unknown (HELO [10.24.1.1]) ([203.206.173.235]) by outbound.icp-qv1-irony-out3.iinet.net.au with ESMTP; 04 Nov 2008 07:18:04 +0900 Message-ID: <490F77ED.9050501@mawer.org> Date: Tue, 04 Nov 2008 09:15:09 +1100 From: Antony Mawer User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: Attilio Rao References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> In-Reply-To: <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 03 Nov 2008 23:03:33 +0000 Cc: freebsd-fs@freebsd.org, developers@freebsd.org, Yuri Pankov , freebsd-current@freebsd.org, Robert Watson Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 22:48:18 -0000 Attilio Rao wrote: > 2008/11/3, Robert Watson : >> On Mon, 3 Nov 2008, John Baldwin wrote: >>>> Yuri, could you please test this fix: >> http://www.freebsd.org/~attilio/netsmb.diff >>>> and report if it works? You could get a KASSERT running but this is >> expected as I want to identify on the callers who passes a malformed request >> and fix it. >>> This allows all smb locks to recurse unlike the original code I think. It >> may be better if smb_vclist was initialized with LK_RECURSE, but not all the >> other smb locks. Also, in smb_co_addchild() I think you should just replace >> the existing asserts with appropriate lockmgr_assert() (you could add a >> smb_co_assert() to preserve the layering) rather than removing assertions >> altogether. >> My general feeling is that the locking in netsmb needs a bit of cleanup, >> updating, etc. I'm reluctant to change the underlying primitives (as this >> patch does) without first clarifying what's going on in the code a layer or >> two above. > > I agree with Robert. > We need to make an upper layers analysis and decide what is the best > solution for locks. > This was a quick hack just to let it not panic when mounting. This probably also applies to NWFS and netncp as well -- I haven't had a chance to test NWFS in 7.x as of yet, but will hope to do so in the coming months... --Antony From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 23:11:39 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87173106564A; Mon, 3 Nov 2008 23:11:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 5B58D8FC1D; Mon, 3 Nov 2008 23:11:39 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTP id EFC5946B09; Mon, 3 Nov 2008 18:11:38 -0500 (EST) Date: Mon, 3 Nov 2008 23:11:38 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Antony Mawer In-Reply-To: <490F77ED.9050501@mawer.org> Message-ID: References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> <490F77ED.9050501@mawer.org> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Yuri Pankov , developers@freebsd.org, Attilio Rao , freebsd-current@freebsd.org, freebsd-fs@freebsd.org Subject: Re: reproducible panic with mount_smbfs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 23:11:39 -0000 On Tue, 4 Nov 2008, Antony Mawer wrote: > This probably also applies to NWFS and netncp as well -- I haven't had a > chance to test NWFS in 7.x as of yet, but will hope to do so in the coming > months... Ah, someone who actually uses netncp and nwfs! I've been trying to keep the ipx/spx code alive and working through the MPSAFE network stack work, but I'm really not set up to test that, let alone the Netware file system parts. Let us know how it goes. The netsmb and netncp code is well-structured, but designed with pre-SMPng locking primitives and network stack in mind, so will need quite a bit of work to pull forwards. As Attilio has already been running into, netsmb has rather intimate knowledge and reliance on some of the more obscure behaviors of lockmgr :-). This is something that will need to be fairly high on the list of things to change. Apple has started doing some of this in their fork of our netsmb code, but there's a lot more to do I think. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 23:20:10 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 14C7E106564A for ; Mon, 3 Nov 2008 23:20:10 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id D2D768FC14 for ; Mon, 3 Nov 2008 23:20:09 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id mA3NK9lZ035114 for ; Mon, 3 Nov 2008 15:20:09 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id mA3NK9U6035110 for freebsd-current@freebsd.org; Mon, 3 Nov 2008 15:20:09 -0800 (PST) (envelope-from sgk) Date: Mon, 3 Nov 2008 15:20:09 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20081103232009.GA3161@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Subject: TTY or SSH character echoing issue X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2008 23:20:10 -0000 With current source of 16 Oct 08, I'm seeing a seemly strange echoing problem when I use ssh to connect from one node in my cluster to another. At the (t)csh command line prompt, I want to execute ~/trunk/cmd. So, I have % ~/trunk/cmd The strange behavior is that the ~ character does not appear on the terminal until after I enter the / character. Any advice at determining whether this a tty or ssh or some other problem would be appreciated. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Nov 3 23:54:18 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AF5F1065678; Mon, 3 Nov 2008 23:54:18 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.170]) by mx1.freebsd.org (Postfix) with ESMTP id 9B0998FC08; Mon, 3 Nov 2008 23:54:17 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so2804911wfg.7 for ; Mon, 03 Nov 2008 15:54:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=yM+FHsPy1csdBkg5frw63cEOGw/gMHch2+S1Ue6Bp/k=; b=nFAUMl5eVcsWHwTE2nMETjfYMB/9dMuusNeCCemd1lBxyoJHn5Ay8e5JeWUCqlD5eQ 8OvidShtWmnOD8H02lXRlITbQmUEuR++CrvI+jKEZh5GM+MXeqyUp7lX0PsJYfiGcaM3 G08Vvicgt6XrFk5HYCe+dhobI5eFxn3N1KHcA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=GHFc8W7m4hrIiUkk1O0OabqlDkdMKEur+ejTFiPBt5Z0t+lzXWtRB9K9KI0LhO2Ig6 jZE/lxJKj9jLoEW1Kb22Hf1POKyYQZxlL5mtYGkIFAHp90zPiXfC+PWOHwogslTIUGVf 0U8yhPtjPH6ke12XqsN2DVSy58C00KvNd7o3M= Received: by 10.142.234.16 with SMTP id g16mr395173wfh.274.1225756457121; Mon, 03 Nov 2008 15:54:17 -0800 (PST) Received: by 10.142.218.14 with HTTP; Mon, 3 Nov 2008 15:54:17 -0800 (PST) Message-ID: <9bbcef730811031554m61bc6762g7f503ad56f0981bd@mail.gmail.com> Date: Tue, 4 Nov 2008 00:54:17 +0100 From: "Ivan Voras" To: "Robert Watson" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20081102123100.GA1434@darklight.homeunix.org> <3bbf2fe10811020737g211dfb3fs54b48e4071db2393@mail.gmail.com> <3bbf2fe10811020817g1409a38ep26c1ee8edf075201@mail.gmail.com> <200811031458.42549.jhb@freebsd.org> <3bbf2fe10811031320o5d977babpe37bcf22836b8d34@mail.gmail.com> <490F77ED.9050501@mawer.org> X-Mailman-Approved-At: Tue, 04 Nov 2008 00:20:32 +0000 Cc: Yuri Pankov , developers@freebsd.org, Attilio Rao , freebsd-current@freebsd.org, freebsd-fs@freebsd.org, Antony Mawer Subject: Re: reproducible panic with mo