From: "Felipe Alfaro Solana" <felipe_alfaro@linuxmail.org>
To: tmolina@cox.net, akpm@digeo.com
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.64-mm6
Date: Thu, 13 Mar 2003 22:49:08 +0100 [thread overview]
Message-ID: <20030313214908.27753.qmail@linuxmail.org> (raw)
----- Original Message -----
From: Thomas Molina <tmolina@cox.net>
Date: Thu, 13 Mar 2003 14:35:18 -0600 (CST)
To: Andrew Morton <akpm@digeo.com>
Subject: Re: 2.5.64-mm6
> I downloaded the mm-6 patch and a pristine 2.5.64 tarball. After applying
> the patch I compiled with the standard configuration I've been using all
> along. No problems were noted during the compile cycle. During bootup
> the system locked up at the point where it did a modprobe uhci-hcd for the
> USB controller. Nothing of interest was noted in the log. I rebooted
> with nousb in the command line and got a good boot. After working with
> this kernel for awhile I don't see anything out of the ordainary except
> that on a 2.5.64-bk kernel I get 330 Kbytes per second download speed
> whereas with mm6 I get 280 Kbytes per second. Several runs show this is
> fairly consistent, with results within one or two percent.
Hmmm... I have experienced some hard locks similar to what
you describe: if I compile usb-uhci as a module, Phoebe3
(8.0.94) locks hard at the time of doing a "modprobe
usb-controller" (being usb-controller an alias for uhci-hcd)
during boot (rc.sysinit script). To fix this, I have had to compile
usb-uhci in to the kernel and then fix rc.sysinit. I haven't tried
using usb-uhci as a module since then.
What's curious is that doing a "modprobe usb-controller" by
hand doesn't cause hard locks. So, there must be some kind
of timing or interaction that's causing rc.sysinit to invoke
"modprobe uchi-hcd" and freeze the machine. Any ideas?
Felipe
--
______________________________________________
http://www.linuxmail.org/
Now with e-mail forwarding for only US$5.95/yr
Powered by Outblaze
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next reply other threads:[~2003-03-13 21:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 21:49 Felipe Alfaro Solana [this message]
2003-03-14 0:23 ` 2.5.64-mm6 Thomas Molina
-- strict thread matches above, loose matches on Subject: below --
2003-03-13 13:42 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 11:26 2.5.64-mm6 Andrew Morton
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 19:34 ` 2.5.64-mm6 Andrew Morton
2003-03-13 20:07 ` 2.5.64-mm6 Roger Larsson
2003-03-14 3:04 ` 2.5.64-mm6 Steven Cole
2003-03-14 3:28 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:46 ` 2.5.64-mm6 Shawn
2003-03-14 3:51 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:56 ` 2.5.64-mm6 Robert Love
2003-03-13 20:35 ` 2.5.64-mm6 Thomas Molina
2003-03-14 9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 11:55 ` 2.5.64-mm6 Andrew Morton
2003-03-15 8:38 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:14 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:38 ` 2.5.64-mm6 Eli Carter
2003-03-14 20:53 ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:01 ` 2.5.64-mm6 Eli Carter
2003-03-14 22:21 ` 2.5.64-mm6 Andrew Morton
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=20030313214908.27753.qmail@linuxmail.org \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tmolina@cox.net \
/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