Re: [libgpiod][PATCH] tools: tests: replace egrep with grep -E

[Kent Gibson <warthog618@xxxxxxxxx>]

On Fri, Jun 02, 2023 at 03:10:18PM +0200, Bartosz Golaszewski wrote:
> On Fri, Jun 2, 2023 at 12:34 PM Kent Gibson <warthog618@xxxxxxxxx> wrote:
> >
> > On Fri, Jun 02, 2023 at 10:13:35AM +0800, Kent Gibson wrote:
> > >
> > > On a related(??) note, I'm occasionally seeing Oopses when testing this
> > > - when creating a basic sim with a shell script, not when deleting it.
> > > In one case after a fresh reboot and on creating the first sim, so it
> > > looks to be purely the construction.  Yay :-(.
> > >
> >
> > I had thought it would be difficult to reproduce this and so difficult
> > to bisect.  Fortunately(??) not.  If I run my setup and cleanup scripts[1]
> > in a tight loop it occurs very readily.  Haven't bisected it yet, but did
> > test it on 6.1-rc1 and it Oopsed there too, so I would need to go back
> > further.  What was the initial release containing gpio-sim?
> >
> > The sim setp is pretty simple - a couple of banks each with a few lines
> > and hogs.
> >
> > Could you confirm that you can repeat the problem?
> > Otherwise I might start thinking there is something broken in my test
> > environment.
> >
> > Btw, the loop script is:
> >
> > #!/bin/env bash
> > for (( ; ; ))
> > do
> >         echo "create sim..."
> >         ./basic_sim.sh
> >         echo "destroy sim..."
> >         ./clean_sims.sh
> > done
> >
> > Cheers,
> > Kent.
> > [1] https://github.com/warthog618/gpiosim-rs
> >
> 
> With this script I've been able to trigger an issue but it looks
> different from yours: https://pastebin.com/cbsgT2ae
> 

Looks similar to me.
I would assume that is the same issue - even if the  particulars of the
crash differ.  If you can fix that and my problem remains then we can be
sure they are distinct.

I've been doing a coarse bisect to see how far back this goes -
basically looking for a known good.
5.18 crashes, but it crashed hard, so no syslog.  It did run considerably
longer before crashing, so that could be different issue masked by the
other (later?) one.

Moving on to subsequent releases...

Cheers,
Kent.