Re: linux port of systrace

[Илья Аржанников]

On May 14, 2014, at 10:49, Philip Guenther  wrote:

> On Tue, May 13, 2014 at 8:06 AM, Илья Аржанников
 wrote:
> I am trying to use linux port systrace. And I found the problem. When I run
under systrace (it does not matter with -A or -a (actually it never came till
-a)) something that use vfork systrace and children processes hangup. I saw in
sources that linux port uses ptrace as backend because it's not a native
systrace subsystem. And linux systrace try to rewrite vfork system call on
sys_clone, but it give nothing. With fork everything is ok, because fork is
wrap around clone syscall and systrace just add one more flag to call it.
>
> Has anyone experience this problem?
>
> This isn't too surprising: vfork() is defined as stopping the parent process
until the child exits or execs, but ptrace() works by reparenting the target
process, so the child that you're supposed to block for isn't yours anymore.
Rewriting vfork() into a clone() call isn't any easier: Linux follows the
original semantics which preserve the the exact stack contents and registers.
That's why on some Linux archs vfork() is a syscall and not just a wrapper of
clone(): clone() has so many args that it requires stack manipulations that
vfork() can't do.
>
> Stepping back, I would suggest you look at what native control subsystems
are offered by Linux that might do what you need to do.  For example, can your
problem be solved with SELinux?
>
> (systrace is only used in the OpenBSD base for some ports building work and
for sshd privsep sandboxing... but as soon as I or someone else comes up with
a simpler replacement for it for those functions, it'll be removed.)
>
>
> Philip Guenther
>
Hi. I fixed hangup on vfork syscall. But now when child process that was
vforked calls exec* function ptrace return user_regs_struct (after call
ptrace(PTRACE_GETREGS, ...)) with rdi rsi rdx rcx r8 r9 register equal to 0
(zero). How it could be?

Re: Lenovo Y510P status on OpenBSD amd64 -current

[bodie]

On 16.05.2014 22:35, Ted Unangst wrote:

On Fri, May 16, 2014 at 18:45, bodie wrote:

preparations I'm most interested in that HDD. It's hybrid model made 
out
of 2 disks. OpenBSD doesn't have access to that SSD cache part? And 
if
it has or will have what will be best partition setup for such 
combo?


As far as I know, it's just an msata ssd, right? the bios may be
configured to hide it in cache mode, but if you disable that it 
should

show up as a second disk.



It's described here 
http://www.seagate.com/www-content/product-content/seagate-laptop-fam/laptop-sshd/en-us/docs/100716627d.pdf
But anyway nothing in BIOS related to cache/SSD part. BIOS is pretty 
simple and for disk there's only either AHCI mode or Legacy for IDE and 
that's all related to the disk.

Re: OT: Does OpenBSD run on SuperMicro MicroCloud models, and may be on 5037MC-H12TRF

[Daniel Ouellet]

Thanks for the feedback on and off list guys.

Chris.

Yes I have a few Super MicroServer and the similar one I do expect them
to work. Still as the price wasn't cheap and the money come from my own
pockets, it's always nice to make sure. I don't mind trying and spend a
few hundreds at time, but this range. well... I am a bit more careful. (:>

For Graphics acceleration, I could careless really. Would be nice to
work, but here, it will not stop me for sure. Thanks for that info.

Stuart.

Same as above. The one I didn't want what the Atome SoC one, as so far
it's not working well, but that's why I asked. I have the others however
and I am happy with them.

And for Video, you are 100% right. I only care about ssh remote access
to it. The only time I use Video on these box is when I buy them to test
and after that, there is never a monitor connected to them ever! No
Video and better console would makes me happier anyway. (:>

As for the AMD one, I was considering it for the XOR feature, but I
wasn't sure to go that AMD yet. Thanks for the update on it I appreciate it!

Maxim

Thanks for the feedback as well. Good to know the C2758 works. The one I
refer at that was said to not work yet anyway was the C1200 series SoC.
As I knew the C1200 wasn't working, well a few months ago anyway, I
thought to make sure the new C2750 was as this unit is one package, you
can't get it not fully loaded and that's not cheap. So, it's always good
to make sure. (:>

Sebastian.

That clarify the info I had on the C1200 SoC not working. Thank you!
Looks like it wasn't the SoC C1200 after all but the chipset for the
drives. I had look at both the EP and EF model, and simply pass on them
after feedback I got. So, still the same situation. Good to know.

Thank you all for the feedback on and off list, it was very much
appreciated!!!

I guess now I will need to cut my beer budget for a while to get one of
these. (:>

Daniel

Re: Lenovo Y510P status on OpenBSD amd64 -current

[Ted Unangst]

On Fri, May 16, 2014 at 18:45, bodie wrote:

> preparations I'm most interested in that HDD. It's hybrid model made out 
> of 2 disks. OpenBSD doesn't have access to that SSD cache part? And if 
> it has or will have what will be best partition setup for such combo?

As far as I know, it's just an msata ssd, right? the bios may be
configured to hide it in cache mode, but if you disable that it should
show up as a second disk.

Re: Lenovo Y510P status on OpenBSD amd64 -current

[bodie]

On 16.05.2014 22:04, Mihai Popescu wrote:

It's hybrid model made out
of 2 disks. OpenBSD doesn't have access to that SSD cache part? And 
if
it has or will have what will be best partition setup for such 
combo?


From what I see on internet about this hybrid, the SSD part is 
managed

by internal firmware and acts as a cache. I doubt you can access it
separately.


Intel Rapid Storage software in Windows doesn't show it either. That 
cache is "visible" only in Device manager -> Disk -> Properties -> 
Policies (Write caching policy). So it will mean that any BSD can see 
only that ~1TB part of regular SATA device without any chance to have 
some influence on SSD cache part and disk firmware will not use it at 
all or use it no matter what if it was enabled before in Windows? I 
know, more question for vendor of that disk, but maybe someone with deep 
knowledge of such devices can sched some light on this. Will be nice to 
have it for /tmp, /var/tmp or whatever.

Re: Lenovo Y510P status on OpenBSD amd64 -current

[Mihai Popescu]

> It's hybrid model made out
> of 2 disks. OpenBSD doesn't have access to that SSD cache part? And if
> it has or will have what will be best partition setup for such combo?

>From what I see on internet about this hybrid, the SSD part is managed
by internal firmware and acts as a cache. I doubt you can access it
separately.

Re: Lenovo Y510P status on OpenBSD amd64 -current

[bodie]

On 16.05.2014 17:55, Miod Vallat wrote:

6) Wired LAN not supported


"Attansic Technology AR8171" rev 0x10 at pci1 dev 0 function 0 not 
configured


There is currently no support for this chip in OpenBSD. If you're
willing to tinker, you could try and port the FreeBSD driver 
available

here:
  https://github.com/markjdb/alx-freebsd
which is supposed to work (it has been done by a FreeBSD developer, 
but
for some reason I'm not aware of, it does not seem to have been 
commited

to their main repository).

Miod


Can leave some time without wired LAN just fine, however for proper 
preparations I'm most interested in that HDD. It's hybrid model made out 
of 2 disks. OpenBSD doesn't have access to that SSD cache part? And if 
it has or will have what will be best partition setup for such combo?

Re: Lenovo Y510P status on OpenBSD amd64 -current

[Miod Vallat]

> 6) Wired LAN not supported

> "Attansic Technology AR8171" rev 0x10 at pci1 dev 0 function 0 not configured

There is currently no support for this chip in OpenBSD. If you're
willing to tinker, you could try and port the FreeBSD driver available
here:
  https://github.com/markjdb/alx-freebsd
which is supposed to work (it has been done by a FreeBSD developer, but
for some reason I'm not aware of, it does not seem to have been commited
to their main repository).

Miod

Re: interested in this patch?

[Peter J. Philipp]

On 05/16/14 17:35, Stuart Henderson wrote:
> On 2014-05-16, Peter J. Philipp  wrote:
>> Hi,
>>
>> While working on putting notify (RFC 1996) support into my DNS server, I
>> came across this puzzling output (with OpenBSD's tcpdump):
>>
>> 10:14:48.292789 192.168.34.5.26837 > 192.168.35.1.53: [udp sum ok] 48054
>> notify [b2&3=0x2400] SOA? centroid.eu. (29) (ttl 64, id 4395, len 57)
>>
>> Notice the b2&3=0x2400.  It struck me as odd so I googled and found a
>> patch for tcpdump that perhaps OpenBSD is interested in?
>>
>> http://marc.info/?l=tcpdump-patches&m=98115734907026&w=2
>>
>> Regards,
>>
>> -peter
>>
> 
> The equivalent for our tree would be this (tested on BE and LE).
> Any OKs? (I note that tcpdump.org haven't taken it, though that doesn't
> mean anything in itself)..
> 


I tested.  The output now looks like this:


# tcpdump -v -n -i em0 -s 1500 -X port 53 and host 192.168.35.1
tcpdump: listening on em0, link-type EN10MB
tcpdump: WARNING: compensating for unaligned libpcap packets
17:54:48.388854 192.168.34.5.5362 > 192.168.35.1.53: [udp sum ok] 10088
notify SOA? centroid.eu. (29) (ttl 64, id 31235, len 57)

This is just like I had hoped it would do.  Thanks for the work on
porting this patch!


-peter


> Index: nameser.h
> ===
> RCS file: /cvs/src/usr.sbin/tcpdump/nameser.h,v
> retrieving revision 1.6
> diff -u -p -r1.6 nameser.h
> --- nameser.h 4 Nov 2010 17:37:05 -   1.6
> +++ nameser.h 16 May 2014 15:33:12 -
> @@ -82,6 +82,8 @@
>  #if 0
>  #define xxx  0x3 /* 0x3 reserved */
>  #endif
> +#define NS_NOTIFY_OP 0x4 /* notify secondary of SOA change */
> +
>   /* non standard - supports ALLOW_UPDATES stuff from Mike Schwartz */
>  #define UPDATEA  0x9 /* add resource record */
>  #define UPDATED  0xa /* delete a specific resource 
> record */
> Index: print-domain.c
> ===
> RCS file: /cvs/src/usr.sbin/tcpdump/print-domain.c,v
> retrieving revision 1.18
> diff -u -p -r1.18 print-domain.c
> --- print-domain.c4 Nov 2010 17:37:05 -   1.18
> +++ print-domain.c16 May 2014 15:33:12 -
> @@ -663,9 +663,10 @@ ns_print(register const u_char *bp, u_in
>   DNS_RD(np) ? "+" : "",
>   DNS_CD(np) ? "%" : "");
>  
> - /* any weirdness? */
> + /* any weirdness? AA is expected in NOTIFY. */
>   b2 = EXTRACT_16BITS(((u_short *)np)+1);
> - if (b2 & 0x6cf)
> + if ((b2 & 0x6cf) !=
> + (DNS_OPCODE(np) == NS_NOTIFY_OP ? 0x400 : 0))
>   printf(" [b2&3=0x%x]", b2);
>  
>   if (DNS_OPCODE(np) == IQUERY) {

Re: interested in this patch?

[Stuart Henderson]

On 2014-05-16, Peter J. Philipp  wrote:
> Hi,
>
> While working on putting notify (RFC 1996) support into my DNS server, I
> came across this puzzling output (with OpenBSD's tcpdump):
>
> 10:14:48.292789 192.168.34.5.26837 > 192.168.35.1.53: [udp sum ok] 48054
> notify [b2&3=0x2400] SOA? centroid.eu. (29) (ttl 64, id 4395, len 57)
>
> Notice the b2&3=0x2400.  It struck me as odd so I googled and found a
> patch for tcpdump that perhaps OpenBSD is interested in?
>
> http://marc.info/?l=tcpdump-patches&m=98115734907026&w=2
>
> Regards,
>
> -peter
>

The equivalent for our tree would be this (tested on BE and LE).
Any OKs? (I note that tcpdump.org haven't taken it, though that doesn't
mean anything in itself)..

Index: nameser.h
===
RCS file: /cvs/src/usr.sbin/tcpdump/nameser.h,v
retrieving revision 1.6
diff -u -p -r1.6 nameser.h
--- nameser.h   4 Nov 2010 17:37:05 -   1.6
+++ nameser.h   16 May 2014 15:33:12 -
@@ -82,6 +82,8 @@
 #if 0
 #define xxx0x3 /* 0x3 reserved */
 #endif
+#define NS_NOTIFY_OP   0x4 /* notify secondary of SOA change */
+
/* non standard - supports ALLOW_UPDATES stuff from Mike Schwartz */
 #define UPDATEA0x9 /* add resource record */
 #define UPDATED0xa /* delete a specific resource 
record */
Index: print-domain.c
===
RCS file: /cvs/src/usr.sbin/tcpdump/print-domain.c,v
retrieving revision 1.18
diff -u -p -r1.18 print-domain.c
--- print-domain.c  4 Nov 2010 17:37:05 -   1.18
+++ print-domain.c  16 May 2014 15:33:12 -
@@ -663,9 +663,10 @@ ns_print(register const u_char *bp, u_in
DNS_RD(np) ? "+" : "",
DNS_CD(np) ? "%" : "");
 
-   /* any weirdness? */
+   /* any weirdness? AA is expected in NOTIFY. */
b2 = EXTRACT_16BITS(((u_short *)np)+1);
-   if (b2 & 0x6cf)
+   if ((b2 & 0x6cf) !=
+   (DNS_OPCODE(np) == NS_NOTIFY_OP ? 0x400 : 0))
printf(" [b2&3=0x%x]", b2);
 
if (DNS_OPCODE(np) == IQUERY) {

Re: OT: Does OpenBSD run on SuperMicro MicroCloud models, and may be on 5037MC-H12TRF

[Sebastian Benoit]

Daniel Ouellet(dan...@presscom.net) on 2014.05.15 20:51:12 -0400:
> Hi,
> 
> Sorry for the off topic question, but I don't know any other way to find
> out. Google didn't provide much answer on this model yet for OpenBSD.
> 
> Does anyone may had a chance to know or test if that unit can run
> OpenBSD properly yet?
> 
> I have to asked as to get that unit, you can't get only the rack and one
> module to test, but this come as full unit only and configure as it
> maybe good cost >15K up 23K depend on model below. So I would like to
> know before I get one obviously...
> 
> SuperServer 5037MC-H12TRF
> http://www.supermicro.com/products/system/3U/5037/SYS-5037MC-H12TRF.cfm
> 
> I was also looking at these two if the above one wasn't supported. But
> if I remember the Atom SoC one is not working on OpenBSD yet, but I
> could be wrong.

i only know that the 5017A-EF does not work, because of the SATA chip on it
among other things.
 
> SuperServer 5038MA-H24TRF
> http://www.supermicro.com/products/system/3U/5038/SYS-5038MA-H24TRF.cfm
> 
> A+ Server 3012MA-H12TRF
> http://www.supermicro.com/Aplus/system/3U/3012/AS-3012MA-H12TRF.cfm
> 
> Fell free to answer off list as to not pollute this, or on list if
> others are interested to know.
> 
> I would very much appreciate feedback good/bad on any SuperMicro
> MicroCloud model(s) and as well on the management of it if anyone had a
> chance to play with them?
> 
> Many thanks in advance for your time.

Supermicro 5037MC-H8TRF (but i only tested install and ran some tests)
Supermicro 5038ML-H8TRF (in production)

both work, in the 5038ML the AOC-CTG-i2S 10G network card works as well.

Re: 'newer' Qlogic HBA support on amd64

[David Gwynne]

hey pete,

could you try enabling the emc driver too?

cheers,
dlg

On 16 May 2014, at 7:47 pm, Pete Vickers  wrote:

> Hi,
> 
> Sorry for the delay. I finally upgraded the box (very quick and easy process 
> - nice ) and the HBA is now attached by the qle driver. However whilst it 
> 'sees' the SAN disk behind it, it remain unable to talk to it.
> 
> 
> # uname -mrv 
> 5.5 GENERIC.MP#315 amd64
> 
> 
> # dmesg | egrep -i "qle|scsibus1"
> qle0 at pci8 dev 0 function 0 "QLogic ISP2432" rev 0x02: msi
> qle0: bad startup mboxes: 0 0
> qle0: firmware rev 4.0.20, attrs 0x2
> scsibus1 at qle0: 2048 targets, WWPN 50060b66644e, WWNN 50060b66644f
> sd1 at scsibus1 targ 130 lun 0:  SCSI2 0/direct fixed 
> naa.600601601b662700d837603da8efe011
> sd2 at scsibus1 targ 131 lun 0:  SCSI2 0/direct fixed 
> naa.600601601b662700d837603da8efe011
> 
> 
> sd1 & sd2 : Are these duplicates due to redundant paths in SAN fabric ?
> 
> 
> # fdisk sd1 
> fdisk: DIOCGPDINFO: Input/output error
> fdisk: Can't get disk geometry, please use [-chs] to specify.
> 
> 
> 
> # pcidump  -v 19:0:0
> 19:0:0: QLogic ISP2432
>0x: Vendor ID: 1077 Product ID: 2432
>0x0004: Command: 0147 Status: 0010
>0x0008: Class: 0c Subclass: 04 Interface: 00 Revision: 02
>0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 10
>0x0010: BAR io addr: 0x5000/0x0100
>0x0014: BAR mem 64bit addr: 0xfdff/0x4000
>0x001c: BAR empty ()
>0x0020: BAR empty ()
>0x0024: BAR empty ()
>0x0028: Cardbus CIS: 
>0x002c: Subsystem Vendor ID: 103c Product ID: 7040
>0x0030: Expansion ROM Base Address: 
>0x0038: 
>0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00
>0x0044: Capability 0x01: Power Management
>0x004c: Capability 0x10: PCI Express
>Link Speed: 2.5 / 2.5 GT/s Link Width: x4 / x4
>0x0064: Capability 0x05: Message Signaled Interrupts (MSI)
>0x0074: Capability 0x03: Vital Product Data (VPD)
>0x007c: Capability 0x11: Extended Message Signaled Interrupts (MSI-X)
> 
> e.g. http://filedownloads.qlogic.com/files/datasheets/32359/83432-580-00D.pdf
> 
> 
> 
> (let me know if you want list spam with full dmesg).
> 
> 
> /Pete
> 
> 
> On 13. mars 2014, at 18:48, Ted Unangst  wrote:
> 
>> On Thu, Mar 13, 2014 at 18:44, Pete Vickers wrote:
>>> Hi,
>>> I have a an amd64 server (HP DL360 G5), with an Qlogic FC HBA in it. It
>>> appears to be based on the ISP2400 series, and isp man page says the
>>> driver only supports up to the ISP2300 series. However the driver appears
>>> to try to attach the device irrespective (and fail). Does anyone know how
>>> different the 2400 series are, or if there is work in progress to support
>>> them ?
>> 
>> In 5.5 and later, that's supported by the qle driver. The isp driver
>> is being broken into parts (qlw, qla, qle) depending on generation.
>> I'd try a snapshot. It should work better. And if it doesn't work,
>> we'd like to know.

Re: Lenovo Y510P status on OpenBSD amd64 -current

[David Coppa]

On Fri, May 16, 2014 at 3:11 PM, Mike Jackson  wrote:
> Quoting bodie :
>
>> 6) Wired LAN not supported
>>
>> Any hints for points 6 and 7?
>
>
>
> I read through your dmesg twice but didn't see anything related to wired
> lan. OTOH, my eyes don't always work so well when they're dry after having
> been lasered. What is the name of your wired LAN device?

"Attansic Technology AR8171" rev 0x10 at pci1 dev 0 function 0 not configured

Re: 'newer' Qlogic HBA support on amd64

[Johan Huldtgren]

Quoting Pete Vickers :


# dmesg | egrep -i "qle|scsibus1"
qle0 at pci8 dev 0 function 0 "QLogic ISP2432" rev 0x02: msi
qle0: bad startup mboxes: 0 0
qle0: firmware rev 4.0.20, attrs 0x2
scsibus1 at qle0: 2048 targets, WWPN 50060b66644e, WWNN 50060b66644f
sd1 at scsibus1 targ 130 lun 0:  SCSI2 0/direct  
fixed naa.600601601b662700d837603da8efe011
sd2 at scsibus1 targ 131 lun 0:  SCSI2 0/direct  
fixed naa.600601601b662700d837603da8efe011



sd1 & sd2 : Are these duplicates due to redundant paths in SAN fabric ?


yes, the naa.60... number is the uid of the volume, same uid, same volume. an
easy way to confirm is if you assign another volume from your frame (looks
like a CX or VNX) you should get two new devices with different uids.

.jh

Re: Lenovo Y510P status on OpenBSD amd64 -current

[Mike Jackson]

Quoting bodie :


6) Wired LAN not supported

Any hints for points 6 and 7?



I read through your dmesg twice but didn't see anything related to  
wired lan. OTOH, my eyes don't always work so well when they're dry  
after having been lasered. What is the name of your wired LAN device?


And that inteldrm, something else...


-mike

Re: Where is my memory?

[Tristan PILAT]

2014-05-16 11:45 GMT+02:00 Stuart Henderson :

> On 2014-05-15, Stuart Henderson  wrote:
> > On 2014-05-15, Tristan PILAT  wrote:
> >> So apps are using around 200M of RAM but where is the rest? vmstat is
> not
> >> very useful for me, or maybe i'm not able to understand it.
> >
> > The information might be in here but the line-wrapping makes it
> unreadable.
> > It would also be useful to include netstat -m. Can you try with a newer
> > OpenBSD version? 5.2 is a bit old ..
> >
> >
>
> A reader was nice enough to cut through the mangled formatting
> and point this out off-list:
>
> NameSize Requests FailInUse Pgreq Pgrel Npage Hiwat Minpg
> Maxpg Idle
> pfruleitempl  24 2224044085 933 50224416 303139 572 302567 302567   0
> 80
>
> Perhaps it could be the bug fixed by this commit:
>
> $ acvs log -r1.841 -N sys/net/pf.c
>
> RCS file: /cvs/src/sys/net/pf.c,v
> Working file: sys/net/pf.c
> head: 1.877
> branch:
> locks: strict
> access list:
> keyword substitution: kv
> total revisions: 936;   selected revisions: 1
> description:
> 
> revision 1.841
> date: 2013/10/09 09:32:01;  author: camield;  state: Exp;  lines: +7 -8;
> Don't leak ruleitems from match rules when hitting a per-rule max state
> limit.
>
> ok henning
>
> =
>

Ok, thanks for your reply. Will try to manage to upgrade as soon as
possible.

Lenovo Y510P status on OpenBSD amd64 -current

[bodie]

Hi all,

so finally get to further testing and collecting outputs.

1) Can see 8 CPUs on bsd.mp even as some issues reported in dmesg
2) X is working despite error for vga in dmesg
3) audio is working despite error in dmesg
4) Touchpad is working
5) Descrete (Nvidia and Intel) or UMA only both work on Intel HD4600, 
option with 2x Nvidia not obviously tested as it doesn't make sense for 
OpenBSD

