From: "Mikko C." <mikko.cal@gmail.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Random problems with 2.6.28-rc1-git1
Date: Sun, 26 Oct 2008 08:25:39 +0100 [thread overview]
Message-ID: <49041B73.8060603@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810260235490.22126@twin.jikos.cz>
Jiri Kosina ha scritto:
> On Sat, 25 Oct 2008, Mikko C. wrote:
>
>> Today I tried upgrading to 2.6.28-rc1-git1 (-rc1 couldn't even mount the
>> disk). I'm having some problems with it :)
>> 1) Whenever I try to unload (rmmod or modprobe -r) *any* modules (even
>> if not used), the system hangs. I can still move the mouse and see
>> the cursor moving, but I can't type, can't switch console, nothing.
>> Because of this, I can't shutdown the system properly because it
>> hangs when "Unloading ALSA modules"
>>
>
> 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.
>> 2) Sometimes (randomly it seems) the system doesn't detect any usb
>> devices: I have an external HD and a Logitech mouse. Sometimes they
>> are recognized, sometimes not. Unplugging and re-plugging them
>> doesn't help. lsusb shows no attached device.
>>
>
> Compiling with CONFIG_USB_DEBUG and sending report to
> linux-usb@vger.kernel.org with the output included might be a good start.
>
Ok, done: http://marc.info/?l=linux-usb&m=122500580917403&w=2
Thanks
next prev parent reply other threads:[~2008-10-26 7:25 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. [this message]
2008-10-26 11:30 ` Andres Freund
2008-10-26 11:54 ` Mikko C.
-- 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=49041B73.8060603@gmail.com \
--to=mikko.cal@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox