From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752601AbZHQSza (ORCPT ); Mon, 17 Aug 2009 14:55:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751455AbZHQSz3 (ORCPT ); Mon, 17 Aug 2009 14:55:29 -0400 Received: from wf-out-1314.google.com ([209.85.200.174]:57697 "EHLO wf-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751051AbZHQSz2 (ORCPT ); Mon, 17 Aug 2009 14:55:28 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=msKNS5Mx+tMy5RljAFc2l+rCbSKlWw6UtLdhEI3Jv7oDUn0HsoBjpPgyVtg2HEGLLE +dJTH14avAxl1fCYzwMIHBh5+ZxtCLP1WUPqwBUh+G2dvdL5gLgkEuiW5YR4c0Bq1PRw Nc0PCrnH70ZEicfheWVro6oe9cEdfgYFJIJRY= Message-ID: <4A89A7C0.1090909@gmail.com> Date: Mon, 17 Aug 2009 11:56:00 -0700 From: "Justin P. Mattock" User-Agent: Spicebird/0.7.1 (X11; 2009031304) MIME-Version: 1.0 To: Stefan Richter CC: Linux Kernel Mailing List Subject: Re: ohci1396_dma=early nogo on an imac? References: <4A88F6BF.7090104@gmail.com> <4A89722A.1070407@s5r6.in-berlin.de> <4A899D41.7000405@s5r6.in-berlin.de> In-Reply-To: <4A899D41.7000405@s5r6.in-berlin.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Stefan Richter wrote: > Justin Mattock wrote: >> [ 660.190134] ieee1394: Current remote IRM is not 1394a-2000 >> compliant, resetting... > ... >> keeps going. > > It's a bug in ieee1394. http://bugzilla.kernel.org/show_bug.cgi?id=8403 > > Use the ieee1394 disable_irm=1 parameter on one or both nodes. > Perhaps firescope will then get going as well. O.K. Thanks to you using 2.6.30.4 I was able to log the boot message. now I can see if I can grab the info on the stuckage that im getting with the bad kernel. The problem im seeing is if I use ohci1394_dma=early on the bad kernel instantly Ill get a message on the screen saying: PANIC: early exception 08 rip 246:10 error ffffffff8145ff15 cr2 0 if I don't use the boot param the system loads but half way through ill get a message of manually writing down: [ 0.655640] [] panic+0x84/0x129 [ 0.655883] [] do_exit+0x84/0x67e [ 0.656125] [] oops_end+0x9c/0xb7 [ 0.656368] [] no_context+0x200/0x223 [ 0.656611] [] ? __mutex_lock_slowpath+0x226/0x249 [ 0.656848] [] __bad_area_nosemaphore+0x1a7/0x1e1 [ 0.657097] []? mutex_unlock+0x1c/0x32 [ 0.657097] [] ? inode_doinit_with_dentry+0x533/0x5be [ 0.657579] [] ? _spin_unlock+0x1c/0x32 [ 0.657822] [] bad_area_nosemaphore+0x2a/0x40 [ 0.658066] [] ? selinux_d_instantiate+0x2a/0x40 [ 0.658309] [] do_page_fault+0x192/0x2dd [ 0.658549] [] page_fault+0x1f/0x30 [ 0.658791] [] ? strcmp+0x17/0x46 [ 0.659040] [] event_create_dir+0x49/0x37b [ 0.659276] [] ? event_trace_init+0x0/0x1a2 [ 0.659519] [] event_trace_init+0x157/0x1a2 [ 0.659762] [] ? event_trace_init+0x0/0x1a2 [ 0.660008] [] do_one_initcall+0x65/0x14e [ 0.660251] [] ? proc_set_super+0x49/0x5d [ 0.660488] [] kernel_init+0x160/0x1cc [ 0.660731] [] child_rip+0xa/0x20 [ 0.660973] [] ? kernel_init+0x0/0x1cc [ 0.661220] [] ? child_rip+0x0/0x20 Justin P. Mattock