Date: Mon, 07 Jul 1997 23:29:34 -0700 (PDT) From: Simon Shapiro <Shimon@i-Connect.Net> To: dg@root.com Cc: FreeBSD-Hackers@FreeBSD.ORG Subject: Re: PCI Bridge Question Message-ID: <XFMail.970707232934.Shimon@i-Connect.Net> In-Reply-To: <199707080138.SAA02838@implode.root.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi David Greenman; On 08-Jul-97 you wrote:
> >> Then what version was it failing under?
> >
> >RELENG_2_2 as of Saturday. Are you maintaining this driver? Is there a
> >maintainer? Should I dig into it?
>
> I wrote it; I maintain it.
Great. Now i know who to blame :-)
>
> >> an mbuf cluster had been freed onto the mclfree list. In any case,
> this
> >> appears to be a much more generic problem - not specific to the fxp
> >> device
> >> driver.
> >
> >Most likely. The fxp is where I see it on this system.
>
> I can't reproduce the problem here, but I haven't tried very hard. Is
> NFS
> static in your kernel, or is it getting loaded as an LKM?
* Setup BONDING PPP (128Kbps)
* NFS mount a large file system (say, FreeBSD/packages-current) directly
form the host you PPP to
* cd to the NFS mount point
* find . | cpio -dmpv /somewhere/else
* Go about your business
* Wait about 20-30 minutes
[ I don't really expect you to do that. This is the setup I am using to
``prove'' the problem ]
...
> Use -current kernel with -current userland sources; start with 2.2.2
> and
> upgrade to -current ("3.0") with a "make world" if necessary.
I understand the procedure and it works well. I was inquiring about 2.2
userland and -current kernel. Guess your answer is ``no''. the more I play
with it, the less I like it (the hybrid idea).
Simon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.970707232934.Shimon>