6) Wired LAN not supported
7) Can't see second "part" of the disks. This disk is hybrid classic 
and 16GB SSD cache. About 2 weeks back it was visible as sd0 and sd1 on 
amd64 snapshot. Now I can see only that bigger regular SATA disk part


Any hints for points 6 and 7?

$ cat glxinfo.txt
direct rendering: Yes
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
GL_NV_conditional_render, GL_AMD_draw_buffers_blend,
$

$ cat mixerctl_out.txt
inputs.dac-2:3=126,126
inputs.dac-0:1=126,126
record.adc-0:1_mute=off
record.adc-0:1=124,124
record.adc-4:5_mute=off
record.adc-4:5=124,124
inputs.mix_source=mic2,beep
inputs.mix_mic2=120,120
inputs.mix_beep=120,120
inputs.mix2_source=dac-2:3,mix
inputs.mix3_source=dac-0:1,mix
record.adc-2:3_source=mic
record.adc-2:3_mute=off
record.adc-2:3=124,124
inputs.mic=85,85
outputs.spkr_source=mix2
outputs.spkr_mute=off
outputs.spkr_eapd=on
inputs.mic2=85,85
outputs.mic2_dir=input-vr80
outputs.SPDIF_source=dig-dac-0:1
outputs.hp_source=mix3
outputs.hp_mute=off
outputs.hp_boost=off
record.adc-4:5_source=mic2,beep,mix
record.adc-0:1_source=mic2,beep,mix
outputs.mic2_sense=unplugged
outputs.hp_sense=unplugged
outputs.spkr_muters=hp
outputs.master=126,126
outputs.master.mute=off
outputs.master.slaves=dac-2:3,dac-0:1,spkr,hp
record.volume=124,124
record.volume.mute=off
record.volume.slaves=adc-0:1,adc-4:5,adc-2:3
outputs.mode=analog
$

