openSUSE AMD64 September 2005

amd64@lists.opensuse.org

57 participants
62 discussions

RE: [suse-amd64] PCI memory hole and remapping (was -> Re: [suse-amd64] Memory Problem: 3Gb instead of 4Gb, TYAN K8WE s2895, 2x252 Opteron )

by Langsdorf, Mark

> > If your BIOS is doing this (as opposed to > > you mucking with the settings), I need to get the AMD BIOS > > developers to talk to your BIOS developers. > > That would be great. Please do that. What's shown above is > indeed the mtrr settings that come from the bios. I didn't > change anything. And that's the same on two different PCs > (both iwth A8V), so it's not that just one PC is broken or > sth... However, whatever problems I was reporting to ASUS, I > never got anything helpful back, or a fix in the next release > etc. They seem to ignore user bug reports, but I guess they > won't ignore AMD... What motherboard, BIOS vendor, and BIOS version are you using? > > You may want to check if your BIOS has an option for "Discrete" or > > "continuous" usage of MTRRs. Experiment with both settings - I > > believe "discrete" should work better in a memory hoisting > > environmnet. > > Unfortunately not! I read about other mainboards having this > option in the bios and looked for it carefully, because other > people reported they could fix the problem with the fglrx > driver using this setting. Unfortunately, Asus didn't put > such a setting in their latest release... They're supposed to have done so, after a huge fuss we had over these issues last year. After you give me the motherboard models, BIOS vendor, and BIOS version I can hopefully get this resolved. -Mark Langsdorf AMD, Inc.

16 years, 6 months

A8V, Suse 9.3 and BIOS memory remapping

by Siegbert Baude

Hi, I just upgraded the BIOS of my A8V deluxe to the newest version (1014) und tried to boot with the Suse 9.3 Live-CD, distributed by the German magazine c't. If I activate "software memory hole" in the BIOS, I see only 3GB (with the "free" comand and also inside the BIOS system information) despite 4GB of physical RAM installed. dmesg says this: Linux version 2.6.11.4-20a-default (geeko@buildhost) (gcc version 3.3.5 20050117 (prerelease) (SUSE Linux)) #1 Wed Mar 23 21:52:37 UTC 2005 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000bffb0000 (usable) BIOS-e820: 00000000bffb0000 - 00000000bffc0000 (ACPI data) BIOS-e820: 00000000bffc0000 - 00000000bfff0000 (ACPI NVS) BIOS-e820: 00000000bfff0000 - 00000000c0000000 (reserved) BIOS-e820: 00000000ff780000 - 0000000100000000 (reserved) BIOS-e820: 0000000100000000 - 0000000140000000 (usable) Warning only 4GB will be used. Use a PAE enabled kernel. 3200MB HIGHMEM available. 896MB LOWMEM available. Just as clarification of terms: - What is HIGHMEM and LOWMEM and shouldn't they be called the other way round as the big part is counted from 0x00000000 on? - Isn't PAE for 32bit OS only (I booted the 64bit version)? So after all, would a full 64bit installation of 9.3 install a "PAE enabled kernel", so that I would see all 4GB of installed RAM? Is this a special choice then or simply the standard kernel? Thanks in advance for your help! Ciao Siegbert

16 years, 7 months

apache+php 64 calling elf32 exe

by Riccardo Ghiglianovich

Hi all, I am new here; I have found that if I call an ELF32 Executable program from a php page loaded by a 64 bit PHP module then I obtain a shared library error, even if the program does not require the library. practical example: compile this ====== pro.c #include <stdio.h> main() { printf("Hello world\n"); } ------ cc -o pro -m32 pro.c then call it from a php page: ========= r.phtml <?php $s = "/tmp/pro 2>/tmp/er 1>&2"; echo "$s : "; $rrr=exec($s); echo `cat /tmp/er`; echo "<hr>"; // just to test that it works... $s = "ls -al /tmp 2>/tmp/er 1>&2"; echo "$s : "; $rrr=exec($s); echo `cat /tmp/er`; ?> ---- http://localhost/r,phtml issuee? Error?Bug? my fault??? Hints? I cannot recompile at 64 all my programs ... Thanks, regards, Ric

16 years, 7 months

system locks up with SuSE 9.3

by Wilko Keegstra

We have 3 computers with Asus A8V motherboard. 1 has no raid and uses the on board Marvell Gigabit ethernet.... NO problems (driver sk98lin loaded) 2 with raid 0 , when Marvell Gigabit ethernet is used (sk98lin driver) System locks up 3 with raid 1, when Marvell Gigabit ethernet is used (sk98lin driver) system locks up So the right drivers are used, but on the systems with raid (VIA VT8237) the system will hang sooner or later (but within minutes). Wilko -- +------------------------------------------------------------+ | Dr. Wilko Keegstra priv.phone: +31594514153,+31610477915| | Groningen University email: W.Keegstra(a)rug.nl | | Dept.of Biophys.Chemistry | | Nijenborgh 4 phone: +31503634224 | | 9747 AG GRONINGEN fax : +31503634800 | | The Netherlands | +------------------------------------------------------------+

