April 2005 - openSUSE AMD64 - openSUSE Mailing Lists

radiusd
by Riccardo Ghiglianovich 06 Apr '05

06 Apr '05

hi all, I am using Suse Enterprise 9.0 amd64; I am trying to use freeradius as radius daemon. I can install it from the CDs but it doesnt work. at start, it says Failed to link to module 'rlm_exec': rlm_exec.a: cannot open shared object file: No such file or directory I discovered that rlm_exec.la looks for rlm_exec.a and it DOES EXIST and it is in the right place: /usr/lib/freeradius mhh... the radiusd is ELF64 but the lib is 32... may be this the issue? I dont know, ... Is there here someone that has freeradius up and running?? thanks, Ric

1 0

Kernel Bug? (SuSE Linux 9.1 Prof. AMD64, kernel 2.6.5-7.151-smp)
by Alexander Karakas 06 Apr '05

06 Apr '05

Hello, I got the following stack trace in the log on an AMD64-File-Server running SAMBA shares on (LVM2-Volumegroup with ReiserFS v3.6 partitions) with quotas turned on. The dump occured during a the copying of files from a SuSE Linux 9.1 Prof. client (smbclient) to a SAMBA share. During this operation the user exceeded his quota. ########################################################## Apr 6 10:01:30 kingarthur kernel: Kernel BUG at dquot:310 Apr 6 10:01:30 kingarthur kernel: invalid operand: 0000 [1] SMP Apr 6 10:01:30 kingarthur kernel: CPU 0 Apr 6 10:01:30 kingarthur kernel: Pid: 25508, comm: quotaoff Not tainted (2.6.5-7.151-smp SLES9_SP1_BRANCH-200503181131210000) Apr 6 10:01:30 kingarthur kernel: RIP: 0010:[vfs_quota_off+341/704] <ffffffff801be5c5>{vfs_quota_off+341} Apr 6 10:01:30 kingarthur kernel: RIP: 0010:[<ffffffff801be5c5>] <ffffffff801be5c5>{vfs_quota_off+341} Apr 6 10:01:30 kingarthur kernel: RSP: 0018:000001004ded9ca8 EFLAGS: 00010202 Apr 6 10:01:30 kingarthur kernel: RAX: 0000000000000001 RBX: 000001003e2bf690 RCX: 000001003e2bf490 Apr 6 10:01:30 kingarthur kernel: RDX: ffffffff803d89d0 RSI: 000001003e2bf980 RDI: 000001007fd86700 Apr 6 10:01:30 kingarthur kernel: RBP: 00000100037b1c00 R08: 0000000000000000 R09: 000001004ded9c28 Apr 6 10:01:30 kingarthur kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 000001004ded9cc8 Apr 6 10:01:30 kingarthur kernel: R13: 00000100037b1d28 R14: 00000100037b1d28 R15: 0000000000000000 Apr 6 10:01:30 kingarthur kernel: FS: 0000002a9588d6e0(0000) GS:ffffffff80554200(0000) knlGS:00000000557be2a0 Apr 6 10:01:30 kingarthur kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Apr 6 10:01:30 kingarthur kernel: CR2: 0000002a9556b000 CR3: 0000000000101000 CR4: 00000000000006e0 Apr 6 10:01:30 kingarthur kernel: Process quotaoff (pid: 25508, threadinfo 000001004ded8000, task 00000100104b40c0) Apr 6 10:01:30 kingarthur kernel: Stack: 0000000100000001 00000100037b1d30 00000100037b1d70 0000000000000010 Apr 6 10:01:30 kingarthur kernel: 000001004ded9cc8 000001004ded9cc8 0000000000000000 0000000080000300 Apr 6 10:01:30 kingarthur kernel: 000001007ad5fc00 0000000000000000 Apr 6 10:01:30 kingarthur kernel: Call Trace:<ffffffff801bfeb9>{sys_quotactl+1385} <ffffffff8019a8e1>{do_lookup+49} Apr 6 10:01:30 kingarthur kernel: <ffffffff8013cd00>{autoremove_wake_function+0} <ffffffff8019aad7>{permission+55} Apr 6 10:01:30 kingarthur kernel: <ffffffff8019bf2c>{may_open+108} <ffffffff8016b410>{file_ra_state_init+32} Apr 6 10:01:30 kingarthur kernel: <ffffffff80187f86>{dentry_open_it+310} <ffffffff80188131>{filp_open+113} Apr 6 10:01:30 kingarthur kernel: <ffffffff801a5ce1>{dput+33} <ffffffff8018be2e>{__fput+270} Apr 6 10:01:30 kingarthur kernel: <ffffffff80187aae>{filp_close+126} <ffffffff80187bb5>{sys_close+229} Apr 6 10:01:30 kingarthur kernel: <ffffffff801106d4>{system_call+124} Apr 6 10:01:30 kingarthur kernel: Apr 6 10:01:30 kingarthur kernel: Code: 0f 0b 73 5c 38 80 ff ff ff ff 36 01 48 8b 56 08 48 8b 06 48 Apr 6 10:01:30 kingarthur kernel: RIP <ffffffff801be5c5>{vfs_quota_off+341} RSP <000001004ded9ca8> ########################################################## The system didn't crash completely but the access to all the partitions of the volumegroup wasn't possible anymore. As an workaround quota support has been disabled and all is running quite well again. There was an kernel update made (with YOU) on March, 18th 2005, but he problem occured just today. Maybe, somebody has a hint, how to get quota support up and running again? Thanks, Alexander Karakas akarak(a)gmx.de

