Re: Possible regression on dhclient (current)

2012-11-14 Thread Kenneth R Westerback
On Tue, Nov 13, 2012 at 12:01:31AM +0200, Ville Valkonen wrote:
 Hello all,
 
 I was surfing on a Web when suddenly all traffic stopped. Closer examination
 revealed Too many open files failure with the dhclient. Since there have 
 been

You are not sufficiently current. That should have been fixed a couple of
days ago.

 Ken

 improvements in the dhclient lately, could this be related?
 
 Tried to do pkill -TERM dhclient  sudo dhclient trunk0 but no cigar. Any
 hints what to try the next time if this occurs? Uptime was 3 days if it 
 happens
 to matter. I'm also testing Brain Fuck Scheduler patch since it makes videos
 playable. Yes, I can rule it out by running GENERIC if necessary.
 
 Complete dmesg at the bottom of this message.
 
 But now, here's some information:
 $ dmesg |tail -100
 ...
 arpresolve: 192.168.50.101: route without link local address
 arpresolve: 192.168.50.101: route without link local address
 arpresolve: 192.168.50.101: route without link local address
 arpresolve: 192.168.50.101: route without link local address
 arpresolve: 192.168.50.101: route without link local address
 ...
 
 /var/log/daemon:
 Nov 12 23:08:38  dhclient[9627]: DHCPDISCOVER on trunk0 to
 255.255.255.255 port 67 interval 3
 Nov 12 23:08:38  dhclient[9627]: DHCPOFFER from 192.168.50.101
 (00:30:18:a4:f8:e3)
 Nov 12 23:08:38  dhclient[9627]: DHCPREQUEST on trunk0 to
 255.255.255.255 port 67
 Nov 12 23:08:38  dhclient[9627]: DHCPACK from 192.168.50.101 
 (00:30:18:a4:f8:e3)
 Nov 12 23:08:38  dhclient[7427]: socket open failed: Too many open files
 Nov 12 23:08:38  dhclient[9627]: bound to 192.168.50.102 -- renewal in
 300 seconds.
 Nov 12 23:08:38  dhclient[9627]: DHCPDISCOVER on trunk0 to
 255.255.255.255 port 67 interval 3
 Nov 12 23:08:38  dhclient[9627]: DHCPOFFER from 192.168.50.101
 (00:30:18:a4:f8:e3)
 Nov 12 23:08:38  dhclient[9627]: DHCPREQUEST on trunk0 to
 255.255.255.255 port 67
 Nov 12 23:08:38  dhclient[9627]: DHCPACK from 192.168.50.101 
 (00:30:18:a4:f8:e3)
 Nov 12 23:08:38  dhclient[7427]: socket open failed: Too many open files
 Nov 12 23:08:38  dhclient[9627]: bound to 192.168.50.102 -- renewal in
 300 seconds.
 
 /var/log/messages
 Nov 12 23:11:59  /bsd: arpresolve: 192.168.50.101: route without link
 local address
 Nov 12 23:12:21  /bsd: arpresolve: 192.168.50.101: route without link
 local address
 Nov 12 23:14:58  last message repeated 15 times
 Nov 12 23:22:22  last message repeated 32 times
 Nov 12 23:22:24  dhclient[9276]: SIOCDIFADDR failed (192.168.50.102):
 Can't assign requested address
 Nov 12 23:22:24  dhclient[9276]: SIOCDIFADDR failed (192.168.50.102):
 Can't assign requested address
 Nov 12 23:22:27  /bsd: arpresolve: 192.168.50.101: route without link
 local address
 Nov 12 23:23:04  last message repeated 5 times
 
 $ ulimit -a
 time(cpu-seconds)unlimited
 file(blocks) unlimited
 coredump(blocks) unlimited
 data(kbytes) 716800
 stack(kbytes)4096
 lockedmem(kbytes)1298308
 memory(kbytes)   3881796
 nofiles(descriptors) 500
 processes128
 
 NOTICE: Closed Chromium since it had several descriptors opened. After that
 fstat |wc -l   showed ~400. Tried to restart dhclient again but with no luck.
 
 
 $ route -n show # (not using inet6)
 Routing tables
 
 Internet:
 DestinationGatewayFlags   Refs  Use   Mtu  Prio Iface
 default192.168.50.101 UGS4  192 - 8 trunk0
 127/8  127.0.0.1  UGRS   00 33152 8 lo0
 127.0.0.1  127.0.0.1  UH 2 2935 33152 4 lo0
 192.168.50/24  link#5 UC 10 - 4 trunk0
 192.168.50.101 00:30:18:a4:f8:e3  UHLc   0   55 - 4 trunk0
 192.168.50.102 127.0.0.1  UG 00 3315256 lo0
 224/4  127.0.0.1  URS00 33152 8 lo0
 
 
 OpenBSD 5.2-current (GENERIC.MP) #0: Fri Nov  9 15:19:24 EET 2012
 weezel@:/usr/src/sys/arch/amd64/compile/GENERIC.MP
 real mem = 4121640960 (3930MB)
 avail mem = 3989434368 (3804MB)
 mainbus0 at root
 bios0 at mainbus0: SMBIOS rev. 2.5 @ 0xe0010 (44 entries)
 bios0: vendor LENOVO version 6JET93WW (1.51 ) date 03/26/2012
 bios0: LENOVO 284756G
 acpi0 at bios0: rev 4
 acpi0: sleep states S0 S3 S4 S5
 acpi0: tables DSDT FACP HPET MCFG APIC BOOT SLIC SSDT SSDT SSDT
 acpi0: wakeup devices P0P2(S4) P0P1(S4) USB0(S3) USB1(S3) USB2(S3)
 USBR(S3) EHC1(S3) USB3(S3) USB4(S3) USB5(S3) EHC2(S3) HDEF(S4)
 PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4)
 RP04(S4) PXSX(S4) RP05(S4) RP06(S4) BLAN(S4) LID_(S3) SLPB(S3)
 acpitimer0 at acpi0: 3579545 Hz, 24 bits
 acpihpet0 at acpi0: 14318179 Hz
 acpimcfg0 at acpi0 addr 0xe000, bus 0-255
 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
 cpu0 at mainbus0: apid 0 (boot processor)
 cpu0: Intel(R) Core(TM)2 Duo CPU T5870 @ 2.00GHz, 1995.34 MHz
 cpu0: 
 

