From owner-freebsd-ppc@FreeBSD.ORG  Wed Jun  5 03:35:11 2013
Return-Path: <owner-freebsd-ppc@FreeBSD.ORG>
Delivered-To: freebsd-ppc@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 72BDC99F
 for <freebsd-ppc@freebsd.org>; Wed,  5 Jun 2013 03:35:11 +0000 (UTC)
 (envelope-from chmeeedalf@gmail.com)
Received: from mail-bk0-x232.google.com (mail-bk0-x232.google.com
 [IPv6:2a00:1450:4008:c01::232])
 by mx1.freebsd.org (Postfix) with ESMTP id 0B2151FC5
 for <freebsd-ppc@freebsd.org>; Wed,  5 Jun 2013 03:35:10 +0000 (UTC)
Received: by mail-bk0-f50.google.com with SMTP id ik5so560718bkc.9
 for <freebsd-ppc@freebsd.org>; Tue, 04 Jun 2013 20:35:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:date:x-google-sender-auth:message-id:subject
 :from:to:content-type;
 bh=FBZI+cKDpr3JIk+2SOZosduYjur4yB+v6TRsljYJPkE=;
 b=q+2WAQCG9t7sqb97aygsObk38nR9NfZZ+SgPOILWBPn8u3yIdApmHrEvxfr8FW8RRF
 eqRl0ea6SoHRRnHX2B1oo0i829wSfLNX6+jGC0dtO02DYvHG5Yq42CpX56VibiFWPpyK
 Arkk7uY3HtZPC1chUDdqcvSdxUE67Popc4Ydr/LslhIH0ySjhx3WT+f41ntW7Qepru10
 8OERondZcxwxMDTLx0/0iU7KknOHScnGR5awtJWfolP083RxjUOaz5kxjxgrMEO6Pw3J
 gKxPxoMQIe77n5tjdIZbnr+hmPQswOMBQfJOmZ2Vs1oBy8XREQpL33HN50BHFFY0VncI
 uN2g==
MIME-Version: 1.0
X-Received: by 10.205.36.138 with SMTP id ta10mr8947605bkb.4.1370403310091;
 Tue, 04 Jun 2013 20:35:10 -0700 (PDT)
Sender: chmeeedalf@gmail.com
Received: by 10.204.236.132 with HTTP; Tue, 4 Jun 2013 20:35:10 -0700 (PDT)
Date: Tue, 4 Jun 2013 20:35:10 -0700
X-Google-Sender-Auth: OTafgm8ACn_gBMcleceGWauC1hs
Message-ID: <CAHSQbTAZTc9puGaH0rbhyY11s0+L0xGjSabK1kj65UMm1t7j3w@mail.gmail.com>
Subject: Strange panic on ppc64
From: Justin Hibbits <jhibbits@freebsd.org>
To: FreeBSD PowerPC ML <freebsd-ppc@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
X-BeenThere: freebsd-ppc@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Porting FreeBSD to the PowerPC <freebsd-ppc.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ppc>
List-Post: <mailto:freebsd-ppc@freebsd.org>
List-Help: <mailto:freebsd-ppc-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ppc>,
 <mailto:freebsd-ppc-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jun 2013 03:35:11 -0000

After a string of seemingly random hangs, I added invariants (but not
witness) to my custom kernel config, and I get the following panic,
recreated from a fuzzy cell phone picture:


[thread pid -1 tid 1006665719 ]
Stopped at 0: illegal instruction 0
db> panic: mutex ohci1 owned at
/usr/home/chmeee/freebsd/head/sys/dev/usb/usb_transfer.c:2280
cpuid = 0
Uptime: 9h8m1s
<my dump code>
...
panic: msleep1
cpu = 0
KDB: enter: panic
[ thread pid -1 tid 100665719 ]
....

The first question I have is how the hell it got such a strange PID/TID,
memory corruption my guess, something is stomping on the pcpu or something,
and I think these hangs have only happened since I added a lot more memory
(up to 12G from 4G, Andreas Tobler was seeing hangs as well), so it might
be something in the moea64 pmap code, but that's pure speculation on my
part.  Then the other panic messages, owned mutex and panic in msleep1.  I
enabled more trace code, so hopefully the next time it panics I can collect
better data.

- Justin