headsup on enclosure driver

[John]

----- Gyrd Thane Lange's Original Message -----
> On Sat, 11 Aug 2012 08:15:57 -0700
> Matthew Jacob <mj at feral.com> wrote:
> 
> > On 8/10/2012 1:44 PM, Bruce Cran wrote:
> > > On Friday 15 June 2012 18:21:10 Matthew Jacob wrote:
> > >> 2) Default logging via enc_log to not be chatty unless a new sysctl
> > >> enc_verbose or bootverbose is set.
> > >> This is all motivated by my hudson case system's log that is
> > >> filled full of charm like:
> > > Did you get around to committing this? I got a WD "My Passport"
> > > drive today and (not terribly surprisingly) its enclosure seems a
> > > bit broken - ses (on 10- CURRENT from late July) is spamming the
> > > logs:
> > >
> > > Aug 10 14:19:01 router kernel: ses1 at umass-sim0 bus 0 scbus8
> > > target 0 lun 1 Aug 10 14:19:01 router kernel: ses1: <WD SES Device
> > > 1010> Fixed Enclosure Services SCSI-6 device
> > > Aug 10 14:19:01 router kernel: ses1: 40.000MB/s transfers
> > > Aug 10 14:19:01 router kernel: ses1: SCSI-3 ENC Device
> > > Aug 10 14:19:01 router kernel: ses1: Enclosure Status Page Too Short
> > > Aug 10 14:19:44 router su: brucec to root on /dev/pts/0
> > > Aug 10 14:20:01 router kernel: ses1: Enclosure Status Page Too Short
> > > Aug 10 14:21:01 router kernel: ses1: Enclosure Status Page Too Short
> > > Aug 10 14:23:01 router last message repeated 2 times
> > > Aug 10 14:33:01 router last message repeated 10 times
> > > Aug 10 14:43:01 router last message repeated 10 times
> > >
> > No, I didn't get around to it. I probably should.
> 
> I'm experiencing the same with some WD "My Book"s, so I too will
> appreciate some way of dampening these messages. :-)

   Reducing these msgs is straight forward. However, is their implementation
incorrect, or are they returning a format the driver doesn't understand?

   Thoughts?

Cheers!
John