From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932219AbZJ0UeM (ORCPT ); Tue, 27 Oct 2009 16:34:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932192AbZJ0UeL (ORCPT ); Tue, 27 Oct 2009 16:34:11 -0400 Received: from mail-bw0-f227.google.com ([209.85.218.227]:37505 "EHLO mail-bw0-f227.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932190AbZJ0UeJ (ORCPT ); Tue, 27 Oct 2009 16:34:09 -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=qEMw/aZs914uoJIIeQPyE+6KPbLagpZQ5Fqkx/HtRJw0Yxcz+HMKBhEe5lgz2CHg46 FPj3yF2PG5tdCOSS1DAK+ikoWon0K1NWLmuz1XYCEP3E6fNP9R09rsNidnXQIMS1dmOw ft7q8HW8MS8AUEZwloeg5fxMlWeyXPzV/t6Q8= Message-ID: <4AE75945.8010407@gmail.com> Date: Tue, 27 Oct 2009 13:34:13 -0700 From: "Justin P. Mattock" User-Agent: Spicebird/0.7.1 (X11; 2009022519) MIME-Version: 1.0 To: Valdis.Kletnieks@vt.edu CC: Linux Kernel Subject: Re: PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0 References: <4AE24009.4090408@gmail.com> <21504.1256588976@turing-police.cc.vt.edu> <4AE611B2.1030409@gmail.com> <29209.1256624599@turing-police.cc.vt.edu> <4AE744F6.5050801@gmail.com> <22388.1256672113@turing-police.cc.vt.edu> In-Reply-To: <22388.1256672113@turing-police.cc.vt.edu> 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 Valdis.Kletnieks@vt.edu wrote: > On Tue, 27 Oct 2009 12:07:34 PDT, "Justin P. Mattock" said: > > >> The results are similar with the messages, except >> with the curly's the system will panic the same as above >> and not boot. >> > > As I expected - I explained why already. And in fact, I intentionally did > that, so that the *last* one of those added messages before your panic > will output the info regarding the device that caused it (hacking around > the panic would mean that you'd get a whole bunch of messages and not have > an easy way to tell *which one* caused the now-bypassed issue...) > > >> (So I guess it was good to forget the curly's >> to some extent). >> > > So out of curiosity, what did the messages actually *SAY*? They should > be pointing at the device that's giving your system indigestion, so it's > useful to actually include the output (I didn't pull that printk format > string out of thin air.. ;) > > o.k. you should be able to view this:(let me know if you can't and I can manually write out, and in time find a public photo sharing suite to make things easier). http://www.flickr.com/photos/44066293@N08/4050317695 When this happens I see lots of messages from the print during boot, then this happens. Justin P. Mattock