January 2004 - openSUSE AMD64 - openSUSE Mailing Lists

8.2 Beta + S2880 + 3ware = crash?
by Rob Thomas 12 Jan '04

12 Jan '04

Hey, We've got a new system I've been trying to get going... Specs are as follows: - Tyan S2880 motherboard - Dual 246's - 2gb ddr 333 ecc - 3ware 8506 sata (I think) The server will randomly crash. I'm not sure if it's panicking or just freezing, as whenever we plug a monitor into it it's dead to the world, and thanks to screen-blanking isn't showing us what happened last on the monitor ;) All the server has been doing is acting as a mysql replication slave, under extremely light load. The crashes are not reproducable, but frequent. I've ran a few load tests and benchmarking tools, which the server handled without problems. I've updated the Tyan to the latest release (2.02, from 11/17/03), and installed k_smp-2.4.21 from Suse 9, neither helped. The only helpful information I could find on the topic was this post: http://www.beowulf.org/pipermail/beowulf/2003-November/008540.html I'm not sure what to try next, all help is appreciated. Thanks! -Rob Thomas

2 1

Instable kswapd / kernel oopses
by Kees Hoekzema 12 Jan '04

12 Jan '04

Hello list, We have a strange problem with one of our opteron servers. It used to be very unstable when we put it in production the first time, but after some tweaks we managed it to run for more than 20 days without crashing (the previous record was 2 hours..). Until today. We had to reboot the server and after it came up it was very unstable again. It crashed every half hour, it was pingable, a running vmstat would continue to run but no new commando's or shells could be started effectivily freezing the server. This was the same behavior we experienced when we started to use the server, we were unable than to conclude what was exactly wrong, it was just running stable after the xx'th reboot without any reason why it should be stable. We are currently using only 4G memory (6G total avail.) this makes the server stable but very slow, it almost looks like the memory management of the kernel still thinks he has 6G ram and uses 2G of swap to compensate the missing 2G of ram (we are starting with mem=4g, we don't have physical access to the server now). Also when running in 4G-mode kswapd is doing strange things ~ every 5 minutes, a snapshot of top shows it useing a huge amount of CPU and MEM, it blocks the other processes completely making the server unavailable for several minutes. top - 17:08:37 up 3:27, 2 users, load average: 9.65, 9.75, 8.59 Tasks: 350 total, 10 running, 340 sleeping, 0 stopped, 0 zombie Cpu(s): 4.0% user, 95.6% system, 0.0% nice, 0.4% idle Mem: 3641112k total, 3367880k used, 273232k free, 16308k buffers Swap: 4056360k total, 1372000k used, 2684360k free, 1940732k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 7 root 25 0 0 0 0 R 96.5 0.0 42:24.97 kswapd 29695 acm 21 0 632 248 232 R 20.4 0.0 0:03.57 top 29619 mysql 17 0 1333m 2228 2084 R 6.8 0.1 0:01.26 mysqld 29651 mysql 18 0 1333m 936 856 R 6.1 0.0 0:00.48 mysqld 29623 mysql 18 0 1333m 1556 1452 R 5.1 0.0 0:00.92 mysqld 29650 mysql 17 0 1333m 692 664 R 5.0 0.0 0:00.29 mysqld This is the reason that with only 4G ram the load-averages of the server are 8 to 10 times higher than normal, we cant figure out why. But that isn't the main problem, the main problem are the kernel oopses that causes our server to freeze, we get this in our logs: Jan 12 11:00:00 apollo /USR/SBIN/CRON[1973]: (root) CMD (/usr/sbin/ntpdatentp.xs4all.nl > /dev/null 2>&1) Jan 12 11:00:02 apollo xinetd[746]: sysinfo: fork failed: Cannot allocate memory (errno = 12) Jan 12 11:00:22 apollo last message repeated 4 times Jan 12 11:00:22 apollo xinetd[746]: service sysinfo: too many consecutive fork failures Jan 12 11:00:23 apollo xinetd[746]: sysinfo: fork failed: Cannot allocate memory (errno = 12) Jan 12 11:00:43 apollo last message repeated 4 times Jan 12 11:00:43 apollo xinetd[746]: service sysinfo: too many consecutive fork failures Jan 12 11:00:22 apollo last message repeated 4 times Jan 12 11:00:22 apollo xinetd[746]: service sysinfo: too many consecutive fork failures Jan 12 11:00:23 apollo xinetd[746]: sysinfo: fork failed: Cannot allocate memory (errno = 12) Jan 12 11:00:43 apollo last message repeated 4 times Jan 12 11:00:43 apollo xinetd[746]: service sysinfo: too many consecutive fork failures Jan 12 11:01:15 apollo kernel: Unable to handle kernel paging request at virtual address 0000007f804537e0 Jan 12 11:01:15 apollo kernel: printing rip: Jan 12 11:01:15 apollo kernel: ffffffff801494f7 Jan 12 11:01:15 apollo kernel: PML4 3febf067 PGD 401a3067 PMD 0 Jan 12 11:01:15 apollo kernel: Oops: 0000 Jan 12 11:01:15 apollo kernel: CPU 0 Jan 12 11:01:15 apollo kernel: Pid: 7, comm: kswapd Not tainted Jan 12 11:01:15 apollo kernel: RIP: 0010:[kmem_cache_reap+343/880]{kmem_cache_reap+343} Jan 12 11:01:15 apollo kernel: RIP: 0010:[<ffffffff801494f7>]{kmem_cache_reap+343} Jan 12 11:01:15 apollo kernel: RSP: 0018:0000010102c4fdf8 EFLAGS: 00010016 Jan 12 11:01:15 apollo kernel: RAX: 000ffffff0000000 RBX: 0000000000000001 RCX: 0000000000000019 Jan 12 11:01:15 apollo kernel: RDX: 0000007fffff8000 RSI: 0000000000000000 RDI: 00000100e78f3b10 Jan 12 11:01:15 apollo kernel: RBP: 00000100e78f4440 R08: 000000000000003a R09: 00000100e78f3b30 Jan 12 11:01:15 apollo kernel: R10: 000001017fd06408 R11: 000001017fd06400 R12: 0000000000000058 Jan 12 11:01:15 apollo kernel: R13: 0000000000000001 R14: ffffffff7fffffff R15: 0000000080000000 Jan 12 11:01:15 apollo kernel: FS: 000000000050e800(0000) GS:ffffffff804bba80(0000) knlGS:0000000000000000 Jan 12 11:01:15 apollo kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b Jan 12 11:01:15 apollo kernel: CR2: 0000007f804537e0 CR3: 0000000000101000 CR4: 00000000000006e0 Jan 12 11:01:15 apollo kernel: Process kswapd (pid: 7, stackpage=10102c4f000) Jan 12 11:01:15 apollo kernel: Stack: 0000010102c4fdf8 0000000000000018 ffffffff8014ae20 00000100e78f3b20 Jan 12 11:01:15 apollo kernel: 0000000100000000 0000010100013008 0000000000000020 00000000000001d0 Jan 12 11:01:15 apollo kernel: 00000101000003c0 0000010102c4fe84 0000000000000000 0000000000000000 Jan 12 11:01:15 apollo kernel: Call Trace: [shrink_cache+1104/1184]{shrink_cache+1104} Jan 12 11:01:15 apollo kernel: Call Trace: [<ffffffff8014ae20>]{shrink_cache+1104} Jan 12 11:01:15 apollo kernel: [shrink_caches+41/128]{shrink_caches+41} [try_to_free_pages_zone+98/272]{try_to_free_pages_zone+98} Jan 12 11:01:15 apollo kernel: [<ffffffff8014b0f9>]{shrink_caches+41} [<ffffffff8014b1b2>]{try_to_free_pages_zone+98} Jan 12 11:01:15 apollo kernel: [kswapd_balance_pgdat+113/224]{kswapd_balance_pgdat+113} [kswapd_balance+28/64]{kswapd_balance+28} Jan 12 11:01:15 apollo kernel: [<ffffffff8014b3d1>]{kswapd_balance_pgdat+113} [<ffffffff8014b45c>]{kswapd_balance+28} Jan 12 11:01:15 apollo kernel: [kswapd+168/195]{kswapd+168} [child_rip+8/16]{child_rip+8} Jan 12 11:01:15 apollo kernel: [<ffffffff8014b5b8>]{kswapd+168} [<ffffffff80110ae4>]{child_rip+8} Jan 12 11:01:15 apollo kernel: [kswapd+0/195]{kswapd+0} [child_rip+0/16]{child_rip+0} Jan 12 11:01:15 apollo kernel: [<ffffffff8014b510>]{kswapd+0} [<ffffffff80110adc>]{child_rip+0} Jan 12 11:01:15 apollo kernel: Jan 12 11:01:15 apollo kernel: Jan 12 11:01:15 apollo kernel: Code: 48 0f b6 92 e0 b7 45 80 48 8b 14 d5 00 b6 45 80 48 8b 8a c8 Jan 12 12:11:09 apollo syslogd 1.4.1: restart. And output from vmstat during and after this oops: procs -----------memory---------- ---swap-- -----io---- --system-- ----cpu---- r b swpd free buff cache si so bi bo in cs us sy id wa 1 2 0 187088 37800 3940288 0 0 1372 5772 500 745 3 3 94 0 1 2 0 186372 37916 3940844 0 0 560 2108 293 297 0 23 77 0 0 2 0 186364 37924 3940844 0 0 0 12 140 31 0 35 65 0 0 2 0 186364 37924 3940844 0 0 0 0 127 4 0 0 100 0 0 2 0 186364 37924 3940844 0 0 0 0 148 12 0 0 100 0 (after which it stays at 100% idle and a building up of blocked processes, not even one running process). A kinda nasty piece of work from.. kspwad! What is wrong with kswapd? it crashes our server if we use 6G and slows down our server to a crawl when using 4G (kernel option mem=4g). Is this the BIOS bug mentioned earlier or an undocumented AMD 'feature'. We are going to take two dimms out the server so it runs physically with 4G (maybe we just slap it a bit too for the trouble it is giving us ;)). But are there more things we can do? it won't boot a vanilla kernel (it crashes during boot on.. kswapd!..) , it boots the latest 2.4.21-149 suse kernel without problems though. -kees

