On Wed, 2023-08-30 at 11:43 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Fri, 2023-08-25 at 07:34 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > > >
> > > > qemu 8.1.0 brings with it a new set of problems but I've reproduced the
> > > > hang with 8.1.0 so it does
On Fri, 2023-08-25 at 07:34 +0100, Richard Purdie via
lists.openembedded.org wrote:
> > >
> > > qemu 8.1.0 brings with it a new set of problems but I've reproduced the
> > > hang with 8.1.0 so it does not solve that.
> > >
> > > I'm really struggling to understand which change brought in these
>
Hi,
On Fri, Aug 25, 2023 at 07:34:25AM +0100, Richard Purdie wrote:
> On Fri, 2023-08-25 at 09:27 +0300, Mikko Rapeli wrote:
> > Hi,
> >
> > On Thu, Aug 24, 2023 at 09:18:03PM +0100, Richard Purdie wrote:
> > > On Thu, 2023-08-24 at 15:04 +0100, Richard Purdie via
> > > lists.openembedded.org
On Fri, 2023-08-25 at 09:27 +0300, Mikko Rapeli wrote:
> Hi,
>
> On Thu, Aug 24, 2023 at 09:18:03PM +0100, Richard Purdie wrote:
> > On Thu, 2023-08-24 at 15:04 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > On Wed, 2023-08-23 at 22:16 +0100, Richard Purdie via
> > >
Hi,
On Thu, Aug 24, 2023 at 09:18:03PM +0100, Richard Purdie wrote:
> On Thu, 2023-08-24 at 15:04 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2023-08-23 at 22:16 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > On Tue, 2023-08-22 at 23:01 +0100, Richard
Le jeu. 24 août 2023, 22:18, Richard Purdie <
richard.pur...@linuxfoundation.org> a écrit :
> On Thu, 2023-08-24 at 15:04 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Wed, 2023-08-23 at 22:16 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > On Tue, 2023-08-22
On Thu, 2023-08-24 at 15:04 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Wed, 2023-08-23 at 22:16 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > On Tue, 2023-08-22 at 23:01 +0100, Richard Purdie via
> > lists.openembedded.org wrote:
> > > so the commands are stopping
On Wed, 2023-08-23 at 22:16 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Tue, 2023-08-22 at 23:01 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > so the commands are stopping mid flow for unknown reasons or the ssh
> > connection fails. I can't tell if this coincides
On Tue, 2023-08-22 at 23:01 +0100, Richard Purdie via
lists.openembedded.org wrote:
> so the commands are stopping mid flow for unknown reasons or the ssh
> connection fails. I can't tell if this coincides with an rcu stall or
> not. Both logs do have rcu stalls in.
>
> After these failures the
On Tue, 2023-08-22 at 22:08 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Tue, 2023-08-22 at 15:49 +0100, Richard Purdie via
> lists.openembedded.org wrote:
> > 03b2c470a136a83a9961a2a855cde59498361598 shows as broken
> >
> > deda0761dc6161f03278da4679d96d4727992e91 doesn't seem to
On Tue, 2023-08-22 at 15:49 +0100, Richard Purdie via
lists.openembedded.org wrote:
> 03b2c470a136a83a9961a2a855cde59498361598 shows as broken
>
> deda0761dc6161f03278da4679d96d4727992e91 doesn't seem to break
>
> but this doesn't seem to make any sense as the changes are:
>
> kernel-source$
03b2c470a136a83a9961a2a855cde59498361598 shows as broken
deda0761dc6161f03278da4679d96d4727992e91 doesn't seem to break
but this doesn't seem to make any sense as the changes are:
kernel-source$ git diff 03b2c470a136a83a9961a2a855cde59498361598
deda0761dc6161f03278da4679d96d4727992e91 |
Maybe this is stating the obvious, but please avoid the temptation to
shortcut a bisect, once it's been started. There's been so many times
I guessed wrong what is the offending commit in the remaining set, all
the way to the end. Still having the issue after a revert is one of
the most
On Tue, 2023-08-22 at 15:20 +0300, Mikko Rapeli wrote:
> Hi,
>
> On Tue, Aug 22, 2023 at 12:47:04PM +0100, Richard Purdie wrote:
> > so between 6.1.38 and 6.1.39?
>
> Maybe:
>
> commit b1cdc56bc177c2e182c204bb08ad4e87bfd67942
> Author: Paul E. McKenney
> AuthorDate: Wed Apr 26 11:11:29
Hi,
On Tue, Aug 22, 2023 at 12:47:04PM +0100, Richard Purdie wrote:
> so between 6.1.38 and 6.1.39?
Maybe:
commit b1cdc56bc177c2e182c204bb08ad4e87bfd67942
Author: Paul E. McKenney
AuthorDate: Wed Apr 26 11:11:29 2023 -0700
Commit: Greg Kroah-Hartman
CommitDate: Wed Jul 19 16:21:01
On Tue, 2023-08-22 at 12:07 +0100, Richard Purdie via
lists.openembedded.org wrote:
> so between 6.1.38 and 6.1.41 ?
[0.00] Linux version 6.1.39-yocto-standard (oe-user@oe-host)
(powerpc-poky-linux-gcc (GCC) 13.2.0, GNU ld (GNU Binutils) 2.41.0.20230731) #1
PREEMPT Wed Jul 19 14:22:18
On Tue, 2023-08-22 at 10:31 +0100, Richard Purdie via
lists.openembedded.org wrote:
> On Thu, 2023-08-17 at 23:22 -0400, Paul Gortmaker wrote:
> > [Re: [OE-core] Dilemma on changes - merge or not to merge (e.g. 6.4)] On
> > 16/08/2023 (Wed 09:55) Rasmus Villemoes wrote:
> >
On Thu, 2023-08-17 at 23:22 -0400, Paul Gortmaker wrote:
> [Re: [OE-core] Dilemma on changes - merge or not to merge (e.g. 6.4)] On
> 16/08/2023 (Wed 09:55) Rasmus Villemoes wrote:
>
> > On 15/08/2023 15.08, Paul Gortmaker via lists.openembedded.org wrote:
> > > [Di
[Re: [OE-core] Dilemma on changes - merge or not to merge (e.g. 6.4)] On
16/08/2023 (Wed 09:55) Rasmus Villemoes wrote:
> On 15/08/2023 15.08, Paul Gortmaker via lists.openembedded.org wrote:
> > [Dilemma on changes - merge or not to merge (e.g. 6.4)] On 14/08/2023 (Mon
> >
On 15/08/2023 15.08, Paul Gortmaker via lists.openembedded.org wrote:
> [Dilemma on changes - merge or not to merge (e.g. 6.4)] On 14/08/2023 (Mon
> 10:54) Richard Purdie wrote:
>
>> Remaining are:
>> * an error upon boot on preempt-rt on qemux86-64
>> (e.g.
>>
On Tue, 2023-08-15 at 09:08 -0400, Paul Gortmaker wrote:
> [Dilemma on changes - merge or not to merge (e.g. 6.4)] On 14/08/2023 (Mon
> 10:54) Richard Purdie wrote:
>
> > I'm becoming a little weary/wary of some of the changes that are coming
> > in. The challenge is that once they merge, issues
[Dilemma on changes - merge or not to merge (e.g. 6.4)] On 14/08/2023 (Mon
10:54) Richard Purdie wrote:
> I'm becoming a little weary/wary of some of the changes that are coming
> in. The challenge is that once they merge, issues become the problem of
> a very small number of people.
>
> My
I'm becoming a little weary/wary of some of the changes that are coming
in. The challenge is that once they merge, issues become the problem of
a very small number of people.
My current dilemma is the 6.4 kernel. People would like it, we'd really
ideally use it for the next release but there are
23 matches
Mail list logo
