RE: about the kernelnewbies email signature
Oh, I see..that was the case.. I can see in the replies it's included. Thanks! From : Kristofer Hallin kristofer.hal...@gmail.com Sent : 2014-04-09 13:23:41 ( +09:00 ) To : Chan Kim c...@etri.re.kr Cc : kernelnewbies@kernelnewbies.org kernelnewbies@kernelnewbies.org, Sam Dodrill shadow.h...@gmail.com Subject : RE: about the kernelnewbies email signature As far as I can see it's included in the mails you send to the list. On 9 Apr 2014 06:19, Chan Kim c...@etri.re.krmailto:c...@etri.re.kr wrote: Yeah, that's what I expected. But everytime I write an email, I don't see that attached for mine. Where should I set it up? I tried kernelnewbies email setup page but couldn't find it. Maybe something in my mail server(sender) is preventing it from being done. like language option? From : Sam Dodrill shadow.h...@gmail.commailto:shadow.h...@gmail.com Sent : 2014-04-09 13:15:41 ( +09:00 ) To : kernelnewbies@kernelnewbies.orgmailto:kernelnewbies@kernelnewbies.org kernelnewbies@kernelnewbies.orgmailto:kernelnewbies@kernelnewbies.org Cc : Subject : Re: about the kernelnewbies email signature The mailing list server does that for you. On Wed, Apr 09, 2014 at 02:29:30AM +, Chan Kim wrote: Hi, How come some people's email contain the email signature shown below ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.orgmailto:Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies .. while my email doesn't have it attached? Are those people explicitly inserting it? or is there any option? Thanks in advance. Chan ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.orgmailto:Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies -- Sam Dodrill shadow.h...@gmail.commailto:shadow.h...@gmail.com vim: set ts=4 sw=8 tw=75 et : ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.orgmailto:Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Gianfar Ethernet Device Driver used in MPC8641D-HPCN
Hi,
I Have MPC8641D-HPCN based custom designed board and After some changes the
Linux 3.14 is now booting on my board. we are using same phy device ie
vitesse vsc8244. The Difference between my board and the original board is
in only PHY interrupt ie
Our custom Designed Board MPC8641D-HPCN original board
eTSEC0(mac) phy0 irq0 eTSEC0(mac) phy0
irq10
eTSEC1(mac) phy1 irq1 eTSEC1(mac) phy1
irq10
eTSEC2(mac) phy2 irq2 eTSEC2(mac) phy2
irq10
eTSEC3(mac) phy3 irq3 eTSEC3(mac) phy3
irq10
After Booting Linux the first Ethernet device is only eTSEC0 is working
means at booting time it detects all 4 ports and initialize all ports. The
following IP addresses are assigned to each port:
interfaceBoard IP Host IP
eth0 192.168.10.2 192.168.10.1
eth1 192.168.20.2 192.168.20.1
eth2 192.168.30.2 192.168.30.1
eth3 192.168.40.2 192.168.40.1
when i Tried to ping from board to host (ie ping 192.168.10.1) through eth0
its pinging. but when i tried to ping from other ports ie eth1, eth2 eth3
its not pinging and prints destination host not reachable. Also I tried
to ping from pc(ie host) to board same result was printing.
Then I started debugging, I put a printk function inside Gianfar.c file and
gfar_clean_rx_ring() for printing packet sequence and packet size. I
started pinging each port from pc (ie host) and its printing on each
reception as:
For eth0
[ 94.966113] Packet 1 size 60
[ 95.965588] Packet 2 size 120
[ 97.980729] Packet 3 size 180
[ 98.980705] Packet 4 size 240
[ 99.998872] Packet 5 size 300
and same for other interfaces too.
Here is the device tree snap-shot for ethernet which I am using with this
kernel (hope may be helpful):
enet0: ethernet@24000 {
#address-cells = 1;
#size-cells = 1;
cell-index = 0;
device_type = network;
model = TSEC;
compatible = gianfar;
reg = 0x24000 0x1000;
ranges = 0x0 0x24000 0x1000;
local-mac-address = [ 00 00 00 00 00 00 ];
interrupts = 29 2 30 2 34 2;
interrupt-parent = mpic;
tbi-handle = tbi0;
phy-handle = phy0;
phy-connection-type = rgmii-id;
mdio@520 {
#address-cells = 1;
#size-cells = 0;
compatible = fsl,gianfar-mdio;
reg = 0x520 0x20;
phy0: ethernet-phy@0 {
interrupt-parent = mpic;
interrupts = 0 1;
reg = 0;
device_type = ethernet-phy;
};
phy1: ethernet-phy@1 {
interrupt-parent = mpic;
interrupts = 1 1;
reg = 1;
device_type = ethernet-phy;
};
phy2: ethernet-phy@2 {
interrupt-parent = mpic;
interrupts = 2 1;
reg = 2;
device_type = ethernet-phy;
};
phy3: ethernet-phy@3 {
interrupt-parent = mpic;
interrupts = 3 1;
reg = 3;
device_type = ethernet-phy;
};
tbi0: tbi-phy@11 {
reg = 0x11;
device_type = tbi-phy;
};
};
};
enet1: ethernet@25000 {
#address-cells = 1;
#size-cells = 1;
cell-index = 1;
device_type = network;
model = TSEC;
compatible = gianfar;
reg = 0x25000 0x1000;
ranges = 0x0 0x25000 0x1000;
local-mac-address = [ 00 00 00 00 00 00 ];
interrupts = 35 2 36 2 40 2;
interrupt-parent = mpic;
Where is debug_mutex_wake_waiter used? And it waits for what, I am getting oops
While bringing up kernel on armv7 I am getting this error, Can anyone please help me. What could be the issue. t= Internal error: Oops: 5 [#1] PREEMPT SMP ARM t= Modules linked in: t= CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.14.0-11033-g3dee3bc-dirty #34 t= task: cf858400 ti: cf85a000 task.ti: cf85a000 t= PC is at debug_mutex_wake_waiter+0x3c/0x174 t= LR is at __mutex_unlock_slowpath+0xc4/0x188 t= pc : [c0050a74]lr : [c03810e4]psr: 0193 sp : cf85be00 ip : fp : t= r10: c0525c59 r9 : 413fc0f3 r8 : 0001 t= r7 : r6 : c05296ec r5 : c04ec014 r4 : t= r3 : r2 : 0002 r1 : r0 : c04ec000 t= Flags: nzcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel0 ip : fp : t= Control: 10c5387d Table: 4000406a DAC: 0015 t= Process swapper/0 (pid: 1, stack limit = 0xcf85a240) Segment kernel0 ip : fp : t= Stack: (0xcf85be00 to 0xcf85c000) t= be00: c04ec000 c04f4460 c03852cc c03810e4 cf8a7b40 t= be20: c010a9b8 000d c04e8ae0 cf8a79d8 c038ab40 t= be40: cf8a7b40 c010baf0 0001 cfde7c9c cf8a79d8 c010c3cc t= be60: 000d c038ab40 cfde7c9c 0001 0001 t= be80: c046d974 cfde7b68 cfde7c84 c046d974 cfde7b3c c010c580 c046d974 t= bea0: cfde7b3c c02d33d0 cfde7ba6 cf85bec4 cfde7b3c cfde7c84 c0525d80 t= bec0: c04bb500 c02d34b8 cfde7b3c c056133c c04de060 c04d480c cf85a000 t= bee0: c0008818 0012 c00563b4 c04d47a8 t= bf00: c05296f2 0012 cf88bb80 6113 c04f9960 c04f9960 t= bf20: c04f995c c04f995c c04de080 0001 c04de060 c0525d80 c04bb500 t= bf40: c04e8adc 0079 c037b508 c0432ad4 c04de080 0001 c04de060 t= bf60: c0525d80 c04bb500 c04e8ae0 0079 c04bbc6c 0001 0001 t= bf80: c04bb500 c003ccec c03798b8 t= bfa0: c03798c0 c000e438 t= bfc0: t= bfe0: 0013 t= [c0050a74] (debug_mutex_wake_waiter) from [c03810e4] (__mutex_unlock_slowpath+0xc4/0x188) t= [c03810e4] (__mutex_unlock_slowpath) from [c010a9b8] (kernfs_add_one+0xc0/0x134)c4/0x188) t= [c010a9b8] (kernfs_add_one) from [c010baf0] (__kernfs_create_file+0x80/0x9c)134)c4/0x188) t= [c010baf0] (__kernfs_create_file) from [c010c3cc] (sysfs_add_file_mode_ns+0xa0/0x160) t= [c010c3cc] (sysfs_add_file_mode_ns) from [c010c580] (sysfs_add_file+0x18/0x20) t= [c010c580] (sysfs_add_file) from [c02d33d0] (__of_add_property_sysfs+0x64/0xb8) t= [c02d33d0] (__of_add_property_sysfs) from [c02d34b8] (__of_node_add+0x94/0xe0) t= [c02d34b8] (__of_node_add) from [c04d480c] (of_init+0x64/0xd4) t= [c04d480c] (of_init) from [c0008818] (do_one_initcall+0x34/0x158) t= [c0008818] (do_one_initcall) from [c04bbc6c] (kernel_init_freeable+0x108/0x1dc) t= [c04bbc6c] (kernel_init_freeable) from [c03798c0] (kernel_init+0x8/0xe4)/0x1dc) t= [c03798c0] (kernel_init) from [c000e438] (ret_from_fork+0x14/0x3c) t= Code: e5953014 e2855014 e1530005 0a1d (e594300c) t= ---[ end trace 7c418b9a0bc03a79 ]---0001d (e594300c) ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Cannot use USB device after compiling new kernel.
I am using 3.14.0 kernel version. I compiled using localmodconfig. I am using Ubuntu in my Lenovo U410 Ultrabook. I can use USB mouse, keyboard, pendrives with the distro kernel 3.11.0-18-generic. I can use USB mouse in distro kernel, but cannot use the same in compiled kernel. I can plug in new pendrive in distro kernel and are automatically mounted. But i cannot mount pendrive in new kernel. The same occurs for USB keyboard. But i can mount Nexus 7 in both kernel. Here is the output of dmesg and lsusb. habisravi@U410:~$ dmesg tail [ 866.156540] audit: type=1400 audit(1397006611.192:33): apparmor=DENIED operation=capable profile=/usr/sbin/cupsd pid=1113 comm=cupsd capability=36 capname=block_suspend [ 869.326789] usb 3-2: new low-speed USB device number 13 using xhci_hcd [ 869.515935] usb 3-2: New USB device found, idVendor=1bcf, idProduct=0007 [ 869.515949] usb 3-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 869.515951] usb 3-2: Product: USB Optical Mouse [ 869.516121] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes habisravi@U410:~$ habisravi@U410:~$ lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 013: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 003 Device 003: ID 04f2:b2e1 Chicony Electronics Co., Ltd Bus 003 Device 004: ID 0cf3:3004 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub habisravi@U410:~$ ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Cannot use USB device after compiling new kernel.
2014-04-09 14:48 GMT+04:00, HABI S RAVI habi...@gmail.com: I am using 3.14.0 kernel version. I compiled using localmodconfig. I am using Ubuntu in my Lenovo U410 Ultrabook. I can use USB mouse, keyboard, pendrives with the distro kernel 3.11.0-18-generic. I can use USB mouse in distro kernel, but cannot use the same in compiled kernel. I can plug in new pendrive in distro kernel and are automatically mounted. But i cannot mount pendrive in new kernel. The same occurs for USB keyboard. But i can mount Nexus 7 in both kernel. Here is the output of dmesg and lsusb. habisravi@U410:~$ dmesg tail [ 866.156540] audit: type=1400 audit(1397006611.192:33): apparmor=DENIED operation=capable profile=/usr/sbin/cupsd pid=1113 comm=cupsd capability=36 capname=block_suspend [ 869.326789] usb 3-2: new low-speed USB device number 13 using xhci_hcd [ 869.515935] usb 3-2: New USB device found, idVendor=1bcf, idProduct=0007 [ 869.515949] usb 3-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 869.515951] usb 3-2: Product: USB Optical Mouse [ 869.516121] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes habisravi@U410:~$ habisravi@U410:~$ lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 013: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 003 Device 003: ID 04f2:b2e1 Chicony Electronics Co., Ltd Bus 003 Device 004: ID 0cf3:3004 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub habisravi@U410:~$ connect all your usb devices, reboot to the uduntu precompiled kernel, be sure that all modules are loaded and all devices are working properly, then again do localmodconfig and re-compile a new kernel. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: What is the benefit of running CONFIG_SMP on single core device?
Using SMP would let your system take advantage of HyperThreading. If you have a fairly decent CPU there is a good chance that your single core have support for HyperThreading which will improve parallelization. On Wed, Apr 9, 2014 at 1:05 PM, Mj Embd mj.e...@gmail.com wrote: -- -mj ___ 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: Cannot use USB device after compiling new kernel.
On Wed, Apr 9, 2014 at 1:10 PM, Ivan Riabtsov ivriabt...@gmail.com wrote: 2014-04-09 14:48 GMT+04:00, HABI S RAVI habi...@gmail.com: I am using 3.14.0 kernel version. I compiled using localmodconfig. I am using Ubuntu in my Lenovo U410 Ultrabook. I can use USB mouse, keyboard, pendrives with the distro kernel 3.11.0-18-generic. I can use USB mouse in distro kernel, but cannot use the same in compiled kernel. I can plug in new pendrive in distro kernel and are automatically mounted. But i cannot mount pendrive in new kernel. The same occurs for USB keyboard. But i can mount Nexus 7 in both kernel. Here is the output of dmesg and lsusb. habisravi@U410:~$ dmesg tail [ 866.156540] audit: type=1400 audit(1397006611.192:33): apparmor=DENIED operation=capable profile=/usr/sbin/cupsd pid=1113 comm=cupsd capability=36 capname=block_suspend [ 869.326789] usb 3-2: new low-speed USB device number 13 using xhci_hcd [ 869.515935] usb 3-2: New USB device found, idVendor=1bcf, idProduct=0007 [ 869.515949] usb 3-2: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [ 869.515951] usb 3-2: Product: USB Optical Mouse [ 869.516121] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes habisravi@U410:~$ habisravi@U410:~$ lsusb Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 013: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 003 Device 003: ID 04f2:b2e1 Chicony Electronics Co., Ltd Bus 003 Device 004: ID 0cf3:3004 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub habisravi@U410:~$ connect all your usb devices, reboot to the uduntu precompiled kernel, be sure that all modules are loaded and all devices are working properly, then again do localmodconfig and re-compile a new kernel. Or you can try to figure out which drivers you need by fallowing GKH's Linux kernel in a Nutshell. http://www.kroah.com/lkn/ I guess this is the old way before localmodconfig, but more fun ;-) Regards, Bojan ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: What is the benefit of running CONFIG_SMP on single core device?
I am running an ARM cpu and linux kernel during kernel init on SMP enabled (running with single core in DT) sends SGI to itself while SMP disabled does not. Am puzzled why it does that? AFAIK there is no hyper threading on ARM On Wed, Apr 9, 2014 at 4:51 PM, Kristofer Hallin kristofer.hal...@gmail.com wrote: Using SMP would let your system take advantage of HyperThreading. If you have a fairly decent CPU there is a good chance that your single core have support for HyperThreading which will improve parallelization. On Wed, Apr 9, 2014 at 1:05 PM, Mj Embd mj.e...@gmail.com wrote: -- -mj ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies -- -mj ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Kconfig set default macro bug?
Hi all, I'm just playing with the early printk macros of the low level printk. The address of the UART port is set to a default value [1]. So if you save the config and then enter again in menuconfig, you are not able to change the value to a different default value (I suppose because Kconfig see the value as set), but there is no way to find out what the values for other UART ports would be. E.g. you have accidentally selected the wrong port. The only solution is, to disable the low level debugging functions, save the config and open it with menuconfig again. I'm not quite sure if this is the most convenient way of doing this. At least the default address should be readable from the config to change the value by hand. Does anyone know if we can consider this to be a bug? Cheers, Matthias [1] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/Kconfig.debug?id=refs/tags/v3.14#n1007 -- motzblog.wordpress.com ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
