<div dir="ltr">Hi Wenda Ni,<div><br></div><div>Please go through the following link to enable debugging output.Seems you have missed enabling DEBUG in Makefile. Hope it will help you.</div><div><br></div><div><a href="https://www.kernel.org/doc/local/pr_debug.txt">https://www.kernel.org/doc/local/pr_debug.txt</a></div><div><br></div><div><pre style="color:rgb(0,0,0);word-wrap:break-word;white-space:pre-wrap"><i>CFLAGS_[filename].o := -DDEBUG</i>
</pre><div><br></div><div><br></div><div><br></div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><p style="text-align:left"><font size="2"><span style="font-family:arial,helvetica,sans-serif"><b><span style="color:rgb(31,73,125)">With Best Regards,</span></b></span></font></p><p style="text-align:left"><font size="2"><span style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(89,89,89)">Sukanya Ch</span></span></font></p><p style="text-align:left"><font size="2"><span style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(89,89,89)">Software Engineer</span></span></font></p><p style="text-align:left"><font size="2"><span style="font-family:arial,helvetica,sans-serif"><span style="color:rgb(31,73,125)">VVDN Technologies Pvt Ltd</span></span></font></p><p style="text-align:left"><font size="2"><span style="font-family:arial,helvetica,sans-serif"><b><span style="color:rgb(31,73,125)">Cell : </span></b></span></font><span style="color:#1f497d"><font size="2"><span style="font-family:arial,helvetica,sans-serif">+91 9551955031 | <b>Skype :</b> sukanya.chinthamreddy</span></font><br></span></p>  <span style="color:#1f497d"></span></div></div></div></div></div>
<br><div class="gmail_quote">On Tue, Oct 18, 2016 at 7:44 PM,  <span dir="ltr">&lt;<a href="mailto:kernelnewbies-request@kernelnewbies.org" target="_blank">kernelnewbies-request@kernelnewbies.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Kernelnewbies mailing list submissions to<br>
        <a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
        <a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
        <a href="mailto:kernelnewbies-request@kernelnewbies.org">kernelnewbies-request@<wbr>kernelnewbies.org</a><br>
<br>
You can reach the person managing the list at<br>
        <a href="mailto:kernelnewbies-owner@kernelnewbies.org">kernelnewbies-owner@<wbr>kernelnewbies.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of Kernelnewbies digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
   1. kernel loglevel (Wenda Ni)<br>
   2. Re: kernel loglevel (Wenda Ni)<br>
   3. Re: kernel loglevel (Joel Fernandes)<br>
   4. Re: kernel loglevel (Thibaut SAUTEREAU)<br>
   5. Re: kernel loglevel (Wenda Ni)<br>
   6. Fw: TPS65910 Regulator Isuue (Amit Mahadik)<br>
<br>
<br>
------------------------------<wbr>------------------------------<wbr>----------<br>
<br>
Message: 1<br>
Date: Mon, 17 Oct 2016 19:17:32 -0400<br>
From: Wenda Ni &lt;<a href="mailto:wonda.ni@gmail.com">wonda.ni@gmail.com</a>&gt;<br>
Subject: kernel loglevel<br>
To: <a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a><br>
Message-ID:<br>
        &lt;CAEnvTt0RRDWtMD=<a href="mailto:VxVpuhiiJ%2BMRX2g3WiTgXkA-M5GGaTMyB-g@mail.gmail.com">VxVpuhiiJ+<wbr>MRX2g3WiTgXkA-M5GGaTMyB-g@<wbr>mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Dear all,<br>
<br>
I am working on a kernel module that incorporate both pr_debug and<br>
pr_warn. I would like to see pr_debug messages from dmesg.<br>
<br>
What I followed is to specify kernel parameter by saying &quot;loglevel=7&quot;.<br>
This can be seen confirmed  from /proc/cmdline. But still, I donot get<br>
pr_debug level messages either from dmesg or from /var/log/messages. I<br>
also tried echo 7 &gt; /proc/sys/kernel/printk. It does not return what I<br>
expect, either.<br>
<br>
Let me know what I am missing. Thank you very much in advance.<br>
<br>
Cheers,<br>
<br>
Wenda Ni, Ph.D.<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 17 Oct 2016 19:47:14 -0400<br>
From: Wenda Ni &lt;<a href="mailto:wonda.ni@gmail.com">wonda.ni@gmail.com</a>&gt;<br>
Subject: Re: kernel loglevel<br>
To: Thibaut SAUTEREAU &lt;<a href="mailto:thibaut.sautereau@telecom-sudparis.eu">thibaut.sautereau@telecom-<wbr>sudparis.eu</a>&gt;<br>
Cc: <a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a><br>
Message-ID:<br>
        &lt;<a href="mailto:CAEnvTt3oh%2BtuhKCwho8eZd5VmJfuXdcmWGpUpsjiH2wWSFpWvg@mail.gmail.com">CAEnvTt3oh+<wbr>tuhKCwho8eZd5VmJfuXdcmWGpUpsji<wbr>H2wWSFpWvg@mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=&quot;utf-8&quot;<br>
