Date: Wed, 24 Dec 2008 13:35:03 -0800 From: Garrett Cooper <yanefbsd@gmail.com> To: Ian FREISLICH <ianf@clue.co.za> Cc: "Sam Fourman Jr." <sfourman@gmail.com>, "pyunyh@gmail.com" <pyunyh@gmail.com>, "current@freebsd.org" <current@freebsd.org> Subject: Re: msk(4) stops working. Message-ID: <76D47549-EC5A-4CF4-A5D3-371FA0A0920C@gmail.com> In-Reply-To: <E1LFNdS-0001pT-0q@clue.co.za> References: <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
On Dec 23, 2008, at 22:54, Ian FREISLICH <ianf@clue.co.za> 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 >> system >> 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. > > Ian > > -- > Ian Freislich I have an SMP system at home with ULE enabled and I transfer multiple gigs of data via smb without issue. I'll try scp'ing the file too. Btw are you using amd64 or i386, and how large is the file exactly? -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76D47549-EC5A-4CF4-A5D3-371FA0A0920C>