Re: sync to 2.6.6. Mostly fine, some error messages during boot.

[Helge H. <hel...@ai...>]

Aivils wrote:

>Hi All!
>
>	CVS now contains linux-ruby against 2.6.6.
>
>FBIOGET_CON2FBMAP, FBIOSET_CON2FBMAP ioctl() uses
>dummy call.
>  
>
Thanks for the good work - ruby-2.6.6 works for me.
There is a small problem where I get 998 messages in
/var/log/messages during startup.
This slows startup down with abouit half a minute,
but doesn't seem to have other problems:
One run:

May 26 22:57:27 monster kernel: Badness in vc_resize at 
drivers/char/vt.c:1095
May 26 22:57:27 monster kernel: Call Trace:
May 26 22:57:27 monster kernel:  [<c0208ad4>] vc_resize+0x3b4/0x3c0
May 26 22:57:27 monster kernel:  [<c0128678>] notifier_call_chain+0x18/0x40
May 26 22:57:27 monster kernel:  [<c0283999>] fb_resize_vt+0x59/0x70
May 26 22:57:27 monster kernel:  [<c0283b17>] fb_ioctl+0x167/0x340
May 26 22:57:27 monster kernel:  [<c0134391>] unlock_page+0x11/0x60
May 26 22:57:27 monster kernel:  [<c014aaa9>] exclusive_swap_page+0x39/0x90
May 26 22:57:27 monster kernel:  [<c0134391>] unlock_page+0x11/0x60
May 26 22:57:27 monster kernel:  [<c014109d>] do_wp_page+0x7d/0x2f0
May 26 22:57:27 monster kernel:  [<c014613d>] __pte_chain_free+0x4d/0x50
May 26 22:57:27 monster kernel:  [<c015f5dc>] sys_ioctl+0xec/0x25a
May 26 22:57:27 monster kernel:  [<c0106cff>] syscall_call+0x7/0xb
May 26 22:57:28 monster kernel:

The next one appeared twice:

May 26 22:57:28 monster kernel: Badness in set_origin at 
drivers/char/vt.c:503
May 26 22:57:28 monster kernel: Call Trace:
May 26 22:57:28 monster kernel:  [<c020767c>] set_origin+0x9c/0xb0
May 26 22:57:28 monster kernel:  [<c0208970>] vc_resize+0x250/0x3c0
May 26 22:57:28 monster kernel:  [<c0128678>] notifier_call_chain+0x18/0x40
May 26 22:57:28 monster kernel:  [<c0283999>] fb_resize_vt+0x59/0x70
May 26 22:57:28 monster kernel:  [<c0283b17>] fb_ioctl+0x167/0x340
May 26 22:57:28 monster kernel:  [<c0134391>] unlock_page+0x11/0x60
May 26 22:57:28 monster kernel:  [<c014aaa9>] exclusive_swap_page+0x39/0x90
May 26 22:57:28 monster kernel:  [<c0134391>] unlock_page+0x11/0x60
May 26 22:57:28 monster kernel:  [<c014109d>] do_wp_page+0x7d/0x2f0
May 26 22:57:28 monster kernel:  [<c014613d>] __pte_chain_free+0x4d/0x50
May 26 22:57:28 monster kernel:  [<c015f5dc>] sys_ioctl+0xec/0x25a
May 26 22:57:28 monster kernel:  [<c0106cff>] syscall_call+0x7/0xb
May 26 22:57:28 monster kernel:
May 26 22:57:28 monster kernel: Badness in set_palette at 
drivers/char/vt.c:291
May 26 22:57:28 monster kernel: Call Trace:
May 26 22:57:28 monster kernel:  [<c0206e18>] set_palette+0x78/0x80
May 26 22:57:28 monster kernel:  [<c0207936>] update_screen+0x36/0x80
May 26 22:57:28 monster kernel:  [<c0208a25>] vc_resize+0x305/0x3c0
May 26 22:57:28 monster kernel:  [<c0283999>] fb_resize_vt+0x59/0x70
May 26 22:57:28 monster kernel:  [<c0283b17>] fb_ioctl+0x167/0x340
May 26 22:57:28 monster kernel:  [<c0134391>] unlock_page+0x11/0x60
May 26 22:57:28 monster kernel:  [<c014aaa9>] exclusive_swap_page+0x39/0x90
May 26 22:57:28 monster kernel:  [<c0134391>] unlock_page+0x11/0x60
May 26 22:57:28 monster kernel:  [<c014109d>] do_wp_page+0x7d/0x2f0
May 26 22:57:28 monster kernel:  [<c014613d>] __pte_chain_free+0x4d/0x50
May 26 22:57:28 monster kernel:  [<c015f5dc>] sys_ioctl+0xec/0x25a
May 26 22:57:28 monster kernel:  [<c0106cff>] syscall_call+0x7/0xb

Then I got 31 of these:

May 26 22:57:28 monster kernel: Badness in vc_resize at 
drivers/char/vt.c:1095
May 26 22:57:28 monster kernel: Call Trace:
May 26 22:57:28 monster kernel:  [<c0208ad4>] vc_resize+0x3b4/0x3c0
May 26 22:57:28 monster kernel:  [<c0283999>] fb_resize_vt+0x59/0x70
May 26 22:57:28 monster kernel:  [<c0283b17>] fb_ioctl+0x167/0x340
May 26 22:57:28 monster kernel:  [<c0134391>] unlock_page+0x11/0x60
May 26 22:57:28 monster kernel:  [<c014aaa9>] exclusive_swap_page+0x39/0x90
May 26 22:57:28 monster kernel:  [<c0134391>] unlock_page+0x11/0x60
May 26 22:57:28 monster kernel:  [<c014109d>] do_wp_page+0x7d/0x2f0
May 26 22:57:28 monster kernel:  [<c014613d>] __pte_chain_free+0x4d/0x50
May 26 22:57:28 monster kernel:  [<c015f5dc>] sys_ioctl+0xec/0x25a
May 26 22:57:28 monster kernel:  [<c0106cff>] syscall_call+0x7/0xb

Then the machine was reset, probably by me.

The log then contains a restart followed by about 900 of these
vc_restart messages. 

Could this be a ruby problem, or some sort of framebuffer problem?

Helge Hafting