On Thu, 28 Nov 2002 rwhron@earthlink.net wrote:

I saw the call trace below during 2.5.50 boot, but not on:
2.5.44-mm5
2.5.46-mm1
2.5.47-mm1
2.5.47-mm2
2.5.48-mm1
2.5.49
2.5.49-mm1

Invalid vesa mode 0x0000
matroxfb: Matrox G400 (AGP) detected
matroxfb: MTRR's turned on
matroxfb: 1920x1440x8bpp (virtual: 1920x8736)
matroxfb: framebuffer at 0xD4000000, mapped to 0xf8805000, size 33554432
Uninitialised timer!
This is just a warning.  Your computer is OK
function=0xc01c9050, data=0x0
Call Trace:
 [<c011c340>] check_timer_failed+0x40/0x50
 [<c01c9050>] cursor_timer_handler+0x0/0x30

Yes, the timer initialization was reverted in 2.5.50. Please apply the patch
Mathijs Mohlmann send to this list.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds



-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET 
comprehensive development tool, built to increase your 
productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en