James,
		I still see the same problem using 2.5.59. I think this
is the same problem as that referred to by Udo A. Steinberg
http://marc.theaimsgroup.com/?l=linux-kernel&m=104278873827538&w=2
( I get similar results as him if I compile rivafb built-in )

Is this possibly related to driver-model issues discussed in this thread ?
http://marc.theaimsgroup.com/?l=linux-kernel&m=104283662023857&w=2

Good news is that 2.5.59 seems quite stable as regards framebuffer.
It no longer locks up after loading fbcon. But rmmod fbcon still
causes instant death accompanied by increased whirring noises from inside
box.

To summarise:
 insmod rivafb causes "Badness in kobject_register" every time 
   ( after pci_register_driver() in rivafb_init(),see below )
 after insmod rivafb, I have a green screen, which can be cleared by fbset
  ( fbset now changes resolution of all VTs, this is different from 2.4.x )
 after clearing green screen using fbset, text colours are wrong
 now ( 2.5.59 ), I can insmod fbcon, and screen looks OK again ( apart from
  the left-hand-most column of screen appears at right-hand side of screen )
 rmmod fbcon locks up machine, no ALT-SYSRQ effective

Jan 18 14:44:10 TBird kernel: About to pci_module_init() in rivafb_init()
Jan 18 14:44:10 TBird kernel: Entering rivafb_probe()
Jan 18 14:44:10 TBird kernel: rivafb: nVidia device/chipset 10DE002C
Jan 18 14:44:10 TBird kernel: rivafb: RIVA MTRR set to ON
Jan 18 14:44:10 TBird kernel: About to pci_set_drvdata() in rivafb_probe()
Jan 18 14:44:10 TBird kernel: rivafb: PCI nVidia NV4 framebuffer ver 0.9.5b (nVidiaRIVA-VTNT2, 16MB @ 0xD0000000)
Jan 18 14:44:10 TBird kernel: Return OK from rivafb_probe()
Jan 18 14:44:10 TBird kernel: About to pci_register_driver() in rivafb_init()
Jan 18 14:44:10 TBird kernel: Badness in kobject_register at lib/kobject.c:152
Jan 18 14:44:10 TBird kernel: Call Trace:
Jan 18 14:44:10 TBird kernel:  [<d08d17b4>] rivafb_driver+0x54/0xfffe0918 [rivafb]
Jan 18 14:44:10 TBird kernel:  [<c01d1436>] kobject_register+0x56/0x60
Jan 18 14:44:10 TBird kernel:  [<d08d17a4>] rivafb_driver+0x44/0xfffe0918 [rivafb]
Jan 18 14:44:10 TBird kernel:  [<c0202707>] bus_add_driver+0x57/0xf0
Jan 18 14:44:10 TBird kernel:  [<d08d17a4>] rivafb_driver+0x44/0xfffe0918 [rivafb]
Jan 18 14:44:10 TBird kernel:  [<c0202b91>] driver_register+0x31/0x40
Jan 18 14:44:10 TBird kernel:  [<d08d1788>] rivafb_driver+0x28/0xfffe0918 [rivafb]
Jan 18 14:44:10 TBird kernel:  [<c01d5ae9>] pci_register_driver+0x49/0x60
Jan 18 14:44:10 TBird kernel:  [<d08d1788>] rivafb_driver+0x28/0xfffe0918 [rivafb]
Jan 18 14:44:10 TBird kernel:  [<d08b204a>] +0x4a/0x68 [rivafb]
Jan 18 14:44:10 TBird kernel:  [<d08d1760>] rivafb_driver+0x0/0xfffe0918 [rivafb]
Jan 18 14:44:10 TBird kernel:  [<d08d3100>] +0x0/0xfffdef78 [rivafb]
Jan 18 14:44:10 TBird kernel:  [<c0133e07>] sys_init_module+0x117/0x1c0
Jan 18 14:44:10 TBird kernel:  [<c010a393>] syscall_call+0x7/0xb

				Thanks,
						Jak.

On Wednesday 15 January 2003 00:43, James Simmons wrote:

Can you try the latest pacth at

http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz

-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit encryption. 
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en