$ cat audioctl_out.txt
name=HD-Audio
version=1.0
config=azalia1
encodings=slinear_le:16:2:1,slinear_le:20:4:1,slinear_le:24:4:1
properties=full_duplex,independent
full_duplex=0
fullduplex=0
blocksize=9600
hiwat=6
lowat=4
output_muted=0
monitor_gain=0
mode=
play.rate=48000
play.channels=2
play.precision=16
play.bps=2
play.msb=1
play.encoding=slinear_le
play.gain=126
play.balance=32
play.port=0x0
play.avail_ports=0x0
play.seek=0
play.samples=0
play.eof=0
play.pause=0
play.error=0
play.waiting=0
play.open=0
play.active=0
play.buffer_size=65536
play.block_size=9600
play.errors=0
record.rate=48000
record.channels=2
record.precision=16
record.bps=2
record.msb=1
record.encoding=slinear_le
record.gain=124
record.balance=32
record.port=0x0
record.avail_ports=0x0
record.seek=0
record.samples=0
record.eof=0
record.pause=0
record.error=0
record.waiting=0
record.open=0
record.active=0
record.buffer_size=65536
record.block_size=9600
record.errors=0
$

$ grep EE Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   251.773] Initializing built-in extension MIT-SCREEN-SAVER
$ grep WW Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[   251.822] (WW) Falling back to old probe method for vesa
$

