headers
Stefan Krüger | 2 Feb 2012 15:36
Picon
Picon

Re: trouble building/loading crypto.ko

On Mon, 30 Jan 2012, Stefan Krüger wrote:

> Hi,
> 
> ...
> 
> # kldload crypto
> cryptosoft0: <software crypto> on motherboard
> spin_lock: 0xffffffff830601c0, indefinite wait (1 secs)!
> ... bunch of indefinite waits
> Trace beginning at frame 0xffffffe0a7443be0
> spin_lock_contested() at spin_lock_contested+0xd4 0xffffffff8032e989
> spin_lock_contested() at spin_lock_contested+0xd4 0xffffffff8032e989
> lockmgr() at lockmgr+0x8e 0xffffffff80309317
> crypto_ret_proc() at crypto_ret_proc+0x22 0xffffffff8303d43b
> ... some more indefinite waits
> spin_lock: 0xffffffff830601c0, indefinite wait (59 secs)!
> panic: spin_lock: 0xffffffff830601c0, indefinite wait!
> 
> cpuid = 1
> Trace beginning at frame 0xffffffe0a7443b60
> panic() at panic+0x1fb 0xffffffff803186ad
> panic() at panic+0x1fb 0xffffffff803186ad
> spin_lock_contested() at spin_lock_contested+0x104 0xffffffff8032e9b9
> lockmgr() at lockmgr+0x8e 0xffffffff80309317
> crypto_ret_proc() at crypto_ret_proc+0x22 0xffffffff8303d43b
> Debugger("panic")
> 
> And I'm pretty stuck on this one :(
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thomas Nikolajsen | 2 Feb 2012 23:19
Picon

Re: trouble building/loading crypto.ko

>> .. but now I get this:
>>
>># kldload crypto
>>cryptosoft0: <software crypto> on motherboard
>>spin_lock: 0xffffffff830601c0, indefinite wait (1 secs)!
>
>Please open a bug (submit to bugs <at>  or use http://bugs.dragobflybsd.org),
>this will make it easier to handle, e.g. get it resolved in 3.0 before release.

Current master now works here;
could be nice to have it MFC'ed to rel3.0.

 -thomas
Permalink | Reply | 0 comments |
headers
Justin Sherrill | 6 Feb 2012 05:28
Favicon
Gravatar

Google Summer of Code 2012

Google Summer of Code for 2012 has been announced - it'd be nice for
DragonFly to participate for the 5th (!) time.  I'll administrate
again, unless someone else is hungry for it.

http://google-opensource.blogspot.com/2012/02/google-summer-of-code-2012-is-on.html

This leads to the usual questions:

1: Who wants to mentor?  You have to be willing to spend April 23rd
through August 24th helping a student, and some time before that
looking at and ranking project proposals.  There's not much formal
organization past "get the student moving".

2: Who wants to be a student?  Generally you qualify by being a
college student.  You have to put in a decent amount of work; this is
your summer job.

3: Who has project ideas?  This can be anyone.  We have an existing
projects page, but more ideas that are suitable in scope for students
are always welcome.

http://www.dragonflybsd.org/docs/developer/ProjectsPage/ (The existing
general projects page)

We can apply as an organization starting the 27th.  I need at least a
couple people willing to mentor so that I know it's worth putting in
the application.
Permalink | Reply | 1 comment |
headers
Alex Hornung | 6 Feb 2012 08:01
Picon
Gravatar

Re: Google Summer of Code 2012

I'll gladly mentor again.

Cheers,
Alex

On 6 Feb 2012, at 04:28, Justin Sherrill <justin <at> shiningsilence.com> wrote:

> Google Summer of Code for 2012 has been announced - it'd be nice for
> DragonFly to participate for the 5th (!) time.  I'll administrate
> again, unless someone else is hungry for it.
> 
> http://google-opensource.blogspot.com/2012/02/google-summer-of-code-2012-is-on.html
> 
> This leads to the usual questions:
> 
> 1: Who wants to mentor?  You have to be willing to spend April 23rd
> through August 24th helping a student, and some time before that
> looking at and ranking project proposals.  There's not much formal
> organization past "get the student moving".
> 
> 2: Who wants to be a student?  Generally you qualify by being a
> college student.  You have to put in a decent amount of work; this is
> your summer job.
> 
> 3: Who has project ideas?  This can be anyone.  We have an existing
> projects page, but more ideas that are suitable in scope for students
> are always welcome.
> 
> http://www.dragonflybsd.org/docs/developer/ProjectsPage/ (The existing
> general projects page)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Thomas Nikolajsen | 11 Feb 2012 07:17
Picon

