I should add that the rfcomm module may have a different timestamp because I moved it to rfcomm.ko.orig and back again, since before posting this I tried a patch from the kernel bugtracker to see if it resolves the problem; however, it doesn't.
I should add that the rfcomm module may have a different timestamp because I moved it to rfcomm.ko.orig and back again, since before posting this I tried a patch from the kernel bugtracker to see if it resolves the problem; however, it doesn't.