Bug 11561 (unplugging) - unpluggin a processor restuls in scheduling while atomc
Summary: unpluggin a processor restuls in scheduling while atomc
Status: REJECTED INVALID
Alias: unplugging
Product: ACPI
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: acpi_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-13 03:42 UTC by raz ben yehuda
Modified: 2008-09-13 03:48 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.26.5
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description raz ben yehuda 2008-09-13 03:42:33 UTC
Latest working kernel version: 2.6.18-8.el5 
Earliest failing kernel version: 2.6.26.5
Distribution:centos-5.0 64bit.
Hardware Environment:laptop. lenovo T61, dual core.
Software Environment: 
Problem Description:
configure kernel as described in section 12 in Documentation/SumbitCheckList ( setting slab corruption on) 
then " echo 0 >  /sys/devices/system/node/node0/cpu1/online"
results in a sleeping function from invalid context:

dmesg reports:

CPU0 attaching NULL sched-domain.
CPU1 attaching NULL sched-domain.
CPU 1 is now offline
lockdep: fixing up alternatives.
SMP alternatives: switching to UP code
BUG: sleeping function called from invalid context at mm/slab.c:3052
in_atomic():1, irqs_disabled():0
INFO: lockdep is turned off.
Pid: 2463, comm: bash Not tainted 2.6.26.5 #28

Call Trace:
 [<ffffffff80251c61>] ? __debug_show_held_locks+0x1b/0x24
 [<ffffffff8022aae6>] __might_sleep+0x108/0x10a
 [<ffffffff802962fd>] kmem_cache_alloc_node+0x39/0x1a3
 [<ffffffff80289432>] ? __get_vm_area_node+0xa4/0x1d7
 [<ffffffff80289432>] __get_vm_area_node+0xa4/0x1d7
 [<ffffffff8020a3d7>] ? disable_TSC+0x17/0x53
 [<ffffffff802895c5>] get_vm_area_caller+0x2f/0x31
 [<ffffffff804b2653>] ? text_poke+0x11d/0x19a
 [<ffffffff80289d40>] vmap+0x31/0x63
 [<ffffffff804b7b62>] ? _etext+0x0/0xe
 [<ffffffff804b2653>] text_poke+0x11d/0x19a
 [<ffffffff804b7b62>] ? _etext+0x0/0xe
 [<ffffffff802118d4>] alternatives_smp_unlock+0x4f/0x63
 [<ffffffff80211b77>] alternatives_smp_switch+0x161/0x19e
 [<ffffffff8021b80c>] __cpu_die+0x5c/0x86
 [<ffffffff8049d047>] _cpu_down+0x1b5/0x28d
 [<ffffffff8049d145>] cpu_down+0x26/0x36
 [<ffffffff8049e306>] store_online+0x32/0x75
 [<ffffffff8037402e>] sysdev_store+0x24/0x26
 [<ffffffff802e3134>] sysfs_write_file+0xe5/0x121
 [<ffffffff8029dddc>] vfs_write+0xae/0x124
 [<ffffffff8029e320>] sys_write+0x47/0x70
 [<ffffffff8020bffb>] system_call_after_swapgs+0x7b/0x80

CPU0 attaching sched-domain:
 domain 0: span 0
  groups: 0

Steps to reproduce:
Comment 1 raz ben yehuda 2008-09-13 03:45:14 UTC
(In reply to comment #0)
> Latest working kernel version: I do not know.
> Earliest failing kernel version: 2.6.26.5
> Distribution:centos-5.0 64bit.
> Hardware Environment:laptop. lenovo T61, dual core.
> Software Environment: 
> Problem Description:
> configure kernel as described in section 12 in Documentation/SumbitCheckList
> (
> setting slab corruption on) 
> then " echo 0 >  /sys/devices/system/node/node0/cpu1/online"
> results in a sleeping function from invalid context:
> 
> dmesg reports:
> 
> CPU0 attaching NULL sched-domain.
> CPU1 attaching NULL sched-domain.
> CPU 1 is now offline
> lockdep: fixing up alternatives.
> SMP alternatives: switching to UP code
> BUG: sleeping function called from invalid context at mm/slab.c:3052
> in_atomic():1, irqs_disabled():0
> INFO: lockdep is turned off.
> Pid: 2463, comm: bash Not tainted 2.6.26.5 #28
> 
> Call Trace:
>  [<ffffffff80251c61>] ? __debug_show_held_locks+0x1b/0x24
>  [<ffffffff8022aae6>] __might_sleep+0x108/0x10a
>  [<ffffffff802962fd>] kmem_cache_alloc_node+0x39/0x1a3
>  [<ffffffff80289432>] ? __get_vm_area_node+0xa4/0x1d7
>  [<ffffffff80289432>] __get_vm_area_node+0xa4/0x1d7
>  [<ffffffff8020a3d7>] ? disable_TSC+0x17/0x53
>  [<ffffffff802895c5>] get_vm_area_caller+0x2f/0x31
>  [<ffffffff804b2653>] ? text_poke+0x11d/0x19a
>  [<ffffffff80289d40>] vmap+0x31/0x63
>  [<ffffffff804b7b62>] ? _etext+0x0/0xe
>  [<ffffffff804b2653>] text_poke+0x11d/0x19a
>  [<ffffffff804b7b62>] ? _etext+0x0/0xe
>  [<ffffffff802118d4>] alternatives_smp_unlock+0x4f/0x63
>  [<ffffffff80211b77>] alternatives_smp_switch+0x161/0x19e
>  [<ffffffff8021b80c>] __cpu_die+0x5c/0x86
>  [<ffffffff8049d047>] _cpu_down+0x1b5/0x28d
>  [<ffffffff8049d145>] cpu_down+0x26/0x36
>  [<ffffffff8049e306>] store_online+0x32/0x75
>  [<ffffffff8037402e>] sysdev_store+0x24/0x26
>  [<ffffffff802e3134>] sysfs_write_file+0xe5/0x121
>  [<ffffffff8029dddc>] vfs_write+0xae/0x124
>  [<ffffffff8029e320>] sys_write+0x47/0x70
>  [<ffffffff8020bffb>] system_call_after_swapgs+0x7b/0x80
> 
> CPU0 attaching sched-domain:
>  domain 0: span 0
>   groups: 0
> 
> Steps to reproduce:
> 

Note You need to log in before you can comment on or make changes to this bug.