Re: CAM verbosity (xpt_release_devq(0): requested 1 > present 0)

Marcel Moolenaar wrote:
> On Feb 2, 2010, at 2:05 PM, Alexander Motin wrote:
>> Marcel Moolenaar wrote:
>>> On recent -CURRENT the console gets spammed with the following:
>>>
>>> xpt_release_devq(0): requested 1 > present 0
>>>
>>> Can we put this under bootverbose?
>> It was already put under INVARIANTS.
> 
> Which is what developers run by default :-)

And on strange coincidence, it is developers who are fixing bugs. :)

>>> Do we need to print this at all?
>> It was hidden before, but we need to fix this, if we want error handling
>> to work correctly.
>>
>> Can you somehow localize situations when those messages appear? What
>> controller and devices do you use?
> 
> SCSI controller is:
> mpt0: <LSILogic SAS/SATA Adapter> mem 0xa0470000-0xa0473fff,0xa0460000-0xa046ffff irq 27 at device 1.0 on pci1
> mpt0: [ITHREAD]
> mpt0: MPI Version=1.5.13.0
> mpt0: Capabilities: ( RAID-0 RAID-1E RAID-1 )
> mpt0: 0 Active Volumes (2 Max)
> mpt0: 0 Hidden Drive Members (10 Max)
> 
> Harddisk is:
> da0: <HP DG146ABAB4 HPDA> Fixed Direct Access SCSI-5 device 
> da0: 300.000MB/s transfers
> da0: Command Queueing enabled
> da0: 140014MB (286749488 512 byte sectors: 255H 63S/T 17849C)
> 
> This disk has tagged queuing enabled but the disk only has 122
> openings. When busy the number of openings can reduce to 121.
> Due to bugs in the CAM layer the number of openings never gets
> adjusted when MPT inform CAM about it a Queue Full Event.
> 
> I suspect this is related to it, but may be wrong...

Whether it is related or not, both issues definitely should be fixed.
Could you give me an access to debug that system, or it is in use?

-- 
Alexander Motin