June 2004 - openSUSE AMD64 - openSUSE Mailing Lists

suse 2.6.5-7.75 kernel compilation issues?
by Peter Buckingham 22 Jun '04

22 Jun '04

Hi, I have been playing with the latest kernel and there seem to be some compilation issues with it. firstly the prototype for follow_hugetlb_page() is wrong (line 17 include/linux/hugetlb.h), it seems to be a simple matter of adding an int at the end of the argument list. this then uncovers an issue with the usage of follow_hugetlb_page at line 753 of mm/memory.c, I just added a 0 for the final write argument to make it compile. I'd be interested in knowing whether that's right thing to do, and/or some explanation of this function ;-) I can generate a patch if it's useful, but this seems kinda trivial... thanks, peter

1 0

system hangs on 244
by Chiu, PCM (Peter) 22 Jun '04

22 Jun '04

We have been experiencing some intermittent but quite critical problems on a cluster of 10 dual 244 with 1GB memory boxes running Suse prof 9.0. The problem occurs on all 10 nodes, ranges between 4 - 10 days. When the system hangs, no response to ping, or any input at the console. The only way out is to hit the reset button. We have checked the cpu temperature but that have settled down to between 25 - 48 C across different nodes. We have also transferred our application to run on RAM drives and that has helped to keep the system to 16 - 22 days. Does anyone has any idea on how to analyse this problem? Thanks. Peter

1 0

AGP question
by rkimber＠ntlworld.com 22 Jun '04

22 Jun '04

Where in sax2 or yast2 do I set the AGP, or does X automatically detect and set the maximum AGP setting? I cannot find any reference in the logs to an AGP setting. How can I tell what the setting is? I have an FX 5200 on a K8T Master series board that has an 8x/4x AGP Pro slot. -- Richard Kimber http://www.psr.keele.ac.uk/

5 7

Scilab on Suse 9.0 AMD64
by Bernard Uguen 22 Jun '04

22 Jun '04

Hello, I am a scilab user. I have difficulty to run or build a scilab application. Is there somebody on the list who succeed to run scilab on suse9.0 (64 BIT) ? My config is : Linux 2.4.21-102-default x86_x64 I will appreciate suggestion to know how to compile in 32 bit with the good library. Thank you for your help Bernard

1 0

VMWare and kernel mis-match
by Creamer, Mark 22 Jun '04

22 Jun '04

Hi folks, I'm new to Linux, but I'm picking things up pretty quickly. This one has me stumped though. I did a fresh-out-of-the-box install of 9.1 on my new AMD 64-based system. I then installed kernel-source, gcc, make and I think one or two other required components, as needed by VMWare GSX installer. I run the script to configure VMWare, and see this: ****************************************** " Trying to find a suitable vmmon module for your running kernel. None of VMware Workstation's pre-built vmmon modules is suitable for your running kernel. Do you want this program to try to build the vmmon module for your system (you need to have a C compiler installed on your system)? [yes] Using compiler "/usr/bin/gcc". Use environment variable CC to override. What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] The path "/usr/src/linux/include" is not an existing directory. What is the location of the directory of C header files that match your running kernel? [/usr/src/linux/include] ****************************************** I don't have this default path, but I have similar, /usr/src/linux-______/include (where _____ is my version number - I don't have that in front of me). So I key in that path, and it says... The directory of kernel headers [snip] does not match your running kernel [snip]. I sort-of understand what it's trying to tell me, but both the running kernel and the kernel-source were installed at the same time, and from the same 9.1 media - no online updates have occurred that would make them out of sync. I've read a lot about this issue on various postings, but so far none of the suggestions have worked for me. If you have any ideas, I'd really appreciate it. Specs: AMD64, 2GB RAM, SuSE 9.1, VMWare GSX Server for Linux, Evaluation edition Mark Creamer

4 5

Re: [suse-amd64] oops in current->journal-info in ext3 and reiserfs
by adelphia user 22 Jun '04

22 Jun '04

Hi Andi, I am trying to use the following macro to detect stack overflow in some of the functions which showed a high value in the objdump command you mentioned, But somehow i am not able to hit the condition yet, i wonder if this macro is somehow broken. #define thread_check_stack() { \ register unsigned long _sp_; \ register unsigned long _ebp_; \ unsigned long address; \ struct task_struct *p = current; \ __asm__("movq %%rsp, %0" : "=r" (_sp_)); \ __asm__("movq %%rbp, %0" : "=r" (_ebp_)); \ address = (unsigned long )p->journal_info ; \ if ( _sp_ <= address ) { \ printk(KERN_ALERT "!!!! %s:%d : stack shoots in to task struct here sp: %016lx jinfo %016lx!!\n", \ __FILE__, __LINE__, _sp_, address );\ drop_to_debugger(); \ }\ if ( address ) { \ if ( address < PAGE_SIZE ) { \ printk(KERN_ALERT "!!!! %s:%d : Journal Info appears to be corrupted here\n", \ __FILE__, __LINE__ );\ printk(" at virtual address %016lx\n",address);\ drop_to_debugger(); \ }\ }\ address = (unsigned long )p->fs ; \ if ( address < PAGE_SIZE ) { \ printk(KERN_ALERT "!!!! %s:%d : task->fs appears to be here\n", \ __FILE__, __LINE__ );\ printk(" at virtual address %016lx\n",address);\ drop_to_debugger(); \ }\ if (in_interrupt()) { \ printk(KERN_ERR "!!!! %s:%d : In interrupt \n", \ __FILE__, __LINE__ );\ if( ((_sp_ & ~(PAGE_MASK << 1)) - sizeof(struct task_struct)) < 256) { \ printk(KERN_ERR "!!!! %s:%d : total intr stack size exceeded: %lu\n", \ __FILE__, __LINE__, \ ((_sp_ & ~(PAGE_MASK << 1)) - sizeof(struct task_struct))); \ drop_to_debugger(); \ } \ } \ else { \ if( ((_sp_ & ~(PAGE_MASK << 1)) - sizeof(struct task_struct)) < 1200) { \ printk(KERN_ERR "!!!! %s:%d : total stack size exceeded: %lu\n", \ __FILE__, __LINE__, \ ((_sp_ & ~(PAGE_MASK << 1)) - sizeof(struct task_struct))); \ drop_to_debugger(); \ } \ } \ if( (_ebp_ > _sp_) && \ ((_ebp_ - _sp_) > 400) ) { \ printk(KERN_ERR "!!!! %s:%d : total stack size exceeded: %lu\n", \ __FILE__, __LINE__, \ } \ } Thanks in advance for any help, Satya >From: Andi Kleen <ak(a)suse.de> >To: "adelphia user" <sendtoadelphia(a)hotmail.com> >CC: suse-amd64(a)suse.com >Subject: Re: [suse-amd64] oops in current->journal-info in ext3 and >reiserfs >Date: Mon, 21 Jun 2004 17:24:56 +0200 > >On Mon, 21 Jun 2004 18:33:31 +0530 >"adelphia user" <sendtoadelphia(a)hotmail.com> wrote: > > > Yes we use our own filesystem module. Apart from this i also see oops >due to > > invalid address etc. I suspect our module is overwriting in to the >stack, > > probably causing corruption. Is there a way to increase the stack size? >I > >Nope, you have to fix your module. In 2.6 kernels (like in 9.1) there is >~2k >more stack, but even with that it it's better to fix it. > >One way to start is to do objdump -S module.o | egrep '>:|sub.*sp' >and fix any function that uses more than ~200bytes stack frame. > >Usually you can do that by using kmalloc() to allocate space for a >big stack variable. > > >-Andi > >-- >Check the List-Unsubscribe header to unsubscribe >For additional commands, email: suse-amd64-help(a)suse.com > _________________________________________________________________ Pay Cash on delivery on lakhs of products. http://go.msnserver.com/IN/50757.asp Only on Baazee.com

2 1