2 1

Re: [suse-amd64] Status of Serial ATA support [Virus checked US]
by Rodrigo V Monteiro 12 Jan '04

12 Jan '04

Hello Pete, Yes, I read your reply and found your machine a splendid one setup. Mine setup involves a ATA133- 80GB disc layouted like this: hda1 - Windows 2000 (just for games) hda2 - /boot for Slackware hda3 - /boot for Suse 9.0 AMD64 hda4 - extended like this: hda5: Windows data volume hda6: Linux Swap for both ones hda7: / for Slackware hda8: / for Suse Just keeping boot partitions at the begining of the disc to play safe with IDE issues. I had Suse 8.2 installed before but I am not sure if I had problems booting it with SK8N (I had similiar problems with an older K7 board). When installing Suse 9-64bit I got no problems with the boot CD but the first reboot would not work stopping after discs messages. I booted safe option grom GRUB, added the 3 parameters to it (ide=nodma apm=no acpi=no) and everything went fine. I took out ide=dma and got the regular boot, so I need to isolate the apm and acpi yet. The setup is 2 days old so I haven't time to play around with it. I do intend to buy next AMD64 Suse version with new Kernel and SATA drivers (the 64-bit is not sold here yet so I had to download it for awhile). Also I do believe Suse will provide them soon since SK8N is the most popular board for Opteron/64-FX processor. As it goes on the list, SATA chipset used in this board is still not well supprted or designed. People advise to buy a well supported board for SATA and RAID. Unfortunatelly there is no SATA drivers easily to be found in Brazil to test it. It should be a year until it caches up. If I can be of any help, just let me know. (Embedded image moved to file: pic00153.gif) (Embedded image moved to file: O: +55 11 F: +55 11 EY/Comm: pic00292.gif)Rodrigo De 3523-5494 3078-1105 4776668 Vincenzo Monteiro "Pete Bradbury" <pete.bradbury@stantonb To: "Rodrigo V Monteiro" <Rodrigo.V.Monteiro(a)br.ey.com> ury.org.uk> cc: Subject: Re: [suse-amd64] Status of Serial ATA support [Virus checked US] 12/01/2004 12:36 Hi Rodrigo Was yours a dual boot or a standalone? I ask because I have a similar setup - perhaps you've read my reply to this thread along the way? ----- Original Message ----- From: "Rodrigo V Monteiro" <Rodrigo.V.Monteiro(a)br.ey.com> To: <suse-amd64(a)suse.com> Sent: Monday, January 12, 2004 11:14 AM Subject: Re: [suse-amd64] Status of Serial ATA support [Virus checked US] Hi Dave, not sure if it helps but when I installed Suse 8.2 and Suse 9.0 64-bit in my SK8N board with ATA133 I only was able to reboot it using ide=nodma apm=off acpi=off parameters at boot line in GRUB. These parameters are listed at Safe Boot menu option. This same problem happend to me with an older board during install boot and I could proceed normally using the safe boot option from the install menu. I still have to trim down which of the 3 parameters I can exclude from the boot line so to disable functions. ide=nodma should slow down disc performance a bit but I would have to benchmark how much. Hope that helps. (Embedded image moved to file: pic26299.gif) (Embedded image moved to file: O: +55 11 F: +55 11 EY/Comm: pic17035.gif)Rodrigo De 3523-5494 3078-1105 4776668 Vincenzo Monteiro Andreas Jaeger <aj(a)suse.de> To: <davereid(a)telusplanet.net> cc: <suse-amd64(a)suse.com> 12/01/2004 06:12 Subject: Re: [suse-amd64] Status of Serial ATA support "Dave Reid" <davereid(a)telusplanet.net> writes: > I disabled the Serial ATA drive and installed a 60GIG standard ATA133 drive. > I installed Windows on this drive to confirm all the hardware was working > and it was. In went the SUSE 9.0 PRO for AMD 64 DVD I paid $200 for, it > displayed the install menu, I selected INSTALL and it start to boot. It then > promptly seized up at exactly the same place it did before as below: > > Starting hardware detection >>misc.1.3 read floppy - then nothing. This so far was always a BIOS bug. So, please buy next time correctly working hardware. Workarounds: - Add "idle=poll" to the linuxrc command line (where you choose the boot options) - Disable legacy USB support Which of these two will help, depends on the exact problem and the BIOS bug. > [...] Andreas -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj SuSE Linux AG, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 (See attached file: attmnqoz.dat) ---------------------------------------------------------- The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Ernst & Young is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. Note: If you have received a delivery failure report, it may be due to the change in the Ernst & Young e-mail domains from "eyi.com", "ey.bm", or "ey.bs" to "ey.com". Could you please make the necessary amendment, if required, and resend the message. ---------------------------------------------------------------------------- ---- > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: suse-amd64-help(a)suse.com ---------------------------------------------------------- The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. Ernst & Young is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt. Note: If you have received a delivery failure report, it may be due to the change in the Ernst & Young e-mail domains from "eyi.com", "ey.bm", or "ey.bs" to "ey.com". Could you please make the necessary amendment, if required, and resend the message.

