Re: NULL pointer dereference when 'rmmod gpio_lynxpoint'

[Linus Walleij <linus.walleij@xxxxxxxxxx>]

On Tue, May 3, 2016 at 5:23 AM, Anatol Pomozov <anatol.pomozov@xxxxxxxxx> wrote:
> On Sun, May 1, 2016 at 11:30 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
>> On Sun, May 1, 2016 at 4:36 PM, Anatol Pomozov <anatol.pomozov@xxxxxxxxx> wrote:
>>> On Sun, May 1, 2016 at 1:38 AM, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:
>>>> On Sun, May 1, 2016 at 2:33 AM, Anatol Pomozov <anatol.pomozov@xxxxxxxxx> wrote:
>>
>>> Starting from 4.2/4.3 kernel release I see numerous problems with this
>>> driver. For example there are regular crashes at the boot time when
>>> tries to load this driver https://goo.gl/photos/fGk2U6PgUFtxUk9w5    I
>>> have to stick with Arch 4.1 kernel that does not have this problem.
>>
>> Hm atleast it is not due to my recent refactorings of GPIO then.
>>
>> Any chance you can run a bisect and nail the commit?
>
> I compiled lynx gpio into kernel instead of compiling it as a module.
> And the system got more stable - I rebooted my devices ~50 times
> already and I do not see the boot problem I had before. 'CONFIG_..=y'
> definitely makes the situation better.
>
> As of bisecting - it will require time do find the commit. I might do
> it if I find some spare time.

If nothing else works I'm happy to accept a patch turning the
driver into a bool and removing all module handling code.

Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-gpio" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html