[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yun8vqccjlp.fsf@aiko.keithp.com>
Date: Mon, 29 Aug 2011 08:39:46 -0700
From: Keith Packard <keithp@...thp.com>
To: Pawel Sikora <pluto@...k.net>, linux-kernel@...r.kernel.org
Cc: kamal@...onical.com
Subject: Re: Linux 3.1-rc4
On Mon, 29 Aug 2011 15:22:10 +0200, Pawel Sikora <pluto@...k.net> wrote:
> Hi,
>
> the recent -rc4 fix ( Kamal Mostafa / i915: do not setup intel_backlight twice ) fixes an oops
> described in https://bugzilla.kernel.org/show_bug.cgi?id=40892#c1 but the core error
> "[drm:intel_dsm_platform_mux_info] *ERROR* MUX INFO call failed" still
> exists.
That looks harmless; I'll check with the ACPI experts though.
> Aug 29 15:10:55 vmx kernel: [22761.103401] BUG: unable to handle kernel paging request at 000000104a69c2f8
> Aug 29 15:10:55 vmx kernel: [22761.103403] IP: [<ffffffff81265d02>] fb_flashcursor+0x42/0x150
I'm assuming this is a regression; can you find a version that it worked
on without any other changes in the environment? I'm concerned that
you're loading both vesafb and then switching to the drm fb, which
always seems fraught with peril to me.
And, of course, a bisect would be most helpful if possible. I can't
think of any i915-specific changes that would cause fb mappings to go wrong.
--
keith.packard@...el.com
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists