Re: Random problems with 2.6.28-rc1-git1

From: Mikko C.
Date: Sun Oct 26 2008 - 07:55:07 EST


Andres Freund ha scritto:
Hi,

On Sunday 26 October 2008 08:25:39 Mikko C. wrote:
If rmmod never returns, alt-sysrq-t output should show us where it got
stuck.
Thanks for your answer
I tried Alt-Sysrq-T after a rmmod, but all I get is:
"SysRq : Show State"
Is it normal? Does it dump the information to a log?
Sorry but I never used sysrq in the past.
You propably have to set the loglevel to something higher before. Either use dmesg -n 6 or so or sysrq-6.

Andres
Ok, got it.

Oct 26 12:39:56 gentoo rmmod D ffffffff80532a80 0 5264 5088
Oct 26 12:39:56 gentoo ffff880079b5bd78 0000000000000082 0000000000000000 ffff880079b5bd3c
Oct 26 12:39:56 gentoo ffffffff806d3000 ffff88007fafb600 ffff88007f863000 ffff88007fafb850
Oct 26 12:39:56 gentoo 00000001895a50c0 00000000fffe90e8 ffff88007fafb850 00000000000160d1
Oct 26 12:39:56 gentoo Call Trace:
Oct 26 12:39:56 gentoo [<ffffffff8052332d>] schedule_timeout+0xad/0xf0
Oct 26 12:39:56 gentoo [<ffffffff80522578>] wait_for_common+0x148/0x170
Oct 26 12:39:56 gentoo [<ffffffff80231770>] default_wake_function+0x0/0x10
Oct 26 12:39:56 gentoo [<ffffffff8022da33>] __wake_up+0x43/0x70
Oct 26 12:39:56 gentoo [<ffffffff8024a464>] flush_cpu_workqueue+0x44/0x90
Oct 26 12:39:56 gentoo [<ffffffff8024a690>] wq_barrier_func+0x0/0x10
Oct 26 12:39:56 gentoo [<ffffffff8025e150>] __try_stop_module+0x0/0x30
Oct 26 12:39:56 gentoo [<ffffffff8024a5cb>] flush_workqueue+0x3b/0x60
Oct 26 12:39:56 gentoo [<ffffffff8025e150>] __try_stop_module+0x0/0x30
Oct 26 12:39:56 gentoo [<ffffffff8026997c>] __stop_machine+0x10c/0x130
Oct 26 12:39:56 gentoo [<ffffffff80261ced>] sys_delete_module+0x17d/0x290
Oct 26 12:39:56 gentoo [<ffffffff80288c68>] do_munmap+0x348/0x390
Oct 26 12:39:56 gentoo [<ffffffff803a0d51>] __up_write+0x21/0x150
Oct 26 12:39:56 gentoo [<ffffffff8020b94b>] system_call_fastpath+0x16/0x1b

Let me know if it's enough.
Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/