Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753062Ab1BESLs (ORCPT <rfc822;w@1wt.eu>);
	Sat, 5 Feb 2011 13:11:48 -0500
Received: from cavan.codon.org.uk ([93.93.128.6]:43312 "EHLO
	cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752798Ab1BESLr (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sat, 5 Feb 2011 13:11:47 -0500
Date: Sat, 5 Feb 2011 18:11:41 +0000
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Felipe Balbi <balbi@ti.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dell-wmi: Received unknown WMI event (0x11)
Message-ID: <20110205181141.GA28947@srcf.ucam.org>
References: <20110205171807.GA3738@legolas.emea.dhcp.ti.com> <20110205173259.GA28134@srcf.ucam.org> <20110205174124.GB2619@legolas.emea.dhcp.ti.com> <20110205174417.GA28395@srcf.ucam.org> <20110205180859.GA2830@legolas.emea.dhcp.ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110205180859.GA2830@legolas.emea.dhcp.ti.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: mjg59@cavan.codon.org.uk
X-SA-Exim-Scanned: No (on cavan.codon.org.uk); SAEximRunCond expanded to false
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1222
Lines: 27

On Sat, Feb 05, 2011 at 08:08:59PM +0200, Felipe Balbi wrote:
> On Sat, Feb 05, 2011 at 05:44:17PM +0000, Matthew Garrett wrote:
> > On Sat, Feb 05, 2011 at 07:41:25PM +0200, Felipe Balbi wrote:
> > > > 
> > > > Nothing's changed in dell-wmi in that timeframe, so I suspect it's some 
> > > > other issue that's triggering here and the hardware is responding by 
> > > > sending events? Alternatively, these messages are pretty spread out. Do 
> > > > they directly correspond to you trying to burn something?
> > > 
> > > it's actually right after inserting a disc on the drive. I'll try
> > > switching to AHCI on BIOS and see if it works fine.
> > 
> > And that message isn't generated in .37?
> 
> nope. dmesg is clean.

Hm. I'd still lean towards blaming something in the ata layer - I can't 
see any way that dell-wmi could be directly involved, and it's primarily 
just a mechanism for the firmware to report events to the OS.

-- 
Matthew Garrett | mjg59@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/