From: Jak <rfjak@eircom.net>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: rivafb "Badness" using fbdev.diff.gz and 2.5.5[45]
Date: Sat, 11 Jan 2003 13:30:11 +0000 [thread overview]
Message-ID: <200301111330.11827.rfjak@eircom.net> (raw)
With so much good development being done on framebuffer drivers at the moment, perhaps
the following is only a temporary problem, but I hope the following report is of some use.
I seem to be triggering a reproducible bug when loading rivafb, whether it is built-in or modular
with both 2.5.54 & 2.5.55 ( and, I suspect, 2.5.53 also ).
I have tried rivafb on 2 different nVidia cards, both yield the similar results when using recent
( Jan 8 ) fbdev.diff.gz patch.
After rivafb is loaded, the display goes bright green. After entering a command, I get
text back, but colours are wrong - there is no visible blue on screen i.e with colorized
ls listing, normally blue text is bright green, normally red is ( brighter ) red, normally white
is grey.
This is from 2.5.55 with fbdev.diff.gz applied, rivafb and fbcon both modular:
I have manually insmodded cfbimgblt & vgastate, then insmod rivafb
Jan 11 12:30:41 TBird kernel: rivafb: nVidia device/chipset 10DE002C
Jan 11 12:30:41 TBird kernel: rivafb: RIVA MTRR set to ON
Jan 11 12:30:41 TBird kernel: rivafb: PCI nVidia NV4 framebuffer ver 0.9.5b (nVidiaRIVA-VTNT2, 16
MB @ 0xD0000000)
Jan 11 12:30:41 TBird kernel: Badness in kobject_register at lib/kobject.c:129
Jan 11 12:30:41 TBird kernel: Call Trace:
Jan 11 12:30:41 TBird kernel: [<d08d43b4>] rivafb_driver+0x54/0xfffddd00 [rivafb]
Jan 11 12:30:41 TBird kernel: [<c01c6aa6>] kobject_add+0x56/0x60
Jan 11 12:30:41 TBird kernel: [<d08d43a4>] rivafb_driver+0x44/0xfffddd00 [rivafb]
Jan 11 12:30:41 TBird kernel: [<c01f67f9>] bus_remove_device+0x59/0xc0
Jan 11 12:30:41 TBird kernel: [<d08d43a4>] rivafb_driver+0x44/0xfffddd00 [rivafb]
Jan 11 12:30:41 TBird kernel: [<d08d3078>] +0x0/0xfffdefe8 [rivafb]
Jan 11 12:30:41 TBird kernel: [<c01f6c51>] put_driver+0x31/0x40
Jan 11 12:30:41 TBird kernel: [<d08d4388>] rivafb_driver+0x28/0xfffddd00 [rivafb]
Jan 11 12:30:41 TBird kernel: [<c01cb369>] pci_device_resume+0x49/0x60
Jan 11 12:30:41 TBird kernel: [<d08d4388>] rivafb_driver+0x28/0xfffddd00 [rivafb]
Jan 11 12:30:41 TBird kernel: [<d08b2032>] 0xd08b2032
Jan 11 12:30:41 TBird kernel: [<d08d4360>] rivafb_driver+0x0/0xfffddd00 [rivafb]
Jan 11 12:30:41 TBird kernel: [<d08d5d00>] +0x0/0xfffdc360 [rivafb]
Jan 11 12:30:41 TBird kernel: [<c012ca97>] load_module+0x117/0x1c0
Jan 11 12:30:41 TBird kernel: [<c0109327>] system_call+0x7/0xb
Jan 11 12:30:41 TBird kernel:
Module Size Used by
rivafb 45444 0
cfbimgblt 2880 1 rivafb
vgastate 9472 1 rivafb
mousedev 7256 1
Now I rmmod rivafb and insmod it again :
Module Size Used by
cfbimgblt 2880 0
vgastate 9472 0
mousedev 7256 1
Jan 11 12:35:29 TBird kernel: Badness in kobject_register at lib/kobject.c:129
Jan 11 12:35:29 TBird kernel: Call Trace:
Jan 11 12:35:29 TBird kernel: [<d08d43b4>] rivafb_driver+0x54/0xfffddd00 [rivafb]
Jan 11 12:35:29 TBird kernel: [<c01c6aa6>] kobject_add+0x56/0x60
Jan 11 12:35:29 TBird kernel: [<d08d43a4>] rivafb_driver+0x44/0xfffddd00 [rivafb]
Jan 11 12:35:29 TBird kernel: [<c01f67f9>] bus_remove_device+0x59/0xc0
Jan 11 12:35:29 TBird kernel: [<d08d43a4>] rivafb_driver+0x44/0xfffddd00 [rivafb]
Jan 11 12:35:29 TBird kernel: [<d08d3078>] +0x0/0xfffdefe8 [rivafb]
Jan 11 12:35:29 TBird kernel: [<c01f6c51>] put_driver+0x31/0x40
Jan 11 12:35:29 TBird kernel: [<d08d4388>] rivafb_driver+0x28/0xfffddd00 [rivafb]
Jan 11 12:35:29 TBird kernel: [<c01cb369>] pci_device_resume+0x49/0x60
Jan 11 12:35:29 TBird kernel: [<d08d4388>] rivafb_driver+0x28/0xfffddd00 [rivafb]
Jan 11 12:35:29 TBird kernel: [<d08b2032>] 0xd08b2032
Jan 11 12:35:29 TBird kernel: [<d08d4360>] rivafb_driver+0x0/0xfffddd00 [rivafb]
Jan 11 12:35:29 TBird kernel: [<d08d5d00>] +0x0/0xfffdc360 [rivafb]
Jan 11 12:35:29 TBird kernel: [<c012ca97>] load_module+0x117/0x1c0
Jan 11 12:35:29 TBird kernel: [<c0109327>] system_call+0x7/0xb
Jan 11 12:35:29 TBird kernel:
Module Size Used by
rivafb 45444 0
cfbimgblt 2880 1 rivafb
vgastate 9472 1 rivafb
mousedev 7256 1
BTW1: With stock 2.5.5 and modular rivafb, module will not load, this is what I get :
Jan 10 12:49:53 TBird kernel: rivafb: falsely claims to have parameter font
BTW2: the FBCON_ADVANCED "Advanced low level driver options" still shows up in
make *config, but does not seem to do much - should it still be there ?
BTW3: the second nVidia card I referred to is on my new laptop, using Geforce4 420 Go
card, which is not yet supported in 2.4.x, but seems to be detected properly in 2.5.x.
Loading fbcon causes bigger problems : serial OOPSes shortly followed by complete lockup
accel_putcs always seems to be implicated.
Jan 11 12:36:51 TBird kernel: Call Trace:
Jan 11 12:36:51 TBird kernel: [<d08cd437>] accel_putcs+0x157/0xfffe4f95 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d2d30>] +0x30/0xfffdf575 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d2d00>] +0x0/0xfffdf575 [fbcon]
Jan 11 12:36:51 TBird kernel: [<c017a731>] ext3_get_block_handle+0x51/0x90
Jan 11 12:36:51 TBird kernel: [<c0211b2c>] blk_recount_segments+0xdc/0x150
Jan 11 12:36:51 TBird kernel: [<d08d4da0>] fb_display+0x0/0xfffdd4d5 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08ce976>] fbcon_putcs+0x86/0xfffe3985 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d4da0>] fb_display+0x0/0xfffdd4d5 [fbcon]
Jan 11 12:36:51 TBird kernel: [<c020b14b>] set_console+0x24b/0x300
Jan 11 12:36:51 TBird kernel: [<c011c350>] sys_syslog+0x60/0x70
Jan 11 12:36:51 TBird kernel: [<c011c42c>] _call_console_drivers+0x5c/0x120
Jan 11 12:36:51 TBird kernel: [<c011c73f>] acquire_console_sem+0x3f/0xa0
Jan 11 12:36:51 TBird kernel: [<c011c669>] emit_log_char+0x109/0x140
Jan 11 12:36:51 TBird kernel: [<c0129eb5>] __constant_c_and_count_memset+0x35/0x40
Jan 11 12:36:51 TBird kernel: [<c0117b3f>] bust_spinlocks+0x21f/0x4b8
Jan 11 12:36:51 TBird kernel: [<c021fbd6>] execute_drive_cmd+0xf6/0x1a0
Jan 11 12:36:51 TBird kernel: [<c021fda7>] ide_stall_queue+0xd7/0x1d0
Jan 11 12:36:51 TBird kernel: [<c021febf>] ide_do_request+0x1f/0x30
Jan 11 12:36:51 TBird kernel: [<c0212152>] blk_remove_plug+0x42/0x50
Jan 11 12:36:51 TBird kernel: [<c0118f9a>] scheduling_functions_start_here+0x16a/0x2a0
Jan 11 12:36:51 TBird kernel: [<d08d324f>] +0x54f/0xfffdf575 [fbcon]
Jan 11 12:36:51 TBird kernel: [<c0117920>] bust_spinlocks+0x0/0x4b8
Jan 11 12:36:51 TBird kernel: [<c0109d31>] divide_error+0x2d/0x38
Jan 11 12:36:51 TBird kernel: [<d08d324f>] +0x54f/0xfffdf575 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08c1ef0>] fontdata_8x16+0x210/0x2f73e320 [font]
Jan 11 12:36:51 TBird kernel: [<d08d4300>] +0x1600/0xfffdf575 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08cd437>] accel_putcs+0x157/0xfffe4f95 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d2d50>] +0x50/0xfffdf575 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d2d00>] +0x0/0xfffdf575 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d4da0>] fb_display+0x0/0xfffdd4d5 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08ce976>] fbcon_putcs+0x86/0xfffe3985 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d4da0>] fb_display+0x0/0xfffdd4d5 [fbcon]
Jan 11 12:36:51 TBird kernel: [<c0207224>] scrdown+0x124/0x190
Jan 11 12:36:51 TBird kernel: [<c0207e20>] set_origin+0x150/0x180
Jan 11 12:36:51 TBird kernel: [<c02083f3>] vc_allocate+0x303/0x420
Jan 11 12:36:51 TBird kernel: [<d08ce27d>] fbcon_set_display+0x31d/0xfffe4315 [fbcon]
Jan 11 12:36:51 TBird kernel: [<c0135cb8>] cache_free_debugcheck+0xb8/0xd0
Jan 11 12:36:51 TBird kernel: [<c0134e36>] kmem_cache_alloc+0x96/0xd0
Jan 11 12:36:51 TBird kernel: [<d08d4da0>] fb_display+0x0/0xfffdd4d5 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08cdac9>] fbcon_init+0x59/0xfffe4805 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d1820>] fb_con+0x0/0xfffe0a55 [fbcon]
Jan 11 12:36:51 TBird kernel: [<c0207f1c>] vc_cons_allocated+0xac/0x110
Jan 11 12:36:51 TBird kernel: [<c020b8ba>] clear_buffer_attributes+0xaa/0x1c0
Jan 11 12:36:51 TBird kernel: [<d08d2bc0>] +0x0/0xfffdf6b5 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d1939>] +0x1d/0xfffe0959 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08d2bc0>] +0x0/0xfffdf6b5 [fbcon]
Jan 11 12:36:51 TBird kernel: [<d08b226d>] 0xd08b226d
Jan 11 12:36:51 TBird kernel: [<d08d1820>] fb_con+0x0/0xfffe0a55 [fbcon]
Jan 11 12:36:51 TBird kernel: [<c012ca97>] load_module+0x117/0x1c0
Jan 11 12:36:51 TBird kernel: [<c0109327>] system_call+0x7/0xb
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
next reply other threads:[~2003-01-11 13:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 13:30 Jak [this message]
2003-01-15 0:43 ` rivafb "Badness" using fbdev.diff.gz and 2.5.5[45] James Simmons
2003-01-18 20:28 ` Jak
2003-01-19 15:40 ` Antonino Daplas
2003-01-20 19:09 ` Jak
2003-01-20 22:44 ` Antonino Daplas
2003-01-21 10:29 ` Geert Uytterhoeven
2003-01-21 11:31 ` Antonino Daplas
2003-01-24 22:53 ` James Simmons
2003-01-25 9:00 ` Geert Uytterhoeven
2003-01-30 23:00 ` Antonino Daplas
2003-02-12 20:13 ` James Simmons
2003-01-21 0:08 ` Antonino Daplas
2003-01-24 20:14 ` James Simmons
2003-01-30 23:01 ` Antonino Daplas
2003-02-12 20:15 ` James Simmons
2003-02-12 23:37 ` Antonino Daplas
2003-01-24 19:09 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2003-01-19 11:29 Fredrik Noring
2003-01-19 15:41 ` Antonino Daplas
2003-01-19 16:42 ` Fredrik Noring
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=200301111330.11827.rfjak@eircom.net \
--to=rfjak@eircom.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).