From: Derek Witt <dwitt1@kc.rr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6 kernel OOPs with Nomad MuVo MP3 player
Date: Sat, 29 May 2004 16:40:13 -0500 [thread overview]
Message-ID: <1085866812.10867.4.camel@saiya-jin> (raw)
In-Reply-To: <1085816432.11120.18.camel@saiya-jin>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
I have rebuilt my kernel without preempt support and passed
"elevator=deadline" to the kernel on reboot. I now can mount my nomad
muvo without any major problems.
However, it times out and gives the oops on attemptng to dismount, but
the only effect of that is that the USB reiterates itself and the next
time I insert the drive, it gets bumped up (e.g. from /dev/sda1 to
/dev/sdb1). Also, it sometimes gets rendered read-only (easily resolved
by remounting the drive with same device name).
But, during the copy process, my computer is unsually bogged down (the
jumping mouse cursor in X).
So, I am suspecting the AS Anticipatory IO scheduler at fault.
On Sat, 2004-05-29 at 02:40, Derek Witt wrote:
> Good morning.
>
> I am attempting to mount my Creative Nomad MuVo MP3 Player. However,
> every time I try to mount or copy to the drive, I constantly get a
> Kernel oops. I am currently running 2.6.6-rc1 under Gentoo 1.4. SuSE 9.0
> running vanilla 2.6.5 returns the same problem.
>
> My dump indicates a problem with usb-storage trying to preempt parts of
> itself.
>
> The included dump is during a copy attempt.
>
> I am quite puzzled by this.. I'm going to rebuild my kernel sans preempt
> and see what happens.
>
Derek J Witt,
dwitt1@kc.rr.com.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-29 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 7:40 Derek Witt
2004-05-29 21:40 ` Derek Witt [this message]
2004-06-01 5:32 ` Derek Witt
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=1085866812.10867.4.camel@saiya-jin \
--to=dwitt1@kc.rr.com \
--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
all inboxes | Powered by JetHome®