From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Olaf Hering <olh@suse.de>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: 2.6.11-rc5
Date: Sat, 26 Feb 2005 11:54:13 +1100 [thread overview]
Message-ID: <1109379254.14992.96.camel@gaston> (raw)
In-Reply-To: <20050225172945.GA31211@suse.de>
> > It seem to detect the flat panel incorrectly, or the EDID data is bogus,
> > maybe that's wrecking something in the new modelist management in
> > fbdev ? It might be causing us to use a bogus mode that itself casues
> > atyfb to crash. Tried forcing a mode ?
>
> cfb_imageblit(320) dst1 fa51a800 base e0b80000 bitstart 1999a800
> fast_imageblit(237) s daea4000 dst1 fa51a800
> fast_imageblit(269) j 1 fa51a800 0
> Unable to handle kernel paging request at virtual address fa51a800
>
> is bitstart incorrect or is the thing just not (yet) mapped?
It should be all mapped, i suspect the mode set is totally bogus. To
check it, can you enable radeonfb verbose debug ?
> radeonfb: Found Intel x86 BIOS ROM Image
> radeonfb: Retreived PLL infos from BIOS
> radeonfb: Reference=27.00 MHz (RefDiv=60) Memory=133.00 Mhz, System=133.00 MHz
> radeonfb: PLL min 12000 max 35000
> radeonfb: Monitor 1 type DFP found
> radeonfb: EDID probed
> radeonfb: Monitor 2 type no found
> radeonfb: Assuming panel size 8x1
> radeonfb: Can't find mode for panel size, going back to CRT
> cfb_imageblit(320) dst1 fa51a800 base e0b80000 bitstart 1999a800
> fast_imageblit(237) s daea4000 dst1 fa51a800
> fast_imageblit(269) j 1 fa51a800 0
> Unable to handle kernel paging request at virtual address fa51a800
> printing eip:
> c020f17e
> *pde = 00000000
> Oops: 0002 [#1]
> Modules linked in: ohci1394 ieee1394 radeonfb i2c_algo_bit i2c_core ehci_hcd uhci_hcd capability usbcore
> CPU: 0
> EIP: 0060:[<c020f17e>] Tainted: G U VLI
> EFLAGS: 00010282 (2.6.11-rc5-20050225-default)
> EIP is at cfb_imageblit+0x57e/0x67c
> eax: 00000000 ebx: 00000001 ecx: 00000000 edx: fa51a800
> esi: fa51a804 edi: daea4000 ebp: 00000004 esp: dcae9c14
> ds: 007b es: 007b ss: 0068
> Process modprobe (pid: 2080, threadinfo=dcae8000 task=dc4a7550)
> Stack: c01110ac 00000001 c0321d60 dcae9c20 dcae9c20 c01303a2 00000001 c03c87a8
> 0000000a dae23ca8 c011c783 00000046 00000000 dc202000 00000046 dcae9c64
> c010513d 0000384d dc202290 00000007 c032db20 daea4000 00000000 0000000f
> Call Trace:
> [<c01110ac>] smp_local_timer_interrupt+0xc/0x50
> [<c01303a2>] handle_IRQ_event+0x32/0x70
> [<c011c783>] __do_softirq+0x43/0xa0
> [<c010513d>] do_IRQ+0x3d/0x60
> [<c020d790>] soft_cursor+0x190/0x200
> [<c02043cc>] bit_cursor+0x48c/0x4f0
> [<e0b26c01>] radeonfb_prim_fillrect+0xf1/0x120 [radeonfb]
> [<c012043f>] msleep+0x2f/0x40
> [<c01fff28>] fbcon_cursor+0x1a8/0x280
> [<c023ad08>] hide_cursor+0x18/0x30
> [<c023b014>] redraw_screen+0x174/0x200
> [<c01fed4a>] fbcon_prepare_logo+0x39a/0x3a0
> [<c01ff8a0>] fbcon_init+0x2b0/0x370
> [<c023b1a9>] visual_init+0xe9/0x170
>
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2005-02-26 0:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0502232014190.18997@ppc970.osdl.org>
[not found] ` <20050224145049.GA21313@suse.de>
[not found] ` <1109287708.15026.25.camel@gaston>
[not found] ` <20050225070813.GA13735@suse.de>
[not found] ` <1109316551.14993.63.camel@gaston>
2005-02-25 17:29 ` 2.6.11-rc5 Olaf Hering
2005-02-25 17:59 ` [Linux-fbdev-devel] 2.6.11-rc5 James Simmons
2005-02-25 20:24 ` Olaf Hering
2005-02-25 21:21 ` [Linux-fbdev-devel] " Olaf Hering
2005-02-25 23:30 ` Olaf Hering
2005-02-26 1:01 ` Benjamin Herrenschmidt
2005-02-26 9:52 ` Giuseppe Bilotta
2005-02-26 0:58 ` Benjamin Herrenschmidt
2005-02-26 0:57 ` Benjamin Herrenschmidt
2005-02-26 0:54 ` Benjamin Herrenschmidt [this message]
2005-02-26 0:41 ` 2.6.11-rc5 Olaf Hering
2005-02-26 0:49 ` 2.6.11-rc5 Linus Torvalds
2005-02-26 0:53 ` 2.6.11-rc5 Olaf Hering
2005-02-26 1:04 ` 2.6.11-rc5 Linus Torvalds
2005-02-26 1:08 ` 2.6.11-rc5 Buttchereit, Axel (XL)
2005-02-26 1:17 ` [Linux-fbdev-devel] " Benjamin Herrenschmidt
2005-02-26 1:13 ` 2.6.11-rc5 Benjamin Herrenschmidt
2005-02-26 7:41 ` [Linux-fbdev-devel] 2.6.11-rc5 Antonino A. Daplas
2005-02-27 8:07 ` 2.6.11-rc5 Geert Uytterhoeven
2005-02-27 20:32 ` 2.6.11-rc5, rivafb i2c oops, bogus error handling Olaf Hering
2005-02-28 14:41 ` Antonino A. Daplas
2005-03-01 12:02 ` [Linux-fbdev-devel] " Olaf Hering
2005-03-01 20:58 ` Olaf Hering
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=1109379254.14992.96.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=olh@suse.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).