dmesg with bsd.mp and UMA only

OpenBSD 5.5-current (GENERIC.MP) #131: Thu May 15 16:28:00 MDT 2014
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 80
real mem = 17075793920 (16284MB)
avail mem = 16612474880 (15842MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe6e70 (69 entries)
bios0: vendor LENOVO version "74CN44WW(V3.05)" date 09/18/2013
bios0: LENOVO 20217
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP SLIC UEFI FPDT MSDM ASF! HPET APIC MCFG SSDT 
BOOT ASPT DBGP SSDT SSDT SSDT
acpi0: wakeup devices P0P1(S4) EHC1(S3) EHC2(S3) XHC_(S3) RP01(S4) 
RP02(S4) RP03(S4) RP04(S4) RP06(S4) RP07(S4) RP08(S4) PEG0(S4) PEG1(S4) 
LID0(S3)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz, 2195.27 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A

ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4, IBE
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz, 2194.92 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,A

ES,XSAVE,AVX,F16C,RDRAND,NXE,LONG,LAHF,ABM,PE

interested in this patch?

[Peter J. Philipp]

Hi,

While working on putting notify (RFC 1996) support into my DNS server, I
came across this puzzling output (with OpenBSD's tcpdump):

10:14:48.292789 192.168.34.5.26837 > 192.168.35.1.53: [udp sum ok] 48054
notify [b2&3=0x2400] SOA? centroid.eu. (29) (ttl 64, id 4395, len 57)

Notice the b2&3=0x2400.  It struck me as odd so I googled and found a
patch for tcpdump that perhaps OpenBSD is interested in?

http://marc.info/?l=tcpdump-patches&m=98115734907026&w=2

Regards,

-peter

Re: OT: Does OpenBSD run on SuperMicro MicroCloud models, and may be on 5037MC-H12TRF

[Maxim Khitrov]

On Thu, May 15, 2014 at 8:51 PM, Daniel Ouellet  wrote:
> I was also looking at these two if the above one wasn't supported. But
> if I remember the Atom SoC one is not working on OpenBSD yet, but I
> could be wrong.
>
> SuperServer 5038MA-H24TRF
> http://www.supermicro.com/products/system/3U/5038/SYS-5038MA-H24TRF.cfm

I have the Supermicro A1SRi-2758F motherboard (Atom C2758 Rangeley).
No issues running OpenBSD 5.5 amd64.

Re: OT: Does OpenBSD run on SuperMicro MicroCloud models, and may be on 5037MC-H12TRF

[Stuart Henderson]

There are very similar systems in standard form factor (micro atx for the
AMD board, mini itx and micro atx for the avoton atom board) so if you
wanted to see if the basic system is likely to work, you could buy one
of those as a one-off.

>> SuperServer 5038MA-H24TRF
>> http://www.supermicro.com/products/system/3U/5038/SYS-5038MA-H24TRF.cfm
>
> I think this stuff is supported now (except for the odd server graphics
> chip having accelerated support in X11). At least the i350 and i354 are
> working now.

I can't speak for the AST2400, but the AST2000 (should be a pretty similar
graphics core) works OK in X for 2d, but no 3d acceleration (in the chipset;
not just missing driver support).

But obviously this simple server-centric video adapter (integrated with
the BMC) is not something you would use if video was a priority ;)

