Re: Interpreting ktrace output for unresponsive xterm

On Sun, 16 Apr 2017, Pavan Maddamsetti wrote: > I ran a perfectly innocuous Perl one-liner in my xterm, and it printed > the correct output. But then, the xterm stopped responding to keyboard > input. So, to paraphrase: "This perfectly innocuous thing broke things"? _I_ would start by

Re: DDB "boot sync" or "boot dump" hangs

On 04/16/17 02:37, Philip Guenther wrote: On Sun, 12 Mar 2017, gwes wrote: I'm trying to debug the following panic. I can't get a crash dump. At the DDB prompt, either "boot sync" or "boot dump" the system prints "Syncing disks: 2" and nothing more. So you asked it to sync the disks and that

Re: opening bugs for OpenBSD 6.0

Em 16/04/2017 09:16, Stuart Henderson escreveu: On 2017-04-15, Alceu Rodrigues de Freitas Junior wrote: Hi, I think I spotted a bug for OpenBSD 6.0: https://github.com/perl5-dbi/DBD-mysql/issues/120 But since 6.1 is already available (and I couldn't reproduce the

Re: flaky network connection after 6.1 upgrade

Stephan, > I would guess you are running into some issue with 802.11n support which > was added to this driver in 6.1. You should be able to restore the previous > behaviour with: ifconfig athn0 mode 11g Your hunch was almost right. 11g had the same problem, but 11b worked as expected. Attached

iwm0: could send power command (error 35), cd0 SENSE KEY: Not Ready

Hello ! I installed OpenBSD 6.1-current on a ThinkPad w541 (last 2 dmesgs are below) without problems. iwm works without problems and from time to time I see the message cd0(ahci0:5:0): Check Condition (error 0x70) on opcode 0x0 SENSE KEY: Not Ready at the console. I use the drive only to

Re: Thinkpad T460s on lastest -snapshot, no Xorg

I tried the solution. OpenBSD gets to boot, and I can see the resolution change to fb console for an instant, then the panel goes black. Too quick to be able to see anything; I'll try recording the screen with my smartphone xD This laptop doesn't have HDD lights, so I'm not sure if the computer

Re: Thinkpad T460s on lastest -snapshot, no Xorg

Got it! CSM setting must be enable in BIOS setup to correctly boot on fb console. Now I have wsfb running. Thanks for the kind help! 2017-04-16 17:34 GMT+02:00 Daniel Gracia : > I tried the solution. OpenBSD gets to boot, and I can see the resolution > change to fb console

Re: ordering

On 04/16/17 03:28, Friedrich Locke wrote: > i would like to order obsd 6.1, butfrom the openbsd store i cannot see it > available for ordering. > May you help me ? As others have pointed out, 6.0 was the last release with an official CD set made. But as long as you have funds allocated, you

Re: opening bugs for OpenBSD 6.0

On 2017-04-15, Alceu Rodrigues de Freitas Junior wrote: > Hi, > > I think I spotted a bug for OpenBSD 6.0: > > https://github.com/perl5-dbi/DBD-mysql/issues/120 > > But since 6.1 is already available (and I couldn't reproduce the error > for it), I'm not sure if I

Re: Using X with VESA on Skylake

I tried a suggestion from Gregor Best on a different thread https://marc.info/?l=openbsd-misc=149229853815568=2 I reinstalled 6.1, but booting via UEFI this time. Using the wsfb driver like it says in that thread worked for me. I am not sure if I could have got my original "bios" install

Re: Is randomizing UID/GUID would make sense?

On 2017-04-15, wrote: > OpenBSD still randomizes PIDs, but I don't see the point these days: > https://security.stackexchange.com/questions/88692/do-randomized-pids-bring-more-security/89961 'Protect against PID prediction vulnerabilities

Re: pf.conf: best practice for IP address lookup?

Am 16. April 2017 10:54:51 MESZ schrieb Harald Dunkel : >Hash: SHA256 > >Hi Florian, > >sorry to say, but you missed the point. The IP address of >*another* host inside my LAN changes, e.g. a mail server, >a http proxy, etc. The interface identifier of each host is >surely stable.

Re: pf.conf: best practice for IP address lookup?

Hi Harald, just use `($IFACE)` to get interface's current IP (with the rules being updated when the IP changes). In addition you can use the interface group `egress` to address the interface which is used for the default route. Both options are used together in the OpenBSD router tutorial on

