Date: Sat, 19 Jul 2008 10:57:26 -0500 From: "Edward Ruggeri" <smallhand@crawblog.com> To: "Garrett Cooper" <yanefbsd@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: 7.0 CURRENT kernel's ath driver causes page fault, kernel panic (debugging kernel) Message-ID: <919383240807190857x6352a004x37943642399242fa@mail.gmail.com> In-Reply-To: <919383240807181729n210402a5r5095f8b1554e9891@mail.gmail.com> References: <919383240807172100j35e1c796q513fa34d83f8e8e0@mail.gmail.com> <7d6fde3d0807180336h61f13a73pcc433be16a732c7e@mail.gmail.com> <919383240807181729n210402a5r5095f8b1554e9891@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jul 18, 2008 at 7:29 PM, Edward Ruggeri <smallhand@crawblog.com> wrote: >> As for the actual debug process, there's a spot in the dev handbook >> about it (http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html), >> but when I tried debugging my issue with NTFS and SMB I didn't really >> find it helpful to be honest... AND >> You may also have to compile without SMP and with the 4BSD scheduler >> just to see whether or not it's an issue reproducible with the ULE >> scheduler, the driver, or something else... I have a couple dumps now, with different kernel configurations. In addition to the debugging options Garrett has recommended, I've switched from the ULE to the 4BSD scheduler and removed SMP support. The error persists. The backtrace in kgdb says that panic is called from the function ath_start at line 1748 in ath_start.c. Here is a snippet: bf = STAILQ_FIRST(&frags); KASSERT(bf != NULL, ("no buf for txfrag")); Does that sound like enough to file a problem report with? What other information would be desired? -- Ned Ruggeri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?919383240807190857x6352a004x37943642399242fa>