On Fri, Apr 27, 2018 at 11:07:22PM +0200, Tom Ivar Helbekkmo wrote:
> No xhci in this system, no. The uhci usage here is serial communication
> with a Z-Wave device that implements ucom0, as seen in dmesg.boot:
Ok, there was a xhci interrupt and usb softint related change recently,
so just making
Updating src tree:
P src/share/man/man9/mbuf.9
P src/share/man/man9/secmodel_securelevel.9
P src/sys/arch/aarch64/aarch64/pmap.c
P src/sys/arch/aarch64/include/db_machdep.h
P src/sys/arch/aarch64/include/pmap.h
P src/sys/arch/aarch64/include/types.h
P src/sys/arch/arm/arm32/bus_dma.c
P src/sys/arc
Date:Fri, 27 Apr 2018 21:34:49 +0100
From:Roy Marples
Message-ID:
| Hopefully this fixes the issues and won't impact small memory devices
| too much.
While those are probably useful changes to make, they don't fix anything,
merely make it less likely.
We reall
On Fri, 27 Apr 2018, Roy Marples wrote:
Hi Paul
On 27/04/2018 04:09, Paul Goyette wrote:
I've got lots of memory, so I don't understand what buffers are not
available.?? Ever since upgrading to my current system (sources dated
2018-03-20 11:25:00 UTC), I've been seeing these messages at random
Martin Husemann writes:
> Is that uhci a companion of a xhci? Which version of sys/dev/usb/xhci.c
> do you have and can you post a full dmesg please?
No xhci in this system, no. The uhci usage here is serial communication
with a Z-Wave device that implements ucom0, as seen in dmesg.boot:
Copyr
Hi Paul
On 27/04/2018 04:09, Paul Goyette wrote:
I've got lots of memory, so I don't understand what buffers are not
available. Ever since upgrading to my current system (sources dated
2018-03-20 11:25:00 UTC), I've been seeing these messages at random
intervals:
Can you test the below patche
On Fri, Apr 27, 2018 at 07:13:28PM +0200, Tom Ivar Helbekkmo wrote:
> I'm playing with home automation software, so I'm suddenly doing a lot
> of USB communication. Here are a couple of crashes with -current as of
> a couple of days ago:
> uhci_reset_std_chain.isra.5() at uhci_reset_std_chain.isra
I'm playing with home automation software, so I'm suddenly doing a lot
of USB communication. Here are a couple of crashes with -current as of
a couple of days ago:
: dejah# ;crash -N netbsd.9 -M netbsd.9.core
Crash version 8.99.14, image version 8.99.14.
System panicked: kernel diagnostic asserti
Date:Fri, 27 Apr 2018 15:34:22 +0200
From:Joerg Sonnenberger
Message-ID: <20180427133422.gc30...@britannica.bec.de>
| Sure, but we also have a history of at least providing a "best effort"
| to notify the source when the datagrams are discarded locally.
Sure, not
On Fri, Apr 27, 2018 at 01:05:33PM +0700, Robert Elz wrote:
> Date:Fri, 27 Apr 2018 05:18:16 +0100
> From:Roy Marples
> Message-ID: <58598dae-238e-44a5-e74f-bbb2fdd7b...@marples.name>
>
> | No-one has yet weighed in on how this should be resolved.
>
> Go back to si
Date:Fri, 27 Apr 2018 12:36:31 +0200
From:Martin Husemann
Message-ID: <20180427103631.gh21...@mail.duskware.de>
| Syslogd could catch it and log a better error message,
How? All it can ever discover is that some datagram (on its
unix domain socket) lost a message
On Fri, Apr 27, 2018 at 11:25:32AM +0100, Patrick Welche wrote:
> syslogd[316]: recvfrom() unix `/var/run/log': No buffer space available
Syslogd could catch it and log a better error message, but it IS an
important error and should not be silently ignored, IMHO.
Martin
On Fri, Apr 27, 2018 at 11:14:12AM +0100, Roy Marples wrote:
> Which application logged the error? Both wpa_supplicant and dhcpcd look at
> route(4).
> dhcpcd will note it and call getifaddrs(3) to resync the state of affairs.
> wpa_supplicant will just log the error and continue.
There's a questi
On 27/04/2018 09:45, Patrick Welche wrote:
The very odd situation in which I saw those buffer overflows, is simply
on a home machine, so flaky home broadband, running a pkg_rolling-replace.
The machine has 32G of memory, but from your message that is irrelevant.
The urtwmn0 was struggling (that's
On Fri, Apr 27, 2018 at 08:52:35AM +0100, Roy Marples wrote:
> Since NetBSD-5, I've modified the kernel to announce IPv6 address state
> changes, introduced IPv4 address state changes which are also announced AND
> added a layer of compat to the more generic RTM messages so that interface
> address
On 27/04/2018 07:05, Robert Elz wrote:
Date:Fri, 27 Apr 2018 05:18:16 +0100
From:Roy Marples
Message-ID: <58598dae-238e-44a5-e74f-bbb2fdd7b...@marples.name>
| No-one has yet weighed in on how this should be resolved.
Go back to silently discarding the error
16 matches
Mail list logo
