On Mon, Nov 30, 2020 at 01:22:45PM -0800, David Wolfskill wrote:
> On Mon, Nov 30, 2020 at 11:03:29PM +0200, Konstantin Belousov wrote:
> > ...
> > > I suppose I will be commenting out that DIAGNOSTIC option now :-}
> >
> > Try to just set debug.vmem_check to 0 and see if it helps.
> > ...
>
On Mon, Nov 30, 2020 at 11:03:29PM +0200, Konstantin Belousov wrote:
> ...
> > I suppose I will be commenting out that DIAGNOSTIC option now :-}
>
> Try to just set debug.vmem_check to 0 and see if it helps.
> ...
OK; I rebooted the new(er) laptop with the previous kernel (that was
built
On Mon, Nov 30, 2020 at 12:48:47PM -0800, David Wolfskill wrote:
> On Mon, Nov 30, 2020 at 05:21:28AM -0800, David Wolfskill wrote:
> > ...
> > FWIW, the copy of the laptop's "head" kernel config in
> > http://www.catwhisker.org/~david/FreeBSD/head/CANARY is current.
> >
> > And the only
On Mon, Nov 30, 2020 at 05:21:28AM -0800, David Wolfskill wrote:
> ...
> FWIW, the copy of the laptop's "head" kernel config in
> http://www.catwhisker.org/~david/FreeBSD/head/CANARY is current.
>
> And the only difference between the stable/12 config and the head config
> is:
>
>
On Mon, Nov 30, 2020 at 02:10:51PM +0100, Mateusz Guzik wrote:
> ...
> > I definitely do NOT see anything like this running stable/12 (presently
> > at r368181).
> >
> > I will try some experiments with another laptop (a newer one, for which
> > the built-in mouse is detected weirdly, making it
On 11/30/20, David Wolfskill wrote:
> On Sun, Nov 29, 2020 at 03:20:15PM +0100, Mateusz Guzik wrote:
>> On 11/29/20, David Wolfskill wrote:
>> > On Sat, Nov 28, 2020 at 10:47:57AM -0500, Jonathan Looney wrote:
>> >> FWIW, I would try running lockstat on the box. (My supposition is that
>> >> the
On Sun, Nov 29, 2020 at 03:20:15PM +0100, Mateusz Guzik wrote:
> On 11/29/20, David Wolfskill wrote:
> > On Sat, Nov 28, 2020 at 10:47:57AM -0500, Jonathan Looney wrote:
> >> FWIW, I would try running lockstat on the box. (My supposition is that
> >> the
> >> delay is due to a lock. That could be
On Sun, Nov 29, 2020 at 08:16:22AM -0800, David Wolfskill wrote:
> On Sun, Nov 29, 2020 at 11:04:46AM -0500, Ryan Stone wrote:
> ...
> > I believe that if you run lockstat with the additional "-x
> > destructive" option, it will disable the responsiveness test (the
> > option does sound scary but
On Sun, Nov 29, 2020 at 11:04:46AM -0500, Ryan Stone wrote:
> On Sun, Nov 29, 2020 at 9:12 AM David Wolfskill wrote:
> > OK, and demonstrated some long RTTs about every 11 packets or so, but we
> > see thing come to a screeching halt with:
> >
> > ...
> > 64 bytes from 172.16.8.13: icmp_seq=534
On Sun, Nov 29, 2020 at 9:12 AM David Wolfskill wrote:
> OK, and demonstrated some long RTTs about every 11 packets or so, but we
> see thing come to a screeching halt with:
>
> ...
> 64 bytes from 172.16.8.13: icmp_seq=534 ttl=63 time=0.664 ms
> lockstat: dtrace_status(): Abort due to systemic
On Sun, Nov 29, 2020 at 03:20:15PM +0100, Mateusz Guzik wrote:
> ...
> According to the data you got the entire kernel "freezes" every 11-12
> seconds. So something way off is going on there.
I'm (quite) prepared to believe that. :-}
> Given that the bug seems to be reproducible I think it would
On 11/29/20, David Wolfskill wrote:
> On Sat, Nov 28, 2020 at 10:47:57AM -0500, Jonathan Looney wrote:
>> FWIW, I would try running lockstat on the box. (My supposition is that
>> the
>> delay is due to a lock. That could be incorrect. Lockstat may provide
>> some
>> clue as to whether this is a
On Sat, Nov 28, 2020 at 10:47:57AM -0500, Jonathan Looney wrote:
> FWIW, I would try running lockstat on the box. (My supposition is that the
> delay is due to a lock. That could be incorrect. Lockstat may provide some
> clue as to whether this is a line of inquiry worth pursuing.)
>
Thanks
I've delayed trying to send this, as I wasn't clear on how to express it
-- and I had hoped that the problem would "go away" before I figured
that part out: I first observed it around 09 Nov, which is when I
updated the laptop (via in-place source upgrade, as usual) from r367484
to r367517.
One
14 matches
Mail list logo