Switching VT twice (ctrl-alt-f1 ctrl-alt-f2) or starting and exiting X
changes the console background to red. Doesn't bother me but if anyone
would like me to try and diffs on it, please send them my way in the
next couple of days while I still have the machine!

>> A+ Server 3012MA-H12TRF
>> http://www.supermicro.com/Aplus/system/3U/3012/AS-3012MA-H12TRF.cfm

I can't say I have had particularly good success with previous (albeit
much older) Supermicro AMD systems. Once I got them working they have
been OK but it was a bit of a struggle getting there.

Re: 'newer' Qlogic HBA support on amd64

[Pete Vickers]

Hi,

Sorry for the delay. I finally upgraded the box (very quick and easy process - 
nice ) and the HBA is now attached by the qle driver. However whilst it 'sees' 
the SAN disk behind it, it remain unable to talk to it.
 

# uname -mrv 
5.5 GENERIC.MP#315 amd64


# dmesg | egrep -i "qle|scsibus1"
qle0 at pci8 dev 0 function 0 "QLogic ISP2432" rev 0x02: msi
qle0: bad startup mboxes: 0 0
qle0: firmware rev 4.0.20, attrs 0x2
scsibus1 at qle0: 2048 targets, WWPN 50060b66644e, WWNN 50060b66644f
sd1 at scsibus1 targ 130 lun 0:  SCSI2 0/direct fixed 
naa.600601601b662700d837603da8efe011
sd2 at scsibus1 targ 131 lun 0:  SCSI2 0/direct fixed 
naa.600601601b662700d837603da8efe011