Re: Noppoo Mini Choc 84 USB keyboard can not work correctly on OpenBSD 5.2 (loongson)

2012-11-14 Thread yunplusplus
After the Noppoo keyboard plugged in, usbdevs -dv shows:

Controller /dev/usb0:
addr 1: high speed, self powered, config 1, EHCI root hub(0x), NEC(0x1033), 
rev 1.00
  uhub0
 port 1 powered
 port 2 powered
 port 3 powered
Controller /dev/usb1:
addr 1: high speed, self powered, config 1, EHCI root hub(0x), AMD(0x1022), 
rev 1.00
  uhub1
 port 1 addr 2: high speed, power 500 mA, config 1, USB2.0-CRW(0x0158), 
Generic(0x0bda), rev 58.87, iSerialNumber 2007111417340
   umass0
 port 2 powered
 port 3 powered
 port 4 addr 4: high speed, power 500 mA, config 1, RTL8187B(0x8189), 
Realtek(0x0bda), rev 2.00, iSerialNumber 00e04c01
   urtw0
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, OHCI root hub(0x), NEC(0x1033), 
rev 1.00
  uhub2
 port 1 powered
 port 2 powered
 port 3 powered
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, OHCI root hub(0x), AMD(0x1022), 
rev 1.00
  uhub3
 port 1 powered
 port 2 addr 2: low speed, power 100 mA, config 1, USB Keyboard(0x0022), vendor 
0x1006(0x1006), rev 1.40
   uhidev0
   uhidev1
 port 3 powered
 port 4 powered

I am upgrading my system form 5.2 to current version.
I hope it will work correctly on the current version.
Thank you for your advise.







At 2012-11-14 14:06:57,Tomas Bodzar tomas.bod...@gmail.com wrote:
On Wed, Nov 14, 2012 at 6:19 AM, yunplusplus yunplusp...@163.com wrote:
 PLATFORM: Yeelong 2F 8089D
 OS:   OpenBSD 5.2 stable
 PROBLEM:   Noppoo Mini Choc 84 USB keyboard do not work correctly on my 
 system.
  For exampIe, when I type Enter, but get 5 displayed 
 on the screen.


 When I plug in my Noppoo Mini Choc 84 USB keyboard, the dmesg is:
 ukbd1 detached
 uhidev1 detached
 uhidev0 at uhub3 port 2 configuration 1 interface 0 vendor 0x1006 USB 
 Keyboard rev 2.00/1.40 addr 2
 uhidev0: iclass 3/1
 ukbd0 at uhidev0: 64 variable keys, 0 key codes
 wskbd1 at ukbd0 mux 1
 wskbd1: connecting to wsdisplay0
 uhidev1 at uhub3 port 2 configuration 1 interface 1 vendor 0x1006 USB 
 Keyboard rev 2.00/1.40 addr 2
 uhidev1: iclass 3/0, 3 report ids
 uhid0 at uhidev1 reportid 1: input=2, output=0, feature=0
 uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
 ukbd1 at uhidev1 reportid 3: 56 variable keys, 0 key codes
 wskbd2 at ukbd1 mux 1
 wskbd2: connecting to wsdisplay0


 Another Logitech USB keyboard  works well. Its dmesg is:
 uhidev0 at uhub3 port 2 configuration 1 interface 0 Logitech Logitech USB 
 Keyboard rev 1.10/28.00 addr 2
 uhidev0: iclass 3/1
 ukbd0 at uhidev0: 8 variable keys, 6 key codes
 wskbd1 at ukbd0 mux 1
 wskbd1: connecting to wsdisplay0


 It seems that the OS detect two devices when I plugged in my Noppoo Mini 
 Choc 84 USB keyboard.
 By the way, this Noppoo Mini Choc 84 USB keyboard works well on several 
 diffirent linux distributions i ever used.


 Can any one help me?

Can you post output of usbdevs -dv ? Can't see 0x1006 related with
your device in /usr/src/sys/dev/usb , but any chance to try current?



 Thanks.



address conflict

2012-11-14 Thread Jan Stary
On an IBM THinkpad T40, dmesg reports address conflicts
and I am not sure what exactly that means and whether to worry.

The full dmesg and the full output of pcidump -v are below.
Here are the snipets that seem relevant.


 0:31:1: Intel 82801DBM IDE
0x: Vendor ID: 8086 Product ID: 24ca
0x0004: Command: 0005 Status ID: 0280
0x0008: Class: 01 Subclass: 01 Interface: 8a Revision: 01
0x000c: BIST: 00 Header Type: 00 Latency Timer: 00 Cache Line Size: 00
0x0010: BAR io addr: 0x/0x0008
0x0014: BAR io addr: 0x/0x0004
0x0018: BAR io addr: 0x/0x0008
0x001c: BAR io addr: 0x/0x0004
0x0020: BAR io addr: 0x1860/0x0010
0x0024: BAR mem 32bit addr: 0x1000/0x0400
0x0028: Cardbus CIS: 
0x002c: Subsystem Vendor ID: 1014 Product ID: 052d
0x0030: Expansion ROM Base Address: 
0x0038: 
0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00

0:31:1: io address conflict 0x5800/0x8
0:31:1: io address conflict 0x5808/0x4
0:31:1: io address conflict 0x5810/0x8
0:31:1: io address conflict 0x580c/0x4


 2:0:0: TI PCI1520 CardBus
0x: Vendor ID: 104c Product ID: ac55
0x0004: Command: 0107 Status ID: 0210
0x0008: Class: 06 Subclass: 07 Interface: 00 Revision: 01
0x000c: BIST: 00 Header Type: 82 Latency Timer: 40 Cache Line Size: 08
0x0010: Cardbus Control Registers Base Address: c0211000
0x0018: Primary Bus: 2 Cardbus Bus: 3 Subordinate Bus: 5 
Cardbus Latency Timer: b0
0x001c: Memory Base 0: f000
0x0020: Memory Limit 0: 
0x0024: Memory Base 1: f000
0x0028: Memory Limit 1: 
0x002c: I/O Base 0: fffc
0x0030: I/O Limit 0: 
0x0034: I/O Base 1: fffc
0x0038: I/O Limit 1: 
0x003c: Interrupt Pin: 01 Line: 0b Bridge Control: 07c0
0x0040: Subsystem Vendor ID: 1014 Product ID: 0512
0x0044: 16-bit Legacy Mode Base Address: 0001
0x00a0: Capability 0x01: Power Management

 2:0:1: TI PCI1520 CardBus
0x: Vendor ID: 104c Product ID: ac55
0x0004: Command: 0107 Status ID: 0210
0x0008: Class: 06 Subclass: 07 Interface: 00 Revision: 01
0x000c: BIST: 00 Header Type: 82 Latency Timer: 40 Cache Line Size: 08
0x0010: Cardbus Control Registers Base Address: c0212000
0x0018: Primary Bus: 2 Cardbus Bus: 6 Subordinate Bus: 8 
Cardbus Latency Timer: b0
0x001c: Memory Base 0: f000
0x0020: Memory Limit 0: 
0x0024: Memory Base 1: f000
0x0028: Memory Limit 1: 
0x002c: I/O Base 0: fffc
0x0030: I/O Limit 0: 
0x0034: I/O Base 1: fffc
0x0038: I/O Limit 1: 
0x003c: Interrupt Pin: 02 Line: 0b Bridge Control: 07c0
0x0040: Subsystem Vendor ID: 1014 Product ID: 0512
0x0044: 16-bit Legacy Mode Base Address: 0001
0x00a0: Capability 0x01: Power Management

2:0:0: mem address conflict 0xb000/0x1000
2:0:1: mem address conflict 0xb100/0x1000


Can somebody please shed a light on this?

Jan


OpenBSD 5.2-current (GENERIC) #0: Fri Oct 19 10:07:44 CEST 2012
r...@ibm.stare.cz:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel(R) Pentium(R) M processor 1500MHz (GenuineIntel 686-class) 1.50 
GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,TM,PBE,EST,TM2
real mem  = 267317248 (254MB)
avail mem = 251990016 (240MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/18/07, BIOS32 rev. 0 @ 0xfd750, SMBIOS 
rev. 2.33 @ 0xe0010 (61 entries)
bios0: vendor IBM version 1RETDRWW (3.23 ) date 06/18/2007
bios0: IBM 237382G
apm0 at bios0: Power Management spec V1.2
acpi at bios0 function 0x0 not configured
pcibios0 at bios0: rev 2.1 @ 0xfd6e0/0x920
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdea0/272 (15 entries)
pcibios0: PCI Interrupt Router at 000:31:0 (Intel 82371FB ISA rev 0x00)
pcibios0: PCI bus #6 is the last bus
bios0: ROM list: 0xc/0x1 0xd/0x1000 0xd1000/0x1000 0xdc000/0x4000! 
0xe/0x1
cpu0 at mainbus0: (uniprocessor)
cpu0: Enhanced SpeedStep 1496 MHz: speeds: 1500, 1400, 1200, 1000, 800, 600 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
0:31:1: io address conflict 0x5800/0x8
0:31:1: io address conflict 0x5808/0x4
0:31:1: io address conflict 0x5810/0x8
0:31:1: io address conflict 0x580c/0x4
pchb0 at pci0 dev 0 function 0 Intel 82855PM Host rev 0x03
intelagp0 at pchb0
agp0 at intelagp0: aperture at 0xd000, size 0x1000
ppb0 at pci0 dev 1 function 0 Intel 82855PM AGP rev 0x03
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 ATI Radeon Mobility M7 rev 0x00
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)

Re: address conflict

2012-11-14 Thread Jan Stary
On other Thinkpads, this seems to be the case too:
http://article.gmane.org/gmane.os.openbsd.newbies/2234



Re: Noppoo Mini Choc 84 USB keyboard can not work correctly on OpenBSD 5.2 (loongson)

2012-11-14 Thread Tomas Bodzar
On Wed, Nov 14, 2012 at 3:24 PM, yunplusplus yunplusp...@163.com wrote:
 After the Noppoo keyboard plugged in, usbdevs -dv shows:

 Controller /dev/usb0:
 addr 1: high speed, self powered, config 1, EHCI root hub(0x),
 NEC(0x1033), rev 1.00
   uhub0
  port 1 powered
  port 2 powered
  port 3 powered
 Controller /dev/usb1:
 addr 1: high speed, self powered, config 1, EHCI root hub(0x),
 AMD(0x1022), rev 1.00
   uhub1
  port 1 addr 2: high speed, power 500 mA, config 1, USB2.0-CRW(0x0158),
 Generic(0x0bda), rev 58.87, iSerialNumber 2007111417340
umass0
  port 2 powered
  port 3 powered
  port 4 addr 4: high speed, power 500 mA, config 1, RTL8187B(0x8189),
 Realtek(0x0bda), rev 2.00, iSerialNumber 00e04c01
urtw0
 Controller /dev/usb2:
 addr 1: full speed, self powered, config 1, OHCI root hub(0x),
 NEC(0x1033), rev 1.00
   uhub2
  port 1 powered
  port 2 powered
  port 3 powered
 Controller /dev/usb3:
 addr 1: full speed, self powered, config 1, OHCI root hub(0x),
 AMD(0x1022), rev 1.00
   uhub3
  port 1 powered
  port 2 addr 2: low speed, power 100 mA, config 1, USB Keyboard(0x0022),
 vendor 0x1006(0x1006), rev 1.40
uhidev0
uhidev1
  port 3 powered
  port 4 powered

 I am upgrading my system form 5.2 to current version.
 I hope it will work correctly on the current version.
 Thank you for your advise.

However I think you need to do this (you need to do that and test on
current anyway)
http://undeadly.org/cgi?action=articlesid=20080315134047 or
http://undeadly.org/cgi?action=articlesid=20070207152423 because I
can't see your device in /usr/src/sys/dev/usb/usbdevs*






 At 2012-11-14 14:06:57,Tomas Bodzar tomas.bod...@gmail.com wrote:
On Wed, Nov 14, 2012 at 6:19 AM, yunplusplus yunplusp...@163.com wrote:
 PLATFORM: Yeelong 2F 8089D
 OS:   OpenBSD 5.2 stable
 PROBLEM:   Noppoo Mini Choc 84 USB keyboard do not work correctly on my
 system.
  For exampIe, when I type Enter, but get 5
 displayed on the screen.


 When I plug in my Noppoo Mini Choc 84 USB keyboard, the dmesg is:
 ukbd1 detached
 uhidev1 detached
 uhidev0 at uhub3 port 2 configuration 1 interface 0 vendor 0x1006 USB
 Keyboard rev 2.00/1.40 addr 2
 uhidev0: iclass 3/1
 ukbd0 at uhidev0: 64 variable keys, 0 key codes
 wskbd1 at ukbd0 mux 1
 wskbd1: connecting to wsdisplay0
 uhidev1 at uhub3 port 2 configuration 1 interface 1 vendor 0x1006 USB
 Keyboard rev 2.00/1.40 addr 2
 uhidev1: iclass 3/0, 3 report ids
 uhid0 at uhidev1 reportid 1: input=2, output=0, feature=0
 uhid1 at uhidev1 reportid 2: input=1, output=0, feature=0
 ukbd1 at uhidev1 reportid 3: 56 variable keys, 0 key codes
 wskbd2 at ukbd1 mux 1
 wskbd2: connecting to wsdisplay0


 Another Logitech USB keyboard  works well. Its dmesg is:
 uhidev0 at uhub3 port 2 configuration 1 interface 0 Logitech Logitech
 USB Keyboard rev 1.10/28.00 addr 2
 uhidev0: iclass 3/1
 ukbd0 at uhidev0: 8 variable keys, 6 key codes
 wskbd1 at ukbd0 mux 1
 wskbd1: connecting to wsdisplay0


 It seems that the OS detect two devices when I plugged in my Noppoo Mini
 Choc 84 USB keyboard.
 By the way, this Noppoo Mini Choc 84 USB keyboard works well on several
 diffirent linux distributions i ever used.


 Can any one help me?

Can you post output of usbdevs -dv ? Can't see 0x1006 related with
your device in /usr/src/sys/dev/usb , but any chance to try current?



 Thanks.



Re: HP Ethernet 1Gb 4-port 331FLR card supported?

2012-11-14 Thread Stuart Henderson
On 2012-11-14, Sebastian Reitenbach sebas...@l00-bugdead-prods.de wrote:
 Hi,

 we have a HP Proliant Server Gen8, where we want to run OpenBSD on it. 
 The card mentioned has to go into the FlexibleLOM port on the server, 
 therefore
 there is not that much choice of a card.
 As far as I have seen, this card is not listed in any of the drivers, but I 
 found that
 link here:
 http://partnerweb.vmware.com/comp_guide1/detail.php?device_cat=iodevice_id=21446
 which tells me that the card has a BroadCom NetXtreme BCM5719 chipset, and 
 bge(4) at least tells me, that this chipset is supported.

 But to be sure, I thought trying to ask if anyone has such a card in use with 
 OpenBSD?

 thanks,
 Sebastian



BCM5719 is not yet supported, I understand there are problems
getting the phy to work.



Re: mountd needs to reboot to change mapall argument

2012-11-14 Thread Joe Kowalski
On Saturday, November 10, 2012 04:35:33 PM Philip Guenther wrote:
 Hmm, it works for me, using an exports of
 
 /usr/src -mapall=guenther 127.0.0.1
 /usr/obj -mapall=guenther 127.0.0.1
 
 and switching the -mapall on /usr/src from guenther to otheruser,
 pkill -HUP mountd, then testing by creating a file in a mode 777
 directory on the NFS mount from 127.0.0.1.  Various other switches and
 tests show that it doesn't seem to be related to the sorting of the
 directory names.
 
 So: need more data.  Run mountd yourself with the -d option and snag
 the *complete* output from start, making changes to /etc/exports and
 HUP'ing it, etc.
I've been working with Tim on this. 

I set up a new  exports file like yours  above:
# cat /etc/exports  

 
#   $OpenBSD: exports,v 1.2 2002/05/31 08:15:44 pjanzen Exp $
#
# NFS exports Database
# See exports(5) for more information.  Be very careful:  misconfiguration
# of this file can result in your filesystems being readable by the world.
/usr/src -mapall=common 127.0.0.1

Then I setup the nfs servers by manually running the daemons:
nas1#portmap  mountd -d  nfsd -tun4
[1] 13159
[2] 7037
[1] - Done portmap 
nas1#Getting export list.
Got line #  $OpenBSD: exports,v 1.2 2002/05/31 08:15:44 pjanzen Exp $
Got line #
Got line # NFS exports Database
Got line # See exports(5) for more information.  Be very careful:  
misconfiguration
Got line # of this file can result in your filesystems being readable by the 
world.
Got line /usr/src -mapall=common 127.0.0.1
Making new ep fs=0x406,0x22b1c3bb
doing opt -mapall=common 127.0.0.1
got host 127.0.0.1
exporting /usr/src
unexporting / /
unexporting /home /home
unexporting /root /root
unexporting /storage /storage
unexporting /tmp /tmp
unexporting /usr /usr
unexporting /var /var
Getting mount list.
Here we go.

I then chmod /usr/src to 777 so that my user common has write permissions 
there:
#chmod 777 /usr/src

I then mount the export to a local directory:
#mount -t nfs 127.0.0.1:/usr/src /mnt/test

And mountd then provides the following output:

Got mount request from 127.0.0.1
rpcpath: /usr/src
# Mount successful for /usr/src by 127.0.0.1.
Got line #  $OpenBSD: exports,v 1.2 2002/05/31 08:15:44 pjanzen Exp $
Got line #
Got line # NFS exports Database
Got line # See exports(5) for more information.  Be very careful:  
misconfiguration
Got line # of this file can result in your filesystems being readable by the 
world.
Got line /usr/src -mapall=joe 127.0.0.1
Making new ep fs=0x3,0xd111762b
doing opt -mapall=joe 127.0.0.1
got host 127.0.0.1
exporting /usr/src
unexporting / /
unexporting /home /home
unexporting /usr /usr

