Waiting for your Response.

2018-06-20 Thread Valodzka Anatoli. 
Hello,

I sent you an email earlier 4 days ago regarding a business proposal, but did 
not get a reply from you up till this moment.  I do not know if you receive it 
or not.  Meanwhile, I am a Banker here in Bahrain. I sent you a business 
proposition that will benefit the two of us and it is important that we discuss 
it. Kindly get back to confirm receipt my email, so we can talk in details 
about it.  Waiting your urgent response.

Thanks.

Anatoli.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ATI video problem - extremely slow desktop - 100% cpu load

2018-06-20 Thread Mark Saad 
On Wed, Jun 20, 2018 at 3:43 PM, Vincent Stemen  wrote:
> I have now tested with two additional ATI cards.
> A Radeon HD 5450 and and older card that shows as
> "RV370 [Radeon X300 SE]" in the PCI info.
>
> Same problem on all of them.  Before, it would come up and run correctly
> once in a while.  It doesn't seem to at all now.  This seems to be some
> kind of core radeon driver bug.
>

Vincent
 I am running 11.2-PRERELEASE with a Cedar PRO [Radeon HD 5450/6350]
and I dont have any issues like that

here is what I do to get it working for me; and I have used more or
less the same setup since 10.3-RELEASE

In my loader.conf I have

radeonkms_load="YES"
radeonkmsfw_CEDAR_pfp_load="YES"
radeonkmsfw_CEDAR_rlc_load="YES"
radeonkmsfw_CEDAR_me_load="YES"

I use a static xorg.conf as well  In there I have the following bits

  1 Section "ServerLayout"
  2 Identifier "X.org Configured"
  3 Screen  0  "Screen0" 0 0
  4 InputDevice"Mouse0" "CorePointer"
  5 InputDevice"Keyboard0" "CoreKeyboard"
  6 Option "AIGLX" "true"
  7 EndSection
...
 19 Section "Module"
 20 Load   "dbe"
 21 Load   "dri"
 22 Load   "dri2"
 23 Load   "extmod"
 24 Load   "record"
 25 Load   "freetype"
 26 Load   "bitmap"
 27 Load   "type1"
 28 Load   "glx"
 29 EndSection
...
 50 Section "Device"
 51 Option "AccelMethod" "EXA"
 52 Option "DRI" "true"
 53 Identifier  "Card0"
 54 Driver  "radeon"
 55 BusID   "PCI:3:0:0"
 56 EndSection
 57
...

Also if the redeon driver is not working for you try scfb . It works
better the vesa it some cases


msaad@ostrich:~ % pkg info xf86-video-scfb-0.0.4_5
xf86-video-scfb-0.0.4_5
Name   : xf86-video-scfb
Version: 0.0.4_5
Installed on   : Mon Sep 25 10:52:09 2017 EDT
Origin : x11-drivers/xf86-video-scfb
Architecture   : FreeBSD:11:amd64
Prefix : /usr/local
Categories : x11-drivers
Licenses   :
Maintainer : x...@freebsd.org
WWW: UNKNOWN
Comment: X.Org syscons display driver
Annotations:
repo_type  : binary
repository : FreeBSD
Flat size  : 21.4KiB
Description:
This package contains the X.Org xf86-video-scfb driver.
Framebuffer access via FreeBSD syscons.




> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"



-- 
mark saad | nones...@longcount.org
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ATI video problem - extremely slow desktop - 100% cpu load

2018-06-20 Thread Vincent Stemen 
I have now tested with two additional ATI cards.
A Radeon HD 5450 and and older card that shows as 
"RV370 [Radeon X300 SE]" in the PCI info.

Same problem on all of them.  Before, it would come up and run correctly
once in a while.  It doesn't seem to at all now.  This seems to be some
kind of core radeon driver bug.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: iostat busy value calculation

2018-06-20 Thread Miroslav Lachman 

Warner Losh wrote on 2018/06/20 18:13:



On Wed, Jun 20, 2018 at 8:55 AM, Miroslav Lachman <000.f...@quip.cz 
> wrote:


I would like to know how the value of disk "busy" is calculated?

I want to use values from iostat in the monitoring (zabbix).
iostat shows averages by default and the last column is "busy %",
but the first output contains averages from the system boot til now.


