Date: Mon, 7 Nov 2005 06:21:21 -0500 From: Derek Tattersall <dlt@mebtel.net> To: Bill Paul <wpaul@FreeBSD.ORG> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Panic with GENERIC from today Message-ID: <20051107112121.GA13870@lorne.arm.org> In-Reply-To: <20051107091744.69E6D16A420@hub.freebsd.org> References: <200511070044.jA70ioNQ012174@lorne.arm.org> <20051107091744.69E6D16A420@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Bill Paul <wpaul@FreeBSD.ORG> [051107 06:13]: > > An i386 GENERIC kernel with an ndisgen'd wrapper for bcmwl5_sys driver > > for a Linksys WPC54G panics as it attempts to DHCP. The back trace > > reads (hand transcribed): > > kdb_enter (c08y0b30) at kdb_enter + 0x2b > > panic(c08773ef,c082441,0,d52bb944,c07daf6) at panic+0x127 > > mb_free_ext(c3737e00) at mb_free_ext +0x185 > > m_freem(c3737e00,c34d5cf8,0,c34e2800,c3737e00) at m_freem + 0x1a > > ndis_rxeof(c34ec200,d511b9e8,1,c34fc7d4,d51bbb7e) at ndis_rxeof + 0xb9 > > _end(c3785414,0,c34fc7d4,c34fc000,c34fc7d4)at 0xc333dd61 > > BCMWL5_SYS_drv_data_start(c3652228,17,7a171200,d51bf098,0) at 0xc09ba8bb > > BCMWL5_SYS_drv_data_start() at BCMWL5_SYS_drv_data_start + 0x3110 > > You know, I'm constantly amazed just how many ways people find to > mess up a simple thing like sending in a bug report. You went to > so much trouble to emphasize that your system panicked, and you were > dilligent enough to copy down the stack trace. > > And then you went and forgot to tell us what the panic message said. Oops! Message is: NDIS0 Link state changed to Up panic mb_free_ext: unknown ext type CPUID = 0 > > Go back and repeat the crash and make a note of the actual panic > message this time (i.e. "panic: something bad happened!"). Please > note that "I don't remember" or "I'll get around to it later" are > not valid responses. > > > A GENERIC kernel from a week ago with an ndisgen'd wrapper for the > > same driver works fine. > > > > Di I cvsup in the middle of a commit? I noticed Bill had committed > > some changes to the NDIS later later this afternoon, but they appeared > > to be for an intel driver. > > More than likely this is the result of Andre's recent changes to > the mbuf code. The NDISulator is still working fine for me with 6.x. > > When you report the full panic message so that I can tell what > actually went wrong, I may be able to tell you more. > > -Bill > > -- > ============================================================================= > -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu > wpaul@windriver.com | Wind River Systems > ============================================================================= > <adamw> you're just BEGGING to face the moose > ============================================================================= Thanks for looking at this. -- Best regards, Derek Tattersall dlt@mebtel.net dlt666@yahoo.com dtatters@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051107112121.GA13870>