once again:
KDB: stack backtrace:
db_trace_self_wrapper(c074b5ee,e70c79ac,c05b6853,c4b8c420,e70c79ac,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c4b8c420,e70c79ac,c07025c5,e70c79bc,c4c002b8,...) at
kdb_backtrace+0x29
vfs_badlock(c4a31900,e70c79bc,c07b00a0,c4c002b8,c4b8c420) at vfs_badlock+0x2
On Thu, Mar 20, 2008 at 10:20 AM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
> [..]
> This is likely to be a unionfs bug.
>
unionfs_close: warning: open count is 0
unionfs_close: warning: open count is 0
unionfs_close: warning: open count is 0
unionfs_close: warning: open count is 0
unionfs_close:
On Thu, Mar 20, 2008 at 10:20 AM, Kris Kennaway <[EMAIL PROTECTED]> wrote:
>
> Brad Pitney wrote:
> > Not sure why it keeps wedging, at first I thought it was something to
> > do with the LORs, now after adding some more debugging options I
> > think
Not sure why it keeps wedging, at first I thought it was something to
do with the LORs, now after adding some more debugging options I
think I might have found the answer!
KDB: stack backtrace:
db_trace_self_wrapper(c074b5ee,e70599ac,c05b6853,c4a9e000,e70599ac,...)
at db_trace_self_wrapper+0x26
k
On Wed, Mar 19, 2008 at 7:46 PM, Kevin K <[EMAIL PROTECTED]> wrote:
> > That said: I do understand what you're saying, and yes, I can see why
> > you would want that. It does make sense, and it's reasonable. It's
> > just hard to achieve. I don't think other mainstream OSes (e.g. Linux)
> > o
On Mon, Mar 17, 2008 at 5:29 AM, peter stern <[EMAIL PROTECTED]> wrote:
> I'd appreciate suggestions on how to get a working xorg from the mess 6.3
> shipped with. I've been using FreeBSD since 2.2 and have never had much
> trouble with it until the 6 branch was released. My hardware is pretty
>
