On Fri, Aug 12, 2016 at 08:51:32AM +0200, Sebastien Marie wrote:
>
> If I saw a critical shutdown message, I will report it.
>
Aug 12 08:23:58 clyde /bsd: root on sd1a (46bec6cd2747dbb1.a) swap on sd1b dump
on sd1b
Aug 12 08:23:58 clyde sendsyslog: dropped 3 messages, error 57
Aug 12 08:23:59 c
>Synopsis: gnome-shell: mmap W^X violation
>Category: user
>Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0-current (GENERIC.MP) #2336: Mon Aug 8
12:45:09 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERI
On Fri, Aug 12, 2016 at 05:01:32AM +0200, borisbo...@gmx.net wrote:
> >Synopsis:Virtualized OpenBSD under FreeBSD/bhyve and PCI passthrough
> >fails with interrupt errors
> >Category:system
> >Environment:
> System : OpenBSD 5.9
> Details : OpenBSD 5.9 (GENERIC) #1761:
>Synopsis: A user running adb can trigger a diagnostic panic
>Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
Architecture: OpenBSD.amd64
M
Hi OpenBSD crew!
In your documentation on: http://www.openbsd.org/faq/pf/nat.html#except
you state a wrong example:
pass out on tl0 from 192.168.1.0/24 to any nat-to 198.51.100.79
pass out on tl0 from 192.168.1.208 to any
(also you miss a line break there)
where should be:
pass out on tl0 from
On Fri, Aug 12, 2016 at 8:19 AM, Petr Topiarz wrote:
> where should be:
> pass out on tl0 from 192.168.1.0/24 to any nat-to 198.51.100.79
> block out on tl0 from 192.168.1.208 to any
I think you're mistaken, your rule blocks 192.168.1.208, whereas the
example serves to pass 192.168.1.208 but not
On 2016/08/12 10:15, Sonic wrote:
> On Fri, Aug 12, 2016 at 8:19 AM, Petr Topiarz wrote:
> > where should be:
> > pass out on tl0 from 192.168.1.0/24 to any nat-to 198.51.100.79
> > block out on tl0 from 192.168.1.208 to any
>
> I think you're mistaken, your rule blocks 192.168.1.208, whereas the
> Can you please give us the output of pcidump -xxv when it fails? The pcidump
> below seems to be from a boot where you weren't using pci passthrough on the
> host and thus does not include the relevant PCI config space data for the
>passed-through em/re.
>
> -ml
Of couse. Thanks @Mike for the fa
> From: "Boris Meyer"
> Date: Fri, 12 Aug 2016 21:21:04 +0200
>
> > Can you please give us the output of pcidump -xxv when it fails?
> > The pcidump below seems to be from a boot where you weren't using
> > pci passthrough on the host and thus does not include the relevant
> > PCI config space da
After latest fontconfig update (aug 10 snapshot) cwm shows the following
message and fails to start:
$ cwm: XftFontOpenName
Other applications that use xft fonts show warnings complaining about
being linked to the old freetype lib (need to be recompiled?). Some
examples:
mwm:/usr/X11R6/lib/lib
On 12 August 2016 at 22:34, Walter Alejandro Iglesias
wrote:
> After latest fontconfig update (aug 10 snapshot) cwm shows the following
I had the same thing, except cwm did start, but there were lots of these errors.
After installing another newer snapshot and an pkg_add -u, the errors
are no lo
On Fri, Aug 12, 2016 at 10:34:11PM +0200, Walter Alejandro Iglesias wrote:
> After latest fontconfig update (aug 10 snapshot) cwm shows the following
> message and fails to start:
>
> $ cwm: XftFontOpenName
No idea what's going on here. Did you configure a special font in
.cwmrc ?
Also cwm coul
On Fri, Aug 12, 2016 at 10:56:08PM +0200, Matthieu Herrb wrote:
> On Fri, Aug 12, 2016 at 10:34:11PM +0200, Walter Alejandro Iglesias wrote:
> > After latest fontconfig update (aug 10 snapshot) cwm shows the following
> > message and fails to start:
> >
> > $ cwm: XftFontOpenName
>
> No idea what
On Fri, Aug 12, 2016 at 11:10:28PM +0200, Walter Alejandro Iglesias wrote:
> On Fri, Aug 12, 2016 at 10:56:08PM +0200, Matthieu Herrb wrote:
> > On Fri, Aug 12, 2016 at 10:34:11PM +0200, Walter Alejandro Iglesias wrote:
> > > After latest fontconfig update (aug 10 snapshot) cwm shows the following
On Fri, Aug 12, 2016 at 11:26:34PM +0200, Matthieu Herrb wrote:
> On Fri, Aug 12, 2016 at 11:10:28PM +0200, Walter Alejandro Iglesias wrote:
> >
> > I've slightly changed the cwmrc syntax from
> >
> > fontname "Tahoma:size=8"
> >
> > to
> >
> > fontname "Tahoma-8"
> >
> > and it is working aga
> and therefore disable MSI support on the PCI bus. Could you check if
> the diff below probably fixes the issue?
> Seems thet the vendor ID 0x1275 is NetApp. How suprising. I suppose
> that if the diff below works, we could add the device as "NetApp BHyVe
> Host" or something like it.
It works
As addition, I also tried it with the em0 interface. As soon as I try to send
packets, I'll get the following error:
# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
ping: sendto: Host is down
ping: wrote 192.168.2.1 64 chars, ret=-1
em0: watchdog: head 5 tail 0 TDH 5 TDT 5
With
PS: Sorry, that was the wrong pcidump entry, here the right one. I appologize,
it's late...
0:5:0: Intel I217-V
0x: Vendor ID: 8086 Product ID: 153b
0x0004: Command: 0007 Status: 0018
0x0008: Class: 02 Subclass: 00 Interface: 00 Revision: 00
0x000c: BIST: 00
>Synopsis: Installing py-ndg-httpsclient makes py-requests segfault python
>Category: ports
>Environment:
System : OpenBSD 6.0
Details : OpenBSD 6.0-current (GENERIC) #2179: Fri Aug 12 11:52:42
MDT 2016
dera...@amd64.openbsd.org:/usr/src
19 matches
Mail list logo
