Date: Wed, 21 Dec 2005 22:54:57 +0100 From: Andrea Campi <andrea+freebsd_current@webcom.it> To: Sam Leffler <sam@errno.com> Cc: Andrea Campi <andrea+freebsd_current@webcom.it>, current@freebsd.org Subject: Re: Panic and LOR on -CURRENT with ath Message-ID: <20051221215457.GE17950@webcom.it> Resent-Message-ID: <20051221215808.GA30095@webcom.it> In-Reply-To: <43A9B5EA.8030905@errno.com> References: <20051221191919.GB17950@webcom.it> <43A9B5EA.8030905@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sam,
On Wed, Dec 21, 2005 at 12:07:06PM -0800, Sam Leffler wrote:
> This is a driver lock held across an ioctl that does copyout and the
> destination faults. I've tried to get people to buy into a solution to
> the general problem w/o luck.
Does this only need someone to sit down and code a solution, or is that
a broader and not only technical issue?
> It appears the mbuf was reclaimed while sitting on the tx queue waiting
> to be reaped. I've seen a few complaints of this sort but never enough
> info to start looking. This problem seems to be common to soekris h/w
> or perhaps this general config which is common on soekris h/w. Knowing
> the configuration might be useful; e.g. bridged config? what packet
> filter package? network setup?
Nope, no bridging; this is nanobsd with a GENERIC kernel minus a lot of
stuff plus ipfw (which I also use for NAT). Nothing fancy really. It's
not even under any high load.
Is there anything I can investigate from DDB?
Bye,
Andrea
--
Press every key to continue.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051221215457.GE17950>