no media opt on axe(4)

Hi, sometimes since 6.3, something broken axe(4) mediaopt: media: Ethernet none (none) supported media: media none This is a trendnet TU2-ET100, listed in the manpage and shown in dmesg as: axe0 at uhub1 port 1 configuration 1 interface 0 "ASIX Electronics

Re: curl/w3m https request with torsocks core dump at exit

On Tuesday 24 April 2018 12:07:10 Philip Guenther wrote: > On Tue, 24 Apr 2018, Jeremie Courreges-Anglas wrote: > ... > > > We took a quick look yesterday, the crash happens in dtors, the cause of > > the crash looks like a use after free. I'm not a BIO_* hacker, here's > > a stack trace on

Re: curl/w3m https request with torsocks core dump at exit

On Tue, 24 Apr 2018, Jeremie Courreges-Anglas wrote: ... > We took a quick look yesterday, the crash happens in dtors, the cause of > the crash looks like a use after free. I'm not a BIO_* hacker, here's > a stack trace on amd64, curl rebuilt with DEBUG=-g: > > Program received signal SIGBUS, Bus

Re: curl/w3m https request with torsocks core dump at exit

On Sat, Apr 21 2018, Solene Rapenne wrote: >>Synopsis: >>Category: >>Environment: > System : OpenBSD 6.3 > Details : OpenBSD 6.3-current (GENERIC) #53: Thu Apr 19 11:07:26 > MDT 2018 > >

Re: panic in radeondrm_attachhook

On Wed, Apr 18, 2018 at 06:55:35PM +0200, Alexander Bluhm wrote: > On Thu, Apr 19, 2018 at 12:10:04AM +1000, Jonathan Gray wrote: > > That's with the big radeon update diff as well? > > That was current. Boots fine. > > With ~jsg/radeon.diff.2 it still crashes. I have checked, it is > the diff

Re: modesetting driver broke video(1)

On Thu, Mar 29, 2018 at 11:47:16AM +0200, Martin Pieuchot wrote: > Since we switched to the modesetting driver by default, the supported > XvImage formats no longer include YUY2 nor UYVY which are expected by > video(1). Using the following Xorg.conf makes video(1) works again. > > Section

Re: panic in radeondrm_attachhook

> Date: Tue, 24 Apr 2018 20:18:42 +1000 > From: Jonathan Gray > > On Wed, Apr 18, 2018 at 06:55:35PM +0200, Alexander Bluhm wrote: > > On Thu, Apr 19, 2018 at 12:10:04AM +1000, Jonathan Gray wrote: > > > That's with the big radeon update diff as well? > > > > That was current.

Re: modesetting driver broke video(1)

> Date: Tue, 24 Apr 2018 10:35:36 +0200 > From: Landry Breuil > > All that to say, maybe that means that video(1) can/should be adapted to > use another method/encoding, because the camera itself works in firefox > and is supported. If YUY2 and UYVY are not going to come back

Re: panic in radeondrm_attachhook

On Tue, Apr 24, 2018 at 01:53:07PM +0200, Mark Kettenis wrote: > > Date: Tue, 24 Apr 2018 20:18:42 +1000 > > From: Jonathan Gray > > > > On Wed, Apr 18, 2018 at 06:55:35PM +0200, Alexander Bluhm wrote: > > > On Thu, Apr 19, 2018 at 12:10:04AM +1000, Jonathan Gray wrote: > > > >

Re: panic in radeondrm_attachhook

On Tue, Apr 24, 2018 at 02:25:24PM +0200, Alexander Bluhm wrote: > On Tue, Apr 24, 2018 at 08:18:42PM +1000, Jonathan Gray wrote: > > After spending some time trying to track this down I have come up with > > the diff below and included it in ~jsg/radeon.diff.4 can you confirm > > that it works

Re: panic in radeondrm_attachhook

On Tue, Apr 24, 2018 at 08:18:42PM +1000, Jonathan Gray wrote: > After spending some time trying to track this down I have come up with > the diff below and included it in ~jsg/radeon.diff.4 can you confirm > that it works for you as well? With this diff my machine boots fine. No monitor

Re: Console resolution restricted to 848x400 on inteldrm

> From: Thomas Sullivan > > HI all, > > I've just installed 6.3 on my Early 2008 MacBook, with `inteldrm` graphics > and the console resolution seems misconfigured such that the screen > resolution is the full panel resolution at 1280x800 but the console itself > much

Re: ksh: regression in timing for loops

On Sun, Apr 22, 2018 at 04:31:08AM +0200, Klemens Nanni wrote: > While looking at `time' for other things, tb@ pointed out that the > following code is broken: > > $ time for i in 1 2; do echo $i; done > ksh: : is read only > > Note the missing variable name: time's pipeline fails

Re: Console resolution restricted to 848x400 on inteldrm

On Tue, 24 Apr 2018 at 11:37 pm, Thomas Sullivan wrote: > Thanks Mark, > > That was my thought too, but it’s not hooked up to anything except power > and ethernet. > > On Tue, 24 Apr 2018 at 11:24 pm, Mark Kettenis > wrote: > >> > From: Thomas