Messages in this thread | | | From | Dirk Gouders <> | Subject | Re: [BUG] Problem with commit cf03c5dac83609f09d9f0e9fa3c09d86daed614d | Date | Thu, 26 Jul 2012 19:53:57 +0200 |
| |
Seth Forshee <seth.forshee@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
| |