From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 00:04:51 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 002C616A4CE; Wed, 29 Sep 2004 00:04:50 +0000 (GMT) Received: from pilchuck.reedmedia.net (pilchuck.reedmedia.net [209.166.74.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 629AB43D45; Wed, 29 Sep 2004 00:04:50 +0000 (GMT) (envelope-from reed@reedmedia.net) Received: from reed by pilchuck.reedmedia.net with local-esmtp (Exim 3.12 #1 (Debian)) id 1CCRxd-0001lq-00; Tue, 28 Sep 2004 17:04:45 -0700 Date: Tue, 28 Sep 2004 17:04:44 -0700 (PDT) From: "Jeremy C. Reed" To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 29 Sep 2004 11:54:18 +0000 Subject: Re: panic "bio_completed can't be greater than bio_length" on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 00:04:51 -0000 > Anyone seeing this? > > panic("bio_completed can't be greater than bio_length") I upgraded and old laptop running 5.1 to -current this week. I have had that message twice. Once on first reboot with new kernel but old userland when I ran "fsck /usr". I typed in my notes: ad0: TIMEOUT - READ retrying (2 retries left) LBA=235520522 panic: bio_completed can't be greater than bio_length cpuid = 0 KDB: enter: panic [thread 100027] Stopped at kdb_enter+0x2b: nop db> I thought this was because of old fsck. So I rebooted, didn't run fsck, and finished the install of userland. Later, I started receiving random messages like: ad0: TIMEOUT - READ retrying (2 retries left) LBA=101139222 ad0: WARNING - WRITE no interrupt but good status (four times) It went into kernel debugger again (but I don't know when): panic: bio_completed can't be greater than bio_length cpuid = 0 KDB: enter: panic [thread 100027] Stopped at kdb_enter+0x2b: nop db> It sits at that prompt now. I am running OLDCARD kernel. (I don't know if it is needed still, but I had to use it before.) Jeremy C. Reed p.s. Please CC me on replies.