From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dell-wmi: Received unknown WMI event (0x11)
Date: Sat, 5 Feb 2011 19:23:19 +0200 [thread overview]
Message-ID: <20110205172319.GA2619@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20110205171807.GA3738@legolas.emea.dhcp.ti.com>
Hi,
On Sat, Feb 05, 2011 at 07:18:07PM +0200, Felipe Balbi wrote:
> Hi,
>
> I believe this is a regression as it was working on 2.6.37 but with
> 2.6.38-rc3 I can't burn DVDs with my latitute e6410. When I put a blank
> double layer DVD on the drive I get:
>
> [ 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!
>
> and when I try to burn anything (well, a dry-run burn) I get:
>
> $ growisofs -dvd-compat -use-the-force-luke=dao -use-the-force-luke=break:1913760 -speed=2 -Z /dev/dvd=my-backup-files.iso -dry-run
> :-( /dev/dvd: CD_ROM_MEDIA_CHANGED ioctl failed: Inappropriate ioctl for device
>
> Has anyone seen that before ? I'll try to reboot on 2.6.37 and try again
> just to be sure and will report back on the differences.
yes, it works like a charm on 2.6.37:
$ dmesg
[ 91.522079] cdrom: This disc doesn't have any tracks I recognize!
$ growisofs -dvd-compat -use-the-force-luke=dao -use-the-force-luke=break:1913760 -speed=2 -Z /dev/dvd=my-backup-files.iso -dry-run
Executing 'builtin_dd if=cpx-mja.iso of=/dev/dvd obs=32k seek=0'
What more information can I grab which would help debugging ? I guess I
could bisect and try to find the offending commit, but that'll take a
few days.
--
balbi
next prev parent reply other threads:[~2011-02-05 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 17:18 Felipe Balbi
2011-02-05 17:23 ` Felipe Balbi [this message]
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
2011-02-05 18:18 ` Felipe Balbi
2011-02-05 18:20 ` Matthew Garrett
2011-02-07 8:25 ` Felipe Balbi
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=20110205172319.GA2619@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@srcf.ucam.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
all inboxes | Powered by JetHome®