[#5924] Scheduling error shows up sometimes in latest trunk

Document created by Aaronwu Employee on Sep 10, 2013
Version 1Show Document
  • View in full screen mode

[#5924] Scheduling error shows up sometimes in latest trunk

Submitted By: Vivi Li

Open Date

2010-02-22 23:14:17    

Priority:

Low     Assignee:

Barry Song

Status:

Open     Fixed In Release:

N/A

Found In Release:

2010R1     Release:

Category:

N/A     Board:

N/A

Processor:

BF537     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Postponed

Uboot version or rev.:

    Toolchain version or rev.:

gcc4.3_trunk3815

App binary format:

N/A     

Summary: Scheduling error shows up sometimes in latest trunk

Details:

 

Scheduling error shows up when install usb1761 driver on bf537-stamp.

 

Bellow is the log:

--

root:/> modprobe isp1760

isp1760 isp1760.0: NXP ISP1760 USB Host Controller

isp1760 isp1760.0: new USB bus registered, assigned bus number 1

isp1760 isp1760.0: bus width: 16, oc: digital

isp1760 isp1760.0: irq 57, io mem 0x203c0000

isp1760 isp1760.0: USB ISP 1761 HW rev. 1 started

usb usb1: configuration #1 chosen from 1 choice

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

ISP1760 USB device initialised

root:/> port 1 high speed

usb 1-1: new high speed USB device using isp1760 and address 2

port 1 high speed

usb 1-1: configuration #1 chosen from 1 choice

hub 1-1:1.0: USB hub found

hub 1-1:1.0: 3 ports detected

usb 1-1.1: new high speed USB device using isp1760 and address 3

usb 1-1.1: configuration #1 chosen from 1 choice

scsi0 : SCSI emulation for USB Mass Storage devices

scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer           7.01 PQ: 0 ANSI: 0 CCS

scsi 0:0:0:1: CD-ROM            SanDisk  Cruzer           7.01 PQ: 0 ANSI: 0

sd 0:0:0:0: [sda] 1957887 512-byte logical blocks: (1.00 GB/955 MiB)

sd 0:0:0:0: [sda] Write Protect is off

sd 0:0:0:0: [sda] Assuming drive cache: write through

sd 0:0:0:0: [sda] Assuming drive cache: write through

sda:

BUG: scheduling while atomic: mdev/216/0x04000001

Modules linked in: isp1760

Hardware Trace:

   0 Target : <0x0013efb0> { _dump_stack + 0x0 }

     Source : <0x0000e2da> { ___schedule_bug + 0x5a } JUMP.L

   1 Target : <0x0000e2d4> { ___schedule_bug + 0x54 }

     Source : <0x0000e2c6> { ___schedule_bug + 0x46 } IF !CC JUMP

   2 Target : <0x0000e2ba> { ___schedule_bug + 0x3a }

     Source : <0x0002be54> { _print_modules + 0x4c } RTS

   3 Target : <0x0002be4e> { _print_modules + 0x46 }

     Source : <0x0013f134> { _printk + 0x14 } RTS

   4 Target : <0x0013f130> { _printk + 0x10 }

     Source : <0x00011aca> { _vprintk + 0x16a } RTS

   5 Target : <0x00011aa8> { _vprintk + 0x148 }

     Source : <0x00011bee> { _vprintk + 0x28e } JUMP.S

   6 Target : <0x00011bee> { _vprintk + 0x28e }

     Source : <0x000116fa> { _release_console_sem + 0x1ca } RTS

   7 Target : <0x000116f2> { _release_console_sem + 0x1c2 }

     Source : <0x000116e4> { _release_console_sem + 0x1b4 } IF !CC JUMP

   8 Target : <0x000116d4> { _release_console_sem + 0x1a4 }

     Source : <0x000116c6> { _release_console_sem + 0x196 } IF CC JUMP

   9 Target : <0x000116be> { _release_console_sem + 0x18e }

     Source : <0x00024232> { _up + 0x3e } RTS

  10 Target : <0x0002422c> { _up + 0x38 }

     Source : <0x0002421e> { _up + 0x2a } IF CC JUMP

  11 Target : <0x000241f4> { _up + 0x0 }

     Source : <0x000116ba> { _release_console_sem + 0x18a } CALL pcrel

  12 Target : <0x000116a6> { _release_console_sem + 0x176 }

     Source : <0x00011592> { _release_console_sem + 0x62 } IF !CC JUMP

  13 Target : <0x00011572> { _release_console_sem + 0x42 }

     Source : <0x000115c2> { _release_console_sem + 0x92 } IF CC JUMP

  14 Target : <0x000115b8> { _release_console_sem + 0x88 }

     Source : <0x00011292> { __call_console_drivers + 0x62 } RTS

  15 Target : <0x0001128c> { __call_console_drivers + 0x5c }

     Source : <0x00011266> { __call_console_drivers + 0x36 } IF !CC JUMP

Stack info:

SP: [0x02afbb2c] <0x02afbb2c> /* kernel dynamic memory */

Invalid stack pointer

sda1 sda2

sd 0:0:0:0: [sda] Assuming drive cache: write through

sd 0:0:0:0: [sda] Attached SCSI removable disk

 

root:/>

--

 

Last passed version:

--

kernel:    Linux release 2.6.32.8-ADI-2010R1-pre-svn8325, build #108 Sat Feb 20 17:39:00 CST 2010

toolchain: bfin-uclinux-gcc release gcc version 4.3.4 (ADI-trunk/svn-3815)

user-dist: release svn-9458, build #1943 Sat Feb 20 17:38:10 CST 2010

--

 

First failed version:

--

kernel:    Linux release 2.6.32.8-ADI-2010R1-pre-svn8329, build #112 Sun Feb 21 22:39:16 CST 2010

toolchain: bfin-uclinux-gcc release gcc version 4.3.4 (ADI-trunk/svn-3815)

user-dist: release svn-9458, build #2017 Sun Feb 21 22:38:24 CST 2010

--

 

Follow-ups

 

--- Vivi Li                                                  2010-02-22 23:32:36

I see similar error in other test, dmacopy, lmbench, etc...

 

--- Sonic Zhang                                              2010-02-22 23:50:07

May be caused by latest access_ok changes.

 

--- Barry Song                                               2010-02-24 23:21:33

Some kernel codes call access_ok in atomic context. So cause this problem. I

have reverted the new access_ok function. Let's handle it later.

 

 

 

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

 

File Name     File Type     File Size     Posted By

config.linux.usbhost_176x    application/octet-stream    40762    Vivi Li

Outcomes