From mboxrd@z Thu Jan 1 00:00:00 1970 From: navych@126.com (Navy Cheng) Date: Thu, 25 Feb 2016 15:05:14 +0800 Subject: Is there a bug in dgnc.ko? In-Reply-To: References: <20160224045742.GA24012@debian> <20160224054356.GA1138@kroah.com> <20160224115701.GB1998@debian> Message-ID: <20160225070514.GA26084@debian> To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Wed, Feb 24, 2016 at 05:33:11PM +0530, Sudip Mukherjee wrote: > On Wed, Feb 24, 2016 at 5:27 PM, Navy Cheng wrote: > > On Tue, Feb 23, 2016 at 09:43:56PM -0800, Greg KH wrote: > >> On Wed, Feb 24, 2016 at 12:57:42PM +0800, Navy Cheng wrote: > >> > Hi, > >> > > >> > My kernel version is v4.4, and I have built drivers/staging/dgnc/dgnc.ko. > >> > I change to *dir*/drivers/staging/dgnc and do like this: > >> > > >> > sudo insmod ./dgnc.ko > >> > >> Do you have the hardware that this driver controls? > > > > I'm not sure. My laptop is Dell Inspiron 14R - 5437 and I don't know if > > there is the right hardware. I often don't know about what a driver is used > > for in drivers/staging/. Is there any good way to know the function of a > > driver or module? > > > >> > >> > sudo lsmod | grep dgnc > >> > >> Does that show anything? > > > > Output: dgnc 65536 0 > > > >> > sudo rmmod ./dgnc > > what did dmesg showed after you did rmmod? > *dmesg* show nothing after I rmmod dgnc. I guess something wrong with dgnc_cleanup_module() which is called when dgnc is removed.