From nobody@FreeBSD.org  Tue Jul 17 17:19:19 2007
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id C9C4916A402
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 17 Jul 2007 17:19:19 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (groups.freebsd.org [69.147.83.33])
	by mx1.freebsd.org (Postfix) with ESMTP id A2B2D13C4AA
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 17 Jul 2007 17:19:19 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.1/8.14.1) with ESMTP id l6HHJJpQ050574
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 17 Jul 2007 17:19:19 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.1/8.14.1/Submit) id l6HHJJSm050573;
	Tue, 17 Jul 2007 17:19:19 GMT
	(envelope-from nobody)
Message-Id: <200707171719.l6HHJJSm050573@www.freebsd.org>
Date: Tue, 17 Jul 2007 17:19:19 GMT
From: David Southwell <david@vizion2000.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: UMASS device error log problem
X-Send-Pr-Version: www-3.0

>Number:         114667
>Category:       kern
>Synopsis:       [umass] UMASS device error log problem
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jul 17 17:20:02 GMT 2007
>Closed-Date:    Tue Nov 13 20:51:53 UTC 2012
>Last-Modified:  Tue Nov 13 20:51:53 UTC 2012
>Originator:     David Southwell
>Release:        6.1
>Organization:
Voice & Vision
>Environment:
6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May  7 04:15:57 UTC 2006     root@bloom.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP  amd64

>Description:
Hi

I originally posted the report below in April to freebsd questions but
so far noone has reported a fix.

The umass device provides repeated message there is no card present and
there seems no way to stop them apart from ensuring there is a card always
present.

This problem clogs the logs files and provides an unnecessary load. A fix
would be appreciated.

Thanks in advance

David Southwell



[root@dns1 /var/run]# camcontrol devlist
<USB2.0 CF CardReader >      at scbus0 target 0 lun 0 (pass0,da0)
<USB2.0 CBO CardReader >      at scbus0 target 0 lun 1 (pass1,da1)
-----------------------------------------------------------
From /var/log/messages:
Apr 18 03:27:03 dns1 kernel: Opened disk da1 -> 6
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 
0 0 0 0 0 0 0 0 
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status 
Error
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check 
Condition
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): Medium not present
Apr 18 03:27:05 dns1 kernel: (da0:umass-sim0:0:0:0): Unretryable error
Apr 18 03:27:05 dns1 kernel: Opened disk da0 -> 6
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 
0 0 0 0 0 0 0 0 
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): CAM Status: SCSI Status 
Error
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): SCSI Status: Check 
Condition
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): NOT READY asc:3a,0
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): Medium not present
Apr 18 03:27:05 dns1 kernel: (da1:umass-sim0:0:0:1): Unretryable error
Apr 18 03:27:05 dns1 kernel: Opened disk da1 -> 6
>How-To-Repeat:
The problem repeats automattically!!!!
>Fix:


>Release-Note:
>Audit-Trail:

From: David Southwell <david@vizion2000.net>
To: bug-followup@freebsd.org,
 david@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

From: David Southwell <david@vizion2000.net>
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 <david@vizion2000.net>
  To: "M. Warner Losh" <imp@bsdimp.com>
  CC: remko@elvandar.org, usb@freebsd.org, freebsd-bugs@freebsd.org
  
 On Wednesday 08 August 2007 15:17:06 M. Warner Losh wrote:
 > In message: <200708081502.14940.david@vizion2000.net>
 >
 > David Southwell <david@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@vizion2000.net>
 > : > > To: bug-followup@freebsd.org,
 > : > >  david@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 addition
 > : > 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
 
 That is precisely why I have put in a PR. CAM is pretty ancient and IMHO it is 
 time it was revisited to get rid of this tiresome behaviour. Unfortunately I 
 do not have the capability to do it myself. In this case "hacking the source" 
 and "bug fixing" are synonyms.
 
 It needs fixing - and therefore a PR is IMHO  most appropriate.
 
 David
State-Changed-From-To: open->feedback 
State-Changed-By: jh 
State-Changed-When: Fri Nov 11 19:38:38 UTC 2011 
State-Changed-Why:  
Note that submitter has been asked for feedback. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=114667 
State-Changed-From-To: feedback->open 
State-Changed-By: jh 
State-Changed-When: Thu Jul 12 08:24:33 UTC 2012 
State-Changed-Why:  
Back to open. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=114667 
State-Changed-From-To: open->feedback 
State-Changed-By: jh 
State-Changed-When: Thu Jul 12 08:25:01 UTC 2012 
State-Changed-Why:  
Is this still a problem on recent FreeBSD versions? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=114667 
State-Changed-From-To: feedback->closed 
State-Changed-By: eadler 
State-Changed-When: Tue Nov 13 20:51:52 UTC 2012 
State-Changed-Why:  
Feedback timeout. Please email me and I will reopen if needed. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=114667 
>Unformatted:
