Network stack slow?


#1

Hi guys/gals… just a quick question I have, it’s about the network stack/performance…

Is it just my setups or is the network implementation really slow?? I’ve run haiku (lastest nightly) on 4 different boxes/laptops… and the result is the same on all of them… very slow to begin to download any pages/data , sometimes I have to refresh the page 2 times.
Makes no difference if it’s on web+ or some of the other browsers on the depot.

Also makes no difference wether via wifi (supported card) or via ethernet (supported chipset/card) on an 18mb/sec line.

Not meaning to complain, but was just thinking it’s very odd? Anyone else have this?

It’s not my backbone/equipment, both windoze and OSX run/browse fine.

Sometimes is so bad that even apps in the depot time out…

Anyways, just thought I’d ask if that’s normal at the moment?


#2

Not for me. iprowifi4965 here.
Maybe you see something in the syslog. Start a tail -f /var/logs/syslog in Terminal to see if something suspicious happens.


#3

Maybe not “really” but generally it is slower than Linux/Windows.


#4

kallisti5 has been talking about getting some 10gbe hardware to test out haikus network stack so that testing could shed some light on slowdowns…

Your issue sounds like a dns problem…try manually configuring 8.8.8.8 Google as your dns.


#5

I’ve just benchmarked a 2Gb file transfer on local network (broadcom 570x driver) onto the same physical disk (5400 rpm FAT32 system), both Haiku x64 hrev 52394 (Oct 09, 2018) and the latest Windows 10 (updated).
Haiku took 1m13s, Windows took 1m14s. Apparently exact same SFTP performance on same disk, FAT32 file system. From this benchmark, I cannot conclude that the broadcom 570x driver is any slower than the windows version.

However, when using SSD and NTFS I get 400% better performance. I dont have Haiku on SSD partition, so cannot compare.


#6

Thanks Zenja for the file transfer test, that sounds pretty darn good if you ask me.

