Re: msk(4) stops working.

On Wed, Dec 24, 2008 at 12:43:56PM +0200, Ian FREISLICH wrote:
 > Pyun YongHyeon wrote:
 > > 
 > > On Wed, Dec 24, 2008 at 08:54:26AM +0200, Ian FREISLICH wrote:
 > >  > "Sam Fourman Jr." wrote:
 > >  > > >> About 2-3 months ago I committed workaround for Yukon silicon bug.
 > >  > > >> Do you use latest CURRENT?
 > >  > > >
 > >  > > > Yes, this is on yesterday's sources.  It was better for a month or
 > >  > > > so, but over the last month it's been really bad.  Now I can provoke
 > >  > > > this condition in under 1 minute of uptime.
 > >  > > >
 > >  > > I have a few msk cards, and I could stand to install -CURRENT on a syste
 > m
 > >  > > how do I reproduce your problem?
 > >  > 
 > >  > I induce it by scp-ing a large (several GB) file from one host to
 > >  > another.  I only have one interface msk interface in my laptop, but
 > >  > it's an SMP system.  Maybe that has something to do with it.
 > >  > 
 > > 
 > > Would you show me the output of "sysctl dev.msk.0.stats" before and
 > > after the watchdog timeouts after appling attached patch?
 > 
 > Before:
 > dev.msk.0.stats.rx.ucast_frames: 0
 > dev.msk.0.stats.rx.bcast_frames: 4
 > dev.msk.0.stats.rx.pause_frames: 0
 > dev.msk.0.stats.rx.mcast_frames: 0

[...]

 > dev.msk.0.stats.tx.single_colls: 0
 > dev.msk.0.stats.tx.underflows: 0
 > 

Thanks for testing and I don't see unusual things from the output.
I still can't reproduce this but would you try attached patch? Also
show me dmesg output to see controller revision.

 > > BTW, did you intentionally disable MSI?
 > 
 > No, MSI is enabled.
 > 

Ok.

-- 
Regards,
Pyun YongHyeon