From: Krishnakumar B <kitty@cse.wustl.edu>
To: linux-kernel@vger.kernel.org
Subject: USB call trace with Linux 2.5.40 + BK-snapshots as of 10/7/2002 13:00 CST
Date: Mon, 7 Oct 2002 21:42:40 -0500 [thread overview]
Message-ID: <15778.17952.262307.796106@samba.doc.wustl.edu> (raw)
Hi,
I got the following when I powered off my laptop. Normally it powers off
without problems but this time it didn't and I managed to write this down
by hand. I didn't write down the stack frame information. Don't know if
this is useful.
Debug: sleeping function called from illegal context at include/asm/semaphore.h:119
Call Trace:
driverfs_remove_file
device_remove_file
pci_pool_destroy
hcd_buffer_destroy
usb_hcd_pci_remove
pci_match_device
device_shutdown
unregister_reboot_notifier
force_sig_info
kill_proc_info
notify_parent
dput
fput
filp_close
sys_close
__up_wakeup
drivers/usb/core/hcd.c: USB bus 1 deregistered
drivers/usb/core/hcd-pci.c: usb_hcd_pci_remove 00:07.2, count != 1
Power down.
-kitty.
--
Krishnakumar B <kitty at cs dot wustl dot edu>
Distributed Object Computing Laboratory, Washington University in St.Louis
reply other threads:[~2002-10-08 2:37 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=15778.17952.262307.796106@samba.doc.wustl.edu \
--to=kitty@cse.wustl.edu \
--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;
as well as URLs for NNTP newsgroup(s).