New testing kernel. 2.6.10-1.727_FC3

Gene C. czar at czarc.net
Sat Jan 8 15:59:12 UTC 2005


On Saturday 08 January 2005 10:46, Alan Cox wrote:
> On Sat, Jan 08, 2005 at 10:37:35AM -0500, Gene C. wrote:
> > Jan  8 09:37:27 eagle kernel: rivafb: RIVA MTRR set to ON
> > Jan  8 09:37:27 eagle kernel: rivafb: setting virtual Y resolution to
> > 104857
>
> That looked sane until
>
> > Jan  8 09:37:27 eagle startfb: rivafb not installed
>
> Umm
>
> > Jan  8 09:37:27 eagle startfb: /etc/rc3.d/S98startfb: line 16:  4992
> > Segmentation fault      /sbin/modprobe rivafb >/dev/null 2>&1
>
> And in dmesg ?

OK, rather than rebooting from run level 2 (which does not automatically run 
startfb), I ran it "manually" and have much more information from dmesg:

rivafb: nVidia device/chipset 10DE0179
rivafb: On a laptop.  Assuming Digital Flat Panel
rivafb: Detected CRTC controller 1 being used
rivafb: RIVA MTRR set to ON
rivafb: setting virtual Y resolution to 104857
Unable to handle kernel paging request at virtual address c03bf9fc
 printing eip:
c01e6297
*pde = 00419027
Oops: 0000 [#1]
DEBUG_PAGEALLOC
Modules linked in: rivafb vgastate md5 ipv6 parport_pc lp parport pcmcia 
ipt_REJECT ipt_state ip_conntrack iptable_filter ip_tables dm_mod video 
button battery ac ohci1394 ieee1394 yenta_socket pcmcia_core ohci_hcd 
ehci_hcd i2c_nforce2 i2c_core snd_intel8x0m snd_intel8x0 snd_ac97_codec 
snd_pcm_oss snd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc 
8139too mii ext3 jbd
CPU:    0
EIP:    0060:[<c01e6297>]    Not tainted VLI
EFLAGS: 00010282   (2.6.10-1.727_FC3)
EIP is at fb_prepare_logo+0x90/0xd3
eax: 000001e0   ebx: ec8fb000   ecx: 00000003   edx: c03bf9f4
esi: 0000001e   edi: c04019fc   ebp: c03ffd60   esp: ec898db8
ds: 007b   es: 007b   ss: 0068
Process modprobe (pid: 4360, threadinfo=ec898000 task=ec89baa0)
Stack: ec8fb000 0000001e c01e0ef5 00000003 00000000 00000000 00000000 00000720
       00000050 0000001e 00000050 c1821000 c1821000 ec8fb000 0000001e c03ffd60
       c01e1be1 0000001e 00000050 0000001e 00000050 00043701 00000100 00000050
Call Trace:
 [<c01e0ef5>] fbcon_prepare_logo+0x58/0x2e7
 [<c01e1be1>] fbcon_init+0x220/0x266
 [<c021e804>] visual_init+0xf4/0x14c
 [<c0221961>] take_over_console+0x1ed/0x2da
 [<c01e0e73>] fbcon_takeover+0x5c/0x86
 [<c01e4e15>] fbcon_fb_registered+0x36/0x64
 [<c01e4e7b>] fbcon_event_notify+0x38/0x65
 [<c01298dd>] notifier_call_chain+0x17/0x2b
 [<c01e7080>] register_framebuffer+0x12d/0x139
 [<f8b2fe01>] rivafb_check_var+0x1dc/0x235 [rivafb]
 [<f8b30ed3>] rivafb_probe+0x3b7/0x454 [rivafb]
 [<c01db21a>] pci_device_probe_static+0x2a/0x3d
 [<c01db248>] __pci_device_probe+0x1b/0x2c
 [<c01db274>] pci_device_probe+0x1b/0x2d
 [<c0239649>] driver_probe_device+0x30/0x4d
 [<c0239711>] driver_attach+0x37/0x66
 [<c0239ac8>] bus_add_driver+0x7a/0xa4
 [<c0239f54>] driver_register+0x51/0x58
 [<c01db42c>] pci_register_driver+0x8b/0x9e
 [<c01358c1>] sys_init_module+0x1c4/0x294
 [<c0103337>] syscall_call+0x7/0xb
Code: eb 14 c7 05 ec 19 40 c0 01 00 00 00 c7 05 f4 19 40 c0 01 00 00 00 89 d0 
e8 4b f9 ff ff a3 f8 19 40 c0 85 c0 89 c2 74 08 8b 43 0c <39> 42 08 76 0e c7 
05 f8 19 40 c0 00 00 00 00 31 c0 eb 2d 8b 02


Needless to say, startfb and loading rivafb works fine on the 2.6.9-1.724_FC3 
kernel.
-- 
Gene




More information about the test mailing list