My issue is with the transfer rate of data/initial handshake for it to START transferring data/pages. Once its going it goes great. (although even in haiku depot its always pretty darn slow, but i was thinking that was due to the amount of users downloading apps/data from Haikudepot.

So just to be clear, its generally not the transfer rate, but its the time it takes to start ?

Cheers

Humdinger, ill take a look tonight at the logs :smiley:


#7

Vanne is it faster for sites you have already visited?

I still think your issue might be DNS related if the initial lookup is slow… then that would explain why connecting is slow.


#8

Cb, yeah def faster for sites ive already visted, but take for example this site, or this thread for example, its def a LOT slower than when i visit it on OSX. A LOT!!!

Its the same for Haikudepot, a lot of the times “Software update” for example times out. Ill include a snap.


#9

Def something funny going on. Dont think its the dns, as ping to various outfits works just fine.

My syslog is huge…

Quite a lot of rubbish coming from the network part of the log.

Appologies for posting a bit of the syslog.

KERN: package_daemon [16526928: 292] Volume::InitialVerify(0xfebe6db960, (nil))
KERN: package_daemon [16545157: 292] Volume::InitialVerify(): volume at “/boot/home/config” is consistent
KERN: sis19x:00.16.700:init_hardware::SiS19X:init_hardware()
KERN: register_domain(5, internet6)
KERN: unregister_domain(0xffffffff905ebe00, 5, internet6)
KERN: register_domain(5, internet6)
KERN: unregister_domain(0xffffffff905ebd00, 5, internet6)
KERN: register_domain(1, internet)
KERN: unregister_domain(0xffffffff905ebd00, 1, internet)
KERN: register_domain(9, unix)
KERN: unregister_domain(0xffffffff905ebd00, 9, unix)
KERN: register_domain(5, internet6)
KERN: unregister_domain(0xffffffff905eb580, 5, internet6)
KERN: usb_hid: no handlers for hid device
KERN: register_domain(5, internet6)
KERN: unregister_domain(0xffffffff905eb580, 5, internet6)
KERN: usb_hid: no handlers for hid device
KERN: register_domain(1, internet)
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/input/usb_hid
KERN: unregister_domain(0xffffffff905eb200, 1, internet)
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/input/wacom
KERN: ps2_hid: init_hardware
KERN: ps2_hid: init_driver
KERN: register_domain(5, internet6)
KERN: unregister_domain(0xffffffff905b1d80, 5, internet6)
KERN: register_domain(5, internet6)
KERN: unregister_domain(0xffffffff905b1d80, 5, internet6)
KERN: register_domain(1, internet)
KERN: unregister_domain(0xffffffff905b1d80, 1, internet)
KERN: register_domain(9, unix)
KERN: unregister_domain(0xffffffff905b1d80, 9, unix)
KERN: register_domain(5, internet6)
KERN: unregister_domain(0xffffffff905b1d80, 5, internet6)
KERN: register_domain(5, internet6)
KERN: unregister_domain(0xffffffff905b1d80, 5, internet6)
KERN: ps2_hid: publish_devices
KERN: ps2_hid: uninit_driver
KERN: register_domain(1, internet)
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/input/ps2_hid
KERN: [net/broadcom570x/0] compat_open(0x2)
KERN: slab memory manager: created area 0xffffffff91801000 (4247)
KERN: ifmedia_ioctl: switching bge to KERN: Type: Ethernet
KERN: SubType: autoselect
KERN: ps2: reset failed
KERN: ps2: devfs_publish_device input/mouse/ps2/0, status = 0xffffffff
KERN: ps2: devfs_publish_device input/keyboard/at/0, status = 0x00000000
KERN: /dev/net/broadcom570x/0: media change, media 0x22 quality 1000 speed 10000000
KERN: register_domain(5, internet6)
KERN: ps2: keyboard reset failed, status 0x80000001, data 0xff
KERN: ps2: keyboard probing failed
KERN: KeyboardDevice: error when opening /dev/input/keyboard/at/0: No error
KERN: ps2: devfs_unpublish_device input/keyboard/at/0, status = 0x00000000
KERN: usb_hid: keyboard device unhandled control 0x00002710
KERN: register_domain(9, unix)
DAEMON ‘transmission-daemon’[378]: Transmission 2.94 (d8e60ee44f) started (/sources/transmission-2.94/libtransmission/session.c:740)
DAEMON ‘transmission-daemon’[378]: RPC Server Adding address to whitelist: 127.0.0.1 (/sources/transmission-2.94/libtransmission/rpc-server.c:971)
DAEMON ‘transmission-daemon’[378]: RPC Server Serving RPC and Web requests on port 127.0.0.1:9091/transmission/ (/sources/transmission-2.94/libtransmission/rpc-server.c:1213)
DAEMON ‘transmission-daemon’[378]: RPC Server Whitelist enabled (/sources/transmission-2.94/libtransmission/rpc-server.c:1217)
DAEMON ‘transmission-daemon’[378]: DHT Reusing old id (/sources/transmission-2.94/libtransmission/tr-dht.c:307)
DAEMON ‘transmission-daemon’[378]: DHT Bootstrapping from 116 IPv4 nodes (/sources/transmission-2.94/libtransmission/tr-dht.c:156)
DAEMON ‘transmission-daemon’[378]: Using settings from “/boot/home/config/settings/transmission-daemon” (/sources/transmission-2.94/daemon/daemon.c:528)
DAEMON ‘transmission-daemon’[378]: Saved “/boot/home/config/settings/transmission-daemon/settings.json” (/sources/transmission-2.94/libtransmission/variant.c:1266)
DAEMON ‘transmission-daemon’[378]: Loaded 3 torrents (/sources/transmission-2.94/libtransmission/session.c:2034)
KERN: /dev/net/broadcom570x/0: media change, media 0x900030 quality 1000 speed 1000000000
KERN: register_domain(4, link)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘transmission-daemon’[378]: Port Forwarding State changed from “Not forwarded” to “???” (/sources/transmission-2.94/libtransmission/port-forwarding.c:92)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
KERN: /dev/net/broadcom570x/0: media change, media 0x22 quality 1000 speed 10000000
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
KERN: bfs: bfs_create_index:2135: File or Directory already exists
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
KERN: bfs: bfs_create_index:2135: File or Directory already exists
KERN: emuxki: init_hardware()
KERN: emuxki: init_driver()
KERN: mpu401: B_MODULE_INIT
KERN: pci_reserve_device(1, 10, 0, emuxki)
KERN: emuxki: setup_emuxki(0xffffffff915ac140)
KERN: emuxki: audio/hmulti/emuxki/1 deviceid = 0x04 chiprev = 4 model = 2002 enhanced at 9400
KERN: emuxki: PCI command before: 5
KERN: emuxki: PCI command after: 5
KERN: emuxki: codec reset
KERN: emuxki: codec vendor id = 0x83847650
KERN: emuxki: codec description = SigmaTel
KERN: emuxki: codec 3d enhancement = SigmaTel
KERN: emuxki: writing codec registers
KERN: emuxki: codec master output = 0x00
KERN: emuxki: codec aux output = 0x00
KERN: emuxki: codec mono output = 0x8000
KERN: emuxki: codec pcm output = 0x808
KERN: emuxki: codec line in = 0x8808
KERN: emuxki: codec record line in= 0x404
KERN: emuxki: codec record gain = 0x8000
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
KERN: emuxki: installing interrupt : 10
KERN: emuxki: setup_emuxki done
KERN: emuxki: publish_devices()
KERN: emuxki: publish midi/emuxki/1
KERN: emuxki: publish audio/hmulti/emuxki/1
KERN: emuxki: emuxki: find_device(midi/emuxki/1)
KERN: emuxki: emuxki: find_device(audio/hmulti/emuxki/1)
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/audio/hmulti/emuxki
KERN: echo3g: init_hardware()
KERN: echo3g: no card found
KERN: auvia: init_hardware()
KERN: auich: init_hardware()
KERN: sis7018:init_hardware:ver:2.0.2
KERN: emuxki: emuxki_pmem_alloc : numblocks : 1
KERN: emuxki: emuxki_pmem_alloc : 0
KERN: emuxki: emuxki_pmem_alloc : j == numblocks 1
KERN: emuxki: emuxki_pmem_alloc : j == numblocks emuxki_mem_new ok
KERN: emuxki: emuxki_pmem_alloc : j == numblocks returning
KERN: emuxki: emuxki_pmem_alloc : numblocks : 1
KERN: emuxki: emuxki_pmem_alloc : 0
KERN: emuxki: emuxki_pmem_alloc : 1
KERN: emuxki: emuxki_pmem_alloc : j == numblocks 1
KERN: emuxki: emuxki_pmem_alloc : j == numblocks emuxki_mem_new ok
KERN: emuxki: emuxki_pmem_alloc : j == numblocks returning
KERN: emuxki: emuxki_pmem_alloc : numblocks : 1
KERN: emuxki: emuxki_pmem_alloc : 0
KERN: emuxki: emuxki_pmem_alloc : 1
KERN: emuxki: emuxki_pmem_alloc : 2
KERN: emuxki: emuxki_pmem_alloc : j == numblocks 1
KERN: emuxki: emuxki_pmem_alloc : j == numblocks emuxki_mem_new ok
KERN: emuxki: emuxki_pmem_alloc : j == numblocks returning
KERN: emuxki: emuxki_pmem_alloc : numblocks : 1
KERN: emuxki: emuxki_pmem_alloc : 0
KERN: emuxki: emuxki_pmem_alloc : 1
KERN: emuxki: emuxki_pmem_alloc : 2
KERN: emuxki: emuxki_pmem_alloc : 3
KERN: emuxki: emuxki_pmem_alloc : j == numblocks 1
KERN: emuxki: emuxki_pmem_alloc : j == numblocks emuxki_mem_new ok
KERN: emuxki: emuxki_pmem_alloc : j == numblocks returning
KERN: emuxki: emuxki_pmem_alloc : numblocks : 1
KERN: emuxki: emuxki_pmem_alloc : 0
KERN: emuxki: emuxki_pmem_alloc : 1
KERN: emuxki: emuxki_pmem_alloc : 2
KERN: emuxki: emuxki_pmem_alloc : 3
KERN: emuxki: emuxki_pmem_alloc : 4
KERN: emuxki: emuxki_pmem_alloc : j == numblocks 1
KERN: emuxki: emuxki_pmem_alloc : j == numblocks emuxki_mem_new ok
KERN: emuxki: emuxki_pmem_alloc : j == numblocks returning
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
KERN: emuxki: set_enabled_channels 0 : enabled
KERN: emuxki: set_enabled_channels 1 : enabled
KERN: emuxki: set_enabled_channels 2 : enabled
KERN: emuxki: set_enabled_channels 3 : enabled
KERN: emuxki: name : Record
KERN: emuxki: multi->control_count 67
KERN: Highpoint-IDE: supports_device()
Last message repeated 1 time
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/bus/usb_raw
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
KERN: /dev/net/broadcom570x/0: media change, media 0x900030 quality 1000 speed 1000000000
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
KERN: /dev/net/broadcom570x/0: media change, media 0x22 quality 1000 speed 10000000
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
KERN: /dev/net/broadcom570x/0: media change, media 0x900030 quality 1000 speed 1000000000
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
KERN: /dev/net/broadcom570x/0: media change, media 0x22 quality 1000 speed 10000000
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST to 255.255.255.255:67
KERN: /dev/net/broadcom570x/0: media change, media 0x900026 quality 1000 speed 10000000
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_OFFER from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_NACK from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_OFFER from 192.168.1.1
DAEMON ‘DHCP’: your_address: 192.168.1.109
DAEMON ‘DHCP’: server: 192.168.1.1
DAEMON ‘DHCP’: lease time: 60 seconds
DAEMON ‘DHCP’: subnet: 255.255.255.0
DAEMON ‘DHCP’: gateway: 192.168.1.1
DAEMON ‘DHCP’: nameserver[0]: 192.168.1.1
DAEMON ‘DHCP’: domain name: “dlinkrouter”
DAEMON ‘DHCP’: UNKNOWN OPTION 60 (0x3c)
DAEMON ‘DHCP’: UNKNOWN OPTION 125 (0x7d)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST for 192.168.1.109 to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_NACK from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_OFFER from 192.168.1.1
DAEMON ‘DHCP’: your_address: 192.168.1.109
DAEMON ‘DHCP’: server: 192.168.1.1
DAEMON ‘DHCP’: lease time: 60 seconds
DAEMON ‘DHCP’: subnet: 255.255.255.0
DAEMON ‘DHCP’: gateway: 192.168.1.1
DAEMON ‘DHCP’: nameserver[0]: 192.168.1.1
DAEMON ‘DHCP’: domain name: “dlinkrouter”
DAEMON ‘DHCP’: UNKNOWN OPTION 60 (0x3c)
DAEMON ‘DHCP’: UNKNOWN OPTION 125 (0x7d)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST for 192.168.1.109 to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_NACK from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_OFFER from 192.168.1.1
DAEMON ‘DHCP’: your_address: 192.168.1.109
DAEMON ‘DHCP’: server: 192.168.1.1
DAEMON ‘DHCP’: lease time: 60 seconds
DAEMON ‘DHCP’: subnet: 255.255.255.0
DAEMON ‘DHCP’: gateway: 192.168.1.1
DAEMON ‘DHCP’: nameserver[0]: 192.168.1.1
DAEMON ‘DHCP’: domain name: “dlinkrouter”
DAEMON ‘DHCP’: UNKNOWN OPTION 60 (0x3c)
DAEMON ‘DHCP’: UNKNOWN OPTION 125 (0x7d)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST for 192.168.1.109 to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_NACK from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_DISCOVER to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_OFFER from 192.168.1.1
DAEMON ‘DHCP’: your_address: 192.168.1.109
DAEMON ‘DHCP’: server: 192.168.1.1
DAEMON ‘DHCP’: lease time: 60 seconds
DAEMON ‘DHCP’: subnet: 255.255.255.0
DAEMON ‘DHCP’: gateway: 192.168.1.1
DAEMON ‘DHCP’: nameserver[0]: 192.168.1.1
DAEMON ‘DHCP’: domain name: “dlinkrouter”
DAEMON ‘DHCP’: UNKNOWN OPTION 60 (0x3c)
DAEMON ‘DHCP’: UNKNOWN OPTION 125 (0x7d)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST for 192.168.1.109 to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_ACK from 192.168.1.1
DAEMON ‘DHCP’: server: 192.168.1.1
DAEMON ‘DHCP’: lease time: 28800 seconds
DAEMON ‘DHCP’: subnet: 255.255.255.0
DAEMON ‘DHCP’: gateway: 192.168.1.1
DAEMON ‘DHCP’: nameserver[0]: 192.168.1.1
DAEMON ‘DHCP’: domain name: “dlinkrouter”
DAEMON ‘DHCP’: UNKNOWN OPTION 125 (0x7d)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: DHCP status = No error
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST for 192.168.1.109 to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Ignoring DHCP_OFFER not for us from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Ignoring DHCP_ACK not for us from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Ignoring DHCP_OFFER not for us from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Ignoring DHCP_ACK not for us from 192.168.1.1
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_ACK from 192.168.1.1
DAEMON ‘DHCP’: server: 192.168.1.1
DAEMON ‘DHCP’: lease time: 28800 seconds
DAEMON ‘DHCP’: subnet: 255.255.255.0
DAEMON ‘DHCP’: gateway: 192.168.1.1
DAEMON ‘DHCP’: nameserver[0]: 192.168.1.1
DAEMON ‘DHCP’: domain name: “dlinkrouter”
DAEMON ‘DHCP’: UNKNOWN OPTION 125 (0x7d)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: DHCP status = No error
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST for 192.168.1.109 to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_ACK from 192.168.1.1
DAEMON ‘DHCP’: server: 192.168.1.1
DAEMON ‘DHCP’: lease time: 28800 seconds
DAEMON ‘DHCP’: subnet: 255.255.255.0
DAEMON ‘DHCP’: gateway: 192.168.1.1
DAEMON ‘DHCP’: nameserver[0]: 192.168.1.1
DAEMON ‘DHCP’: domain name: “dlinkrouter”
DAEMON ‘DHCP’: UNKNOWN OPTION 125 (0x7d)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: DHCP status = No error
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Send DHCP_REQUEST for 192.168.1.109 to 255.255.255.255:67
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: Received DHCP_ACK from 192.168.1.1
DAEMON ‘DHCP’: server: 192.168.1.1
DAEMON ‘DHCP’: lease time: 28800 seconds
DAEMON ‘DHCP’: subnet: 255.255.255.0
DAEMON ‘DHCP’: gateway: 192.168.1.1
DAEMON ‘DHCP’: nameserver[0]: 192.168.1.1
DAEMON ‘DHCP’: domain name: “dlinkrouter”
DAEMON ‘DHCP’: UNKNOWN OPTION 125 (0x7d)
DAEMON ‘DHCP’: /dev/net/broadcom570x/0: DHCP status = No error
KERN: acquire_advisory_lock(vnode = 0xffffffff90

c65280, flock = 0xffffffff9168aeb0, wait = no)
Last message repeated 1 time
KERN: acquire_advisory_lock(vnode = 0xffffffff90c7b180, flock = 0xffffffff9168aeb0, wait = no)
KERN: Last message repeated 14 times.
KERN: Disabling unhandled io interrupt 9

KERN: vm_soft_fault: va 0xbbadb000 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error ‘Bad address’ on fault at 0xbbadbeef, ip 0x1aa71dc1f7c, write 1, user 1, thread 0xa3a
KERN: vm_page_fault: thread “WebCore: Worker” (2618) in team “WebPositive” (1393) tried to write address 0xbbadbeef, ip 0x1aa71dc1f7c (“libJavaScriptCore.so.18.7.4_seg” +0xe0ef7c)
KERN: debug_server: Thread 2618 entered the debugger: Segment violation
KERN: vm_soft_fault: va 0xbbadb000 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error ‘Bad address’ on fault at 0xbbadbeef, ip 0x1aa71dc1f7c, write 1, user 1, thread 0xa38
KERN: vm_soft_fault: va 0xbbadb000 not covered by area in address space
KERN: vm_page_fault: thread “WebCore: Worker” (2616) in team “WebPositive” (1393) tried to write address 0xbbadbeef, ip 0x1aa71dc1f7c (“libJavaScriptCore.so.18.7.4_seg” +0xe0ef7c)
KERN: vm_page_fault: vm_soft_fault returned error ‘Bad address’ on fault at 0xbbadbeef, ip 0x1aa71dc1f7c, write 1, user 1, thread 0xa3b
KERN: vm_page_fault: thread “WebCore: Worker” (2619) in team “WebPositive” (1393) tried to write address 0xbbadbeef, ip 0x1aa71dc1f7c (“libJavaScriptCore.so.18.7.4_seg” +0xe0ef7c)
KERN: low resource memory: normal -> critical
KERN: stack trace, current PC 0x1aa71dc1f7c WTFCrash + 0x1c:
KERN: (0x7f7bf7385250) 0x1aa71d02cdd _ZN3JSC4Wasm6Memory6createENS0_9PageCountES2_ON3WTF8FunctionIFvNS1_14NotifyPressureEEEEONS4_IFvNS1_16SyncTryToReclaimEEEEONS4_IFvNS1_11GrowSuccessES2_S2_EEE + 0xa9d
KERN: (0x7f7bf7385330) 0x1aa71d4c31a _ZN3JSCL28constructJSWebAssemblyMemoryEPNS_9ExecStateE + 0x42a
KERN: 0xffffffff90e4d750->VMAnonymousCache::_Commit(4303355904): Failed to reserve 4303355904 bytes of RAM
KERN: low resource memory: critical -> warning
KERN: (0x7f7bf73853b0) 0x76c1fa74 (mmap area + 0x3b4a74)
KERN: vm_soft_fault: va 0xbbadb000 not covered by area in address space
KERN: vm_page_fault: vm_soft_fault returned error ‘Bad address’ on fault at 0xbbadbeef, ip 0x1aa71dc1f7c, write 1, user 1, thread 0xa3c
KERN: vm_page_fault: thread “WebCore: Worker” (2620) in team “WebPositive” (1393) tried to write address 0xbbadbeef, ip 0x1aa71dc1f7c (“libJavaScriptCore.so.18.7.4_seg” +0xe0ef7c)
KERN: (0x7f7bf73853c0) 0x1aa7198f177 llint_entry + 0x7478 (closest symbol)
KERN: (0x7f7bf7385460) 0x1aa71987b17 vmEntryToJavaScript + 0x130 (closest symbol)
KERN: (0x7f7bf73854d0) 0x1aa7192e071 _ZN3JSC7JITCode7executeEPNS_2VMEPNS_14ProtoCallFrameE + 0x61
KERN: (0x7f7bf7385500) 0x1aa719044be _ZN3JSC11Interpreter14executeProgramERKNS_10SourceCodeEPNS_9ExecStateEPNS_8JSObjectE + 0x9fe
KERN: (0x7f7bf7385f20) 0x1aa71b036cc _ZN3JSC8evaluateEPNS_9ExecStateERKNS_10SourceCodeENS_7JSValueERN3WTF8NakedPtrINS_9ExceptionEEE + 0xec
KERN: (0x7f7bf7385f80) 0x1ce72d3c98a _ZN7WebCore22WorkerScriptController8evaluateERKNS_16ScriptSourceCodeERN3WTF8NakedPtrIN3JSC9ExceptionEEEPNS4_6StringE + 0x9a
KERN: (0x7f7bf7386010) 0x1ce72d3cc8a _ZN7WebCore22WorkerScriptController8evaluateERKNS_16ScriptSourceCodeEPN3WTF6StringE + 0x4a
KERN: (0x7f7bf7386050) 0x1ce737481fb _ZN7WebCore12WorkerThread12workerThreadEv + 0x35b
KERN: (0x7f7bf7386140) 0x1aa71ddfc3c _ZN3WTF6Thread10entryPointEPNS0_16NewThreadContextE + 0x6c
KERN: (0x7f7bf7386170) 0x1aa71e138b9 _ZN3WTFL19wtfThreadEntryPointEPv + 0x9
KERN: (0x7f7bf7386180) 0x1078bd62709 ZL20pthread_thread_entryPvS + 0xb
KERN: low resource memory: warning -> note
KERN: debug_server: Killing team 1393 (/boot/system/apps/WebPositive)
KERN: debug_server: TeamDebugHandler::Init(): Failed to get info for team 1393: Operation on invalid team
KERN: debug_server: KillTeam(): Error getting info for team 1393: Operation on invalid team
KERN: debug_server: Killing team 1393 ()
KERN: low resource memory: note -> normal
KERN: acquire_advisory_lock(vnode = 0xffffffff90c65280, flock = 0xffffffff9172aeb0, wait = no)
Last message repeated 1 time
KERN: acquire_advisory_lock(vnode = 0xffffffff90c7b180, flock = 0xffffffff9172aeb0, wait = no)KERN: Last message repeated 14 times.
KERN: Last message repeated 2 times.
KERN: acquire_advisory_lock(vnode = 0xffffffff90c65280, flock = 0xffffffff9172aeb0, wait = no)
Last message repeated 1 time
KERN: acquire_advisory_lock(vnode = 0xffffffff90c65280, flock = 0xffffffff9161ceb0, wait = no)
Last message repeated 1 time
KERN: acquire_advisory_lock(vnode = 0xffffffff90379700, flock = 0xffffffff9161ceb0, wait = no)
KERN: Last message repeated 14 times.
KERN: bfs: Remove:2125: No such file or directory
KERN: bfs: Could not find value in index “size”!
KERN: bfs: Remove:2125: No such file or directory
KERN: bfs: Could not find value in index “last_modified”!


#10

Transmission Daemon? Turn off Transmission; I got in trouble with my ISP once because it was making hundreds of DNS requests every minute. That could be slowing down your DNS server (particularly small router ones). Though that was an early version Transmission for BeOS.


#11

Works ok for me.


#12

I spot also weird behavior regarding DHCP.
Your dlinkrouter offer an ip address 192.168.1.109 with a 60 second lease (!?) and when Haiku DHCP client request it, it got refused 4 or 5 times before, finally, got an ACK from your router DHCP server and a longer lease time.

I don’t know about DHCP option 0x3c and 0x7d, maybe it’s a lead, as the final offer which works don’t have the 0x3c option set.

I also think the transmissiondaemon could be culprid of something bad here, too.


#13

I set transmission up as a headless server with autostart, but as i told i never experienced any problem like this.


#14

Looks like these DHCP options are related to MS-NKPU:
https://msdn.microsoft.com/en-us/library/hh554879.aspx


#15

It also looks like something (probably WebPositive) ate all of your memory (Failed to reserve 4303355904 bytes of RAM).


#16

Good catch, indeed.


#17

Hey guys, after a little testing, i thougfht stuff it and throw a different system together…

Same bloody result, which leads me to think it might be my router issue after all. Either that or Web+ just hates my router… On the plus side i can say that the intel system compared to the Dual opty system is much, much faster… plays Solo, a Star wars movie, in 1080P like its nothing.

this is on a Evga 122-yw-E173 (which i thought was long dead, but has miraculously come back to life) 750i mobo, with the onboard sound working out of the box… rtl81xx/0 also works a treat.

Just a couple of notes to the previous, Transmission was not running, well it was, but its not transmission specific, as the issue was there while transmission was active or not started.

Ill have a dig around my setting in my d-link router… one thing though, why would it work normally in windows or OSX and then not properly in Haiku? thats weird right?


#18

There are a few known issues with the nightlies at the moment to keep in mind. I noticed an error about package updates failing…

https://dev.haiku-os.org/ticket/14638


#19

Thanks Kal, but this issue is independant of resizing the terminal.

… there is Definitely a network stack issue going on here. I just chucked in 2 different live Linux distro CD’s and the included browsers work without any delay… period. No delay or slowdown at all. So this is definitely Haiku specific.

So windows, OSX ,mint and unbunto work with zero issues on the network stack.

What I will do when I get home is download all the different browsers available for haiku and see if the issue persists. Could it be that it’s a web+ issue? I did try a few others and could have sworn it was the same… but I didn’t quantify any of my findings.


#20

Apart from trying with a browser, a commandline browsing test may be good, using the curl command.

Untimed:

curl www.google.com

Timed:

time curl www.google.com
time curl www.randomurl.com