Date: Mon, 15 Dec 2008 13:32:35 +0100 From: "Paul B. Mahol" <onemda@gmail.com> To: "Kip Macy" <kmacy@freebsd.org> Cc: Damian Gerow <dgerow@afflictions.org>, freebsd-current@freebsd.org Subject: Re: ural(4) hits usb/124758 (Was: Panic while using ural(4) with wpa_supplicant) Message-ID: <3a142e750812150432l1d59b6e0icc070935d569ec87@mail.gmail.com> In-Reply-To: <3c1674c90812142117m71a6c67dkf6f7dda02a6aa411@mail.gmail.com> References: <20081212054137.GA42087@plebeian.afflictions.org> <20081215051245.GA58909@plebeian.afflictions.org> <3c1674c90812142117m71a6c67dkf6f7dda02a6aa411@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/15/08, Kip Macy <kmacy@freebsd.org> wrote: > I reliably hit panics with ural(4) as well - they appear to be locking > related. > Correct, this PR is same as one from me - but mine is for rum driver. using kern.smp.disabled=1 is workaround. usb2_wlan_rum from usb2 doesnt have that problem - I do not use old usb stack any more. > Cheers, > Kip > > On Mon, Dec 15, 2008 at 5:12 AM, Damian Gerow <dgerow@afflictions.org> > wrote: >> I've been able to reliably trigger the panic with ural(4), but I'm pretty >> sure it has nothing to do with wpa_supplicant(8). A quick search of the >> PR >> database turns up usb/124758. >> >> Panic (PID 12 is "irq19: ehci1"): >> >> ----- >> ural0: could not transmit buffer: SHORT_XFER >> panic: ehci_free_sqtd_chain: chain not found >> cpuid = 0 >> KDB: enter: panic >> [thread pid 12 tid 100042] -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750812150432l1d59b6e0icc070935d569ec87>