From there I can create a test file on the mount point while logged in as 
root:
nas1#whoami 


root
nas1#touch /mnt/test/test.123   


nas1#ls -l /mnt/test/test.123   


-rw-r--r--  1 common  wsrc  0 Nov 14 12:16 /mnt/test/test.123

The test file is correctly created with owner common as the mapall option 
directs.

Now the problem kicks in if I edit /etc/exports, change mapall to another 
user, unmount the export, and HUP mountd:

#   $OpenBSD: exports,v 1.2 2002/05/31 08:15:44 pjanzen Exp $
#
# NFS exports Database
# See exports(5) for more information.  Be very careful:  misconfiguration
# of this file can result in your filesystems being readable by the world.
/usr/src -mapall=maptest 127.0.0.1

nas1#umount /mnt/test
nas1#pkill -HUP mountd
Got line #  $OpenBSD: exports,v 1.2 2002/05/31 08:15:44 pjanzen Exp $
Got line #
Got line # NFS exports Database
Got line # See exports(5) for more information.  Be very careful:  
misconfiguration
Got line # of this file can result in your filesystems being readable by the 
world.
Got line /usr/src -mapall=maptest 127.0.0.1
Making new ep fs=0x406,0x22b1c3bb
doing opt -mapall=maptest 127.0.0.1
got host 127.0.0.1
exporting /usr/src
unexporting / /
unexporting /home /home
unexporting /root /root
unexporting /storage /storage
unexporting /tmp /tmp
unexporting /usr /usr
unexporting /var /var

Then remount the export:
nas1#mount -t nfs 127.0.0.1:/usr/src /mnt/test/ 


Got mount request from 127.0.0.1
rpcpath: /usr/src
Mount successful for 

Re: Noppoo Mini Choc 84 USB keyboard can not work correctly on OpenBSD 5.2 (loongson)

2012-11-14 Thread Stuart Henderson
On 2012-11-14, Tomas Bodzar tomas.bod...@gmail.com wrote:
 However I think you need to do this (you need to do that and test on
 current anyway)
 http://undeadly.org/cgi?action=articlesid=20080315134047 or
 http://undeadly.org/cgi?action=articlesid=20070207152423 because I
 can't see your device in /usr/src/sys/dev/usb/usbdevs*

For many USB devices, there are common device classes with
standard(ish) drivers, devices in those classes will automatically
attach to the relevant driver. In this case the device already
attaches to uhid(4) and ukbd(4) based on the device class.


 On Wed, Nov 14, 2012 at 3:24 PM, yunplusplus yunplusp...@163.com wrote:
 After the Noppoo keyboard plugged in, usbdevs -dv shows:

This gives more information which might be useful,

pkg_add usbutils
lsusb -d 1006: -v

(-d 1006: restricts to devices matching the vendor ID of this keyboard).



Diskset arrival today -- sort of (funny)

2012-11-14 Thread Scott McEachern
I pre-ordered the 5.2 disksets and four t-shirts on September 8th. I'm 
located just outside of Toronto, so there shouldn't be a problem with 
international shipping.


November 1st came and went, with no disksets or t-shirts in sight. Since 
the days of 2.8, I've always received the disksets before the release 
date.  I'm a patient guy, so it's no big deal.  (I've already downloaded 
the amd64 and i386 sets for my servers, and I run -current on my 
workstations, but geez, I'd really like to get my hands on those 
shirts... and the stickers!)


Today the OpenBSD package arrives.  Four new t-shirts, but no disksets 
(and no stickers, dammit!)


The packing list has five checkmarks made in pencil beside each item, so 
somebody made an oops.  Shit happens..


The funny part?  They mailed me the freaking pencil!  I never thought 
I'd buy a $50 pencil, but I guess I was wrong.  I laughed my ass off.


Wondering where my package was, I exchanged emails with Pam at the 
computershop.ca on Nov. 6th.  They were having some shipping issues, but 
she was *really* nice about it.  No joke, she was a real sweetie.


I've since emailed her again, and I'm certain this will eventually get 
sorted out, but until then I just had to share this story.


A pencil?  Seriously?  Hilarious!  I'm still laughing!

--
Scott McEachern

https://www.blackstaff.ca



OpenBSD hangs when i unplug USB disk

2012-11-14 Thread Marcos Laufer
Hello, i'd like to inform a problem when dettaching an external 1TB USB 
disk drive , the system just freezes, i can't type anything. Also It 
stops responding to ping.
If i don't unplug it then i can use the disk normally, i can copy and 
delete files with no problem. But as soon as i unplug the USB cord, the 
machine freezes.
I've tested it on several machines, different OpenBSD versions starting 
from 4.3, i'm not asking for support, i know old OpenBSD versions are no 
longer supported, but this seemed pretty odd, i suppose that plugging 
and unplugging a USB disk should not cause any problems on any OS version.


These are the lines on dmesg about this disk:


Nov 14 16:00:31 hq /bsd: umass0 at uhub0
Nov 14 16:00:31 hq /bsd:  port 5 configuration 1 interface 0 Western 
Digital My Passport 0748 rev 2.10/10.15 addr 2

Nov 14 16:00:31 hq /bsd: umass0: using SCSI over Bulk-Only
Nov 14 16:00:31 hq /bsd: scsibus0 at umass0: 2 targets, initiator 0
Nov 14 16:00:31 hq /bsd: sd0 at scsibus0 targ 1 lun 0: WD, My Passport 
0748, 1015 SCSI4 0/direct fixed

Nov 14 16:00:38 hq /bsd: sd0: 953837MB, 512 bytes/sec, 1953458176 sec total
Nov 14 16:00:38 hq /bsd: ses0 at scsibus0 targ 1 lun 1: WD, SES Device, 
1015 SCSI4 13/enclosure services fixed

Nov 14 16:00:38 hq /bsd: ses0: unable to read enclosure configuration

Best regards,
Marcos



bgpd send corrupt AS path message to peer in router server used at Equinix Ashburn

