From: Kent Gibson <warthog618@gmail.com>
To: Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Subject: Re: [libgpiod][PATCH] tools: tests: replace egrep with grep -E
Date: Fri, 2 Jun 2023 18:34:45 +0800 [thread overview]
Message-ID: <ZHnFxdcZJEd1ta0R@sol> (raw)
In-Reply-To: <ZHlQT5KeU+7GkYba@sol>
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
next prev parent reply other threads:[~2023-06-02 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 14:09 [libgpiod][PATCH] tools: tests: replace egrep with grep -E Bartosz Golaszewski
2023-06-01 14:28 ` Kent Gibson
2023-06-01 16:58 ` Andy Shevchenko
2023-06-02 2:13 ` Kent Gibson
2023-06-02 10:34 ` Kent Gibson [this message]
2023-06-02 13:10 ` Bartosz Golaszewski
2023-06-02 13:26 ` Kent Gibson
2023-06-02 15:33 ` Bartosz Golaszewski
2023-06-02 16:07 ` Kent Gibson
2023-06-03 1:53 ` Kent Gibson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZHnFxdcZJEd1ta0R@sol \
--to=warthog618@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bartosz.golaszewski@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.