1 0

sound server
by Roy F. cabaniss 05 Apr '05

05 Apr '05

on a amd-64 an odd error. I keep getting the following message sound server fatal error cpu overload whilst the performance ceases and the system locks up. any others having this problem? After a few minutes the system is again usable. using an asus k8v motherboard with the onboard sound. Roy Cabaniss

3 2

9.2 64Bit + 3w SATA-RAID = very slow with high load??
by Hugo 05 Apr '05

05 Apr '05

Hi! Problem: very slow disk access + very high load during disk access. System: Dual Opteron, SuSE professional 9.2 64-bit, default SMP-kernel 2.6.8-24.11, SATA-RAID from 3ware with 3w-9xxx driver version v2.26.02.001 (From SuSE 9.2), RAID is the only "disk" in system and we have LVM on top of it (so we can change the sizes of the partitions later on.) Example1: currently one java process reading data from file. Java get's 85-100% CPU time and load is at 6-7.5. Nothing else. Example2: yesterday, I copied data from another server (Dual Opteron SuSE 9.0) over NFS mount with cp -command. Load was at 2.5-3 and at the top of top listing I had nfsd processes with 1-2% CPU load each. Data transfer rate was only 2.2Mb/s and the servers were connected with Gigabit lan! Example3: From old RH server the file transfers resulted in high loads (4-7) during rsync copying - so it's not the "other" servers fault. What's wrong? And what can I do about it? -- Hugo.

1 0

How to tell if the list is dead
by Brad Bourn 04 Apr '05

04 Apr '05

Like others, I posted to the list asking if it was me or the list. No response (of course, because the list was dead), so I thought about it for a little. If instead of posting to the list to test it. I figured out that all you have to do is go to the archives at lists.suse.com and check to see what the latest non-spam email is for the list in question, and if you don't see anything newer (lots newer, like days, because of slight lag) aside from spam, I'd think it pretty safe to assume it is the list itself. If suse can't post to its own archive.... heheheh thought I'd put this out here as I'm now seeing so many messages like mine asking if the list is down. B-)

1 0

RE: [suse-amd64] need help with megaraid driver, suse 9.2
by James D. Parra 04 Apr '05

04 Apr '05

> > Can't figure out why the megaraid module won't load for the LSI Logic > > MegaRAID 150-6 card. The LSI site has a driver for Suse 9.1, but not for > > Suse 9.2. Has anyone else had difficulty with this? > From dmesg I get the following; > I2O Core - (C) Copyright 1999 Red Hat Software >I don't know the SATA Megaraid controller but I very much doubt it is >related to I2O at all. At least there is no mention of I2O anywhere in the >/usr/src/linux-2.6.8-24.13/drivers/scsi/megaraid/ directory. >Please post the related portion of "lspci", as well as the dmesg >output after "modprobe megaraid" and the "lsmod | grep mega" output >afterwards. Also be sure to check the CONFIG_MEGARAID parameters in >/proc/config.gz, like, >CONFIG_MEGARAID_NEWGEN=y >CONFIG_MEGARAID_MM=m >CONFIG_MEGARAID_MAILBOX=m Thank you for your response. With modprobe I get; # modprobe megaraid FATAL: Module megaraid not found. ...and lspci shows; # lspci 0000:00:09.0 I2O: LSI Logic / Symbios Logic MegaRAID (rev 01) ...while dmesg shows; dmesg |grep I2O I2O Core - (C) Copyright 1999 Red Hat Software i2o: Checking for PCI I2O controllers... i2o: I2O controller found on bus 0 at 72. i2o: PCI I2O controller at E8800000 size=4194304 iop0: Activating I2O controller... I2O controller: probe of 0000:00:09.0 failed with error -110 I2O configuration manager v 0.04. I2O Block Storage OSM v0.9 I don't see a "megaraid.ko" file. Are the ".ko" extensions for modules not used on Suse 9.2? The directory contents of ../megaraid/ are; -rw-r--r-- 1 root root 2753 Mar 18 03:31 Kconfig.megaraid -rw-r--r-- 1 root root 93 Mar 18 03:31 Makefile -rw-r--r-- 1 root root 21173 Mar 18 03:31 mbox_defs.h -rw-r--r-- 1 root root 9454 Mar 18 03:31 mega_common.h -rw-r--r-- 1 root root 8312 Mar 18 03:31 megaraid_ioctl.h -rw-r--r-- 1 root root 94385 Mar 18 03:32 megaraid_mbox.c -rw-r--r-- 1 root root 9071 Mar 18 03:32 megaraid_mbox.h -rw-r--r-- 1 root root 24679 Mar 18 03:31 megaraid_mm.c -rw-r--r-- 1 root root 2141 Mar 18 03:31 megaraid_mm.h Is anything missing? Thank you again. James

1 0

RE: [suse-amd64] need help with megaraid driver, suse 9.2
by James D. Parra 04 Apr '05

04 Apr '05

> > Can't figure out why the megaraid module won't load for the LSI Logic > > MegaRAID 150-6 card. The LSI site has a driver for Suse 9.1, but not for > > Suse 9.2. Has anyone else had difficulty with this? > From dmesg I get the following; > I2O Core - (C) Copyright 1999 Red Hat Software >I don't know the SATA Megaraid controller but I very much doubt it is >related to I2O at all. At least there is no mention of I2O anywhere in the >/usr/src/linux-2.6.8-24.13/drivers/scsi/megaraid/ directory. >Please post the related portion of "lspci", as well as the dmesg >output after "modprobe megaraid" and the "lsmod | grep mega" output >afterwards. Also be sure to check the CONFIG_MEGARAID parameters in >/proc/config.gz, like, >CONFIG_MEGARAID_NEWGEN=y >CONFIG_MEGARAID_MM=m >CONFIG_MEGARAID_MAILBOX=m Thank you for your response. With modprobe I get; # modprobe megaraid FATAL: Module megaraid not found. ...and lspci shows; # lspci 0000:00:09.0 I2O: LSI Logic / Symbios Logic MegaRAID (rev 01) ...while dmesg shows; dmesg |grep I2O I2O Core - (C) Copyright 1999 Red Hat Software i2o: Checking for PCI I2O controllers... i2o: I2O controller found on bus 0 at 72. i2o: PCI I2O controller at E8800000 size=4194304 iop0: Activating I2O controller... I2O controller: probe of 0000:00:09.0 failed with error -110 I2O configuration manager v 0.04. I2O Block Storage OSM v0.9 I don't see a "megaraid.ko" file. Are the ".ko" extensions for modules not used on Suse 9.2? The directory contents of ../megaraid/ are; -rw-r--r-- 1 root root 2753 Mar 18 03:31 Kconfig.megaraid -rw-r--r-- 1 root root 93 Mar 18 03:31 Makefile -rw-r--r-- 1 root root 21173 Mar 18 03:31 mbox_defs.h -rw-r--r-- 1 root root 9454 Mar 18 03:31 mega_common.h -rw-r--r-- 1 root root 8312 Mar 18 03:31 megaraid_ioctl.h -rw-r--r-- 1 root root 94385 Mar 18 03:32 megaraid_mbox.c -rw-r--r-- 1 root root 9071 Mar 18 03:32 megaraid_mbox.h -rw-r--r-- 1 root root 24679 Mar 18 03:31 megaraid_mm.c -rw-r--r-- 1 root root 2141 Mar 18 03:31 megaraid_mm.h Is anything missing? Thank you again. James

