From owner-freebsd-net@FreeBSD.ORG Sun Dec 20 13:24:57 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 32A9F1065694 for ; Sun, 20 Dec 2009 13:24:57 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from mail-ew0-f211.google.com (mail-ew0-f211.google.com [209.85.219.211]) by mx1.freebsd.org (Postfix) with ESMTP id B35DC8FC0C for ; Sun, 20 Dec 2009 13:24:56 +0000 (UTC) Received: by ewy3 with SMTP id 3so5228847ewy.13 for ; Sun, 20 Dec 2009 05:24:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=+OAYqcv0hjQZuCbuXHoeJPB7fWA570DqQzsQXwoZqzA=; b=jeWlaSg5P/LFznc5UE8INfi8r1GCJpc2msbZCBebCEAa2FGzlXjoyoBKi19J6ZXiV2 J/6oF+Pi5SI7rOHDVcdEZEaKWq9hasKJo1BawTE4GteWR/CyzCKEKmk4/K+AzoHjHaaq ING25ivrim299r5sm14nisDZwi6DghqMPPCrk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cTxNPtQODTlDdQMwB4WlMFMr76aZ+1M8VS+DI6oP+jaOfFuPwbevvyHjw884jWKeEh eBF8IbmWH2BloCxsZel08nX94dInZrG34ZS8UnDuT2rm4GK+hkkgPyOKW/GBX2dSbEui 9wmMpBVSjsV4wfW3j9P/NG/7+Kboj6/c/izzQ= MIME-Version: 1.0 Received: by 10.213.100.217 with SMTP id z25mr117929ebn.88.1261315495680; Sun, 20 Dec 2009 05:24:55 -0800 (PST) In-Reply-To: References: Date: Sun, 20 Dec 2009 14:24:55 +0100 Message-ID: <3a142e750912200524i3618bf49v6a54ee797667c921@mail.gmail.com> From: Paul B Mahol To: Kurt Buff Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org Subject: Re: 8.0R, AMD64 and wpi is giving me major grief X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2009 13:24:57 -0000 On 12/17/09, Kurt Buff wrote: > Anyone? > > BTW - I dual-boot this with XP, and don't have any issues with > wireless when running that. Also works flawlessly when running wired, > over em0. > > I've just done a BIOS update - I'll be trying that out tomorrow, and > will update this with results. > > Kurt > > On Mon, Dec 14, 2009 at 19:21, Kurt Buff wrote: >> All, >> >> I've got a Lenovo t61 with 4gbytes RAM that is giving me fits. >> >> It's got a 3945abg chip in it, and it's getting really flaky. I can >> boot it up, and work at the console for a while, and that seems to >> work OK, usually. >> >> However, today, when I start up my gui (xfce4), wireless just dies on >> me. For a week before, it would usually run for a while (sometimes >> days) before dying on me and requiring a reboot. >> >> Below is a snippet of /var/log/messages - Does this mean anything to >> anyone? Is there anything I can do to recover once this happens? >> >> Thanks, >> >> Kurt >> >> Dec 14 07:16:43 grimsqueaker kernel: wlan0: Ethernet address: >> 00:1f:3c:4d:e2:55 >> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 1 >> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 3 >> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 4 >> Dec 14 07:16:43 grimsqueaker kernel: microcode alive notification >> version 10e02 alive 1 >> Dec 14 07:16:43 grimsqueaker kernel: microcode alive notification >> version 10e02 alive 1 >> Dec 14 07:16:43 grimsqueaker kernel: wpi_newstate: INIT -> SCAN flags 0x0 >> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: CTRL-EVENT-SCAN-RESULTS >> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: Trying to associate >> with 00:23:69:82:b2:bf (SSID='5705NE197th' freq=2462 MHz) >> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: SCAN -> AUTH flags 0x0 >> Dec 14 07:16:45 grimsqueaker kernel: config chan 11 flags 8005 cck f ofdm >> 15 >> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: AUTH -> ASSOC flags 0x0 >> Dec 14 07:16:45 grimsqueaker kernel: >> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: Associated with >> 00:23:69:82:b2:bf >> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: ASSOC -> RUN flags 0x0 >> Dec 14 07:16:45 grimsqueaker kernel: config chan 11 flags 8035 >> Dec 14 07:16:45 grimsqueaker kernel: wlan0: link state changed to UP >> Dec 14 07:16:45 grimsqueaker kernel: wpi0: need multicast update callback >> Dec 14 07:16:46 grimsqueaker wpa_supplicant[381]: WPA: Key negotiation >> completed with 00:23:69:82:b2:bf [PTK=CCMP GTK=CCMP] >> Dec 14 07:16:46 grimsqueaker wpa_supplicant[381]: CTRL-EVENT-CONNECTED >> - Connection to 00:23:69:82:b2:bf completed (auth) [id=0 id_str=] >> Dec 14 07:16:53 grimsqueaker dhclient: New IP Address (wlan0): >> 192.168.151.104 >> Dec 14 07:16:53 grimsqueaker kernel: wpi0: need multicast update callback >> Dec 14 07:16:53 grimsqueaker kernel: wpi0: need multicast update callback >> Dec 14 07:16:53 grimsqueaker dhclient: New Subnet Mask (wlan0): >> 255.255.255.0 >> Dec 14 07:16:53 grimsqueaker dhclient: New Broadcast Address (wlan0): >> 192.168.151.255 >> Dec 14 07:16:53 grimsqueaker dhclient: New Routers (wlan0): 192.168.151.1 >> Dec 14 07:17:56 grimsqueaker kernel: drm0: on vgapci0 >> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] MSI enabled 1 message(s) >> Dec 14 07:17:56 grimsqueaker kernel: vgapci0: child drm0 requested >> pci_enable_busmaster >> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] AGP at 0xe0000000 256MB >> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] Initialized i915 1.6.0 >> 20080730 >> Dec 14 07:17:57 grimsqueaker kernel: drm0: [ITHREAD] >> Dec 14 07:18:24 grimsqueaker kernel: pid 1424 (xfce4-panel), uid 1001: >> exited on signal 11 (core dumped) >> Dec 14 07:25:43 grimsqueaker wpa_supplicant[381]: WPA: Group rekeying >> completed with 00:23:69:82:b2:bf [GTK=CCMP] >> Dec 14 07:48:38 grimsqueaker kernel: wpi0: device timeout >> Dec 14 07:48:39 grimsqueaker kernel: wpi0: could not set power mode >> Enable all wpi debug messages? -- Paul B Mahol From owner-freebsd-net@FreeBSD.ORG Sun Dec 20 15:46:20 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBA201065672 for ; Sun, 20 Dec 2009 15:46:20 +0000 (UTC) (envelope-from freebsd@insightbb.com) Received: from mxsf00.insightbb.com (mxsf00.insightbb.com [74.128.0.70]) by mx1.freebsd.org (Postfix) with ESMTP id 872C98FC15 for ; Sun, 20 Dec 2009 15:46:20 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.47,427,1257138000"; d="scan'208";a="726877154" Received: from unknown (HELO mxsf10.insightbb.com) ([172.31.249.60]) by mxsf00.insightbb.com with ESMTP; 20 Dec 2009 10:46:15 -0500 X-IronPort-AV: E=Sophos;i="4.47,427,1257138000"; d="scan'208";a="12964890" Received: from unknown (HELO asav01.insightbb.com) ([172.31.249.123]) by mxsf10.insightbb.com with ESMTP; 20 Dec 2009 10:46:15 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsgEAA/VLUvQLicL/2dsb2JhbACBStAvhC4E X-IronPort-AV: E=Sophos;i="4.47,427,1257138000"; d="scan'208";a="238812492" Received: from 208-46-39-11.dia.static.qwest.net (HELO laptop2.stevenfriedrich.org) ([208.46.39.11]) by asavout01.insightbb.com with ESMTP; 20 Dec 2009 10:46:14 -0500 From: Steven Friedrich To: freebsd-net@freebsd.org Date: Sun, 20 Dec 2009 10:46:08 -0500 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; i386; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200912201046.08184.freebsd@insightbb.com> Subject: ap_scan values X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2009 15:46:20 -0000 I've been using a Project Evil Windows ethernet driver wrapped by NDIS. I use wpa, and in /etc/wpa_supplicant.conf, I have the following line: ap_scan=2 Our man page, for wpa_supplicant.conf states that this value should always be 1, but I had to set it to 2 to get it to work. I believe this is because we're using a windows driver so we need to pretend we're running Windows. So I had to set it to 1 when I want to use the bwi driver (new for 8.0) or uath driver. Once I made this change, bwi works. uath still escapes me. I hope someone changes the man page to let people know they need to use 2 when using the NDIS driver. From owner-freebsd-net@FreeBSD.ORG Sun Dec 20 17:32:00 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04AF6106568D for ; Sun, 20 Dec 2009 17:32:00 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.24]) by mx1.freebsd.org (Postfix) with ESMTP id 8F5968FC18 for ; Sun, 20 Dec 2009 17:31:59 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so1163183eyf.9 for ; Sun, 20 Dec 2009 09:31:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=x6GVvem12fxy8ox/FSSrFRNAlz9o0oCaPfWhrZUhydY=; b=HzhEuVzYOcoOrcUgtCPNkLEqHTMKv4+GuP7r1FPxbSht6/s/+nhUdu5wqw/Bnzdlj5 6gkfBUx793E+0SwTi/Sjdnp+qL4XbSDZ4yGAU15wwfrDS3gawVDI08DKxVkTnfikKy4D vPd7hgHxtstMguVFhhBnRphCrV+AOj00JqK14= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hi+8Yb9FcPJvcoEGBYm6fAf/GxHRC9PXbyhkHdrio2D5lM0/ZT0y1Vb/UFdoEWruyV eHRKetmewfFyPCsc01GqWvxb1KBal+XfOy3YGScZw2MrNHHkGqkvd9Mf9R+xcELWTyG0 yKrDxZeS3Kg8vpiWPo9K1N0NdZMPFkBwOZJHU= MIME-Version: 1.0 Received: by 10.213.102.129 with SMTP id g1mr13539581ebo.41.1261330318372; Sun, 20 Dec 2009 09:31:58 -0800 (PST) In-Reply-To: <200912201046.08184.freebsd@insightbb.com> References: <200912201046.08184.freebsd@insightbb.com> Date: Sun, 20 Dec 2009 18:31:58 +0100 Message-ID: <3a142e750912200931y7a48b605wdf8711bcab0ba5aa@mail.gmail.com> From: Paul B Mahol To: Steven Friedrich Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org Subject: Re: ap_scan values X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Dec 2009 17:32:00 -0000 On 12/20/09, Steven Friedrich wrote: > I've been using a Project Evil Windows ethernet driver wrapped by NDIS. > I use wpa, and in /etc/wpa_supplicant.conf, I have the following line: > ap_scan=2 > > Our man page, for wpa_supplicant.conf states that this value should always > be > 1, but I had to set it to 2 to get it to work. I believe this is because > we're > using a windows driver so we need to pretend we're running Windows. > > So I had to set it to 1 when I want to use the bwi driver (new for 8.0) or > uath driver. > > Once I made this change, bwi works. > uath still escapes me. > > I hope someone changes the man page to let people know they need to use 2 > when > using the NDIS driver. I dont use ap_scan at all and it works for me. Using ap_scan=2 is just workaround for buggy/broken scan results. -- Paul B Mahol From owner-freebsd-net@FreeBSD.ORG Mon Dec 21 07:02:30 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 33EFF1065672; Mon, 21 Dec 2009 07:02:30 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E01778FC12; Mon, 21 Dec 2009 07:02:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBL72TMF021757; Mon, 21 Dec 2009 07:02:29 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBL72Tjk021753; Mon, 21 Dec 2009 07:02:29 GMT (envelope-from linimon) Date: Mon, 21 Dec 2009 07:02:29 GMT Message-Id: <200912210702.nBL72Tjk021753@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-i386@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/141741: Etherlink III NIC won't work after upgrade to FBSD 8, If I run tcpdump - it works. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 07:02:30 -0000 Synopsis: Etherlink III NIC won't work after upgrade to FBSD 8, If I run tcpdump - it works. Responsible-Changed-From-To: freebsd-i386->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 21 06:51:14 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). To submitter: what driver detects this card? http://www.freebsd.org/cgi/query-pr.cgi?pr=141741 From owner-freebsd-net@FreeBSD.ORG Mon Dec 21 11:07:01 2009 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06EC6106566B for ; Mon, 21 Dec 2009 11:07:01 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E85FF8FC17 for ; Mon, 21 Dec 2009 11:07:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBLB70ar004161 for ; Mon, 21 Dec 2009 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBLB70OM004159 for freebsd-net@FreeBSD.org; Mon, 21 Dec 2009 11:07:00 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 21 Dec 2009 11:07:00 GMT Message-Id: <200912211107.nBLB70OM004159@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-net@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-net@FreeBSD.org X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 11:07:01 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/141777 net [rum] [patch] Support usbdevs / rum(4) for Buffalo WLI o kern/141741 net Etherlink III NIC won't work after upgrade to FBSD 8, o kern/141720 net [sctp] [lor] [hang] sctp-create vs. sctp-it causes sys o kern/141698 net [sctp] [panic] Own lock on stcb at return from input o kern/141697 net [sctp] [panic] lock (sleep mutex) sctp-tcb not locked o kern/141696 net [rum] [panic] rum(4)+ vimage = kernel panic o kern/141695 net [sctp] [panic] kernel page fault with non-sleepable lo o kern/141646 net [em] em(4) + lagg(4) + vlan(4) generates ISL-tagged fr o kern/141314 net Network Performance has decreased by 30% [regression] o kern/141285 net [em] hangs down/up intel nic during creating vlan o kern/141256 net [iwn] iwn(4) causes page fault on interface up o kern/141023 net [carp] CARP arp replays with wrong src mac o kern/140970 net [bce] The two NetXtreme II BCM5709S NICs on our HP Bl4 o kern/140796 net [ath] [panic] privileged instruction fault o kern/140778 net [em] randomly panic in vlan/em o kern/140742 net rum(4) Two asus-WL167G adapters cannot talk to each ot o kern/140728 net [em] [patch] Fast irq registration in em driver o kern/140684 net [bce] Broadcom NetXtreme II BCM5709 1000Base-T - fail o kern/140647 net [em] [patch] e1000 driver does not correctly handle mu o kern/140634 net [vlan] destroying if_lagg interface with if_vlan membe o kern/140619 net [ifnet] [patch] refine obsolete if_var.h comments desc s kern/140597 net [request] implement Lost Retransmission Detection o kern/140567 net [ath] [patch] ath is not worked on my notebook PC o kern/140564 net [wpi] Problem with Intel(R) PRO/Wireless 3945ABG o kern/140346 net [wlan] High bandwidth use causes loss of wlan connecti o kern/140326 net [em] em0: watchdog timeout when communicating to windo o kern/140245 net [ath] [panic] Kernel panic during network activity on o kern/140142 net [ip6] [panic] FreeBSD 7.2-amd64 panic w/IPv6 o kern/140066 net [bwi] install report for 8.0 RC 2 (multiple problems) o kern/140051 net [bce] [arp] ARP not sent through Bridge Firewall with o kern/140036 net [iwn] [lor] lock order reversal with iwn0_com_lock and o kern/139761 net [bce] bce driver on IBM HS22 [No PHY found on Child MI o kern/139565 net [ipfilter] ipfilter ioctl SIOCDELST broken o kern/139387 net [ipsec] Wrong lenth of PF_KEY messages in promiscuous o bin/139346 net [patch] arp(8) add option to remove static entries lis o kern/139268 net [if_bridge] [patch] allow if_bridge to forward just VL o kern/139204 net [arp] DHCP server replies rejected, ARP entry lost bef o kern/139162 net [fwip] [panic] 8.0-RC1 panics if using IP over firewir o kern/139117 net [lagg] + wlan boot timing (EBUSY) o kern/139079 net [wpi] Failure to attach wpi(4) o kern/139058 net [ipfilter] mbuf cluster leak on FreeBSD 7.2 o kern/138999 net [libc] lighttpd/php-cgi with freebsd sendfile(2) enabl o kern/138850 net [dummynet] dummynet doesn't work correctly on a bridge o kern/138782 net [panic] sbflush_internal: cc 0 || mb 0xffffff004127b00 o kern/138739 net [wpi] wpi(4) does not work very well under 8.0-BETA4 o kern/138694 net [bge] FreeBSD 6.3 release does not recognize Broadcom o amd64/138688 net [rum] possibly broken on 8 Beta 4 amd64: able to wpa a o kern/138678 net [lo] FreeBSD does not assign linklocal address to loop f kern/138666 net [multicast] [panic] not working multicast through igmp o kern/138660 net [igb] igb driver troubles in 8.0-BETA4 o kern/138652 net TCP window scaling value calculated incorrectly? o kern/138620 net [lagg] [patch] lagg port bpf-writes blocked o kern/138427 net [wpi] [panic] Kernel panic after trying set monitor wl o kern/138407 net [gre] gre(4) interface does not come up after reboot o kern/138332 net [tun] [lor] ifconfig tun0 destroy causes LOR on 8.0-BE o kern/138266 net [panic] kernel panic when udp benchmark test used as r o kern/138177 net [ipfilter] FreeBSD crashing repeatedly in ip_nat.c:257 o kern/138046 net [tcp] tcp sockets stay in SYN_SENT even after receivin o kern/137881 net [netgraph] [panic] ng_pppoe fatal trap 12 o bin/137841 net [patch] wpa_supplicant(8) cannot verify SHA256 signed p kern/137795 net [sctp] [panic] mtx_lock() of destroyed mutex o kern/137776 net [rum] panic in rum(4) driver on 8.0-BETA2 o kern/137775 net [netgraph] [patch] Add XMIT_FAILOVER to ng_one2many o bin/137641 net ifconfig(8): various problems with "vlan_device.vlan_i o kern/137592 net [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne o bin/137484 net [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/137392 net [ip] [panic] crash in ip_nat.c line 2577 o kern/137372 net [ral] FreeBSD doesn't support wireless interface from o kern/137317 net [tcp] logs full of syncache problems o kern/137292 net [ste] DFE-580TX not working properly o kern/137279 net [bge] [panic] Page fault (fatal trap 12) NFS server w/ o kern/137089 net [lagg] lagg falsely triggers IPv6 duplicate address de o bin/136994 net [patch] ifconfig(8) print carp mac address o kern/136943 net [wpi] [lor] wpi0_com_lock / wpi0 o kern/136911 net [netgraph] [panic] system panic on kldload ng_bpf.ko t o kern/136876 net [bge] bge will not resume properly after suspend o kern/136836 net [ath] atheros card stops functioning after about 12 ho o kern/136618 net [pf][stf] panic on cloning interface without unit numb o kern/136482 net [age] Attansic L1 Gigabit Ethernet recieves multicasts o kern/136426 net [panic] spawning several dhclients in parallel panics o kern/136168 net [em] em driver initialization fails on Intel 5000PSL m o kern/135836 net [bce] bce BCM5709 Watchdog after warm boot - ok after o kern/135502 net [periodic] Warning message raised by rtfree function i o kern/135222 net [igb] low speed routing between two igb interfaces o kern/135067 net [patch] [fib] Incorrect KASSERTs in sys/net/route.c o kern/134956 net [em] FreeBSD 7.1 & 7.2, Intel PRO/1000 PT Quad Port Se o kern/134931 net [route] [fib] Route messages sent to all socket listen o kern/134658 net [bce] bce driver fails on PowerEdge m610 blade. o kern/134583 net [hang] Machine with jail freezes after random amount o o kern/134531 net [route] [panic] kernel crash related to routes/zebra o kern/134401 net [msk] [panic] Kernel Fatal trap 12: page fault while i o kern/134168 net [ral] ral driver problem on RT2525 2.4GHz transceiver o kern/134157 net [dummynet] dummynet loads cpu for 100% and make a syst o kern/134079 net [em] "em0: Invalid MAC address" in FreeBSD-Current ( 8 o kern/133969 net [dummynet] [panic] Fatal trap 12: page fault while in o kern/133968 net [dummynet] [panic] dummynet kernel panic o kern/133902 net [tun] Killing tun0 iface ssh tunnel causes Panic Strin o kern/133786 net [netinet] [patch] ip_input might cause kernel panic o kern/133736 net [udp] ip_id not protected ... o kern/133613 net [wpi] [panic] kernel panic in wpi(4) o kern/133595 net [panic] Kernel Panic at pcpu.h:195 o kern/133572 net [ppp] [hang] incoming PPTP connection hangs the system o kern/133490 net [bpf] [panic] 'kmem_map too small' panic on Dell r900 o kern/133328 net [bge] [panic] Kernel panics with Windows7 client o kern/133235 net [netinet] [patch] Process SIOCDLIFADDR command incorre o kern/133218 net [carp] [hang] use of carp(4) causes system to freeze f kern/133213 net arp and sshd errors on 7.1-PRERELEASE o kern/133204 net [msk] msk driver timeouts o kern/133060 net [ipsec] [pfsync] [panic] Kernel panic with ipsec + pfs o kern/132991 net [bge] if_bge low performance problem f bin/132911 net ip6fw(8): argument type of fill_icmptypes is wrong and o kern/132889 net [ndis] [panic] NDIS kernel crash on load BCM4321 AGN d o kern/132885 net [wlan] 802.1x broken after SVN rev 189592 o conf/132851 net [fib] [patch] allow to setup fib for service running f o kern/132832 net [netinet] [patch] tcp_output() might generate invalid o bin/132798 net [patch] ggatec(8): ggated/ggatec connection slowdown p o kern/132734 net [ifmib] [panic] panic in net/if_mib.c o kern/132722 net [ath] Wifi ath0 associates fine with AP, but DHCP or I o kern/132705 net [libwrap] [patch] libwrap - infinite loop if hosts.all o kern/132672 net [ndis] [panic] ndis with rt2860.sys causes kernel pani o kern/132669 net [xl] 3c905-TX send DUP! in reply on ping (sometime) o kern/132554 net [ipl] There is no ippool start script/ipfilter magic t o kern/132354 net [nat] Getting some packages to ipnat(8) causes crash o kern/132285 net [carp] alias gives incorrect hash in dmesg o kern/132277 net [crypto] [ipsec] poor performance using cryptodevice f o kern/132107 net [carp] carp(4) advskew setting ignored when carp IP us o kern/131781 net [ndis] ndis keeps dropping the link o kern/131776 net [wi] driver fails to init o kern/131753 net [altq] [panic] kernel panic in hfsc_dequeue o bin/131567 net [socket] [patch] Update for regression/sockets/unix_cm o kern/131549 net ifconfig(8) can't clear 'monitor' mode on the wireless o kern/131536 net [netinet] [patch] kernel does allow manipulation of su o bin/131365 net route(8): route add changes interpretation of network o kern/131162 net [ath] Atheros driver bugginess and kernel crashes o kern/131153 net [iwi] iwi doesn't see a wireless network f kern/131087 net [ipw] [panic] ipw / iwi - no sent/received packets; iw f kern/130820 net [ndis] wpa_supplicant(8) returns 'no space on device' o kern/130628 net [nfs] NFS / rpc.lockd deadlock on 7.1-R o conf/130555 net [rc.d] [patch] No good way to set ipfilter variables a o kern/130525 net [ndis] [panic] 64 bit ar5008 ndisgen-erated driver cau o kern/130311 net [wlan_xauth] [panic] hostapd restart causing kernel pa o kern/130109 net [ipfw] Can not set fib for packets originated from loc f kern/130059 net [panic] Leaking 50k mbufs/hour o kern/129750 net [ath] Atheros AR5006 exits on "cannot map register spa f kern/129719 net [nfs] [panic] Panic during shutdown, tcp_ctloutput: in o kern/129580 net [ndis] Netgear WG311v3 (ndis) causes kenel trap at boo o kern/129517 net [ipsec] [panic] double fault / stack overflow o kern/129508 net [carp] [panic] Kernel panic with EtherIP (may be relat o kern/129352 net [xl] [patch] xl0 watchdog timeout o kern/129219 net [ppp] Kernel panic when using kernel mode ppp o kern/129197 net [panic] 7.0 IP stack related panic o bin/128954 net ifconfig(8) deletes valid routes o kern/128917 net [wpi] [panic] if_wpi and wpa+tkip causing kernel panic o kern/128884 net [msk] if_msk page fault while in kernel mode o kern/128840 net [igb] page fault under load with igb/LRO o bin/128602 net [an] wpa_supplicant(8) crashes with an(4) o kern/128448 net [nfs] 6.4-RC1 Boot Fails if NFS Hostname cannot be res o conf/128334 net [request] use wpa_cli in the "WPA DHCP" situation o bin/128295 net [patch] ifconfig(8) does not print TOE4 or TOE6 capabi o bin/128001 net wpa_supplicant(8), wlan(4), and wi(4) issues o kern/127928 net [tcp] [patch] TCP bandwidth gets squeezed every time t o kern/127834 net [ixgbe] [patch] wrong error counting o kern/127826 net [iwi] iwi0 driver has reduced performance and connecti o kern/127815 net [gif] [patch] if_gif does not set vlan attributes from o kern/127724 net [rtalloc] rtfree: 0xc5a8f870 has 1 refs f bin/127719 net [arp] arp: Segmentation fault (core dumped) s kern/127587 net [bge] [request] if_bge(4) doesn't support BCM576X fami f kern/127528 net [icmp]: icmp socket receives icmp replies not owned by o bin/127192 net routed(8) removes the secondary alias IP of interface f kern/127145 net [wi]: prism (wi) driver crash at bigger traffic o kern/127102 net [wpi] Intel 3945ABG low throughput o kern/127057 net [udp] Unable to send UDP packet via IPv6 socket to IPv o kern/127050 net [carp] ipv6 does not work on carp interfaces [regressi o kern/126945 net [carp] CARP interface destruction with ifconfig destro o kern/126895 net [patch] [ral] Add antenna selection (marked as TBD) o kern/126874 net [vlan]: Zebra problem if ifconfig vlanX destroy o bin/126822 net wpa_supplicant(8): WPA PSK does not work in adhoc mode o kern/126714 net [carp] CARP interface renaming makes system no longer o kern/126695 net rtfree messages and network disruption upon use of if_ o kern/126688 net [ixgbe] [patch] 1.4.7 ixgbe driver panic with 4GB and o kern/126475 net [ath] [panic] ath pcmcia card inevitably panics under o kern/126339 net [ipw] ipw driver drops the connection o kern/126214 net [ath] txpower problem with Atheros wifi card o kern/126075 net [inet] [patch] internet control accesses beyond end of o bin/125922 net [patch] Deadlock in arp(8) o kern/125920 net [arp] Kernel Routing Table loses Ethernet Link status o kern/125845 net [netinet] [patch] tcp_lro_rx() should make use of hard o kern/125816 net [carp] [if_bridge] carp stuck in init when using bridg f kern/125502 net [ral] ifconfig ral0 scan produces no output unless in o kern/125258 net [socket] socket's SO_REUSEADDR option does not work o kern/125239 net [gre] kernel crash when using gre o kern/124767 net [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 net [ieee80211] net80211 discards power-save queue packets o kern/124341 net [ral] promiscuous mode for wireless device ral0 looses o kern/124160 net [libc] connect(2) function loops indefinitely o kern/124127 net [msk] watchdog timeout (missed Tx interrupts) -- recov o kern/124021 net [ip6] [panic] page fault in nd6_output() o kern/123968 net [rum] [panic] rum driver causes kernel panic with WPA. p kern/123961 net [vr] [patch] Allow vr interface to handle vlans o kern/123892 net [tap] [patch] No buffer space available o kern/123890 net [ppp] [panic] crash & reboot on work with PPP low-spee o kern/123858 net [stf] [patch] stf not usable behind a NAT o kern/123796 net [ipf] FreeBSD 6.1+VPN+ipnat+ipf: port mapping does not o bin/123633 net ifconfig(8) doesn't set inet and ether address in one f kern/123617 net [tcp] breaking connection when client downloading file o kern/123603 net [tcp] tcp_do_segment and Received duplicate SYN o kern/123559 net [iwi] iwi periodically disassociates/associates [regre o bin/123465 net [ip6] route(8): route add -inet6 -interfac o kern/123463 net [ipsec] [panic] repeatable crash related to ipsec-tool o kern/123429 net [nfe] [hang] "ifconfig nfe up" causes a hard system lo o kern/123347 net [bge] bge1: watchdog timeout -- linkstate changed to D o conf/123330 net [nsswitch.conf] Enabling samba wins in nsswitch.conf c o kern/123256 net [wpi] panic: blockable sleep lock with wpi(4) f kern/123172 net [bce] Watchdog timeout problems with if_bce o kern/123160 net [ip] Panic and reboot at sysctl kern.polling.enable=0 o kern/122989 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/122954 net [lagg] IPv6 EUI64 incorrectly chosen for lagg devices o kern/122928 net [em] interface watchdog timeouts and stops receiving p f kern/122839 net [if_em] FreeBSD 7 multicast routing problem o kern/122780 net [lagg] tcpdump on lagg interface during high pps wedge o kern/122772 net [em] em0 taskq panic, tcp reassembly bug causes radix o kern/122743 net [mbuf] [panic] vm_page_unwire: invalid wire count: 0 o kern/122697 net [ath] Atheros card is not well supported o kern/122685 net It is not visible passing packets in tcpdump(1) o kern/122551 net [bge] Broadcom 5715S no carrier on HP BL460c blade usi o kern/122319 net [wi] imposible to enable ad-hoc demo mode with Orinoco o kern/122290 net [netgraph] [panic] Netgraph related "kmem_map too smal o kern/122195 net [ed] Alignment problems in if_ed o kern/122058 net [em] [panic] Panic on em1: taskq o kern/122033 net [ral] [lor] Lock order reversal in ral0 at bootup [reg o bin/121895 net [patch] rtsol(8)/rtsold(8) doesn't handle managed netw o kern/121872 net [wpi] driver fails to attach on a fujitsu-siemens s711 s kern/121774 net [swi] [panic] 6.3 kernel panic in swi1: net o kern/121706 net [netinet] [patch] "rtfree: 0xc4383870 has 1 refs" emit o kern/121624 net [em] [regression] Intel em WOL fails after upgrade to o kern/121555 net [panic] Fatal trap 12: current process = 12 (swi1: net o kern/121443 net [gif] [lor] icmp6_input/nd6_lookup o kern/121437 net [vlan] Routing to layer-2 address does not work on VLA o bin/121359 net [patch] ppp(8): fix local stack overflow in ppp o kern/121298 net [em] [panic] Fatal trap 12: page fault while in kernel o kern/121257 net [tcp] TSO + natd -> slow outgoing tcp traffic o kern/121181 net [panic] Fatal trap 3: breakpoint instruction fault whi o kern/121080 net [bge] IPv6 NUD problem on multi address config on bge0 o kern/120966 net [rum] kernel panic with if_rum and WPA encryption p docs/120945 net [patch] ip6(4) man page lacks documentation for TCLASS o kern/120566 net [request]: ifconfig(8) make order of arguments more fr o kern/120304 net [netgraph] [patch] netgraph source assumes 32-bit time o kern/120266 net [udp] [panic] gnugk causes kernel panic when closing U o kern/120232 net [nfe] [patch] Bring in nfe(4) to RELENG_6 o kern/120130 net [carp] [panic] carp causes kernel panics in any conste o bin/120060 net routed(8) deletes link-level routes in the presence of o kern/119945 net [rum] [panic] rum device in hostap mode, cause kernel o kern/119791 net [nfs] UDP NFS mount of aliased IP addresses from a Sol o kern/119617 net [nfs] nfs error on wpa network when reseting/shutdown f kern/119516 net [ip6] [panic] _mtx_lock_sleep: recursed on non-recursi o kern/119432 net [arp] route add -host -iface causes arp e o kern/119225 net [wi] 7.0-RC1 no carrier with Prism 2.5 wifi card [regr o sparc/118932 net [panic] 7.0-BETA4/sparc-64 kernel panic in rip_output a kern/118879 net [bge] [patch] bge has checksum problems on the 5703 ch o kern/118727 net [netgraph] [patch] [request] add new ng_pf module a kern/118238 net [bce] [patch] bce driver shows "no carrier" on Intel S s kern/117717 net [panic] Kernel panic with Bittorrent client. o kern/117448 net [carp] 6.2 kernel crash [regression] o kern/117423 net [vlan] Duplicate IP on different interfaces o bin/117339 net [patch] route(8): loading routing management commands o kern/117271 net [tap] OpenVPN TAP uses 99% CPU on releng_6 when if_tap o kern/117043 net [em] Intel PWLA8492MT Dual-Port Network adapter EEPROM o kern/116837 net [tun] [panic] [patch] ifconfig tunX destroy: panic o kern/116747 net [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile o bin/116643 net [patch] [request] fstat(1): add INET/INET6 socket deta o kern/116185 net [iwi] if_iwi driver leads system to reboot o kern/115239 net [ipnat] panic with 'kmem_map too small' using ipnat o kern/115019 net [netgraph] ng_ether upper hook packet flow stops on ad o kern/115002 net [wi] if_wi timeout. failed allocation (busy bit). ifco o kern/114915 net [patch] [pcn] pcn (sys/pci/if_pcn.c) ethernet driver f o kern/113895 net [xl] xl0 fails on 6.2-RELEASE but worked fine on 5.5-R o kern/113432 net [ucom] WARNING: attempt to net_add_domain(netgraph) af o kern/112722 net [ipsec] [udp] IP v4 udp fragmented packet reject o kern/112686 net [patm] patm driver freezes System (FreeBSD 6.2-p4) i38 o kern/112570 net [bge] packet loss with bge driver on BCM5704 chipset o bin/112557 net [patch] ppp(8) lock file should not use symlink name o kern/112528 net [nfs] NFS over TCP under load hangs with "impossible p o kern/111457 net [ral] ral(4) freeze o kern/110140 net [ipw] ipw fails under load o kern/109733 net [bge] bge link state issues [regression] o kern/109470 net [wi] Orinoco Classic Gold PC Card Can't Channel Hop o kern/109308 net [pppd] [panic] Multiple panics kernel ppp suspected [r o kern/109251 net [re] [patch] if_re cardbus card won't attach o bin/108895 net pppd(8): PPPoE dead connections on 6.2 [regression] o kern/108542 net [bce] Huge network latencies with 6.2-RELEASE / STABLE o kern/107944 net [wi] [patch] Forget to unlock mutex-locks o kern/107850 net [bce] bce driver link negotiation is faulty o conf/107035 net [patch] bridge(8): bridge interface given in rc.conf n o kern/106438 net [ipf] ipfilter: keep state does not seem to allow repl o kern/106316 net [dummynet] dummynet with multipass ipfw drops packets o kern/106243 net [nve] double fault panic in if_nve.c on high loads o kern/105945 net Address can disappear from network interface s kern/105943 net Network stack may modify read-only mbuf chain copies o bin/105925 net problems with ifconfig(8) and vlan(4) [regression] o kern/105348 net [ath] ath device stopps TX o kern/104851 net [inet6] [patch] On link routes not configured when usi o kern/104751 net [netgraph] kernel panic, when getting info about my tr o kern/104485 net [bge] Broadcom BCM5704C: Intermittent on newer chip ve o kern/103191 net Unpredictable reboot o kern/103135 net [ipsec] ipsec with ipfw divert (not NAT) encodes a pac o conf/102502 net [netgraph] [patch] ifconfig name does't rename netgrap o kern/102035 net [plip] plip networking disables parallel port printing o kern/101948 net [ipf] [panic] Kernel Panic Trap No 12 Page Fault - cau o kern/100709 net [libc] getaddrinfo(3) should return TTL info o kern/100519 net [netisr] suggestion to fix suboptimal network polling o kern/98978 net [ipf] [patch] ipfilter drops OOW packets under 6.1-Rel o kern/98597 net [inet6] Bug in FreeBSD 6.1 IPv6 link-local DAD procedu o bin/98218 net wpa_supplicant(8) blacklist not working f bin/97392 net ppp(8) hangs instead terminating o kern/97306 net [netgraph] NG_L2TP locks after connection with failed f kern/96268 net [socket] TCP socket performance drops by 3000% if pack o kern/96030 net [bfe] [patch] Install hangs with Broadcomm 440x NIC in o kern/95519 net [ral] ral0 could not map mbuf o kern/95288 net [pppd] [tty] [panic] if_ppp panic in sys/kern/tty_subr o kern/95277 net [netinet] [patch] IP Encapsulation mask_match() return o kern/95267 net packet drops periodically appear s kern/94863 net [bge] [patch] hack to get bge(4) working on IBM e326m o kern/94162 net [bge] 6.x kenel stale with bge(4) o kern/93886 net [ath] Atheros/D-Link DWL-G650 long delay to associate f kern/93378 net [tcp] Slow data transfer in Postfix and Cyrus IMAP (wo o kern/93019 net [ppp] ppp and tunX problems: no traffic after restarti o kern/92880 net [libc] [patch] almost rewritten inet_network(3) functi f kern/92552 net A serious bug in most network drivers from 5.X to 6.X s kern/92279 net [dc] Core faults everytime I reboot, possible NIC issu o kern/92090 net [bge] bge0: watchdog timeout -- resetting o kern/91859 net [ndis] if_ndis does not work with Asus WL-138 s kern/91777 net [ipf] [patch] wrong behaviour with skip rule inside an o kern/91594 net [em] FreeBSD > 5.4 w/ACPI fails to detect Intel Pro/10 o kern/91364 net [ral] [wep] WF-511 RT2500 Card PCI and WEP o kern/91311 net [aue] aue interface hanging o kern/90890 net [vr] Problems with network: vr0: tx shutdown timeout s kern/90086 net [hang] 5.4p8 on supermicro P8SCT hangs during boot if f kern/88082 net [ath] [panic] cts protection for ath0 causes panic o kern/87521 net [ipf] [panic] using ipfilter "auth" keyword leads to k o kern/87506 net [vr] [patch] Fix alias support on vr interfaces s kern/86920 net [ndis] ifconfig: SIOCS80211: Invalid argument [regress o kern/86103 net [ipf] Illegal NAT Traversal in IPFilter o kern/85780 net 'panic: bogus refcnt 0' in routing/ipv6 o bin/85445 net ifconfig(8): deprecated keyword to ifconfig inoperativ o kern/85266 net [xe] [patch] xe(4) driver does not recognise Xircom XE o kern/84202 net [ed] [patch] Holtek HT80232 PCI NIC recognition on Fre o bin/82975 net route change does not parse classfull network as given s kern/81147 net [net] [patch] em0 reinitialization while adding aliase o kern/80853 net [ed] [patch] add support for Compex RL2000/ISA in PnP o kern/79895 net [ipf] 5.4-RC2 breaks ipfilter NAT when using netgraph f kern/79262 net [dc] Adaptec ANA-6922 not fully supported o bin/79228 net [patch] extend arp(8) to be able to create blackhole r o kern/78090 net [ipf] ipf filtering on bridged packets doesn't work if p kern/77913 net [wi] [patch] Add the APDL-325 WLAN pccard to wi(4) o kern/77341 net [ip6] problems with IPV6 implementation o kern/77273 net [ipf] ipfilter breaks ipv6 statefull filtering on 5.3 s kern/77195 net [ipf] [patch] ipfilter ioctl SIOCGNATL does not match o kern/75873 net Usability problem with non-RFC-compliant IP spoof prot s kern/75407 net [an] an(4): no carrier after short time f kern/73538 net [bge] problem with the Broadcom BCM5788 Gigabit Ethern o kern/71469 net default route to internet magically disappears with mu o kern/70904 net [ipf] ipfilter ipnat problem with h323 proxy support o kern/64556 net [sis] [patch] if_sis short cable fix problems with Net s kern/60293 net [patch] FreeBSD arp poison patch o kern/54383 net [nfs] [patch] NFS root configurations without dynamic f i386/45773 net [bge] Softboot causes autoconf failure on Broadcom 570 s bin/41647 net ifconfig(8) doesn't accept lladdr along with inet addr s kern/39937 net ipstealth issue a kern/38554 net [patch] changing interface ipaddress doesn't seem to w o kern/35442 net [sis] [patch] Problem transmitting runts in if_sis dri o kern/34665 net [ipf] [hang] ipfilter rcmd proxy "hangs". o kern/31647 net [libc] socket calls can return undocumented EINVAL o kern/30186 net [libc] getaddrinfo(3) does not handle incorrect servna o kern/27474 net [ipf] [ppp] Interactive use of user PPP and ipfilter c o conf/23063 net [arp] [patch] for static ARP tables in rc.network 375 problems total. From owner-freebsd-net@FreeBSD.ORG Mon Dec 21 12:20:05 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 970DE106566C for ; Mon, 21 Dec 2009 12:20:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 858B68FC14 for ; Mon, 21 Dec 2009 12:20:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBLCK5ov073659 for ; Mon, 21 Dec 2009 12:20:05 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBLCK5hH073658; Mon, 21 Dec 2009 12:20:05 GMT (envelope-from gnats) Date: Mon, 21 Dec 2009 12:20:05 GMT Message-Id: <200912211220.nBLCK5hH073658@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Miroslav Lachman <000.fbsd@quip.cz> Cc: Subject: Re: kern/140970: [bce] The two NetXtreme II BCM5709S NICs on our HP Bl460c G1 Blade can't be accessed on FreeBSD 7.2 and 8 [regression] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Miroslav Lachman <000.fbsd@quip.cz> List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 12:20:05 -0000 The following reply was made to PR kern/140970; it has been noted by GNATS. From: Miroslav Lachman <000.fbsd@quip.cz> To: bug-followup@FreeBSD.org, kormann@itm.tum.de Cc: Subject: Re: kern/140970: [bce] The two NetXtreme II BCM5709S NICs on our HP Bl460c G1 Blade can't be accessed on FreeBSD 7.2 and 8 [regression] Date: Mon, 21 Dec 2009 13:17:19 +0100 This seems to be a duplicate of: kern/134658 kern/136417 kern/139761 And maybe related to the kern/134788, which is solved and already closed. (fixed in 7-STABLE) http://lists.freebsd.org/pipermail/freebsd-net/2009-November/023706.html http://lists.freebsd.org/pipermail/freebsd-net/2009-November/023815.html From owner-freebsd-net@FreeBSD.ORG Mon Dec 21 13:20:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 334C5106566C for ; Mon, 21 Dec 2009 13:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 22F218FC0C for ; Mon, 21 Dec 2009 13:20:03 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBLDK2Ma030742 for ; Mon, 21 Dec 2009 13:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBLDK2f3030741; Mon, 21 Dec 2009 13:20:02 GMT (envelope-from gnats) Date: Mon, 21 Dec 2009 13:20:02 GMT Message-Id: <200912211320.nBLDK2f3030741@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Dennis Yusupoff Cc: Subject: Re: bin/136994: [patch] ifconfig(8) print carp mac address X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dennis Yusupoff List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 13:20:03 -0000 The following reply was made to PR bin/136994; it has been noted by GNATS. From: Dennis Yusupoff To: bug-followup@FreeBSD.org, Artis.Caune@gmail.com Cc: Subject: Re: bin/136994: [patch] ifconfig(8) print carp mac address Date: Mon, 21 Dec 2009 15:45:40 +0300 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA4B9AA74B0E28FEA26407577 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It will be really nice to see this feature in production. Could you speed up its commiting? --- With best regards, Dennis Yusupoff, network engineer of Smart-Telecom ISP Russia, Saint-Petersburg --------------enigA4B9AA74B0E28FEA26407577 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJLL234AAoJEBUTaqBS2NB4F6QIAIArXFiLhqqGCW20UvoSKUTo T5m/0GbrrRAstbQDV1un9P3NthlO4ydvMUeutUpr7PlpBkjU8OEN9zAl34kyDLFs cEvaBUBkigukfFKXFMmAzZC0ecetgPNekrSqkaMvca9q8vijazkBQNWG+oIYGYFq RkrRcEvKLWMk1f6fZlyzZfMx4EMudwAOXHObL5Z8reEabcVRBZYBA+aPpxXYUzXZ Qe3kgd+j/EGokEgq6cbSsbZwSydQ29nkJVMDA7zeUCVhIDXUo7XXaK69ePzqKmql Rkh9Q1vyPjxYRAaSb7r1jLsuOaMzteQ44kgPk3R6LMK7Bzo4T2kFV5ppOCUDhr0= =nBly -----END PGP SIGNATURE----- --------------enigA4B9AA74B0E28FEA26407577-- From owner-freebsd-net@FreeBSD.ORG Mon Dec 21 21:44:59 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6988E1065670; Mon, 21 Dec 2009 21:44:59 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 260948FC12; Mon, 21 Dec 2009 21:44:59 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id B20D846B35; Mon, 21 Dec 2009 16:44:58 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id E5D8D8A020; Mon, 21 Dec 2009 16:44:57 -0500 (EST) From: John Baldwin To: net@freebsd.org Date: Mon, 21 Dec 2009 16:44:31 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) References: <200911131244.58819.jhb@freebsd.org> In-Reply-To: <200911131244.58819.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912211644.31826.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 21 Dec 2009 16:44:58 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Brooks Davis Subject: Re: ifnet renaming interacts badly with vlans X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 21:44:59 -0000 On Friday 13 November 2009 12:44:58 pm John Baldwin wrote: > So first the problem I am trying to solve. I would like to give meaningful > aliases to interfaces and vlans on interfaces. For example, suppose I would > I have em0 with a vlan of 112, but I would like to call em0, "foo" and > em0.112, "foo.bar". One can do this if you do things in this order: > > ifconfig em0 name foo > ifconfig foo.112 create > ifconfig foo.112 name foo.bar > > However, our rc.d scripts want to create all cloned interfaces before applying > renames, so to attempt to do this in /etc/rc.conf you would use something > like: > > cloned_interfaces="em0.112" > ifconfig_em0_name="foo" > ifconfig_em0_112_name="foo.bar" > > However, this ends up doing a sequence more like: > > ifconfig em0.112 create > ifconfig em0 name foo > ifconfig em0.112 name foo.bar > > Unfortuantely, this sequence breaks em0.112 at the second step. The reason is > that when em0 is renamed, the kernel actaully fires off event handlers > claiming that the em0 ifnet has been detached and that a new foo ifnet has > been attached. When this happens, the em0.112 vlan ifnet is orphaned. > > I think this is a bug in how renames are handled. Specifically, I don't think > renaming an interface should always have the same semantics as if I had > physically removed an interface and then later added it back. One > alternative would be to instead broadcast a single "rename" event when an > interface is renamed and things that cared about interface names (such as > firewall rules) could still honor those events, but other subsystems might > choose to ignore said events (e.g. vlan devices). Another alternative might > be to use two different events ('ifnet_removed_name' and 'ifnet_added_name'). > Subsystems that care about the name changing could reuse their existing > detached/attached handlers for those two events without needing to change the > event handlers themselves. A separate issue if the eventhandlers were > changed is if we should use a different routing socket message when an > interface is renamed or if it we should still claim that an interface has > gone away and then come back. Given that we don't flush addresses from an > interface when the name changes or even the ifindex it seems a bit > disingenous to claim that the interface has detached and then reattached. So I took a more conservative approach so that the change was easier to MFC. My current patch adds a new flag to the ifnet if_flags IFF_RENAMING that is set during a rename operation. ifnet attach/detach handlers can then use this flag to handle renames differently from other events. This means that no other bits of code have to change to handle renames. I then changed the vlan(4) driver to do what I felt was most intuitive in that it renames the child vlan interfaces if their existing name was tied to the parent interface. However, it turns out that this does not work well with our rc.d scripts. Specifically, ifnet_rename() in /etc/network.subr fetches the list of devices before any renames happen, so with the auto-renaming feature the vlan gets renamed before the vlan interface can have its name changed. If I remove the auto-renaming feature then the example I gave above to rename em0.112 to foo.bar would work fine. This is also a smaller and simpler diff to go with this approach. What do other folks thing? (Current patch is http://www.FreeBSD.org/~jhb/patches/vlan_rename.patch ) -- John Baldwin From owner-freebsd-net@FreeBSD.ORG Mon Dec 21 22:31:55 2009 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 54895106568F; Mon, 21 Dec 2009 22:31:55 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 269FB8FC16; Mon, 21 Dec 2009 22:31:55 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 8759746B0D; Mon, 21 Dec 2009 17:31:54 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id C72698A01B; Mon, 21 Dec 2009 17:31:53 -0500 (EST) From: John Baldwin To: net@freebsd.org Date: Mon, 21 Dec 2009 17:25:39 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) References: <200911131244.58819.jhb@freebsd.org> <200912211644.31826.jhb@freebsd.org> In-Reply-To: <200912211644.31826.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912211725.39245.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 21 Dec 2009 17:31:53 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Brooks Davis Subject: Re: ifnet renaming interacts badly with vlans X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 22:31:55 -0000 On Monday 21 December 2009 4:44:31 pm John Baldwin wrote: > On Friday 13 November 2009 12:44:58 pm John Baldwin wrote: > > So first the problem I am trying to solve. I would like to give meaningful > > aliases to interfaces and vlans on interfaces. For example, suppose I would > > I have em0 with a vlan of 112, but I would like to call em0, "foo" and > > em0.112, "foo.bar". One can do this if you do things in this order: > > > > ifconfig em0 name foo > > ifconfig foo.112 create > > ifconfig foo.112 name foo.bar > > > > However, our rc.d scripts want to create all cloned interfaces before applying > > renames, so to attempt to do this in /etc/rc.conf you would use something > > like: > > > > cloned_interfaces="em0.112" > > ifconfig_em0_name="foo" > > ifconfig_em0_112_name="foo.bar" > > > > However, this ends up doing a sequence more like: > > > > ifconfig em0.112 create > > ifconfig em0 name foo > > ifconfig em0.112 name foo.bar > > > > Unfortuantely, this sequence breaks em0.112 at the second step. The reason is > > that when em0 is renamed, the kernel actaully fires off event handlers > > claiming that the em0 ifnet has been detached and that a new foo ifnet has > > been attached. When this happens, the em0.112 vlan ifnet is orphaned. > > > > I think this is a bug in how renames are handled. Specifically, I don't think > > renaming an interface should always have the same semantics as if I had > > physically removed an interface and then later added it back. One > > alternative would be to instead broadcast a single "rename" event when an > > interface is renamed and things that cared about interface names (such as > > firewall rules) could still honor those events, but other subsystems might > > choose to ignore said events (e.g. vlan devices). Another alternative might > > be to use two different events ('ifnet_removed_name' and 'ifnet_added_name'). > > Subsystems that care about the name changing could reuse their existing > > detached/attached handlers for those two events without needing to change the > > event handlers themselves. A separate issue if the eventhandlers were > > changed is if we should use a different routing socket message when an > > interface is renamed or if it we should still claim that an interface has > > gone away and then come back. Given that we don't flush addresses from an > > interface when the name changes or even the ifindex it seems a bit > > disingenous to claim that the interface has detached and then reattached. > > So I took a more conservative approach so that the change was easier to MFC. > My current patch adds a new flag to the ifnet if_flags IFF_RENAMING that is > set during a rename operation. ifnet attach/detach handlers can then use > this flag to handle renames differently from other events. This means that > no other bits of code have to change to handle renames. I then changed the > vlan(4) driver to do what I felt was most intuitive in that it renames the > child vlan interfaces if their existing name was tied to the parent > interface. > > However, it turns out that this does not work well with our rc.d scripts. > Specifically, ifnet_rename() in /etc/network.subr fetches the list of devices > before any renames happen, so with the auto-renaming feature the vlan gets > renamed before the vlan interface can have its name changed. If I remove > the auto-renaming feature then the example I gave above to rename em0.112 > to foo.bar would work fine. This is also a smaller and simpler diff to go > with this approach. What do other folks thing? > > (Current patch is http://www.FreeBSD.org/~jhb/patches/vlan_rename.patch ) I think I've mostly convinced myself (with the aid of a few other folks) that the auto-renaming feature should go. An alternate (and much simpler) patch that just changes vlan interfaces to ignore detach events that are really renames is available at vlan_simple.patch. I have also verified that it works with our existing rc.d scripts so that you can do the following: cloned_interfaces="em0.112" ifconfig_em0_name="foo" ifconfig_em0_112_name="foo.bar" ifconfig_foo="inet 192.168.1.1/24" ifconfig_foo_bar="inet 192.168.2.1/24" -- John Baldwin From owner-freebsd-net@FreeBSD.ORG Mon Dec 21 23:53:22 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1CA9106568D; Mon, 21 Dec 2009 23:53:22 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 997CB8FC26; Mon, 21 Dec 2009 23:53:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBLNrMYw015202; Mon, 21 Dec 2009 23:53:22 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBLNrM5U015198; Mon, 21 Dec 2009 23:53:22 GMT (envelope-from linimon) Date: Mon, 21 Dec 2009 23:53:22 GMT Message-Id: <200912212353.nBLNrM5U015198@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/141843: [em] [vlan] Intel txcsum and assigned vlan invoke wrong dst MAC in TCP packets X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 23:53:22 -0000 Old Synopsis: Intel txcsum and assigned vlan invoke wrong dst MAC in TCP packets New Synopsis: [em] [vlan] Intel txcsum and assigned vlan invoke wrong dst MAC in TCP packets Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 21 23:51:33 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=141843 From owner-freebsd-net@FreeBSD.ORG Mon Dec 21 23:54:00 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AD151065696; Mon, 21 Dec 2009 23:54:00 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D77278FC21; Mon, 21 Dec 2009 23:53:59 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBLNrxr4015253; Mon, 21 Dec 2009 23:53:59 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBLNrxkA015249; Mon, 21 Dec 2009 23:53:59 GMT (envelope-from linimon) Date: Mon, 21 Dec 2009 23:53:59 GMT Message-Id: <200912212353.nBLNrxkA015249@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/141848: [vimage][panic] kernel with vimage panics on xen/domu/hvm guest X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 23:54:00 -0000 Synopsis: [vimage][panic] kernel with vimage panics on xen/domu/hvm guest Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Dec 21 23:53:41 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=141848 From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 06:33:21 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64F4E1065676; Tue, 22 Dec 2009 06:33:21 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3B8F98FC1A; Tue, 22 Dec 2009 06:33:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBM6XLU2084819; Tue, 22 Dec 2009 06:33:21 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBM6XLkj084814; Tue, 22 Dec 2009 06:33:21 GMT (envelope-from linimon) Date: Tue, 22 Dec 2009 06:33:21 GMT Message-Id: <200912220633.nBM6XLkj084814@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/141861: [wi] data garbled with WEP and wi(4) with Prism 2.5 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 06:33:21 -0000 Old Synopsis: data garbled with WEP and wi(4) with Prism 2.5 New Synopsis: [wi] data garbled with WEP and wi(4) with Prism 2.5 Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Tue Dec 22 06:32:33 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=141861 From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 09:22:35 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D73FD10656AB; Tue, 22 Dec 2009 09:22:35 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id AE79B8FC1C; Tue, 22 Dec 2009 09:22:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBM9MZ1x070905; Tue, 22 Dec 2009 09:22:35 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBM9MZHh070901; Tue, 22 Dec 2009 09:22:35 GMT (envelope-from linimon) Date: Tue, 22 Dec 2009 09:22:35 GMT Message-Id: <200912220922.nBM9MZHh070901@freefall.freebsd.org> To: robert@maerzkegeneral.com, linimon@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/141741: Etherlink III NIC won't work after upgrade to FBSD 8, If I run tcpdump - it works. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 09:22:35 -0000 Synopsis: Etherlink III NIC won't work after upgrade to FBSD 8, If I run tcpdump - it works. State-Changed-From-To: open->feedback State-Changed-By: linimon State-Changed-When: Tue Dec 22 09:22:10 UTC 2009 State-Changed-Why: Note that submitter was asked for feedback. http://www.freebsd.org/cgi/query-pr.cgi?pr=141741 From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 09:30:04 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE65F106566B for ; Tue, 22 Dec 2009 09:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 740268FC13 for ; Tue, 22 Dec 2009 09:30:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBM9U4ak071357 for ; Tue, 22 Dec 2009 09:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBM9U49R071350; Tue, 22 Dec 2009 09:30:04 GMT (envelope-from gnats) Date: Tue, 22 Dec 2009 09:30:04 GMT Message-Id: <200912220930.nBM9U49R071350@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Dominic Fandrey Cc: Subject: Re: kern/136876: [bge] bge will not resume properly after suspend X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dominic Fandrey List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 09:30:04 -0000 The following reply was made to PR kern/136876; it has been noted by GNATS. From: Dominic Fandrey To: bug-followup@FreeBSD.org, adamk@voicenet.com Cc: Subject: Re: kern/136876: [bge] bge will not resume properly after suspend Date: Tue, 22 Dec 2009 10:26:43 +0100 The problem is also present on amd64: > uname -a FreeBSD mobileKamikaze.norad 8.0-STABLE FreeBSD 8.0-STABLE #0: Tue Dec 15 22:48:25 CET 2009 root@mobileKamikaze.norad:/usr/obj/HP6510b-8/amd64/usr/src/sys/HP6510b-8 amd64 I can provide more details. I'd really like to see this work. From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 14:05:31 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E604106568D for ; Tue, 22 Dec 2009 14:05:31 +0000 (UTC) (envelope-from fengdreamer@126.com) Received: from m50-110.126.com (m50-110.126.com [123.125.50.110]) by mx1.freebsd.org (Postfix) with ESMTP id 23CF78FC1F for ; Tue, 22 Dec 2009 14:05:29 +0000 (UTC) Received: from hao251 (unknown [219.237.184.171]) by smtp4 (Coremail) with SMTP id jdKowLCbSzgq0jBLAESVCA--.52197S2; Tue, 22 Dec 2009 22:05:31 +0800 (CST) Date: Tue, 22 Dec 2009 22:05:21 +0800 From: "fengdreamer" To: "freebsd-net" References: <31264189.456321261063444556.JavaMail.coremail@bj126app49.126.com>, <200912192345192969851@126.com> Message-ID: <200912222205205465309@126.com> X-mailer: Foxmail 6, 15, 201, 22 [cn] Mime-Version: 1.0 X-CM-TRANSID: jdKowLCbSzgq0jBLAESVCA--.52197S2 X-Coremail-Antispam: 1UD129KBjvJXoW7ZrW7Kw13Zw15Cw4rWw45ZFb_yoW8Zw17pa yYq39xGrn2qrZ5Ars7Cr40gr1093yFyFy5J3yUWryYvw1Yg392gF12yrWa9wnruFs2vw1Y 9FWUXF15Ga1kC37anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUy0b7IF0VCYb41lb7IF0VCF04k20xv_Gry3M7k042IE42xK82IY 64kIx2x0424lb7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI4VWUJwAYFVCjjxCrM7Avxs IEb2xv6ckvw2Wl14x267AKxVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq 3wAFIxvE14AKwVWUJVWUGwA2z4x0Y4vE2Ix0cI8IcVAFwI0_tr0E3s1l84ACjcxK6xIIjx v20xvEc7CjxVAFwI0_GcCE3s1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2 jsIEc7CjxVAFwI0_GcCE3s1l57IF6xkI12xvs2x26I8E6xACxx1l57IF6s8CjcxG0xyl5I 8CrVCF0I0E4I0vr24lYx0Ex4A2jsIE14v26r1j6r4UM4x0Y48IcxkI7VAKI48JM4xvF2IE b7IF0Fy264kE64k0F24lFcxC0VAYjxAxZF0Ex2IqxwAC62BYpTIE1TZKA3svLVAKvSnIqf ZI6r4l7I0Y64k_MxkFs20EY4vE8sxKj4xv1wCY02Avz4vE14v_Xrylc2IjII80xcxEwVAK I48JMxAIw28IcxkI7VAKI48JMxCjnVAqn7xvrwC2zVAF1VAY17CE14v26r1j6r15MIIF0x vE42xK8VAvwI8IcIk0rVWrZr1j6s0DMs8CjcxG0xvEn4CqF7xvrwCE64xvF2IEb7IF0Fy7 YxBIdaVFxhVjvjDU0xZFpf9x07UY9aPUUUUU= X-CM-SenderInfo: pihqwv5uhdzvbu6rjloofrz/1tbiHRlBs0ihO5Q-9wAAs4 X-Mailman-Approved-At: Tue, 22 Dec 2009 14:11:55 +0000 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: KASSERT when connect to the peer(system is running out of memory) . X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 14:05:31 -0000 Hello ALL: I am using the FreeBSD 7.1. My system is running out of memory, in this sidution when i create the socket and connect, the the KASSERT come out. Here is my description, please read the brief first and get the problem and then contnue with the detail description. How is this problem happen: Brief description: 1. First, Connect side send SYN to the listerner 2. Second, Connect side will retransmit the SYN packet, but when it alloc mbuf fail in the tcp_output. the tcp_sndnxt will not increase. 3. SYN ACK arrives, tcp_snduna increase, and will lager then tcp_sndnxt by 1. sender side will response the ACK, invoke tcp_output: len is 1, but cc is zero. KASSERT happen. Detail description: 1.First, Connect side send SYN to the listerner, tcp->snd_nxt will just larger than the tcp->snd_una by 1. 2. Second, Connect side will retransmit the SYN packet. The retransmit is triger by the retransmit timer, it will then roll back the tcp->snd_nxt equal to tcp->snd_una. and begin to call the tcp_output. If the tcp_output working fun, the tcp->snd_nxt will then advanced by 1 before it calls the ip_output. But if the mbuf alloc fail, the tcp->snd_nxt will stay equal to tcp->snd_una. (on my system, memery is running out, so mbuf alloc may fail. ) please refer the below code in the tcp_output: MGETHDR(m, M_DONTWAIT, MT_DATA); if (m == NULL) { error = ENOBUFS; goto out; // goto out, so the tcp->snd_nxt will not increased. } 3. as above describtion, the tcp->snd_nxt is equal to tcp->snd_una. then the SYN ACK packet arrives, and the connection is established, and the tcp->snd_una will increase by 1. Also the connect side will then send the last ACK, it invode the tcp_output, tcp output len is compute by the below expression: off = tp->snd_nxt - tp->snd_una; len = ((long)ulmin(so->so_snd.sb_cc, sendwin) - off); ofcourse you have seen. the off is -1, the so_snd.sb_cc is 0, so the len is 1. so below KASSERT will came: KASSERT(sb->sb_mb != NULL, ("%s: sb_mb is NULL", __func__)); /* (sbsndptr ) */ Thanks Regard From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 17:20:03 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A033106566B for ; Tue, 22 Dec 2009 17:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D35B38FC24 for ; Tue, 22 Dec 2009 17:20:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBMHK2A4008183 for ; Tue, 22 Dec 2009 17:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBMHK2js008182; Tue, 22 Dec 2009 17:20:02 GMT (envelope-from gnats) Date: Tue, 22 Dec 2009 17:20:02 GMT Message-Id: <200912221720.nBMHK2js008182@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Robert Maerzke Cc: Subject: Re: kern/141741: Etherlink III NIC won't work after upgrade to FBSD 8, If I run tcpdump - it works. X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Robert Maerzke List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 17:20:03 -0000 The following reply was made to PR kern/141741; it has been noted by GNATS. From: Robert Maerzke To: bug-followup@FreeBSD.org, robert@maerzkegeneral.com Cc: Subject: Re: kern/141741: Etherlink III NIC won't work after upgrade to FBSD 8, If I run tcpdump - it works. Date: Tue, 22 Dec 2009 10:58:29 -0600 Here's the relevant lines from dmesg: ep0: <3Com 3C509B-Combo EtherLink III (PnP)> at port 0x210-0x21f irq 5 pnpid TCM5094 on isa0 ep0: WARNING: using obsoleted if_watchdog interface ep0: Ethernet address: 00:60:97:22:8b:f5 ep0: [ITHREAD] driver bug: Unable to set devclass (devname: (null)) From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 19:30:41 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B2AF1065676 for ; Tue, 22 Dec 2009 19:30:41 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id DFEC98FC13 for ; Tue, 22 Dec 2009 19:30:40 +0000 (UTC) Received: by qyk6 with SMTP id 6so2819654qyk.3 for ; Tue, 22 Dec 2009 11:30:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:organization:x-operation-sytem; bh=3Ww54K7+/7tFH3CKLHy/DqWHHmqIWTR7BvuyUtd2u1U=; b=Awqj+QDjklYnfqmVmMDOxpz2/GAFMU6Bkfe4EIS4jTVDSi9q8ja/2FHX4KePoiNTij VgeUVU0eCI3u6nQWvAmeF3wxG+RC8Ofv6CjOQJElcMEyquequMRgeMXm0SEkedtIH9AU ziNWCw4q6ZhC3KuHmvoh/qY/lcycCjtt9dHRA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent:organization:x-operation-sytem; b=UFqtJBTyKXVXXuW5Gy025O7CI4xN0iJpy06OiQgPXfY4xEaq77dXHQIiCEMEpp6YwX 0RSaBemN19xoobAS+9sklEFFytU4kPw0u98Cjd1kSqW7qNyc6LjzONvMKJwevI3/C5Wh iFPEXE88Kg64BeAvxdjB706spZW2NTgH6Owc8= Received: by 10.224.102.194 with SMTP id h2mr4793454qao.96.1261510239873; Tue, 22 Dec 2009 11:30:39 -0800 (PST) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id 22sm5784027qyk.6.2009.12.22.11.30.37 (version=SSLv3 cipher=RC4-MD5); Tue, 22 Dec 2009 11:30:38 -0800 (PST) Received: by weongyo (sSMTP sendmail emulation); Tue, 22 Dec 2009 11:31:04 -0800 From: Weongyo Jeong Date: Tue, 22 Dec 2009 11:31:04 -0800 To: Steven Friedrich Message-ID: <20091222193104.GH1479@weongyo> Mail-Followup-To: Steven Friedrich , freebsd-net@freebsd.org References: <200912151603.32111.freebsd@insightbb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200912151603.32111.freebsd@insightbb.com> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: freebsd-net@freebsd.org Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Weongyo Jeong List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 19:30:41 -0000 On Tue, Dec 15, 2009 at 04:03:31PM -0500, Steven Friedrich wrote: > Ok, I am able to load firmware with: > uathload -d /dev/ugen4.3 > but it also appears to do so when I plug it in... > > Now what? It doesn't show up in ifconfig... Could you please show me dmesg output and the output of # usbconfig dump_device_desc ? regards, Weongyo Jeong From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 22:54:36 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED9AB10656C3 for ; Tue, 22 Dec 2009 22:54:35 +0000 (UTC) (envelope-from freebsd@insightbb.com) Received: from mxsf07.insightbb.com (mxsf07.insightbb.com [74.128.0.77]) by mx1.freebsd.org (Postfix) with ESMTP id AE7058FC24 for ; Tue, 22 Dec 2009 22:54:35 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.47,438,1257138000"; d="scan'208";a="814087242" Received: from unknown (HELO asav03.insightbb.com) ([172.31.249.123]) by mxsf07.insightbb.com with ESMTP; 22 Dec 2009 17:54:34 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiUFAI/dMEvQLicL/2dsb2JhbACBStUwhDMEgWU X-IronPort-AV: E=Sophos;i="4.47,438,1257138000"; d="scan'208";a="118229025" Received: from 208-46-39-11.dia.static.qwest.net (HELO laptop2.stevenfriedrich.org) ([208.46.39.11]) by asavout03.insightbb.com with ESMTP; 22 Dec 2009 17:54:32 -0500 From: Steven Friedrich To: freebsd-net@freebsd.org Date: Tue, 22 Dec 2009 17:54:25 -0500 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; i386; ; ) References: <200912151603.32111.freebsd@insightbb.com> <20091222193104.GH1479@weongyo> In-Reply-To: <20091222193104.GH1479@weongyo> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912221754.25692.freebsd@insightbb.com> Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 22:54:36 -0000 On Tuesday 22 December 2009 02:31:04 pm Weongyo Jeong wrote: > On Tue, Dec 15, 2009 at 04:03:31PM -0500, Steven Friedrich wrote: > > Ok, I am able to load firmware with: > > uathload -d /dev/ugen4.3 > > but it also appears to do so when I plug it in... > > > > Now what? It doesn't show up in ifconfig... > > Could you please show me dmesg output and the output of > > # usbconfig dump_device_desc This message appears on the console when the device is plugged in: ugen4.3: < Atheros Communications Inc > at usbus4 usbconfig -u 4 -a 3 dump_info ugen4.3: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON kldstat Id Refs Address Size Name 1 84 0xc0400000 651018 kernel 2 1 0xc0a52000 7df8 if_rl.ko 3 2 0xc0a5a000 2699c miibus.ko 4 1 0xc0a81000 8bac if_uath.ko 5 1 0xc0a8a000 33bc speaker.ko 6 1 0xc0a8e000 88978 bcmwl5_sys.ko 7 1 0xc0b17000 5a2c acpi_hp.ko 8 2 0xc0b1d000 4590 acpi_wmi.ko 9 3 0xc0b22000 6e360 acpi.ko 10 1 0xc5bb8000 1e000 smbfs.ko 11 2 0xc5bd7000 4000 libiconv.ko 12 2 0xc5c75000 3000 libmchain.ko The device doesn't show up in ifconfig, so the example from the man page: ifconfig wlan create wlandev uath0 doesn't work because uath0 isn't found by ifconfig. ifconfig wlan0 create wlandev uath0 ifconfig: SIOCIFCREATE2: Device not configured I filed a PR against usb, probably should have made it net. Sorry. usbconfig dump_device_desc ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0100 bDeviceClass = 0x0009 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0000 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0100 bDeviceClass = 0x0009 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0000 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0100 bDeviceClass = 0x0009 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0000 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0100 bDeviceClass = 0x0009 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0000 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0000 idProduct = 0x0000 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 ugen4.2: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x1058 idProduct = 0x1100 bcdDevice = 0x0175 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <57442D574341535537363239323938> bNumConfigurations = 0x0001 ugen3.2: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0008 idVendor = 0x046d idProduct = 0xc518 bcdDevice = 0x4202 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 ugen4.3: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x00ff bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x1385 idProduct = 0x4251 bcdDevice = 0x0001 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0003 <1.0> bNumConfigurations = 0x0001 From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 23:01:29 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DD601065672 for ; Tue, 22 Dec 2009 23:01:29 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 236E08FC0C for ; Tue, 22 Dec 2009 23:01:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id D326A7BE1A; Wed, 23 Dec 2009 12:01:27 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZducHLlxjjAe; Wed, 23 Dec 2009 12:01:23 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Wed, 23 Dec 2009 12:01:23 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id E20D811432; Wed, 23 Dec 2009 12:01:22 +1300 (NZDT) Date: Wed, 23 Dec 2009 12:01:22 +1300 From: Andrew Thompson To: Steven Friedrich Message-ID: <20091222230122.GA49597@citylink.fud.org.nz> References: <200912151603.32111.freebsd@insightbb.com> <20091222193104.GH1479@weongyo> <200912221754.25692.freebsd@insightbb.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200912221754.25692.freebsd@insightbb.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 23:01:29 -0000 On Tue, Dec 22, 2009 at 05:54:25PM -0500, Steven Friedrich wrote: > On Tuesday 22 December 2009 02:31:04 pm Weongyo Jeong wrote: > > On Tue, Dec 15, 2009 at 04:03:31PM -0500, Steven Friedrich wrote: > > > Ok, I am able to load firmware with: > > > uathload -d /dev/ugen4.3 > > > but it also appears to do so when I plug it in... > > > > > > Now what? It doesn't show up in ifconfig... > > > > Could you please show me dmesg output and the output of > > > > # usbconfig dump_device_desc > This message appears on the console when the device is plugged in: > ugen4.3: < Atheros Communications Inc > at usbus4 > > usbconfig -u 4 -a 3 dump_info > ugen4.3: at usbus4, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON It looks like you are missing the step to load the firmware with uathload(8). # uathload -d /dev/ugen4.3 Maybe the documentation is missing this, or even better would be to have devd do it automagically. Andrew From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 23:04:15 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AE67106566B for ; Tue, 22 Dec 2009 23:04:15 +0000 (UTC) (envelope-from thompsa@FreeBSD.org) Received: from pele.citylink.co.nz (pele.citylink.co.nz [202.8.44.226]) by mx1.freebsd.org (Postfix) with ESMTP id 58A898FC08 for ; Tue, 22 Dec 2009 23:04:15 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by pele.citylink.co.nz (Postfix) with ESMTP id 791D87BE1A; Wed, 23 Dec 2009 12:04:14 +1300 (NZDT) X-Virus-Scanned: Debian amavisd-new at citylink.co.nz Received: from pele.citylink.co.nz ([127.0.0.1]) by localhost (pele.citylink.co.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cl15EjWIRrSe; Wed, 23 Dec 2009 12:04:10 +1300 (NZDT) Received: from citylink.fud.org.nz (unknown [202.8.44.45]) by pele.citylink.co.nz (Postfix) with ESMTP; Wed, 23 Dec 2009 12:04:10 +1300 (NZDT) Received: by citylink.fud.org.nz (Postfix, from userid 1001) id 6FFC911434; Wed, 23 Dec 2009 12:04:10 +1300 (NZDT) Date: Wed, 23 Dec 2009 12:04:10 +1300 From: Andrew Thompson To: Steven Friedrich Message-ID: <20091222230410.GB49597@citylink.fud.org.nz> References: <200912151603.32111.freebsd@insightbb.com> <20091222193104.GH1479@weongyo> <200912221754.25692.freebsd@insightbb.com> <20091222230122.GA49597@citylink.fud.org.nz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091222230122.GA49597@citylink.fud.org.nz> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 23:04:15 -0000 On Wed, Dec 23, 2009 at 12:01:22PM +1300, Andrew Thompson wrote: > On Tue, Dec 22, 2009 at 05:54:25PM -0500, Steven Friedrich wrote: > > On Tuesday 22 December 2009 02:31:04 pm Weongyo Jeong wrote: > > > On Tue, Dec 15, 2009 at 04:03:31PM -0500, Steven Friedrich wrote: > > > > Ok, I am able to load firmware with: > > > > uathload -d /dev/ugen4.3 ^^^^ Oops, disregard my suggestion :) > > > > but it also appears to do so when I plug it in... > > > > > > > > Now what? It doesn't show up in ifconfig... > > > > > > Could you please show me dmesg output and the output of > > > > > > # usbconfig dump_device_desc > > This message appears on the console when the device is plugged in: > > ugen4.3: < Atheros Communications Inc > at usbus4 > > > > usbconfig -u 4 -a 3 dump_info > > ugen4.3: at usbus4, cfg=0 md=HOST spd=HIGH > > (480Mbps) pwr=ON > > It looks like you are missing the step to load the firmware with > uathload(8). > > # uathload -d /dev/ugen4.3 > > > Maybe the documentation is missing this, or even better would be to have > devd do it automagically. > > > Andrew > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 23:07:09 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 776CC1065692 for ; Tue, 22 Dec 2009 23:07:09 +0000 (UTC) (envelope-from freebsd@insightbb.com) Received: from mxsf03.insightbb.com (mxsf03.insightbb.com [74.128.0.64]) by mx1.freebsd.org (Postfix) with ESMTP id 3EFC98FC24 for ; Tue, 22 Dec 2009 23:07:09 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.47,438,1257138000"; d="scan'208";a="773221278" Received: from unknown (HELO mxsf13.insightbb.com) ([172.31.249.233]) by mxsf03.insightbb.com with ESMTP; 22 Dec 2009 18:06:56 -0500 X-IronPort-AV: E=Sophos;i="4.47,438,1257138000"; d="scan'208";a="13112727" Received: from unknown (HELO asav03.insightbb.com) ([172.31.249.123]) by mxsf13.insightbb.com with ESMTP; 22 Dec 2009 18:06:54 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AiUFALffMEvQLicL/2dsb2JhbACBS9U9hDMEgWWBMw X-IronPort-AV: E=Sophos;i="4.47,438,1257138000"; d="scan'208";a="118230297" Received: from 208-46-39-11.dia.static.qwest.net (HELO laptop2.stevenfriedrich.org) ([208.46.39.11]) by asavout03.insightbb.com with ESMTP; 22 Dec 2009 18:06:54 -0500 From: Steven Friedrich To: freebsd-net@freebsd.org Date: Tue, 22 Dec 2009 18:06:53 -0500 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; i386; ; ) References: <200912151603.32111.freebsd@insightbb.com> <200912221754.25692.freebsd@insightbb.com> <20091222230122.GA49597@citylink.fud.org.nz> In-Reply-To: <20091222230122.GA49597@citylink.fud.org.nz> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912221806.53391.freebsd@insightbb.com> Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 23:07:09 -0000 On Tuesday 22 December 2009 06:01:22 pm Andrew Thompson wrote: > On Tue, Dec 22, 2009 at 05:54:25PM -0500, Steven Friedrich wrote: > > On Tuesday 22 December 2009 02:31:04 pm Weongyo Jeong wrote: > > > On Tue, Dec 15, 2009 at 04:03:31PM -0500, Steven Friedrich wrote: > > > > Ok, I am able to load firmware with: > > > > uathload -d /dev/ugen4.3 > > > > but it also appears to do so when I plug it in... > > > > > > > > Now what? It doesn't show up in ifconfig... > > > > > > Could you please show me dmesg output and the output of > > > > > > # usbconfig dump_device_desc > > > > This message appears on the console when the device is plugged in: > > ugen4.3: < Atheros Communications Inc > at usbus4 > > > > usbconfig -u 4 -a 3 dump_info > > ugen4.3: at usbus4, cfg=0 md=HOST > > spd=HIGH (480Mbps) pwr=ON > > It looks like you are missing the step to load the firmware with > uathload(8). > > # uathload -d /dev/ugen4.3 > > > Maybe the documentation is missing this, or even better would be to have > devd do it automagically. I've tried that and it doesn't look any different than just plugging it in... From owner-freebsd-net@FreeBSD.ORG Tue Dec 22 23:17:47 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C8321065676 for ; Tue, 22 Dec 2009 23:17:47 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f218.google.com (mail-fx0-f218.google.com [209.85.220.218]) by mx1.freebsd.org (Postfix) with ESMTP id 1E9988FC17 for ; Tue, 22 Dec 2009 23:17:46 +0000 (UTC) Received: by fxm10 with SMTP id 10so3657435fxm.14 for ; Tue, 22 Dec 2009 15:17:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:x-enigmail-version:content-type :content-transfer-encoding; bh=wv4vY6FCb8VFDATZSEfPt+e+jN1TwmSc+XN6qA/QKRc=; b=Hft4LGC3egzkTtWTXfbZStm5HOGcgHFLTfiG/J6BieSGShIn/46pyBT1wl4p5k7rH/ J5lsdxZGpAOr4IVZk5dO8WcWYkjBksaIOjh+tuJZY3auLOrYF65c92HpfnLXt5gXZxZ7 5fvjK+K0LZixdIIDlczQsVQG4xzWuBTqta2+Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; b=APM0ckBrprCfs8BP+QIv7vLoicEnVoDcmEnZzZk6zmYh+MInqFfMz1+r03Bjnrfyfh 9YTO1nIgbbW0jEYCwkijVRWD2AG1XPGcYnabHo7xkir+s6OGK6IgZB80udSg6D6v7gzp RulN7rGhwAbFRF94d5vIwuzLzzGSbsEdQClIQ= Received: by 10.223.164.96 with SMTP id d32mr12049095fay.106.1261523865928; Tue, 22 Dec 2009 15:17:45 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 14sm2422086fxm.3.2009.12.22.15.17.44 (version=SSLv3 cipher=RC4-MD5); Tue, 22 Dec 2009 15:17:45 -0800 (PST) Sender: Alexander Motin Message-ID: <4B315398.2090806@FreeBSD.org> Date: Wed, 23 Dec 2009 01:17:44 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: freebsd-net X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Subject: Mpd-5.4 with RADIUS CoA/DR support released X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2009 23:17:47 -0000 Hi. I would like to note, that new 5.4 version of Multilink PPP Daemon was released and available in ports (net/mpd5). The main feature of this release is long-awaited ability to change subscriber session parameters (shapes, filters, ...) on-fly without link termination. It is done in quite standard way, as defined by RFC 3576 "Dynamic Authorization Extensions to RADIUS". Mpd implements both CoA (Change of Authorization) and DR (Disconnect Request) requests, defined by this RFC. To provide this new functionality mpd should be built and running on FreeBSD 7/8-STABLE updated after 2009-10-30, or patched with this patch: http://people.freebsd.org/~mav/libradius.server.20090813.patch. Updated manual can be found here: http://mpd.sourceforge.net/doc5/mpd.html Special thanks to JSC 'Ufanet' (ufanet.ru) for sponsoring this work. PS: Ancient (mpd-3.18) net/mpd port was marked as deprecated and will be removed soon. Consider migration to net/mpd5 if you are still using one. -- Alexander Motin From owner-freebsd-net@FreeBSD.ORG Wed Dec 23 09:47:33 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 679011065693 for ; Wed, 23 Dec 2009 09:47:33 +0000 (UTC) (envelope-from lhunath@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id EF0718FC0C for ; Wed, 23 Dec 2009 09:47:32 +0000 (UTC) Received: by ewy26 with SMTP id 26so3553012ewy.3 for ; Wed, 23 Dec 2009 01:47:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:content-type :content-transfer-encoding:subject:date:message-id:to:mime-version :x-mailer; bh=oFGHmVxCtipnsdS1Ud2ko5Jy982NIk/SAUAnGL35BEo=; b=OzbAysvSIYDOYSc2xRbgXJKFDLE8Zdjj5ZkH2Fwm2uwwZWoVOz3NtCevpL1cO7byMu 2y2iwWj9R0poeTlymM+Tc91AjDoh1tQzvyIwBUCPaasYTbQgPCHKqB6+ijr/mlMKltsZ WKke988QYIlXVaePY9/dmOq2EskrJBodFeizI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:content-type:content-transfer-encoding:subject:date:message-id :to:mime-version:x-mailer; b=OekazdWDBZKYIQ/FUpfSAWkQwP479mR5+AwykcMXR4sLADmkifAuZfKlMSM8GHA5wk x/mMi8plh7fUK6q5PPDOsvLxHUM8XNmG0IZWFgaeTxjVpy62URiL+8NAlpKPd0ggZ2mp Pu9ZoAHEWn+xoPU6IEdM5LMy1OxAsgEmp+PDc= Received: by 10.213.103.11 with SMTP id i11mr3453911ebo.63.1261559833432; Wed, 23 Dec 2009 01:17:13 -0800 (PST) Received: from ?172.19.3.2? (ip-81-11-162-155.dsl.scarlet.be [81.11.162.155]) by mx.google.com with ESMTPS id 16sm5006242ewy.6.2009.12.23.01.17.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 23 Dec 2009 01:17:12 -0800 (PST) From: "Lhunath (Maarten B.)" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 23 Dec 2009 10:11:11 +0100 Message-Id: To: freebsd-net@freebsd.org Mime-Version: 1.0 (Apple Message framework v1077) X-Mailer: Apple Mail (2.1077) Subject: mskc0: Tx descriptor error X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 09:47:33 -0000 Hey, I'm having problems getting my Marvell Yukon to work. I can = successfully get it set up using DHCP, but when I start using it, I get = error messages such as: "mskc0: Tx descriptor error" and "msk0: watchdog = timeout". This is using the msk(4) module from 8.0-RELEASE. A bit of googling indicates that this problem is not uncommon, but had = each time been resolved by patches that appear to have already been = applied to the msk module that I'm using. Some help would be appreciated. Here is the ''dmesg'' output with = bootverbose on and a ''vmstat -i'' should it matter. =46rom dmesg: mskc0: port 0xe800-0xe8ff mem = 0xfebfc000-0xfebfffff irq 17 at device 0.0 on pci4 pcib4: mskc0 requested memory range 0xfebfc000-0xfebfffff: good mskc0: MSI count : 1 mskc0: attempting to allocate 1 MSI vectors (1 supported) msi: routing MSI IRQ 256 to local APIC 0 vector 58 mskc0: using IRQ 256 for MSI mskc0: RAM buffer size : 0KB msk0: on = mskc0 msk0: bpf attached msk0: Ethernet address: 00:1f:c6:83:a7:d0 miibus0: on msk0 e1000phy0: PHY 0 on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, = 1000baseT-FDX, auto mskc0: [MPSAFE] mskc0: [FILTER] pci5: driver added pci6: driver added msk0: link state changed to DOWN msk0: link state changed to UP mskc0: Tx descriptor error mskc0: Tx descriptor error mskc0: Tx descriptor error mskc0: Tx descriptor error mskc0: Tx descriptor error mskc0: Tx descriptor error mskc0: Tx descriptor error mskc0: Tx descriptor error mskc0: Tx descriptor error mskc0: Tx descriptor error msk0: watchdog timeout msk0: link state changed to DOWN msk0: link state changed to UP =46rom vmstat -i: interrupt total rate irq14: ata0 246 0 irq17: fwohci0 2 0 irq20: ohci1 1 0 irq21: ehci1 9412 0 irq22: ohci0 5379 0 irq23: ehci0+ 11296 1 cpu0: timer 18926028 1999 irq256: mskc0 377 0 Total 18952741 2002 From owner-freebsd-net@FreeBSD.ORG Wed Dec 23 11:05:25 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ACC81065679; Wed, 23 Dec 2009 11:05:25 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 1245D8FC0C; Wed, 23 Dec 2009 11:05:25 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBNB5Org020275; Wed, 23 Dec 2009 11:05:24 GMT (envelope-from bz@freefall.freebsd.org) Received: (from bz@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBNB5OIv020271; Wed, 23 Dec 2009 11:05:24 GMT (envelope-from bz) Date: Wed, 23 Dec 2009 11:05:24 GMT Message-Id: <200912231105.nBNB5OIv020271@freefall.freebsd.org> To: venture37@geeklan.co.uk, bz@FreeBSD.org, freebsd-net@FreeBSD.org, bz@FreeBSD.org From: bz@FreeBSD.org Cc: Subject: Re: kern/141848: [vimage][panic] kernel with vimage panics on xen/domu/hvm guest X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 11:05:25 -0000 Synopsis: [vimage][panic] kernel with vimage panics on xen/domu/hvm guest State-Changed-From-To: open->closed State-Changed-By: bz State-Changed-When: Wed Dec 23 11:04:46 UTC 2009 State-Changed-Why: As discussed von freebsd-virtualization, pf is not yet supported with VIMAGE. What you get is expected. Responsible-Changed-From-To: freebsd-net->bz Responsible-Changed-By: bz Responsible-Changed-When: Wed Dec 23 11:04:46 UTC 2009 Responsible-Changed-Why: Take in case of foolow-up. http://www.freebsd.org/cgi/query-pr.cgi?pr=141848 From owner-freebsd-net@FreeBSD.ORG Wed Dec 23 14:17:06 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E6F01065696 for ; Wed, 23 Dec 2009 14:17:06 +0000 (UTC) (envelope-from fengdreamer@126.com) Received: from m50-111.126.com (m50-111.126.com [123.125.50.111]) by mx1.freebsd.org (Postfix) with ESMTP id C167C8FC1B for ; Wed, 23 Dec 2009 14:17:03 +0000 (UTC) Received: from hao251 (unknown [219.237.185.160]) by smtp5 (Coremail) with SMTP id jtKowLC7v_JfJjJLQI_hCA--.10758S2; Wed, 23 Dec 2009 22:17:03 +0800 (CST) Date: Wed, 23 Dec 2009 22:16:52 +0800 From: "fengdreamer" To: "freebsd-net" References: <31264189.456321261063444556.JavaMail.coremail@bj126app49.126.com>, <200912192345192969851@126.com>, <200912222205205465309@126.com> Message-ID: <200912232216513904203@126.com> X-mailer: Foxmail 6, 15, 201, 22 [cn] Mime-Version: 1.0 X-CM-TRANSID: jtKowLC7v_JfJjJLQI_hCA--.10758S2 X-Coremail-Antispam: 1UD129KBjvJXoW7ZrW7Kw13Zw15Cw4rWw45ZFb_yoW8trWkpa yYq39xGrn7XrZYyrs7CrW0gr10k3ySyFy5J3yUXryYyw45K392gF17trW3uwnruFs2vw1Y 9FWjqF15GF4kC37anT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUy2b7IF0VCF04k20xv_Gry3M7k042IE42xK82IY64kIx2x0424l b7IF0VCFI7km07C26c804VAKzcIF0wAYjsxI4VWUJwAYFVCjjxCrM7AvxsIEb2xv6ckvw2 Wl14x267AKxVWUJVW8JwAFc2x0x2IEx4CE42xK8VAvwI8IcIk0rVWrJVCq3wAFIxvE14AK wVWUJVWUGwA2z4x0Y4vE2Ix0cI8IcVAFwI0_tr0E3s1l84ACjcxK6xIIjxv20xvEc7CjxV AFwI0_GcCE3s1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4A2jsIEc7CjxVAF wI0_GcCE3s1ln7IjY7xE6298M2vj6xkI62vS6c8GOVWUtr1rJFyl57IF6xkI12xvs2x26I 8E6xACxx1l57IF6s8CjcxG0xyl5I8CrVCF0I0E4I0vr24lYx0Ex4A2jsIE14v26r1j6r4U M4x0Y48IcxkI7VAKI48JM4xvF2IEb7IF0Fy264kE64k0F24lFcxC0VAYjxAxZF0Ex2Iqxw AC62BYpTIE1TZKA3svLVAKvSnIqfZI6r4l7I0Y64k_MxkIecxEwVAFwVW5XwCY0x0Ix7I2 Y4AK64vIr41l42xK82IYc2Ij64vIr41l4x8a6c8ajcxJMI8E67AF67kF1VAFwI0_Jr0_Jr ylIxkGc2Ij64vIr41lIxAIcVCF04k26cxKx2IYs7xG6rW3Jr0E3s1l34x0Y48IcVAazs8C jcxJYxBIdaVFxhVjvjDU0xZFpf9x0zEna93UUUUU= X-CM-SenderInfo: pihqwv5uhdzvbu6rjloofrz/1tbirQRCs0X9d63IQQABsy X-Mailman-Approved-At: Wed, 23 Dec 2009 15:03:10 +0000 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Fw: KASSERT when connect to the peer(system is running out of memory) . X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Dec 2009 14:17:06 -0000 DQoNCjIwMDktMTItMjMNCg0KDQoNCmZlbmdkcmVhbWVyDQoNCg0KDQq3orz+yMujuiBmZW5nZHJl YW1lcg0Kt6LLzcqxvOSjuiAyMDA5LTEyLTIyIDIyOjA1OjIwDQrK1bz+yMujuiBmcmVlYnNkLW5l dA0Ks63LzaO6IA0K1vfM4qO6IEtBU1NFUlQgd2hlbiBjb25uZWN0IHRvIHRoZSBwZWVyKHN5c3Rl bSBpcyBydW5uaW5nIG91dCBvZiBtZW1vcnkpIC4NCg0KSGVsbG8gQUxMOg0KDQpJIGFtIHVzaW5n IHRoZSBGcmVlQlNEIDcuMS4gTXkgc3lzdGVtIGlzIHJ1bm5pbmcgb3V0IG9mIG1lbW9yeSwgaW4g dGhpcyBzaWR1dGlvbiB3aGVuIGkgY3JlYXRlIHRoZSBzb2NrZXQgYW5kIGNvbm5lY3QsIHRoZSB0 aGUgS0FTU0VSVCBjb21lIG91dC4gSGVyZSBpcyBteSBkZXNjcmlwdGlvbiwgcGxlYXNlIHJlYWQg dGhlIGJyaWVmIGZpcnN0IGFuZCBnZXQgdGhlIHByb2JsZW0gYW5kIHRoZW4gY29udG51ZSB3aXRo IHRoZSBkZXRhaWwgZGVzY3JpcHRpb24uDQoNCkhvdyBpcyB0aGlzIHByb2JsZW0gaGFwcGVuOg0K QnJpZWYgZGVzY3JpcHRpb246DQoxLiBGaXJzdCwgQ29ubmVjdCBzaWRlIHNlbmQgU1lOIHRvIHRo ZSBsaXN0ZXJuZXINCjIuIFNlY29uZCwgQ29ubmVjdCBzaWRlIHdpbGwgcmV0cmFuc21pdCB0aGUg U1lOIHBhY2tldCwgYnV0IHdoZW4gaXQgYWxsb2MgbWJ1ZiBmYWlsIGluIHRoZSB0Y3Bfb3V0cHV0 LiB0aGUgdGNwX3NuZG54dCB3aWxsIG5vdCBpbmNyZWFzZS4NCjMuIFNZTiBBQ0sgYXJyaXZlcywg dGNwX3NuZHVuYSBpbmNyZWFzZSwgYW5kIHdpbGwgbGFnZXIgdGhlbiB0Y3Bfc25kbnh0IGJ5IDEu IHNlbmRlciBzaWRlIHdpbGwgcmVzcG9uc2UgdGhlIEFDSywgaW52b2tlIHRjcF9vdXRwdXQ6IGxl biBpcyAxLCBidXQgY2MgaXMgemVyby4gS0FTU0VSVCBoYXBwZW4uDQoNCkRldGFpbCBkZXNjcmlw dGlvbjoNCjEuRmlyc3QsIENvbm5lY3Qgc2lkZSBzZW5kIFNZTiB0byB0aGUgbGlzdGVybmVyLCB0 Y3AtPnNuZF9ueHQgd2lsbCBqdXN0IGxhcmdlciB0aGFuIHRoZSB0Y3AtPnNuZF91bmEgYnkgMS4N CjIuIFNlY29uZCwgQ29ubmVjdCBzaWRlIHdpbGwgcmV0cmFuc21pdCB0aGUgU1lOIHBhY2tldC4g VGhlIHJldHJhbnNtaXQgaXMgdHJpZ2VyIGJ5IHRoZSByZXRyYW5zbWl0IHRpbWVyLCBpdCB3aWxs IHRoZW4gcm9sbCBiYWNrIHRoZSB0Y3AtPnNuZF9ueHQgZXF1YWwgdG8gdGNwLT5zbmRfdW5hLiAg YW5kIGJlZ2luIHRvIGNhbGwgdGhlIHRjcF9vdXRwdXQuIElmIHRoZSB0Y3Bfb3V0cHV0IHdvcmtp bmcgZnVuLCB0aGUgdGNwLT5zbmRfbnh0IHdpbGwgdGhlbiBhZHZhbmNlZCBieSAxIGJlZm9yZSBp dCBjYWxscyB0aGUgaXBfb3V0cHV0LiBCdXQgaWYgdGhlIG1idWYgYWxsb2MgZmFpbCwgdGhlIHRj cC0+c25kX254dCB3aWxsIHN0YXkgZXF1YWwgdG8gdGNwLT5zbmRfdW5hLiAob24gbXkgc3lzdGVt LCBtZW1lcnkgaXMgcnVubmluZyBvdXQsIHNvIG1idWYgYWxsb2MgbWF5IGZhaWwuICkgcGxlYXNl IHJlZmVyIHRoZSBiZWxvdyBjb2RlIGluIHRoZSB0Y3Bfb3V0cHV0Og0KDQpNR0VUSERSKG0sIE1f RE9OVFdBSVQsIE1UX0RBVEEpOw0KaWYgKG0gPT0gTlVMTCkgew0KZXJyb3IgPSBFTk9CVUZTOw0K Z290byBvdXQ7IC8vIGdvdG8gb3V0LCBzbyB0aGUgdGNwLT5zbmRfbnh0IHdpbGwgbm90IGluY3Jl YXNlZC4NCn0gDQoNCg0KMy4gYXMgYWJvdmUgZGVzY3JpYnRpb24sIHRoZSB0Y3AtPnNuZF9ueHQg aXMgZXF1YWwgdG8gdGNwLT5zbmRfdW5hLiB0aGVuIHRoZSBTWU4gQUNLIHBhY2tldCBhcnJpdmVz LCBhbmQgdGhlIGNvbm5lY3Rpb24gaXMgZXN0YWJsaXNoZWQsIGFuZCB0aGUgdGNwLT5zbmRfdW5h IHdpbGwgaW5jcmVhc2UgYnkgMS4gQWxzbyB0aGUgY29ubmVjdCBzaWRlIHdpbGwgdGhlbiBzZW5k IHRoZSBsYXN0IEFDSywgaXQgaW52b2RlIHRoZSB0Y3Bfb3V0cHV0LCB0Y3Agb3V0cHV0IGxlbiBp cyBjb21wdXRlIGJ5IHRoZSBiZWxvdyBleHByZXNzaW9uOg0KDQpvZmYgPSB0cC0+c25kX254dCAt IHRwLT5zbmRfdW5hOyANCmxlbiA9ICgobG9uZyl1bG1pbihzby0+c29fc25kLnNiX2NjLCBzZW5k d2luKSAtIG9mZik7IA0KDQpvZmNvdXJzZSB5b3UgaGF2ZSBzZWVuLiB0aGUgb2ZmIGlzIC0xLCB0 aGUgc29fc25kLnNiX2NjIGlzIDAsIHNvIHRoZSBsZW4gaXMgMS4gc28gYmVsb3cgS0FTU0VSVCB3 aWxsIGNhbWU6DQoNCktBU1NFUlQoc2ItPnNiX21iICE9IE5VTEwsICgiJXM6IHNiX21iIGlzIE5V TEwiLCBfX2Z1bmNfXykpOyAvKiAoc2JzbmRwdHIgKSAqLw0KDQpUaGFua3MgDQpSZWdhcmQNCg== From owner-freebsd-net@FreeBSD.ORG Thu Dec 24 08:38:08 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B2B9106568B; Thu, 24 Dec 2009 08:38:08 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-px0-f190.google.com (mail-px0-f190.google.com [209.85.216.190]) by mx1.freebsd.org (Postfix) with ESMTP id 404178FC08; Thu, 24 Dec 2009 08:38:08 +0000 (UTC) Received: by pxi28 with SMTP id 28so5331722pxi.7 for ; Thu, 24 Dec 2009 00:38:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=caedL7hv6QsAGepQhqt5W31GLnQoWkmroQhyBxyZe7U=; b=VYk7Fk55ROIbxpOC2K7V2BL0Y0I9NinZKPNjXL+acLGYd1A3qpgQI6KnpP+XlL8ENQ /fekRSdh5wod6bL4U1NATZoUnM8lq7sPSIkyb2lDl+VvATSBaVVVdQEukw8Bt+cKmWTU u41F+p92m0iln1hBU8TJ8WwiluX7EdZ6bx7KY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ngeM11l19XDpExuTOiHnFd3NbjO8AIBEXnzXaAGb8LBC/XQ6iVS/0+qn/aoVy8wyWE LmbUgXfrRfwdOdOvPbqPRq9vWoOwHdmCgc8lyedOmbsaE0xFvWb/DF/rJQOlhdQr/VAC FY2iIL1aMq4GghUzrGW5Z83d7stcuFKiPMBcs= MIME-Version: 1.0 Received: by 10.114.54.12 with SMTP id c12mr7741064waa.81.1261643887828; Thu, 24 Dec 2009 00:38:07 -0800 (PST) Date: Thu, 24 Dec 2009 00:38:07 -0800 Message-ID: From: Xin LI To: FreeBSD Stable , freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: Routing question (GRE packet vs normal traceroute)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 08:38:08 -0000 Hi, A friend of mine has encountered some problem in his setup which consists a pair of GRE peer, one running on OpenBSD and another running FreeBSD 7.2-RELEASE; with 7.2-STABLE, there is no improvement over the situation. The problem we have observed seems to be related to GRE packet not being routed as observed, here is some details: - The FreeBSD box has one network interface connected to two (2) upstream network, with different IP and does not belong to the same subnet, say, one is 1.2.3.4/24 and another is 5.6.7.8/24 - The default gateway can be reached through the first IP address bound to the network interface; - An explicit route has been configured to the OpenBSD host, the gateway being used can be reached directly via the secondary (aliased 5.6.7.8/24) IP. - Both the default gateway and the explicit host route can reach the OpenBSD route. The problem they had is, while traceroute to the OpenBSD host can give the desired result, however, packets that is supposed to be transferred through the GRE tunnel, while they will be encapsulated into a GRE packet, the GRE packet itself won't go to the explicit host route, but end up going to the default gateway. The friend has configured his switch to "bounce" the packet back to the server by configuring a host route on L3 switch, and it seems that the FreeBSD box is able to route the GRE packet to its desired gateway this time. Any suggestions? Cheers, -- Xin LI http://www.delphij.net From owner-freebsd-net@FreeBSD.ORG Thu Dec 24 15:05:21 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F409C10656A6 for ; Thu, 24 Dec 2009 15:05:20 +0000 (UTC) (envelope-from cjeker@diehard.n-r-g.com) Received: from diehard.n-r-g.com (diehard.n-r-g.com [62.48.3.9]) by mx1.freebsd.org (Postfix) with ESMTP id 1F0338FC08 for ; Thu, 24 Dec 2009 15:05:19 +0000 (UTC) Received: (qmail 2796 invoked by uid 1001); 24 Dec 2009 15:05:18 -0000 Date: Thu, 24 Dec 2009 16:05:18 +0100 From: Claudio Jeker To: freebsd-net@freebsd.org Message-ID: <20091224150518.GA21386@diehard.n-r-g.com> Mail-Followup-To: Claudio Jeker , freebsd-net@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Routing question (GRE packet vs normal traceroute)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 15:05:21 -0000 On Thu, Dec 24, 2009 at 12:38:07AM -0800, Xin LI wrote: > Hi, > > A friend of mine has encountered some problem in his setup which > consists a pair of GRE peer, one running on OpenBSD and another > running FreeBSD 7.2-RELEASE; with 7.2-STABLE, there is no improvement > over the situation. The problem we have observed seems to be related > to GRE packet not being routed as observed, here is some details: > > - The FreeBSD box has one network interface connected to two (2) > upstream network, with different IP and does not belong to the same > subnet, say, one is 1.2.3.4/24 and another is 5.6.7.8/24 > - The default gateway can be reached through the first IP address > bound to the network interface; > - An explicit route has been configured to the OpenBSD host, the > gateway being used can be reached directly via the secondary (aliased > 5.6.7.8/24) IP. > - Both the default gateway and the explicit host route can reach the > OpenBSD route. > > The problem they had is, while traceroute to the OpenBSD host can give > the desired result, however, packets that is supposed to be > transferred through the GRE tunnel, while they will be encapsulated > into a GRE packet, the GRE packet itself won't go to the explicit host > route, but end up going to the default gateway. > > The friend has configured his switch to "bounce" the packet back to > the server by configuring a host route on L3 switch, and it seems that > the FreeBSD box is able to route the GRE packet to its desired gateway > this time. > > Any suggestions? > gre(4) is caching the route to the destination on creation time (when the ifconfig greX tunnel src_addr dest_addr command is issued). So you need to create the host route to the openbsd box before configuring the gre tunnel. It should be possible to reconfigure the tunnel-endpoints which should redo the route lookup resulting in a correct routing. -- :wq Claudio From owner-freebsd-net@FreeBSD.ORG Thu Dec 24 17:15:28 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA9C81065693 for ; Thu, 24 Dec 2009 17:15:28 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-iw0-f198.google.com (mail-iw0-f198.google.com [209.85.223.198]) by mx1.freebsd.org (Postfix) with ESMTP id A31388FC1E for ; Thu, 24 Dec 2009 17:15:28 +0000 (UTC) Received: by iwn36 with SMTP id 36so5646624iwn.3 for ; Thu, 24 Dec 2009 09:15:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=2B90d4vSUqdMvHkrBkXdp9rh+f8cjnQEJ/yrZY98Rck=; b=AJlr4JXXxD09FcpHSKNBjlTx565HEmaADvH8S4840GJTc3TfHtJjeBNFlCtFfrwrFX e2jiwmSdovZmdwxnh4jxo1GXvwHcHVPXrIUT0mmSDKoxNgcM9M92du44RkCisx32ctxD Q+/6xevctSh/Mp4btE0XlInyo9WK2opPCCq7Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=MZCCoXoGZkYel3zcY8Qh46cS3wZFspQNnX6iTk8AvF8B5ickZCBVEZcwIx1nMsaYfF 6hFztHFoHohD80f6ZpQkRSP/dKPtpgYlstmrf6fdFpSzEdbZAd3g5rz+2LNZxzu0+/Kk 47ccwuIj8C+UqosCLDA8SQMu+DVVjYw+NaAgo= MIME-Version: 1.0 Received: by 10.231.29.149 with SMTP id q21mr1454478ibc.35.1261674927957; Thu, 24 Dec 2009 09:15:27 -0800 (PST) In-Reply-To: <3a142e750912200524i3618bf49v6a54ee797667c921@mail.gmail.com> References: <3a142e750912200524i3618bf49v6a54ee797667c921@mail.gmail.com> Date: Thu, 24 Dec 2009 09:15:27 -0800 Message-ID: From: Kurt Buff To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: 8.0R, AMD64 and wpi is giving me major grief X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 17:15:28 -0000 On Sun, Dec 20, 2009 at 05:24, Paul B Mahol wrote: > On 12/17/09, Kurt Buff wrote: >> Anyone? >> >> BTW - I dual-boot this with XP, and don't have any issues with >> wireless when running that. Also works flawlessly when running wired, >> over em0. >> >> I've just done a BIOS update - I'll be trying that out tomorrow, and >> will update this with results. >> >> Kurt >> >> On Mon, Dec 14, 2009 at 19:21, Kurt Buff wrote: >>> All, >>> >>> I've got a Lenovo t61 with 4gbytes RAM that is giving me fits. >>> >>> It's got a 3945abg chip in it, and it's getting really flaky. I can >>> boot it up, and work at the console for a while, and that seems to >>> work OK, usually. >>> >>> However, today, when I start up my gui (xfce4), wireless just dies on >>> me. For a week before, it would usually run for a while (sometimes >>> days) before dying on me and requiring a reboot. >>> >>> Below is a snippet of /var/log/messages - Does this mean anything to >>> anyone? Is there anything I can do to recover once this happens? >>> >>> Thanks, >>> >>> Kurt >>> >>> Dec 14 07:16:43 grimsqueaker kernel: wlan0: Ethernet address: >>> 00:1f:3c:4d:e2:55 >>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 1 >>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 3 >>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 4 >>> Dec 14 07:16:43 grimsqueaker kernel: microcode alive notification >>> version 10e02 alive 1 >>> Dec 14 07:16:43 grimsqueaker kernel: microcode alive notification >>> version 10e02 alive 1 >>> Dec 14 07:16:43 grimsqueaker kernel: wpi_newstate: INIT -> SCAN flags 0x0 >>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: CTRL-EVENT-SCAN-RESULTS >>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: Trying to associate >>> with 00:23:69:82:b2:bf (SSID='5705NE197th' freq=2462 MHz) >>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: SCAN -> AUTH flags 0x0 >>> Dec 14 07:16:45 grimsqueaker kernel: config chan 11 flags 8005 cck f ofdm >>> 15 >>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: AUTH -> ASSOC flags 0x0 >>> Dec 14 07:16:45 grimsqueaker kernel: >>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: Associated with >>> 00:23:69:82:b2:bf >>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: ASSOC -> RUN flags 0x0 >>> Dec 14 07:16:45 grimsqueaker kernel: config chan 11 flags 8035 >>> Dec 14 07:16:45 grimsqueaker kernel: wlan0: link state changed to UP >>> Dec 14 07:16:45 grimsqueaker kernel: wpi0: need multicast update callback >>> Dec 14 07:16:46 grimsqueaker wpa_supplicant[381]: WPA: Key negotiation >>> completed with 00:23:69:82:b2:bf [PTK=CCMP GTK=CCMP] >>> Dec 14 07:16:46 grimsqueaker wpa_supplicant[381]: CTRL-EVENT-CONNECTED >>> - Connection to 00:23:69:82:b2:bf completed (auth) [id=0 id_str=] >>> Dec 14 07:16:53 grimsqueaker dhclient: New IP Address (wlan0): >>> 192.168.151.104 >>> Dec 14 07:16:53 grimsqueaker kernel: wpi0: need multicast update callback >>> Dec 14 07:16:53 grimsqueaker kernel: wpi0: need multicast update callback >>> Dec 14 07:16:53 grimsqueaker dhclient: New Subnet Mask (wlan0): >>> 255.255.255.0 >>> Dec 14 07:16:53 grimsqueaker dhclient: New Broadcast Address (wlan0): >>> 192.168.151.255 >>> Dec 14 07:16:53 grimsqueaker dhclient: New Routers (wlan0): 192.168.151.1 >>> Dec 14 07:17:56 grimsqueaker kernel: drm0: on vgapci0 >>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] MSI enabled 1 message(s) >>> Dec 14 07:17:56 grimsqueaker kernel: vgapci0: child drm0 requested >>> pci_enable_busmaster >>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] AGP at 0xe0000000 256MB >>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] Initialized i915 1.6.0 >>> 20080730 >>> Dec 14 07:17:57 grimsqueaker kernel: drm0: [ITHREAD] >>> Dec 14 07:18:24 grimsqueaker kernel: pid 1424 (xfce4-panel), uid 1001: >>> exited on signal 11 (core dumped) >>> Dec 14 07:25:43 grimsqueaker wpa_supplicant[381]: WPA: Group rekeying >>> completed with 00:23:69:82:b2:bf [GTK=CCMP] >>> Dec 14 07:48:38 grimsqueaker kernel: wpi0: device timeout >>> Dec 14 07:48:39 grimsqueaker kernel: wpi0: could not set power mode >>> > > Enable all wpi debug messages? sysctl debug.wpi=-2 <<--- is this correct? Sorry for the delay - between work, sick child and lack of extra on which to try this, I've been distracted from this task. Kurt From owner-freebsd-net@FreeBSD.ORG Thu Dec 24 18:47:48 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0505106568D for ; Thu, 24 Dec 2009 18:47:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outQ.internet-mail-service.net (outq.internet-mail-service.net [216.240.47.240]) by mx1.freebsd.org (Postfix) with ESMTP id 952E18FC1C for ; Thu, 24 Dec 2009 18:47:48 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 5526B27861; Thu, 24 Dec 2009 10:47:48 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id CEC3B2D6018; Thu, 24 Dec 2009 10:47:47 -0800 (PST) Message-ID: <4B33B76B.5070600@elischer.org> Date: Thu, 24 Dec 2009 10:48:11 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Xin LI References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, FreeBSD Stable Subject: Re: Routing question (GRE packet vs normal traceroute)? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 18:47:48 -0000 Xin LI wrote: > Hi, > > A friend of mine has encountered some problem in his setup which > consists a pair of GRE peer, one running on OpenBSD and another > running FreeBSD 7.2-RELEASE; with 7.2-STABLE, there is no improvement > over the situation. The problem we have observed seems to be related > to GRE packet not being routed as observed, here is some details: > > - The FreeBSD box has one network interface connected to two (2) > upstream network, with different IP and does not belong to the same > subnet, say, one is 1.2.3.4/24 and another is 5.6.7.8/24 > - The default gateway can be reached through the first IP address > bound to the network interface; > - An explicit route has been configured to the OpenBSD host, the > gateway being used can be reached directly via the secondary (aliased > 5.6.7.8/24) IP. > - Both the default gateway and the explicit host route can reach the > OpenBSD route. > > The problem they had is, while traceroute to the OpenBSD host can give > the desired result, however, packets that is supposed to be > transferred through the GRE tunnel, while they will be encapsulated > into a GRE packet, the GRE packet itself won't go to the explicit host > route, but end up going to the default gateway. > > The friend has configured his switch to "bounce" the packet back to > the server by configuring a host route on L3 switch, and it seems that > the FreeBSD box is able to route the GRE packet to its desired gateway > this time. > > Any suggestions? there is a hack in the GRE code "that you can turn off" where the GRE envelope is looking up the address of the peer *WITH THE LAST BIT SWITCHED* try adding a route to the address of the openBSD host with /31 (not 32) I forget how to turn it off but th man page says. there IS a good reason for it if you want packets for the OpenBSD host itself to go through the tunnel.. Then you need to not use that address itself or you get a routing loop. > > Cheers, From owner-freebsd-net@FreeBSD.ORG Thu Dec 24 19:42:22 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B612D1065679 for ; Thu, 24 Dec 2009 19:42:22 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id 680B08FC16 for ; Thu, 24 Dec 2009 19:42:22 +0000 (UTC) Received: by qyk6 with SMTP id 6so3591946qyk.3 for ; Thu, 24 Dec 2009 11:42:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=lB4t8P3Z0wkCx4PWXwL9bfSfcA214MqGWppMUEcvdVQ=; b=ECq8KLDJ35qMtm9GW+I9RQ/gFo0YZm7/U2vFFpnMDZm8xxub45EUpffc6OtQkLlE2z 2rWhBNaw8/p2b0b8h7pYYAXGL5rX3Kxg2gjJSuTxOBHZEuyvKRhL6RKcEf18xLU40aqs NYnMPYm/RHivWBVXop0+N99NxB2VL/m5rmwVA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=EJ+ybxExvWSNgsZyv8Rp92uKs9kxdKjzFPGyHOKOotStVGoUT7o8lqtEA6uhFUrcuv y+xKUwKWsgGlpMeFkQBsLaqS/pDGsWmDFPDHdQGN+RM71QmlxPRDwVEQUhOCs2XIQjQi 0ONe/PKrtcygXI31tp9QE8xM4fDi5p8ZuISMc= Received: by 10.224.97.200 with SMTP id m8mr6071017qan.141.1261683741916; Thu, 24 Dec 2009 11:42:21 -0800 (PST) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 22sm7538524qyk.10.2009.12.24.11.42.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 24 Dec 2009 11:42:20 -0800 (PST) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 24 Dec 2009 11:42:14 -0800 From: Pyun YongHyeon Date: Thu, 24 Dec 2009 11:42:14 -0800 To: "Lhunath (Maarten B.)" Message-ID: <20091224194214.GE8146@michelle.cdnetworks.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-net@freebsd.org Subject: Re: mskc0: Tx descriptor error X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 19:42:22 -0000 On Wed, Dec 23, 2009 at 10:11:11AM +0100, Lhunath (Maarten B.) wrote: > Hey, > > I'm having problems getting my Marvell Yukon to work. I can successfully get it set up using DHCP, but when I start using it, I get error messages such as: "mskc0: Tx descriptor error" and "msk0: watchdog timeout". This is using the msk(4) module from 8.0-RELEASE. > > A bit of googling indicates that this problem is not uncommon, but had each time been resolved by patches that appear to have already been applied to the msk module that I'm using. > > Some help would be appreciated. Here is the ''dmesg'' output with bootverbose on and a ''vmstat -i'' should it matter. > > From dmesg: > > mskc0: port 0xe800-0xe8ff mem 0xfebfc000-0xfebfffff irq 17 at device 0.0 on pci4 > pcib4: mskc0 requested memory range 0xfebfc000-0xfebfffff: good > mskc0: MSI count : 1 > mskc0: attempting to allocate 1 MSI vectors (1 supported) > msi: routing MSI IRQ 256 to local APIC 0 vector 58 > mskc0: using IRQ 256 for MSI > mskc0: RAM buffer size : 0KB > msk0: on mskc0 > msk0: bpf attached > msk0: Ethernet address: 00:1f:c6:83:a7:d0 > miibus0: on msk0 > e1000phy0: PHY 0 on miibus0 > e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto I guess you hit known msk(4) issue for 88E8056/88E1149 PHY. Some users have no problems but others seem to suffer from the issue. There is also a PR about this but it seems it's hard to fix that mainly because I don't have access to the hardware. > mskc0: [MPSAFE] > mskc0: [FILTER] > pci5: driver added > pci6: driver added > msk0: link state changed to DOWN > msk0: link state changed to UP > mskc0: Tx descriptor error > mskc0: Tx descriptor error > mskc0: Tx descriptor error > mskc0: Tx descriptor error > mskc0: Tx descriptor error > mskc0: Tx descriptor error > mskc0: Tx descriptor error > mskc0: Tx descriptor error > mskc0: Tx descriptor error > mskc0: Tx descriptor error > msk0: watchdog timeout > msk0: link state changed to DOWN > msk0: link state changed to UP From owner-freebsd-net@FreeBSD.ORG Thu Dec 24 21:25:49 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE948106566C for ; Thu, 24 Dec 2009 21:25:49 +0000 (UTC) (envelope-from lhunath@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 6FDF38FC0C for ; Thu, 24 Dec 2009 21:25:49 +0000 (UTC) Received: by ewy26 with SMTP id 26so5121958ewy.3 for ; Thu, 24 Dec 2009 13:25:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:content-type:mime-version :subject:from:in-reply-to:date:content-transfer-encoding:message-id :references:to:x-mailer; bh=H512J9h0CryOhonkCxvnd6DrJYadaEHXYDwEffNvs6Y=; b=jXhm0xCnF/f60RkGvz1t/YB8R4lSVj+aWu87VDC3hxBnrXUy0RjxeeGRXOvUSVKPFO Z81Obbz5alMXkTqrXlCzAVr2Zmi9iiDfZlukU8ZWYcMsgdsN1P6mQsv8+RoljOfl8/A6 XN7AzdGsu7NA3/Go/yTJ/lcBEHqcZSPkHH2f8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to:x-mailer; b=V/Ns8tQG4PsOiBpmPotmxZTxpcZW2VsUdNoYJoAwxKMIalpO0NutPSl7myHjnE7lug 0I2aSocw5Ekd5o0lfJH2aoDCb1mcPYbluoVOY5tXddO4FgVOfl4r6pI7Vv28hFoP3iUp LprCqEEUUdS4z2Wk9ijYCx04tjh9I8cIFtZ5Q= Received: by 10.213.110.17 with SMTP id l17mr4294725ebp.18.1261689948358; Thu, 24 Dec 2009 13:25:48 -0800 (PST) Received: from ?192.168.20.2? ([217.72.231.53]) by mx.google.com with ESMTPS id 13sm6042826ewy.13.2009.12.24.13.25.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 24 Dec 2009 13:25:47 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1077) From: "Lhunath (Maarten B.)" In-Reply-To: <20091224194214.GE8146@michelle.cdnetworks.com> Date: Thu, 24 Dec 2009 22:25:46 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <5D9DCA13-95CC-4848-AAFF-04900CE841B2@gmail.com> References: <20091224194214.GE8146@michelle.cdnetworks.com> To: freebsd-net@freebsd.org X-Mailer: Apple Mail (2.1077) Subject: Re: mskc0: Tx descriptor error X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 21:25:50 -0000 >> e1000phy0: PHY 0 on miibus0 >> e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, = 1000baseT, 1000baseT-FDX, auto >=20 > I guess you hit known msk(4) issue for 88E8056/88E1149 PHY. Some > users have no problems but others seem to suffer from the issue. > There is also a PR about this but it seems it's hard to fix that > mainly because I don't have access to the hardware. Perhaps if you can provide patches against the 8.0-REL msk(1) to make it = extremely verbose, I could provide the output and we might learn more = about the cause of this issue. The fact that it's so easily reproduced = must play in favor. I'm afraid I simply have not got the time and resources to learn about = both the FreeBSD kernel + module writing and network interface driver = operations. The only alternative would be to wait until somebody that = does happens upon this hardware.= From owner-freebsd-net@FreeBSD.ORG Thu Dec 24 22:09:48 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BD56106566B for ; Thu, 24 Dec 2009 22:09:48 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id 2A0E38FC08 for ; Thu, 24 Dec 2009 22:09:48 +0000 (UTC) Received: by qyk6 with SMTP id 6so3622101qyk.3 for ; Thu, 24 Dec 2009 14:09:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:organization:x-operation-sytem; bh=2AXW8zcX6246uBIWqZ80XNqUYXPxp1w2s4qAZPO7tgQ=; b=sI7k2ZVJL21JqivaFdg63JaFkGd1hYBMqTmUbovjgy1hsZzK0mswJfa/+4mTElCQH2 7pqMjg9uG645fYfE2/ePADN2G4lHQGza0zFIePG+KY+wpz9Ib6klDnkwy2JYsEpsD9MF qkhvNjOI63fU+ROOhC3uLfdQpA7sFq1q1M4pg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent:organization:x-operation-sytem; b=ixWg7PKItwhEsomnY7/Q49bsgRzXzlCdK2/TunhuFGBML1unU6kzBywtcV/omJFttb inlqpcI+ZQSXjrGQuwWtM/FlqQ/vdgJX/oOx4BsMJgo26U0hw27UJIO6Yf/lvIovtO3m ST+DnwYE1UirXdYyfqSVRV7QbYMPk4rS8ppVA= Received: by 10.224.106.4 with SMTP id v4mr3566603qao.78.1261692587535; Thu, 24 Dec 2009 14:09:47 -0800 (PST) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id 8sm24118671qwj.13.2009.12.24.14.09.45 (version=SSLv3 cipher=RC4-MD5); Thu, 24 Dec 2009 14:09:46 -0800 (PST) Received: by weongyo (sSMTP sendmail emulation); Thu, 24 Dec 2009 14:09:42 -0800 From: Weongyo Jeong Date: Thu, 24 Dec 2009 14:09:42 -0800 To: Steven Friedrich Message-ID: <20091224220942.GC1491@weongyo> Mail-Followup-To: Steven Friedrich , freebsd-net@freebsd.org References: <200912151603.32111.freebsd@insightbb.com> <20091222193104.GH1479@weongyo> <200912221754.25692.freebsd@insightbb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200912221754.25692.freebsd@insightbb.com> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: freebsd-net@freebsd.org Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Weongyo Jeong List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 22:09:48 -0000 On Tue, Dec 22, 2009 at 05:54:25PM -0500, Steven Friedrich wrote: > On Tuesday 22 December 2009 02:31:04 pm Weongyo Jeong wrote: > > On Tue, Dec 15, 2009 at 04:03:31PM -0500, Steven Friedrich wrote: > > > Ok, I am able to load firmware with: > > > uathload -d /dev/ugen4.3 > > > but it also appears to do so when I plug it in... > > > > > > Now what? It doesn't show up in ifconfig... > > > > Could you please show me dmesg output and the output of > > > > # usbconfig dump_device_desc > This message appears on the console when the device is plugged in: > ugen4.3: < Atheros Communications Inc > at usbus4 > > usbconfig -u 4 -a 3 dump_info > ugen4.3: at usbus4, cfg=0 md=HOST spd=HIGH > (480Mbps) pwr=ON > > The device doesn't show up in ifconfig, so the example from the man page: > ifconfig wlan create wlandev uath0 > > doesn't work because uath0 isn't found by ifconfig. > ifconfig wlan0 create wlandev uath0 > ifconfig: SIOCIFCREATE2: Device not configured > > I filed a PR against usb, probably should have made it net. Sorry. OK. It looks weird idProduct didn't be decreased 1 after loading the firmware. And what I'd like to see is the *full* result of the following steps: 1. plugs in your USB device. 2. run commands as follows: # kldload if_uath # dmesg | tail # uathload -v -d /dev/ugen4.3 # dmesg | tail In a theory, after loading the firmware normally the device which at the moment idProduct is 0x4251 is detached and reseted then it should be reattached with idProduct(0x4250). regards, Weongyo Jeong From owner-freebsd-net@FreeBSD.ORG Thu Dec 24 23:47:39 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D5DD1065692 for ; Thu, 24 Dec 2009 23:47:39 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-iw0-f198.google.com (mail-iw0-f198.google.com [209.85.223.198]) by mx1.freebsd.org (Postfix) with ESMTP id 459538FC18 for ; Thu, 24 Dec 2009 23:47:39 +0000 (UTC) Received: by iwn36 with SMTP id 36so5769470iwn.3 for ; Thu, 24 Dec 2009 15:47:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=/+DZ0WbLEiYS3RgJQvfKgoxmxxPSc+AFhTOtVLOFXIQ=; b=OuNiOtDQjnWdGwqhA5eEQquq6eUlD9azjMKCCT1Kk97QlA1ZevOoJTim/vGh8g96sQ FobXjFv9vaZcSSU8HbkC7gCPi/eCJ/GDeYvQdFU7QtwXgUUSF/EyKTZhDEtlscaRgxNM d+Q9mr7wdMZliRrahw4rJ8eAVJ4yAkYyS2osY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=FBfXcd1MC7USiS4VIMnWybeXbuajx1VXVhKjwzSgAyko1GSAob8cjl4chUudfr3O8M Rad342UjIZcTGY6Wp/KnmvJPSJJYSyN95sTMhDhvD3trK1FijZIxQKs/amy8JcUbuIiM BPqCh4l7HO00Bzb1jQfyA9RVAO9u9Mv38BMfk= MIME-Version: 1.0 Received: by 10.231.125.13 with SMTP id w13mr1445831ibr.32.1261698458518; Thu, 24 Dec 2009 15:47:38 -0800 (PST) In-Reply-To: <3a142e750912200524i3618bf49v6a54ee797667c921@mail.gmail.com> References: <3a142e750912200524i3618bf49v6a54ee797667c921@mail.gmail.com> Date: Thu, 24 Dec 2009 15:47:38 -0800 Message-ID: From: Kurt Buff To: freebsd-net@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: Re: 8.0R, AMD64 and wpi is giving me major grief X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Dec 2009 23:47:39 -0000 On Sun, Dec 20, 2009 at 05:24, Paul B Mahol wrote: > On 12/17/09, Kurt Buff wrote: >> Anyone? >> >> BTW - I dual-boot this with XP, and don't have any issues with >> wireless when running that. Also works flawlessly when running wired, >> over em0. >> >> I've just done a BIOS update - I'll be trying that out tomorrow, and >> will update this with results. >> >> Kurt >> >> On Mon, Dec 14, 2009 at 19:21, Kurt Buff wrote: >>> All, >>> >>> I've got a Lenovo t61 with 4gbytes RAM that is giving me fits. >>> >>> It's got a 3945abg chip in it, and it's getting really flaky. I can >>> boot it up, and work at the console for a while, and that seems to >>> work OK, usually. >>> >>> However, today, when I start up my gui (xfce4), wireless just dies on >>> me. For a week before, it would usually run for a while (sometimes >>> days) before dying on me and requiring a reboot. >>> >>> Below is a snippet of /var/log/messages - Does this mean anything to >>> anyone? Is there anything I can do to recover once this happens? >>> >>> Thanks, >>> >>> Kurt >>> >>> Dec 14 07:16:43 grimsqueaker kernel: wlan0: Ethernet address: >>> 00:1f:3c:4d:e2:55 >>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 1 >>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 3 >>> Dec 14 07:16:43 grimsqueaker kernel: wpi0: timeout resetting Tx ring 4 >>> Dec 14 07:16:43 grimsqueaker kernel: microcode alive notification >>> version 10e02 alive 1 >>> Dec 14 07:16:43 grimsqueaker kernel: microcode alive notification >>> version 10e02 alive 1 >>> Dec 14 07:16:43 grimsqueaker kernel: wpi_newstate: INIT -> SCAN flags 0x0 >>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: CTRL-EVENT-SCAN-RESULTS >>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: Trying to associate >>> with 00:23:69:82:b2:bf (SSID='5705NE197th' freq=2462 MHz) >>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: SCAN -> AUTH flags 0x0 >>> Dec 14 07:16:45 grimsqueaker kernel: config chan 11 flags 8005 cck f ofdm >>> 15 >>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: AUTH -> ASSOC flags 0x0 >>> Dec 14 07:16:45 grimsqueaker kernel: >>> Dec 14 07:16:45 grimsqueaker wpa_supplicant[381]: Associated with >>> 00:23:69:82:b2:bf >>> Dec 14 07:16:45 grimsqueaker kernel: wpi_newstate: ASSOC -> RUN flags 0x0 >>> Dec 14 07:16:45 grimsqueaker kernel: config chan 11 flags 8035 >>> Dec 14 07:16:45 grimsqueaker kernel: wlan0: link state changed to UP >>> Dec 14 07:16:45 grimsqueaker kernel: wpi0: need multicast update callback >>> Dec 14 07:16:46 grimsqueaker wpa_supplicant[381]: WPA: Key negotiation >>> completed with 00:23:69:82:b2:bf [PTK=CCMP GTK=CCMP] >>> Dec 14 07:16:46 grimsqueaker wpa_supplicant[381]: CTRL-EVENT-CONNECTED >>> - Connection to 00:23:69:82:b2:bf completed (auth) [id=0 id_str=] >>> Dec 14 07:16:53 grimsqueaker dhclient: New IP Address (wlan0): >>> 192.168.151.104 >>> Dec 14 07:16:53 grimsqueaker kernel: wpi0: need multicast update callback >>> Dec 14 07:16:53 grimsqueaker kernel: wpi0: need multicast update callback >>> Dec 14 07:16:53 grimsqueaker dhclient: New Subnet Mask (wlan0): >>> 255.255.255.0 >>> Dec 14 07:16:53 grimsqueaker dhclient: New Broadcast Address (wlan0): >>> 192.168.151.255 >>> Dec 14 07:16:53 grimsqueaker dhclient: New Routers (wlan0): 192.168.151.1 >>> Dec 14 07:17:56 grimsqueaker kernel: drm0: on vgapci0 >>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] MSI enabled 1 message(s) >>> Dec 14 07:17:56 grimsqueaker kernel: vgapci0: child drm0 requested >>> pci_enable_busmaster >>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] AGP at 0xe0000000 256MB >>> Dec 14 07:17:56 grimsqueaker kernel: info: [drm] Initialized i915 1.6.0 >>> 20080730 >>> Dec 14 07:17:57 grimsqueaker kernel: drm0: [ITHREAD] >>> Dec 14 07:18:24 grimsqueaker kernel: pid 1424 (xfce4-panel), uid 1001: >>> exited on signal 11 (core dumped) >>> Dec 14 07:25:43 grimsqueaker wpa_supplicant[381]: WPA: Group rekeying >>> completed with 00:23:69:82:b2:bf [GTK=CCMP] >>> Dec 14 07:48:38 grimsqueaker kernel: wpi0: device timeout >>> Dec 14 07:48:39 grimsqueaker kernel: wpi0: could not set power mode >>> > > Enable all wpi debug messages? > > -- > Paul B Mahol So, I su'ed to root after a clean reboot, before entering xfce4, entered the command sysctl debug.wpi=-2 and the console started spewing incredible amounts of messages. Typing blind, I exited su, started xfce4 as my account, and the console was still spewing, and now it works. I have also exited, rebooted clean again, and it still works. BTW - I should mention that I updated to STABLE a few days ago, though that didn't help at all - I was experiencing the same issues: # uname -a FreeBSD grimsqueaker.pigfarm.org 8.0-STABLE FreeBSD 8.0-STABLE #0: Fri Dec 18 18:26:33 PST 2009 root@grimsqueaker.pigfarm.org:/usr/obj/usr/src/sys/GENERIC amd64 I'll work with whomever to see if we can replicate and diagnose the problem. Kurt From owner-freebsd-net@FreeBSD.ORG Fri Dec 25 06:09:18 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D660D106566B for ; Fri, 25 Dec 2009 06:09:18 +0000 (UTC) (envelope-from freebsd@insightbb.com) Received: from mxsf04.insightbb.com (mxsf04.insightbb.com [74.128.0.74]) by mx1.freebsd.org (Postfix) with ESMTP id 92CE38FC12 for ; Fri, 25 Dec 2009 06:09:18 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.47,453,1257138000"; d="scan'208";a="776436010" Received: from unknown (HELO asav03.insightbb.com) ([172.31.249.123]) by mxsf04.insightbb.com with ESMTP; 25 Dec 2009 01:09:17 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmgFAFjlM0vQLicL/2dsb2JhbACBS9U7hDMEgWU X-IronPort-AV: E=Sophos;i="4.47,453,1257138000"; d="scan'208";a="118461210" Received: from 208-46-39-11.dia.static.qwest.net (HELO laptop2.stevenfriedrich.org) ([208.46.39.11]) by asavout03.insightbb.com with ESMTP; 25 Dec 2009 01:09:17 -0500 From: Steven Friedrich To: freebsd-net@freebsd.org Date: Fri, 25 Dec 2009 01:09:14 -0500 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; i386; ; ) References: <200912151603.32111.freebsd@insightbb.com> <200912221754.25692.freebsd@insightbb.com> <20091224220942.GC1491@weongyo> In-Reply-To: <20091224220942.GC1491@weongyo> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912250109.14305.freebsd@insightbb.com> Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Dec 2009 06:09:18 -0000 On Thursday 24 December 2009 05:09:42 pm Weongyo Jeong wrote: > OK. It looks weird idProduct didn't be decreased 1 after loading the > firmware. > > And what I'd like to see is the *full* result of the following steps: > > 1. plugs in your USB device. > 2. run commands as follows: > > # kldload if_uath > # dmesg | tail > # uathload -v -d /dev/ugen4.3 > # dmesg | tail > > In a theory, after loading the firmware normally the device which at the > moment idProduct is 0x4251 is detached and reseted then it should be > reattached with idProduct(0x4250). > root@laptop2(/dev/pts/1)/root/bugs 101% kldload if_uath root@laptop2(/dev/pts/1)/root/bugs 102% dmesg|tail info: [drm] Num pipes: 1 info: [drm] Loading R300 Microcode info: [drm] Num pipes: 1 ugen4.3: at usbus4 info: [drm] Num pipes: 1 ugen4.3: at usbus4 (disconnected) ugen4.3: at usbus4 info: [drm] Loading R300 Microcode info: [drm] Num pipes: 1 info: [drm] Num pipes: 1 root@laptop2(/dev/pts/1)/root/bugs 103% uathload -v -d /dev/ugen4.3 Load firmware ar5523.bin (builtin) to /dev/ugen4.3 send block 0: 147368 bytes remaining : data... : wait for ack... uathload: error reading msg (/dev/usb/4.3.1): No such file or directory root@laptop2(/dev/pts/1)/root/bugs 104% dmesg|tail info: [drm] Num pipes: 1 info: [drm] Loading R300 Microcode info: [drm] Num pipes: 1 ugen4.3: at usbus4 info: [drm] Num pipes: 1 ugen4.3: at usbus4 (disconnected) ugen4.3: at usbus4 info: [drm] Loading R300 Microcode info: [drm] Num pipes: 1 info: [drm] Num pipes: 1 From owner-freebsd-net@FreeBSD.ORG Fri Dec 25 06:17:13 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A668F106566C for ; Fri, 25 Dec 2009 06:17:13 +0000 (UTC) (envelope-from freebsd@insightbb.com) Received: from mxsf01.insightbb.com (mxsf01.insightbb.com [74.128.0.71]) by mx1.freebsd.org (Postfix) with ESMTP id 6820E8FC0C for ; Fri, 25 Dec 2009 06:17:13 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.47,453,1257138000"; d="scan'208";a="787688897" Received: from unknown (HELO mxsf11.insightbb.com) ([172.31.249.227]) by mxsf01.insightbb.com with ESMTP; 25 Dec 2009 01:17:12 -0500 X-IronPort-AV: E=Sophos;i="4.47,453,1257138000"; d="scan'208";a="14329163" Received: from unknown (HELO asav03.insightbb.com) ([172.31.249.123]) by mxsf11.insightbb.com with ESMTP; 25 Dec 2009 01:17:12 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmgFAKrnM0vQLicL/2dsb2JhbACBS9U6hDMEgWU X-IronPort-AV: E=Sophos;i="4.47,453,1257138000"; d="scan'208";a="118461677" Received: from 208-46-39-11.dia.static.qwest.net (HELO laptop2.stevenfriedrich.org) ([208.46.39.11]) by asavout03.insightbb.com with ESMTP; 25 Dec 2009 01:17:11 -0500 From: Steven Friedrich To: freebsd-net@freebsd.org Date: Fri, 25 Dec 2009 01:17:00 -0500 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; i386; ; ) References: <200912151603.32111.freebsd@insightbb.com> <200912221754.25692.freebsd@insightbb.com> <20091224220942.GC1491@weongyo> In-Reply-To: <20091224220942.GC1491@weongyo> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912250117.00907.freebsd@insightbb.com> Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Dec 2009 06:17:13 -0000 On Thursday 24 December 2009 05:09:42 pm Weongyo Jeong wrote: > OK. It looks weird idProduct didn't be decreased 1 after loading the > firmware. > > And what I'd like to see is the *full* result of the following steps: > > 1. plugs in your USB device. > 2. run commands as follows: > > # kldload if_uath > # dmesg | tail > # uathload -v -d /dev/ugen4.3 > # dmesg | tail > > In a theory, after loading the firmware normally the device which at the > moment idProduct is 0x4251 is detached and reseted then it should be > reattached with idProduct(0x4250). > > regards, > Weongyo Jeong > Opps, I'm sorry, the reply I just sent ws wrong because once you've used uathload, you have to unplugplug the device before you can run it again. So here it is: Load firmware ar5523.bin (builtin) to /dev/ugen4.3 send block 0: 147368 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 1: 145320 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 2: 143272 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 3: 141224 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 4: 139176 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 5: 137128 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 6: 135080 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 7: 133032 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 8: 130984 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 9: 128936 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 10: 126888 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 11: 124840 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 12: 122792 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 13: 120744 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 14: 118696 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 15: 116648 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 16: 114600 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 17: 112552 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 18: 110504 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 19: 108456 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 20: 106408 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 21: 104360 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 22: 102312 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 23: 100264 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 24: 98216 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 25: 96168 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 26: 94120 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 27: 92072 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 28: 90024 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 29: 87976 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 30: 85928 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 31: 83880 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 32: 81832 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 33: 79784 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 34: 77736 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 35: 75688 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 36: 73640 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 37: 71592 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 38: 69544 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 39: 67496 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 40: 65448 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 41: 63400 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 42: 61352 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 43: 59304 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 44: 57256 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 45: 55208 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 46: 53160 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 47: 51112 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 48: 49064 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 49: 47016 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 50: 44968 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 51: 42920 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 52: 40872 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 53: 38824 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 54: 36776 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 55: 34728 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 56: 32680 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 57: 30632 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 58: 28584 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 59: 26536 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 60: 24488 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 61: 22440 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 62: 20392 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 63: 18344 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 64: 16296 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 65: 14248 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 66: 12200 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 67: 10152 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 68: 8104 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 69: 6056 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 70: 4008 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 71: 1960 bytes remaining : data... : wait for ack...flags=0x14 total=149416 send block 72: 0 bytes remaining : data... : wait for ack...flags=0x14 total=149416 From owner-freebsd-net@FreeBSD.ORG Fri Dec 25 13:30:06 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A446E106568B for ; Fri, 25 Dec 2009 13:30:06 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 7A8308FC0A for ; Fri, 25 Dec 2009 13:30:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBPDU60j039910 for ; Fri, 25 Dec 2009 13:30:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBPDU6ks039897; Fri, 25 Dec 2009 13:30:06 GMT (envelope-from gnats) Date: Fri, 25 Dec 2009 13:30:06 GMT Message-Id: <200912251330.nBPDU6ks039897@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: Frank Cc: Subject: Re: kern/121437: [vlan] Routing to layer-2 address does not work on VLAN interface X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Frank List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Dec 2009 13:30:06 -0000 The following reply was made to PR kern/121437; it has been noted by GNATS. From: Frank To: bug-followup@FreeBSD.org, frank@deze.org Cc: Subject: Re: kern/121437: [vlan] Routing to layer-2 address does not work on VLAN interface Date: Fri, 25 Dec 2009 14:21:00 +0100 Just checked, and the bug is still present in FreeBSD 8.x Regards, Frank From owner-freebsd-net@FreeBSD.ORG Fri Dec 25 19:44:13 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80B5C106566B for ; Fri, 25 Dec 2009 19:44:13 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2119F8FC0C for ; Fri, 25 Dec 2009 19:44:12 +0000 (UTC) Received: from ice.local ([10.0.0.115]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id nBPJiCKo024182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Dec 2009 11:44:12 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <4B35160C.3040701@errno.com> Date: Fri, 25 Dec 2009 11:44:12 -0800 From: Sam Leffler User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Steven Friedrich References: <200912151603.32111.freebsd@insightbb.com> <200912221754.25692.freebsd@insightbb.com> <20091224220942.GC1491@weongyo> <200912250117.00907.freebsd@insightbb.com> In-Reply-To: <200912250117.00907.freebsd@insightbb.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC-sonic.net-Metrics: ebb.errno.com; whitelist Cc: freebsd-net@freebsd.org Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Dec 2009 19:44:13 -0000 Steven Friedrich wrote: > On Thursday 24 December 2009 05:09:42 pm Weongyo Jeong wrote: >> OK. It looks weird idProduct didn't be decreased 1 after loading the >> firmware. >> >> And what I'd like to see is the *full* result of the following steps: >> >> 1. plugs in your USB device. >> 2. run commands as follows: >> >> # kldload if_uath >> # dmesg | tail >> # uathload -v -d /dev/ugen4.3 >> # dmesg | tail >> >> In a theory, after loading the firmware normally the device which at the >> moment idProduct is 0x4251 is detached and reseted then it should be >> reattached with idProduct(0x4250). >> >> regards, >> Weongyo Jeong >> > Opps, I'm sorry, the reply I just sent ws wrong because once you've used > uathload, you have to unplugplug the device before you can run it again. > So here it is: > Load firmware ar5523.bin (builtin) to /dev/ugen4.3 > send block 0: 147368 bytes remaining > : data... > : wait for ack...flags=0x14 total=149416 <...snip...> The device should detach and be re-enumerated w/ a different device id that the driver attaches to. Hard to say why it does not. uathload should be automatically run by devd but it appears the devd rules file I did got lost (don't see it in the tree). Sam From owner-freebsd-net@FreeBSD.ORG Fri Dec 25 23:53:24 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F8761065679; Fri, 25 Dec 2009 23:53:24 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 16DE88FC08; Fri, 25 Dec 2009 23:53:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBPNrNZx023731; Fri, 25 Dec 2009 23:53:23 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBPNrNeF023727; Fri, 25 Dec 2009 23:53:23 GMT (envelope-from linimon) Date: Fri, 25 Dec 2009 23:53:23 GMT Message-Id: <200912252353.nBPNrNeF023727@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/142018: [iwi] [patch] Possibly wrong interpretation of beacon->number in if_iwi.c X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Dec 2009 23:53:24 -0000 Old Synopsis: iwi: Possibly wrong interpretation of beacon->number in if_iwi.c New Synopsis: [iwi] [patch] Possibly wrong interpretation of beacon->number in if_iwi.c Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Fri Dec 25 23:52:51 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=142018 From owner-freebsd-net@FreeBSD.ORG Sat Dec 26 04:42:44 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4120A1065676 for ; Sat, 26 Dec 2009 04:42:44 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id E1E4B8FC14 for ; Sat, 26 Dec 2009 04:42:43 +0000 (UTC) Received: by qyk6 with SMTP id 6so3885748qyk.3 for ; Fri, 25 Dec 2009 20:42:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:organization:x-operation-sytem; bh=4ec/k8OD0vaZD9pjUxUz6eRltRFJziWKGWtUOlp0pak=; b=T7p2zzJMCWsGzMg7uM1CiyK7YA4yJqg/OiPI9pl3N0CEqTjCwf4nN4yje7rfDvnJXC T5S7r/y7SU8pKNP3b6GSesNV2fO0nefdw9MPzjiF0Ww0MQ2GJELSq5Q0xpEmhkLUnjSA LSoMC9H2mk8SduqolaHkmqGp0hYfSzR/LPrZQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent:organization:x-operation-sytem; b=dLG4XV0I0iuYuGp3MhwA51v3JqTzAZn7WfmUm70iySBlmL4iFXNYMmlnEqFl4ueYDt GaXxdA0Qwmvrecv+CaBCgc7S7jAp2t/WfRuj6nmKMw7jzZOMz0MLQsGPOvRNFR/NC0Fh KoL8u9+NBM6Tf1yPAzVI4ogCKnCTmr1ON8hSc= Received: by 10.224.35.41 with SMTP id n41mr6530984qad.308.1261802563285; Fri, 25 Dec 2009 20:42:43 -0800 (PST) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id 4sm26459125qwe.45.2009.12.25.20.42.41 (version=SSLv3 cipher=RC4-MD5); Fri, 25 Dec 2009 20:42:42 -0800 (PST) Received: by weongyo (sSMTP sendmail emulation); Fri, 25 Dec 2009 20:42:43 -0800 From: Weongyo Jeong Date: Fri, 25 Dec 2009 20:42:43 -0800 To: Steven Friedrich Message-ID: <20091226044243.GE11506@weongyo> Mail-Followup-To: Steven Friedrich , Sam Leffler , freebsd-net@freebsd.org References: <200912151603.32111.freebsd@insightbb.com> <200912221754.25692.freebsd@insightbb.com> <20091224220942.GC1491@weongyo> <200912250117.00907.freebsd@insightbb.com> <4B35160C.3040701@errno.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B35160C.3040701@errno.com> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: freebsd-net@freebsd.org Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Weongyo Jeong List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 04:42:44 -0000 On Fri, Dec 25, 2009 at 11:44:12AM -0800, Sam Leffler wrote: > Steven Friedrich wrote: > >On Thursday 24 December 2009 05:09:42 pm Weongyo Jeong wrote: > >>OK. It looks weird idProduct didn't be decreased 1 after loading the > >>firmware. > >> > >>And what I'd like to see is the *full* result of the following steps: > >> > >> 1. plugs in your USB device. > >> 2. run commands as follows: > >> > >> # kldload if_uath > >> # dmesg | tail > >> # uathload -v -d /dev/ugen4.3 > >> # dmesg | tail > >> > >>In a theory, after loading the firmware normally the device which at the > >>moment idProduct is 0x4251 is detached and reseted then it should be > >>reattached with idProduct(0x4250). > >> > >>regards, > >>Weongyo Jeong > >> > >Opps, I'm sorry, the reply I just sent ws wrong because once you've used > >uathload, you have to unplugplug the device before you can run it again. > >So here it is: > >Load firmware ar5523.bin (builtin) to /dev/ugen4.3 > >send block 0: 147368 bytes remaining > > : data... > > : wait for ack...flags=0x14 total=149416 > > <...snip...> > > The device should detach and be re-enumerated w/ a different device id > that the driver attaches to. Hard to say why it does not. > > uathload should be automatically run by devd but it appears the devd > rules file I did got lost (don't see it in the tree). I agree with sam@ that it's hard to understand why it's not detached after downloading the firmware. Yesterday I ordered `Netgear Wireless USB Adapter WG111T' which probably is same one with you so I could reproduce your problem and debug it. regards, Weongyo Jeong From owner-freebsd-net@FreeBSD.ORG Sat Dec 26 07:42:32 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96A5B106566C; Sat, 26 Dec 2009 07:42:32 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4DFBE8FC1B; Sat, 26 Dec 2009 07:42:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBQ7gWhE089884; Sat, 26 Dec 2009 07:42:32 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBQ7gWet089880; Sat, 26 Dec 2009 07:42:32 GMT (envelope-from linimon) Date: Sat, 26 Dec 2009 07:42:32 GMT Message-Id: <200912260742.nBQ7gWet089880@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-net@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: kern/142019: [em] em needs "ifconfig em0 down up" when link was gone X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 07:42:32 -0000 Old Synopsis: em needs "ifconfig em0 down up" when link was gone New Synopsis: [em] em needs "ifconfig em0 down up" when link was gone Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Sat Dec 26 07:41:55 UTC 2009 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=142019 From owner-freebsd-net@FreeBSD.ORG Sat Dec 26 14:42:51 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C56ED106566C for ; Sat, 26 Dec 2009 14:42:51 +0000 (UTC) (envelope-from freebsd@insightbb.com) Received: from mxsf00.insightbb.com (mxsf00.insightbb.com [74.128.0.70]) by mx1.freebsd.org (Postfix) with ESMTP id 910FB8FC19 for ; Sat, 26 Dec 2009 14:42:51 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.47,455,1257138000"; d="scan'208";a="728967410" Received: from unknown (HELO asav01.insightbb.com) ([172.31.249.123]) by mxsf00.insightbb.com with ESMTP; 26 Dec 2009 09:42:50 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ar8EAAmwNUvQLicL/2dsb2JhbACBStEZhDMEgWWEAw X-IronPort-AV: E=Sophos;i="4.47,455,1257138000"; d="scan'208";a="239357112" Received: from 208-46-39-11.dia.static.qwest.net (HELO laptop2.stevenfriedrich.org) ([208.46.39.11]) by asavout01.insightbb.com with ESMTP; 26 Dec 2009 09:42:50 -0500 From: Steven Friedrich To: Sam Leffler , freebsd-net@freebsd.org Date: Sat, 26 Dec 2009 09:42:48 -0500 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.4; i386; ; ) References: <200912151603.32111.freebsd@insightbb.com> <4B35160C.3040701@errno.com> <20091226044243.GE11506@weongyo> In-Reply-To: <20091226044243.GE11506@weongyo> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912260942.48320.freebsd@insightbb.com> Cc: Subject: Re: uath under FreeBSD 8.0-STABLE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 14:42:51 -0000 On Friday 25 December 2009 11:42:43 pm Weongyo Jeong wrote: > On Fri, Dec 25, 2009 at 11:44:12AM -0800, Sam Leffler wrote: > > Steven Friedrich wrote: > > >On Thursday 24 December 2009 05:09:42 pm Weongyo Jeong wrote: > > >>OK. It looks weird idProduct didn't be decreased 1 after loading the > > >>firmware. > > >> > > >>And what I'd like to see is the *full* result of the following steps: > > >> > > >> 1. plugs in your USB device. > > >> 2. run commands as follows: > > >> > > >> # kldload if_uath > > >> # dmesg | tail > > >> # uathload -v -d /dev/ugen4.3 > > >> # dmesg | tail > > >> > > >>In a theory, after loading the firmware normally the device which at > > >> the moment idProduct is 0x4251 is detached and reseted then it should > > >> be reattached with idProduct(0x4250). > > >> > > >>regards, > > >>Weongyo Jeong > > > > > >Opps, I'm sorry, the reply I just sent ws wrong because once you've used > > >uathload, you have to unplugplug the device before you can run it again. > > >So here it is: > > >Load firmware ar5523.bin (builtin) to /dev/ugen4.3 > > >send block 0: 147368 bytes remaining > > > > > > : data... > > > : wait for ack...flags=0x14 total=149416 > > > > <...snip...> > > > > The device should detach and be re-enumerated w/ a different device id > > that the driver attaches to. Hard to say why it does not. > > > > uathload should be automatically run by devd but it appears the devd > > rules file I did got lost (don't see it in the tree). > > I agree with sam@ that it's hard to understand why it's not detached > after downloading the firmware. > > Yesterday I ordered `Netgear Wireless USB Adapter WG111T' which probably > is same one with you so I could reproduce your problem and debug it. > > regards, > Weongyo Jeong > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > Thanks for your effort. I appreciate it. From owner-freebsd-net@FreeBSD.ORG Sat Dec 26 18:30:05 2009 Return-Path: Delivered-To: freebsd-net@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A03B10656BE for ; Sat, 26 Dec 2009 18:30:05 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0FCF08FC21 for ; Sat, 26 Dec 2009 18:30:05 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id nBQIU4Yl035078 for ; Sat, 26 Dec 2009 18:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id nBQIU4D6035075; Sat, 26 Dec 2009 18:30:04 GMT (envelope-from gnats) Date: Sat, 26 Dec 2009 18:30:04 GMT Message-Id: <200912261830.nBQIU4D6035075@freefall.freebsd.org> To: freebsd-net@FreeBSD.org From: dfilter@FreeBSD.ORG (dfilter service) Cc: Subject: Re: kern/141376: commit references a PR X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dfilter service List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 18:30:05 -0000 The following reply was made to PR kern/141376; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: kern/141376: commit references a PR Date: Sat, 26 Dec 2009 18:26:07 +0000 (UTC) Author: rpaulo Date: Sat Dec 26 18:25:52 2009 New Revision: 201026 URL: http://svn.freebsd.org/changeset/base/201026 Log: MFC r200524: Pass all IEs to net80211. PR: 141376 Submitted by: Paul Modified: stable/8/sys/dev/if_ndis/if_ndis.c Directory Properties: stable/8/sys/ (props changed) stable/8/sys/amd64/include/xen/ (props changed) stable/8/sys/cddl/contrib/opensolaris/ (props changed) stable/8/sys/contrib/dev/acpica/ (props changed) stable/8/sys/contrib/pf/ (props changed) stable/8/sys/dev/xen/xenpci/ (props changed) Modified: stable/8/sys/dev/if_ndis/if_ndis.c ============================================================================== --- stable/8/sys/dev/if_ndis/if_ndis.c Sat Dec 26 18:23:21 2009 (r201025) +++ stable/8/sys/dev/if_ndis/if_ndis.c Sat Dec 26 18:25:52 2009 (r201026) @@ -3355,24 +3355,11 @@ ndis_scan_results(struct ndis_softc *sc) efrm = frm + wb->nwbx_ielen; if (efrm - frm < 12) goto done; - sp.tstamp = frm; - frm += 8; - sp.bintval = le16toh(*(uint16_t *)frm); - frm += 2; - sp.capinfo = le16toh(*(uint16_t *)frm); - frm += 2; - - /* Grab variable length ies */ - while (efrm - frm > 1) { - if (efrm - frm < frm[1] + 2) - break; - switch (*frm) { - case IEEE80211_ELEMID_RSN: - sp.rsn = frm; - break; - } - frm += frm[1] + 2; - } + sp.tstamp = frm; frm += 8; + sp.bintval = le16toh(*(uint16_t *)frm); frm += 2; + sp.capinfo = le16toh(*(uint16_t *)frm); frm += 2; + sp.ies = frm; + sp.ies_len = efrm - frm; } done: DPRINTF(("scan: bssid %s chan %dMHz (%d/%d) rssi %d\n", _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscribe@freebsd.org" From owner-freebsd-net@FreeBSD.ORG Sat Dec 26 21:56:22 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5664106568D for ; Sat, 26 Dec 2009 21:56:22 +0000 (UTC) (envelope-from hyama99@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 6BD3B8FC16 for ; Sat, 26 Dec 2009 21:56:22 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 9so1134395eyd.3 for ; Sat, 26 Dec 2009 13:56:21 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.89.18 with SMTP id b18mr4737098wef.14.1261863208046; Sat, 26 Dec 2009 13:33:28 -0800 (PST) Date: Sun, 27 Dec 2009 06:33:28 +0900 Message-ID: <90dbee150912261333l602c4161nccaf1995dc83699a@mail.gmail.com> From: Hideki Yamamoto To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: GIF MTU parmeter is needed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 21:56:22 -0000 Hi, I often use FreeBSD for developing the gateway. For example, I use gif for the tunnel protocol when using IPv6 over IPv4 and use an application for changing packet address for special purpose. When we were using old FreeBSD, such as FreeBSD 4.11, the MTU of the tunnel packets or forwarded packets was not limited into 1280. However, FreeBSD 6,7, and 8 fragments packets by 1280 when using tunnel. I know that this behavior is based on the RFC specification. However it is not useful when using AV application that use around 1400B RTP packet. AV packets will be fragmented into long packets (1280) and short packets (1400-1280) when using tunnel, and short packet will sometimes be lost by network. I hope new parameter by sysctl to control MTU of tunnel will be implemented. The following is an example of new paramter to control MTU size. net.inet6.use_mmtu :1 --- is the same as current versions, it means minimum MTU 1280 will be used when gateway node. :0--- is the same as the old versions. It means OS uses as long MTU size as possible ( I hope "1" will be default) Are there any comment on this matter? Best regards, Hideki Yamamoto From owner-freebsd-net@FreeBSD.ORG Sat Dec 26 22:25:45 2009 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2EAC81065672 for ; Sat, 26 Dec 2009 22:25:45 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper-int.allbsd.org [IPv6:2001:2f0:104:e002::2]) by mx1.freebsd.org (Postfix) with ESMTP id A88238FC0C for ; Sat, 26 Dec 2009 22:25:44 +0000 (UTC) Received: from delta.allbsd.org (p3177-ipbf416funabasi.chiba.ocn.ne.jp [123.225.92.177]) (authenticated bits=128) by mail.allbsd.org (8.14.3/8.14.3) with ESMTP id nBQMPKVZ019859; Sun, 27 Dec 2009 07:25:31 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id nBQMPEFf087772; Sun, 27 Dec 2009 07:25:18 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sun, 27 Dec 2009 07:24:23 +0900 (JST) Message-Id: <20091227.072423.122179742.hrs@allbsd.org> To: hyama99@gmail.com From: Hiroki Sato In-Reply-To: <90dbee150912261333l602c4161nccaf1995dc83699a@mail.gmail.com> References: <90dbee150912261333l602c4161nccaf1995dc83699a@mail.gmail.com> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Sun_Dec_27_07_24_23_2009_387)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.95.3 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.allbsd.org [133.31.130.32]); Sun, 27 Dec 2009 07:25:37 +0900 (JST) X-Spam-Status: No, score=-5.7 required=13.0 tests=AWL,BAYES_00, CONTENT_TYPE_PRESENT, SPF_SOFTFAIL, X_MAILER_PRESENT autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gatekeeper.allbsd.org Cc: freebsd-net@FreeBSD.org Subject: Re: GIF MTU parmeter is needed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 22:25:45 -0000 ----Security_Multipart(Sun_Dec_27_07_24_23_2009_387)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hideki Yamamoto wrote in <90dbee150912261333l602c4161nccaf1995dc83699a@mail.gmail.com>: hy> Hi, hy> hy> I often use FreeBSD for developing the gateway. For example, I use gif for the hy> tunnel protocol when using IPv6 over IPv4 and use an application for changing hy> packet address for special purpose. When we were using old FreeBSD, such as hy> FreeBSD 4.11, the MTU of the tunnel packets or forwarded packets hy> was not limited into 1280. However, FreeBSD 6,7, and 8 fragments packets hy> by 1280 when using tunnel. The gif(4) interface supports MTU up to 8192 and this has not been changed since FreeBSD 4.X IIRC. Why did you think FreeBSD 6 and later supported a fixed MTU only? -- Hiroki ----Security_Multipart(Sun_Dec_27_07_24_23_2009_387)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAks2jRcACgkQTyzT2CeTzy3OyQCdFJ5YPPUdhkW+IXAAuYL3/vAE y9YAnApCHddlfzQ5n4QtiAeamjXdbYAe =CBEv -----END PGP SIGNATURE----- ----Security_Multipart(Sun_Dec_27_07_24_23_2009_387)---- From owner-freebsd-net@FreeBSD.ORG Sat Dec 26 22:45:20 2009 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B28461065698 for ; Sat, 26 Dec 2009 22:45:20 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outO.internet-mail-service.net (outo.internet-mail-service.net [216.240.47.238]) by mx1.freebsd.org (Postfix) with ESMTP id 9AB098FC0C for ; Sat, 26 Dec 2009 22:45:20 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 48651A1EA7; Sat, 26 Dec 2009 14:45:20 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id BFA492D6013; Sat, 26 Dec 2009 14:45:19 -0800 (PST) Message-ID: <4B3691FF.3050402@elischer.org> Date: Sat, 26 Dec 2009 14:45:19 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Hideki Yamamoto References: <90dbee150912261333l602c4161nccaf1995dc83699a@mail.gmail.com> In-Reply-To: <90dbee150912261333l602c4161nccaf1995dc83699a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org Subject: Re: GIF MTU parmeter is needed X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Dec 2009 22:45:20 -0000 Hideki Yamamoto wrote: > Hi, > > I often use FreeBSD for developing the gateway. For example, I use gif for the > tunnel protocol when using IPv6 over IPv4 and use an application for changing > packet address for special purpose. When we were using old FreeBSD, such as > FreeBSD 4.11, the MTU of the tunnel packets or forwarded packets > was not limited into 1280. However, FreeBSD 6,7, and 8 fragments packets > by 1280 when using tunnel. ?? huh? it is defined by the MTU of the gif interface as set with ifconfig > > I know that this behavior is based on the RFC specification. However > it is not useful when using AV application that use around 1400B RTP packet. > AV packets will be fragmented into long packets (1280) and short > packets (1400-1280) > when using tunnel, and short packet will sometimes be lost by network. > > I hope new parameter by sysctl to control MTU of tunnel will be implemented. > The following is an example of new paramter to control MTU size. > > net.inet6.use_mmtu :1 --- is the same as current versions, it means > minimum MTU 1280 > will be used when gateway node. > :0--- is the same as the > old versions. It means > OS uses > as long MTU size as possible > ( I hope "1" will be default) > > Are there any comment on this matter? > > Best regards, > > Hideki Yamamoto > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"