Date: Fri, 1 Apr 2011 07:40:14 GMT From: Ruan Chunping <rcp@mipang.com> To: freebsd-usb@FreeBSD.org Subject: Re: usb/156000: rum(4) Fatal trap 18: integer divide fault while in kernel mode Message-ID: <201104010740.p317eEqm011484@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR usb/156000; it has been noted by GNATS. From: Ruan Chunping <rcp@mipang.com> To: PseudoCylon <moonlightakkiy@yahoo.ca> 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 15:31:29 +0800 Thanks for your suggestion I will do more test. On Fri, Apr 1, 2011 at 15:14, PseudoCylon <moonlightakkiy@yahoo.ca> wrote: > > >From: Ruan Chunping <rcp@mipang.com> > >To: PseudoCylon <moonlightakkiy@yahoo.ca> > >Cc: bug-followup@freebsd.org; Hans Petter Selasky <hselasky@c2i.net> > >Sent: Tue, March 29, 2011 7:42:54 AM > >Subject: Re: usb/156000: rum(4) Fatal trap 18: integer divide fault whil= e 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 be= having > 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 work= s. > There is nothing wrong from driver's point of view. > > It seems routing table hasn't properly been configured, so arp reply pack= ets 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 menti= oned in > previous thread. That's what bridge is for. > > >bridge0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 m= tu 1500 > > =C2=A0 =C2=A0 =C2=A0 =C2=A0ether 72:5f:7d:8a:55:34 > > =C2=A0 =C2=A0 =C2=A0 =C2=A0inet 192.168.77.1 netmask 0xffffff00 broadca= st 192.168.77.255 > > =C2=A0 =C2=A0 =C2=A0 =C2=A0id 00:00:00:00:00:00 priority 32768 hellotim= e 2 fwddelay 15 > > =C2=A0 =C2=A0 =C2=A0 =C2=A0maxage 20 holdcnt 6 proto rstp maxaddr 100 t= imeout 1200 > > =C2=A0 =C2=A0 =C2=A0 =C2=A0root id 00:00:00:00:00:00 priority 32768 ifc= ost 0 port 0 > > =C2=A0 =C2=A0 =C2=A0 =C2=A0member: wlan0 flags=3D143<LEARNING,DISCOVER,= AUTOEDGE,AUTOPTP> > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0ifmaxaddr 0 port= 10 priority 128 path cost 370370 > >>> =C2=A0 member: em0 ..... << you need this > > > AK >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201104010740.p317eEqm011484>