Re: 7B4 scheduling question

2007-12-30 Thread Kris Kennaway

Chris H. wrote:

Greetings,
I realize that the answer to this question is subject to many
possible variables. But I would greatly apreciate a ventured guess
from anyone willing to do so.
Question being: Is ULE considered the best sceduler in 7-CURRENT?
If not, what might be considered the best?

FWIW this is for a SMP board (2 CPU's)

Thank you for all your time and considerstion.



Yes, ULE is the recommended scheduler.

Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: PR backlog [was: Re: usb/umass, devfs: this sucks]

2007-12-30 Thread Alexander Leidinger
Quoting Mark Linimon [EMAIL PROTECTED] (from Sat, 29 Dec 2007  
22:26:02 -0600):



On Sun, Dec 30, 2007 at 01:01:19AM +0100, Alexander Leidinger wrote:

Quoting Mark Linimon [EMAIL PROTECTED] (from Wed, 26 Dec 2007
12:04:15 -0600):

 - The creation of a weekly posting bugs the bugmeister team thinks are
   ready for commit.  This doesn't seem to have attracted the desired
   attention.  Perhaps this is a problem of push not being the right
   solution here; perhaps it just hasn't been publicized enough.

Where is/was this mail send to?


  To: [EMAIL PROTECTED]
  Subject: PRs recommended for committer evaluation by the bugbusting team

It's sent out weekly.


So only people which are on bugbusters@ receive it. If someone is  
interested in this but is not interested in the other bugbusters@  
mails, they will not see it.


What about an experiment: send those mails (additionally) to hackers@  
or [EMAIL PROTECTED]


Bye,
Alexander.

--
Beware of self-styled experts: an ex is a has-been, and a spurt is a
drip under pressure.

http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org   netchild @ FreeBSD.org  : PGP ID = 72077137
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: RELENG_7 jerky mouse and skipping sound (still a problem -BETA3)

2007-12-30 Thread Kris Kennaway

Kip Macy wrote:

On Nov 19, 2007 9:53 AM, Anish Mistry [EMAIL PROTECTED] wrote:

On Wednesday 07 November 2007, Anish Mistry wrote:

On Monday 05 November 2007, [LoN]Kamikaze wrote:

Marc Fonvieille wrote:

On Thu, Oct 18, 2007 at 05:53:47PM +0200, [LoN]Kamikaze wrote:

Anish Mistry wrote:

On Thursday 18 October 2007, Marc Fonvieille wrote:

On Wed, Oct 17, 2007 at 12:28:30PM -0400, Anish Mistry wrote:

I just updated to RELENG_7 from 6.2 and I'm running into
some really annoying issues with jerky mouse movement and
skipping sound.  This seems to be similar to:
Re: SCHED_4BSD in RELENG_7 disturbs workflow
This happens both with 4BSD and ULE.

I seems to happen when I'm compiling ports and a new
cc/bzip2/sh process fires off (I'm just watching top), I'll
get the skip/freezeup.

[...]

Using ULE and UP kernel (i.e. without SMP etc.) helped a bit
the things but it's still very annoying to use firefox
during ports build.  I see this lag/freeze on all boxes I
use with 7.0, but it's true that with a fast machine people
can ignore the problem, it's less obvious than with a 1GHz
box for example.

Yeah, I'm still seeing this behavior.  Does anyone have
suggestions on debugging?

Thanks,

I did post the solution in this thread.

It has nothing to do with the mouse.

Does the problem persist for you? It's gone for me, even with
moused.

Yes, the problem seems to have been fixed.  I'm back to
kern.hz=1000 and removed FULL_PREEMPTION.  No skipping.

It looks like I spoke too soon.  I've just tried to compile miro and
as it was compiling the boost-python dependency I noticed the problem
again.  Switching kern.hz=100 seems to fix the problem.  Can any of
the developers in this area reproduce the issue?  It's pretty easy to
reproduce on my 1.33Ghz Athlon.


There is an ithread priority inversion bug that might be causing this.
The fix for that should be going in shortly.

 -Kip
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]




Anish,

Can you confirm that this fix helped for you?  i.e. do you still see the 
problem?


Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: 7B4 scheduling question

2007-12-30 Thread Chris H.

Quoting Kris Kennaway [EMAIL PROTECTED]:


Chris H. wrote:

Greetings,
I realize that the answer to this question is subject to many
possible variables. But I would greatly apreciate a ventured guess
from anyone willing to do so.
Question being: Is ULE considered the best sceduler in 7-CURRENT?
If not, what might be considered the best?

FWIW this is for a SMP board (2 CPU's)

Thank you for all your time and considerstion.



Yes, ULE is the recommended scheduler.

Kris


WOW! That was fast. :)
Thank you Kris.


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]





