From owner-freebsd-current@FreeBSD.ORG  Wed May 13 08:46:04 2009
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 00B95106566C;
	Wed, 13 May 2009 08:46:04 +0000 (UTC)
	(envelope-from hselasky@c2i.net)
Received: from swip.net (mailfe05.swip.net [212.247.154.129])
	by mx1.freebsd.org (Postfix) with ESMTP id 62D728FC0C;
	Wed, 13 May 2009 08:46:03 +0000 (UTC)
	(envelope-from hselasky@c2i.net)
X-Cloudmark-Score: 0.000000 []
X-Cloudmark-Analysis: v=1.0 c=1 a=pVrlnhvF3Yt6WR3_Qg0A:9
	a=6v_5w3m9QANlnE7YPMJ8EEFYRgIA:4
Received: from [81.191.55.181] (account mc467741@c2i.net HELO [10.36.2.183])
	by mailfe05.swip.net (CommuniGate Pro SMTP 5.2.13)
	with ESMTPA id 1139060176; Wed, 13 May 2009 10:46:02 +0200
From: Hans Petter Selasky <hselasky@c2i.net>
To: Thomas Sparrevohn <Thomas.Sparrevohn@btinternet.com>,
	Sevan / Venture37 <venture37@gmail.com>,
	Andrew Thompson <thompsa@freebsd.org>, freebsd-current@freebsd.org
Date: Wed, 13 May 2009 10:48:36 +0200
User-Agent: KMail/1.9.7
References: <200905130922.52887.Thomas.Sparrevohn@btinternet.com>
In-Reply-To: <200905130922.52887.Thomas.Sparrevohn@btinternet.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200905131048.37146.hselasky@c2i.net>
Cc: 
Subject: Re: rum(4) not working on 8-CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 May 2009 08:46:04 -0000

On Wednesday 13 May 2009, Thomas Sparrevohn wrote:
> Hans Petter
>
> I don't see this one came through - but I am having real pains with rum(4)
> - the weird thing it that it seems to work with HTTP etc but not with fetch
> - no panics - it just drops all connections and routing information - It am
> still getting the "kernel: rum0: need multicast update callback" error but
> I cannot see that it has anything to do with the issue

In my experience it's not the driver that is flaky, but the firmware in the 
hardware. I've seen several times that if certain commands are intermixed, 
the firmware will completely stop responding.

Has the rum driver ever worked with USB2 and -current? Recently there has been 
several changes in the WLAN layer and some minor changes in if_rum.

--HPS