From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Andrew Morton <akpm@osdl.org>, Olaf Hering <olaf@aepfle.de>,
Michael Hanselmann <linux-kernel@hansmi.ch>
Subject: Re: Fw: oops in aty128_bl_set_power in 2.6.18-rc5
Date: Wed, 30 Aug 2006 22:59:50 +0800 [thread overview]
Message-ID: <1156949990.13504.10.camel@daplas.org> (raw)
In-Reply-To: <20060829205111.19809528.akpm@osdl.org>
On Tue, 2006-08-29 at 20:51 -0700, Andrew Morton wrote:
> NIP [C01A62E8] aty128_bl_set_power+0x28/0x9c
> LR [C01A62E4] aty128_bl_set_power+0x24/0x9c
> Call Trace:
> [CDF95D70] [C01A62E4] aty128_bl_set_power+0x24/0x9c (unreliable)
> [CDF95D90] [C01A65A8] aty128fb_blank+0x64/0x120
> [CDF95DB0] [C01706DC] fb_blank+0x4c/0x84
> [CDF95DE0] [C01716C0] fb_ioctl+0x4e4/0x5c4
> [CDF95ED0] [C00977A0] do_ioctl+0x6c/0x84
> [CDF95EE0] [C0097B38] vfs_ioctl+0x380/0x3b4
> [CDF95F10] [C0097BD4] sys_ioctl+0x68/0x98
> [CDF95F40] [C0012480] ret_from_syscall+0x0/0x40
> --- Exception: c01 at 0xfd75f48
> LR = 0xfd75ee0
Backlight registration can fail resulting in info->bl_dev = NULL. This
may be the cause of the oops. An additional 'if (info->bl_dev)' check
in aty128_bl_set_power() may be necessary.
On another note, is the call to aty128_bl_set_power() from
aty128fb_blank() necessary? aty128_bl_set_power() will be called twice
per call to aty128fb_blank().
Tony
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-08-30 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 3:51 Fw: oops in aty128_bl_set_power in 2.6.18-rc5 Andrew Morton
2006-08-30 14:59 ` Antonino A. Daplas [this message]
2006-08-30 17:34 ` Michael Hanselmann
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=1156949990.13504.10.camel@daplas.org \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@hansmi.ch \
--cc=olaf@aepfle.de \
/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;
as well as URLs for NNTP newsgroup(s).