From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: linux-wireless@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, ath5k-devel@lists.ath5k.org
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: ath5k tries to free an IRQ that is already-free
Date: Tue, 30 Sep 2008 19:15:14 +0100 [thread overview]
Message-ID: <48E26CB2.8000302@yahoo.com> (raw)
In yesterday's linux-tip I was able to provoke this backtrace by
repeatedly disabling and enabling the wifi on my EeePC 900:
[ 786.455830] uvcvideo 1-8:1.0: no reset_resume for driver uvcvideo?
[ 786.455835] uvcvideo 1-8:1.1: no reset_resume for driver uvcvideo?
[ 786.458642] uvcvideo: Found UVC 1.00 device CNF7129 (04f2:b071)
[ 786.485835] Restarting tasks ... <6>pciehp: Card not present on Slot(3)
[ 787.160420] done.
[ 787.197658] Trying to free already-free IRQ 18
[ 787.197726] Pid: 226, comm: pciehpd Not tainted
2.6.27-rc7-tipskw-00976-g30d1868-dirty #25
[ 787.197733] [<c01513b6>] free_irq+0xa6/0x130
[ 787.197749] [<c03ceb97>] ath5k_pci_remove+0x77/0xb0
[ 787.197759] [<c021f38e>] pci_device_remove+0x1e/0x40
[ 787.197770] [<c0298f2e>] __device_release_driver+0x5e/0x90
[ 787.197780] [<c0299038>] device_release_driver+0x28/0x40
[ 787.197788] [<c0298585>] bus_remove_device+0x65/0x80
[ 787.197796] [<c0296c21>] device_del+0x101/0x180
[ 787.197805] [<c0296cb0>] device_unregister+0x10/0x20
[ 787.197813] [<c021b88d>] pci_stop_dev+0x3d/0x50
[ 787.197820] [<c021b960>] pci_remove_bus_device+0x30/0xa0
[ 787.197829] [<c02287b9>] pciehp_unconfigure_device+0x99/0x190
[ 787.197840] [<c022744e>] pciehp_disable_slot+0x5e/0x240
[ 787.197848] [<c014a92b>] ? trace_hardirqs_on+0xb/0x10
[ 787.197858] [<c02279d8>] pciehp_power_thread+0x88/0xe0
[ 787.197867] [<c0136ac4>] ? run_workqueue+0xd4/0x1e0
[ 787.197877] [<c0136ac4>] ? run_workqueue+0xd4/0x1e0
[ 787.197886] [<c0136b26>] run_workqueue+0x136/0x1e0
[ 787.197894] [<c0136ac4>] ? run_workqueue+0xd4/0x1e0
[ 787.197902] [<c0227950>] ? pciehp_power_thread+0x0/0xe0
[ 787.197912] [<c013744b>] worker_thread+0x9b/0xf0
[ 787.197920] [<c013a390>] ? autoremove_wake_function+0x0/0x50
[ 787.197930] [<c01373b0>] ? worker_thread+0x0/0xf0
[ 787.197939] [<c0139fe6>] kthread+0x46/0x80
[ 787.197947] [<c0139fa0>] ? kthread+0x0/0x80
[ 787.197955] [<c010407b>] kernel_thread_helper+0x7/0x10
[ 787.197966] =======================
--
Sitsofe | http://sucs.org/~sits/
reply other threads:[~2008-09-30 18:20 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=48E26CB2.8000302@yahoo.com \
--to=sitsofe@yahoo.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).