<br>
Thank you so much, Thibaut. I have spotted the source-code logic in<br>
include/linux/prink.h<br>
<br>
Cheers,<br>
<br>
Wenda Ni, Ph.D.<br>
<br>
<br>
<br>
On Mon, Oct 17, 2016 at 7:41 PM, Thibaut SAUTEREAU &lt;<br>
<a href="mailto:thibaut.sautereau@telecom-sudparis.eu">thibaut.sautereau@telecom-<wbr>sudparis.eu</a>&gt; wrote:<br>
&gt; On Mon, Oct 17, 2016 at 07:17:32PM -0400, Wenda Ni wrote:<br>
&gt;&gt; Dear all,<br>
&gt;&gt;<br>
&gt;&gt; I am working on a kernel module that incorporate both pr_debug and<br>
&gt;&gt; pr_warn. I would like to see pr_debug messages from dmesg.<br>
&gt;&gt;<br>
&gt;&gt; What I followed is to specify kernel parameter by saying &quot;loglevel=7&quot;.<br>
&gt;&gt; This can be seen confirmed  from /proc/cmdline. But still, I donot get<br>
&gt;&gt; pr_debug level messages either from dmesg or from /var/log/messages. I<br>
&gt;&gt; also tried echo 7 &gt; /proc/sys/kernel/printk. It does not return what I<br>
&gt;&gt; expect, either.<br>
&gt;&gt;<br>
&gt;&gt; Let me know what I am missing. Thank you very much in advance.<br>
&gt;&gt;<br>
&gt;&gt; Cheers,<br>
&gt;&gt;<br>
&gt;&gt; Wenda Ni, Ph.D.<br>
&gt;&gt;<br>
&gt;&gt; ______________________________<wbr>_________________<br>
&gt;&gt; Kernelnewbies mailing list<br>
&gt;&gt; <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.<wbr>org</a><br>
&gt;&gt; <a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
&gt;<br>
&gt; Hello Wenda,<br>
&gt;<br>
&gt; I encountered the same issue a while ago.<br>
&gt; As stated here: <a href="http://elinux.org/Debugging_by_printing" rel="noreferrer" target="_blank">http://elinux.org/Debugging_<wbr>by_printing</a><br>
&gt; pr_debug is replaced with an empty statement unless the kernel is compiled<br>
&gt; with DEBUG. So if you just want to play with printing kernel debug logs,<br>
&gt; just define the DEBUG macro in your module source file for testing.<br>
&gt;<br>
&gt; I also observed that without a new line character at the end of the string<br>
&gt; passed to pr_debug, I could not find the log line in dmesg output. Not<br>
sure<br>
&gt; where this comes from.<br>
&gt;<br>
&gt; --<br>
&gt; Thibaut SAUTEREAU<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161017/8f8419cb/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kernelnewbies.<wbr>org/pipermail/kernelnewbies/<wbr>attachments/20161017/8f8419cb/<wbr>attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 17 Oct 2016 16:48:46 -0700<br>
From: Joel Fernandes &lt;<a href="mailto:agnel.joel@gmail.com">agnel.joel@gmail.com</a>&gt;<br>
Subject: Re: kernel loglevel<br>
To: Wenda Ni &lt;<a href="mailto:wonda.ni@gmail.com">wonda.ni@gmail.com</a>&gt;<br>
Cc: &quot;<a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a>&quot;<br>
        &lt;<a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a>&gt;<br>
