On Sat, Jul 26, 2003 at 01:11:27PM +0200, Felipe Alfaro Solana wrote:
> bad: scheduling while atomic!
> Call Trace:
> [<c01166b2>] schedule+0x3d2/0x3e0
> [<c0116a18>] wait_for_completion+0x78/0xd0
> [<c0116710>] default_wake_function+0x0/0x30
> [<c0116710>] default_wake_function+0x0/0x30
> [<c015eda8>] link_path_walk+0x828/0x8d0
> [<c0129c71>] synchronize_kernel+0x31/0x40
> [<c01d0fdb>] poke_blanked_console+0x6b/0x80
> [<c0129c30>] wakeme_after_rcu+0x0/0x10
> [<c016c55d>] detach_mnt+0x3d/0x70
> [<c016d623>] do_move_mount+0x213/0x250
I wasn't sure what the right way to fix this was, so I punted, as it's
harmless at boot-time. There are somewhat more severe issues floating
around I need to fix, maybe sometime after OLS.
-- wli
-
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/
This archive was generated by hypermail 2b29 : Thu Jul 31 2003 - 22:00:29 EST