2012-11-14 Thread Daniel Ouellet

Hi,

I am hoping that I may be able to somehow reach the consultant that 
support the router server at Equinix in Ashburn VA here, or may be 
someone else can provide me a bit more details as to how I could 
possibly find more details or history on this problem.


There is a dual setup at Equinix that use OpenBSD as router servers for 
public peering there, but somehow the version of the bgpd used is older 
and I cant get them to upgrade it to the latest one and possibly address 
thsi issue here.


What I get is this from the various routers servers (two) when I try to 
either bring IPv4 or IPv6 with it:
Nov 14 16:24:55.432 EST: %BGP-3-NOTIFICATION: sent to neighbor 
2001:504:0:2::::1 3/11 (invalid or corrupt AS path) 13 bytes 
40020A02 0223 2ABD 95
Nov 14 16:24:55.432 EST: %BGP-4-MSGDUMP: unsupported or mal-formatted 
message received from 2001:504:0:2::::1:
        006C 0200  5540 0101 0040 
020A 0202
 232A  BD95 E008 045E 3323 2A80 0E3A 0002 0120 2001 0504  
0002 
 9002 0001 FE80    021D B5FF FEA1 3052 0030 2A02 2818 
 302A

0228 1800 0130 2A02 2818 0002
Nov 14 16:25:56.959 EST: %BGP-3-NOTIFICATION: sent to neighbor 
2001:504:0:2::::1 3/11 (invalid or corrupt AS path) 13 bytes 
40020A02 0223 2ABD 95
Nov 14 16:25:56.959 EST: %BGP-4-MSGDUMP: unsupported or mal-formatted 
message received from 2001:504:0:2::::1:
        006C 0200  5540 0101 0040 
020A 0202
 232A  BD95 E008 045E 3323 2A80 0E3A 0002 0120 2001 0504  
0002 
 9002 0001 FE80    021D B5FF FEA1 3052 0030 2A02 2818 
 302A

0228 1800 0130 2A02 2818 0002
Nov 14 16:27:37.465 EST: %BGP-3-NOTIFICATION: sent to neighbor 
2001:504:0:2::::1 3/11 (invalid or corrupt AS path) 13 bytes 
40020A02 0223 2ABD 95
Nov 14 16:27:37.465 EST: %BGP-4-MSGDUMP: unsupported or mal-formatted 
message received from 2001:504:0:2::::1:
        006C 0200  5540 0101 0040 
020A 0202
 232A  BD95 E008 045E 3323 2A80 0E3A 0002 0120 2001 0504  
0002 
 9002 0001 FE80    021D B5FF FEA1 3052 0030 2A02 2818 
 302A

0228 1800 0130 2A02 2818 0002
Nov 14 16:37:46.917 EST: %BGP-3-NOTIFICATION: sent to neighbor 
206.223.115.251 3/11 (invalid or corrupt AS path) 17 bytes 40020E02 
0327 2A19 F83A EC
Nov 14 16:37:46.917 EST: %BGP-4-MSGDUMP: unsupported or mal-formatted 
message received from 206.223.115.251:
        004A 0200  2F40 0101 0040 
020E 0203
 272A  19F8  3AEC 4003 04CE DF73 28C0 0810 272A 1068 272A 
7F60 272A

9E3A 5E33 272A 18A7 01A3
Nov 14 16:38:40.428 EST: %BGP-3-NOTIFICATION: sent to neighbor 
206.223.115.251 3/11 (invalid or corrupt AS path) 17 bytes 40020E02 
0327 2A19 F83A EC
Nov 14 16:38:40.428 EST: %BGP-4-MSGDUMP: unsupported or mal-formatted 
message received from 206.223.115.251:
        004A 0200  2F40 0101 0040 
020E 0203
 272A  19F8  3AEC 4003 04CE DF73 28C0 0810 272A 1068 272A 
7F60 272A

9E3A 5E33 272A 18A7 01A3

I have over 150 sessions peering there in a combination of IPv4 and 
IPv6, so it's not like the router can't handle it or can't process bgp 
announcement correctly, but only when it try to do one session with the 
router server running OpenBSD it does this.


Is there any one that had similar problem that may be able to provide me 
more details as to get this solved somehow or really give me some 
details as to provide to Equinix showing them that upgrading their 
server routers would fix the problem, or possible something in the 
configuration is wrong and that they should look at?


My hope is really to be able to find the person that support it and for 
what I was told by Equinix support, it is suppose to be someone from 
OpenBSD, but I can't get any name to possibly work directly with that 
person or provide more details to that person to address this for all 
peers at Equinix and we are talking hundreds of ISP peering together there.


Obviously not all use the router servers setup because of this and may 
simply do not use it as a side effect of it, but it would be good if 
this could be address somehow and it would help anyone.


My hope is to move this forward somehow here, but I have to say I do not 
have much to work with as is and sadly I can't provide any configuration 
for the OpenBSD setup a I do not have access to it what so ever.


So, this may not get anywhere, but if there is a chance, I sure would 
appreciate it.


Best,

Daniel



Re: OpenBSD hangs when i unplug USB disk

2012-11-14 Thread Paulm
You *do* know about mount(8)/umount(8), right?


On Wed, Nov 14, 2012 at 04:22:20PM -0300, Marcos Laufer wrote:
 Hello, i'd like to inform a problem when dettaching an external 1TB
 USB disk drive , the system just freezes, i can't type anything.
 Also It stops responding to ping.
 If i don't unplug it then i can use the disk normally, i can copy
 and delete files with no problem. But as soon as i unplug the USB
 cord, the machine freezes.
 I've tested it on several machines, different OpenBSD versions
 starting from 4.3, i'm not asking for support, i know old OpenBSD
 versions are no longer supported, but this seemed pretty odd, i
 suppose that plugging and unplugging a USB disk should not cause any
 problems on any OS version.
 
 These are the lines on dmesg about this disk:
 
 
 Nov 14 16:00:31 hq /bsd: umass0 at uhub0
 Nov 14 16:00:31 hq /bsd:  port 5 configuration 1 interface 0
 Western Digital My Passport 0748 rev 2.10/10.15 addr 2
 Nov 14 16:00:31 hq /bsd: umass0: using SCSI over Bulk-Only
 Nov 14 16:00:31 hq /bsd: scsibus0 at umass0: 2 targets, initiator 0
 Nov 14 16:00:31 hq /bsd: sd0 at scsibus0 targ 1 lun 0: WD, My
 Passport 0748, 1015 SCSI4 0/direct fixed
 Nov 14 16:00:38 hq /bsd: sd0: 953837MB, 512 bytes/sec, 1953458176 sec total
 Nov 14 16:00:38 hq /bsd: ses0 at scsibus0 targ 1 lun 1: WD, SES
 Device, 1015 SCSI4 13/enclosure services fixed
 Nov 14 16:00:38 hq /bsd: ses0: unable to read enclosure configuration
 
 Best regards,
 Marcos



Re: bgpd send corrupt AS path message to peer in router server used at Equinix Ashburn

2012-11-14 Thread Claudio Jeker
On Wed, Nov 14, 2012 at 04:57:17PM -0500, Daniel Ouellet wrote:
 Hi,
 
 I am hoping that I may be able to somehow reach the consultant that
 support the router server at Equinix in Ashburn VA here, or may be
 someone else can provide me a bit more details as to how I could
 possibly find more details or history on this problem.
 
 There is a dual setup at Equinix that use OpenBSD as router servers
 for public peering there, but somehow the version of the bgpd used
 is older and I cant get them to upgrade it to the latest one and
 possibly address thsi issue here.
 
 What I get is this from the various routers servers (two) when I try
 to either bring IPv4 or IPv6 with it:
 Nov 14 16:24:55.432 EST: %BGP-3-NOTIFICATION: sent to neighbor
 2001:504:0:2::::1 3/11 (invalid or corrupt AS path) 13
 bytes 40020A02 0223 2ABD 95

Why is your router unhappy about this AS path? This is a valid 4-byte
AS_PATH. Could it be that for some strange reason one side thinks that
4-byte AS are enabled and the other still expects 2-byte AS numbers?

-- 
:wq Claudio



Re: Noppoo Mini Choc 84 USB keyboard can not work correctly on OpenBSD 5.2 (loongson)

2012-11-14 Thread Tomas Bodzar
On Wed, Nov 14, 2012 at 9:37 PM, Stuart Henderson s...@spacehopper.org wrote:
 On 2012-11-14, Tomas Bodzar tomas.bod...@gmail.com wrote:
 However I think you need to do this (you need to do that and test on
 current anyway)
 http://undeadly.org/cgi?action=articlesid=20080315134047 or
 http://undeadly.org/cgi?action=articlesid=20070207152423 because I
 can't see your device in /usr/src/sys/dev/usb/usbdevs*

 For many USB devices, there are common device classes with
 standard(ish) drivers, devices in those classes will automatically
 attach to the relevant driver. In this case the device already
 attaches to uhid(4) and ukbd(4) based on the device class.


Maybe this can be problem http://deskthority.net/wiki/Noppoo_Choc_Mini
here? Specifically http://deskthority.net/wiki/NKRO-over-USB_issues


 On Wed, Nov 14, 2012 at 3:24 PM, yunplusplus yunplusp...@163.com wrote:
 After the Noppoo keyboard plugged in, usbdevs -dv shows:

 This gives more information which might be useful,

 pkg_add usbutils
 lsusb -d 1006: -v

 (-d 1006: restricts to devices matching the vendor ID of this keyboard).



Re: relayd and header directives

2012-11-14 Thread Bogdan Andu
Hello,

In the meanwhile I have discovered the following issues:

[WITH SSL]:
1) No headers directives are allowed - the session is reported as invalid

2)
If the POST arguments are sent as usual, like this:

$ curl -XPOST -k -v
https://server/cgi-bin/query -d'param1=val1param2=val2'

relayd reports the
session invalid:

relayd www_ssl, session 1 (1 active), 0, 10.10.11.66 -
127.0.0.1:8080, invalid

and the local web server is not accessed

3) If the
POST argumenst are converted into GET like this:

$ curl -XPOST -k -v
https://server/cgi-bin/query?param1=val1param2=val2'

everything work ok.
Although there are sessions reported as invalid, the dialog with local web
server 
works, and the respons returns to the client

[WITHOUT SSL]
Everything work as expected with and without header directives


So, if the
relayd does not makes ssl offloading seems that everything work ok. I suspect
there must be something with ssl processing.

The machine is in trunk0 setup
with link failover in dual stack. So the relayd listens on both IPv4 and IPv6.
With or without SSL offloading I cannot change response headers.

The local
web server is system web server Apache 1.3 with mod_perl 1.3.

The web server
is not chroot-ed.


dmseg follows:

