From: navych@126.com (Navy Cheng)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Is there a bug in dgnc.ko?
Date: Wed, 24 Feb 2016 19:57:01 +0800 [thread overview]
Message-ID: <20160224115701.GB1998@debian> (raw)
In-Reply-To: <20160224054356.GA1138@kroah.com>
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
> > sudo insmod ./dgnc.ko
> >
> > After I re-insmod the dgnc module, my laptop is breakdown.
>
> Then there's a bug to fix in the driver, it must not clean up everything
> properly. Based on a quick read of it, there is lots of things that
> need to be fixed in it, that's why it is in staging. If you are
> interested, I would suggest fixing this issue would be a great start.
I'm very glad to get your advice to fix this issue. As a kernelnewbies, I
have sent two patches about code cleaning to you, and they are merged to
the kernel tree. I realy interested to fix this bug to improve my
understanding of the kerenl.
Thank you.
next prev parent reply other threads:[~2016-02-24 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 4:57 Is there a bug in dgnc.ko? Navy Cheng
2016-02-24 5:37 ` Valdis.Kletnieks at vt.edu
2016-02-24 11:36 ` Navy Cheng
2016-02-24 5:43 ` Greg KH
2016-02-24 11:57 ` Navy Cheng [this message]
2016-02-24 12:03 ` Sudip Mukherjee
2016-02-25 7:05 ` Navy Cheng
2016-02-24 18:25 ` Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160224115701.GB1998@debian \
--to=navych@126.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).