16 years, 7 months

users can't run firefox: undef symbol: gdk_threads_lock

by Ryan Biltz

Hello, Root can run firefox ok but regular users can't. They get the following message: /opt/MozillaFirefox/lib/firefox-bin: symbol lookup error: /opt/MozillaFirefox/lib/firefox-bin: undefined symbol: gdk_threads_lock This occurs on both 1.0.6 and 1.0.7 suse amd64 9.3 Anyone seen this or fixed this before? --ryan

16 years, 7 months

Problem with large disks at Sil 3114 on Opteron

by Jens

Hi, I have a strange problem with 4 SATA disks connected to Sil 3114 SATA controler. With low traffic it works well. But if the traffic is more than 30 - 40 seconds a little bit higher (approx. 20 MB/s) then random disks fails. Sometime the box crash complete, sometimes i become kernel oops. I want build a software raid 5 with these four disks. But everytime during raid initialisation fails one, later second disk and the raid is brocken. The failure occur randomly over the disks. It's a standard SuSE 9.3 (x86_64) with kernel 2.6.11.4-21.9-smp. Motherboard: ASUS K8N-DL (BIOS version 1006) SATA controler: Sil 3114 (BIOS version 5.2.09) 4 SATA disks: Maxtor 6L205S0 (250 GB) ACPI is disable in the BIOS because the on-board Gigabit-Lan doesn't work with activated ACPI. <------- kernel oops in /var/log/messages -------------> ata7: status=0x51 { DriveReady SeekComplete Error } ata7: error=0x04 { DriveStatusError } ata5: command 0x25 timeout, stat 0x51 host_stat 0x60 ata5: status=0x51 { DriveReady SeekComplete Error } ata5: error=0x04 { DriveStatusError } SCSI error : <4 0 0 0> return code = 0x8000002 sda: Current: sense key: Aborted Command Additional sense: No additional sense information end_request: I/O error, dev sda, sector 10682943 raid5: Disk failure on sda1, disabling device. Operation continuing on 2 devices scsi: Device offlined - not ready after error recovery: host 4 channel 0 id 0 lun 0 SCSI error : <4 0 0 0> return code = 0x8000002 sda: Current: sense key: Aborted Command Additional sense: No additional sense information end_request: I/O error, dev sda, sector 10682951 scsi4 (0:0): rejecting I/O to offline device ----------- [cut here ] --------- [please bite here ] --------- Kernel BUG at elevator:613 invalid operand: 0000 [1] SMP CPU 0 Modules linked in: usbserial autofs4 freq_table processor ipv6 snd_pcm_oss snd_mixer_oss snd_intel8x0 snd_ac97_codec snd_pcm sn d_timer snd floppy soundcore snd_page_alloc iptable_mangle iptable_nat iptable_filter ipt_state ip_conntrack_ftp ip_conntrack i p_tables edd evdev joydev st sr_mod video1394 raw1394 capability sg tg3 e1000 ohci1394 ieee1394 ohci_hcd ehci_hcd usbcore i2c_n force2 i2c_core ext3 jbd parport_pc lp parport dm_mod raid5 xor reiserfs ide_cd cdrom ide_disk sata_sil sata_nv libata amd74xx ide_core sd_mod scsi_mod Pid: 906, comm: scsi_eh_4 Not tainted 2.6.11.4-21.9-smp RIP: 0010:[<ffffffff80292672>] <ffffffff80292672>{elv_next_request+130} RSP: 0018:ffff810002ea9cd8 EFLAGS: 00010046 RAX: 00000000000002f0 RBX: ffff8100bdd0dba0 RCX: 000000000003ffff RDX: ffff8100bdd0dba0 RSI: 0000000000000092 RDI: ffffffff80402c40 RBP: 000000000005e000 R08: 0000000000000033 R09: 0000000000000000 R10: 00000000ffffffff R11: 0000000000000000 R12: ffff810081707700 R13: ffff810002f31000 R14: ffff81007fdcede8 R15: ffff810081707700 FS: 00002aaaab3636e0(0000) GS:ffffffff804e3980(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00002aaaaaf65a64 CR3: 00000000bd296000 CR4: 00000000000006e0 Process scsi_eh_4 (pid: 906, threadinfo ffff810002ea8000, task ffff8100bf787070) Stack: ffff810081707700 ffff81007fdcec00 ffff810081707700 ffffffff880066ea ffff810081707700 ffff8100bdd0dba0 ffff810081707700 0000000000000001 0000000000000296 ffffffff802962e0 Call Trace:<ffffffff880066ea>{:scsi_mod:scsi_request_fn+218} <ffffffff802962e0>{__generic_unplug_device+32} <ffffffff802964a6>{blk_insert_request+166} <ffffffff88006bb0>{:scsi_mod:scsi_requeue_command+48} <ffffffff88006c85>{:scsi_mod:scsi_end_request+133} <ffffffff88007167>{:scsi_mod:scsi_io_completion+1127} <ffffffff88029846>{:sd_mod:sd_rw_intr+742} <ffffffff88000556>{:scsi_mod:scsi_finish_command+214} <ffffffff880043ab>{:scsi_mod:scsi_eh_flush_done_q+235} <ffffffff880057a4>{:scsi_mod:scsi_error_handler+1764} <ffffffff8015f529>{__free_pages_ok+217} <ffffffff8010f6bb>{child_rip+8} <ffffffff880050c0>{:scsi_mod:scsi_error_handler+0} <ffffffff8010f6b3>{child_rip+0} Code: 0f 0b 83 d1 36 80 ff ff ff ff 65 02 66 90 48 8b 43 08 48 89 RIP <ffffffff80292672>{elv_next_request+130} RSP <ffff810002ea9cd8> <6>md: md0: sync done. Unable to handle kernel paging request at ffff82bc81000030 RIP: <ffffffff801628b3>{free_block+195} PGD 0 Oops: 0000 [2] SMP CPU 0 Modules linked in: usbserial autofs4 freq_table processor ipv6 snd_pcm_oss snd_mixer_oss snd_intel8x0 snd_ac97_codec snd_pcm sn d_timer snd floppy soundcore snd_page_alloc iptable_mangle iptable_nat iptable_filter ipt_state ip_conntrack_ftp ip_conntrack i p_tables edd evdev joydev st sr_mod video1394 raw1394 capability sg tg3 e1000 ohci1394 ieee1394 ohci_hcd ehci_hcd usbcore i2c_n force2 i2c_core ext3 jbd parport_pc lp parport dm_mod raid5 xor reiserfs ide_cd cdrom ide_disk sata_sil sata_nv libata amd74xx ide_core sd_mod scsi_mod Pid: 6, comm: events/0 Not tainted 2.6.11.4-21.9-smp RIP: 0010:[<ffffffff801628b3>] <ffffffff801628b3>{free_block+195} RSP: 0018:ffff81008157fdc8 EFLAGS: 00010086 RAX: ffff82bc81000000 RBX: ffff8100bfa2eb80 RCX: ffff81000000d000 RDX: 00000007f0000000 RSI: 00007f0000000000 RDI: 0000000000000000 RBP: 0000000000000000 R08: 0000000080000000 R09: 0000000000019a28 R10: 00000000ffffffff R11: 0000000000000000 R12: ffff8100bfa2ebc8 R13: 0000000000000001 R14: ffff810002e1e190 R15: ffffffff7fffffff FS: 00002aaaab3636e0(0000) GS:ffffffff804e3980(0000) knlGS:0000000000000000 CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b CR2: ffff82bc81000030 CR3: 00000000bd296000 CR4: 00000000000006e0 Process events/0 (pid: 6, threadinfo ffff81008157e000, task ffff81007fe60810) Stack: ffff8100bfa2ebe8 ffff810002e1e190 ffff810002e1e180 0000000000000001 0000000000000003 ffff8100bfa2ec28 ffff8100bfa2eae8 ffffffff801629f6 ffff8100bfa2eae8 ffff8100bfa2eb80 Call Trace:<ffffffff801629f6>{drain_array_locked+118} <ffffffff80162aec>{cache_reap+172} <ffffffff80162a40>{cache_reap+0} <ffffffff80148e4c>{worker_thread+476} <ffffffff801326f0>{default_wake_function+0} <ffffffff80130a13>{__wake_up_common+67} <ffffffff801326f0>{default_wake_function+0} <ffffffff80148c70>{worker_thread+0} <ffffffff8014d549>{kthread+217} <ffffffff8010f6bb>{child_rip+8} <ffffffff8014d470>{kthread+0} <ffffffff8010f6b3>{child_rip+0} Code: 48 8b 70 30 48 8b 56 08 48 8b 06 48 89 50 08 48 89 02 48 2b RIP <ffffffff801628b3>{free_block+195} RSP <ffff81008157fdc8> CR2: ffff82bc81000030 2]: Accepted keyboard-interactive/pam for root from ::ffff:141.30.156.117 port 41005 ssh2 8]: Accepted keyboard-interactive/pam for root from ::ffff:141.30.156.117 port 41201 ssh2 <4>warning: many lost ticks. Your time source seems to be instable or some driver is hogging interupts rip default_idle+0x20/0x30 <--------------------------------------------------------------------> Thank you very much for your help. Sincerely yours Jens Weiße ___________________________________________________________ Was denken Sie über E-Mail? Wir hören auf Ihre Meinung: http://surveylink.yahoo.com/wix/p0379378.aspx

