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 17:32:59 +0000 [thread overview]
Message-ID: <20110205173259.GA28134@srcf.ucam.org> (raw)
In-Reply-To: <20110205171807.GA3738@legolas.emea.dhcp.ti.com>
On Sat, Feb 05, 2011 at 07:18:07PM +0200, Felipe Balbi wrote:
> [ 393.020537] dell-wmi: Received unknown WMI event (0x11)
> [ 832.336855] dell-wmi: Received unknown WMI event (0x11)
> [ 832.409353] dell-wmi: Received unknown WMI event (0x11)
> [ 833.621140] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 834.367611] dell-wmi: Received unknown WMI event (0x11)
> [ 1001.665940] dell-wmi: Received unknown WMI event (0x11)
> [ 1002.846845] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 1003.591459] dell-wmi: Received unknown WMI event (0x11)
> [ 1063.690326] dell-wmi: Received unknown WMI event (0x11)
> [ 1064.942777] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 1644.787491] dell-wmi: Received unknown WMI event (0x11)
> [ 1644.849026] dell-wmi: Received unknown WMI event (0x11)
> [ 1645.971790] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 1646.719084] dell-wmi: Received unknown WMI event (0x11)
> [ 2317.273481] dell-wmi: Received unknown WMI event (0x11)
> [ 2318.540645] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 2319.285487] dell-wmi: Received unknown WMI event (0x11)
> [ 2379.364740] dell-wmi: Received unknown WMI event (0x11)
> [ 2877.001258] dell-wmi: Received unknown WMI event (0x11)
> [ 2878.211188] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 2878.957282] dell-wmi: Received unknown WMI event (0x11)
> [ 2903.422959] dell-wmi: Received unknown WMI event (0x11)
> [ 2904.609272] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 2905.352451] dell-wmi: Received unknown WMI event (0x11)
> [ 2965.454915] dell-wmi: Received unknown WMI event (0x11)
> [ 2966.701330] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 3981.339257] dell-wmi: Received unknown WMI event (0x11)
> [ 3982.510612] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 3983.254770] dell-wmi: Received unknown WMI event (0x11)
> [ 4045.466929] dell-wmi: Received unknown WMI event (0x11)
> [ 4046.631137] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 4047.391614] dell-wmi: Received unknown WMI event (0x11)
> [ 4107.480071] dell-wmi: Received unknown WMI event (0x11)
> [ 4108.631339] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 4731.506881] dell-wmi: Received unknown WMI event (0x11)
> [ 4732.646424] [drm:ironlake_crtc_disable] *ERROR* failed to disable transcoder
> [ 4733.391238] dell-wmi: Received unknown WMI event (0x11)
> [ 6025.385179] cdrom: This disc doesn't have any tracks I recognize!
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?
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2011-02-05 17:33 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 [this message]
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
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=20110205173259.GA28134@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