From mboxrd@z Thu Jan 1 00:00:00 1970 From: berk walker Subject: Re: exception Emask 0x0 SAct 0x1 / SErr 0x0 action 0x2 frozen Date: Sat, 04 Oct 2008 20:29:28 -0400 Message-ID: <48E80A68.2000108@panix.com> References: <3E6D0C24877245C3A5A327129A7B4CA7@909927SOSLA> <5419A02543384E69AF2BA82FF6E66C14@909927SOSLA> <4B1ABD0393EF40FFB0A12242FE8356AF@909927SOSLA> <48DBAB81.8050900@tmr.com> <48E08E2D.6050905@kernel.org> <48E6D481 .7050407@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-raid-owner@vger.kernel.org To: Justin Piszcz Cc: Tejun Heo , "Mr. James W. Laferriere" , Tom Mortensen , Bill Davidsen , Gwendal Grignou , Brian Rademacher , linux-ide@vger.kernel.org, linux-raid maillist , Linux Kernel Maillist , Bruce Allen List-Id: linux-ide@vger.kernel.org Justin Piszcz wrote: > > > On Sat, 4 Oct 2008, Justin Piszcz wrote: > >> >> >> On Sat, 4 Oct 2008, Tejun Heo wrote: >> >>> Justin Piszcz wrote: >>> >>> You're leaving the good part out. Please always attach full kernel >>> log. >>> >>> Thanks. > > Are there any specific / useful / debugging options one could turn > on/enable to obtain more information during these events that would > produce meaningful/useful output? > > Justin. > > -- > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > I think that the log stated a lot. b-