Hi,
First off, thank you for OpenBSD in general, and thank you specifically
for the PV drivers on OpenBSD =) The day of migrating workloads to AWS
gets ever closer for me, and I appreciate everything the OpenBSD dev
team does.
I've found what appears to be a repeatable crash that results in
;>> then back to the ehci_sync_hc's posted below, then:
>>>>>>>
>>>>>>> stopped at usb_allocmem+0x175: cmpq %rbx,0(%rax)
>>>>>>>
>>>>>>
>>>>>> cool, could you please post ehci, ohci and uhci li
FYI.
It's easy to reproduce ;-).
Wolfz
De: minha-c...@uol.com.br [mailto:minha-c...@uol.com.br]
Enviada em: sexta-feira, 15 de janeiro de 2016 02:13
Para: 'm...@openbsd.org'
Assunto: VXLAN in version 5.9
Hello,
Anybody already test vxlan in version
Forwarded Message
Subject:Re: current snap fails on gigabyte brix at uhub0
Date: Sun, 17 Jan 2016 08:03:24 -0500
From: gjones
To: m...@openbsd.org
On 1/17/2016 12:50 AM, Andrew wrote:
FYI -- the current snapshot fails on a
>Synopsis: UVM Fault with CARP on re(4)
>Category: Kernel
>Environment:
System : OpenBSD 5.8
Details : OpenBSD 5.8 (GENERIC) #1066: Sun Aug 16 02:33:00 MDT 2015
dera...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
>>>
>>>>> cool, could you please post ehci, ohci and uhci lines from your
>>>>> dmesg as well?
>>>>>
>>>>
>>>> And I'm been told that this might have been caused by something
>>>> else. To rule that out could you also try a newer snapshot (Jan 15).
>>>>
>>>
>>> Sorry, I should have mentioned that I did update to today's snapshot,
>>> and the problem recurred.
>>>
>>> I can still post dmesg output of ehci, ohci, uhci if you still need.
>>>
>>
>> Please do.
>
> Here is the last /var/run/dmesg.boot.
>
> http://dmesgd.nycbug.org/index.cgi?action=dmesgd=view=2883
Issue seems resolved with snapshot #1846 from early 20160117
http://dmesgd.nycbug.org/index.cgi?action=dmesgd=view=2884
Thanks
g