August 2005 - openSUSE AMD64 - openSUSE Mailing Lists

LSI Megaraid 320-2x corruption
by Kelly Burkhart 21 Aug '05

21 Aug '05

I am running SuSE 9.3 on a dual Opteron 246 system (Tyan Thunder K8SR (S2881)). This machine has been running fine for several weeks using the on board SCSI controllers & SW RAID. We installed the LSI MegaRAID 320-2X controller with the TBBU03 battery backup and reinstalled SuSE 9.3. The installation did not go flawlessly: - Towards the end of the NFS installation, copying stopped. I switched consoles and noticed that I couldn't ping any other addresses in our network. I brought the ethernet interface down then back up and the installation resumed. - After the install, both megaraid and megaraid_mbox modules were loaded. I removed megaraid from INITRD_MODULES and ran mkinitrd. At this point we considered the installation suspect, but pressed on with testing. Now the corruption: One user was compiling code, another user was loading a database. After some time, g++ started getting internal compiler errors in cc1plus. I compared the checksum of this program with another install and they were different. I reinstalled gcc, verified checksums and everything worked for a while. Then internal compiler errors and bogus checksum again. I did not see anything alarming in the log files. So I booted into rescue mode and ran reiserfsck --check without any problems. Flashed the controller with the latest firmware and booted again. This time I set up a 'make clean; make' loop and watched it for about two hours without any problems. Then I started creating 4GB files with dd and deleting them and within 15 minutes another internal compiler error. Questions: - Does anyone run a similar setup without problems? - Has anyone seen similar problems? - Can anyone provide me some direction in tracking down this problem? Thanks, -K

4 9

Re: disk speed tips (was Re: [SLE] poor disk performance on 9.3 relative to 9.1)
by Kelly Burkhart 21 Aug '05

21 Aug '05

On Sat, 2005-08-20 at 15:54 -0700, Linda Walsh wrote: > This ended up way longer than I intended, but it covers > several factors that can affect disk performance and I > wanted to try to give you a complete as list as I could > think of to look for areas of change, potential causes, > etc. Sorry it ended up so long though, it's a complex > subject and I probably forgot to mention some items as it > is...:-). This was hugely helpful. Thank you. I came in tonight to do some more controlled experimentation with two machines. One machine is SCSI based HW RAID. The other is IDE based SW RAID. On each machine I partitioned the disks like this: test1 partition 9.1 root swap test2 partition 9.3 root test3 partition I ran my 'dd' test three times on each partition from each SuSE version on the SCSI machine. The differences between 9.1 and 9.3 were small enough I cannot determine which one is faster. The IDE machine took so long to install 9.3 on, I took a break, checked my email and found this note from Linda. I discovered using hdparm that while both disks were using udma5, hda read speed was *much* slower than hdc. I used 'raidsetfaulty' to remove the slow drive from the RAID set and my hdparm reads and dd writes were vastly improved. Nearly all of the servers I have available to test on have already been upgraded to 9.3 and are IDE systems with SW RAID. The few comparable 9.1 machines I had to test were IDE systems, but not using SW RAID. Thus I incorrectly attributed the difference to the OS version. Thank you all for your help! -K

1 0

hwinfo --cpu (Tyan K8E) gives less GHZ than other motherboards
by Pierre Patino 20 Aug '05

20 Aug '05

Hello I got a Tyan K8E and loaded SuSE 9.3 on it. With the original BIOS (1.0), hwinfo --cpu reports 1.0GHz. With the latest and greatest BIOS 2.01, hwinfo --cpu reports 1.8GHz. This is with an AMD Athlon 64 3000+. Two other motherboards (Gigabyte and Asus) report 2.0GHz with the same CPU. I wrote a device driver and also compared TSCs and jiffies and got the same results. Does anyone else see this? No answer from Tyan yet. TIA & Cheers

4 5

poor disk performance on 9.3 relative to 9.1
by Kelly Burkhart 19 Aug '05

19 Aug '05