sd1 & sd2 : Are these duplicates due to redundant paths in SAN fabric ?


# fdisk sd1 
fdisk: DIOCGPDINFO: Input/output error
fdisk: Can't get disk geometry, please use [-chs] to specify.



# pcidump  -v 19:0:0
 19:0:0: QLogic ISP2432
0x: Vendor ID: 1077 Product ID: 2432
0x0004: Command: 0147 Status: 0010
0x0008: Class: 0c Subclass: 04 Interface: 00 Revision: 02
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 10
0x0010: BAR io addr: 0x5000/0x0100
0x0014: BAR mem 64bit addr: 0xfdff/0x4000
0x001c: BAR empty ()
0x0020: BAR empty ()
0x0024: BAR empty ()
0x0028: Cardbus CIS: 
0x002c: Subsystem Vendor ID: 103c Product ID: 7040
0x0030: Expansion ROM Base Address: 
0x0038: 
0x003c: Interrupt Pin: 01 Line: 07 Min Gnt: 00 Max Lat: 00
0x0044: Capability 0x01: Power Management
0x004c: Capability 0x10: PCI Express
Link Speed: 2.5 / 2.5 GT/s Link Width: x4 / x4
0x0064: Capability 0x05: Message Signaled Interrupts (MSI)
0x0074: Capability 0x03: Vital Product Data (VPD)
0x007c: Capability 0x11: Extended Message Signaled Interrupts (MSI-X)

