> I'm wondering if this is due to the fact that we detach usb(4) devices on
> suspend. Looks like this may be trying to process a timeout that corresponds
> to a device that is no longer attached. Maybe the urtwn(4)?
>
> Just guessing, though. Can you reproduce this by zzz'ing, pulling the
>
2018-07-18 23:04 GMT+02:00 Alexander Bluhm :
> On Wed, Jul 18, 2018 at 08:39:17PM +0200, Eivind Eide wrote:
>> Over several snapshots after 6.3 I get reliable system crash after a
>> few minutes uptime on this old i386 machine of mine.
>
> It would be helpful to know when this started. Does it
On Wed, Jul 18, 2018 at 07:13:15AM +, Daniel Stocker wrote:
> ddb{0}> trace
> export_sa(10,800022368520) at export_sa+0x5c
> pfkeyv2_expire(81409800,81409800) at pfkeyv2_expire+0x14e
> tdb_timeout(8000223686d0) at tdb_timeout+0x39
> softclock_thread(0) at
On Wed, Jul 18, 2018 at 08:39:17PM +0200, Eivind Eide wrote:
> Over several snapshots after 6.3 I get reliable system crash after a
> few minutes uptime on this old i386 machine of mine.
It would be helpful to know when this started. Does it happen with
6.3? Since 6.3 we have commited i386
Over several snapshots after 6.3 I get reliable system crash after a
few minutes uptime on this old i386 machine of mine.
I have no explanation other than the documentation I provide.
As gmail mangles all text I try to give the system information as
provided by sendbug as textfile attachment to
