From: Jos van den Oever <jos@vandenoever.info>
To: linux-kernel@vger.kernel.org
Subject: oops & panic on usb-storage umount with 2.6.0-test3
Date: Sun, 10 Aug 2003 00:19:24 +0200 [thread overview]
Message-ID: <200308100019.24942.jos@vandenoever.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
Hi,
After the wonderful ride that was 2.6.0-test2, I decided to try test3.
test2 was perfect except for touchpad and bad latency performance. Playing
midi files finally worked!
test3 however is another matter. I can't access my sound device, even though
the modules seem to load fine and the card seems to be initialized. This mail
is not about that though.
After downloading files from my camera, I got an oops when I switched it off
and then unmounted it. The oops was followed by a kernel panic and is
completely reproducible. Here's the recipe:
- boot
- login as root
- modprobe uhci-hcd (it's not loaded automagically although the module for my
pcmcia network card is)
-> kernel finds USB ports
- switch on connected camera
-> kernel finds camera and assigns device
- mount /dev/sda1
-> files are visible
- switch off camera
-> kernel notes that usb device is switched off
- umount /dev/sda1
-> oops & panic
I've attached the /var/log/messages from boot to panic and also the ksymoops
output. /proc/ksym was not present and I do not know how to make it appear,
so the ksymoops output is not perfect.
Best regards, Jos van den Oever
PS I'm not on the list, so for a relatively quick reply please CC me.
[-- Attachment #2: messages.bz2 --]
[-- Type: application/x-bzip2, Size: 4555 bytes --]
[-- Attachment #3: modules.bz2 --]
[-- Type: application/x-bzip2, Size: 306 bytes --]
[-- Attachment #4: ksymoopsoutput.bz2 --]
[-- Type: application/x-bzip2, Size: 1200 bytes --]
reply other threads:[~2003-08-09 22:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200308100019.24942.jos@vandenoever.info \
--to=jos@vandenoever.info \
--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®