16 years, 7 months

SuSEfirewall2 changes ephemeral port range

by M. Ranjit Mathews

... from 32768:61000 to 1024:29999. There seems to be no reason for it to change the range, so it seems to be a bug.

16 years, 8 months

External USB Keyboard recognition

by Ken Southerland

Hi all, I'm have 64-bit (obviously right?) SuSE 9.2 installed on a Compaq Persario laptop. I am trying to get an external keyboard hooked up to it because I'm used to using the "natural" style keyboards and while i'm at my desk I'ld like to type on that. There is no ps/2 port on this laptop just USB, just an FYI. I can't seem to figure out how to get SuSE to recognize the keyboard, its not automatically detected at boot and nor can I find anything in Yas or in a google search to help me figure out how to do this. Anyone know? Thanks, Ken -- ------s----a----m----s----i----x----e----d----d------ -- Ken Southerland Senior Consultant Sam Six EDD, Inc. 503-236-4288 http://www.samsixedd.com

16 years, 8 months

RE: [suse-amd64] k8_powernow suddenly start to fail.

by Langsdorf, Mark

> I had the CPU frequency scaling working fine on my AMD > Turion-based laptop running SuSE 9.3 and then suddenly it > started to freeze every now and again. > So I tried to reboot and now powersave still does not work. > These are the starup messages after reboot: > --<snip>-- > Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: Found 1 > AMD Athlon 64 / Opteron processors (version 1.00.09e) > Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: 0 : fid 0xa > (1800 MHz), vid 0x4 (1450 mV) > Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: 1 : fid 0x8 > (1600 MHz), vid 0x6 (1400 mV) > Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: 2 : fid 0x0 > (800 MHz), vid 0x16 (1000 mV) > Sep 24 20:23:07 fullyautomatix kernel: powernow-k8: failing > init, change pending bit set > Sep 24 20:23:07 fullyautomatix [powersave][6915]: WARNING in Function > getSupportedSleepStates; line 21: Could not open > /proc/acpi/sleep file to evaluate supported sleeping states > --<snip>-- > > Any idea what could cause this? We've started seeing this internally in AMD QA. The bit that the processor uses to indicate that it is in the process of changing frequencies (aka the pending change bit) is not clearing. The powernow-k8 driver cannot change frequencies until the previous change has completed. Because this is happening on the hardware side, my best guess is that the problem is not software related. We've reported the problem to the AMD hardware debug team and they're investigating. I'll put out a patch when we have a solution. -Mark Langsdorf AMD, Inc.