2 2

Progress on 2.6.x boot iso?
by Dave Pyke 12 Jan '04

12 Jan '04

a week or so ago someone asked about a 2.6.x kernel boot ISO. I've been waiting for the same so I can install 9.0 on my system (1 SATA drive non-raid on an SK8N board). Since the installer can't see my drive using the 2.4.x kernel, I was hoping progress was being made on a new boot iso. Any hope of one in the near future? Thanks Dave Pyke ___________________ We stopped striving to be unique when politically correct people inadvertently made "special" a bad thing.

2 1

Installation problem at raid-0 set at Sil3114 controller at dual- opteron motherboard
by Khamenia, Valery 12 Jan '04

12 Jan '04

Hello All, I have DUAL-opteron matherboard "tyan thunder k8w". I am blocked with a following problem during SUSE 9(AMD64) installation: SUSE installer fails to detect the Raid-0 set created at SiliconImage 3114 controller. As it becomes clear from here: http://beau.org/pipermail/whitebox-devel/2003-December/000561.html and from this thread: http://lists.suse.com/archive/suse-amd64/2003-Dec/0014.html it is still a problem, so any comments/hints/answers are greatly appreciated. Thank you very much, a priori. kind regards, Valery A.Khamenya --------------------------------------------------------------------------- Bioinformatics Department BioVisioN AG, Hannover

