2003-03-25 09:50:26

by Jan Dittmer

[permalink] [raw]
Subject: problems with rivafb again

Hi,

I'm getting plenty of those when switch from X (nv driver) to console
(rivafb) since your latest code got merged in bk. Also, the console
screen is really corrupted when switching back from X (sort of worked
before) and the little penguin isn't drawn anymore at bootup time.

Jan

Debug: sleeping function called from illegal context at mm/slab.c:1723
Call Trace:
[__might_sleep+95/128] __might_sleep+0x5f/0x80
[kmalloc+136/144] kmalloc+0x88/0x90
[accel_cursor+238/816] accel_cursor+0xee/0x330
[page_remove_rmap+287/304] page_remove_rmap+0x11f/0x130
[fb_vbl_handler+136/176] fb_vbl_handler+0x88/0xb0
[init_stall_timer+66/80] init_stall_timer+0x42/0x50
[i8042_timer_func+0/64] i8042_timer_func+0x0/0x40
[cursor_timer_handler+0/64] cursor_timer_handler+0x0/0x40
[cursor_timer_handler+31/64] cursor_timer_handler+0x1f/0x40
[run_timer_softirq+141/368] run_timer_softirq+0x8d/0x170
[timer_interrupt+123/336] timer_interrupt+0x7b/0x150
[do_softirq+156/160] do_softirq+0x9c/0xa0
[do_IRQ+252/288] do_IRQ+0xfc/0x120
[default_idle+0/48] default_idle+0x0/0x30
[default_idle+0/48] default_idle+0x0/0x30
[common_interrupt+24/32] common_interrupt+0x18/0x20
[default_idle+0/48] default_idle+0x0/0x30
[default_idle+0/48] default_idle+0x0/0x30
[default_idle+36/48] default_idle+0x24/0x30
[cpu_idle+46/64] cpu_idle+0x2e/0x40
[rest_init+0/96] _stext+0x0/0x60

ds666:/usr/src/bk/b# grep -i fb .config
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_FB=y
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
# CONFIG_FB_HGA is not set
CONFIG_FB_RIVA=y
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set
ds666:/usr/src/bk/b# grep -i logo .config
# Logo configuration
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y


2003-03-25 17:15:02

by James Simmons

[permalink] [raw]
Subject: Re: problems with rivafb again


> I'm getting plenty of those when switch from X (nv driver) to console
> (rivafb) since your latest code got merged in bk. Also, the console
> screen is really corrupted when switching back from X (sort of worked
> before) and the little penguin isn't drawn anymore at bootup time.

Do you have "UseFBdev" in your XF96Config file? You need to enable that
otherwise X and fbdev will conflict when setting the hardware. As for the
little penguin you need need to enable the Logo code in the video menu.
The logo code is also used by the SGI Newport driver.


2003-03-25 17:38:50

by Jan Dittmer

[permalink] [raw]
Subject: Re: problems with rivafb again

James Simmons wrote:
>>I'm getting plenty of those when switch from X (nv driver) to console
>>(rivafb) since your latest code got merged in bk. Also, the console
>>screen is really corrupted when switching back from X (sort of worked
>>before) and the little penguin isn't drawn anymore at bootup time.
>
>
> Do you have "UseFBdev" in your XF96Config file? You need to enable that
> otherwise X and fbdev will conflict when setting the hardware. As for the
> little penguin you need need to enable the Logo code in the video menu.
> The logo code is also used by the SGI Newport driver.
>
>
I've no such settings in my XF86Config. But it used to work before
without it - I'll try.
And as you may have seen from my .config options, the logo code _is_
enabled or did I overlook something?

Jan

# Logo configuration
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_MONO is not set
# CONFIG_LOGO_LINUX_VGA16 is not set
CONFIG_LOGO_LINUX_CLUT224=y