On Tue, 4 Mar 2003, Vladimir Kushnir wrote:
> On Mon, 3 Mar 2003, Philipp Mergenthaler wrote:
>
> > On Mon, Mar 03, 2003 at 01:23:20AM +0200, Vladimir Kushnir wrote:
> > > Practically 100% repeatable: after some CVS updates (not sure but it
> > > seems after another high HD load as well) -CURRENT
On Mon, 3 Mar 2003, Philipp Mergenthaler wrote:
> On Mon, Mar 03, 2003 at 01:23:20AM +0200, Vladimir Kushnir wrote:
> > Practically 100% repeatable: after some CVS updates (not sure but it
> > seems after another high HD load as well) -CURRENT panics with
> > bwrite: buffer is not busy
> > (in the
On Mon, Mar 03, 2003 at 11:01:22AM +0100, Philipp Mergenthaler wrote:
> In that gdb trace, I think the panic was only an aftereffect and
> the trouble started here:
> #15 0xc02bc1c8 in calltrap () at {standard input}:96
> #16 0xc021fd79 in tcp_input (m=0xc0d49c30, off0=20)
> at /usr/src/sys/ne
On Mon, Mar 03, 2003 at 01:23:20AM +0200, Vladimir Kushnir wrote:
> Practically 100% repeatable: after some CVS updates (not sure but it
> seems after another high HD load as well) -CURRENT panics with
> bwrite: buffer is not busy
> (in the prefious message I've attached gdb trace and so on, and no
Practically 100% repeatable: after some CVS updates (not sure but it
seems after another high HD load as well) -CURRENT panics with
bwrite: buffer is not busy
(in the prefious message I've attached gdb trace and so on, and nothing
has changed so far).
It goes on for at least several days now.
Rega
