BUG: scheduling while atomic:

BUG: scheduling while atomic:

[smitha.vanga]

[-- Attachment #1: Type: text/plain, Size: 2371 bytes --]

Hi Scoot,

 When my  ISR gets exeuted I get a below BUG. Could let me what I am doing wrong in the ISR?


 BUG: scheduling while atomic: IRQ-20/0x0fff0000/108
Call Trace:
[C3AEFEC0] [C0007CCC]  (unreliable)
[C3AEFEF0] [C0017F10]
[C3AEFF00] [C0268818]
[C3AEFF50] [C0017F44]
[C3AEFF60] [C0018044]
[C3AEFF70] [C0046A90]
[C3AEFF90] [C0046D90]
[C3AEFFC0] [C0032AFC]
[C3AEFFF0] [C000F5AC]


Below is the code :
My ISR

irqreturn_t cpld_irq_handler(int irq, void * dev_id, struct pt_regs *regs)

{

wake_up(&cpld_intr_wait);

atomic_inc(&cpld_intr_data); /* incrementing this will indicate the poll() that the interrupt is occured */

return 0;

}

DRIVER_INIT
static int __init gpio_init(void)
{
        int ret = 0;
        int virq;


    atomic_set(&cpld_intr_data, 0);                     /* initialize the Interrupt indicator */
    init_waitqueue_head(&cpld_intr_wait);               /* Initialize the wait queue */

    virq = irq_create_mapping(NULL, CPLD1_INTERRUPT);


   if ((ret = request_irq(virq,cpld_irq_handler, 0, GPIO_CHAR_PATH, NULL))!=0)
   {
      printk(KERN_ERR "gpio_init: Could not grab IRQ line for CPLD ret = %d\n",ret);
          goto err1;
   }


        if((s_nGPIOMajor = register_chrdev(MPC8247_DEVICE_MAJOR_NUM, GPIO_CHAR_PATH, &gpio_fops))<0)
        {
                GPIO_DBG2("GPIO_DRIVER  : unable to get major %d\n", s_nGPIOMajor);
                return s_nGPIOMajor;

        }else{
                GPIO_DBG2("GPIO_DRIVER  : major = %x\n", s_nGPIOMajor );
        }

        return 0;

}

Thanks in Advance

Regards,
Smitha

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com

[-- Attachment #2: Type: text/html, Size: 5576 bytes --]

RE: scheduling while atomic:

[David Laight]

Not entirely relevant to the error you are seeing,
but your ISR is:

>	irqreturn_t cpld_irq_handler(int irq, void * dev_id, struct
pt_regs *regs)
>	{
>		wake_up(&cpld_intr_wait);
>		atomic_inc(&cpld_intr_data); /* incrementing this will
indicate the poll() that the interrupt is occured */
>		return 0;
>	}

You need to set 'cpld_intr_data' before clling wake_up() otherwise
the sleeping process might run on another cpu before the data item
changes.

You also don't need to use the 'atomic' functions.
Writing to a 'volatile' data item is sufficent.
You don't want to count interrupts, just mark they have happened.

Maybe your problem it that the ISR doesn't do anything to
cause the hardware to drop its IRQ.

	David

Re: BUG: scheduling while atomic:

[Scott Wood]

On 10/05/2011 06:24 AM, smitha.vanga@wipro.com wrote:
> Hi Scoot,
> 
>  When my  ISR gets exeuted I get a below BUG. Could let me what I am
> doing wrong in the ISR?
>  
>  
>  BUG: scheduling while atomic: IRQ-20/0x0fff0000/108
> Call Trace:
> [C3AEFEC0] [C0007CCC]  (unreliable)
> [C3AEFEF0] [C0017F10]
> [C3AEFF00] [C0268818]
> [C3AEFF50] [C0017F44]
> [C3AEFF60] [C0018044]
> [C3AEFF70] [C0046A90]
> [C3AEFF90] [C0046D90]
> [C3AEFFC0] [C0032AFC]
> [C3AEFFF0] [C000F5AC]

This trace is useless without debugging symbols from your kernel image.
Please enable kallsyms.

> Below is the code :
> *My ISR*
> 
> irqreturn_t cpld_irq_handler(int irq, void * dev_id, struct pt_regs *regs)
> 
> {
> 
> wake_up(&cpld_intr_wait);
> 
> atomic_inc(&cpld_intr_data); /* incrementing this will indicate the
> poll() that the interrupt is occured */

None of this should schedule when run in interrupt context.

The only thing that comes to mind is possibly wake_up(), if you're
running the RT patch but somehow the interrupt isn't in a thread.

> return 0;

Not related, but return IRQ_HANDLED;

-Scott

RE: BUG: scheduling while atomic:

[smitha.vanga]

 
Hi Scott,

Below are the logs when I enable the kallsyms.
Any suggestion.


sh-3.1# I am in cpld_irq_handler
end cpld_irq_handler
BUG: scheduling while atomic: IRQ-20/0x0fff0000/108
Call Trace:
[C3B13EC0] [C0007DD0] show_stack+0x3c/0x194 (unreliable)
[C3B13EF0] [C0017F70] __schedule_bug+0x34/0x44
[C3B13F00] [C0269E38] schedule+0x31c/0x35c
[C3B13F50] [C0017FA4] __cond_resched+0x24/0x50
[C3B13F60] [C00180A4] cond_resched_hardirq_context+0x8c/0xfc
[C3B13F70] [C0047FBC] thread_simple_irq+0x78/0xc4
[C3B13F90] [C00482BC] do_irqd+0x2b4/0x32c
[C3B13FC0] [C0032BAC] kthread+0xc0/0xfc
[C3B13FF0] [C000F60C] original_kernel_thread+0x44/0x60



Regards,
Smitha
Please do not print this email unless it is absolutely necessary. =0A=
=0A=
The information contained in this electronic message and any attachments to=
 this message are intended for the exclusive use of the addressee(s) and may=
 contain proprietary, confidential or privileged information. If you are not=
 the intended recipient, you should not disseminate, distribute or copy this=
 e-mail. Please notify the sender immediately and destroy all copies of this=
 message and any attachments. =0A=
=0A=
WARNING: Computer viruses can be transmitted via email. The recipient should=
 check this email and any attachments for the presence of viruses. The compa=
ny accepts no liability for any damage caused by any virus transmitted by th=
is email. =0A=
=0A=
www.wipro.com

I2c-cpm drievr not working

[smitha.vanga]

 
Hi Scott,

I am using the i2c-cpm driver to read and write to a LM75 sensor. The 
int i2c_master_send(struct i2c_client *client,const char *buf ,int count) fu=
nction is not successful.
Could you let me know what may be the issue. Below are the traces.

DS75_DRIVER : Open
DS75_DRIVER : Device Open Successful!
DS75_DRIVER  : ioctl TEMP_READ cmd 1
In i2c_master_send enter-------
In i2c_master_send enter [2]-------
In i2c_master_send msg.addr=3Dc031
In i2c_master_send 1 client->addr =3D0
In i2c_master_send 2
In i2c_master_send 3
In i2c_master_send 4
--- enter i2c_transfer
i2c_transfer_entry
*********** cpm_i2c_xfer
***********cpm_i2c_parse_message
***********cpm_i2c_check_message
*********** else
 rv =3D1
In i2c_master_send 5
 i2c_master_recv client.addr=3D0
--- enter i2c_transfer
i2c_transfer_entry
*********** cpm_i2c_xfer
***********cpm_i2c_parse_message
i2c_adapter i2c-0: I2C transfer: timeout
*********** cpm_i2c_xfer out_err
***********cpm_i2c_force_close
 rv =3Dffffff87
DS75_DRIVER  : Error reading from I2C 

Regards,
Smitha
Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to=
 this message are intended for the exclusive use of the addressee(s) and may=
 contain proprietary, confidential or privileged information. If you are not=
 the intended recipient, you should not disseminate, distribute or copy this=
 e-mail. Please notify the sender immediately and destroy all copies of this=
 message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should=
 check this email and any attachments for the presence of viruses. The compa=
ny accepts no liability for any damage caused by any virus transmitted by th=
is email. 

www.wipro.com

RE: I2c-cpm drievr not working

[Bhushan Bharat-R65777]

> -----Original Message-----
> From: linuxppc-dev-bounces+bharat.bhushan=3Dfreescale.com@lists.ozlabs.or=
g
> [mailto:linuxppc-dev-
> bounces+bharat.bhushan=3Dfreescale.com@lists.ozlabs.org] On Behalf Of
> smitha.vanga@wipro.com
> Sent: Friday, October 14, 2011 9:45 AM
> To: Wood Scott-B07421
> Cc: linuxppc-dev@lists.ozlabs.org
> Subject: I2c-cpm drievr not working
>=20
>=20
> Hi Scott,
>=20
> I am using the i2c-cpm driver to read and write to a LM75 sensor. The int
> i2c_master_send(struct i2c_client *client,const char *buf ,int count)
> function is not successful.
> Could you let me know what may be the issue. Below are the traces.
>=20
> DS75_DRIVER : Open
> DS75_DRIVER : Device Open Successful!
> DS75_DRIVER  : ioctl TEMP_READ cmd 1
> In i2c_master_send enter-------
> In i2c_master_send enter [2]-------
> In i2c_master_send msg.addr=3Dc031
> In i2c_master_send 1 client->addr =3D0
> In i2c_master_send 2
> In i2c_master_send 3
> In i2c_master_send 4
> --- enter i2c_transfer

I am a bit confused that i2c_transfer() is called after i2c_master_send is =
entered 4 times. Should not this be called every time ?

> i2c_transfer_entry
> *********** cpm_i2c_xfer
> ***********cpm_i2c_parse_message
> ***********cpm_i2c_check_message
> *********** else
>  rv =3D1
> In i2c_master_send 5
>  i2c_master_recv client.addr=3D0
> --- enter i2c_transfer

This time it is called on first shot.

Do you think you need to define I2C_CHIP_ERRATA ?

Thanks
-Bharat

> i2c_transfer_entry
> *********** cpm_i2c_xfer
> ***********cpm_i2c_parse_message
> i2c_adapter i2c-0: I2C transfer: timeout
> *********** cpm_i2c_xfer out_err
> ***********cpm_i2c_force_close
>  rv =3Dffffff87
> DS75_DRIVER  : Error reading from I2C
>=20
> Regards,
> Smitha
> Please do not print this email unless it is absolutely necessary.
>=20
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged information. If
> you are not the intended recipient, you should not disseminate,
> distribute or copy this e-mail. Please notify the sender immediately and
> destroy all copies of this message and any attachments.
>=20
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>=20
> www.wipro.com
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

RE: I2c-cpm driver not working

[smitha.vanga]

 Hi ,


I see that the i2c_master_send works but when I do a i2c_master_recv returns=
 with a error code -121.

What should be the i2c-base address be configured for the i2c-cpm driver for=
 mpc9247 . Also

When I pass the interrupt for this driver as 1 , I see the registered interr=
upt number as 10 in /proc/interrupts why is it like this?

Regards,
Smitha
Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to=
 this message are intended for the exclusive use of the addressee(s) and may=
 contain proprietary, confidential or privileged information. If you are not=
 the intended recipient, you should not disseminate, distribute or copy this=
 e-mail. Please notify the sender immediately and destroy all copies of this=
 message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should=
 check this email and any attachments for the presence of viruses. The compa=
ny accepts no liability for any damage caused by any virus transmitted by th=
is email. 

www.wipro.com

RE: I2c-cpm driver not working

[Bhushan Bharat-R65777]

Hi Smitha,

Can you provide the device tree information for i2c node?

Thanks
-Bharat

> -----Original Message-----
> From: smitha.vanga@wipro.com [mailto:smitha.vanga@wipro.com]
> Sent: Friday, October 14, 2011 3:33 PM
> To: Bhushan Bharat-R65777; Wood Scott-B07421
> Cc: linuxppc-dev@lists.ozlabs.org
> Subject: RE: I2c-cpm driver not working
>=20
>=20
>  Hi ,
>=20
>=20
> I see that the i2c_master_send works but when I do a i2c_master_recv
> returns with a error code -121.
>=20
> What should be the i2c-base address be configured for the i2c-cpm driver
> for mpc9247 . Also
>=20
> When I pass the interrupt for this driver as 1 , I see the registered
> interrupt number as 10 in /proc/interrupts why is it like this?
>=20
> Regards,
> Smitha
> Please do not print this email unless it is absolutely necessary.
>=20
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged information. If
> you are not the intended recipient, you should not disseminate,
> distribute or copy this e-mail. Please notify the sender immediately and
> destroy all copies of this message and any attachments.
>=20
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>=20
> www.wipro.com

RE: I2c-cpm driver not working

[smitha.vanga]

 
Hi Bhusan,

Below is i2c node in the device tree.

i2c@11860 {
				compatible =3D "fsl-i2c-cpm";
				device_type =3D "i2c";
	  			reg =3D <11860 20 8afc 2>;
				interrupts =3D <1 8>;
				interrupt-parent =3D <10c00>;
				#address-cells =3D <1>;
				#size-cells =3D <0>;
				cell-index =3D <0>;
				fsl,cpm-command =3D <29600000>;

				
			};


Regards,
Smitha
Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to=
 this message are intended for the exclusive use of the addressee(s) and may=
 contain proprietary, confidential or privileged information. If you are not=
 the intended recipient, you should not disseminate, distribute or copy this=
 e-mail. Please notify the sender immediately and destroy all copies of this=
 message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should=
 check this email and any attachments for the presence of viruses. The compa=
ny accepts no liability for any damage caused by any virus transmitted by th=
is email. 

www.wipro.com

RE: I2c-cpm driver not working

[Bhushan Bharat-R65777]

> -----Original Message-----
> From: linuxppc-dev-bounces+bharat.bhushan=3Dfreescale.com@lists.ozlabs.or=
g
> [mailto:linuxppc-dev-
> bounces+bharat.bhushan=3Dfreescale.com@lists.ozlabs.org] On Behalf Of
> smitha.vanga@wipro.com
> Sent: Monday, October 17, 2011 1:48 PM
> To: Bhushan Bharat-R65777; Wood Scott-B07421
> Cc: linuxppc-dev@lists.ozlabs.org
> Subject: RE: I2c-cpm driver not working
>=20
>=20
> Hi Bhusan,
>=20
> Below is i2c node in the device tree.
>=20
> i2c@11860 {
> 				compatible =3D "fsl-i2c-cpm";
> 				device_type =3D "i2c";
> 	  			reg =3D <11860 20 8afc 2>;
> 				interrupts =3D <1 8>;
> 				interrupt-parent =3D <10c00>;
> 				#address-cells =3D <1>;
> 				#size-cells =3D <0>;
> 				cell-index =3D <0>;
> 				fsl,cpm-command =3D <29600000>;
>=20
>=20
> 			};
>=20

This looks ok to me, I hope you provides proper reg, interrupt number, pola=
rity and sense (as per you mpc9247 specification)?

Thanks
-Bharat

>=20
> Regards,
> Smitha
> Please do not print this email unless it is absolutely necessary.
>=20
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s)
> and may contain proprietary, confidential or privileged information. If
> you are not the intended recipient, you should not disseminate,
> distribute or copy this e-mail. Please notify the sender immediately and
> destroy all copies of this message and any attachments.
>=20
> WARNING: Computer viruses can be transmitted via email. The recipient
> should check this email and any attachments for the presence of viruses.
> The company accepts no liability for any damage caused by any virus
> transmitted by this email.
>=20
> www.wipro.com
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

IRQ2 and IRQ 3

[smitha.vanga]

 
Hi ,

I want to use IRQ2 and IRQ3 in my driver. How do I add them in the device tr=
ee file.

Regard,
Smitha

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to=
 this message are intended for the exclusive use of the addressee(s) and may=
 contain proprietary, confidential or privileged information. If you are not=
 the intended recipient, you should not disseminate, distribute or copy this=
 e-mail. Please notify the sender immediately and destroy all copies of this=
 message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should=
 check this email and any attachments for the presence of viruses. The compa=
ny accepts no liability for any damage caused by any virus transmitted by th=
is email. 

www.wipro.com

BUG: scheduling while atomic: ..

[Kelly Bowa]

hi,
found following bug in 2.6.31-rc8. CPU model is Intel(R) Atom(TM) CPU N270. This is produced at boot time. I havent had time to look into this yet but looks like an ACPI bug to me..

<6>Checking 'hlt' instruction... OK.
<6>ACPI: Core revision 20090521
<3>BUG: scheduling while atomic: swapper/0/0x10000002
<4>Modules linked in:
<4>Pid: 0, comm: swapper Not tainted 2.6.31-git #3
<4>Call Trace:
<4> [<c0129e92>] __schedule_bug+0x4d/0x52
<4> [<c03a0354>] schedule+0x97/0xa6b
<4> [<c01b8e4a>] ? __slab_free+0xd7/0x2ab
<4> [<c01bf271>] ? put_object+0x3a/0x3d
<4> [<c02ce4d8>] ? acpi_debug_print+0xa/0xc2
<4> [<c02cb15d>] ? acpi_ps_pop_scope+0x79/0x84
<4> [<c02ce4d8>] ? acpi_debug_print+0xa/0xc2
<4> [<c012ba43>] __cond_resched+0x17/0x23
<4> [<c03a0e2e>] _cond_resched+0x20/0x2b
<4> [<c02ca71c>] acpi_ps_complete_op+0x214/0x223
<4> [<c02c9a8d>] ? acpi_ps_get_next_simple_arg+0xe0/0xeb
<4> [<c02cad98>] acpi_ps_parse_loop+0x66d/0x7bd
<4> [<c02ca089>] acpi_ps_parse_aml+0xd4/0x324
<4> [<c02c909a>] acpi_ns_one_complete_parse+0x10e/0x124
<4> [<c02c90e9>] acpi_ns_parse_table+0x39/0x78
<4> [<c02c5f57>] acpi_ns_load_table+0x63/0xe0
<4> [<c02ccea6>] acpi_load_tables+0x6b/0x13e
<4> [<c05606d1>] acpi_early_init+0x5d/0xeb
<4> [<c054180c>] start_kernel+0x2ce/0x2dd
<4> [<c0541091>] __init_begin+0x91/0x96
<3>BUG: scheduling while atomic: swapper/0/0x10000002
<4>Modules linked in:
<4>Pid: 0, comm: swapper Not tainted 2.6.31-git #3
<4>Call Trace:
<4> [<c0129e92>] __schedule_bug+0x4d/0x52
<4> [<c03a0354>] schedule+0x97/0xa6b
<4> [<c01b8e4a>] ? __slab_free+0xd7/0x2ab
<4> [<c01bf271>] ? put_object+0x3a/0x3d
<4> [<c02ce4d8>] ? acpi_debug_print+0xa/0xc2
<4> [<c02cb15d>] ? acpi_ps_pop_scope+0x79/0x84
<4> [<c02ce4d8>] ? acpi_debug_print+0xa/0xc2
<4> [<c012ba43>] __cond_resched+0x17/0x23
<4> [<c03a0e2e>] _cond_resched+0x20/0x2b
<4> [<c02ca71c>] acpi_ps_complete_op+0x214/0x223
<4> [<c02cad98>] acpi_ps_parse_loop+0x66d/0x7bd
<4> [<c02ca089>] acpi_ps_parse_aml+0xd4/0x324
<4> [<c02c909a>] acpi_ns_one_complete_parse+0x10e/0x124
<4> [<c02c90e9>] acpi_ns_parse_table+0x39/0x78
<4> [<c02c5f57>] acpi_ns_load_table+0x63/0xe0
<4> [<c02ccea6>] acpi_load_tables+0x6b/0x13e
<4> [<c05606d1>] acpi_early_init+0x5d/0xeb
<4> [<c054180c>] start_kernel+0x2ce/0x2dd
<4> [<c0541091>] __init_begin+0x91/0x96
<3>BUG: scheduling while atomic: swapper/0/0x10000002
<4>Modules linked in:
<4>Pid: 0, comm: swapper Not tainted 2.6.31-git #3
<4>Call Trace:
<4> [<c0129e92>] __schedule_bug+0x4d/0x52
<4> [<c03a0354>] schedule+0x97/0xa6b
<4> [<c01b8e4a>] ? __slab_free+0xd7/0x2ab
<4> [<c01bf271>] ? put_object+0x3a/0x3d
<4> [<c02ce4d8>] ? acpi_debug_print+0xa/0xc2
<4> [<c02cb15d>] ? acpi_ps_pop_scope+0x79/0x84
<4> [<c02ce4d8>] ? acpi_debug_print+0xa/0xc2
<4> [<c012ba43>] __cond_resched+0x17/0x23
<4> [<c03a0e2e>] _cond_resched+0x20/0x2b
<4> [<c02ca71c>] acpi_ps_complete_op+0x214/0x223
<4> [<c02cad98>] acpi_ps_parse_loop+0x66d/0x7bd
<4> [<c02ca089>] acpi_ps_parse_aml+0xd4/0x324
<4> [<c02c909a>] acpi_ns_one_complete_parse+0x10e/0x124
<4> [<c02c90e9>] acpi_ns_parse_table+0x39/0x78
<4> [<c02c5f57>] acpi_ns_load_table+0x63/0xe0
<4> [<c02ccea6>] acpi_load_tables+0x6b/0x13e
<4> [<c05606d1>] acpi_early_init+0x5d/0xeb
<4> [<c054180c>] start_kernel+0x2ce/0x2dd
<4> [<c0541091>] __init_begin+0x91/0x96
<3>BUG: scheduling while atomic: swapper/0/0x10000002
<4>Modules linked in:
<4>Pid: 0, comm: swapper Not tainted 2.6.31-git #3
<4>Call Trace:
<4> [<c0129e92>] __schedule_bug+0x4d/0x52
<4> [<c03a0354>] schedule+0x97/0xa6b
<4> [<c01b7e49>] ? init_object+0xe/0x67
<4> [<c03a49d1>] ? sub_preempt_count+0x9/0x9f
<4> [<c01ba21f>] ? kmem_cache_free+0x85/0xd5
<4> [<c02abae5>] ? acpi_os_release_object+0xd/0x11
<4> [<c02abae5>] ? acpi_os_release_object+0xd/0x11
<4> [<c02abae5>] ? acpi_os_release_object+0xd/0x11
<4> [<c02cb2c3>] ? acpi_ps_free_op+0x51/0x56
<4> [<c02cafd0>] ? acpi_ps_delete_parse_tree+0x38/0x50
<4> [<c012ba43>] __cond_resched+0x17/0x23
<4> [<c03a0e2e>] _cond_resched+0x20/0x2b
<4> [<c02ca71c>] acpi_ps_complete_op+0x214/0x223
<4> [<c02b8ab9>] ? acpi_ds_load2_end_op+0x1b3/0x3f6
<4> [<c02cad98>] acpi_ps_parse_loop+0x66d/0x7bd
<4> [<c02ca089>] acpi_ps_parse_aml+0xd4/0x324
<4> [<c02c909a>] acpi_ns_one_complete_parse+0x10e/0x124
<4> [<c02c911b>] acpi_ns_parse_table+0x6b/0x78
<4> [<c02c5f57>] acpi_ns_load_table+0x63/0xe0
<4> [<c02ccea6>] acpi_load_tables+0x6b/0x13e
<4> [<c05606d1>] acpi_early_init+0x5d/0xeb
<4> [<c054180c>] start_kernel+0x2ce/0x2dd
<4> [<c0541091>] __init_begin+0x91/0x96
<3>BUG: scheduling while atomic: swapper/0/0x10000002
<4>Modules linked in:
<4>Pid: 0, comm: swapper Not tainted 2.6.31-git #3
<4>Call Trace:
<4> [<c0129e92>] __schedule_bug+0x4d/0x52
<4> [<c03a0354>] schedule+0x97/0xa6b
<4> [<c01b8e4a>] ? __slab_free+0xd7/0x2ab
<4> [<c01bf271>] ? put_object+0x3a/0x3d
<4> [<c02ce4d8>] ? acpi_debug_print+0xa/0xc2
<4> [<c02cb15d>] ? acpi_ps_pop_scope+0x79/0x84
<4> [<c02ce4d8>] ? acpi_debug_print+0xa/0xc2
<4> [<c012ba43>] __cond_resched+0x17/0x23
<4> [<c03a0e2e>] _cond_resched+0x20/0x2b
<4> [<c02ca71c>] acpi_ps_complete_op+0x214/0x223
<4> [<c02cb21c>] ? acpi_ps_init_op+0x8/0x12
<4> [<c02c9a8d>] ? acpi_ps_get_next_simple_arg+0xe0/0xeb
<4> [<c02cad98>] acpi_ps_parse_loop+0x66d/0x7bd
<4> [<c02ca089>] acpi_ps_parse_aml+0xd4/0x324
<4> [<c02c909a>] acpi_ns_one_complete_parse+0x10e/0x124
<4> [<c02c911b>] acpi_ns_parse_table+0x6b/0x78
<4> [<c02c5f57>] acpi_ns_load_table+0x63/0xe0
<4> [<c02ccea6>] acpi_load_tables+0x6b/0x13e
<4> [<c05606d1>] acpi_early_init+0x5d/0xeb
<4> [<c054180c>] start_kernel+0x2ce/0x2dd
<4> [<c0541091>] __init_begin+0x91/0x96
<3>BUG: scheduling while atomic: swapper/0/0x10000002
<4>Modules linked in:
<4>Pid: 0, comm: swapper Not tainted 2.6.31-git #3
<4>Call Trace:
<4> [<c0129e92>] __schedule_bug+0x4d/0x52
<4> [<c03a0354>] schedule+0x97/0xa6b
<4> [<c01b7e49>] ? init_object+0xe/0x67
<4> [<c03a49d1>] ? sub_preempt_count+0x9/0x9f
<4> [<c01ba21f>] ? kmem_cache_free+0x85/0xd5
<4> [<c02abae5>] ? acpi_os_release_object+0xd/0x11
<4> [<c02abae5>] ? acpi_os_release_object+0xd/0x11
<4> [<c02abae5>] ? acpi_os_release_object+0xd/0x11
<4> [<c02cb2c3>] ? acpi_ps_free_op+0x51/0x56
<4> [<c02cafd0>] ? acpi_ps_delete_parse_tree+0x38/0x50
<4> [<c012ba43>] __cond_resched+0x17/0x23
<4> [<c03a0e2e>] _cond_resched+0x20/0x2b
<4> [<c02ca71c>] acpi_ps_complete_op+0x214/0x223
<4> [<c02b8ab9>] ? acpi_ds_load2_end_op+0x1b3/0x3f6
<4> [<c02cad98>] acpi_ps_parse_loop+0x66d/0x7bd
<4> [<c02ca089>] acpi_ps_parse_aml+0xd4/0x324
<4> [<c02c909a>] acpi_ns_one_complete_parse+0x10e/0x124
<4> [<c02c911b>] acpi_ns_parse_table+0x6b/0x78
<4> [<c02c5f57>] acpi_ns_load_table+0x63/0xe0
<4> [<c02ccea6>] acpi_load_tables+0x6b/0x13e
<4> [<c05606d1>] acpi_early_init+0x5d/0xeb
<4> [<c054180c>] start_kernel+0x2ce/0x2dd
<4> [<c0541091>] __init_begin+0x91/0x96
<6>ftrace: converting mcount calls to 0f 1f 44 00 00
<6>ftrace: allocating 14224 entries in 28 pages
<6>..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
<6>CPU0: Intel(R) Atom(TM) CPU N270   @ 1.60GHz stepping 02
<6>Booting processor 1 APIC 0x1 ip 0x6000
<6>Initializing CPU#1
.....

<3>BUG: using smp_processor_id() in preemptible [00000000] code: events/0/9
<4>caller is vmstat_update+0x14/0x3e
<4>Pid: 9, comm: events/0 Not tainted 2.6.31-git #3
<4>Call Trace:
<4> [<c039ff98>] ? printk+0x14/0x1c
<4> [<c0284e7a>] debug_smp_processor_id+0x9e/0xb4
<4> [<c01a4749>] vmstat_update+0x14/0x3e
<4> [<c0144a30>] worker_thread+0x15f/0x1e8
<4> [<c01a4735>] ? vmstat_update+0x0/0x3e
<4> [<c014809f>] ? autoremove_wake_function+0x0/0x38
<4> [<c01448d1>] ? worker_thread+0x0/0x1e8
<4> [<c0147d9e>] kthread+0x66/0x6b
<4> [<c0147d38>] ? kthread+0x0/0x6b
<4> [<c01035cf>] kernel_thread_helper+0x7/0x10
<3>BUG: using smp_processor_id() in preemptible [00000000] code: events/0/9
<4>caller is vmstat_update+0x2a/0x3e
<4>Pid: 9, comm: events/0 Not tainted 2.6.31-git #3
<4>Call Trace:
<4> [<c039ff98>] ? printk+0x14/0x1c
<4> [<c0284e7a>] debug_smp_processor_id+0x9e/0xb4
<4> [<c01a475f>] vmstat_update+0x2a/0x3e
<4> [<c0144a30>] worker_thread+0x15f/0x1e8
<4> [<c01a4735>] ? vmstat_update+0x0/0x3e
<4> [<c014809f>] ? autoremove_wake_function+0x0/0x38
<4> [<c01448d1>] ? worker_thread+0x0/0x1e8
<4> [<c0147d9e>] kthread+0x66/0x6b
<4> [<c0147d38>] ? kthread+0x0/0x6b
<4> [<c01035cf>] kernel_thread_helper+0x7/0x10

kbpm

Re: BUG: scheduling while atomic: ..

[Kelly Bowa]

* Kelly Bowa (kbpm@tuxedu.org) wrote:
> hi,
> found following bug in 2.6.31-rc8. CPU model is Intel(R) Atom(TM) CPU N270. 
> This is produced at boot time. I havent had time to look into this yet but 
> looks like an ACPI bug to me..
> 
also in dmesg i find:
kmemleak: 9 new suspected memory leaks (see /sys/kernel/debug/kmemleak)

kbpm