From: Mark Lord <lkml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.9-ac3
Date: Thu, 21 Oct 2004 20:59:17 -0400 [thread overview]
Message-ID: <41785B65.4090202@rtr.ca> (raw)
In-Reply-To: <1098400086.18025.0.camel@localhost.localdomain>
>Bug Fixes
>o Working IDE locking (Alan Cox)
> | And a great deal of review by Bartlomiej
Mmm.. may still have some issues.
Here's what "cardctl eject" now gives on unload of ide-cs:
bad: scheduling while atomic!
[<c02a0f7e>] schedule+0x4de/0x4f0
[<c0119451>] __wake_up_common+0x41/0x60
[<c02a1079>] wait_for_completion+0x99/0xf0
[<c01193f0>] default_wake_function+0x0/0x20
[<c01193f0>] default_wake_function+0x0/0x20
[<c012c8a8>] queue_work+0x68/0x80
[<c012c791>] call_usermodehelper+0xe1/0xf0
[<c012c640>] __call_usermodehelper+0x0/0x70
[<c01bdc7d>] kset_hotplug+0x1dd/0x240
[<c01bdd3a>] kobject_hotplug+0x5a/0x60
[<c01be07b>] kobject_del+0x1b/0x40
[<c01be0b3>] kobject_unregister+0x13/0x30
[<c018cef9>] del_gendisk+0x39/0xe0
[<c0223cd8>] idedisk_cleanup+0x48/0x60
[<c0212fd6>] __ide_unregister_hwif+0x506/0x5c0
[<c0196be8>] ext3_mark_iloc_dirty+0x28/0x40
[<c02130b6>] ide_unregister_hwif+0x26/0x40
[<e092da23>] ide_release+0x73/0x80 [ide_cs]
[<c0118992>] activate_task+0x62/0x80
[<e092d1b6>] ide_detach+0x86/0xa0 [ide_cs]
[<e08b5b19>] unbind_request+0xc9/0xd0 [ds]
[<e08b62fd>] ds_ioctl+0x3dd/0x690 [ds]
[<c029c25d>] unix_dgram_sendmsg+0x36d/0x570
[<c0230ce0>] sock_sendmsg+0xe0/0x100
[<c013bd8b>] generic_file_aio_write_nolock+0x27b/0x4b0
[<c0185a7b>] proc_destroy_inode+0x1b/0x20
[<c0172b75>] destroy_inode+0x35/0x60
[<c0173ef2>] iput+0x62/0x90
[<c0185a7b>] proc_destroy_inode+0x1b/0x20
[<c0172b75>] destroy_inode+0x35/0x60
[<c0147bb3>] zap_pmd_range+0x63/0x80
[<c0147c23>] unmap_page_range+0x53/0x80
[<c0147d36>] unmap_vmas+0xe6/0x1d0
[<c014a4d7>] remove_vm_struct+0x77/0xa0
[<c014bf1f>] unmap_vma_list+0x1f/0x30
[<c014c2df>] do_munmap+0x14f/0x190
[<c016ba30>] sys_ioctl+0x100/0x270
[<c01060d9>] sysenter_past_esp+0x52/0x71
I see a similar dump when using delkin_cb on 2.6.9-ac3 as well.
Cheers
--
Mark Lord
(hdparm keeper & the original "Linux IDE Guy")
next prev parent reply other threads:[~2004-10-22 1:08 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 23:08 Linux 2.6.9-ac3 Alan Cox
2004-10-22 0:59 ` Mark Lord [this message]
2004-10-22 1:42 ` [patch 2.6.9-ac3] ide: fixes for 2.6.9-ac3 ide issues Mark Lord
2004-10-22 1:18 ` Linux 2.6.9-ac3 Con Kolivas
2004-10-22 1:50 ` [PATCH 2.6.9-ac3] delkin_cb: new driver for Cardbus IDE CF Adapter Mark Lord
2004-10-22 6:36 ` Linux 2.6.9-ac3 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 8:13 Luca Risolia
2004-10-22 9:21 ` Luc Saillard
2004-10-22 12:30 ` Luca Risolia
2004-10-22 12:34 ` Xavier Bestel
2004-10-22 13:33 ` Luc Saillard
2004-10-22 14:22 ` Ronald S. Bultje
2004-10-22 14:38 ` David Weinehall
2004-10-22 14:15 ` Gergely Nagy
2004-10-22 13:16 ` Luc Saillard
2004-10-22 14:07 ` Luca Risolia
2004-10-22 14:10 ` Gerd Knorr
2004-10-22 15:51 ` Alan Cox
2004-10-22 18:14 ` Gerd Knorr
2004-10-23 13:41 ` Luca Risolia
2004-10-22 11:09 ` Alan Cox
2004-10-22 13:00 ` Luca Risolia
2004-10-22 15:49 ` Alan Cox
2004-10-23 14:54 ` Bill Davidsen
2004-10-23 17:36 ` Luca Risolia
2004-10-25 22:22 ` Bill Davidsen
2004-10-26 5:29 ` Luc Saillard
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=41785B65.4090202@rtr.ca \
--to=lkml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--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