From owner-freebsd-usb@FreeBSD.ORG Fri Apr 1 07:20:13 2011 Return-Path: Delivered-To: freebsd-usb@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4E655106564A for ; Fri, 1 Apr 2011 07:20:13 +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 3C7F98FC12 for ; Fri, 1 Apr 2011 07:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p317KDaS073017 for ; Fri, 1 Apr 2011 07:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p317KDvY073016; Fri, 1 Apr 2011 07:20:13 GMT (envelope-from gnats) Date: Fri, 1 Apr 2011 07:20:13 GMT Message-Id: <201104010720.p317KDvY073016@freefall.freebsd.org> To: freebsd-usb@FreeBSD.org From: PseudoCylon Cc: Subject: Re: usb/156000: rum(4) Fatal trap 18: integer divide fault while in kernel mode X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: PseudoCylon List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Apr 2011 07:20:13 -0000 The following reply was made to PR usb/156000; it has been noted by GNATS. From: PseudoCylon To: Ruan Chunping Cc: bug-followup@freebsd.org Subject: Re: usb/156000: rum(4) Fatal trap 18: integer divide fault while in kernel mode Date: Fri, 1 Apr 2011 00:14:27 -0700 (PDT) >From: Ruan Chunping >To: PseudoCylon >Cc: bug-followup@freebsd.org; Hans Petter Selasky >Sent: Tue, March 29, 2011 7:42:54 AM >Subject: Re: usb/156000: rum(4) Fatal trap 18: integer divide fault while in >kernel mode > >Thanks a lot! > > >Maybe rum(4) has anthor ARP-Reply problem too. > No. The driver shouldn't panic just because it's received an odd packet, and need to be fixed. Other than that, based on your tcpdump output, the driver is behaving fine. When the driver is not receiving any arp packet, it isn't sending any, so android phone doesn't work. No driver sends out a packet spontaneously. When the driver receives an arp packet, it sends out, so nokia phone works. There is nothing wrong from driver's point of view. It seems routing table hasn't properly been configured, so arp reply packets are sent to default gateway (most likely to em0). Once the routing table is set up, every thing should work fine. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-routing.html You can set up an AP without bridge. Since you are making subnet, rather not to. But, if you need to use bridge, you need to add 2 or more NICs as I mentioned in previous thread. That's what bridge is for. >bridge0: flags=8843 metric 0 mtu 1500 > ether 72:5f:7d:8a:55:34 > inet 192.168.77.1 netmask 0xffffff00 broadcast 192.168.77.255 > id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 > maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 > root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 > member: wlan0 flags=143 > ifmaxaddr 0 port 10 priority 128 path cost 370370 >>> member: em0 ..... << you need this AK