Re: kern/54504: -9/-current WAPBL panic: current transaction too big to flush

[Jaromír Doleček <jaromir.dolecek%gmail.com@localhost>]

The following reply was made to PR kern/54504; it has been noted by GNATS.

From: =?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?= <jaromir.dolecek%gmail.com@localhost>
To: "gnats-bugs%NetBSD.org@localhost" <gnats-bugs%netbsd.org@localhost>
Cc: Frank Kardel <kardel%netbsd.org@localhost>
Subject: Re: kern/54504: -9/-current WAPBL panic: current transaction too big
 to flush
Date: Fri, 30 Aug 2019 08:57:56 +0200

 Le ven. 30 ao=C3=BBt 2019 =C3=A0 08:55, Martin Husemann <martin%duskware.de@localhost=
 > a =C3=A9crit :
 >
 > The following reply was made to PR kern/54504; it has been noted by GNATS=
 .
 >
 > From: Martin Husemann <martin%duskware.de@localhost>
 > To: gnats-bugs%netbsd.org@localhost
 > Cc: kardel%netbsd.org@localhost
 > Subject: Re: kern/54504: -9/-current WAPBL panic: current transaction too=
  big
 >  to flush
 > Date: Fri, 30 Aug 2019 08:50:18 +0200
 >
 >  On Fri, Aug 30, 2019 at 06:40:01AM +0000, Frank Kardel wrote:
 >  >  I just tripped over it this week with 9.99.6 from Sat Aug 10 12:14:12
 >  >  CEST 2019. I am not aware that this was an issue in the past, but I m=
 ay
 >  >  have missed that episode.
 >  >
 >  >  Nevertheless it seems to be there.
 >  >
 >  >  I can retry the test with with a more current -current if needed but =
 I
 >  >  do not right away recall any commits with respect to that since Augus=
 t
 >  >  10th.
 >
 >  There was a similar issue fixed quite some time ago, but nothing in this
 >  area changed since the netbsd-9 branch.
 
 Right. I've fixed what looks like exactly this problem at that time,
 need to look at why exactly that fix doesn't work any more.
 
 Jaromir