--
panic: kernel trap (ignored)



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Repeated crashes in 6.3-PRERELEASE

2007-12-30 Thread Frank Mayhar
On Sat, 2007-12-29 at 11:28 -0800, Frank Mayhar wrote:
 This is on a very recent -stable (like, as of just a couple of days
 ago).  Doing nothing in particular, ZERO_COPY_SOCKETS _not_ specified in
 the config.  This has happened twice this morning; if it happens again
 I'll drop back to my older kernel, built back in May.

Sigh.  In the last three days I've had no fewer than four crashes:  This
one, another just like it that I didn't get a dump for, a Fatal trap
12: page fault while in kernel mode in buf_splay():

#27 0x802e2cb4 in buf_splay (lblkno=0, xflags=2 '\002', root=0x9000)
at /usr/src/sys/kern/vfs_subr.c:1339
#28 0x802e2e08 in buf_vlist_remove (bp=0xa1919340)
at /usr/src/sys/kern/vfs_subr.c:1371
#29 0x802e4dab in brelvp (bp=0xa1919340)
at /usr/src/sys/kern/vfs_subr.c:1502
#30 0x802d28f1 in getnewbuf (slpflag=0, slptimeo=0, size=2, 
maxsize=16384) at /usr/src/sys/kern/vfs_bio.c:1801

(where bp-b_left is 0x9000)

and a panic: backgroundwritedone: lost buffer.  I have a dump for each
of the three unique scenarios.  At the moment I've dropped back to the
older kernel and am keeping my fingers crossed that it will run okay.
I'm beginning to suspect hardware, although as two of the three are in
the buf code there might be a problem there...  If it continues with the
older kernel then it is most likely hardware but if not then there's a
problem.

Has anyone else encountered anything like this in 6.3-PRERELEASE?
-- 
Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/
Exit Consulting http://www.gpsclock.com/
http://www.exit.com/blog/frank/
http://www.zazzle.com/fmayhar*
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Repeated crashes in 6.3-PRERELEASE

2007-12-30 Thread Kris Kennaway

Frank Mayhar wrote:

On Sat, 2007-12-29 at 11:28 -0800, Frank Mayhar wrote:

This is on a very recent -stable (like, as of just a couple of days
ago).  Doing nothing in particular, ZERO_COPY_SOCKETS _not_ specified in
the config.  This has happened twice this morning; if it happens again
I'll drop back to my older kernel, built back in May.


Sigh.  In the last three days I've had no fewer than four crashes:  This
one, another just like it that I didn't get a dump for, a Fatal trap
12: page fault while in kernel mode in buf_splay():

#27 0x802e2cb4 in buf_splay (lblkno=0, xflags=2 '\002', root=0x9000)
at /usr/src/sys/kern/vfs_subr.c:1339
#28 0x802e2e08 in buf_vlist_remove (bp=0xa1919340)
at /usr/src/sys/kern/vfs_subr.c:1371
#29 0x802e4dab in brelvp (bp=0xa1919340)
at /usr/src/sys/kern/vfs_subr.c:1502
#30 0x802d28f1 in getnewbuf (slpflag=0, slptimeo=0, size=2, 
maxsize=16384) at /usr/src/sys/kern/vfs_bio.c:1801


(where bp-b_left is 0x9000)

and a panic: backgroundwritedone: lost buffer.  I have a dump for each
of the three unique scenarios.  At the moment I've dropped back to the
older kernel and am keeping my fingers crossed that it will run okay.
I'm beginning to suspect hardware, although as two of the three are in
the buf code there might be a problem there...  If it continues with the
older kernel then it is most likely hardware but if not then there's a
problem.

Has anyone else encountered anything like this in 6.3-PRERELEASE?


