From: "Mikko C." <mikko.cal@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Jiri Kosina <jkosina@suse.cz>, linux-kernel@vger.kernel.org
Subject: Re: Random problems with 2.6.28-rc1-git1
Date: Sun, 26 Oct 2008 12:54:48 +0100 [thread overview]
Message-ID: <49045A88.2010508@gmail.com> (raw)
In-Reply-To: <200810261231.02764.andres@anarazel.de>
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
next prev parent reply other threads:[~2008-10-26 11:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 14:53 Random problems with 2.6.28-rc1-git1 Mikko C.
2008-10-26 0:39 ` Jiri Kosina
2008-10-26 7:25 ` Mikko C.
2008-10-26 11:30 ` Andres Freund
2008-10-26 11:54 ` Mikko C. [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-10-25 20:45 Sid Boyce
2008-10-26 0:42 ` Jiri Kosina
2008-10-26 12:54 ` Sid Boyce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49045A88.2010508@gmail.com \
--to=mikko.cal@gmail.com \
--cc=andres@anarazel.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.