Message-ID:<br>
        &lt;CAD=<a href="mailto:GYpb-UKodnqeb0o71KytF_M2pLGV7bRzZ3YL4Ck0GqLdU%2BA@mail.gmail.com">GYpb-UKodnqeb0o71KytF_<wbr>M2pLGV7bRzZ3YL4Ck0GqLdU+A@<wbr>mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Hi Wenda,<br>
<br>
pr_debug needs you to define the DEBUG macro to activate it.<br>
<br>
Check:<br>
<a href="http://stackoverflow.com/questions/28936199/pr-debug-not-giving-any-output" rel="noreferrer" target="_blank">http://stackoverflow.com/<wbr>questions/28936199/pr-debug-<wbr>not-giving-any-output</a><br>
<br>
and the kernel docs,<br>
<a href="https://www.kernel.org/doc/local/pr_debug.txt" rel="noreferrer" target="_blank">https://www.kernel.org/doc/<wbr>local/pr_debug.txt</a><br>
<br>
Joel<br>
<br>
On Mon, Oct 17, 2016 at 4:17 PM, Wenda Ni &lt;<a href="mailto:wonda.ni@gmail.com">wonda.ni@gmail.com</a>&gt; wrote:<br>
&gt; Dear all,<br>
&gt;<br>
&gt; I am working on a kernel module that incorporate both pr_debug and<br>
&gt; pr_warn. I would like to see pr_debug messages from dmesg.<br>
&gt;<br>
&gt; What I followed is to specify kernel parameter by saying &quot;loglevel=7&quot;.<br>
&gt; This can be seen confirmed  from /proc/cmdline. But still, I donot get<br>
&gt; pr_debug level messages either from dmesg or from /var/log/messages. I<br>
&gt; also tried echo 7 &gt; /proc/sys/kernel/printk. It does not return what I<br>
&gt; expect, either.<br>
&gt;<br>
&gt; Let me know what I am missing. Thank you very much in advance.<br>
&gt;<br>
&gt; Cheers,<br>
&gt;<br>
&gt; Wenda Ni, Ph.D.<br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; Kernelnewbies mailing list<br>
&gt; <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.<wbr>org</a><br>
&gt; <a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Tue, 18 Oct 2016 01:41:57 +0200<br>
From: Thibaut SAUTEREAU &lt;<a href="mailto:thibaut.sautereau@telecom-sudparis.eu">thibaut.sautereau@telecom-<wbr>sudparis.eu</a>&gt;<br>
Subject: Re: kernel loglevel<br>
To: Wenda Ni &lt;<a href="mailto:wonda.ni@gmail.com">wonda.ni@gmail.com</a>&gt;<br>
Cc: <a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a><br>
Message-ID: &lt;<a href="mailto:20161017234156.GB1191@mines-telecom.fr">20161017234156.GB1191@mines-<wbr>telecom.fr</a>&gt;<br>
Content-Type: text/plain; charset=&quot;utf-8&quot;<br>
<br>
On Mon, Oct 17, 2016 at 07:17:32PM -0400, Wenda Ni wrote:<br>
&gt; Dear all,<br>
&gt;<br>
&gt; I am working on a kernel module that incorporate both pr_debug and<br>
&gt; pr_warn. I would like to see pr_debug messages from dmesg.<br>
&gt;<br>
&gt; What I followed is to specify kernel parameter by saying &quot;loglevel=7&quot;.<br>
&gt; This can be seen confirmed  from /proc/cmdline. But still, I donot get<br>
&gt; pr_debug level messages either from dmesg or from /var/log/messages. I<br>
&gt; also tried echo 7 &gt; /proc/sys/kernel/printk. It does not return what I<br>
&gt; expect, either.<br>
&gt;<br>
&gt; Let me know what I am missing. Thank you very much in advance.<br>
&gt;<br>
&gt; Cheers,<br>
&gt;<br>
&gt; Wenda Ni, Ph.D.<br>
&gt;<br>
&gt; ______________________________<wbr>_________________<br>
&gt; Kernelnewbies mailing list<br>
&gt; <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.<wbr>org</a><br>
&gt; <a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
<br>
Hello Wenda,<br>
<br>
I encountered the same issue a while ago.<br>
As stated here: <a href="http://elinux.org/Debugging_by_printing" rel="noreferrer" target="_blank">http://elinux.org/Debugging_<wbr>by_printing</a><br>
pr_debug is replaced with an empty statement unless the kernel is compiled<br>
with DEBUG. So if you just want to play with printing kernel debug logs,<br>
just define the DEBUG macro in your module source file for testing.<br>
<br>
I also observed that without a new line character at the end of the string<br>
passed to pr_debug, I could not find the log line in dmesg output. Not sure<br>
where this comes from.<br>
<br>
--<br>
Thibaut SAUTEREAU<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: not available<br>
Type: application/pgp-signature<br>
Size: 455 bytes<br>
Desc: not available<br>
Url : <a href="http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161018/d282cce1/attachment-0001.bin" rel="noreferrer" target="_blank">http://lists.kernelnewbies.<wbr>org/pipermail/kernelnewbies/<wbr>attachments/20161018/d282cce1/<wbr>attachment-0001.bin</a><br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Mon, 17 Oct 2016 20:29:33 -0400<br>
From: Wenda Ni &lt;<a href="mailto:wonda.ni@gmail.com">wonda.ni@gmail.com</a>&gt;<br>
Subject: Re: kernel loglevel<br>
To: Joel Fernandes &lt;<a href="mailto:agnel.joel@gmail.com">agnel.joel@gmail.com</a>&gt;<br>
Cc: &quot;<a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a>&quot;<br>
        &lt;<a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a>&gt;<br>