1 0

RE: [suse-amd64] Weird Firefox behavior after YAST update on 9.2/64
by jerry bookter 04 Apr '05

04 Apr '05

--- Phil Betts <Phil.Betts(a)heis.co.uk> wrote: > > I daresay you've figured this out yourself by now, > but it won't hurt > having this in the archives... > > The solution (for me at least) was to exit ALL > firefox sessions (check > using ps) then restart. > Yep, it was okay on the next login. Good idea to have it archived here. :)

1 0

evolution AMD64
by William Westfall 04 Apr '05

04 Apr '05

Does anyone know of a link to the latest evolution RPM for SuSE 9.2 AMD64? -- wgwestfall1(a)privatemail.me.uk Made with:________________________________ Thunderbird 1.0.2 (20050317) Linux 2.6.8-24.13 AMD64 GNU/Linux (SuSE 9.2) -- wgwestfall1(a)privatemail.me.uk Made with:________________________________ Thunderbird 1.0.2 (20050317) Linux 2.6.8-24.13 AMD64 GNU/Linux (SuSE 9.2)

1 0

RE: [suse-amd64] need help with megaraid driver, suse 9.2
by James D. Parra 04 Apr '05

04 Apr '05

> Can't figure out why the megaraid module won't load for the LSI Logic > MegaRAID 150-6 card. The LSI site has a driver for Suse 9.1, but not for > Suse 9.2. Has anyone else had difficulty with this? My 9.2 has the drivers already: nathan:/usr/src/linux # find . -type f| xargs grep -i 150-6 ./drivers/pci/pci.ids: 1000 0523 MegaRAID SATA 150-6 RAID Controller ./drivers/scsi/megaraid/Kconfig.megaraid: LSI MegaRAID SATA 150-6 1000:1960:1000:0523 ./drivers/scsi/megaraid/megaraid_mbox.c: * LSI MegaRAID SATA 150-6 10001960 1000 0523 I'd recheck the PCI IDs. "won't load" is a too blurry error message to be helpful. What _exactly_ happens? -> /var/log/messages / dmesg. ~ Thank you for your response. This was noticed during a fresh install of 9.2. Went to Yast to discover that, although the card was detected under Disk Controllers, the "Module to use" was i20_pci with "Module parameters" of abdef. Oddly, why isn't the megaraid module being used? Tried to install the megaraid module by typing it in the "Module to use" section, but that doesn't work. Attempting to insmod megaraid from the source directory didn't work either. >From dmesg I get the following; I2O Core - (C) Copyright 1999 Red Hat Software i2o: max_drivers=4 i2o: Checking for PCI I2O controllers... ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 21 (level, low) -> IRQ 169 i2o: I2O controller found on bus 0 at 72. i2o: PCI I2O controller at E8800000 size=4194304 i2o: using write combining MTRR iop0: Installed at IRQ 169 iop0: Activating I2O controller... iop0: This may take a few minutes if there are many devices iop0: Get status timeout. Unable to obtain status of iop0, attempting a reset. IOP reset timeout. iop0: controller could not activated IOP reset timeout. I2O controller: probe of 0000:00:09.0 failed with error -110 I2O configuration manager v 0.04. (C) Copyright 1999 Red Hat Software I2O Block Storage OSM v0.9 (c) Copyright 1999-2001 Red Hat Software. ...and, like your install, I find the megaraid modules; :/usr/src/linux # find . -type f| xargs grep -i 150-6 ./drivers/pci/pci.ids: 1000 0523 MegaRAID SATA 150-6 RAID Controller ./drivers/scsi/megaraid/Kconfig.megaraid: LSI MegaRAID SATA 150-6 1000:1960:1000:0523 ./drivers/scsi/megaraid/megaraid_mbox.c: * LSI MegaRAID SATA 150-6 1000 1960 1000 0523 What happened? Maybe I am not using the correct syntax to insert the module, although I am not sure why the megaraid modules weren't loaded during install. Thank you again for your reply. Much obliged, James

2 1