2013-10-14 12:34:26

by Borislav Petkov

[permalink] [raw]
Subject: fmc: BUG: scheduling while atomic: swapper/0/1/0x00000002

Hi,

I'm getting the following with randconfig testing in kvm, config is .attached.

...
[ 3.022023] fmc fake-design-for-testing-f001: Driver has no ID: matches all
[ 3.024393] bus: 'fmc': driver_probe_device: matched device fake-design-for-testing-f001 with driver fmc_chardev
[ 3.027890] bus: 'fmc': really_probe: probing driver fmc_chardev with device fake-design-for-testing-f001
[ 3.031236] device: 'fake-design-for-testing-f001': device_add
[ 3.033296] BUG: scheduling while atomic: swapper/0/1/0x00000002
[ 3.035372] 4 locks held by swapper/0/1:
[ 3.036808] #0: [ 3.036808] #0: ( (&__lockdep_no_validate__){......}), at: [<ffffffff81344b5b>] __driver_attach+0x4b/0xa0
[ 3.040537] #1: [ 3.040537] #1: ( (&__lockdep_no_validate__){......}), at: [<ffffffff81344b69>] __driver_attach+0x59/0xa0
[ 3.044294] #2: [ 3.044294] #2: ( (fc_lockfc_lock){+.+...}), at: [<ffffffff815d2466>] fc_probe+0x96/0x150
[ 3.047447] #3: [ 3.047447] #3: ( (misc_mtxmisc_mtx){+.+.+.}), at: [<ffffffff81312619>] misc_register+0x29/0x130
[ 3.050754] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.11.0-00039-g3102d23a949a #1
[ 3.053491] ffff88007edd2bc0 ffff88007c3f19b0 ffffffff817721df ffff88007c3e8000
[ 3.056521] ffff88007c3f19c8 ffffffff8176df69 7fffffffffffffff ffff88007c3f1a30
[ 3.059551] ffffffff817803d4 00000000001d2bc0 ffff88007c3f1fd8 ffff88007c3f1fd8
[ 3.062573] Call Trace:
[ 3.063576] [<ffffffff817721df>] dump_stack+0x54/0x74
[ 3.065383] [<ffffffff8176df69>] __schedule_bug+0x61/0x70
[ 3.067304] [<ffffffff817803d4>] __schedule+0x704/0x7a0
[ 3.069178] [<ffffffff81780499>] schedule+0x29/0x70
[ 3.070935] [<ffffffff8177d5c9>] schedule_timeout+0x209/0x2c0
[ 3.072967] [<ffffffff810c3e03>] ? mark_held_locks+0x63/0x110
[ 3.074988] [<ffffffff817829bc>] ? _raw_spin_unlock_irq+0x2c/0x50
[ 3.077113] [<ffffffff810c3fcd>] ? trace_hardirqs_on_caller+0x11d/0x140
[ 3.079407] [<ffffffff81780b2c>] wait_for_completion+0xac/0x110
[ 3.081483] [<ffffffff810a58b0>] ? wake_up_state+0x20/0x20
[ 3.083439] [<ffffffff81349255>] devtmpfs_create_node+0x115/0x150
[ 3.085544] [<ffffffff81780ab6>] ? wait_for_completion+0x36/0x110
[ 3.087676] [<ffffffff81340abf>] device_add+0x26f/0x680
[ 3.089525] [<ffffffff81340fb0>] device_create_groups_vargs+0xe0/0x110
[ 3.091793] [<ffffffff81341ab1>] device_create+0x41/0x50
[ 3.093673] [<ffffffff813126bf>] misc_register+0xcf/0x130
[ 3.095589] [<ffffffff815d246f>] fc_probe+0x9f/0x150
[ 3.097360] [<ffffffff815cffd7>] fmc_probe+0x17/0x20
[ 3.099142] [<ffffffff81344846>] driver_probe_device.part.10+0xa6/0x2f0
[ 3.101412] [<ffffffff81344ba9>] __driver_attach+0x99/0xa0
[ 3.103371] [<ffffffff81344b10>] ? __device_attach+0x60/0x60
[ 3.105355] [<ffffffff81342a7b>] bus_for_each_dev+0x6b/0xb0
[ 3.107314] [<ffffffff8134471e>] driver_attach+0x1e/0x20
[ 3.109213] [<ffffffff8134349c>] bus_add_driver+0xfc/0x270
[ 3.111144] [<ffffffff815d2390>] ? fc_read+0xa0/0xa0
[ 3.112922] [<ffffffff81345196>] driver_register+0x66/0x140
[ 3.114888] [<ffffffff815d2390>] ? fc_read+0xa0/0xa0
[ 3.116662] [<ffffffff815d01a5>] fmc_driver_register+0x35/0x40
[ 3.118704] [<ffffffff815d23a5>] fc_init+0x15/0x20
[ 3.120438] [<ffffffff821a4e15>] do_one_initcall+0x7f/0xf1
[ 3.122373] [<ffffffff81094638>] ? parse_args+0x1f8/0x330
[ 3.124293] [<ffffffff821a4f99>] kernel_init_freeable+0x112/0x192
[ 3.126413] [<ffffffff821a484b>] ? do_early_param+0x88/0x88
[ 3.128418] [<ffffffff81764b20>] ? rest_init+0xe0/0xe0
[ 3.130240] [<ffffffff81764b2e>] kernel_init+0xe/0x190
[ 3.132071] [<ffffffff817841ac>] ret_from_fork+0x7c/0xb0
[ 3.133946] [<ffffffff81764b20>] ? rest_init+0xe0/0xe0
[ 3.136574] fmc_chardev fake-design-for-testing-f001: Created misc device "fake-design-for-testing-f001"
[ 3.139902] driver: 'fake-design-for-testing-f001': driver_bound: bound to device 'fmc_chardev'
[ 3.142948] bus: 'fmc': really_probe: bound device fake-design-for-testing-f001 to driver fmc_chardev

--
Regards/Gruss,
Boris.

Sent from a fat crate under my desk. Formatting is fine.
--


Attachments:
(No filename) (4.09 kB)
config (78.48 kB)
Download all attachments

2013-10-14 15:23:52

by Borislav Petkov

[permalink] [raw]
Subject: Re: fmc: BUG: scheduling while atomic: swapper/0/1/0x00000002

On Mon, Oct 14, 2013 at 05:10:17PM +0200, Alessandro Rubini wrote:
> Hello.
>
> > I'm getting the following with randconfig testing in kvm, config is
> > .attached.
>
> I acknowledge this is a bug of mine, and your .config shows your are
> testing v3.11.
>
> I posted the fix on Jul 16th 2013, and it is now in master as
> v3.11-rc2-11-g783c2fb. However it is not an ancestor of v3.11, which
> still has the bug. "git tag --contains 783c2fb" reports v3.12-rc1 as
> the first "official" kernel with the fix,

Right, I found that bug report from July but didn't find the fix to it.
Thanks for letting me know.

--
Regards/Gruss,
Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

2013-10-14 15:31:33

by Alessandro Rubini

[permalink] [raw]
Subject: Re: fmc: BUG: scheduling while atomic: swapper/0/1/0x00000002

Hello.

> I'm getting the following with randconfig testing in kvm, config is
> .attached.

I acknowledge this is a bug of mine, and your .config shows your are
testing v3.11.

I posted the fix on Jul 16th 2013, and it is now in master as
v3.11-rc2-11-g783c2fb. However it is not an ancestor of v3.11, which
still has the bug. "git tag --contains 783c2fb" reports v3.12-rc1 as
the first "official" kernel with the fix,

Thank you for your feedback, anyways.
/alessandro