2 1

How to make F2(boot messages) the default?
by david.obrien＠amd.com 09 Jan '04

09 Jan '04

Hi all, How does one make SL 9.0 act as if one hit the "F2" key by default while booting? Thanks, -- David

3 2

AMD 64 + AVM ISDN-Karte über USB
by Ulrich Piethe 09 Jan '04

09 Jan '04

Hallo, welche USB-ISDN-Karte von AVM läuft??? Laut Pressestelle von AVM haut SuSE 9.0 für den AMD Athlon 64 und der FritzCard! USB nicht hin... Welche AVM läuft??? Danke. Mit freundlichen Grüßen Ulrich Piethe

2 1

Installation problem with Mysql x86_64 rpm
by Travis Reeder 08 Jan '04

08 Jan '04

I know this isn't the best list for this, but I didn't get an answer on the mysql list so maybe one of you could help... I have a brand new fresh install of SUSE 9, 64 bit and am trying to install mysql 64 bit, but I get the following output: I've bolded the important lines (or at least what i think is important "mysqld got signal 11;". Has anybody experienced this or know how to solve this? linux:~ # rpm -i --force MySQL-server-4.0.17-0.x86_64.rpm warning: MySQL-server-4.0.17-0.x86_64.rpm: V3 DSA signature: NOKEY, key ID 5072e1f5 Giving mysqld a couple of seconds to exit nicely Preparing db table Preparing host table Preparing user table Preparing func table Preparing tables_priv table Preparing columns_priv table Installing all prepared tables *mysqld got signal 11;* This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=8388600 read_buffer_size=131072 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 225791 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Installation of grant tables failed! Examine the logs in /var/lib/mysql for more information. You can also try to start the mysqld daemon with: /usr/sbin/mysqld --skip-grant & You can use the command line tool /usr/bin/mysql to connect to the mysql database and look at the grant tables: shell> /usr/bin/mysql -u root mysql mysql> show tables Try 'mysqld --help' if you have problems with paths. Using --log gives you a log in /var/lib/mysql that may be helpful. The latest information about MySQL is available on the web at http://www.mysql.com Please consult the MySQL manual section: 'Problems running mysql_install_db', and the manual section that describes problems on your OS. Another information source is the MySQL email archive. Please check all of the above before mailing us! And if you do mail us, you MUST use the /usr/bin/mysqlbug script!