Re: [suse-amd64] oops in current->journal-info in ext3 and reiserfs
by adelphia user 21 Jun '04

21 Jun '04

Hi, Yes we use our own filesystem module. Apart from this i also see oops due to invalid address etc. I suspect our module is overwriting in to the stack, probably causing corruption. Is there a way to increase the stack size? I am pasting one of those stack below. This is the first time our module is getting ported on AMD64. The kernel used is 2.4.21-143-numa. opteron# lsmod Module Size Used by Tainted: P panfs 6260392 2 (autoclean) nfsd 92752 4 (autoclean) ide-cd 36616 0 (autoclean) cdrom 34664 0 (autoclean) [ide-cd] ipv6 284856 -1 (autoclean) key 78248 0 (autoclean) [ipv6] joydev 7136 0 (unused) evdev 6496 0 (unused) input 7488 0 [joydev evdev] usb-ohci 23728 0 (unused) usbcore 87488 1 [usb-ohci] bcm5700 93232 1 lvm-mod 81152 0 (autoclean) reiserfs 248088 1 <1>Unable to handle kernel paging request at virtual address 000000ffd1e7f664 printing rip: ffffffff801c686d PML4 0 Oops: 0002 CPU 1 Pid: 8015, comm: detect_corrupti Tainted: PF RIP: 0010:[<ffffffff801c686d>]{kdbm_memmap+205} RSP: 0018:0000010011e43a88 EFLAGS: 00010292 RAX: fffffffff000eef3 RBX: 0000000000000000 RCX: ffffffff8047e5e0 RDX: 0000000000000001 RSI: 0000000000000000 RDI: 0000010011e43b20 RBP: 0000010000000058 R08: f000f8599f400175 R09: f000eef39f40008e R10: f000ff53f000ef57 R11: f000e987f000fea5 R12: 000000000007fff0 R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffffffff804e8280(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 000000ffd1e7f664 CR3: 000000007f902000 CR4: 00000000000006e0 Process detect_corrupti (pid: 8015, stackpage=10011e43000) Stack: 0000010011e43a88 0000000000000018 ffffffff801c6819 0000000000000007 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000000000000000 0000010000000000 0000000000000000 f000eef300000001 Call Trace: [<ffffffff801c6819>]{kdbm_memmap+121} [<ffffffff801c21f8>]{kdb_parse+504} [<ffffffff801c4929>]{kdb_read+9} [<ffffffff801c496b>]{kdb_getstr+59} [<ffffffff801c26bc>]{kdb_local+876} [<ffffffff80125a85>]{release_console_sem+165} [<ffffffff801258cb>]{vprintk+331} [<ffffffff8012597d>]{printk+141} [<ffffffff801c283a>]{kdb_main_loop+186} [<ffffffff802d8090>]{kdba_main_loop+128} [<ffffffff801c2f95>]{kdb+1509} [<ffffffff80111621>]{die+241} [<ffffffff801c7895>]{do_page_fault+1237} [<ffffffff801109a2>]{error_exit+0} [<ffffffff8012966a>]{do_exit+154} [<ffffffff801299c3>]{sys_exit+19} [<ffffffff801102a3>]{tracesys_call+10} Code: ff 44 84 10 eb 04 ff 44 24 30 8b 44 24 0c ff c0 48 83 bc 24 kdb: Debugger re-entered on cpu 1, new reason = 5 Attempting to abort command and recover [1]kdb> Thanks, Satya >From: Andi Kleen <ak(a)suse.de> >To: adelphia user <sendtoadelphia(a)hotmail.com> >CC: suse-amd64(a)suse.com >Subject: Re: [suse-amd64] oops in current->journal-info in ext3 and >reiserfs >Date: Mon, 21 Jun 2004 12:54:25 +0200 > >On Mon, Jun 21, 2004 at 09:07:40AM +0530, adelphia user wrote: > > Hello , > > > > I am seeing oopses in ext3 and also in reiserfs because of invalid > > current->journal_info. I am facing this problem in kernel > > 2.4.21-143-numa. This is on suse 8.1 amd64. > >This is very likely a kernel stack overflow. > >Do you use any special kernel modules? Please send your lsmod output. > >-Andi > > >-- >Check the List-Unsubscribe header to unsubscribe >For additional commands, email: suse-amd64-help(a)suse.com > _________________________________________________________________ Apply to 50,000 jobs now. http://go.msnserver.com/IN/50740.asp Post your CV on naukri.com today.

2 1

kernel conflict after update
by rkimber＠ntlworld.com 21 Jun '04

21 Jun '04

As a new user, I seem to have got into a difficult situation which has not been all of my making. I used YOU to update a package. I selected the option for making manual selections and selected the package. YOU then installed virtually all of the packages in the list including a kernel update. After that I rebooted to be on the safe side. I now find that when I try to install any software I get a conflict resolution warning saying that kernel-smp requires irqbalance but says that irqbalance is not available - even though the package is on the 'current' website. What should I do? I'm surprised I'm not given the option of installing it. I tried downloading the rpm and pointing yast to the hard disk, but search doesn't seem to find it. -- Richard Kimber http://www.psr.keele.ac.uk/

2 4

oops in current->journal-info in ext3 and reiserfs
by adelphia user 21 Jun '04

21 Jun '04

Hello , I am seeing oopses in ext3 and also in reiserfs because of invalid current->journal_info. I am facing this problem in kernel 2.4.21-143-numa. This is on suse 8.1 amd64. Oops IS WITH IN ext3. The test i am using creates files in ext3 and our filesystem, which is network based, and comparing results in both, and tripping on this oops from time to time. Our filesystem does not modify the journal_info in any way. Is there any workaround for this ? or a possible patch ? Any help is muchly appreciated > Error (regular_file): read_system_map stat /boot/System.map-2.4.21-143-numa >failed Jun 17 14:48:11 porting-10 kernel: Unable to handle kernel NULL >pointer dereference at virtual address 00000000000002ae Jun 17 14:48:11 >porting-10 kernel: ffffffffa0000616 Jun 17 14:48:11 porting-10 kernel: PML4 >1d4d5067 PGD 0 Jun 17 14:48:11 porting-10 kernel: Oops: 0000 Jun 17 >14:48:11 porting-10 kernel: CPU 0 Jun 17 14:48:11 porting-10 kernel: Pid: >15951, comm: detect_corrupti Tainted: P Jun 17 14:48:11 porting-10 kernel: >RIP: 0010:[<ffffffffa0000616>]{:jbd:journal_start_Rsmp_2c291b1f+54} Using >defaults from ksymoops -t elf64-x86-64 -a i386:x86-64 Jun 17 14:48:11 >porting-10 kernel: RSP: 0018:000001001c643e58 EFLAGS: 00010202 Jun 17 >14:48:11 porting-10 kernel: RAX: ffffffffffffffe2 RBX: 00000000000002ae >RCX: 000001002475ae40 Jun 17 14:48:11 porting-10 kernel: RDX: >0000000000000000 RSI: 0000000000000003 RDI: 000001003fd21e00 Jun 17 >14:48:11 porting-10 kernel: RBP: 000001003fd21e00 R08: 00000000000003e8 >R09: 000000000001e660 Jun 17 14:48:11 porting-10 kernel: R10: >0000000040621ef0 R11: 0000000000000202 R12: 000001001c643ee8 Jun 17 >14:48:11 porting-10 kernel: R13: 0000000000000048 R14: 0000000000000000 >R15: 0000000040606340 Jun 17 14:48:11 porting-10 kernel: FS: >0000000000000000(0000) GS:ffffffff804bd740(0000) knlGS:0000000000000000 Jun >17 14:48:11 porting-10 kernel: CS: 0010 DS: 0000 ES: 0000 CR0: >000000008005003b Jun 17 14:48:11 porting-10 kernel: CR2: 00000000000002ae >CR3: 0000000000101000 CR4: 00000000000006e0 Jun 17 14:48:11 porting-10 >kernel: Process detect_corrupti (pid: 15951, stackpage=1001c643000) Jun 17 >14:48:11 porting-10 kernel: Stack: 000001001c643e58 0000000000000018 >000001001c643ee8 0000010013ce6b40 Jun 17 14:48:11 porting-10 kernel: >0000000000000000 0000010013ce6b40 ffffffffa0018366 000001003c1a7b80 Jun 17 >14:48:11 porting-10 kernel: 000001001c643ee8 0000010013ce6b40 >0000010013ce6b40 0000000000000048 Jun 17 14:48:11 porting-10 kernel: Call >Trace: [<ffffffffa0018366>]{:ext3:ext3_setattr+566} Jun 17 14:48:11 >porting-10 kernel: [<ffffffff801746d7>]{notify_change+135} >[<ffffffff80152d15>]{do_truncate+165} Jun 17 14:48:11 porting-10 kernel: >[<ffffffff801530c3>]{sys_ftruncate+259} >[<ffffffff80110093>]{system_call+119} Jun 17 14:48:11 porting-10 kernel: >Code: 48 8b 03 48 39 38 74 34 49 c7 c0 c0 a6 00 a0 b9 fa 00 00 00 > > > >>RIP; ffffffffa0000616 <[jbd]journal_start+36/f0> <===== > > >>RAX; ffffffffffffffe2 <END_OF_CODE+5f88f2c3/????> >>RCX; >000001002475ae40 Before first symbol >>RDI; 000001003fd21e00 Before first >symbol >>RBP; 000001003fd21e00 Before first symbol >>R09; 000000000001e660 >Before first symbol >>R10; 0000000040621ef0 Before first symbol >>R12; >000001001c643ee8 Before first symbol >>R15; 0000000040606340 Before first >symbol > >Trace; ffffffffa0018366 <[ext3]ext3_setattr+236/420> Trace; >ffffffff801746d7 <notify_change+87/360> Trace; ffffffff801530c3 ><sys_ftruncate+103/130> > >Code; ffffffffa0000616 <[jbd]journal_start+36/f0> 0000000000000000 <_RIP>: >Code; ffffffffa0000616 <[jbd]journal_start+36/f0> <===== Code; >ffffffffa0000616 <[jbd]journal_start+36/f0> 0000000000000000 <_RIP>: Code; >ffffffffa0000616 <[jbd]journal_start+36/f0> <===== 0: 48 8b 03 > mov (%rbx),%rax <===== Code; ffffffffa0000619 ><[jbd]journal_start+39/f0> 3: 48 39 38 cmp >%rdi,(%rax) Code; ffffffffa000061c <[jbd]journal_start+3c/f0> 6: 74 >34 je 3c <_RIP+0x3c> ffffffffa0000652 ><[jbd]journal_start+72/f0> Code; ffffffffa000061e ><[jbd]journal_start+3e/f0> 8: 49 c7 c0 c0 a6 00 a0 mov >$0xffffffffa000a6c0,%r8 Code; ffffffffa0000625 <[jbd]journal_start+45/f0> > f: b9 fa 00 00 00 mov $0xfa,%ecx > > >1 warning and 1 error issued. Results may not be reliable. > Thanks, Satya _________________________________________________________________ Pay Cash on delivery on lakhs of products. http://go.msnserver.com/IN/50757.asp Only on Baazee.com

3 2

xon with SuSE9.1
by Yoriaki FUJIMORI 21 Jun '04

21 Jun '04

Dear list, I am testing SuSE9.1 on an AMD64 box. I noticed that SuSE9.1 X server does not permit X output from other servers/workstations listed in /etc/hosts.equiv, although I invoked `xhost +server1 server2' etc in advance. It seems that I have to modify /etc/services to enable x11 tcp/udp, and /etc/X11/xinit/xserverrc to listen tcp. I do not know if these are all. I wonder how we can enable xon as with SuSE9.0 without much hustles. yoriaki fujimori

2 2