%busy comes from the devstat layer. It's defined as the percent of the 
time over the polling interval in which at least one transaction was 
awaiting completion by the lower layers. It's an imperfect measure of 
how busy the drives are (in ye-olden days, before tagged queuing and 
NCQ, it was OK because you had THE transaction pending and it was a good 
measure of how utilized things were. Now with concurrent I/O in flash 
devices, it's only an imperfect approximation).


Yes, I am aware of this issue. This percentage is just  "is it slightly 
loaded or heavily loaded" indicator.


Miroslav Lachman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: iostat busy value calculation

2018-06-20 Thread Miroslav Lachman 

Holger Kipp wrote on 2018/06/20 17:37:

Dear Miroslav,

looking at the manpage for iostat I see:

%b  % of time the device had one or more outstanding 
transactions
tsvc_t/i
total duration of transactions per time period, in seconds
sb/itotal time the device had one or more outstanding transac-
tions per time period, in seconds

So calculating the percentage using sb/i should be fairly easy.


If I understand it correctly, then it cannot be calculated from numbers 
between two independent runs of "iostat -I -x" because it gives me sb/i 
average from the boot time, so the calculated %b will be overall average 
instead of average between two runs after 60 seconds.
The only possible way to calculated is to run "iostat -I -x -c 2 -w 60" 
where the sb/i value of the second line will be average of these last 60 
seconds. But it also means monitoring probe will wait 60 seconds to get 
this value (each time) so it is the same problem as I described in my 
original post with "iostat -x".


Miroslav Lachman



Am 20.06.2018 um 16:55 schrieb Miroslav Lachman 
<000.f...@quip.cz>:

I would like to know how the value of disk "busy" is calculated?

I want to use values from iostat in the monitoring (zabbix).
iostat shows averages by default and the last column is "busy %", but the first 
output contains averages from the system boot til now.

# iostat -x -t da
extended device statistics
device r/s   w/skr/skw/s qlen svc_t  %b
ada0   2.5  13.849.0   287.90  45.7   2
ada1   2.6  13.851.7   287.90  39.6   2

I don't want to use "iostat -x -t da -w 20" to get averages of the last 20 
seconds because it means monitoring needs to wait 20 seconds on each run.

I can use absolute values from iostat. This output is without any delay and the 
monitoring SW can calculate averages between two runs. But the last column is 
no busy %, it is sb/i.

# iostat -I -x -t da
extended device statistics
device   r/i w/i kr/i kw/i qlen tsvc_t/i  
sb/i
ada0   7403218.0  40825749.0  144647824.0  849655694.00 2204904.2   
73121.8
ada1   7537423.0  40825749.0  152643874.5  849655694.00 1914301.0   
69996.5

So the question is - If I want to plot "busy %" in the graph - how the "busy" 
value in the first example is calculated?
Is it possible to calculate it from the numbers that I have from "iostat -I -x" 
and the know time interval between two runs?



___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: iostat busy value calculation

2018-06-20 Thread Warner Losh 
On Wed, Jun 20, 2018 at 8:55 AM, Miroslav Lachman <000.f...@quip.cz> wrote:

> I would like to know how the value of disk "busy" is calculated?
>
> I want to use values from iostat in the monitoring (zabbix).
> iostat shows averages by default and the last column is "busy %", but the
> first output contains averages from the system boot til now.
>

%busy comes from the devstat layer. It's defined as the percent of the time
over the polling interval in which at least one transaction was awaiting
completion by the lower layers. It's an imperfect measure of how busy the
drives are (in ye-olden days, before tagged queuing and NCQ, it was OK
because you had THE transaction pending and it was a good measure of how
utilized things were. Now with concurrent I/O in flash devices, it's only
an imperfect approximation).

Warner
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: iostat busy value calculation

2018-06-20 Thread Holger Kipp 
Dear Miroslav,

looking at the manpage for iostat I see:

   %b  % of time the device had one or more outstanding transactions
   tsvc_t/i
   total duration of transactions per time period, in seconds
   sb/itotal time the device had one or more outstanding transac-
   tions per time period, in seconds

So calculating the percentage using sb/i should be fairly easy.

Best regards,
Holger

Am 20.06.2018 um 16:55 schrieb Miroslav Lachman 
<000.f...@quip.cz>:

I would like to know how the value of disk "busy" is calculated?

I want to use values from iostat in the monitoring (zabbix).
iostat shows averages by default and the last column is "busy %", but the first 
output contains averages from the system boot til now.

# iostat -x -t da
   extended device statistics
device r/s   w/skr/skw/s qlen svc_t  %b
ada0   2.5  13.849.0   287.90  45.7   2
ada1   2.6  13.851.7   287.90  39.6   2

I don't want to use "iostat -x -t da -w 20" to get averages of the last 20 
seconds because it means monitoring needs to wait 20 seconds on each run.

I can use absolute values from iostat. This output is without any delay and the 
monitoring SW can calculate averages between two runs. But the last column is 
no busy %, it is sb/i.

# iostat -I -x -t da
   extended device statistics
device   r/i w/i kr/i kw/i qlen tsvc_t/i  
sb/i
ada0   7403218.0  40825749.0  144647824.0  849655694.00 2204904.2   
73121.8
ada1   7537423.0  40825749.0  152643874.5  849655694.00 1914301.0   
69996.5

So the question is - If I want to plot "busy %" in the graph - how the "busy" 
value in the first example is calculated?
Is it possible to calculate it from the numbers that I have from "iostat -I -x" 
and the know time interval between two runs?

Miroslav Lachman

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

iostat busy value calculation

2018-06-20 Thread Miroslav Lachman 

I would like to know how the value of disk "busy" is calculated?

I want to use values from iostat in the monitoring (zabbix).
iostat shows averages by default and the last column is "busy %", but 
the first output contains averages from the system boot til now.


# iostat -x -t da
extended device statistics
device r/s   w/skr/skw/s qlen svc_t  %b
ada0   2.5  13.849.0   287.90  45.7   2
ada1   2.6  13.851.7   287.90  39.6   2

I don't want to use "iostat -x -t da -w 20" to get averages of the last 
20 seconds because it means monitoring needs to wait 20 seconds on each run.


I can use absolute values from iostat. This output is without any delay 
and the monitoring SW can calculate averages between two runs. But the 
last column is no busy %, it is sb/i.


# iostat -I -x -t da
extended device statistics
device   r/i w/i kr/i kw/i qlen 
tsvc_t/i  sb/i
ada0   7403218.0  40825749.0  144647824.0  849655694.00 
2204904.2   73121.8
ada1   7537423.0  40825749.0  152643874.5  849655694.00 
1914301.0   69996.5


So the question is - If I want to plot "busy %" in the graph - how the 
"busy" value in the first example is calculated?
Is it possible to calculate it from the numbers that I have from "iostat 
-I -x" and the know time interval between two runs?


Miroslav Lachman
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2?

2018-06-20 Thread Pete French 
I use VirtualBox all the time on 11-STABLE. I do make sure I recompile 
the ernel module every time I rebuild the OS, but its pretty solid for 
me. You need the AIO tunings though.


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168298

-pete.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ATI video problem - extremely slow desktop - 100% cpu load

2018-06-20 Thread Nikita Druba 

Hello!
I was have the same problem with my HD 4870x2 at FreeBSD 11.1 and kde5 
some time ago. As a result I was change video card to Nvidia. But I 
don't try vesa drivers.

Good luck!

20.06.2018 00:23, Vincent Stemen пишет:

Hi.

FreeBSD 11.1-RELEASE
Motherboard:gigabyte GA-78LMT-USB3 R2
Video:  Integrated ATI Radeon HD 3000 graphics

System runs fine with a simple stand alone window manager such as jwm,
openbox, etc.  But anytime I run a desktop environment that has a panel and/or
desktop icons, the X desktop takes a very long time to start up and runs
extremely slow and unresponsive, the pointer jumps instead of moving smoothly,
and the main Xorg process runs at 100% load on one core.  I have tried several
different desktops, such as xfce, enlightenment, lumina, etc.  Similar problem
on all of them.

It appears to be any environment that is using DBUS.  That could just be
a coincidence.

The weird thing is that it does not always do it.  Once in a while, when
I launch X, it comes up quick and runs fine.  Shut down X and re-run it and
it's back doing it again.  Sometimes it will come up running fine several
times in a row.  Once it comes up working correctly, it stays working until
I restart X.  Even after a reboot, it is inconsistent about doing it the first
time X is run.

I have tried re-installing all the ports from X11 and the desktop environments
from FreeBSD 11 release_1, release_2, quarterly, and latest.  Same problem
with all of them.

Does anybody have any idea what could be causing this?

I don't know if for sure if this is a FreeBSD or a port problem.  There are
radeon modules running.

# kldstat

51 0x82431000 12b4a0   radeonkms.ko
...
   101 0x825b9000 103e radeonkmsfw_RS780_pfp.ko
   111 0x825bb000 5b3f radeonkmsfw_RS780_me.ko
   121 0x825c1000 1338 radeonkmsfw_R600_rlc.ko

X is using the ati driver from the xf86-video-ati-7.9.0_1,1 package.

The evidence seems to be pointing toward the xf86-video-ati package being the
problem.  If I edit /etc/X11/xorg.conf to use the "vesa" driver rather than
the "radeon" driver the problem goes away.

But, of course, the vesa driver is low resolution and does not re-initialize the
console when I exit X.

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Does VirtualBox's vboxnetflt(4) work on stable/11 | 11.2?

2018-06-20 Thread Graham Menhennitt 
I'm on 11-Stable as of about a month ago. Works or me (although I don't 
stress it very much).


Graham

On 20/06/2018 04:30, Harry Schmalzbauer wrote:

Am 16.06.2018 um 21:42 schrieb Harry Schmalzbauer:
…
To rule out a known vboxnetflt(4) limitation/failure, I'd like to 
know if somebody successfully uses vboxnetflt(4) from 
virtualbox-ose-kmod-5.2.12 on stable/11|11.2.


Really nobody out there who has VirtualBox sucessfully running under 
stable/11 or 11.x with bridged network?


Anyone who tried, but also observed similar problems like I have on 
-current? 


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"