3 4

software suspend?
by Dmitry Melekhov 08 Jan '04

08 Jan '04

Hello! Is it possible to use software suspend on x86-64? Unofortunately, I'll have turn off my workstation every evening :-(

3 3

RE: [suse-amd64] system hanging for 1-3 min
by Alan Gray 08 Jan '04

08 Jan '04

I found that when using the silicon image SATA controller (with serial drives) if the drives were not raid 0/1, I would get hangs exactly like you are saying. (ie) using 2 drives as separate volumes cause the problem. (note) this was on Suse 8.2 Beta and Windows XP 64 bit edition, so it was a hardware issue. Even when I ran SCSI disks on 8.2 beta, pauses still continued. In recent times, running on Windows XP 64, the problem has seemed to go away, as well as Suse 9.0 running on IDE and SCSI. I've changed So many things, that I cannot say why the problem no longer seems to show. Maybe the computer needed a really long burn in period before it stabablised. I'm not a hardware person at all so beyond this, I'm just gropping in the dark. Alan > -----Original Message----- > From: Keith Pettit [mailto:kpettit@dsidata.net] > Sent: Thursday, 8 January 2004 2:25 PM > To: Alan Gray > Cc: suse-amd64(a)suse.com > Subject: Re: [suse-amd64] system hanging for 1-3 min > > > I have SATA ability but I'm not using any serial drives. I'm using a > megaraid SCSI card with raid 5. > > I'm not sure the exact motherboard but the chipset is: > Chipset AMD® 8111™ [HyperTransport I/O Hub] > > > The complete system specs are here: > http://www.penguincomputing.com/store/altus-3200-techspecs.php > > Thanks, > > Keith > > Alan Gray wrote: > > >What hardware ? Is is a Tyan K2885 motherboard with SATA drives ? > > > > > > > >>-----Original Message----- > >>From: Keith Pettit [mailto:kpettit@dsidata.net] > >>Sent: Thursday, 8 January 2004 12:47 PM > >>To: suse-amd64(a)suse.com > >>Subject: [suse-amd64] system hanging for 1-3 min > >> > >> > >>I've notcied a weird problem on both my SUSE 9 and sle8 > systems. It > >>hangs, for periods of 30sec-5min, then starts working like > >>nothing has > >>happened. There is nothing in the logs to give me any clue, and > >>everything always seems to work when it comes back. > >> > >>Currently Im using version 9 with dual AMD's and about 8GB of ram. > >> > >>Has anybody else seen or been able to resolve this problem? > >> > >>Thanks, > >> > >>Keith > >> > >> > >> > >> > >>-- > >>Check the List-Unsubscribe header to unsubscribe > >>For additional commands, email: suse-amd64-help(a)suse.com > >> > >> > >> > >> > > > > > > > > > > -- > Check the List-Unsubscribe header to unsubscribe > For additional commands, email: suse-amd64-help(a)suse.com > >

1 0