Sounds pretty unusual (and e.g. I've not seen other reports of this), 
but if you are *still* able to run an older kernel without incident then 
maybe there was an intervening change that interacts badly with your 
particular hardware.  A binary search might be necessary to determine 
the cause, in that case.


Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: I just broke out of a FreeBSD jail.. Known bug??

2007-12-30 Thread Robert Watson

On Fri, 28 Dec 2007, Johan Ström wrote:


On Dec 28, 2007, at 13:41 , Edwin Groothuis wrote:


On Fri, Dec 28, 2007 at 01:15:38PM +0100, Johan Str?m wrote:
Thats my home dir on core!.. That should very much not be visible there! I 
have full access now (from the wrong jail!)


Known bug or did I just stumble upon something pretty bad??


You didn't really break out of it, the person who managed the machine did 
something he shouldn't have done: Moving the directories while the jail(s) 
were running. It should be mentioned in the BUGS section of the jail(8) 
command.


Yes, thats true.. Without super-root doing that the breakout would never 
happen. But still a bug, so yes I guess it should be mentioned in BUGS (and 
handbook too? not sure where this kind of special features are noted) 
unless its fixed.


While the results are potentially confusing, this is actually an intentional 
design choice. Jails are not intended to provide complete isolation, rather, 
unintrusive and low-overhead containment.  As long as untrusted processes are 
working with the file system namespace exposed to the jail, the privileged 
root user should be very cautious about trusting those bits of namespace, just 
as they should be cautious with bits of file system namespace writable by 
regular users.  In order to prevent these kinds of issues, we'd need to use 
more intensive isolation of the file system components visible in the jail, 
such as allowing access to a particular object only within or outside of 
the jail, rather than both.  If the man page doesn't have a cautionary note on 
users outside the jail trusting data in the jail, it should do so.


Robert N M Watson
Computer Laboratory
University of Cambridge___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: RELENG_7 jerky mouse and skipping sound (still a problem -BETA3)

2007-12-30 Thread David E. Thiel
On Sun, Dec 30, 2007 at 01:50:30PM +0100, Kris Kennaway wrote:
 There is an ithread priority inversion bug that might be causing this.
 The fix for that should be going in shortly.
 
 Anish,
 
 Can you confirm that this fix helped for you?  i.e. do you still see the 
 problem?

FWIW, the problem remains for me. Still terrible performance
during compiles.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: RELENG_7 jerky mouse and skipping sound (still a problem -BETA3)

2007-12-30 Thread Kris Kennaway

David E. Thiel wrote:

On Sun, Dec 30, 2007 at 01:50:30PM +0100, Kris Kennaway wrote:

There is an ithread priority inversion bug that might be causing this.
The fix for that should be going in shortly.

Anish,

Can you confirm that this fix helped for you?  i.e. do you still see the 
problem?


FWIW, the problem remains for me. Still terrible performance
during compiles.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]




OK.  Instead of going over all of the usual questions again, can you 
point me to a previous mail in which you explain your observations and 
test results in detail?


Kris
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: RELENG_7 jerky mouse and skipping sound (still a problem -BETA3)

2007-12-30 Thread David E. Thiel
On Sun, Dec 30, 2007 at 11:12:26PM +0100, Kris Kennaway wrote:
 FWIW, the problem remains for me. Still terrible performance
 during compiles.
 
 OK.  Instead of going over all of the usual questions again, can you point 
 me to a previous mail in which you explain your observations and test 
 results in detail?

The most recent is http://marc.info/?l=freebsd-stablem=119428719505129w=2, but
it started way back at 
http://marc.info/?l=freebsd-currentm=118998090512027w=2.

I've tried a lot of stuff in between, and all I've been able to narrow
it down to is that it's not a display driver issue, and that none of
my swap partition is getting used, so that's not the problem. During
compiles, my UP system with ULE still gets very unresponsive when
compiling, sometimes taking up to 10 seconds just to draw a new terminal
window. Even changing focus with the window manager can take several
seconds. I'd like to provide more info, but I'm not sure what stats
are useful for this particular issue. Please let me know. 

dmesg is at http://redundancy.redundancy.org/dmesg.txt, and kernel
config is at http://redundancy.redundancy.org/DEEPTHOUGHT. Even though
I'm still getting reported 80-95% memory utilization and no paging,
I'm going to get an extra gig of RAM on order to see if that improves
things. 2G of ram for a desktop, what's the world coming to? ;)

Thanks,
David
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]