Re: Severe problem with amd64 -current as of June 13

[STeve Andre']

On 06/16/13 01:05, Philip Guenther wrote:

On Sat, Jun 15, 2013 at 7:19 PM, STeve Andre'  wrote:

On June 13 I updated my tree from anoncvs.usa.openbsd.org, and
the new -current failed shortly after running it.

Things would get *very* slow, with continuous disk activity.  It was
sort of possible to switch between screens, albeit after a few minutes.
Processes would be shown as in a disk wait (D).  Eventually the system
freezes completely with the continuous disk activity as evidenced by
my disk LED.

Hmm, once it gets into this state, can you go to the console, then
break into ddb (you'll need to add ddb.console=1 to your
/etc/sysctl.conf and reboot for that to work), and then do "show uvm"
and report the results?


Philip Guenther


I will try that, but I doubt I can get to a console.  It's very quick
from slow to hung.  But I'll umount everything I can and see
what transpires.  Thanks.

--STeve Andre'

Re: Severe problem with amd64 -current as of June 13

[Philip Guenther]

On Sat, Jun 15, 2013 at 7:19 PM, STeve Andre'  wrote:
>On June 13 I updated my tree from anoncvs.usa.openbsd.org, and
> the new -current failed shortly after running it.
>
>Things would get *very* slow, with continuous disk activity.  It was
> sort of possible to switch between screens, albeit after a few minutes.
> Processes would be shown as in a disk wait (D).  Eventually the system
> freezes completely with the continuous disk activity as evidenced by
> my disk LED.

Hmm, once it gets into this state, can you go to the console, then
break into ddb (you'll need to add ddb.console=1 to your
/etc/sysctl.conf and reboot for that to work), and then do "show uvm"
and report the results?


Philip Guenther

Re: Severe problem with amd64 -current as of June 13

[STeve Andre']

On 06/16/13 00:23, Amit Kulkarni wrote:
>
>
>
> On Sat, Jun 15, 2013 at 9:19 PM, STeve Andre'  > wrote:
>
>  amd64-current seems rather wounded at the moment.  I've been
> running -current since June 5th with no problems.  This is a W500
> thinkpad.
>
>On June 13 I updated my tree from anoncvs.usa.openbsd.org
> , and
> the new -current failed shortly after running it.
>
>Things would get *very* slow, with continuous disk activity.
>  It was
> sort of possible to switch between screens, albeit after a few
> minutes.
> Processes would be shown as in a disk wait (D).  Eventually the system
> freezes completely with the continuous disk activity as evidenced by
> my disk LED.
>
>Going back to the June 5th kernel with the June 13th userland seems
> to be working.  Looking at the FAQ there are things for -current which
> had no relevance to this problem.  I then got a new copy of src and
> xenocara with the same results.
>
>Seeing memmove and similar changes, and a fix for at least one arch
> makes me wonder if amd64 has a problem.
>
>Suggestions?
>
>
> i just updated a desktop PC with the 15th June snap and things were 
> working fine... and the June 10th packages.

Interesting.  I updated my tree this afternoon, and built a new kernel which
finally had the same problem.  It ran for a while fine, but then got 
very slow
and finally froze.  This was after 10 or 15 minutes, long enough for me 
to think
that things were OK.

Running on the June 5th kernel right now and all is well.

I'll try the June 10th snaps, but I think that's missing png?

--STeve Andre'

Severe problem with amd64 -current as of June 13

[STeve Andre']

   amd64-current seems rather wounded at the moment.  I've been
running -current since June 5th with no problems.  This is a W500
thinkpad.

   On June 13 I updated my tree from anoncvs.usa.openbsd.org, and
the new -current failed shortly after running it.

   Things would get *very* slow, with continuous disk activity.  It was
sort of possible to switch between screens, albeit after a few minutes.
Processes would be shown as in a disk wait (D).  Eventually the system
freezes completely with the continuous disk activity as evidenced by
my disk LED.

   Going back to the June 5th kernel with the June 13th userland seems
to be working.  Looking at the FAQ there are things for -current which
had no relevance to this problem.  I then got a new copy of src and
xenocara with the same results.

   Seeing memmove and similar changes, and a fix for at least one arch
makes me wonder if amd64 has a problem.

   Suggestions?

---dmesg of the 'good' kernel of June 5th
Jun 15 00:28:58 paladin /bsd: OpenBSD 5.3-current (GENERIC.MP) #0: Wed 
Jun  5 21:33:29 EDT 2013
Jun 15 00:28:58 paladin /bsd: 
root@paladin:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Jun 15 00:28:58 paladin /bsd: real mem = 8499433472 (8105MB)
Jun 15 00:28:58 paladin /bsd: avail mem = 8265461760 (7882MB)
Jun 15 00:28:58 paladin /bsd: mainbus0 at root
Jun 15 00:28:58 paladin /bsd: bios0 at mainbus0: SMBIOS rev. 2.4 @ 
0xe0010 (80 entries)
Jun 15 00:28:58 paladin /bsd: bios0: vendor LENOVO version "6FET92WW 
(3.22 )" date 12/14/2011

Jun 15 00:28:58 paladin /bsd: bios0: LENOVO 4061CTO
Jun 15 00:28:58 paladin /bsd: acpi0 at bios0: rev 2
Jun 15 00:28:58 paladin /bsd: acpi0: sleep states S0 S3 S4 S5
Jun 15 00:28:58 paladin /bsd: acpi0: tables DSDT FACP SSDT ECDT APIC 
MCFG HPET SLIC BOOT ASF! SSDT TCPA DMAR SSDT SSDT SSDT
Jun 15 00:28:58 paladin /bsd: acpi0: wakeup devices LID_(S3) SLPB(S3) 
UART(S3) IGBE(S4) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) EXP4(S4) PCI1(S4) 
USB0(S3) USB3(S3) USB5(S3) EHC0(S3) EHC1(S3) HDEF(S4)

Jun 15 00:28:58 paladin /bsd: acpitimer0 at acpi0: 3579545 Hz, 24 bits
Jun 15 00:28:58 paladin /bsd: acpiec0 at acpi0
Jun 15 00:28:58 paladin /bsd: acpimadt0 at acpi0 addr 0xfee0: PC-AT 
compat

Jun 15 00:28:58 paladin /bsd: cpu0 at mainbus0: apid 0 (boot processor)
Jun 15 00:28:58 paladin /bsd: cpu0: Intel(R) Core(TM)2 Duo CPU T9600 @ 
2.80GHz, 2793.45 MHz
Jun 15 00:28:58 paladin /bsd: 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF

Jun 15 00:28:58 paladin /bsd: cpu0: 6MB 64b/line 16-way L2 cache
Jun 15 00:28:58 paladin /bsd: cpu0: smt 0, core 0, package 0
Jun 15 00:28:58 paladin /bsd: cpu0: apic clock running at 266MHz
Jun 15 00:28:58 paladin /bsd: cpu1 at mainbus0: apid 1 (application 
processor)
Jun 15 00:28:58 paladin /bsd: cpu1: Intel(R) Core(TM)2 Duo CPU T9600 @ 
2.80GHz, 2793.00 MHz
Jun 15 00:28:58 paladin /bsd: 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,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,NXE,LONG,LAHF,PERF

Jun 15 00:28:58 paladin /bsd: cpu1: 6MB 64b/line 16-way L2 cache
Jun 15 00:28:58 paladin /bsd: cpu1: smt 0, core 1, package 0
Jun 15 00:28:58 paladin /bsd: ioapic0 at mainbus0: apid 1 pa 0xfec0, 
version 20, 24 pins
Jun 15 00:28:58 paladin /bsd: ioapic0: misconfigured as apic 2, remapped 
to apid 1

Jun 15 00:28:58 paladin /bsd: acpimcfg0 at acpi0 addr 0xe000, bus 0-63
Jun 15 00:28:58 paladin /bsd: acpihpet0 at acpi0: 14318179 Hz
Jun 15 00:28:58 paladin /bsd: acpiprt0 at acpi0: bus 0 (PCI0)
Jun 15 00:28:58 paladin /bsd: acpiprt1 at acpi0: bus 1 (AGP_)
Jun 15 00:28:58 paladin /bsd: acpiprt2 at acpi0: bus 2 (EXP0)
Jun 15 00:28:58 paladin /bsd: acpiprt3 at acpi0: bus 3 (EXP1)
Jun 15 00:28:58 paladin /bsd: acpiprt4 at acpi0: bus -1 (EXP2)
Jun 15 00:28:58 paladin /bsd: acpiprt5 at acpi0: bus 5 (EXP3)
Jun 15 00:28:58 paladin /bsd: acpiprt6 at acpi0: bus 13 (EXP4)
Jun 15 00:28:58 paladin /bsd: acpiprt7 at acpi0: bus 21 (PCI1)
Jun 15 00:28:58 paladin /bsd: acpicpu0 at acpi0: C3, C2, C1, PSS
Jun 15 00:28:58 paladin /bsd: acpicpu1 at acpi0: C3, C2, C1, PSS
Jun 15 00:28:58 paladin /bsd: acpipwrres0 at acpi0: PUBS
Jun 15 00:28:58 paladin /bsd: acpitz0 at acpi0: critical temperature is 
127 degC
Jun 15 00:28:58 paladin /bsd: acpitz1 at acpi0: critical temperature is 
100 degC

Jun 15 00:28:58 paladin /bsd: acpibtn0 at acpi0: LID_
Jun 15 00:28:58 paladin /bsd: acpibtn1 at acpi0: SLPB
Jun 15 00:28:58 paladin /bsd: acpibat0 at acpi0: BAT0 model "42T4619" 
serial  5701 type LION oem "SANYO"

Jun 15 00:28:58 paladin /bsd: acpibat1 at acpi0: BAT1 not present
Jun 15 00:28:58 paladin /bsd: acpiac0 at acpi0: AC unit online
Jun 15 00:28:58 paladin /bsd: acpithinkpad0 at acpi0
Jun 15 00:28:58 paladin /bsd: acpidock0 at acpi0: GDCK not docked (0)
Jun 15 00:28:58 

Re: max RAM

[Nick Holland]

I had a chance to briefly play with a monster amd64 system.
511GB worked, 520GB didn't.
Machine had 1.5TB RAM in it and took over five minutes to "initialize
memory", before even starting the POST, so that's as far as I got.

It is entirely possible that this was HW dependent.

Nick.

On 06/15/13 14:10, Tony Berth wrote:
> on a amd64 server. I don't know if the 4GB limit is still in place.
> 
> 
> Thanks
> 
> Tony
> 
> 
> On Sat, Jun 15, 2013 at 8:07 PM, Zé Loff  wrote:
> 
>> On your Zaurus or on your old mac or on your 386 or on your amd64 server
>> or on your VAX or on your sparc64 or...?
>>
>> On 15/06/2013, at 18:37, Tony Berth  wrote:
>>
>> > Dear group,
>> >
>> > what is the max RAM the current release can support?
>> >
>> > Thanks
>> >
>> > Tony

Centrino 6205 no link

[shaul]

It continues saying no link for Centrino Advanced-N 6205. I installed 5.3,
rebooted, it did fw_update for iwn0 and uvideo. I rebooted and got
firmware error.

I manually did

pkg_add http://firmware.openbsd.org/firmware/5.3/iwn-firmware-5.7.tgz

and rebooted. It says no link and in /etc/hostname.iwn0 it has

nwid Network
wpakey 'password'
dhcp

When I do "ifconfig iwn0 scan" it shows a list of available networks but
can not connect

$ ifconfig iwn0
iwn0: flags=8843 mtu 1500
lladdr xx:xx:xx:xx:xx:xx
priority: 4
groups: wlan
media: IEEE802.11 autoselect (autoselect mode 11g)
status: no network
ieee80211: nwid Network wpakey  wpaprotos wpa1,wpa2
wpaakms psk wpaciphers tkip,ccmp wpagroupcipher tkip
inet6 :::::%iwn0 prefixlen 64 scopeid 0x2

OpenBSD 5.3 (GENERIC.MP) #62: Tue Mar 12 18:21:20 MDT 2013
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 5883748352 (5611MB)
avail mem = 5704622080 (5440MB)
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0xe82b0 (33 entries)
bios0: vendor American Megatrends Inc. version "09PW.ME13.20121101.SKK"
date 11/01/2012
bios0: SAMSUNG ELECTRONICS CO., LTD. 305V4A/305V5A/3415VA
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP APIC MCFG SLIC HPET SSDT SSDT
acpi0: wakeup devices PCE4(S4) SBAZ(S4) P0PC(S4) GEC_(S4) PE20(S4)
PE21(S4) PE22(S4) PE23(S4) PWRB(S5)
acpitimer0 at acpi0: 3579545 Hz, 32 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1598.06 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB
64b/line 16-way L2 cache
cpu0: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu0: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu0: AMD erratum 721 detected and fixed
cpu0: apic clock running at 199MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1597.10 MHz
cpu1:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu1: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB
64b/line 16-way L2 cache
cpu1: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu1: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu1: AMD erratum 721 detected and fixed
cpu2 at mainbus0: apid 2 (application processor)
cpu2: AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1597.10 MHz
cpu2:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu2: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB
64b/line 16-way L2 cache
cpu2: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu2: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu2: AMD erratum 721 detected and fixed
cpu3 at mainbus0: apid 3 (application processor)
cpu3: AMD A6-3410MX APU with Radeon(tm) HD Graphics, 1597.10 MHz
cpu3:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,HTT,SSE3,MWAIT,CX16,POPCNT,NXE,MMXX,FFXSR,LONG,3DNOW2,3DNOW,LAHF,CMPLEG,SVM,EAPICSP,AMCR8,ABM,SSE4A,MASSE,3DNOWP,OSVW,IBS,SKINIT,ITSC
cpu3: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 1MB
64b/line 16-way L2 cache
cpu3: ITLB 32 4KB entries fully associative, 16 4MB entries fully associative
cpu3: DTLB 48 4KB entries fully associative, 48 4MB entries fully associative
cpu3: AMD erratum 721 detected and fixed
ioapic0 at mainbus0: apid 5 pa 0xfec0, version 21, 24 pins
acpimcfg0 at acpi0 addr 0xe000, bus 0-255
acpihpet0 at acpi0: 14318180 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 3 (PCE4)
acpiprt2 at acpi0: bus 5 (PE20)
acpiprt3 at acpi0: bus -1 (PE21)
acpiprt4 at acpi0: bus 6 (PE22)
acpiprt5 at acpi0: bus -1 (PE23)
acpiec0 at acpi0
acpicpu0 at acpi0: C2, PSS
acpicpu1 at acpi0: C2, PSS
acpicpu2 at acpi0: C2, PSS
acpicpu3 at acpi0: C2, PSS
acpitz0 at acpi0: critical temperature is 98 degC
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT1 type LION oem "SAMSUNG Electronics"
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: PWRB
acpivideo0 at acpi0: VGA_
acpivideo1 at acpi0: VGA_
cpu0: 1598 MHz: speeds: 1600 1500 1400 1300 1200 1000 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "AMD AMD64 12h Host" rev 0x00
vga1 at pci0 dev 1

Improvement suggestion to CWM

[Rodrigo Mosconi]

Dears,


follow a simple change to enable the use of mouse`s botton4/button5
(wheel-up/wheel-down) on CWM.

I can use M-4, for example, to raise a window and M-5 to lower.

Att,


Index: conf.c
===
RCS file: /cvs/xenocara/app/cwm/conf.c,v
retrieving revision 1.133
diff -u -r1.133 conf.c
--- conf.c  23 May 2013 16:52:39 -  1.133
+++ conf.c  15 Jun 2013 20:14:46 -
@@ -545,7 +545,7 @@
{ "menu_cmd", mousefunc_menu_cmd, MOUSEBIND_CTX_ROOT },
 };

-static unsigned int mouse_btns[] = { Button1, Button2, Button3 };
+static unsigned int mouse_btns[] = { Button1, Button2, Button3, Button4,
Button5 };

 int
 conf_mousebind(struct conf *c, char *name, char *binding)
@@ -571,7 +571,7 @@
} else
substring = name;

-   button = strtonum(substring, 1, 3, &errstr);
+   button = strtonum(substring, 1, 5, &errstr);
if (errstr)
warnx("button number is %s: %s", errstr, substring);

Re: max RAM [solved]

[Tony Berth]

Thanks


On Sat, Jun 15, 2013 at 9:02 PM, Stuart Henderson wrote:

> On 2013-06-15, Tony Berth  wrote:
> > on a amd64 server. I don't know if the 4GB limit is still in place.
>
> 4.9 is the last release which was limited to 4GB on amd64.
>
> http://www.openbsd.org/50.html

Re: max RAM

[Zé Loff]

On your Zaurus or on your old mac or on your 386 or on your amd64 server or on 
your VAX or on your sparc64 or...?

On 15/06/2013, at 18:37, Tony Berth  wrote:

> Dear group,
> 
> what is the max RAM the current release can support?
> 
> Thanks
> 
> Tony

Re: max RAM

[Stuart Henderson]

On 2013-06-15, Tony Berth  wrote:
> on a amd64 server. I don't know if the 4GB limit is still in place.

4.9 is the last release which was limited to 4GB on amd64.

http://www.openbsd.org/50.html

Re: max RAM

[Tony Berth]

on a amd64 server. I don't know if the 4GB limit is still in place.


Thanks

Tony


On Sat, Jun 15, 2013 at 8:07 PM, Zé Loff  wrote:

> On your Zaurus or on your old mac or on your 386 or on your amd64 server
> or on your VAX or on your sparc64 or...?
>
> On 15/06/2013, at 18:37, Tony Berth  wrote:
>
> > Dear group,
> >
> > what is the max RAM the current release can support?
> >
> > Thanks
> >
> > Tony

Re: max RAM

[Kenneth R Westerback]

On Sat, Jun 15, 2013 at 07:37:06PM +0200, Tony Berth wrote:
> Dear group,
> 
> what is the max RAM the current release can support?
> 
> Thanks
> 
> Tony
> 

Define 'support'.

 Ken

Re: install fixes address in /etc/hosts

[Jan Stary]

On Apr 29 11:15:15, t...@tedunangst.com wrote:
> On Mon, Apr 29, 2013 at 11:02, Kenneth R Westerback wrote:
> > On Mon, Apr 29, 2013 at 01:41:52PM +0200, Jan Stary wrote:
> >> Installed yesterday's current/i386, using dhcpd and pxeboot
> >> from another machine. After the installation, I noticed
> >> that the address that was assigned to me during the install
> >> via DHCP was written into /etc/hosts. Is that intended?
> >> Should an arbitrary dhcp-assigned address be written into
> >> /etc/hosts to stay there? Should that be mentioned in afterboot?
> 
> > Your points are valid. I no longer recall the discussions that took
> > place at the time, and am open to any new discussion.
> 
> As I recall, Bad Things (tm) happen when the machine's hostname does
> not resolve, and that's why there is always an entry in hosts.
> 
> If I wanted to open a giant rabbit hole, I might suggest dhclient
> should update hosts as it runs... But it's important that *something*
> be in /etc/hosts that matches what's in /etc/myname.
> 
> We changed it from adding 127.0.0.1 entries for the hostname because
> Other Bad Things (tm) happened when forward and reverse lookups for
> localhost and/or the hostname didn't coordinate.

On a fresh current/i386 I see

127.0.0.1   localhost
::1 localhost
192.168.167.100 gw.my.domain gw

where is the dhcp address assigned to me during install,
now completely meaningless. I just deleted it.

Should this be mentioned afterboot,
possibly under "Check hostname" or
"Verify network interface configuration"?

Jan

max RAM

[Tony Berth]

Dear group,

what is the max RAM the current release can support?

Thanks

Tony

Re: pf queue priq and set prio

[Михаил Швецов]

This all for test - to know how work queue priq and set prio.


15.6.2013 14:58:26 пользователь Stuart Henderson (s...@spacehopper.org) написал:

I have re-ordered the email to make it easier to reply..

On 2013-06-15, Михаил Швецов  wrote:
> Please help me
>
> I have 2 pf.conf files on the server. To example i exec
>
> ifconfig $int_if(em0) media 10baseT
>
> 1)
> set skip on lo
> altq on $int_if priq bandwidth 512Kb queue { qlan_ssh, qlan_def }
> queue qlan_ssh priority 1
> queue qlan_def priority 5 priq (default)
> block
> pass out
> pass in on $int_if
> match in on $int_if proto tcp to port ssh queue qlan_ssh

> When i run 1'st rules:
>
> it's working
>
> I login to this server by ssh and run sysctl and list statistics (vmstat,
> iostat on systat) and see all good.
>
> Then i copy by ftp(may samba) file 1Gig(example) it's copy by 60KB/sec, and i
> CAN'T SEE STATISTICS by ssh. Ssh session freeze.
>
> I may see that "queue qlan_ssh" - worked.

This is expected. High numbers take priority. All "priority 5"
traffic is sent before any "priority 1".

If you have so much high-priority traffic that it totally fills
the link, low-priority traffic will never be sent.



int_if i have 1Gb/sec (GLAN "Intel PRO/1000GT (82541GI)")
queue i make special 512Kb(60KB), to see that ssh freeze when i get file from 
(ftp, samba). And i can see it


> 2)
> set skip on lo
> block
> pass out
> pass in on $int_if
> match in on $int_if set prio 3 # May not wrote this rule, 3 - by default
> match in on $int_if proto tcp to port ssh set prio 1
>
> When i run 2'nd rules:
>
> it's not working
>
> I login to this server by ssh and run sysctl and list statistics (vmstat,
> iostat on systat) and see all good.
>
> Then i copy by ftp(may samba) file 1Gig(example) it's copy by 60KB/sec, and i
> SEE STATISTICS by ssh but with some DELAY. Ssh session with some delay.
>
> I may see that "set prio 1" - NOT worked.
>
> What am i doing wrong?
>
>

For now, "set prio" queues are only limited by NIC speed. If you only
have 512Kb bandwidth as in the first example, this won't do anything
useful yet.

Henning is working on bandwidth controls for this, but it is not
committed. http://undeadly.org/cgi?action=article&sid=20130606101818
has more information.




before second rule i run
ifconfig em0 media 10baseT (when copy file it's get 1000KB/sec) - it's minimum 
for that card)
i want minimum to see that ssh freeze when i get file from (ftp, samba) 
again(how in queue). but i don't see it.


P.S.
this another qestion
Can i do this and will it work?
3-d rule
on $int_if i have 100Mb/sec queue i crop traffice to 512Kb/sec. And how much 
set prio get: 100Mb/sec or 512Kb/sec

set skip on lo
altq on $int_if priq bandwidth 512Kb queue { qlan_def }
 queue qlan_def priority 5 priq (default)
block
pass out
pass in on $int_if
match in on $int_if set prio 3
match in on $int_if proto tcp to port ssh set prio 1

Re: pf queue priq and set prio

[Stuart Henderson]

I have re-ordered the email to make it easier to reply..

On 2013-06-15, Михаил Швецов  wrote:
> Please help me
>
> I have 2 pf.conf files on the server. To example i exec
>
> ifconfig $int_if(em0) media 10baseT
>
> 1)
> set skip on lo
> altq on $int_if priq bandwidth 512Kb queue { qlan_ssh, qlan_def }
> queue qlan_ssh priority 1
> queue qlan_def priority 5 priq (default)
> block
> pass out
> pass in on $int_if
> match in on $int_if proto tcp to port ssh queue qlan_ssh

> When i run 1'st rules:
>
> it's working
>
> I login to this server by ssh and run sysctl and list statistics (vmstat,
> iostat on systat) and see all good.
>
> Then i copy by ftp(may samba) file 1Gig(example) it's copy by 60KB/sec, and i
> CAN'T SEE STATISTICS by ssh. Ssh session freeze.
>
> I may see that "queue qlan_ssh" - worked.


This is expected. High numbers take priority. All "priority 5"
traffic is sent before any "priority 1".

If you have so much high-priority traffic that it totally fills
the link, low-priority traffic will never be sent.


> 2)
> set skip on lo
> block
> pass out
> pass in on $int_if
> match in on $int_if set prio 3 # May not wrote this rule, 3 - by default
> match in on $int_if proto tcp to port ssh set prio 1
>
> When i run 2'nd rules:
>
> it's not working
>
> I login to this server by ssh and run sysctl and list statistics (vmstat,
> iostat on systat) and see all good.
>
> Then i copy by ftp(may samba) file 1Gig(example) it's copy by 60KB/sec, and i
> SEE STATISTICS by ssh but with some DELAY. Ssh session with some delay.
>
> I may see that "set prio 1" - NOT worked.
>
> What am i doing wrong?
>
>

For now, "set prio" queues are only limited by NIC speed. If you only
have 512Kb bandwidth as in the first example, this won't do anything
useful yet.

Henning is working on bandwidth controls for this, but it is not
committed. http://undeadly.org/cgi?action=article&sid=20130606101818
has more information.

pf queue priq and set prio

[Михаил Швецов]

Please help me

I have 2 pf.conf files on the server. To example i exec

ifconfig $int_if(em0) media 10baseT

1)

set skip on lo

altq on $int_if priq bandwidth 512Kb queue { qlan_ssh, qlan_def }

queue qlan_ssh priority 1

queue qlan_def priority 5 priq (default)

block

pass out

pass in on $int_if

match in on $int_if proto tcp to port ssh queue qlan_ssh

2)

set skip on lo

block

pass out

pass in on $int_if

match in on $int_if set prio 3 # May not wrote this rule, 3 - by default

match in on $int_if proto tcp to port ssh set prio 1

When i run 1'st rules:

it's working

I login to this server by ssh and run sysctl and list statistics (vmstat,
iostat
on systat) and see all good.

Then i copy by ftp(may samba) file 1Gig(example) it's copy by 60KB/sec, and i
CAN'T SEE STATISTICS by ssh. Ssh session freeze.

I may see that "queue qlan_ssh" - worked.

When i run 2'nd rules:

it's not working

I login to this server by ssh and run sysctl and list statistics (vmstat,
iostat
on systat) and see all good.

Then i copy by ftp(may samba) file 1Gig(example) it's copy by 60KB/sec, and i
SEE
STATISTICS by ssh but with some DELAY. Ssh session with some delay.

I may see that "set prio 1" - NOT worked.

What am i doing wrong?