Hi On Wed, May 11, 2016 at 7:02 AM, Mika Westerberg <mika.westerberg@xxxxxxxxxxxxxxx> wrote: > On Wed, May 11, 2016 at 07:00:18AM -0700, Anatol Pomozov wrote: >> Hi >> I tried to read the gpio handling code, but I do not see any obvious >> reason for this "insert module" crash. And I had no time to do history >> bisect. >> On Wed, May 11, 2016 at 2:22 AM, Linus Walleij >> <[1]linus.walleij@xxxxxxxxxx> wrote: >> >> > 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. >> >> Before doing this I would love to get some feedback from the driver >> maintainer. Mathias, do you see this issue with the module? >> Also I am going to change Arch Linux kernel config to compile this >> driver as 'y'. > > Let's first analyze why it crashes in the first place. Can you give me > detailed instructions how can I reproduce this? I use Chromebox with Matt's coreboot firmware and Arch Linux that currently compiles LYNX gpio as a module. There are 2 crashes: 1) ~25% chance of crash at boot time. Just boot the device and the system crashes when tries to probe the driver 2) system crashes when try to 'rmmod'. See stack trace in the first message of this thread. -- 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