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

2007-08-08 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]>
David Southwell <[EMAIL PROTECTED]> writes:
: On Wednesday 08 August 2007 10:54:14 Remko Lodder wrote:
: > On Wed, Aug 08, 2007 at 04:20:06PM +, David Southwell wrote:
: > > The following reply was made to PR kern/114667; it has been noted by
: > > GNATS.
: > >
: > > From: David Southwell <[EMAIL PROTECTED]>
: > > To: [EMAIL PROTECTED],
: > >  [EMAIL PROTECTED]
: > > 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
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


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

2007-08-08 Thread David Southwell
On Wednesday 08 August 2007 10:54:14 Remko Lodder wrote:
> On Wed, Aug 08, 2007 at 04:20:06PM +, David Southwell wrote:
> > The following reply was made to PR kern/114667; it has been noted by
> > GNATS.
> >
> > From: David Southwell <[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED],
> >  [EMAIL PROTECTED]
> > 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?"

David




___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


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

2007-08-08 Thread Remko Lodder
On Wed, Aug 08, 2007 at 04:20:06PM +, David Southwell wrote:
> The following reply was made to PR kern/114667; it has been noted by GNATS.
> 
> From: David Southwell <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED],
>  [EMAIL PROTECTED]
> 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

-- 
Kind regards,

 Remko Lodder   ** [EMAIL PROTECTED]
 FreeBSD** [EMAIL PROTECTED]

 /* Quis custodiet ipsos custodes */
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


usb/115298: Turning off USB printer panics kernel

2007-08-08 Thread Jonathan Hanna

>Number: 115298
>Category:   usb
>Synopsis:   Turning off USB printer panics kernel
>Confidential:   no
>Severity:   serious
>Priority:   low
>Responsible:freebsd-usb
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Aug 08 08:20:01 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator: Jonathan Hanna
>Release:FreeBSD 7.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD gbh.pangolin-systems.com 7.0-CURRENT FreeBSD 7.0-CURRENT #16: 
Wed Aug 1 18:50:29 PDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GBH i386

>Description:

When a USB printer was turned off, perhaps while lpd was printing
to it, the kernel paniced with:

ulpt0: at uhub1 port 7 (addr 6) disconnected
ulpt0: detached
panic: Bad tailq NEXT(0xd5924db8->tqh_last) != NULL
cpuid = 0
KDB: enter: panic
[thread pid 13 tid 11 ]
Stopped at  kdb_enter+0x32: leave
db> bt
Tracing pid 13 tid 11 td 0xc5915e00
kdb_enter(c0a910d8,0,c0a47d72,e016fc48,0,..) at kdb_enter+0x32
panic(c0a47d72,d5924db8,c0a92274,1ac,c5908c00,...) at panic+0x124
callout_reset(c0b78f28,a,c0558f70,c5908c00,...) at callout_reset+0x169
dcons_timeout(c5908c00,0,c0a92274,f8,0,...) at dcons_timeout+0x81
softcock(0,0,c0a8dd07,471,c59543e4,...) at softclock+0x299
ithread_loop(c5913400,e016fd38,c0a8da7b,315,c59142ac,...) at ithread_loop+0x1b5
fork_exit(c072f5d0,c5913400,e016fd38) at fork_exit+0xb8
fork_trampoline() at fork_trampoline+0x8
--- trap 0, eip = 0, esp = 0xe016fd70, ebp = 0 ---
db>

>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-usb@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "[EMAIL PROTECTED]"