From owner-freebsd-bugs@FreeBSD.ORG Thu Aug 9 08:30:12 2007 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A719416A41B for ; Thu, 9 Aug 2007 08:30:12 +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 71F3913C468 for ; Thu, 9 Aug 2007 08:30:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.1/8.14.1) with ESMTP id l798UCdP070930 for ; Thu, 9 Aug 2007 08:30:12 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.1/8.14.1/Submit) id l798UCGa070926; Thu, 9 Aug 2007 08:30:12 GMT (envelope-from gnats) Date: Thu, 9 Aug 2007 08:30:12 GMT Message-Id: <200708090830.l798UCGa070926@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: David Southwell Cc: Subject: Re: kern/114667: [umass] UMASS device error log problem X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Southwell List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Aug 2007 08:30:12 -0000 The following reply was made to PR kern/114667; it has been noted by GNATS. From: David Southwell To: bug-followup@freebsd.org, david@vizion2000.net Cc: Subject: Re: kern/114667: [umass] UMASS device error log problem Date: Thu, 9 Aug 2007 01:41:09 -0700 Re: kern/114667: [umass] UMASS device error log problem From: David Southwell To: "M. Warner Losh" CC: remko@elvandar.org, usb@freebsd.org, freebsd-bugs@freebsd.org =20 On Wednesday 08 August 2007 15:17:06 M. Warner Losh wrote: > In message: <200708081502.14940.david@vizion2000.net> > > =A0 =A0 =A0 =A0 =A0 =A0 David Southwell writes: > : On Wednesday 08 August 2007 10:54:14 Remko Lodder wrote: > : > On Wed, Aug 08, 2007 at 04:20:06PM +0000, David Southwell wrote: > : > > The following reply was made to PR kern/114667; it has been noted by > : > > GNATS. > : > > > : > > From: David Southwell > : > > To: bug-followup@freebsd.org, > : > > =A0david@vizion2000.net > : > > Cc: > : > > Subject: Re: kern/114667: [umass] UMASS device error log problem > : > > Date: Wed, 8 Aug 2007 09:27:59 -0700 > : > > > : > > =A0Hi > : > > > : > > =A0Just wondered if anyone might have the time to look at this -- it > : > > really is a nuisance. > : > > > : > > =A0Thanks > : > > : > Hello David, > : > > : > I just checked the PR itself and I personally do not think this is > : > something we should handle though, the messages get in the logfile > : > because you ask for information on a 'heavily removable' device, it > : > mostly has multiple ports and the device has no knowledge to see what > : > 'port' is being used [if at all used]. > : > > : > That said; this is my private opinion, others might ofcourse disagree > : > with me, please feel free to continue to discuss this, but in additti= on > : > I also think this is not worth a PR ticket. > : > > : > Cheers > : > remko > : > : Sorry but I and a number of others who have complained about the same > : problem do agree it is worth a PR. basically we seem to have an > : uncontrollable worthless message generator. > : > : If you can tell me how to stop the messages for this device it would ma= ke > : a PR unnecessary but as things stand none seems to be able to answer the > : question "How do we stop the messages?" > > The messages are from CAM. =A0It likes to get extremely verbose when it > can't do something. =A0There's currently no way to 'fix' this short of > hacking the source. > > Warner That is precisely why I have put in a PR. CAM is pretty ancient and IMHO it= is=20 time it was revisited to get rid of this tiresome behaviour. Unfortunatley = I=20 do not have the capability to do it myself. In this case "hacking the sourc= e"=20 iand "bug fixing" are synonyms. It needs fixing - and therefore a PR is IMHO =A0most appropriate. David