kernel crashes inside MV643xx driver
Hi All, After I started the NFS server, it crashed: <3>Badness in local_bh_enable at /home/cli4/sandbox/main/TelicaRoot/components/mvlinux/cge/devkit/lsp/7xx/linux/kernel/softirq.c:195 Badness in local_bh_enable at /home/cli4/sandbox/main/TelicaRoot/components/mvlinux/cge/devkit/lsp/7xx/linux/kernel/softirq.c:195 Call trace: [c0005340] check_bug_trap+0xbc/0x11c [c0005604] ProgramCheckException+0x264/0x2bc [c0004ac4] ret_from_except_full+0x0/0x4c [c0022ae4] local_bh_enable+0x18/0x80 [c024648c] skb_copy_bits+0x168/0x3b8 [c024db44] __skb_linearize+0x90/0x150 [c020e8a4] mv643xx_eth_start_xmit+0x4c0/0x5bc [c025c934] qdisc_restart+0xac/0x2bc [c024de9c] dev_queue_xmit+0x298/0x34c [c0269814] ip_finish_output+0x140/0x2b8 [c026a3ac] ip_fragment+0x3cc/0x6e0 [c026bac8] ip_push_pending_frames+0x3dc/0x46c [c0289ec4] udp_push_pending_frames+0x10c/0x1cc [c028a7c4] udp_sendpage+0x104/0x188 [c0292fc8] inet_sendpage+0x90/0xb8 I searched the webs and found the similar problems: http://www.mail-archive.com/[EMAIL PROTECTED]/msg05199.html http://oss.sgi.com/archives/netdev/2005-09/msg00025.html Who knew there are fixes for the problem? Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
NFS client show nothing for "ls" command.
Hi All, Recently, I got a funny problem that my NFS client can't show some of mounted directories. These directories that can't be showed by "ls" command have great deals of files. For example. I have a directory on NFS server log and there are 69 files. I can't show it's child files through NFS. ---On NFS server--- bash-2.05b# ls 1 13 17 20 24 28 31 35 39 42 46 5 53 57 60 64 68 9 10 14 18 21 25 29 32 36 4 43 47 50 54 58 61 65 69 11 15 19 22 26 3 33 37 40 44 48 51 55 59 62 66 7 12 16 2 23 27 30 34 38 41 45 49 52 56 6 63 67 8 ---On NFS client--- # ls # After I delete one file from NFS server side, everything becomes OK. ---On NFS server--- bash-2.05b# rm 69 bash-2.05b# ls 1 13 17 20 24 28 31 35 39 42 46 5 53 57 60 64 68 10 14 18 21 25 29 32 36 4 43 47 50 54 58 61 65 7 11 15 19 22 26 3 33 37 40 44 48 51 55 59 62 66 8 12 16 2 23 27 30 34 38 41 45 49 52 56 6 63 67 9 ---On NFS client--- # ls 1 13 17 20 24 28 31 35 39 42 46 5 53 57 60 64 68 10 14 18 21 25 29 32 36 4 43 47 50 54 58 61 65 7 11 15 19 22 26 3 33 37 40 44 48 51 55 59 62 66 8 12 16 2 23 27 30 34 38 41 45 49 52 56 6 63 67 9 # I also scrapped the packets through ethereal and saw that packet sent at case 1) isn't valid. It only has 3 fileds: ., .. and last. I suppose the problem came from NFS server side because we can't received valid NFS packet for such directories with plenty of files. Anybody knew what's the root cause? Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: do_coredump and O_NOFOLLOW
Bernd Eckenfels wrote: In article <[EMAIL PROTECTED]> you wrote: I found that O_NOFOLLOW is used for opened core file in Linux 2.6.10. I think that is for security reasons, otherwise one has to (atomically) check who is the owner of the symlink and where it points to. If you dont have hostile users on your system you might be able to remove it, but it is not a good idea in the general public. Maybe we need a coreadm tool like Solaris has, where you can put the corefiles where you want. That would change the corepattern to include a path and be specific to a process (tree). Gruss Bernd - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ Bernd, Thanks for your reply. I don't think there are any hostile users on the system. So it's relatively of security. I didn't hear of coreadm tool before, Linux will become more powerful with coreadm. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
do_coredump and O_NOFOLLOW
Hi All, I found that O_NOFOLLOW is used for opened core file in Linux 2.6.10. This means the core file couldn't be a symbolic link. However, I want to use symbolic link for core file, So I plan to remove O_NOFOLLOW as follows, but I'm not sure there are any impacts introduced by the change? file = filp_open(corename, O_CREAT | 2 | O_NOFOLLOW | O_LARGEFILE, 0600); TO file = filp_open(corename, O_CREAT | 2 /*| O_NOFOLLOW*/ | O_LARGEFILE, 0600); Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
How to include sysmap in 2.6 kernel image
Hey Guys, Recently, I'm working on xmon. The xmon needs sysmap for symbol lookup, however I don't know how to include sysmap to uImage. I looked the kernel source code for a while and found the kernel image need contain struct bi_record *rec. Everybody knows how to include this? arch/ppc/kernel/setup.c::parse_bootinfo() void parse_bootinfo(struct bi_record *rec) { if (rec == NULL || rec->tag != BI_FIRST) return; while (rec->tag != BI_LAST) { ulong *data = rec->data; printk(KERN_INFO "%s:*** 0x%08lx\n", __FUNCTION__, rec->tag); switch (rec->tag) { case BI_CMD_LINE: strlcpy(cmd_line, (void *)data, sizeof(cmd_line)); break; case BI_SYSMAP: sysmap = (char *)((data[0] >= (KERNELBASE)) ? data[0] : (data[0]+KERNELBASE)); sysmap_size = data[1]; break; #ifdef CONFIG_BLK_DEV_INITRD case BI_INITRD: initrd_start = data[0] + KERNELBASE; initrd_end = data[0] + data[1] + KERNELBASE; break; #endif /* CONFIG_BLK_DEV_INITRD */ #ifdef CONFIG_PPC_MULTIPLATFORM case BI_MACHTYPE: _machine = data[0]; break; #endif case BI_MEMSIZE: boot_mem_size = data[0]; break; } rec = (struct bi_record *)((ulong)rec + rec->size); } } Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
about XMON of 2.6 Linux kernel
Hi All, I have 2 questions on XMON of 2.6 kernel. Any answers are appreciated! 1) Any engineer is still developing for XMON and who is the maintainer? 2) When I issued command "ls", XMON told me there are no sysmap or sysmap_size. Do you know how to include the sysmap? mon> ls : No sysmap or sysmap_size Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Big sized packets have been dropped strangly
Hey Guys, I got a strange problem recently but no ideas, so to post the question here. We have a FPGA what finish ATM AAL5 to ethernet frame, and CPU receives IP packets from it. The interface based on the FPGA (called sar0) has been bound with several IP addresses. When the MTU of the interface is configurated to 1500, trivial packets can be received, but big-sized packets are dropped. If the MTU is increased to 9500, everything is ok except the NFS connection. We mounted with another machine through sar0. When the MTU is 9500, the speed of the NFS becomes very very slow (it almost took 10 minutes to transfer 100KB files). I don't know why it is and how to solve it. Any suggestions are appreciated! Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6 Linux for PowerPC supports kdb?
Randy Dunlap wrote: On Tue, 26 Jun 2007 23:03:55 -0400 Shan, Guo Wen (Gavin) wrote: Does anybody knew if 2.6 linux for PowerPC supports kdb? PowerPC isn't listed AFAICT: ftp://oss.sgi.com/www/projects/kdb/download/v4.4/README I.e., all that I see are i386, x86_64, and ia64. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** Thanks, Randy. So the kgdb is the only tool I could use to debug the kernel right now? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: bugs in __schedule()
Satyam Sharma wrote: On 6/26/07, gshan <[EMAIL PROTECTED]> wrote: I mean kernel thread could sleep, but tasklet can't. If so, it meet my requirements. That's not really a justification to convert a tasklet to a kernel thread. I suspect the simplest solution to your problem would be to simply replace that semaphore with a spinlock. Other than that, we can't really help without looking at code. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ Thank you very much, Satyam. Anyway, I will do experiments. Thank you again :-) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: bugs in __schedule()
Satyam Sharma wrote: On 6/26/07, gshan <[EMAIL PROTECTED]> wrote: Thanks, Satyam. So I can replace the tasklet with kernel thread? That depends on what you want to do ... [ BTW: I should correct a typo in my original reply -- I should've said "scheduling while atomic", and not "scheduling while interrupts disabled" because interrupts are _not_ disabled in bottom halves, and from your stack backtrace it was evident that a tasklet was executing. :-) ] I mean kernel thread could sleep, but tasklet can't. If so, it meet my requirements. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: bugs in __schedule()
Satyam Sharma wrote: Hi Gavin, On 6/26/07, gshan <[EMAIL PROTECTED]> wrote: Here is the all output I have: # ifconfig mgt0 10.0.51.27 BUG: scheduling while atomic: exe/0x0101/752 Yup, you can't sleep in taskets, they're atomic. caller is schedule+0x4c/0xe4 Call trace: [c02dc4dc] __schedule+0x654/0x788 [c02dc6f4] schedule+0x4c/0xe4 [c02dbe24] __compat_down+0xc8/0x12c So, you can't use / acquire semaphores in them. Use spinlocks. If the shared data is also accessed from process context, use spin_lock_bh() from the process context code. Satyam Thanks, Satyam. So I can replace the tasklet with kernel thread? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: bugs in __schedule()
Here is the all output I have: # ifconfig mgt0 10.0.51.27 BUG: scheduling while atomic: exe/0x0101/752 caller is schedule+0x4c/0xe4 Call trace: [c02dc4dc] __schedule+0x654/0x788 [c02dc6f4] schedule+0x4c/0xe4 [c02dbe24] __compat_down+0xc8/0x12c [c0226b60] mv_sw_read_reg+0x178/0x17c [c02296fc] mvSwIntrTasklet+0x128/0x744 [c0020afc] tasklet_action+0x7c/0xec [c00204f4] ___do_softirq+0x80/0x11c [c00205cc] __do_softirq+0x3c/0x6c [c00206a4] do_softirq+0x60/0x68 [c00207a8] irq_exit+0x6c/0x94 [c0005e1c] do_IRQ+0x88/0xa4 [c0004b70] ret_from_except+0x0/0x18 [c000680c] __delay+0xc/0x14 [c0226598] mv_sw_read_smi_reg+0x84/0x1ac [c0226adc] mv_sw_read_reg+0xf4/0x17c Satyam Sharma wrote: Hi Gavin, On 6/26/07, gshan <[EMAIL PROTECTED]> wrote: Anybody has suggestions on this crash? [c02dc4dc] __schedule+0x654/0x788 [c02dc6f4] schedule+0x4c/0xe4 [c02dbe24] __compat_down+0xc8/0x12c [c0226b60] mv_sw_read_reg+0x178/0x17c [c02296fc] mvSwIntrTasklet+0x128/0x744 [c0020afc] tasklet_action+0x7c/0xec [c00204f4] ___do_softirq+0x80/0x11c [c00205cc] __do_softirq+0x3c/0x6c [c00206a4] do_softirq+0x60/0x68 [c00207a8] irq_exit+0x6c/0x94 [c0005e1c] do_IRQ+0x88/0xa4 [c0004b70] ret_from_except+0x0/0x18 [c000680c] __delay+0xc/0x14 [c0226598] mv_sw_read_smi_reg+0x84/0x1ac I bet you got more output than that, didn't you? :-) Now I know this must be a "scheduling while interrupts disabled", but why not post the whole error message? [ Reminds me of the other thread where someone thought just mentioning the EIP without any backtrace / other messages was enough to resolve a boot-time panic. I agree they're all magicians on this list, but Gods they're not ... ] BTW I don't see "mvSwIntrTasklet" anywhere on -rc6. Is this a -mm kernel? Cheers, Satyam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: bugs in __schedule()
The code is written by myself. 2 questions: 1) tasklet couldn't sleep? 2) It is because the tasklet take a semaphore? Thanks, Gavin Alexey Dobriyan wrote: On 6/26/07, gshan <[EMAIL PROTECTED]> wrote: Anybody has suggestions on this crash? talk to whoever supplied the following into your kernel: [c02dc4dc] __schedule+0x654/0x788 [c02dc6f4] schedule+0x4c/0xe4 [c02dbe24] __compat_down+0xc8/0x12c [c0226b60] mv_sw_read_reg+0x178/0x17c this [c02296fc] mvSwIntrTasklet+0x128/0x744 and this. [c0020afc] tasklet_action+0x7c/0xec [c00204f4] ___do_softirq+0x80/0x11c [c00205cc] __do_softirq+0x3c/0x6c [c00206a4] do_softirq+0x60/0x68 [c00207a8] irq_exit+0x6c/0x94 [c0005e1c] do_IRQ+0x88/0xa4 [c0004b70] ret_from_except+0x0/0x18 [c000680c] __delay+0xc/0x14 [c0226598] mv_sw_read_smi_reg+0x84/0x1ac - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
bugs in __schedule()
Anybody has suggestions on this crash? [c02dc4dc] __schedule+0x654/0x788 [c02dc6f4] schedule+0x4c/0xe4 [c02dbe24] __compat_down+0xc8/0x12c [c0226b60] mv_sw_read_reg+0x178/0x17c [c02296fc] mvSwIntrTasklet+0x128/0x744 [c0020afc] tasklet_action+0x7c/0xec [c00204f4] ___do_softirq+0x80/0x11c [c00205cc] __do_softirq+0x3c/0x6c [c00206a4] do_softirq+0x60/0x68 [c00207a8] irq_exit+0x6c/0x94 [c0005e1c] do_IRQ+0x88/0xa4 [c0004b70] ret_from_except+0x0/0x18 [c000680c] __delay+0xc/0x14 [c0226598] mv_sw_read_smi_reg+0x84/0x1ac Thanks, Gavin [c0226adc] mv_sw_read_reg+0xf4/0x17c - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Problems with mounting flash partition with jffs2
Hey Guys, Today, I got a strange problems. When I tried to mount a the last 2 flash partitions, following errors happened. Any ideas are appreciated. # cat /proc/mtd dev:size erasesize name mtd0: 0010 0001 "boot" mtd1: 0020 0001 "ro" mtd2: 0010 0001 "diag-var-log" mtd3: 0010 0001 "mlba" mtd4: 0010 0001 "rw" mtd5: 0020 0001 "sarsu" mtd6: 00c0 0001 "backup" mtd7: 00c0 0001 "kdi" # mknod /dev/mtd.boot b 31 0 # mknod /dev/mtd.ro b 31 1 # mknod /dev/mtd.diag-var-log b 31 2 # mknod /dev/mtd.mlba b 31 3 # mknod /dev/mtd.rw b 31 4 # mknod /dev/mtd.sarsu b 31 5 # mknod /dev/mtd.backup b 31 6 # mknod /dev/mtd.kdi b 31 7 # # mount -t jffs2 /dev/mtd.boot /mnt # umount /mnt # mount -t jffs2 /dev/mtd.ro /mnt Inode #3 was a directory with children - removing those too... <<< Error here # mount -t jffs2 /dev/mtd.diag-var-log /mnt # umount /mnt # mount -t jffs2 /dev/mtd.mlba /mnt Inode #4 was a directory with children - removing those too... <<< Error here # mount -t jffs2 /dev/mtd.rw /mnt # umount /mnt # mount -t jffs2 /dev/mtd.sarsu /mnt # umount /mnt # mount -t jffs2 /dev/mtd.backup /mnt jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0044: 0x5599 instead <<< Error here jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0048: 0x0c00 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00400010: 0x0c80 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00400018: 0x0c80 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0040001c: 0x2020 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00400020: 0x0c80 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00400024: 0x80e4 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00400028: 0x0c00 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00400030: 0x0c00 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00400038: 0x0c00 instead Further such events for this erase block will not be printed Empty flash at 0x004065e4 ends at 0x004065e8 Empty flash at 0x00406670 ends at 0x00406674 Empty flash at 0x00406684 ends at 0x00406688 Empty flash at 0x00406818 ends at 0x0040681c Empty flash at 0x00406854 ends at 0x00406858 Empty flash at 0x00406868 ends at 0x0040686c Empty flash at 0x0040687c ends at 0x00406880 Empty flash at 0x004068a4 ends at 0x004068a8 Empty flash at 0x004069a8 ends at 0x004069ac : : jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005502d8: 0x0200 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0055071c: 0x0400 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00550720: 0x8e00 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00550748: 0x8200 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00550770: 0xa200 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00550794: 0x0100 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00550798: 0x8200 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005507c0: 0x8200 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005507e8: 0xa200 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00550810: 0x8200 instead Further such events for this erase block will not be printed jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0056: 0x2000 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00560004: 0x0021 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0056000c: 0x0028 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00560010: 0x2101 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00560018: 0x6001 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0056001c: 0x0202 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00560020: 0x0002 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00560024: 0x1112 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00560028: 0x8080 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0056002c: 0x0802 instead Further such events for this erase block will not be printed Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes empty_blocks 169, bad_blocks 0, c->nr_blocks 192 mount: mounting /dev/mtd.backup on /mnt failed # # # # mount -t jffs2 /dev/mtd.kdi /mnt jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0044: 0x5599 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0048: 0x0c00 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00400010: 0x0c80 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0
Is kdb package available for 2.6 Linux on PowerPC?
Hey Guys, Recently, I need work on my TTY (console) driver so that it could support kdb. I didn't have much experiences on linux kdb. So my questions are: 1) 2.6 Linux for PowerPC could support kdb? where can I find the source code? 2) If 2.6 Linux for PowerPC doesn't support kdb, where could I get the package and integrated it to kernel? Thanks in advance, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Questions on one PowerPC assembly instruction from hash_page
Mikael Pettersson wrote: On Mon, 18 Jun 2007 16:33:22 +0800, gshan <[EMAIL PROTECTED]> wrote: I can't understand the following instructions from arch/ppc/mm/hashtable.S::hash_page. If I got the right design, the following instruction is to get the PMD (Page Middle Descritor) because Linux for 32-bits PowerPC cut page table into 3 domains: root, PMD, PTE. The top bits (22 to 31 bit) is the index for PMD, and the next 10 bits (12 to 21 bit) is the index for PTE in the associative PMD. The remaining 12 bits (0 to 11 bit) indicated the page size (4KB). However, the following instruction polled [8-17] bits instead of [22-31] bits as expected. Anybody could give me answer? r4 is the address that caused the DSI r5 is the address of swapper_pg_dir if we are under kernel mode. rlwimi r5,r4,12,20,29 /* insert top 10 bits of address */ POWER/PowerPC has an insanely broken bit numbering scheme, in which the most significant bit has number 0 (or is it 1?), and the least significant bit has number N-1 (or is it N?) where N is number of bits in a word. The fact that you refer to the top bits as 22-31 makes me suspect that you haven't compensated for this quirk. /Mikael Mikael, Thanks a lot. I understood why the instruction is there. So the 0-11 bits are used as address index for PMD. swapper_pg_dir is 4KB large and there are 1K PMDs inside swapper_pg_dir. So 10 bits (0-9 bits) are used as index for PMD, right? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Questions on one PowerPC assembly instruction from hash_page
Hey Guys, I can't understand the following instructions from arch/ppc/mm/hashtable.S::hash_page. If I got the right design, the following instruction is to get the PMD (Page Middle Descritor) because Linux for 32-bits PowerPC cut page table into 3 domains: root, PMD, PTE. The top bits (22 to 31 bit) is the index for PMD, and the next 10 bits (12 to 21 bit) is the index for PTE in the associative PMD. The remaining 12 bits (0 to 11 bit) indicated the page size (4KB). However, the following instruction polled [8-17] bits instead of [22-31] bits as expected. Anybody could give me answer? r4 is the address that caused the DSI r5 is the address of swapper_pg_dir if we are under kernel mode. rlwimi r5,r4,12,20,29 /* insert top 10 bits of address */ Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to access kdb explicitly
Jiri Kosina wrote: On Fri, 1 Jun 2007, gshan wrote: I want to access kdb explicitly. For example, I could recognize the special characters inside console driver. If the the special characters are detected , then drop to kdb immediately. However, I don't know what should I to do after the special characters received. See http://www.ibm.com/developerworks/linux/library/l-kdbug/ - section "Activating KDB". Thanks a lot :-) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
How to access kdb explicitly
All, I want to access kdb explicitly. For example, I could recognize the special characters inside console driver. If the the special characters are detected , then drop to kdb immediately. However, I don't know what should I to do after the special characters received. Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Change IP TOS inside ethernet driver
I want to change the IP TOS inside ioctl callback of ethernet driver, but don't know how to do this. Anybody has ideas? Thanks in advance, Gavin. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
kernel crash in timer interrupt handler
The kernel crashed inside timer handler. Anyone has ideas? The Linux I'm using is 2.6.19. Thanks in advance! BUG: soft lockup detected on CPU#0! Call Trace: [C0395EA0] [C000C308] show_stack+0x58/0x180 (unreliable) [C0395ED0] [C0043A18] softlockup_tick+0xac/0xc8 [C0395EF0] [C00223C4] run_local_timers+0x18/0x28 [C0395F00] [C0022414] update_process_times+0x40/0x7c [C0395F10] [C0005800] timer_interrupt+0x70/0x208 [C0395F40] [C0004874] ret_from_except+0x0/0x14 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: How to produce a core
Willy Tarreau wrote: On Thu, May 24, 2007 at 11:28:15AM +0800, gshan wrote: This morning, I tried command "kill -7 [pid]" but didn't see the core file. Anybody has ideas? do the following before starting your program : # ulimit -c unlimited You can check before and after that the core size changed from 0 to "unlimited" : # ulimit -a Willy Willy, Thank you very much. The command "kill -7 [pid]" really works with "ulimit -c unlimited" # /bin/sh # ps PID USER COMMAND 1 0init 2 0[ksoftirqd/0] 3 0[desched/0] 4 0[events/0] 5 0[khelper] 10 0[kthread] 31 0[kblockd/0] 60 0[pdflush] 61 0[pdflush] 63 0[aio/0] 62 0[kswapd0] 64 0[jfsIO] 65 0[jfsCommit] 66 0[jfsSync] 67 0[xfslogd/0] 68 0[xfsdatad/0] 69 0[xfsbufd] 706 0[mtdblockd] 730 0-sh 788 0/bin/sh 789 0ps # ulimit -c unlimited # kill -7 788 Bus error (core dumped) # ls -al drwxr-xr-x 12 00 0 Jan 1 00:55 . drwxr-xr-x 12 00 0 Jan 1 00:55 .. drwxr-xr-x2 1000 10000 Jan 1 00:00 bin -rw---1 00 417792 Jan 1 00:55 core <<< Here is the corefile drwxr-xr-x2 00 0 Jan 1 00:00 dev drwxr-xr-x3 00 0 Jan 1 00:00 etc lrwxrwxrwx1 00 12 Jan 1 00:00 init -> /bin/busybox drwxr-xr-x2 00 0 Jan 1 00:00 lib drwxr-xr-x2 00 0 Jan 1 00:00 misc dr-xr-xr-x 32 00 0 Jan 1 00:00 proc drwx--2 00 0 Jan 1 00:00 root drwxr-xr-x2 00 0 Jan 1 00:00 sbin drwxr-xr-x2 00 0 Jan 1 00:00 sys drwxr-xr-x4 00 0 Jan 1 00:00 usr # Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
How to produce a core
This morning, I tried command "kill -7 [pid]" but didn't see the core file. Anybody has ideas? bash-2.05b# ps PID USER COMMAND 1 0init 2 0[ksoftirqd/0] 3 0[watchdog/0] 4 0[events/0] 5 0[khelper] 6 0[kthread] 36 0[kblockd/0] 38 0[kseriod] 50 0[pdflush] 51 0[pdflush] 52 0[kswapd0] 53 0[aio/0] 171 0-sh 174 0[rpciod/0] 182 0bash 198 0gdi_trans 16777471 0 0 12 1 0 1 8000 0 0 0 1 1 204 0ps bash-2.05b# kill -7 198 bash-2.05b# ps PID USER COMMAND 1 0init 2 0[ksoftirqd/0] 3 0[watchdog/0] 4 0[events/0] 5 0[khelper] 6 0[kthread] 36 0[kblockd/0] 38 0[kseriod] 50 0[pdflush] 51 0[pdflush] 52 0[kswapd0] 53 0[aio/0] 171 0-sh 174 0[rpciod/0] 182 0bash 205 0ps [1]+ Bus error gdi_trans 16777471 0 0 12 1 0 1 8000 0 0 0 1 1 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
It's a bug of printk?
Hi, I need 2 consoles for 2 individual serial ports that is registered by register_console(). The console for the 1st serial port is registered at first. I can see the output from the serial port #1 before the console for the 2nd serial port is registered. However, I saw duplicated output from serial port #1 again after the console for #2 serial port is registered. The root cause is that there is only one con_start for all consoles. I think con_start need to be merged with struct console so that different console could have different start? Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Questions on printk and console_drivers
Hi Folks, I got a questions on printk and console_drivers. I have 2 serial ports and want to see output from all of them. So I registered 2 console driver using register_console. I can see the output from serial port 1 after it was registered, but can't see any output from it after serial port 2 has been registered. I don't why. Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: PROBLEM: kernel 2.6.20.6 build failed for ppc board chestnut(ibm ppc 750GX/FX)
I'm using eldk4, there are no problems. Wang, Baojun wrote: PROBLEM: linux kernel 2.6.20.6 build failed for ppc board chestnut(ibm ppc 750GX/FX) STEPS I followed: 1) make ARCH=ppc CROSS_COMPILE=ppc_4xx- chestnut_defconfig # toolchain from eldk 4.1 2) make ARCH=ppc CROSS_COMPILE=ppc_4xx- V=1 ... make -f scripts/Makefile.build obj=arch/ppc/platforms ppc_4xx-gcc -m32 -Wp,-MD,arch/ppc/platforms/.chestnut.o.d -nostdinc -isystem /opt/eldk/usr/bin/../lib/gcc/powerpc-linux/4.0.0/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Iarch/ppc -Iarch/ppc/include -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -O2 -Iarch/ppc -msoft-float -pipe -ffixed-r2 -mmultiple -mno-altivec -mstring -Wa,-maltivec -fomit-frame-pointer -Wdeclaration-after-statement -Wno-pointer-sign-D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(chestnut)" -D"KBUILD_MODNAME=KBUILD_STR(chestnut)" -c -o arch/ppc/platforms/chestnut.o arch/ppc/platforms/chestnut.c arch/ppc/platforms/chestnut.c: In function 'chestnut_setup_mtd': arch/ppc/platforms/chestnut.c:435: error: 'physmap_map' undeclared (first use in this function) arch/ppc/platforms/chestnut.c:435: error: (Each undeclared identifier is reported only once arch/ppc/platforms/chestnut.c:435: error: for each function it appears in.) make[1]: *** [arch/ppc/platforms/chestnut.o] Error 1 make: *** [arch/ppc/platforms] Error 2 This PROBLEM should also affect these boards: find -name '*.[chS]' -exec grep physmap_map {} \; -print physmap_map.size = CHESTNUT_32BIT_SIZE; ./arch/ppc/platforms/chestnut.c physmap_map.size = size; ./arch/ppc/platforms/ev64360.c physmap_map.size = size; ./arch/ppc/platforms/katana.c I've veryfied 2.6.15, 2.6.19.2 2.6.20.1 2.6.20.6 ONLY 2.6.15 can build successfully. sounds like the problem is caused by the interface change of mtd. this brute force patch sould solve the problem: diff -Nru /tmp/linux-2.6.20.6/arch/ppc/platforms/chestnut.c \ linux-2.6.20.6/arch/ppc/platforms/chestnut.c --- /tmp/linux-2.6.20.6/arch/ppc/platforms/chestnut.c 2007-04-07 04:02:48.0 +0800 +++ linux-2.6.20.6/arch/ppc/platforms/chestnut.c2007-04-13 17:09:03.0 +0800 @@ -432,7 +432,9 @@ ptbl.name = "User FS"; ptbl.size = CHESTNUT_32BIT_SIZE; - physmap_map.size = CHESTNUT_32BIT_SIZE; + // physmap_map.size = CHESTNUT_32BIT_SIZE; + physmap_configure(CHESTNUT_32BIT_BASE, CHESTNUT_32BIT_SIZE, CONFIG_MTD_PHYSMAP_BANKWIDTH, NULL); + physmap_set_partitions(&ptbl, 1); return 0; } - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Unable to mount root fs on unknown-block(1,0)
Sorry, the version of linux should be 2.6.15 for MPC8xx, which is included in ELDK. gshan wrote: Hi Folks, I got problem to boot linux 2.6.25 using u-boot-1.1.4, any ideas? - U-Boot 1.1.4 (Apr 14 2007 - 00:57:01) CPU: XPC850xxZTB at 50 MHz: 2 kB I-Cache 1 kB D-Cache Board: ### No HW ID - assuming TQM8xxL DRAM: 8 MB FLASH: 4 MB In:serial Out: serial Err: serial Net: SCC ETHERNET Hit any key to stop autoboot: 0 Using SCC ETHERNET device TFTP from server 90.0.0.1; our IP address is 90.0.0.2 Filename 'uImage'. Load address: 0x10 Loading: # # done Bytes transferred = 825541 (c98c5 hex) => printenv bootdelay=5 baudrate=9600 loads_echo=1 ethact=SCC ETHERNET netmask=0xff00 vlan=0x nvlan=0x clocks_in_mhz=1 bootcmd=tftp 0x10 uImage autostart=no filesize=c98c5 fileaddr=10 ipaddr=90.0.0.2 serverip=90.0.0.1 bootargs=root=/dev/ram rw stdin=serial stdout=serial stderr=serial Environment size: 293/16380 bytes => bdinfo memstart= 0x memsize = 0x0080 flashstart = 0x1000 flashsize = 0x0040 flashoffset = 0x00021000 sramstart = 0x sramsize= 0x0080 immr_base = 0xFFF0 bootflags = 0x0001 intfreq = 50 MHz busfreq = 50 MHz ethaddr = 00:00:00:00:00:00 IP addr = 90.0.0.2 baudrate= 9600 bps => tftp 0x20 aaa Using SCC ETHERNET device TFTP from server 90.0.0.1; our IP address is 90.0.0.2 Filename 'aaa'. Load address: 0x20 Loading: # done Bytes transferred = 776 (308 hex) => bootm 0x10 0x20 ## Booting image at 0010 ... Image Name: Linux-2.6.15 Created: 2007-04-15 16:56:44 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:825477 Bytes = 806.1 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 0020 ... Image Name: ramdisk Created: 2007-04-15 17:31:31 UTC Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:712 Bytes = 0.7 kB Load Address: Entry Point: Verifying Checksum ... OK Loading Ramdisk to 007b8000, end 007b82c8 ... OK Linux version 2.6.15 ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.0 4.0.0)) #182 Mon Apr 16 00:56:43 CST 2007 Built 1 zonelists Kernel command line: root=/dev/ram rw PID hash table entries: 64 (order: 6, 1024 bytes) 50 Decrementer Frequency = 18750/60 Console: colour dummy device 80x25 Dentry cache hash table entries: 2048 (order: 1, 8192 bytes) Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) Memory: 6236k available (1408k kernel code, 364k data, 84k init, 0k highmem) Mount-cache hash table entries: 512 checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 0k freed NET: Registered protocol family 16 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Generic RTC Driver v1.07 Serial: CPM driver $Revision: 0.01 $ ttyCPM0 at MMIO 0xfff00a80 (irq = 20) is a CPM UART RAMDISK driver initialized: 2 RAM disks of 1024K size 1024 blocksize loop: loaded (max 8 devices) eth0: CPM ENET Version 0.2 on SCC1, 00:00:00:00:00:00 NET: Registered protocol family 2 IP route cache hash table entries: 128 (order: -3, 512 bytes) TCP established hash table entries: 512 (order: -1, 2048 bytes) TCP bind hash table entries: 512 (order: -1, 2048 bytes) TCP: Hash tables configured (established 512 bind 512) TCP reno registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: Compressed image found at block 0 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) <0>Rebooting in 180 seconds.. Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Unable to mount root fs on unknown-block(1,0)
Hi Folks, I got problem to boot linux 2.6.25 using u-boot-1.1.4, any ideas? - U-Boot 1.1.4 (Apr 14 2007 - 00:57:01) CPU: XPC850xxZTB at 50 MHz: 2 kB I-Cache 1 kB D-Cache Board: ### No HW ID - assuming TQM8xxL DRAM: 8 MB FLASH: 4 MB In:serial Out: serial Err: serial Net: SCC ETHERNET Hit any key to stop autoboot: 0 Using SCC ETHERNET device TFTP from server 90.0.0.1; our IP address is 90.0.0.2 Filename 'uImage'. Load address: 0x10 Loading: # # done Bytes transferred = 825541 (c98c5 hex) => printenv bootdelay=5 baudrate=9600 loads_echo=1 ethact=SCC ETHERNET netmask=0xff00 vlan=0x nvlan=0x clocks_in_mhz=1 bootcmd=tftp 0x10 uImage autostart=no filesize=c98c5 fileaddr=10 ipaddr=90.0.0.2 serverip=90.0.0.1 bootargs=root=/dev/ram rw stdin=serial stdout=serial stderr=serial Environment size: 293/16380 bytes => bdinfo memstart= 0x memsize = 0x0080 flashstart = 0x1000 flashsize = 0x0040 flashoffset = 0x00021000 sramstart = 0x sramsize= 0x0080 immr_base = 0xFFF0 bootflags = 0x0001 intfreq = 50 MHz busfreq = 50 MHz ethaddr = 00:00:00:00:00:00 IP addr = 90.0.0.2 baudrate= 9600 bps => tftp 0x20 aaa Using SCC ETHERNET device TFTP from server 90.0.0.1; our IP address is 90.0.0.2 Filename 'aaa'. Load address: 0x20 Loading: # done Bytes transferred = 776 (308 hex) => bootm 0x10 0x20 ## Booting image at 0010 ... Image Name: Linux-2.6.15 Created: 2007-04-15 16:56:44 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:825477 Bytes = 806.1 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK ## Loading RAMDisk Image at 0020 ... Image Name: ramdisk Created: 2007-04-15 17:31:31 UTC Image Type: PowerPC Linux RAMDisk Image (gzip compressed) Data Size:712 Bytes = 0.7 kB Load Address: Entry Point: Verifying Checksum ... OK Loading Ramdisk to 007b8000, end 007b82c8 ... OK Linux version 2.6.15 ([EMAIL PROTECTED]) (gcc version 4.0.0 (DENX ELDK 4.0 4.0.0)) #182 Mon Apr 16 00:56:43 CST 2007 Built 1 zonelists Kernel command line: root=/dev/ram rw PID hash table entries: 64 (order: 6, 1024 bytes) 50 Decrementer Frequency = 18750/60 Console: colour dummy device 80x25 Dentry cache hash table entries: 2048 (order: 1, 8192 bytes) Inode-cache hash table entries: 1024 (order: 0, 4096 bytes) Memory: 6236k available (1408k kernel code, 364k data, 84k init, 0k highmem) Mount-cache hash table entries: 512 checking if image is initramfs...it isn't (no cpio magic); looks like an initrd Freeing initrd memory: 0k freed NET: Registered protocol family 16 io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered Generic RTC Driver v1.07 Serial: CPM driver $Revision: 0.01 $ ttyCPM0 at MMIO 0xfff00a80 (irq = 20) is a CPM UART RAMDISK driver initialized: 2 RAM disks of 1024K size 1024 blocksize loop: loaded (max 8 devices) eth0: CPM ENET Version 0.2 on SCC1, 00:00:00:00:00:00 NET: Registered protocol family 2 IP route cache hash table entries: 128 (order: -3, 512 bytes) TCP established hash table entries: 512 (order: -1, 2048 bytes) TCP bind hash table entries: 512 (order: -1, 2048 bytes) TCP: Hash tables configured (established 512 bind 512) TCP reno registered TCP bic registered NET: Registered protocol family 1 NET: Registered protocol family 17 RAMDISK: Compressed image found at block 0 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) <0>Rebooting in 180 seconds.. Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
help me on 2.6.15 kernel on MPC850
Hey Guys, The CPU was spinning when executing in head_8xx.S::initial_mmu. I have located the instruction that cause the spinning through on-board leds. Do you have any ideas? #ifdef CONFIG_8xx_COPYBACK mtspr SPRN_DC_CST, r8 <<< The spinning was caused by this instruction #endif #else /* * For a debug option, I left this here to easily enable * the write through cache mode */ lis r8, [EMAIL PROTECTED] mtspr SPRN_DC_CST, r8 lis r8, [EMAIL PROTECTED] mtspr SPRN_DC_CST, r8 #endif blr - The output from u-boot: => tftp 0x10 uImage Using SCC ETHERNET device TFTP from server 90.0.0.3; our IP address is 90.0.0.50 Filename 'uImage'. Load address: 0x10 Loading: # # ### done Bytes transferred = 844738 (ce3c2 hex) => bootm ## Booting image at 0010 ... Image Name: Linux-2.6.15 Created: 2007-04-07 17:25:29 UTC Image Type: PowerPC Linux Kernel Image (gzip compressed) Data Size:844674 Bytes = 824.9 kB Load Address: Entry Point: Verifying Checksum ... OK Uncompressing Kernel Image ... OK <<< The CPU is spinning then - The hardware, bootloader, linux I'm using: 1) MPC850, 1KB DCache + 2KB ICache 2) u-boot 1.1.4 ( Data Cache is turned off all the way, but instruction cache is always on) 3) ppclinux 2.6.15 Thanks, Gavin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/