From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755624Ab1KWCpw (ORCPT ); Tue, 22 Nov 2011 21:45:52 -0500 Received: from mx1.redhat.com ([209.132.183.28]:54930 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754464Ab1KWCpv (ORCPT ); Tue, 22 Nov 2011 21:45:51 -0500 Date: Tue, 22 Nov 2011 21:45:45 -0500 From: Dave Jones To: wwguy Cc: Linux Kernel , "ilw@linux.intel.com" , "linux-wireless@vger.kernel.org" Subject: Re: 3.1+ iwlwifi lockup Message-ID: <20111123024545.GA9703@redhat.com> Mail-Followup-To: Dave Jones , wwguy , Linux Kernel , "ilw@linux.intel.com" , "linux-wireless@vger.kernel.org" References: <20111031143408.GA17152@redhat.com> <1321992902.8072.7.camel@wwguy-ubuntu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1321992902.8072.7.camel@wwguy-ubuntu> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 22, 2011 at 12:15:02PM -0800, wwguy wrote: > Hi Dave, > > Sorry for taking so long. > it is a bogus command from the firmware which driver try to process it > and cause problem. I am not sure how it happen. But could you please try > the patch I attach here. > > For now I am just ignore the command, but not sure it is good enough, > might has to reload the firmware, but not sure. With Linus' current tree and this patch, I got a panic pretty quickly, but with a different trace. https://twitpic.com/7i4o10 Dave