OpenBSD 5.2 (GENERIC.MP) #368: Wed Aug  1
10:04:49 MDT 2012
   
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem
= 4292550656 (4093MB)
avail mem = 4155912192 (3963MB)
mainbus0 at root
bios0
at mainbus0: SMBIOS rev. 2.5 @ 0xcff9c000 (46 entries)
bios0: vendor Dell Inc.
version 1.4.3 date 05/15/2009
bios0: Dell Inc. PowerEdge R200
acpi0 at
bios0: rev 2
acpi0: sleep states S0 S4 S5
acpi0: tables DSDT FACP APIC SPCR
HPET MCFG WD__ SLIC ERST HEST BERT EINJ SSDT SSDT SSDT
acpi0: wakeup devices
PCI0(S5)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr
0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0:
Intel(R) Xeon(R) CPU E3110 @ 3.00GHz, 3000.60 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,S
SSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF
cpu0: 6MB 64b/line 16-way L2
cache
cpu0: apic clock running at 333MHz
cpu1 at mainbus0: apid 1 (application
processor)
cpu1: Intel(R) Xeon(R) CPU E3110 @ 3.00GHz, 3000.21 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUS
H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,SMX,EST,TM2,S
SSE3,CX16,xTPR,PDCM,SSE4.1,XSAVE,NXE,LONG,LAHF
cpu1: 6MB 64b/line 16-way L2
cache
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0:
misconfigured as apic 0, remapped to apid 2
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (PEX1)
acpiprt2 at acpi0: bus 2 (SBE0)
acpiprt3 at
acpi0: bus 3 (SBE4)
acpiprt4 at acpi0: bus 4 (SBE5)
acpiprt5 at acpi0: bus 5
(COMP)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
ipmi at mainbus0 not
configured
cpu0: Enhanced SpeedStep 3000 MHz: speeds: 3000, 2667, 2333, 2000
MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 Intel 3200/3210
Host rev 0x01
ppb0 at pci0 dev 1 function 0 Intel 3200/3210 PCIE rev 0x01:
msi
pci1 at ppb0 bus 1
mpi0 at pci1 dev 0 function 0 Symbios Logic SAS1068E
rev 0x08: msi
scsibus0 at mpi0: 112 targets
sd0 at scsibus0 targ 0 lun 0:
Dell, VIRTUAL DISK, 1028 SCSI3 0/direct fixed
naa.600508e0b29cee969c7b3107
sd0: 152064MB, 512 bytes/sector,
311427072 sectors
ppb1 at pci0 dev 28 function 0 Intel 82801I PCIE rev 0x02:
msi
pci2 at ppb1 bus 2
ppb2 at pci0 dev 28 function 4 Intel 82801I PCIE rev
0x02
pci3 at ppb2 bus 3
bge0 at pci3 dev 0 function 0 Broadcom BCM5721 rev
0x21, BCM5750 C1 (0x4201): apic 2 int 16, address 00:25:64:3b:a6:e6
brgphy0 at
bge0 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
ppb3 at pci0 dev 28 function
5 Intel 82801I PCIE rev 0x02
pci4 at ppb3 bus 4
bge1 at pci4 dev 0 function
0 Broadcom BCM5721 rev 0x21, BCM5750 C1 (0x4201): apic 2 int 17, address
00:25:64:3b:a6:e7
brgphy1 at bge1 phy 1: BCM5750 10/100/1000baseT PHY, rev. 0
uhci0 at pci0 dev 29 function 0 Intel 82801I USB rev 0x02: apic 2 int 21
uhci1 at pci0 dev 29 function 1 Intel 82801I USB rev 0x02: apic 2 int 20
uhci2 at pci0 dev 29 function 2 Intel 82801I USB rev 0x02: apic 2 int 21
ehci0 at pci0 dev 29 function 7 Intel 82801I USB rev 0x02: apic 2 int 21
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 Intel EHCI root hub rev
2.00/1.00 addr 1
ppb4 at pci0 dev 30 function 0 Intel 82801BA Hub-to-PCI rev
0x92
pci5 at ppb4 bus 5
vga1 at pci5 dev 5 function 0 ATI ES1000 rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen
1-5 added (80x25, vt100 emulation)
radeondrm0 at vga1: apic 2 int 19
drm0 at
radeondrm0
pcib0 at pci0 dev 31 function 0 Intel 82801IR LPC rev 0x02
pciide0 at pci0 dev 31 function 2 Intel 82801I SATA rev 0x02: DMA, channel 0
configured to native-PCI, channel 1 

Re: HP Ethernet 1Gb 4-port 331FLR card supported?

2012-11-14 Thread Sebastian Reitenbach
On Wednesday, November 14, 2012 21:27 CET, Stuart Henderson 
s...@spacehopper.org wrote: 
 
 On 2012-11-14, Sebastian Reitenbach sebas...@l00-bugdead-prods.de wrote:
  Hi,
 
  we have a HP Proliant Server Gen8, where we want to run OpenBSD on it. 
  The card mentioned has to go into the FlexibleLOM port on the server, 
  therefore
  there is not that much choice of a card.
  As far as I have seen, this card is not listed in any of the drivers, but I 
  found that
  link here:
  http://partnerweb.vmware.com/comp_guide1/detail.php?device_cat=iodevice_id=21446
  which tells me that the card has a BroadCom NetXtreme BCM5719 chipset, and 
  bge(4) at least tells me, that this chipset is supported.
 
  But to be sure, I thought trying to ask if anyone has such a card in use 
  with OpenBSD?
 
  thanks,
  Sebastian
 
 
 
 BCM5719 is not yet supported, I understand there are problems
 getting the phy to work.

Thanks Stuart, Instead of searching for the HP name of the card, I now 
searching for 
the chipset, I  found the patch for BCM5719 from dlg@ on tech@ and it seems 
that 
patch didn't made it into CVS yet.

Sebastian



Re: HP Ethernet 1Gb 4-port 331FLR card supported?

2012-11-14 Thread Grzegorz Patola
Hi,

I'm also looking to make this car working. I found some patches against 4.9 but 
it crashes when you trying to assign IP to the interface. I found that the 
supporting code is in stable freebsd so maybe it could be imported from there ?

Does anywane have working patch for openbsd ?

Regards,
Greg.
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Sebastian Reitenbach sebas...@l00-bugdead-prods.de wrote:

On Wednesday, November 14, 2012 21:27 CET, Stuart Henderson 
s...@spacehopper.org wrote: 

 On 2012-11-14, Sebastian Reitenbach sebas...@l00-bugdead-prods.de wrote:
  Hi,
 
  we have a HP Proliant Server Gen8, where we want to run OpenBSD on it. 
  The card mentioned has to go into the FlexibleLOM port on the server, 
  therefore
  there is not that much choice of a card.
  As far as I have seen, this card is not listed in any of the drivers, but I 
  found that
  link here:
  http://partnerweb.vmware.com/comp_guide1/detail.php?device_cat=iodevice_id=21446
  which tells me that the card has a BroadCom NetXtreme BCM5719 chipset, and 
  bge(4) at least tells me, that this chipset is supported.
 
  But to be sure, I thought trying to ask if anyone has such a card in use 
  with OpenBSD?
 
  thanks,
  Sebastian
 
 
 
 BCM5719 is not yet supported, I understand there are problems
 getting the phy to work.

Thanks Stuart, Instead of searching for the HP name of the card, I now 
searching for 
the chipset, I found the patch for BCM5719 from dlg@ on tech@ and it seems that 
patch didn't made it into CVS yet.

Sebastian