procmap prints ?VNODE?

2015-11-30 Thread Stefan Berger
hi,

with the command 'procmap pid', I often/always get ?VNODE? instead of
the actual filename.  My question is, whether this is on purpose because
on similary BSDs (pmap on NetBSD) , I don't get ?VNODE? but the actual 
filename.  Any ideas what went wrong?

$ doas procmap 1

1000  0K [ anon ]
0DE726A0272K read/exec   [ ?VNODE? ]  <-
0DE726B43000 48K read[ ?VNODE? ]  <-
0DE726C0  0K [ anon ]
0DE726C4E000  4K read/write  [ anon ]
0DE726D4E000  4K read[ ?VNODE? ]  <-
0DE726D4F000  4K read[ anon ]
0DE726E4F000  4K read/write  [ ?VNODE? ]  <-
 

(system: OpenBSD 5.8)

bergers



OpenBSD current crash (Thinkpad X220i)

2015-08-26 Thread Stefan Berger
hi, 

my notebook had a hiccup: it suddenly hanged and stoped working. 
I had firefox, cwm+X11, emacs (terminal) and a few tmux sessions open. 

The snapshot is from Monday, 24.08.  I also checkoud out the sources and it 
is selfcompiled. 

Here is what I can see in my /var/log/messages before the hiccup: 

Aug 26 11:29:19 x220i dhclient[6121]: iwn0 down; exiting
Aug 26 11:43:44 x220i apmd: battery status: high. external power status: not 
connected. estimated battery life 76% (251 minutes)
Aug 26 12:00:01 x220i syslogd: restart
Aug 26 12:33:14 x220i apmd: battery status: high. external power status: not 
connected. estimated battery life 55% (132 minutes)
Aug 26 12:43:14 x220i apmd: battery status: low. external power status: not 
connected. estimated battery life 50% (119 minutes)
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:33 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:35 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_wait_for_thread_c0] 
*ERROR* GT thread status wait timed out
Aug 26 12:43:36 x220i /bsd: error: [drm:pid12821:__gen6_gt_force_wake_get] 
*ERROR* Timed out waiting for forcewake to ack request.
Aug 26 12:43:36 x220i /bsd: error: 

IPSec OpenBSD road warrior

2015-08-20 Thread Stefan Berger
Hi, 
I am trying to accomplish this:  Connect a laptop (OpenBSD 5.7, road-warrior) 
with IPSec/VPN tunnel to an OpenBSD server.  The laptop is sitting in different 
networks who all do NAT, the server has a static IPv4 address.  The goal is 
to route all the traffic from the laptop to the server, encapsulated as IPSec 
packets.  And then, forward those packages so that communciation goes entirly 
over 'server'. 

On both machines, I created a lo1 device with the addresses 10.0.0.1 (server) 
and 10.0.0.2 (laptop).  So the configuration looks like: 

server NAT GW/DSL router
ext:1.2.3.4   -- internet --  ext:5.6.7.8  laptop
lo1:10.0.0.1  int:192.168.0.1 -  int: 
192.168.0.10
   lo1: 
10.0.0.2

ipsec.conf on the client:
ike esp from egress to 10.0.0.1 peer 1.2.3.4 psk key

ipsec.conf on the server: 
ike passive esp from 10.0.0.1 to any srcid 'servername' psk key

I can ping 10.0.0.1 (from client and server) and see that encrypted packages 
arrive 
and the enc0 says that I got icmp requests from 192.168.0.10.  I don't know, 
how to 
set up my my default route on the laptop (should be 10.0.0.1) (and then, do 
NATting).  
On lo1, there do not arrive any packages. 

Any help is much appreciated. 

Thanks, 
Berger S. 



Re: aucat problems

2015-07-28 Thread Stefan Berger
I found this

http://archives.neohapsis.com/archives/openbsd/2010-12/0057.html

but aucat seemed to have changed, at least for me, I 
can't follow the explanation.  

I am running a Thinkpad x220i and I am pretty sure that 
my microphone is supported but I tried a lot of different 
settings with mixerctl, I am not 'there' yet.. 

greetings. 



Re: aucat problems

2015-07-28 Thread Stefan Berger
On Tue, Jul 28, 2015 at 10:01:56AM +0200, Alexandre Ratchov wrote:
 On Mon, Jul 27, 2015 at 04:47:56PM -0400, Stefan Berger wrote:
  Hi, 
  
  i have some trouble, configuring my audio devices: I want to 
  record with my internal microphone (Thinkpad x220i) or/and my headphones 
  with aucat, but I can't configure it according to FAQ because 
  the output from mixerctl is somehow, different. 
 
 does playback work? assuping it does, if you run:
 
 aucat -o test.wav

I did that, but when I do the 

aucat -i test.wav

command, then I can't hear anything.  I also tried 

