Re: video: ioctl VIDIOC_STREAMON: Invalid Argument

2016-10-14 Thread Martin Pieuchot

On 07/10/2016 06:44, cwl...@mst.edu wrote:

Synopsis:   video(1) fails to open webcam interface
Category:   system
Environment:

System  : OpenBSD 6.0
Details : OpenBSD 6.0-current (GENERIC.MP) #2533: Wed Oct  5
16:23:11 MDT 2016
			 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP


Architecture: OpenBSD.amd64
Machine : amd64

Description:
	When I execute video(1) on this system using my Logitech c270 Webcam, 
I get

the error in subject line. The webcam activation light flashes on for
half a second,
but does not stay. A line is entered in dmesg(1) that says:
'uvideo0: unable to open VS PIPE: INVAL'.
Oddly, this webcam works perfectly on my Thinkpad running the 6.0
release, but not
	with this hardware running 6.0. I have tried with the most recent 
snapshot, but

no luck.

How-To-Repeat:

Use video(1) with a Logitech c270 with similar hardware. I'm sorry
that's probably
unhelpful.


That's because xhci(4) lacks support for isochronous transfers.  
Somebody has to write that
code in order to support uvideo(4) and uaudio(4) devices attached to 
USB3 Host Controllers.




Re: flickering/screen blinking in -current

2016-10-14 Thread Mark Kettenis
> Date: Fri, 14 Oct 2016 23:53:02 +0100
> From: Dimitris Papastamos 
> 
> On Fri, Oct 14, 2016 at 11:47:58PM +0100, Dimitris Papastamos wrote:
> > Hi,
> > 
> > In an attempt to fix video tearing in fullscreen mode I used the
> > following config in /etc/X11/xorg.conf.d/10-intel.conf
> > 
> > Section "Device"
> > Identifier  "Intel Graphics"
> > Driver  "intel"
> > Option  "Tearfree" "true"
> > EndSection
> 
> I just noticed that even if I comment out the TearFree option
> but leave the driver option set to "intel" I still experience
> weird artifacts.

There is a reason why we use the modesetting driver on Broadwell by
default.



Re: flickering/screen blinking in -current

2016-10-14 Thread Dimitris Papastamos
On Fri, Oct 14, 2016 at 11:47:58PM +0100, Dimitris Papastamos wrote:
> Hi,
> 
> In an attempt to fix video tearing in fullscreen mode I used the
> following config in /etc/X11/xorg.conf.d/10-intel.conf
> 
> Section "Device"
>   Identifier  "Intel Graphics"
>   Driver  "intel"
>   Option  "Tearfree" "true"
> EndSection

I just noticed that even if I comment out the TearFree option
but leave the driver option set to "intel" I still experience
weird artifacts.



Volunteering for feature addition to openssh_client: Specification of source port

2016-10-14 Thread Tanmay Tiwari
Hi,

*Feature*: Specification of local port when initiating a ssh connection
using ssh client (and optionally specification of local address/interface)

Many people approach me for patching their openssh installation to allow
specification of source port when using ssh client. Mostly the reason is
they are using a source port based firewall.

I think it would be good to have the feature in the main branch of openssh.
Specifying local port is a rather basic feature for a network related
application.

I am willing to work on the feature (Its a 50 line patch anyway). Kindly
respond with whether you think the feature should be added.


Re: IPv6/NDP/IPsec breakage in -current

2016-10-14 Thread Alexander Bluhm
On Thu, Oct 06, 2016 at 11:12:18PM +0200, Christian Weisgerber wrote:
> Something is very broken at the intersection of IPv6, NDP, and IPsec
> in -current.

I also see issues with IPv6 and NDP, but no IPsec involved.  There
are several other threads on bugs@ about broken IPv6.

It seems that sending neighbor solicitation retries for expired ND
entries does not work.  The diff below helps in my case, although
it is only a workaround and not MP safe.  It would be interesting
to know wether it also affects your scenario.

The RTF_CACHED code was introduced with this commit:

revision 1.190
date: 2016/08/22 16:01:52;  author: mpi;  state: Exp;  lines: +24 -6;  
commitid: Jx7agqiuXqs8RRGd;
Make the ``rt_gwroute'' pointer of RTF_GATEWAY entries immutable.

This means that no protection is needed to guarantee that the next hop
route wont be modified by CPU1 while CPU0 is dereferencing it in a L2
resolution functions.

While here also fix an ``ifa'' leak resulting in RTF_GATEWAY being always
invalid.

dlg@ likes it, inputs and ok bluhm@


bluhm

Index: netinet6/nd6.c
===
RCS file: /data/mirror/openbsd/cvs/src/sys/netinet6/nd6.c,v
retrieving revision 1.193
diff -u -p -r1.193 nd6.c
--- netinet6/nd6.c  3 Oct 2016 12:33:21 -   1.193
+++ netinet6/nd6.c  13 Oct 2016 21:47:25 -
@@ -827,7 +827,7 @@ nd6_free(struct rtentry *rt, int gc)
 * caches, and disable the route entry not to be used in already
 * cached routes.
 */
-   if (!ISSET(rt->rt_flags, RTF_STATIC|RTF_CACHED))
+   if (!ISSET(rt->rt_flags, RTF_STATIC))
rtdeletemsg(rt, ifp, ifp->if_rdomain);
splx(s);