Messages in this thread | | | Subject | 2.6.5-rc2-mm3 badness | From | Jurgen Kramer <> | Date | Fri, 26 Mar 2004 01:14:07 +0100 |
| |
I not sure if this has been reported yet but after booting 2.6.5-rc2-mm3 I get:
Mar 26 01:05:44 paragon kernel: on+0x8c/0x114 Mar 26 01:05:44 paragon kernel: [<c011d8d9>] default_wake_function+0x0/0xc Mar 26 01:05:44 paragon kernel: [<c011d8d9>] default_wake_function+0x0/0xc Mar 26 01:05:44 paragon kernel: [<c011be87>] sched_migrate_task+0x94/0x9d Mar 26 01:05:44 paragon kernel: [<c011bfd6>] sched_balance_exec+0x5d/0x7b Mar 26 01:05:44 paragon kernel: [<c0164f9c>] do_execve+0x16/0x201 Mar 26 01:05:44 paragon kernel: [<c0140d24>] buffered_rmqueue+0x110/0x214 Mar 26 01:05:44 paragon kernel: [<c0140ed3>] __alloc_pages+0xab/0x2e0 Mar 26 01:05:44 paragon kernel: [<c0150656>] page_remove_rmap+0x18/0x197 Mar 26 01:05:44 paragon kernel: [<c014b75c>] do_wp_page+0x247/0x3ae Mar 26 01:05:44 paragon kernel: [<c014c7ec>] handle_mm_fault+0x187/0x1eb Mar 26 01:05:44 paragon syslog: klogd startup succeeded Mar 26 01:05:44 paragon kernel: [<c011a0ff>] do_page_fault+0x2b8/0x49f Mar 26 01:05:44 paragon kernel: [<c012e079>] do_sigaction+0x197/0x254 Mar 26 01:05:44 paragon kernel: [<c012e4a4>] sys_rt_sigaction+0xd4/0xef Mar 26 01:05:44 paragon kernel: [<c0107b65>] sys_execve+0x35/0x68 Mar 26 01:05:44 paragon kernel: [<c025497a>] sysenter_past_esp+0x43/0x65 Mar 26 01:05:44 paragon kernel: Mar 26 01:05:44 paragon kernel: bad: scheduling while atomic! Mar 26 01:05:44 paragon kernel: Call Trace: Mar 26 01:05:44 paragon kernel: [<c011d891>] schedule+0x814/0x819 Mar 26 01:05:44 paragon kernel: [<c0140d24>] buffered_rmqueue+0x110/0x214 Mar 26 01:05:44 paragon kernel: [<c011af9a>] recalc_task_prio+0x8f/0x183 Mar 26 01:05:44 paragon kernel: [<c011b0ea>] activate_task+0x5c/0x70 Mar 26 01:05:44 paragon kernel: [<c011db9a>] wait_for_completion+0x8c/0x114 Mar 26 01:05:44 paragon irqbalance: irqbalance startup succeeded Mar 26 01:05:44 paragon kernel: [<c011d8d9>] default_wake_function+0x0/0xc Mar 26 01:05:44 paragon kernel: [<c011d8d9>] default_wake_function+0x0/0xc Mar 26 01:05:44 paragon kernel: [<c011be87>] sched_migrate_task+0x94/0x9d Mar 26 01:05:44 paragon kernel: [<c011bfd6>] sched_balance_exec+0x5d/0x7b Mar 26 01:05:44 paragon kernel: [<c0164f9c>] do_execve+0x16/0x201 Mar 26 01:05:44 paragon kernel: [<c0140d24>] buffered_rmqueue+0x110/0x214 Mar 26 01:05:44 paragon kernel: [<c0140ed3>] __alloc_pages+0xab/0x2e0 Mar 26 01:05:44 paragon kernel: [<c0150656>] page_remove_rmap+0x18/0x197 Mar 26 01:05:44 paragon kernel: [<c014b75c>] do_wp_page+0x247/0x3ae Mar 26 01:05:44 paragon kernel: [<c014c7ec>] handle_mm_fault+0x187/0x1eb Mar 26 01:05:44 paragon kernel: [<c011a0ff>] do_page_fault+0x2b8/0x49f Mar 26 01:05:44 paragon kernel: [<c012e090>] do_sigaction+0x1ae/0x254 Mar 26 01:05:44 paragon kernel: [<c012e4a4>] sys_rt_sigaction+0xd4/0xef Mar 26 01:05:44 paragon kernel: [<c0107b65>] sys_execve+0x35/0x68 Mar 26 01:05:44 paragon kernel: [<c025497a>] sysenter_past_esp+0x43/0x65
Which keeps on going and going. I manage to get a login prompt but the messages keep coming and the systems freezes. If more details are needed...
Jurgen
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |