From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Randy Dunlap" <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: BUG: scheduling while atomic, new libata code
Date: Wed, 27 Dec 2006 21:16:26 -0500 [thread overview]
Message-ID: <9e4733910612271816x1ebc968auf94de2a84526aee0@mail.gmail.com> (raw)
In-Reply-To: <20061226175559.e280e66e.randy.dunlap@oracle.com>
Still getting the bug with patch applied.
BUG: scheduling while atomic: hald-addon-stor/0x20000000/5078
[<c02b0289>] __sched_text_start+0x5f9/0xb00
[<c024a623>] net_rx_action+0xb3/0x180
[<c01210f2>] __do_softirq+0x72/0xe0
[<c0105205>] do_IRQ+0x45/0x80
[<c0103aab>] common_interrupt+0x23/0x28
[<c0117696>] __cond_resched+0x16/0x40
[<c02b07b3>] cond_resched+0x23/0x30
[<c02b225c>] __reacquire_kernel_lock+0x1c/0x3c
[<c02b02b9>] __sched_text_start+0x629/0xb00
[<c02b086e>] wait_for_completion+0x8e/0xc0
[<c0117650>] default_wake_function+0x0/0x10
[<c01b321c>] blk_execute_rq+0x7c/0xe0
[<c0117696>] __cond_resched+0x16/0x40
[<c02b07b3>] cond_resched+0x23/0x30
[<c0161a36>] kmem_cache_zalloc+0x76/0x90
[<c02181fd>] scsi_execute_req+0x3d/0xf0
[<c01b6ce9>] sg_io+0x2a9/0x340
[<c0218306>] scsi_test_unit_ready+0x56/0xa0
[<f8986132>] sr_media_change+0x52/0x220 [sr_mod]
[<c0103ad8>] reschedule_interrupt+0x28/0x30
[<f8986320>] sr_block_media_changed+0x0/0x10 [sr_mod]
[<f89f508d>] media_changed+0x5d/0xa0 [cdrom]
[<c01883ac>] check_disk_change+0x1c/0x80
[<f89f9432>] cdrom_open+0x152/0xa90 [cdrom]
[<c0218306>] scsi_test_unit_ready+0x56/0xa0
[<c0175619>] __d_lookup+0x89/0x100
[<c0175b85>] dput+0xb5/0x130
[<c016ba75>] do_lookup+0x65/0x190
[<f8972540>] ext3_permission+0x0/0x10 [ext3]
[<c0175b85>] dput+0xb5/0x130
[<c016dc6a>] __link_path_walk+0xc1a/0xc90
[<c017828e>] touch_atime+0x9e/0x110
[<c0179b5b>] mntput_no_expire+0x1b/0x80
[<c016dd45>] link_path_walk+0x65/0xc0
[<c01323fe>] hrtimer_cancel+0xe/0x20
[<c0132539>] hrtimer_nanosleep+0x49/0x110
[<c01bdf3f>] kobject_get+0xf/0x20
[<c01b5ce9>] get_disk+0x39/0x70
[<c01b5d27>] exact_lock+0x7/0x10
[<c01bdf3f>] kobject_get+0xf/0x20
[<f89863dc>] sr_block_open+0x5c/0xa0 [sr_mod]
[<c0188e70>] blkdev_open+0x0/0x70
[<c0188bc9>] do_open+0x1e9/0x290
[<c0188e70>] blkdev_open+0x0/0x70
[<c0188ea0>] blkdev_open+0x30/0x70
[<c016307a>] __dentry_open+0xba/0x1c0
[<c0163235>] nameidata_to_filp+0x35/0x40
[<c016328b>] do_filp_open+0x4b/0x60
[<c01323fe>] hrtimer_cancel+0xe/0x20
[<c0132539>] hrtimer_nanosleep+0x49/0x110
[<c01632ea>] do_sys_open+0x4a/0xe0
[<c01633bc>] sys_open+0x1c/0x20
[<c010309a>] sysenter_past_esp+0x5f/0x85
=======================
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2006-12-28 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-27 1:47 Jon Smirl
2006-12-27 1:55 ` Randy Dunlap
2006-12-27 4:33 ` Jon Smirl
2006-12-28 2:16 ` Jon Smirl [this message]
2006-12-28 21:47 ` Arnd Bergmann
2006-12-28 22:43 ` Jon Smirl
2006-12-28 22:46 ` Jon Smirl
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=9e4733910612271816x1ebc968auf94de2a84526aee0@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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®