aucat -c 0:1 -o 1.wav -c 2:3 -o 2.wav -c 4:5 -o 3.wav

but nothing for all three files.  

 could you post the output of mixerctl -v ?

here is my mixerctl -v output:  

inputs.dac-0:1_mute=off  [ off on ]
inputs.dac-0:1=180,180 
inputs.dac-2:3_mute=off  [ off on ]
inputs.dac-2:3=180,180 
inputs.beep=108 
record.adc-0:1_source=mic2  [ sel sel2 mic2 mix ]
record.adc-0:1_mute=off  [ off on ]
record.adc-0:1=126,126 
record.adc-2:3_source=mic2  [ sel sel2 mic2 mix ]
record.adc-2:3_mute=off  [ off on ]
record.adc-2:3=126,126 
record.adc-4:5_source=mic2  [ sel sel2 mic2 mix ]
record.adc-4:5_mute=off  [ off on ]
record.adc-4:5=126,126 
inputs.sel_source=mic  [ mic ]
outputs.sel=126,126 
inputs.sel2_source=mic  [ mic ]
outputs.sel2=126,126 
outputs.hp_source=dac-0:1  [ dac-0:1 dac-2:3 ]
outputs.hp_boost=off  [ off on ]
outputs.mic_source=dac-0:1  [ dac-0:1 dac-2:3 ]
outputs.mic_dir=input-vr80  [ none output input input-vr50 input-vr80 ]
outputs.mic_eapd=on  [ off on ]
outputs.spkr_source=dac-2:3  [ dac-0:1 dac-2:3 ]
inputs.mic2=126,126 
inputs.mix_source=dac-0:1,dac-2:3  { dac-0:1 dac-2:3 }
inputs.mix_dac-0:1=126,126 
inputs.mix_dac-2:3=126,126 
outputs.hp_sense=unplugged  [ unplugged plugged ]
outputs.mic_sense=unplugged  [ unplugged plugged ]
outputs.spkr_muters=hp,mic  { hp mic }
outputs.master=181,181 
outputs.master.mute=off  [ off on ]
outputs.master.slaves=dac-0:1,dac-2:3  { dac-0:1 dac-2:3 beep sel sel2 }
record.volume=126,126 
record.volume.mute=off  [ off on ]
record.volume.slaves=adc-0:1,adc-2:3,adc-4:5  { adc-0:1 adc-2:3 adc-4:5 mic2 }



Re: aucat problems

2015-07-28 Thread Stefan Berger
On Tue, Jul 28, 2015 at 10:53:26AM +0200, Alexandre Ratchov wrote:
 If it doesn't work, try to use the other mic:
 
 mixerctl record.adc-0:1_source=sel
 mixerctl record.adc-2:3_source=sel
 mixerctl record.adc-4:5_source=sel

Setting mixerctl to sel2 worked: 

mixerctl record.adc-0:1_source=sel2
mixerctl record.adc-2:3_source=sel2
mixerctl record.adc-4:5_source=sel2


Thank you for helping. 



aucat problems

2015-07-27 Thread Stefan Berger
Hi, 

i have some trouble, configuring my audio devices: I want to 
record with my internal microphone (Thinkpad x220i) or/and my headphones 
with aucat, but I can't configure it according to FAQ because 
the output from mixerctl is somehow, different. 

inputs.dac-0:1_mute=off
inputs.dac-0:1=153,153
inputs.dac-2:3_mute=on
inputs.dac-2:3=153,153
inputs.beep=108
record.adc-0:1_source=mic2
record.adc-0:1_mute=off
record.adc-0:1=126,126
record.adc-2:3_source=mic2
record.adc-2:3_mute=off
record.adc-2:3=126,126
record.adc-4:5_source=mic2
record.adc-4:5_mute=off
record.adc-4:5=126,126
inputs.sel_source=mic
outputs.sel=126,126
inputs.sel2_source=mic
outputs.sel2=126,126
outputs.hp_source=dac-0:1
outputs.hp_boost=off
outputs.mic_source=dac-0:1
outputs.mic_dir=input-vr80
outputs.mic_eapd=on
outputs.spkr_source=dac-2:3
inputs.mic2=126,126
inputs.mix_source=dac-0:1,dac-2:3
inputs.mix_dac-0:1=126,126
inputs.mix_dac-2:3=126,126
outputs.hp_sense=plugged
outputs.mic_sense=plugged
outputs.spkr_muters=hp,mic
outputs.master=155,155
outputs.master.mute=off
outputs.master.slaves=dac-0:1,dac-2:3
record.volume=126,126
record.volume.mute=off
record.volume.slaves=adc-0:1,adc-2:3,adc-4:5


I am not sure which settings must be changed to record with the internal 
microphone.  When i start aucat, I can't hear anything. 

Thanks for your help. 



