[#5320] can not remove all installed module after modprobe bf537_lq035

Submitted By: Vivi Li

Open Date

2009-07-07 05:14:18 Close Date

2009-07-09 02:20:32

Priority:

Low Assignee:

Vivi Li

Status:

Closed Fixed In Release:

N/A

Found In Release:

N/A Release:

Category:

Drivers Board:

N/A

Processor:

BF537 Silicon Revision:

Is this bug repeatable?:

Yes Resolution:

Fixed

Uboot version or rev.:

Toolchain version or rev.:

gcc4.1_09r1-rc7

App binary format:

N/A

Summary: can not remove all installed module after modprobe bf537_lq035

Details:

Build lcd lq035 as module, when remove module, error message says "Resource temporarily unavailable". No all installed module can be removed. It's not a regression results.

Bellow is the log:

root:/> lsmod

Module Size Used by

root:/>

root:/> modprobe bf537_lq035

i2c-bfin-twi i2c-bfin-twi.0: Blackfin BF5xx on-chip I2C TWI Contoller, regs_base@ffc01400

bf537-lq035: FrameBuffer initializing...<6>Done.

root:/> lsmod

Module Size Used by

i2c_bfin_twi 5432 0

bf537_lq035 7932 0

cfbfillrect 2764 1 bf537_lq035

cfbimgblt 1604 1 bf537_lq035

lcd 2516 1 bf537_lq035

backlight 2652 1 bf537_lq035

cfbcopyarea 2540 1 bf537_lq035

i2c_core 14564 2 i2c_bfin_twi,bf537_lq035

root:/> video_test

^Croot:/>

root:/> modprobe -r bf537_lq035

bf537-lq035: Unregister LCD driver.

modprobe: Failed to unload module bf537_lq035: Resource temporarily unavailable.

root:/> lsmod

Module Size Used by

i2c_bfin_twi 5432 0

i2c_core 14564 1 i2c_bfin_twi

root:/>

Follow-ups

--- Mike Frysinger 2009-07-07 14:19:56

does it work if you manually remove i2c-bfin-twi and i2c-core ? there have been

some modprobe -r fixes added to busybox 1.14.x i believe ...

--- Vivi Li 2009-07-08 00:21:33

i2c-bfin-twi and i2c-core can be manually removed.

So we need to wait for the fixes of modprobe in busybox...

--- Mike Frysinger 2009-07-08 01:33:05

are you only seeing this on the branch ? i'll have to manually backport things

from trunk.

--- Vivi Li 2009-07-08 02:15:31

I checked with trunk, it seem alright.

This problem exists in 09r1 branch. In the older releases, I also find out

similar bug, only the error message changed a bit.

--- Mike Frysinger 2009-07-08 21:48:54

should be fixed now ... if dependent modules dont unload, we dont error out now

--- Vivi Li 2009-07-09 02:20:32

OK now. Close it.

Files

Changes

Commits

Dependencies

Duplicates

Associations