16 years, 8 months

Video goes blank for a couple of seconds and then comes back (SuSE 9.3)

by Pierre Patino

Greetings I've been experiencing an annoyance since I built this box. Every once in a while, a few times per day, the video goes blank for a couple of seconds and then comes back as if nothing happened. I'm using the nvidia-supplied drivers and the digital video output. Any clues? TIA&Cheers uname -a : Linux lbox 2.6.11.4-21.7-default #2 Tue Jun 21 14:21:54 PDT 2005 x86_64 x86_64 x86_64 GNU/Linux hwinfo --gfxcard: 27: PCI(AGP) 100.0: 0300 VGA compatible controller (VGA) [Created at pci.273] Unique ID: VCu0.Hj+k_rvGEWB Parent ID: vSkL.CP+qXDDqow8 SysFS ID: /devices/pci0000:00/0000:00:01.0/0000:01:00.0 SysFS BusID: 0000:01:00.0 Hardware Class: graphics card Model: "nVidia GeForce FX 5200 (0x0322)" Vendor: pci 0x10de "nVidia Corporation" Device: pci 0x0322 "GeForce FX 5200 (0x0322)" Revision: 0xa1 Driver: "nvidia" Memory Range: 0xf6000000-0xf6ffffff (rw,non-prefetchable) Memory Range: 0xe0000000-0xefffffff (rw,prefetchable) Memory Range: 0xf7800000-0xf781ffff (ro,prefetchable,disabled) IRQ: 193 (2076818 events) I/O Ports: 0x3c0-0x3df (rw) Driver Info #0: XFree86 v4 Server Module: nv Driver Info #1: XFree86 v4 Server Module: nvidia 3D Support: yes Color Depths: 16 Extensions: Options: Config Status: cfg=yes, avail=yes, need=yes, active=unknown Attached to: #11 (PCI bridge) Primary display adapter: #27

16 years, 8 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

openSUSE AMD64 September 2005