From owner-freebsd-current@FreeBSD.ORG  Thu Mar 21 21:30:19 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 56A191CE;
 Thu, 21 Mar 2013 21:30:19 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com
 [IPv6:2a00:1450:400c:c05::236])
 by mx1.freebsd.org (Postfix) with ESMTP id C4195BF7;
 Thu, 21 Mar 2013 21:30:18 +0000 (UTC)
Received: by mail-wi0-f182.google.com with SMTP id hi18so3647218wib.3
 for <multiple recipients>; Thu, 21 Mar 2013 14:30:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=IjgmQ3hYws1YlgRcu+3raF7whNzjK/5bg/ac6qFILH0=;
 b=yqJlBJ6+s6tUdxwiNlTW1AuION2YqcdED7tWeOoIZHBpvqc9FoIeMXrj0LnQUYOFCn
 AR5TbzsHu2MI9KFs4cWXUiIg2br53IJooSkISWITiG2fA2zJY7oZXasSC2INDaYYW9kR
 FfWmq7I6UH9DI6/HJjGwJE2FJeEInF+uTBPmJbwCBz9JU5MmP5kzTyK9DuBE5eXR+cpI
 i9zzITp2k4s2Dy8c9vnHWVaLNu0RO1+5Zee1Ne33mZ4MOWI6CzggRUuKSoH5//4wNtGQ
 ROqzxL6BB+eLv4Pya1axaZdf2UDtGs2FMW+axx4bNAJyASwpKwyTWquXQ1ZNxolIM+SE
 Eo9w==
MIME-Version: 1.0
X-Received: by 10.180.189.205 with SMTP id gk13mr4775851wic.25.1363901417966; 
 Thu, 21 Mar 2013 14:30:17 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.216.108.130 with HTTP; Thu, 21 Mar 2013 14:30:17 -0700 (PDT)
In-Reply-To: <514B748F.80009@gmail.com>
References: <514B748F.80009@gmail.com>
Date: Thu, 21 Mar 2013 14:30:17 -0700
X-Google-Sender-Auth: qXos8JgzPHZcI-mk-MKbHxPtN3w
Message-ID: <CAJ-Vmok-O0taV+mcs-jLiPb81-KkYu6kqgN-cG_zAVo_QhnTXA@mail.gmail.com>
Subject: Re: Kernel panics, one starting with r248508
From: Adrian Chadd <adrian@freebsd.org>
To: Joshua Isom <jrisom@gmail.com>, Konstantin Belousov <kib@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: freebsd-current@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Mar 2013 21:30:19 -0000

grr, another possible fallout from the unmapped io from kib?

Kib?



Adrian


On 21 March 2013 13:58, Joshua Isom <jrisom@gmail.com> wrote:
> I've been helping Adrian test the new ath improvements that support the
> chipset I have.  The first kernel panic is on my system if I have the cd
> driver loaded into the kernel, I would get a panic on boot.  While "Mounting
> local file systems:" it would panic with "Memory modified after free."
> Removing the driver solved it.  I'd rather have wireless than cd for right
> now anyway.  But a couple days ago a new build would always panic, a couple
> seconds after getty is spawned.  All I get is "panic: Bio too short
> 0xfffffe000b1395d0."  Before that, the builds worked other than occasional
> issues due to cleaning.  The only place that panic can be generated is
> geom_io.c so I'm guessing I can't just remove the driver.  What needs done
> so I can get a working kernel again?
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"