kern/114667: [umass] UMASS device error log problem

[M. Warner Losh]

In message: <200708081502.14940.david at vizion2000.net>
            David Southwell <david at vizion2000.net> 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 <david at vizion2000.net>
: > > To: bug-followup at freebsd.org,
: > >  david at vizion2000.net
: > > Cc:
: > > Subject: Re: kern/114667: [umass] UMASS device error log problem
: > > Date: Wed, 8 Aug 2007 09:27:59 -0700
: > >
: > >  Hi
: > >
: > >  Just wondered if anyone might have the time to look at this -- it really
: > > is a nuisance.
: > >
: > >  Thanks
: >
: > 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 addittion 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 make 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.  It likes to get extremely verbose when it
can't do something.  There's currently no way to 'fix' this short of
hacking the source.

Warner