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:36:21 +0800 [thread overview]
Message-ID: <20160224113621.GA1998@debian> (raw)
In-Reply-To: <11119.1456292260@turing-police.cc.vt.edu>
On Wed, Feb 24, 2016 at 12:37:40AM -0500, Valdis.Kletnieks at vt.edu wrote:
> On Wed, 24 Feb 2016 12:57:42 +0800, Navy Cheng said:
> > 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
>
> What output, if any, did this generate?
No output. I use *dmesg* to find more information:
[ 572.915977] dgnc: module is from the staging directory, the quality is
unknown, you have been warned.
> > sudo lsmod | grep dgnc
>
> Again, what messages?
Output:
dgnc 65536 0
> > sudo rmmod ./dgnc
>
> Again, what happened?
No output. After *dmesg*, no more info in the ring buffer.
> > sudo insmod ./dgnc.ko
>
> And here?
No output.
> > After I re-insmod the dgnc module, my laptop is breakdown.
>
> What does "breakdown" mean? Did it hang entirely? Did you get a message
> in your dmesg output and/or on the console? Other?
The GUI stop work and any key in my laptop is not work. The *Caps Lock lamp*
in the keyboard is flashing.
> > My OS is debian 8.0. Is there a bug in dgnc.ko or something wrong with my
> > OS or kernel. If there is a bug, How can I find it?
>
> Start by providing enough info to see if there's a bug.
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2016-02-24 11:36 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 [this message]
2016-02-24 5:43 ` Greg KH
2016-02-24 11:57 ` Navy Cheng
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=20160224113621.GA1998@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).