From: Mark H. <Mar...@xs...> - 2005-03-15 23:45:56
|
Hi, Investigating yesterday=B4s crash when starting X, it seems also ruby related :-(... Anyone have suggestions on how to tackle this one? Regards Mark. Mar 15 01:38:58 ws1 kernel: CPU: 0 Mar 15 01:38:58 ws1 kernel: EIP: 0060:[<fcb28b02>] Not tainted VLI Mar 15 01:38:58 ws1 kernel: EFLAGS: 00010297 (2.6.11-mm1-rubymh2) Mar 15 01:38:58 ws1 kernel: EIP is at fbcon_switch+0x122/0x4c0 [fbcon] Mar 15 01:38:58 ws1 kernel: eax: 00000000 ebx: f7c51e64 ecx: 00000000 = =20 edx: c053481c Mar 15 01:38:58 ws1 kernel: esi: f6657000 edi: f7c51f04 ebp: fcb2bf88 = =20 esp: f7c51e34 Mar 15 01:38:58 ws1 kernel: ds: 007b es: 007b ss: 0068 Mar 15 01:38:58 ws1 kernel: Process events/0 (pid: 6, threadinfo=3Df7c50000= =20 task=3Df7c1fa80) Mar 15 01:38:58 ws1 kernel: Stack: f6657000 f7c51e64 00000000 c1725000=20 00000000 fcabbf20 00000000 00000720 Mar 15 01:38:58 ws1 kernel: 00000001 f71800ff 00000000 c053481c=20 00000280 000001e0 00000280 00006666 Mar 15 01:38:58 ws1 kernel: 00000000 00000000 00000008 00000000=20 00000000 00000008 00000000 00000000 Mar 15 01:38:58 ws1 kernel: Call Trace: Mar 15 01:38:58 ws1 kernel: [<c02aa564>] complete_change_console+0x74/0x1d0 Mar 15 01:38:58 ws1 kernel: [<c02b2047>] console_callback+0xe7/0xf0 Mar 15 01:38:58 ws1 kernel: [<c012a63e>] worker_thread+0x1ae/0x250 Mar 15 01:38:58 ws1 kernel: [<c02b1f60>] console_callback+0x0/0xf0 Mar 15 01:38:58 ws1 kernel: [<c01153b0>] default_wake_function+0x0/0x20 Mar 15 01:38:58 ws1 kernel: [<c01153b0>] default_wake_function+0x0/0x20 Mar 15 01:38:58 ws1 kernel: [<c012a490>] worker_thread+0x0/0x250 Mar 15 01:38:58 ws1 kernel: [<c012ee77>] kthread+0xb7/0xc0 Mar 15 01:38:58 ws1 kernel: [<c012edc0>] kthread+0x0/0xc0 Mar 15 01:38:58 ws1 kernel: [<c01009d1>] kernel_thread_helper+0x5/0x14 Mar 15 01:38:58 ws1 kernel: Code: 00 00 c7 46 18 00 00 00 00 c7 46 1c 00 00= 00=20 00 89 34 24 89 5c 24 04 e8 1d b4 74 c3 83 7c 24 2c ff 0f 84 5e 03 00 00 8 b 54 24 2c <0f> be 82 a0 d7 b2 fc 39 34 85 c0 e4 54 c0 0f 84 46 03 00 00 8b |