Seth Forshee <seth.fors...@canonical.com> writes: > On Thu, Jul 26, 2012 at 05:07:57PM +0200, Dirk Gouders wrote: >> Hi Seth, >> >> thanks for your reply and sorry for the noise. >> >> I followed your advice and tried to boot with the WLAN interface turned >> off, and the problem still exists. I'll start a new bisect session, >> probably with one of the commits you mentioned as the first good commit. > > Just to make sure three's not any confusion ... > > What I was suggesting was not just disabling the network interface but > completely preventing brcmsmac from being loaded. The oops you saw > happens in the context of the driver's probe function and would happen > regardless of whether or not the interface is enabled.
Sorry for the confusion. I already started a new bisect session, with a bad commit I disabled brcmsmac in the kernel config and the problem still exists. Now, I continue with brcmsmac disabled and will see where the bisect ends. Dirk -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
