Re: Mentor

2015-11-02 Thread Chris Lee
Best thing to do is determine what you are interested in. Pick an area and
start studying. The kernel is to big imo to be floating around everywhere.
I picked dvb drivers, others are interested in networking or graphics etc.

UDL

On Mon, Nov 2, 2015, 9:02 AM Ranjith T  wrote:

> Hi,
>
> I am Ranjith from India and I would like to contribute something for
> linux kernel. But I really don't know from where I have to start.(I
> have submitted linux kernel patch already).
>
> Thanks,
> Ranjith.T.
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: videobuf2_core oops, recent media_build. dvbsky t980c's

2014-12-29 Thread Chris Lee
I'm running 3.19.0-rc1

This started on the Prof 7301 in the 3.18 kernel when vb2 was
implemented in the cx88 driver, previously vb2 wasn't used.

I do a lot of work in the dvb side of the media kernels but have never
done any work on the vb2 side of things and don't really feel
comfortable messing around in there. I'll stick to what I know.

Ive reported it in the V4L media mailing list, we'll see if it gets
any attention there.

Chris Lee

On Mon, Dec 29, 2014 at 12:11 PM, nick  wrote:
> Chris,
> Please try the latest rc kernel to see if the issue is fixed.
> Regards Nick
>
> On 2014-12-29 09:47 AM, Chris Lee wrote:
>> Im seeing the same issue and others using the Prof 7301, different
>> drivers, same vb2 usage though. Its defn a vb2 issue across multiple
>> devices :(
>>
>> Chris Lee
>>
>> On Mon, Dec 29, 2014 at 7:47 AM, Chris Lee  wrote:
>>> Im seeing the same issue and others using the Prof 7301, different
>>> drivers, same vb2 usage though. Its defn a vb2 issue across multiple
>>> devices :(
>>>
>>> Chris Lee
>>>
>>> On Mon, Dec 29, 2014 at 7:38 AM, Jurgen Kramer  wrote:
>>>>
>>>> On Sat, 2014-12-27 at 10:35 +0100, Jurgen Kramer wrote:
>>>>> I am seeing kernel oopses using recent media_builds on kernel 3.17:
>>>>>
>>>>> [  506.969697] BUG: unable to handle kernel NULL pointer dereference at
>>>>> 0058
>>>>> [  506.969720] IP: [] vb2_thread+0x17a/0x480
>>>>> [videobuf2_core]
>>>>> [  506.969739] PGD 0
>>>>> [  506.969746] Oops: 0002 [#1] SMP
>>>>> [  506.969754] Modules linked in: nf_conntrack_netbios_ns
>>>>> nf_conntrack_broadcast cfg80211 rfkill ip6t_rpfilter ip6t_REJECT
>>>>> xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter
>>>>> ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6
>>>>> ip6table_mangle ip6table_security ip6table_raw ip6table_filter
>>>>> ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
>>>>> nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw sp2(OE)
>>>>> si2157(OE) si2168(OE) i2c_mux nouveau cx25840(OE) cx23885(OE)
>>>>> altera_ci(OE) tda18271(OE) altera_stapl(OE) videobuf2_dvb(OE)
>>>>> videobuf2_core(OE) videobuf2_dma_sg(OE) videobuf2_memops(OE) snd_seq
>>>>> snd_seq_device snd_pcm snd_timer snd video i2c_algo_bit ttm
>>>>> drm_kms_helper soundcore iTCO_wdt ppdev gpio_ich iTCO_vendor_support
>>>>> tveeprom(OE) cx2341x(OE)
>>>>> [  506.969871]  coretemp dvb_core(OE) v4l2_common(OE) videodev(OE)
>>>>> media(OE) kvm crc32c_intel raid456 async_raid6_recov async_memcpy
>>>>> async_pq async_xor drm xor async_tx raid6_pq microcode serio_raw shpchp
>>>>> i7core_edac edac_core i2c_i801 lpc_ich mfd_core parport_pc parport
>>>>> ite_cir(OE) rc_core(OE) tpm_infineon tpm_tis tpm acpi_cpufreq nfsd
>>>>> auth_rpcgss nfs_acl lockd sunrpc mxm_wmi asix usbnet r8169 mii wmi
>>>>> [  506.969970] CPU: 0 PID: 3160 Comm: vb2-cx23885[0] Tainted: G
>>>>> OE  3.17.4-200.fc20.x86_64 #1
>>>>> [  506.969982] Hardware name: To Be Filled By O.E.M. To Be Filled By
>>>>> O.E.M./P55 Extreme, BIOS P2.70 08/20/2010
>>>>> [  506.969993] task: 8800bc18e220 ti: 88020d36c000 task.ti:
>>>>> 88020d36c000
>>>>> [  506.970002] RIP: 0010:[]  []
>>>>> vb2_thread+0x17a/0x480 [videobuf2_core]
>>>>> [  506.970021] RSP: 0018:88020d36fe68  EFLAGS: 00010246
>>>>> [  506.970663] RAX:  RBX:  RCX:
>>>>> 000b
>>>>> [  506.971305] RDX: 0058 RSI: 8800bc18e220 RDI:
>>>>> 0058
>>>>> [  506.971952] RBP: 88020d36fec0 R08: 88020d36c000 R09:
>>>>> 158f
>>>>> [  506.972611] R10: 30de R11: 0010 R12:
>>>>> 0058
>>>>> [  506.973275] R13: 8800b81814a0 R14:  R15:
>>>>> 880225c61028
>>>>> [  506.973947] FS:  () GS:880233c0()
>>>>> knlGS:
>>>>> [  506.974634] CS:  0010 DS:  ES:  CR0: 8005003b
>>>>> [  506.975321] CR2: 0058 CR3: 01c14000 CR4:
>>>>> 07f0
>>>>> [  506

Re: videobuf2_core oops, recent media_build. dvbsky t980c's

2014-12-29 Thread Chris Lee
Im seeing the same issue and others using the Prof 7301, different
drivers, same vb2 usage though. Its defn a vb2 issue across multiple
devices :(

Chris Lee

On Mon, Dec 29, 2014 at 7:47 AM, Chris Lee  wrote:
> Im seeing the same issue and others using the Prof 7301, different
> drivers, same vb2 usage though. Its defn a vb2 issue across multiple
> devices :(
>
> Chris Lee
>
> On Mon, Dec 29, 2014 at 7:38 AM, Jurgen Kramer  wrote:
>>
>> On Sat, 2014-12-27 at 10:35 +0100, Jurgen Kramer wrote:
>>> I am seeing kernel oopses using recent media_builds on kernel 3.17:
>>>
>>> [  506.969697] BUG: unable to handle kernel NULL pointer dereference at
>>> 0058
>>> [  506.969720] IP: [] vb2_thread+0x17a/0x480
>>> [videobuf2_core]
>>> [  506.969739] PGD 0
>>> [  506.969746] Oops: 0002 [#1] SMP
>>> [  506.969754] Modules linked in: nf_conntrack_netbios_ns
>>> nf_conntrack_broadcast cfg80211 rfkill ip6t_rpfilter ip6t_REJECT
>>> xt_conntrack ebtable_nat ebtable_broute bridge stp llc ebtable_filter
>>> ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6
>>> ip6table_mangle ip6table_security ip6table_raw ip6table_filter
>>> ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
>>> nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw sp2(OE)
>>> si2157(OE) si2168(OE) i2c_mux nouveau cx25840(OE) cx23885(OE)
>>> altera_ci(OE) tda18271(OE) altera_stapl(OE) videobuf2_dvb(OE)
>>> videobuf2_core(OE) videobuf2_dma_sg(OE) videobuf2_memops(OE) snd_seq
>>> snd_seq_device snd_pcm snd_timer snd video i2c_algo_bit ttm
>>> drm_kms_helper soundcore iTCO_wdt ppdev gpio_ich iTCO_vendor_support
>>> tveeprom(OE) cx2341x(OE)
>>> [  506.969871]  coretemp dvb_core(OE) v4l2_common(OE) videodev(OE)
>>> media(OE) kvm crc32c_intel raid456 async_raid6_recov async_memcpy
>>> async_pq async_xor drm xor async_tx raid6_pq microcode serio_raw shpchp
>>> i7core_edac edac_core i2c_i801 lpc_ich mfd_core parport_pc parport
>>> ite_cir(OE) rc_core(OE) tpm_infineon tpm_tis tpm acpi_cpufreq nfsd
>>> auth_rpcgss nfs_acl lockd sunrpc mxm_wmi asix usbnet r8169 mii wmi
>>> [  506.969970] CPU: 0 PID: 3160 Comm: vb2-cx23885[0] Tainted: G
>>> OE  3.17.4-200.fc20.x86_64 #1
>>> [  506.969982] Hardware name: To Be Filled By O.E.M. To Be Filled By
>>> O.E.M./P55 Extreme, BIOS P2.70 08/20/2010
>>> [  506.969993] task: 8800bc18e220 ti: 88020d36c000 task.ti:
>>> 88020d36c000
>>> [  506.970002] RIP: 0010:[]  []
>>> vb2_thread+0x17a/0x480 [videobuf2_core]
>>> [  506.970021] RSP: 0018:88020d36fe68  EFLAGS: 00010246
>>> [  506.970663] RAX:  RBX:  RCX:
>>> 000b
>>> [  506.971305] RDX: 0058 RSI: 8800bc18e220 RDI:
>>> 0058
>>> [  506.971952] RBP: 88020d36fec0 R08: 88020d36c000 R09:
>>> 158f
>>> [  506.972611] R10: 30de R11: 0010 R12:
>>> 0058
>>> [  506.973275] R13: 8800b81814a0 R14:  R15:
>>> 880225c61028
>>> [  506.973947] FS:  () GS:880233c0()
>>> knlGS:
>>> [  506.974634] CS:  0010 DS:  ES:  CR0: 8005003b
>>> [  506.975321] CR2: 0058 CR3: 01c14000 CR4:
>>> 07f0
>>> [  506.976021] Stack:
>>> [  506.976723]  8800bc18e220 0070 00ff81c1b460
>>> 
>>> [  506.977442]  8802 880225c61028 88020d1d8480
>>> 880225c61028
>>> [  506.978165]  a03a21c0  
>>> 88020d36ff48
>>> [  506.979055] Call Trace:
>>> [  506.979795]  [] ? vb2_internal_qbuf+0x210/0x210
>>> [videobuf2_core]
>>> [  506.980545]  [] kthread+0xd8/0xf0
>>> [  506.981293]  [] ? kthread_create_on_node
>>> +0x190/0x190
>>> [  506.982045]  [] ret_from_fork+0x7c/0xb0
>>> [  506.982806]  [] ? kthread_create_on_node
>>> +0x190/0x190
>>> [  506.983568] Code: 89 e7 ba 58 00 00 00 0f 85 94 01 00 00 40 f6 c7 02
>>> 0f 85 72 01 00 00 40 f6 c7 04 0f 85 50 01 00 00 89 d1 31 c0 c1 e9 03 f6
>>> c2 04  48 ab 74 0a c7 07 00 00 00 00 48 83 c7 04 f6 c2 02 74 0a 31
>>> [  506.984464] RIP  [] vb2_thread+0x17a/0x480
>>> [videobuf2_core]
>>> [  506.985306]  RSP 
>>> [  506.986147] CR2: 0058
>>> [  506.990986] ---[ end trac

Re: Bad Commit for Current Lockups

2014-12-11 Thread Chris Lee
Did you test this theory or just do a simple search and make an
assumption? Did you test before and after reverting the patch?

You cant just make a statement without backing it up.

Chris

On Thu, Dec 11, 2014 at 7:37 AM, nick  wrote:
> Greetings,
> I send Dave, what I feel is the bad commit for the current lockups found in 
> kernel 3.18 r4. The bad commit I believe is 
> 4995ab9cf512e9a6cc07dfd6b1d4e2fc48ce7fef as it does touch the TLB code in the 
> function that is most likely causing issues.
> Nick
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies


Re: A quick guide to why stand-alone checkpatch patches suck...

2014-09-17 Thread Chris Lee
>
> Rday,
> I meant I didn't understand the code not the effect to write good solid
> patches and learn it.
> Please read my messages more carefully.
> Nick
>
> ___
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies



Terrible reason to submit a patch. If you dont understand the code snippet,
you should not be submitting patch's against them. You need to fully
understand the code inside and out before you even consider fixing it.

Chris
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies