Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Dec 2008 12:43:56 +0200
From:      Ian FREISLICH <ianf@clue.co.za>
To:        pyunyh@gmail.com
Cc:        current@freebsd.org
Subject:   Re: msk(4) stops working. 
Message-ID:  <E1LFRDn-0000Oi-SK@clue.co.za>
In-Reply-To: <20081224085143.GH95088@cdnetworks.co.kr> 
References:  <20081224085143.GH95088@cdnetworks.co.kr> <11167f520812232229g5ee1d475kdd92fd6511c50c29@mail.gmail.com> <E1LF7Oc-000Djt-C1@clue.co.za> <20081224021016.GF95088@cdnetworks.co.kr> <E1LFMVU-0001fB-Mz@clue.co.za> <E1LFNdS-0001pT-0q@clue.co.za> 

next in thread | previous in thread | raw e-mail | index | archive | help
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.rx.crc_errs: 0
dev.msk.0.stats.rx.good_octets: 538
dev.msk.0.stats.rx.bad_octets: 0
dev.msk.0.stats.rx.frames_64: 3
dev.msk.0.stats.rx.frames_65_127: 0
dev.msk.0.stats.rx.frames_128_255: 0
dev.msk.0.stats.rx.frames_256_511: 1
dev.msk.0.stats.rx.frames_512_1023: 0
dev.msk.0.stats.rx.frames_1024_1518: 0
dev.msk.0.stats.rx.frames_1519_max: 0
dev.msk.0.stats.rx.frames_too_long: 0
dev.msk.0.stats.rx.jabbers: 0
dev.msk.0.stats.tx.ucast_frames: 0
dev.msk.0.stats.tx.bcast_frames: 0
dev.msk.0.stats.tx.pause_frames: 0
dev.msk.0.stats.tx.mcast_frames: 0
dev.msk.0.stats.tx.octets: 0
dev.msk.0.stats.tx.frames_64: 0
dev.msk.0.stats.tx.frames_65_127: 0
dev.msk.0.stats.tx.frames_128_255: 0
dev.msk.0.stats.tx.frames_256_511: 0
dev.msk.0.stats.tx.frames_512_1023: 0
dev.msk.0.stats.tx.frames_1024_1518: 0
dev.msk.0.stats.tx.frames_1519_max: 0
dev.msk.0.stats.tx.colls: 0
dev.msk.0.stats.tx.late_colls: 0
dev.msk.0.stats.tx.excess_colls: 0
dev.msk.0.stats.tx.multi_colls: 0
dev.msk.0.stats.tx.single_colls: 0
dev.msk.0.stats.tx.underflows: 0

After:
[apple] /usr/home/ianf # sysctl dev.msk.0.stats
dev.msk.0.stats.rx.ucast_frames: 8561
dev.msk.0.stats.rx.bcast_frames: 5
dev.msk.0.stats.rx.pause_frames: 0
dev.msk.0.stats.rx.mcast_frames: 0
dev.msk.0.stats.rx.crc_errs: 0
dev.msk.0.stats.rx.good_octets: 12964072
dev.msk.0.stats.rx.bad_octets: 0
dev.msk.0.stats.rx.frames_64: 5
dev.msk.0.stats.rx.frames_65_127: 10
dev.msk.0.stats.rx.frames_128_255: 6
dev.msk.0.stats.rx.frames_256_511: 4
dev.msk.0.stats.rx.frames_512_1023: 6
dev.msk.0.stats.rx.frames_1024_1518: 8535
dev.msk.0.stats.rx.frames_1519_max: 0
dev.msk.0.stats.rx.frames_too_long: 0
dev.msk.0.stats.rx.jabbers: 0
dev.msk.0.stats.tx.ucast_frames: 10050
dev.msk.0.stats.tx.bcast_frames: 5
dev.msk.0.stats.tx.pause_frames: 0
dev.msk.0.stats.tx.mcast_frames: 0
dev.msk.0.stats.tx.octets: 712314
dev.msk.0.stats.tx.frames_64: 2
dev.msk.0.stats.tx.frames_65_127: 10038
dev.msk.0.stats.tx.frames_128_255: 9
dev.msk.0.stats.tx.frames_256_511: 3
dev.msk.0.stats.tx.frames_512_1023: 3
dev.msk.0.stats.tx.frames_1024_1518: 0
dev.msk.0.stats.tx.frames_1519_max: 0
dev.msk.0.stats.tx.colls: 0
dev.msk.0.stats.tx.late_colls: 0
dev.msk.0.stats.tx.excess_colls: 0
dev.msk.0.stats.tx.multi_colls: 0
dev.msk.0.stats.tx.single_colls: 0
dev.msk.0.stats.tx.underflows: 0

> BTW, did you intentionally disable MSI?

No, MSI is enabled.

Ian

--
Ian Freislich



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1LFRDn-0000Oi-SK>