@bsd: "Hi, i have become fascinated with getting sched_ule to run reliably, and 
I've been running tests with about 8 different configurations.  I've 
listed some of them and the results at my website, at 
<url> the index html for which I've 
also attached to this email.  I have not yet succeeded in getting a core 
dump from the kernel, any advice on coaxing a kernel panic instead of a 
hang so that a core dump can be obtained, let me know.
The score is this, I get a hard hang (capslock/numlock do not respond, 
can't ping) when running XOrg, always after loading the program nicotine 
(ports/net/nicotine), which is a python/gtk2 program.  Sometimes, it has 
done a sudden reboot instead of a hang, and I haven't had much luck 
reproducing these results with any other program in X reliably.  Also, I 
have not had any hang at all when not running X.  As far as testing 
goes, ive generally recompiled the kernel with -j8 as a stress test, 
without XOrg, and have had no problems with any configuration.  So the 
bug on my system involving sched_ule seems to be brought out by 
something nicotine is doing within the first minute or so of loading 
up.  I do think that nicotine uses gdk threads, which use the posix 
threads, so the connection could be there...
I'm going to continue to search/test things as I think of them, but any 
advice as to what to check next would be helpful.
One thing that my results there don't list is the following:
 Never had a crash or hang with SMP disabled (even with sched_ule enabled).
Also never had a crash or hang with sched_4bsd and SMP enabled.
My system is a Tyan Tiger MP motherboard with dual athlon MPs.
Any other information that you might find helpful to know, let me know. 
Also: what other email lists should I post this too, if any?  Should I 
make this into a problem report?  sched_ule is already known to have 
problems...
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>""
    @bsd: "<quote>
I am actually aware of this.  I just thought my testing might be helpful
to someone.  Probably "everyone" is tied up with getting things together
for 5.4 release, I guess.  But nobody cares about sched_ule right now?
What about later?  Should I forward to -hackers or -current?
Not to waste anymore of anyone's time or bandwidth.  Its just that I am
having fun using this as excuse to learn about the inner workings of the
freebsd kernel.  ( Its a bit bigger but oh so much more well written
then NACHOS.. heh =P  )
_derek
_______________________________________________
<email_address> mailing list
<url>
To unsubscribe, send any mail to "<email_address>""
{'source': 'USENET', 'other_information': '{"reply_count": 1, "forum_name": "mpc.lists.freebsd.stable.20140728.mbox"}', 'file': 'data/output/usenet-mpc.lists.parquet'}