Bug 602682

Summary:	kernel oops after rmmod rfcomm
Product:	[openSUSE] openSUSE 11.2	Reporter:	Juergen Weigert <jw>
Component:	Kernel	Assignee:	E-mail List <kernel-maintainers>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	jslaby
Version:	Final
Target Milestone:	---
Hardware:	i586
OS:	Other
Whiteboard:
Found By:	Documentation	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Bug Depends on:
Bug Blocks:	357354
Attachments:	/var/log/messages excerpt

Description Juergen Weigert 2010-05-05 08:02:55 UTC

While trying to diagnose a non-responding bluetooth device, I wanted to make sure on which side the problem was. I found that it did not respond to l2ping, and started to unload modules.

both btusb and rmmod claimed that they were in use, although I could not find any active devices.

The following sequence then lead to an oops:

rmmod -f rfcomm
modprobe rfcomm
rfcomm bind 0
l2ping 00:26:69:58:F4:81
rmmod rfcomm

Comment 1 Juergen Weigert 2010-05-05 08:07:47 UTC

Created attachment 359379 [details]
/var/log/messages excerpt

Comment 2 Juergen Weigert 2010-05-05 08:08:45 UTC

this is a lenovo x60s, running 
Linux linux-k0t2 2.6.31.12-0.2-desktop #1 SMP PREEMPT 2010-03-16 21:25:39 +0100 i686 i686 i386 GNU/Linux

Comment 3 Nikanth Karthikesan 2010-05-11 06:20:26 UTC

Forced module unloading can always result in problems.

When rmmod claims that it is in use, can you try lsmod.
The lsmod shows the other modules, if any were using the module in question.

Comment 4 Jiri Slaby 2010-06-05 19:53:21 UTC

If this is also reproducible without forcing module unload, please reopen.