e.g. http://filedownloads.qlogic.com/files/datasheets/32359/83432-580-00D.pdf



(let me know if you want list spam with full dmesg).


/Pete


On 13. mars 2014, at 18:48, Ted Unangst  wrote:

> On Thu, Mar 13, 2014 at 18:44, Pete Vickers wrote:
>> Hi,
>> I have a an amd64 server (HP DL360 G5), with an Qlogic FC HBA in it. It
>> appears to be based on the ISP2400 series, and isp man page says the
>> driver only supports up to the ISP2300 series. However the driver appears
>> to try to attach the device irrespective (and fail). Does anyone know how
>> different the 2400 series are, or if there is work in progress to support
>> them ?
> 
> In 5.5 and later, that's supported by the qle driver. The isp driver
> is being broken into parts (qlw, qla, qle) depending on generation.
> I'd try a snapshot. It should work better. And if it doesn't work,
> we'd like to know.

Re: Where is my memory?

[Stuart Henderson]

On 2014-05-15, Stuart Henderson  wrote:
> On 2014-05-15, Tristan PILAT  wrote:
>> So apps are using around 200M of RAM but where is the rest? vmstat is not
>> very useful for me, or maybe i'm not able to understand it.
>
> The information might be in here but the line-wrapping makes it unreadable.
> It would also be useful to include netstat -m. Can you try with a newer
> OpenBSD version? 5.2 is a bit old ..
>
>

A reader was nice enough to cut through the mangled formatting
and point this out off-list:

NameSize Requests FailInUse Pgreq Pgrel Npage Hiwat Minpg Maxpg Idle
pfruleitempl  24 2224044085 933 50224416 303139 572 302567 302567   0 80

Perhaps it could be the bug fixed by this commit:

$ acvs log -r1.841 -N sys/net/pf.c  

RCS file: /cvs/src/sys/net/pf.c,v
Working file: sys/net/pf.c
head: 1.877
branch:
locks: strict
access list:
keyword substitution: kv
total revisions: 936;   selected revisions: 1
description:

revision 1.841
date: 2013/10/09 09:32:01;  author: camield;  state: Exp;  lines: +7 -8;
Don't leak ruleitems from match rules when hitting a per-rule max state limit.

ok henning
=