Hi, I've noticed a noticeable disk IO performance decrease in 9.3 vs. 9.1. To test I've been running the following command: time dd if=/dev/zero of=bigfile bs=8k count=500000 Here are some representative numbers for three fairly comparable machines: 9.1 machine: 2*Opteron 242, 2 GB RAM 2 IDE drives (hda,hdc) ST312022A in SW RAID 1 kernel: 2.6.5-7.145-smp dd time: 103seconds ~ 39.8MB/Sec 9.3 machine: 2*Opteron 242, 1 GB RAM 2 IDE drives (hda,hdc) ST3120026A in SW RAID 1 kernel: 2.6.11.4-20a-smp dd time: 608seconds ~ 6.7MB/Sec 9.3 machine 2*Opteron 246, 1 GB RAM 2 IDE drives (hda,hdc) ST3120026A in SW RAID 1 kernel: 2.6.11.4-20a-smp dd time: 228seconds ~ 17.9MB/Sec All machines were idle while running the test. All filesystems are Reiser 3.6. - Has anyone noticed a disk performance degradation moving from 9.1 to 9.3? - What can I do to track down the cause of the difference between the 9.1 machine and the two 9.3 machines as well as the fast vs. slow 9.3 machine? -K

1 0

gcc with march=i686
by David Lazanja 19 Aug '05

19 Aug '05

When I try to compile a simple C program with -march=i686, I get the following error: cc1: error: CPU you selected does not support x86-64 instruction set I have gcc-32bit installed. Any help appreciated. Thanks David -- # Department of Applied Physics and Applied Mathematics # Columbia University

5 4

permissions quiz
by Mike Roy 19 Aug '05

19 Aug '05

Hello everyone: As you may remember from 'dumb guy number 1', I saved my old /home/mike directory on a separate HD and was able to recover all of my working files. That's the good news. The bad news is that they all are now listed as ROOT everything (user, group). I know there's commands to change individual files, etc. (chmod, chown), but is there a way I can change the permissions of a directory and all of its contents without doing each file individually? Any ideas greatly appreciated. Otherwise I'll be here until Thanksgiving :-\ Cheers, Mike

3 2

Display driver for MSI RS 480 on Suse 9.3
by Suraj Jacob 19 Aug '05

19 Aug '05

Hi, I recently purchased an MSI RS480 board and AMD Athlon 64 Fortunately, the installation had the SATA modules and I didnt have any trouble with the harddisks. But the display is still on framebuffer. I tried changing the driver to ati and raedon, but it didnt help, the X server dies saying no screens found. I am not sure if there is any other module that need to be installed. I guess someone on this list must have run into similar problems. If so, please help me. Thanks Suraj ____________________________________________________ Send a rakhi to your brother, buy gifts and win attractive prizes. Log on to http://in.promos.yahoo.com/rakhi/index.html

2 2

mouse pauses every 5 seconds?
by Ryan Biltz 18 Aug '05

18 Aug '05

I have a few Sun Java Desktop Systems (w2100z) with the dual AMD Opteron 250 processors and the Nvidia FX 3000 DH video card. I have the 7667 driver loaded. It's running SuSE 9.3 pro. I've noticed that there is a slight pause in mouse and monitor movement every 5 seconds or so then it jumps to catch up to where it should be. Does anyone have an idea what maybe causing this? TIA

1 0

clean installed 9.3 blocks tcsh users
by Yoriaki FUJIMORI 18 Aug '05

18 Aug '05

Dear listers, Recently I made clean installation of 9.3 on X2-based PC. Then I noticed that I cannot start desktop session properly. I have tried to find out what is wrong. Some of facts are as follows: (1) when users with tcsh as default shell (tcsh users) try to login to desktop, only xterm window without top bar appears. It is invoked as `xterm -T Failsafe'. (2) users with bash as defalut shell (bash users) have got no problem; they can start their desktop session very soon. (3) If the session is switched to Gnome-Failsafe, then tcsh users can start desktop session, with limited environment. (4) This phenomena do not appear on PCs running 9.3 upgraded from either 9.1 or 9.2. I made internet search, but I could not find a clue for my problem. I appreciate if some kind soul can give me pointers. Thanks for your attention. yoriaki fujimori

2 1

fc system spewing warning messages
by Yogesh Bhanu 18 Aug '05

18 Aug '05

Hi , I just bumped up my System SP2 from SP1 . and on boot the FC-System dissappeared . But with Qlogic SANSURFER I had to just map the luns again and all was back. But the system spews warning messages like the one listed below. System is Dual opteron 248 with qlogic 2312 attached to an IBM T600. ttached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0 scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:1) UNDERRUN status detected 0x15-0x800. scsi(2:255:1) UNDERRUN status detected 0x15-0x800. scsi(2:255:2) UNDERRUN status detected 0x15-0x800. scsi(2:255:2) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:1) UNDERRUN status detected 0x15-0x800. scsi(2:255:1) UNDERRUN status detected 0x15-0x800. scsi(2:255:2) UNDERRUN status detected 0x15-0x800. scsi(2:255:2) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:1) UNDERRUN status detected 0x15-0x800. scsi(2:255:1) UNDERRUN status detected 0x15-0x800. scsi(2:255:2) UNDERRUN status detected 0x15-0x800. scsi(2:255:2) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:0) UNDERRUN status detected 0x15-0x800. scsi(2:255:1) UNDERRUN status detected 0x15-0x800. scsi(2:255:1) UNDERRUN status detected 0x15-0x800. scsi(2:255:2) UNDERRUN status detected 0x15-0x800. scsi(2:255:2) UNDERRUN status detected 0x15-0x800. serio: kseriod exiting tg3: eth0: Link is up at 1000 Mbps, full duplex. tg3: eth0: Flow control is on for TX and on for RX. tg3: eth1: Link is up at 1000 Mbps, full duplex. tg3: eth1: Flow control is on for TX and on for RX. powernow-k8: Found 2 AMD Athlon 64 / Opteron processors (version 1.39.05) powernow-k8: MP systems not supported by PSB BIOS structure powernow-k8: init not cpu 0 eth0: no IPv6 routers present eth1: no IPv6 routers present QLogic Fibre Channel HBA Driver ACPI: PCI interrupt 0000:03:03.0[A] -> GSI 28 (level, low) -> IRQ 28 qla2300 0000:03:03.0: Found an ISP2312, irq 28, iobase 0xffffff0000015000 qla2300 0000:03:03.0: Configuring PCI space... qla2300 0000:03:03.0: Configure NVRAM parameters... qla2300 0000:03:03.0: Verifying loaded RISC code... scsi(3): Alloc Target 0 @ 00000100f727d000 scsi(3): Alloc Target 1 @ 00000100f8b97000 scsi(3): Alloc Target 2 @ 00000100f8f3d000 scsi(3): Alloc Target 3 @ 00000100f8b94000 scsi(3): **** Load RISC code **** qla2300 0000:03:03.0: Waiting for LIP to complete... scsi(3): Asynchronous P2P MODE received. scsi(3): Asynchronous LOOP UP (2 Gbps). qla2300 0000:03:03.0: LOOP UP detected (2 Gbps). scsi(3): Asynchronous PORT UPDATE. qla2300 0000:03:03.0: Topology - (F_Port), Host Loop address 0xffff scsi(3): RFT_ID exiting normally. scsi(3): RFF_ID exiting normally. scsi(3): RNN_ID exiting normally. scsi(3): RSNN_NN exiting normally. scsi(3): GID_PT entry - nn 200400a0b8163ace pn 200400a0b8163acf portid=010000. scsi(3): GID_PT entry - nn 200400a0b8163ace pn 200500a0b8163acf portid=010400. scsi(3): GID_PT entry - nn 200000e08b0ad239 pn 210000e08b0ad239 portid=010900. scsi(3): GID_PT entry - nn 200800a0b81711fa pn 200800a0b81711fb portid=010100. scsi(3): GID_PT entry - nn 200800a0b81711fa pn 200900a0b81711fb portid=010500. scsi(3): device wrap (010500) scsi(3): Assigning target ID=00 @ 00000100f727d000 to loop id=0x0081, port state=0x4, port down retry=24 scsi(3): Alloc Lun 0 @ tgt 0. scsi(3): Assigning target ID=01 @ 00000100f8b97000 to loop id=0x0082, port state=0x4, port down retry=24 scsi(3): Alloc Lun 0 @ tgt 1. scsi(3): Assigning target ID=02 @ 00000100f8f3d000 to loop id=0x0083, port state=0x4, port down retry=24 scsi(3): Alloc Lun 0 @ tgt 2. scsi(3): Alloc Lun 1 @ tgt 2. scsi(3): Alloc Lun 2 @ tgt 2. scsi(3): Assigning target ID=03 @ 00000100f8b94000 to loop id=0x0084, port state=0x4, port down retry=24 scsi(3): Alloc Lun 0 @ tgt 3. scsi(3): Alloc Lun 1 @ tgt 3. scsi(3): Alloc Lun 2 @ tgt 3. DEBUG: detect hba 3 at address = 00000100fb980328 scsi3 : qla2xxx qla2300 0000:03:03.0: QLogic Fibre Channel HBA Driver: 8.00.02 QLogic QLA2340 - ISP2312: PCI-X (133 MHz) @ 0000:03:03.0 hdma+, host#=3, fw=3.03.11 IPX Vendor: IBM Model: 1722-600 Rev: 0520 Type: Unknown ANSI SCSI revision: 03 qla2300 0000:03:03.0: scsi(3:0:0:0): Enabled tagged queuing, queue depth 32. scsi(3): Asynchronous PORT UPDATE ignored. scsi(3): Asynchronous PORT UPDATE ignored. Attached scsi generic sg1 at scsi3, channel 0, id 0, lun 0, type 31 scsi(3:0:0) UNDERRUN status detected 0x15-0x800. Vendor: IBM Model: 1722-600 Rev: 0520 Type: Unknown ANSI SCSI revision: 03 qla2300 0000:03:03.0: scsi(3:0:1:0): Enabled tagged queuing, queue depth 32. Attached scsi generic sg2 at scsi3, channel 0, id 1, lun 0, type 31 scsi(3:1:0) UNDERRUN status detected 0x15-0x800. Vendor: IBM Model: 1722-600 Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 qla2300 0000:03:03.0: scsi(3:0:2:0): Enabled tagged queuing, queue depth 32. SCSI device sdb: 487545184 512-byte hdwr sectors (249623 MB) scsi(3:2:0) UNDERRUN status detected 0x15-0x800. SCSI device sdb: drive cache: write back sdb: sdb1 Attached scsi disk sdb at scsi3, channel 0, id 2, lun 0 Attached scsi generic sg3 at scsi3, channel 0, id 2, lun 0, type 0 scsi(3:2:0) UNDERRUN status detected 0x15-0x800. Vendor: IBM Model: 1722-600 Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 qla2300 0000:03:03.0: scsi(3:0:2:1): Enabled tagged queuing, queue depth 32. scsi(3:2:0) UNDERRUN status detected 0x15-0x800. scsi(3:2:0) UNDERRUN status detected 0x15-0x800. SCSI device sdc: 4269799374 512-byte hdwr sectors (2186137 MB) scsi(3:2:1) UNDERRUN status detected 0x15-0x800. SCSI device sdc: drive cache: write back sdc: sdc1 Attached scsi disk sdc at scsi3, channel 0, id 2, lun 1 Attached scsi generic sg4 at scsi3, channel 0, id 2, lun 1, type 0 Vendor: IBM Model: 1722-600 Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 qla2300 0000:03:03.0: scsi(3:0:2:2): Enabled tagged queuing, queue depth 32. scsi(3:2:0) UNDERRUN status detected 0x15-0x800. scsi(3:2:0) UNDERRUN status detected 0x15-0x800. scsi(3:2:0) UNDERRUN status detected 0x15-0x800. SCSI device sdd: 3527417856 512-byte hdwr sectors (1806038 MB) scsi(3:2:2) UNDERRUN status detected 0x15-0x800. SCSI device sdd: drive cache: write back scsi(3:2:0) UNDERRUN status detected 0x15-0x800. sdd: sdd1 Attached scsi disk sdd at scsi3, channel 0, id 2, lun 2 scsi(3:2:1) UNDERRUN status detected 0x15-0x800. scsi(3:2:1) UNDERRUN status detected 0x15-0x800. Attached scsi generic sg5 at scsi3, channel 0, id 2, lun 2, type 0 Vendor: IBM Model: 1722-600 Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 qla2300 0000:03:03.0: scsi(3:0:3:0): Enabled tagged queuing, queue depth 32. scsi(3:2:1) UNDERRUN status detected 0x15-0x800. scsi(3:2:1) UNDERRUN status detected 0x15-0x800. scsi(3:2:1) UNDERRUN status detected 0x15-0x800. scsi(3:2:1) UNDERRUN status detected 0x15-0x800. SCSI device sde: 487545184 512-byte hdwr sectors (249623 MB) scsi(3:3:0) UNDERRUN status detected 0x15-0x800. SCSI device sde: drive cache: write back scsi(3:2:2) UNDERRUN status detected 0x15-0x800. scsi(3:2:2) UNDERRUN status detected 0x15-0x800. scsi(3:2:2) UNDERRUN status detected 0x15-0x800. scsi(3:2:2) UNDERRUN status detected 0x15-0x800. scsi(3:2:2) UNDERRUN status detected 0x15-0x800. scsi(3:2:2) UNDERRUN status detected 0x15-0x800. sde: sde1 Attached scsi disk sde at scsi3, channel 0, id 3, lun 0 Attached scsi generic sg6 at scsi3, channel 0, id 3, lun 0, type 0 scsi(3:3:0) UNDERRUN status detected 0x15-0x800. Vendor: IBM Model: 1722-600 Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 qla2300 0000:03:03.0: scsi(3:0:3:1): Enabled tagged queuing, queue depth 32. SCSI device sdf: 4269799374 512-byte hdwr sectors (2186137 MB) scsi(3:3:1) UNDERRUN status detected 0x15-0x800. SCSI device sdf: drive cache: write back scsi(3:3:0) UNDERRUN status detected 0x15-0x800. scsi(3:3:0) UNDERRUN status detected 0x15-0x800. scsi(3:3:0) UNDERRUN status detected 0x15-0x800. scsi(3:3:0) UNDERRUN status detected 0x15-0x800. scsi(3:3:0) UNDERRUN status detected 0x15-0x800. scsi(3:3:0) UNDERRUN status detected 0x15-0x800. sdf: sdf1 Attached scsi disk sdf at scsi3, channel 0, id 3, lun 1 Attached scsi generic sg7 at scsi3, channel 0, id 3, lun 1, type 0 Vendor: IBM Model: 1722-600 Rev: 0520 Type: Direct-Access ANSI SCSI revision: 03 qla2300 0000:03:03.0: scsi(3:0:3:2): Enabled tagged queuing, queue depth 32. SCSI device sdg: 3527417856 512-byte hdwr sectors (1806038 MB) scsi(3:3:2) UNDERRUN status detected 0x15-0x800. SCSI device sdg: drive cache: write back scsi(3:3:1) UNDERRUN status detected 0x15-0x800. scsi(3:3:1) UNDERRUN status detected 0x15-0x800. scsi(3:3:1) UNDERRUN status detected 0x15-0x800. scsi(3:3:1) UNDERRUN status detected 0x15-0x800. scsi(3:3:1) UNDERRUN status detected 0x15-0x800. scsi(3:3:1) UNDERRUN status detected 0x15-0x800. scsi(3:2:0) UNDERRUN status detected 0x15-0x800. sdg: sdg1 Attached scsi disk sdg at scsi3, channel 0, id 3, lun 2 Attached scsi generic sg8 at scsi3, channel 0, id 3, lun 2, type 0 scsi(3:3:2) UNDERRUN status detected 0x15-0x800. scsi(3:3:2) UNDERRUN status detected 0x15-0x800. scsi(3:3:2) UNDERRUN status detected 0x15-0x800. scsi(3:3:2) UNDERRUN status detected 0x15-0x800. scsi(3:3:2) UNDERRUN status detected 0x15-0x800. scsi(3:3:2) UNDERRUN status detected 0x15-0x800. scsi(3:255:0) UNDERRUN status detected 0x15-0x800. scsi(3:255:0) UNDERRUN status detected 0x15-0x800. scsi(3:255:0) UNDERRUN status detected 0x15-0x800. scsi(3:255:0) UNDERRUN status detected 0x15-0x800. scsi(3:255:0) UNDERRUN status detected 0x15-0x800. scsi(3:2:1) UNDERRUN status detected 0x15-0x800. scsi(3:255:1) UNDERRUN status detected 0x15-0x800. scsi(3:255:1) UNDERRUN status detected 0x15-0x800. scsi(3:2:2) UNDERRUN status detected 0x15-0x800. scsi(3:255:2) UNDERRUN status detected 0x15-0x800. scsi(3:255:2) UNDERRUN status detected 0x15-0x800. scsi(3:255:0) UNDERRUN status detected 0x15-0x800. scsi(3:255:0) UNDERRUN status detected 0x15-0x800. scsi(3:255:0) UNDERRUN status detected 0x15-0x800. scsi(3:255:1) UNDERRUN status detected 0x15-0x800. scsi(3:255:1) UNDERRUN status detected 0x15-0x800. scsi(3:255:2) UNDERRUN status detected 0x15-0x800. scsi(3:255:2) UNDERRUN status detected 0x15-0x800. scsi(3:3:0) UNDERRUN status detected 0x15-0x800. scsi(3:3:1) UNDERRUN status detected 0x15-0x800. scsi(3:3:2) UNDERRUN status detected 0x15-0x800. SGI XFS Quota Management subsystem XFS mounting filesystem dm-0 Ending clean XFS mount for filesystem: dm-0 The system comes up fine with SP1 and the earlier configuration. I had to use SanSurfer once more to reconfigure the system. For some reason The settings are not being retained when switching between SLES 9 and SP2 and same is repeated between SP1 and SP2 though if I switch between SLES 9 and SP1 the system comes up fine and there are no warning messages. any pointers what is causing this yogesh

1 0