Re: 3.0 release planning

>My guestimate is that I'll tag tomorrow, and release in roughly a week.
>
>Tell me if this plan doesn't work for you.

How is the release progressing?

From issue 2286 (3.0 release catchall ticket)
http://bugs.dragonflybsd.org/issues/2286
it seems like we still have a few bugs we need to resolve.
(our bugs system shows a nice list of related issues)

 -thomas
Permalink | Reply | 3 comments |
headers
Justin Sherrill | 11 Feb 2012 19:57
Favicon
Gravatar

Re: 3.0 release planning

On Sat, Feb 11, 2012 at 1:17 AM, Thomas Nikolajsen
<thomas.nikolajsen <at> mail.dk> wrote:

> How is the release progressing?
>
> From issue 2286 (3.0 release catchall ticket)
> http://bugs.dragonflybsd.org/issues/2286
> it seems like we still have a few bugs we need to resolve.
> (our bugs system shows a nice list of related issues)

It's pretty much as you saw it - those bugs attached to the ticket are
all the remaining issues.  We have packages built, and the release
notes are partially written.  That's 7 bugs to kill.
Permalink | Reply | 2 comments |
headers
Dmitrij D. Czarkoff | 13 Feb 2012 11:26
Picon
Gravatar

Re: 3.0 release planning

On Sat, 2012-02-11 at 13:57 -0500, Justin Sherrill wrote:
> It's pretty much as you saw it - those bugs attached to the ticket are
> all the remaining issues.  We have packages built, and the release
> notes are partially written.  That's 7 bugs to kill.

The ticket contains a comment about the packages' rebuild needed, which
is pretty much the opposite. Any insight on that?

--

-- 
Dmitrij D. Czarkoff
Permalink | Reply | 1 comment |
headers
John Marino | 13 Feb 2012 12:39
Favicon

Re: 3.0 release planning

On 2/13/2012 11:26, Dmitrij D. Czarkoff wrote:
> On Sat, 2012-02-11 at 13:57 -0500, Justin Sherrill wrote:
>> It's pretty much as you saw it - those bugs attached to the ticket are
>> all the remaining issues.  We have packages built, and the release
>> notes are partially written.  That's 7 bugs to kill.
>
> The ticket contains a comment about the packages' rebuild needed, which
> is pretty much the opposite. Any insight on that?
>

To clarify, the packages that are already built are fine.  There are a 
few hundred packages that did not build for a couple of different 
reasons, so the ticket is making a comment that a "delta" build still 
needs to occur to get these missing packages.

John
Permalink | Reply | 0 comments |
headers
Justin Sherrill | 17 Feb 2012 04:04
Favicon
Gravatar

3.0 release this weekend

I'm aiming to tag 3.0.1 this weekend and upload images.  There's 5
bugs still linked on the catchall 3.0 ticket:

http://bugs.dragonflybsd.org/issues/2286

... but I don't think they are worth holding up the release.  If
anyone wants to try to close them in the next 48 hours or so, please
do.  We're short a relatively small number of binary pkgsrc packages
(mostly ruby-related, I think), but they'll be uploaded after the next
build finishes.

If anyone wants to add to the release page, I'd appreciate it:

http://www.dragonflybsd.org/release30/

I'm going to be digging through git log and past Digest articles to
make sure I have everything, but extra eyes never hurt.
Permalink | Reply | 2 comments |
headers
John Marino | 17 Feb 2012 23:40
Favicon

Re: 3.0 release this weekend

On 2/17/2012 4:04 AM, Justin Sherrill wrote:
> We're short a relatively small number of binary pkgsrc packages
> (mostly ruby-related, I think), but they'll be uploaded after the next
> build finishes.

I understand the important news here is that there is another build 
ongoing and delta packages will be uploaded when it's finished.  I just 
to to clarify:
1) The "small number" is likely around 10% of the buildable packages, so 
we're talking roughly about a 1000 packages
2) Ruby was one issue, the separate DSO issue took out the esound 
package which broke nearly 400 dependent packages, most of which were 
multimedia.  Those are popular packages.  I remember kde3 was one of the 
victims.

Question since I haven't been around the last week:
Is the bulkbuild problem with ruby fixed?

John
Permalink | Reply | 1 comment |

Gmane