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)
Date: Sat, 5 Feb 2011 18:11:41 +0000 [thread overview]
Message-ID: <20110205181141.GA28947@srcf.ucam.org> (raw)
In-Reply-To: <20110205180859.GA2830@legolas.emea.dhcp.ti.com>
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
next prev parent reply other threads:[~2011-02-05 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 17:18 dell-wmi: Received unknown WMI event (0x11) Felipe Balbi
2011-02-05 17:23 ` Felipe Balbi
2011-02-05 17:32 ` Matthew Garrett
2011-02-05 17:41 ` Felipe Balbi
2011-02-05 17:44 ` Matthew Garrett
2011-02-05 18:08 ` Felipe Balbi
2011-02-05 18:11 ` Matthew Garrett [this message]
2011-02-05 18:18 ` Felipe Balbi
2011-02-05 18:20 ` Matthew Garrett
2011-02-07 8:25 ` Felipe Balbi
-- strict thread matches above, loose matches on Subject: below --
2011-02-08 0:12 Trond Husø
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110205181141.GA28947@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox