Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Oct 2002 01:10:06 -0700 (PDT)
From:      Roger Hardiman <roger@FreeBSD.org>
To:        roger@FreeBSD.org, roger@FreeBSD.org, freebsd-bugs@FreeBSD.org
Subject:   Re: kern/38883: 'kldload bktr' stuck in state swwrt, exercising the disk
Message-ID:  <200210080810.g988A6fZ023559@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
Synopsis: 'kldload bktr' stuck in state swwrt, exercising the disk

Responsible-Changed-From-To: roger->freebsd-bugs
Responsible-Changed-By: roger
Responsible-Changed-When: Tue Oct 8 01:03:32 PDT 2002
Responsible-Changed-Why: 
It is not a bug wih the bktr driver. The bug lies in the kernel's
contiguous memory allocation function which never returns.

There is no way to check in advance if the contiguous memory
callocation will pass or fail. When the bktr driver loads, it asks for
contiguous memory.
Contiguous memory is memory which is not fragmented and so you only
get contiguous memory at boot time, or shortly after booting before large
programs have run.
So, on my own machines, I can boot, run a few small programs
and then kldload the bktr driver.
But if I start X and then quit X, I cannot load it because memory
is fragmented.

So, the problem is the kernel's memory allocation routine failing to
return memory or an error.
There is nothing the bktr driver can do.



http://www.freebsd.org/cgi/query-pr.cgi?pr=38883

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210080810.g988A6fZ023559>