Message-ID:<br>
        &lt;<a href="mailto:CAEnvTt0BmAJ_nxf0oEUsFqqJjGssuXCQBg6pdt95Jk3PyBBQew@mail.gmail.com">CAEnvTt0BmAJ_<wbr>nxf0oEUsFqqJjGssuXCQBg6pdt95Jk<wbr>3PyBBQew@mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=&quot;utf-8&quot;<br>
<br>
Hi Joel,<br>
<br>
It works by specifying ccflags-y += -DDEBUG in the Makefile.<br>
<br>
Thank you for the info!!!!<br>
<br>
<br>
Cheers,<br>
<br>
Wenda Ni, Ph.D.<br>
<br>
<br>
On Mon, Oct 17, 2016 at 7:48 PM, Joel Fernandes &lt;<a href="mailto:agnel.joel@gmail.com">agnel.joel@gmail.com</a>&gt;<br>
wrote:<br>
<br>
&gt; Hi Wenda,<br>
&gt;<br>
&gt; pr_debug needs you to define the DEBUG macro to activate it.<br>
&gt;<br>
&gt; Check:<br>
&gt; <a href="http://stackoverflow.com/questions/28936199/pr-debug-not-giving-any-output" rel="noreferrer" target="_blank">http://stackoverflow.com/<wbr>questions/28936199/pr-debug-<wbr>not-giving-any-output</a><br>
&gt;<br>
&gt; and the kernel docs,<br>
&gt; <a href="https://www.kernel.org/doc/local/pr_debug.txt" rel="noreferrer" target="_blank">https://www.kernel.org/doc/<wbr>local/pr_debug.txt</a><br>
&gt;<br>
&gt; Joel<br>
&gt;<br>
&gt; On Mon, Oct 17, 2016 at 4:17 PM, Wenda Ni &lt;<a href="mailto:wonda.ni@gmail.com">wonda.ni@gmail.com</a>&gt; wrote:<br>
&gt; &gt; Dear all,<br>
&gt; &gt;<br>
&gt; &gt; I am working on a kernel module that incorporate both pr_debug and<br>
&gt; &gt; pr_warn. I would like to see pr_debug messages from dmesg.<br>
&gt; &gt;<br>
&gt; &gt; What I followed is to specify kernel parameter by saying &quot;loglevel=7&quot;.<br>
&gt; &gt; This can be seen confirmed  from /proc/cmdline. But still, I donot get<br>
&gt; &gt; pr_debug level messages either from dmesg or from /var/log/messages. I<br>
&gt; &gt; also tried echo 7 &gt; /proc/sys/kernel/printk. It does not return what I<br>
&gt; &gt; expect, either.<br>
&gt; &gt;<br>
&gt; &gt; Let me know what I am missing. Thank you very much in advance.<br>
&gt; &gt;<br>
&gt; &gt; Cheers,<br>
&gt; &gt;<br>
&gt; &gt; Wenda Ni, Ph.D.<br>
&gt; &gt;<br>
&gt; &gt; ______________________________<wbr>_________________<br>
&gt; &gt; Kernelnewbies mailing list<br>
&gt; &gt; <a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.<wbr>org</a><br>
&gt; &gt; <a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
&gt;<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161017/16f479c1/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.kernelnewbies.<wbr>org/pipermail/kernelnewbies/<wbr>attachments/20161017/16f479c1/<wbr>attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Tue, 18 Oct 2016 14:11:41 +0000 (UTC)<br>
From: Amit Mahadik &lt;<a href="mailto:amitmahadik35@yahoo.com">amitmahadik35@yahoo.com</a>&gt;<br>
Subject: Fw: TPS65910 Regulator Isuue<br>
To: Kernelnewbies &lt;<a href="mailto:kernelnewbies@kernelnewbies.org">kernelnewbies@kernelnewbies.<wbr>org</a>&gt;<br>
Message-ID: &lt;<a href="mailto:1865063607.2350837.1476799901899@mail.yahoo.com">1865063607.2350837.<wbr>1476799901899@mail.yahoo.com</a>&gt;<br>
Content-Type: text/plain; charset=&quot;utf-8&quot;<br>
<br>
<br>
<br>
<br>
Hi,? ? ?I am working on integrating TPS695190 regulator code into kernel version 4.4.16. The regulator powers MMC card slot using Designware MMC controller. I have declared the necessary code in my board.c file. The MMC card slot is powered by ldo8 supply declared as<br>
------------------------------<wbr>------------------------------<wbr>-----------------Code---------<wbr>------------------------------<wbr>------------------------------<wbr>------------<br>
<br>
static struct regulator_consumer_supply opv5xc_ldo8_supply[] = {<br>
??????? REGULATOR_SUPPLY(&quot;sd_vdd&quot;, NULL),<br>
};<br>
<br>
static struct regulator_init_data opv5xc_ldo8 = {<br>
??????? .constraints = {<br>
??????????????? .min_uV = 1000000,<br>
??????????????? .max_uV = 3300000,<br>
??????????????? .valid_ops_mask = (REGULATOR_CHANGE_VOLTAGE |<br>
??????????????????????????????<wbr>? REGULATOR_CHANGE_STATUS),<br>
??????????????? .boot_on = 1,<br>
??????? },<br>
??????? .num_consumer_supplies = ARRAY_SIZE(opv5xc_ldo8_supply)<wbr>,<br>
??????? .consumer_supplies = opv5xc_ldo8_supply,<br>
};<br>
static struct tps65910_board tps65910_pdata = {<br>
????? ??????? .tps65910_pmic_init_data[<wbr>TPS65911_REG_LDO8]???? = &amp;opv5xc_ldo8,<br>
};<br>
static struct i2c_board_info __initdata opv5xc_i2c1_devs[] = {<br>
??????? {<br>
??????????????? I2C_BOARD_INFO (&quot;tps65911&quot;, TPS65910_I2C_ID1),<br>
??????????????? .platform_data = &amp;tps65910_pdata,<br>
??????? },<br>
};<br>
------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>------------------------------<wbr>-----------------<br>
When I call regulator_get struct regulator *sd_vdd = regulator_get(NULL, &quot;sd_vdd&quot;);? function from the Designware MMC driver code function the kernel panics.I have attached the log file for reference. Can somebody please let me know what I am doing wrong here?<br>
Regards,Amit.<br>
<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161018/389572dc/attachment.html" rel="noreferrer" target="_blank">http://lists.kernelnewbies.<wbr>org/pipermail/kernelnewbies/<wbr>attachments/20161018/389572dc/<wbr>attachment.html</a><br>
-------------- next part --------------<br>
An embedded and charset-unspecified text was scrubbed...<br>
Name: log.txt<br>
Url: <a href="http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161018/389572dc/attachment.txt" rel="noreferrer" target="_blank">http://lists.kernelnewbies.<wbr>org/pipermail/kernelnewbies/<wbr>attachments/20161018/389572dc/<wbr>attachment.txt</a><br>
<br>
------------------------------<br>
<br>
______________________________<wbr>_________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org">Kernelnewbies@kernelnewbies.<wbr>org</a><br>
<a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.<wbr>org/mailman/listinfo/<wbr>kernelnewbies</a><br>
<br>
<br>
End of Kernelnewbies Digest, Vol 71, Issue 22<br>
******************************<wbr>***************<br>
</blockquote></div><br></div>