From: Keith Packard <keithp@keithp.com>
To: Pawel Sikora <pluto@agmk.net>, linux-kernel@vger.kernel.org
Cc: kamal@canonical.com
Subject: Re: Linux 3.1-rc4
Date: Mon, 29 Aug 2011 08:39:46 -0700 [thread overview]
Message-ID: <yun8vqccjlp.fsf@aiko.keithp.com> (raw)
In-Reply-To: <2352775.A2sX9R5EWV@pawels>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
On Mon, 29 Aug 2011 15:22:10 +0200, Pawel Sikora <pluto@agmk.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@intel.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2011-08-29 15:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 13:22 Linux 3.1-rc4 Pawel Sikora
2011-08-29 15:39 ` Keith Packard [this message]
2011-09-02 4:52 ` Paweł Sikora
-- strict thread matches above, loose matches on Subject: below --
2011-08-29 4:52 Linus Torvalds
2011-08-29 5:53 ` Stephen Rothwell
2011-08-30 7:07 ` Borislav Petkov
2011-08-30 7:58 ` Yong Zhang
2011-08-30 9:14 ` Peter Zijlstra
2011-08-30 10:02 ` Borislav Petkov
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=yun8vqccjlp.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=kamal@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pluto@agmk.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.