Re: Panic and LOR on -CURRENT with ath
- From: Andrea Campi <andrea+freebsd_current@xxxxxxxxx>
- Date: Wed, 21 Dec 2005 22:54:57 +0100
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.
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Panic and LOR on -CURRENT with ath
- From: Sam Leffler
- Re: Panic and LOR on -CURRENT with ath
- References:
- Panic and LOR on -CURRENT with ath
- From: Andrea Campi
- Re: Panic and LOR on -CURRENT with ath
- From: Sam Leffler
- Panic and LOR on -CURRENT with ath
- Prev by Date: Re: -current kernel as of this morning breaks the nvidia driver
- Next by Date: Re: Dual core CPUs support
- Previous by thread: Re: Panic and LOR on -CURRENT with ath
- Next by thread: Re: Panic and LOR on -CURRENT with ath
- Index(es):
Relevant Pages
|