What exactly is sigtramp?

2015-01-14 Thread Stefan Berger
hello, 

at [1], I read something about 'Sigtramp separation' within 
the W^X transition.   I only know that this sigtramp-page (?) is 
used to jump back into the kernel when a signal arrives.  

My question is, what exactly is this signal trampoline?  

Why do I need it?  

Why was it on the Stack (first page of the virtual memory)?  

And why must it be executable /  what does the code?  

Thank you for your help. 


[1] http://www.openbsd.org/papers/ru13-deraadt/mgp00012.html



Re: OpenBSD 5.6 pre-orders in Germany possible

2014-09-27 Thread Stefan Berger
On Sat, Sep 27, 2014 at 07:30:45AM +0100, OpenBSD Europe wrote:
  Hi folks,
 
  I just noticed that in Germany Lehmanns (see OpenBSD's order-site)
  already accepts pre-orders for OpenBSD 5.6-release.
 
  Guess what I just did :-)
 
  My little contribution to the project along with a big
  THANK YOU to the devs!
 
  Cheers,
  STEFAN
 
 
 Please don't do this and cancel your order. Things will become obvious on
 Monday :)

i'd like to buy the 5.6 version on CD, too.  But which shops (in Germany) 
are sane and help the project?   I read a mail from Mr De Raadt and he said 
that ixsoft isn't a -- how should I say that -- proper shop, too.  

I appreciate your work and try to help (at least, a little bit).  Which shop 
is recommended to be OpenBSD friendly? 



[1] http://marc.info/?l=openbsd-miscm=140803642814873w=2



Re: Has anyone gotten qemu to install a Linux vm on OpenBSD5.5, 64bit?

2014-09-13 Thread Stefan Berger
On Sat, Sep 13, 2014 at 10:18:31PM +1000, Brett Mahar wrote:
 On Fri, 12 Sep 2014 21:15:59 -0400
 Steve Litt sl...@troubleshooters.com wrote:
 
 | Hi all,
 | 
 | Has anyone gotten qemu to install a Linux vm on OpenBSD5.5, 64bit?
 
 Hi Steve,
 
 There's a readme that is installed when you install the qemu package, you 
 should check that out. I had opensuse running a while ago (lots of the other 
 linux distributions would not work). What I did was:
 
 After creating .img file:
 
 $ ulimit -d 200
 
 $ qemu -m 1300 -no-acpi -monitor stdio -no-fd-bootchk -hda virtual.img -cdrom 
 openSUSE-11.4-GNOME-LiveCD-i686.iso -boot d
 
 Then when you get to the installer screen, select f4[kernel version]safe 
 mode; F3[graphics]vesa
 
 Once installed and virtual disk compressed, normal booting works with:
 
 $ qemu -m 1300 -no-acpi -no-fd-bootchk -hda virtual.img
 
 then selecting failsafe mode to boot into a console (no x11) desktop. If you 
 want a graphical desktop
 environment, choose failsafe mode and then delete nomodeset x11 failsafe 
 from the boot arguments.
 
 This would need to be adjusted for newer qemu, command line options I used 
 recently with pcbsd were:
 
 $ qemu-system-x86_64 -m 256 -cdrom 
 PCBSD10.0.2-RELEASE-06-20-2014-x64-DVD-USB.iso pcbsd-qemu.img 
 
 launch:
 $ qemu-system-x86_64 -m 1200 -display gtk -vga std -sdl -hda pcbsd-qemu.img
 
 Brett.

Thanks a lot.  I will try that too because I had problems with 
Linux distributions too.  Maybe, this 'Damn Small Linux' thing might be 
usable... .  Gentoo booted, too (the install iso), but I don't want to 
waste my entire life compiling linux stuff inside qemu. 

However, I got MINIX up and running within qemu (the system compiles 
inside the qemu box without any problems) and of course, OpenBSD runs 
inside qemu, too.  



Re: The rant about browsers

2014-08-23 Thread Stefan Berger
On Sat, Aug 23, 2014 at 08:15:23PM +0200, Peter J. Philipp wrote:
 However I have a different problem.  I use firefox over ssh to another
 user on the same system.  I do this because I don't want a would-be
 attacker to get to sensitive files such as my ssh keys.  Now this setup
 runs pretty good, except at one point and perhaps someone can look into
 this for me.  When I control-f for searching a website and enter 3
 characters the browser crashes.  However it doesn't happen always and it
 never happens when I run firefox as my own user.

works for me.  

 Another drawback to my using another user to sandbox firefox is that I
 cannot copy-paste from browser to another window, not sure if that is
 related.

just select the text, and paste it with the third mouse button 
(usually the mouse wheel)

 Anyhow for memory I'm set with 32 GB so that's not the problem in this
 system.

32 GB RAM?  Not bad... 



berger s.