[Bug 195262] [lor] Possibly two LORs: entropy harvest mutex and scrlock, and entropy harvest mutex and sleepq chain

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195262 Xin LI changed: What|Removed |Added Status|New |Open --- Comment #7 from Xin LI --- (In

[Bug 197989] gpart(8) can't define start for new partition

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197989 Andrey V. Elsukov changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|a...@freebsd.org -- You are r

[Bug 197989] gpart(8) can't define start for new partition

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197989 --- Comment #4 from Andrey V. Elsukov --- (In reply to timp87 from comment #3) > The first partition has been added from 792 and it is a bit strange. Why not > earlier? from 40 for example. This is because your disk has logical block size

[Bug 195262] [lor] Possibly two LORs: entropy harvest mutex and scrlock, and entropy harvest mutex and sleepq chain

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195262 --- Comment #6 from John Baldwin --- If this fixes the LOR report, then this looks good to me. Xin, can you commit this? -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 195262] [lor] Possibly two LORs: entropy harvest mutex and scrlock, and entropy harvest mutex and sleepq chain

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195262 --- Comment #5 from Ellis H. Wilson III --- I believe we have a patch here that works, at least per my testing. What are the correct next steps in terms of moving this along? -- You are receiving this mail because: You are the assignee f

[Bug 189958] crypt(1): broken /usr/bin/crypt [regression]

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=189958 --- Comment #2 from commit-h...@freebsd.org --- A commit references this bug: Author: delphij Date: Wed Feb 25 20:47:26 UTC 2015 New revision: 279296 URL: https://svnweb.freebsd.org/changeset/base/279296 Log: Explicitly crypt_set_format(

[Bug 198043] Updated OpenSSH no longer uses FQDN in known_hosts

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198043 Bug ID: 198043 Summary: Updated OpenSSH no longer uses FQDN in known_hosts Product: Base System Version: 10.1-RELEASE Hardware: Any OS: Any Status: New

[Bug 193802] tso seems broken on RELENG10 for version 7.4.2 of em driver

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193802 Friedrich Volkmann changed: What|Removed |Added CC||b...@volki.at --- Comment #1

[Bug 198035] Make freebsd-version output revision information for non-release builds

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198035 Bug ID: 198035 Summary: Make freebsd-version output revision information for non-release builds Product: Base System Version: 10.1-STABLE Hardware: Any

[Bug 198014] Signals can lead to an inconsistency in PI mutex ownership

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198014 --- Comment #12 from e...@vangyzen.net --- (In reply to Konstantin Belousov from comment #11) OK, we can ignore the foreign owner. I've tested that code quite a bit already. I'll change the comments, as you suggest. -- You are receiving

[Bug 198014] Signals can lead to an inconsistency in PI mutex ownership

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198014 e...@vangyzen.net changed: What|Removed |Added Attachment #153475|0 |1 is obsolete|

[Bug 197535] [re] [panic] if_re (Realtek 8168) causes memory write after free and kernel panic

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197535 --- Comment #10 from luca.pizzamig...@gmail.com --- Finally, I get the behavior of the my re0 interface, unfortunately, still without solution. When the driver gets a new descriptor on the rxring, the mbuf is still full of 0xdeadcode. The

[Bug 198014] Signals can lead to an inconsistency in PI mutex ownership

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198014 --- Comment #11 from Konstantin Belousov --- (In reply to eric from comment #10) I do not have an opinion which case currently is handled more correctly. I tend to agree with notion that empty case handling of silent ignore of the foreign

[Bug 198014] Signals can lead to an inconsistency in PI mutex ownership

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198014 --- Comment #10 from e...@vangyzen.net --- I considered this, but I'm indecisive. The current "userland messed the mutex" error path compounds the problem by leaving the umutex owned by the current thread, while libthr already disowned the

[Bug 198014] Signals can lead to an inconsistency in PI mutex ownership

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198014 --- Comment #9 from Konstantin Belousov --- I agree with all three patches, with one detail. In the first patch, which does umtx_pi_disown() for empty queue, shouldn't the case of pi->pi_owner != curthread be handled the same as it is done

[Bug 198030] /usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory on freebsd-update install

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198030 Bug ID: 198030 Summary: /usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory on freebsd-update install Product: Base System Version: 10.1-RELEASE Har

[Bug 197922] [patch] [sched] Remove random() from sched_ule, add short circuit for non-SMP, non-balancing

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197922 Harrison Grundy changed: What|Removed |Added Attachment #153515|0 |1 is obsolete|

[Bug 197922] [patch] [sched] Remove random() from sched_ule, add short circuit for non-SMP, non-balancing

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197922 --- Comment #6 from Harrison Grundy --- Created attachment 153515 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=153515&action=edit No randomness in scheduler at all -- You are receiving this mail because: You are the assignee

[Bug 197922] [patch] [sched] Remove random() from sched_ule, add short circuit for non-SMP, non-balancing

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197922 Harrison Grundy changed: What|Removed |Added Attachment #153513|0 |1 is obsolete|

[Bug 197922] [patch] [sched] Remove random() from sched_ule, add short circuit for non-SMP, non-balancing

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197922 --- Comment #4 from Harrison Grundy --- (In reply to Ivan Klymenko from comment #3) Each of the 3 patches solves the problem in a slightly different way. There's some discussion on -arch about which approach makes the most sense here, so I

Hanging Egg Chair

2015-02-25 Thread ImporterDeals
Importer Deals Hand - Woven White Egg Chair: http://rdir.importerdeals.com.au/d/d.html?q0vy00jris00dlyi000cmyxy5 240 Watt Solar Folding - $290: http://rdir.importerdeals.com.au/d/d.html?q0qi00jris00dlyi000cczqq5 Safe Wash - $299: http://rdir.importerdeals.com.au/d

[Bug 197922] [patch] [sched] Remove random() from sched_ule, add short circuit for non-SMP, non-balancing

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197922 Ivan Klymenko changed: What|Removed |Added CC||fi...@ukr.net --- Comment #3 from

[Bug 197922] [patch] [sched] Remove random() from sched_ule, add short circuit for non-SMP, non-balancing

2015-02-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197922 --- Comment #2 from Harrison Grundy --- Created attachment 153513 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=153513&action=edit Creates sched_random, using the system used in cpu_search. Another option. If this doesn't work