Re: Is randomizing UID/GUID would make sense?

On Sat, 15 Apr 2017 23:16:18 -0600 "Theo de Raadt" wrote: > > Responding to multiple messages: > > > > On Fri, 20 Jan 2017 08:43:46 +0100 > > "minek van" wrote: > > > I can see that the default users and when creating new ones have > > > their UID/GUID

Re: flaky network connection after 6.1 upgrade

On Sat, Apr 15, 2017 at 10:06:44PM -0500, Colton Lewis wrote: > After upgrading to 6.1, I have been unable to maintain an internet > connection for more than a few seconds at a time. > > The machine in question uses an Atheros AR9281 for a wifi connection. > All other machines on that wifi

Re: pf.conf: best practice for IP address lookup?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Florian, sorry to say, but you missed the point. The IP address of *another* host inside my LAN changes, e.g. a mail server, a http proxy, etc. The interface identifier of each host is surely stable. The prefix is not. Using the old prefix in

Re: ordering

Hi Vijay and everyone else, > I had sent an email to ord...@openbsdstore.com regarding this > yesterday and they replied that "there isn't a 6.1 cd, please check > out the obsd.org site to persuade them to make one...". However I did > not want to bother the list and the developers in case

Re: DDB "boot sync" or "boot dump" hangs

On Sun, 12 Mar 2017, gwes wrote: > I'm trying to debug the following panic. > I can't get a crash dump. > At the DDB prompt, either "boot sync" or "boot dump" > the system prints "Syncing disks: 2" and nothing more. So you asked it to sync the disks and that was unable complete: if it did it

Re: 6.1: dnsmasq unresponsive?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 04/15/17 23:39, Stuart Henderson wrote: > > It's the same version of dnsmasq. The thing that changed is that we now have > IP_SENDSRCADDR. > > Needs fixing, but you can use -z on the dnsmasq command line as a workaround > for now. > Seems

Re: building release without noperm?

> > bash-4.4# export DESTDIR=/dest; export RELEASEDIR=/export/releasedir > > bash-4.4# cd /usr/src/etc && make release > > sh /usr/src/sys/conf/newvers.sh > > touch: version: Permission denied > > /usr/src/sys/conf/newvers.sh[84]: cannot create version: Permission denied > > *** Error 1 in

Re: ordering

While I understand this decision, I would like to mention some issues [which you almost certainly already knew about] which might convince someone else to eventually tackle the CD release process (or maybe scare them away from doing so): (1) CDs, by their nature, are a bit more difficult to

Re: Thinkpad T460s on lastest -snapshot, no Xorg

Thanks for the tip; I was installing a Win side-to-side and using legacy BIOS mode. Cheers! 2017-04-16 1:21 GMT+02:00 Gregor Best : > Hi Daniel, > > I have a laptop with a similar chipset. The issue is that the > inteldrm(4) driver does not support Skylake devices at the

Re: pf.conf: best practice for IP address lookup?

Am 16. April 2017 14:22:42 MESZ schrieb Florian Ermisch : >Am 16. April 2017 10:54:51 MESZ schrieb Harald Dunkel >: >>Hash: SHA256 >> >>Hi Florian, >> >>sorry to say, but you missed the point. The IP address of >>*another* host inside my LAN changes,

Re: pf.conf: best practice for IP address lookup?

Am 04/16/17 um 16:49 schrieb Florian Ermisch: > But then I couldn't even say if an address change would trigger > ifstated(8)… In this case it would, because an IPv6 address change at Deutsche Telekom is triggered by a reconnect. I use ifstated to trigger an asterisk and pf reload. > > Regards,

Re: installing Graphite on OpenBSD 6.0

On 04/12, Alceu R. de Freitas Jr. wrote: > Hello there, > I was struggling yesterday to try to setup Collectd with Graphite on a > OpenBSD 6.0 running over Virtualbox but couldn't complete the Graphite part > of it. > It seems Graphite is not entirely available to OpenBSD (package or ports): I

Interpreting ktrace output for unresponsive xterm

I ran a perfectly innocuous Perl one-liner in my xterm, and it printed the correct output. But then, the xterm stopped responding to keyboard input. Here is my dmesg: OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT 2016