Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Mar 2003 15:15:45 -0800 (PST)
From:      =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= <mbsd@pacbell.net>
To:        current@FreeBSD.ORG
Subject:   Re: -CURRENT + cvs = panic
Message-ID:  <20030303150427.M6008-100000@atlas.home>
In-Reply-To: <20030304003148.K636@kushnir1.kiev.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
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 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.
> >
> > 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/netinet/tcp_input.c:2324
> >
> > Do you have version 1.198 of sys/netinet/tcp_input.c?  I haven't had
> > that panic since then (i.e. for the last four days).
> >
> > Bye, Philipp
> >
> Yes:
> src/sys/netinet/tcp_input.c,v 1.198 2003/02/26 18:20:41
> Doesn't help, though. Of all "cvs up ..." or "cvsup ..." there was 1 or 2
> that did not panic :-(

Just to chime in: I get these panics almost daily on my laptop since
the last update (including tcp_input.c 1.198).  They used to happen
before as well, but less frequently.  Sadly, I no longer seem to get
crashdumps, but back when I did get them, the code path looked the
same (trap somewhere in tcp_input).

The crashes can happen at any time, even under very light load and are
invariably preceeded by the mouse freezing up, then a flurry of
error messages like:

  psmintr: delay too long; resetting byte count
  psmintr: out of sync (0000 != 0080).
  psmintr: discard a byte (1).
  psmintr: delay too long; resetting byte count
  psmintr: out of sync (0000 != 0080).
  psmintr: discard a byte (1).

Then the mouse recovers, but after that it looks like almost any
network activity will trigger a panic.  WITNESS does not print
anything.

  $.02,
  /Mikko

(Since the d*mn ACPI does not work anyway, I predict a "downgrade" to
 4.8 in the near future...)


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




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