- openSUSE AMD64

[opensuse-amd64] How do I confirm which IOMMU method is being used?
by Ron Widell 29 Feb '12

29 Feb '12

Sorry for just barging in so soon after subscribing to this list, but the last messages I saw in the archives related to shutting the list down and I need some help from AMD64 experts. If this is not the correct venue, please point me to a more appropriate one. CPU: AMD Phenom II x6 1100T mobo: Gigabyte GA-990FXA-UD5 (AMD 990FX/SB950 chipset), BIOS version F6 memory: Patriot Viper Extreme 2000MHz (2x4GB, recently upgraded to 4x4GB) OS: openSUSE 12.1 (3.1.9 kernel) Searches related to enabling the AMD-Vi say that it has to be enabled in the BIOS or (I believe it should be AND) have an IVRS table in the ACPI tables. However the kernel ring buffer reported by dmesg(1) shows the following (IOMMU=enabled in the BIOS, no kernel args): [ 0.000000] ACPI: IVRS 00000000bfde0930 000F8 (v01 AMD RD890S 00202031 AMD 00000000) .... [ 0.000000] No AGP bridge found [ 0.000000] Node 0: aperture @ b0000000 size 32 MB [ 0.000000] Aperture pointing to e820 RAM. Ignoring. [ 0.000000] Your BIOS doesn't leave a aperture memory hole [ 0.000000] Please enable the IOMMU option in the BIOS setup [ 0.000000] This costs you 64 MB of RAM [ 0.000000] Mapping aperture over 65536 KB of RAM @ b4000000 and [ 0.772264] AMD-Vi: Enabling IOMMU at 0000:00:00.2 cap 0x40 [ 0.832267] AMD-Vi: Lazy IO/TLB flushing enabled [ 0.832270] PCI-DMA: Using software bounce buffering for IO (SWIOTLB) [ 0.832272] Placing 64MB software IO TLB between ffff8800bbda0000 - ffff8800bfda0000 [ 0.832274] software IO TLB at phys 0xbbda0000 - 0xbfda0000 So it looks like the AMD-Vi IOMMU has been enabled, and I find what appears to me to be a properly formatted IVRS table at /sys/firmware/acpi/tables/IVRS. But it also looks like there have been 2 64MB TLBs created and neither are for the AMD-Vi IOMMU. One appears to be for the GART and the other appears to be for the SWIOTLB mechansim. What I don't see (but I expected to see) is a 64MB area allocated for AMD-Vi IOTLB entries. I also ran a test where I installed 64-bit Mandriva 2011 as a VM under KVM. I then measured the boot times, from kernel launch via GRUB to login screen of that system. In all cases, I performed a cold boot of both the Physical and Virtual systems. This is what I saw: Kernel Args Time iommu=soft,noagp,noaperture 26.87S iommu=memaper 33.84S <none> 33.80S In all cases, the "Kernel Args" are the IOMMU-related parameters I passed to the host machine (openSUSE 12.1) kernel. In cases 1 & 2, the IOMMU (AMD-Vi) was disabled in the (host machine) BIOS. I case 3, the IOMMU was enabled in the BIOS. As you can see, the software implementation was actually faster than the hardware alternatives and there was no difference between the GART and the AMD-Vi instances. None of this passes the common sense test, nor is it consistent with results published by AMD (and others) describing the benefits of the AMD-Vi technology. This also leads me to believe that something is broken with the BIOS in my system. I've tried contacting Gigabyte tech support, but they tell me to get help from the Linux forums, so nothing will get fixed unless I can tell them exactly what's wrong and how to fix it. What else should I be seeing and what shouldn't I be seeing in a properly functioning system? Is there a more definitive way to test or confirm which IOMMU mechanism is actually being used by a running kernel? If more data is needed, please let me know what you need and the most appropriate way to provide it. Thanks, ron -- Ron Widell | Disclaimer, dat-claimer... r_widell<at>bwig<dot>net | if she's mine, I'll claim 'er. -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-amd64+owner(a)opensuse.org

2 2

[opensuse-amd64] Re: [opensuse-ppc] Re: [opensuse-arm] [ml-admin] Merging the architecture lists to opensuse-arch
by Joop Boonen 27 Oct '11

27 Oct '11

On Thu, October 27, 2011 2:41 pm, Karl Eichwalder wrote: > Larry Stotler <larrystotler(a)gmail.com> writes: > >>> Meantime a merged list seems to me to be the wrong way to go: keep >>> lists >>> that are active or might reasonably be expected to become so and kill >>> the >>> others, effectively merging into -project and -factory. >> >> Is it really that big of a deal to leave it be and see what happens? >> Not really sure why it's so necessary to consider something dead when >> it may rise up again unexpectedly. > > Agreed. These arch lists are fine. Problematic are those general > purpose lists such as -factory, -marketing, -project, etc. But as long > as we do not create more of them, we can stand it. (I'm subscribe to > -factory only, though.) When we are at it, is it an option to add opensuse-mips? > > -- > Karl Eichwalder SUSE LINUX Products GmbH > R&D / Documentation MaxfeldstraÃe 5 > 90409 NÃ¼rnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix ImendÃ¶rffer, HRB 16746 (AG > NÃ¼rnberg) > -- > To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org > > Regards, Joop. -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-amd64+owner(a)opensuse.org

1 0

[opensuse-amd64] Re: [opensuse-arm] [ml-admin] Merging the architecture lists to opensuse-arch
by Joop Boonen 26 Oct '11

26 Oct '11

On Wed, October 26, 2011 3:25 pm, Andreas Färber wrote: > Hi, > > Am 26.10.2011 15:04, schrieb Henne Vogelsang: >> On 26.10.2011 14:58, Adrian Schröter wrote: >>> Am Mittwoch, 26. Oktober 2011, 14:29:57 schrieb Henne Vogelsang: >>>> >>>> we are currently trying to reduce the amount of communication channels >>>> we provide. Because of this I would like to merge the 4 architecture >>>> lists into one list called opensuse-arch. >>>> >>>> If nobody objects until the 15th of November 12:00 UTC I will merge >>>> the >>>> lists. You don't have to do anything except rewriting your filter if >>>> you >>>> use one. >>> >>> I would definitive unsubscribe from such a list if the majority of >>> mails is >>> not interessting for me. >> >> The ppc, amd64 and ia64 lists didn't have any traffic in 2010 and 2011. >> I would like to have some point for people to go for non x86 >> architecture specific stuff. > > There was some recent activity to revive ppc openSUSE, so if arm stays > ppc should probably stay as well. > amd64 is mainstream now, so that's different I guess. > I agree. I think it's best to have separate mailing lists for different architectures. I think traffic wise it also safes bandwidth. Only people that are interested in a specific mailing list will get this mail and not traffic they don't want. The ppc mailing list will be very interesting again when the AmigaOne X1000 and Netbook will be released. http://en.wikipedia.org/wiki/AmigaOne_X1000 http://eab.abime.net/showthread.php?p=781936 If this ends up in an active mailing list where also ARM resides it's difficult to filter, I'm subscribed to both. > Andreas > > -- > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany > GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg > -- > To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org > Regards, Joop. -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-amd64+owner(a)opensuse.org

1 0

[opensuse-amd64] Re: [opensuse-arm] [ml-admin] Merging the architecture lists to opensuse-arch
by Henne Vogelsang 26 Oct '11

26 Oct '11

Hey, On 26.10.2011 14:58, Adrian Schröter wrote: > Am Mittwoch, 26. Oktober 2011, 14:29:57 schrieb Henne Vogelsang: >> >> we are currently trying to reduce the amount of communication channels >> we provide. Because of this I would like to merge the 4 architecture >> lists into one list called opensuse-arch. >> >> If nobody objects until the 15th of November 12:00 UTC I will merge the >> lists. You don't have to do anything except rewriting your filter if you >> use one. > > I would definitive unsubscribe from such a list if the majority of mails is > not interessting for me. The ppc, amd64 and ia64 lists didn't have any traffic in 2010 and 2011. I would like to have some point for people to go for non x86 architecture specific stuff. Henne -- ml-admin http://www.opensuse.org -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-amd64+owner(a)opensuse.org

1 0

[opensuse-amd64] Re: [opensuse-ppc] [ml-admin] Merging the architecture lists to opensuse-arch
by Joop Boonen 26 Oct '11

26 Oct '11

On Wed, October 26, 2011 2:29 pm, Henne Vogelsang wrote: > Hey, > > we are currently trying to reduce the amount of communication channels we provide. Because of this I would like to merge the 4 architecture lists into one list called opensuse-arch. > > If nobody objects until the 15th of November 12:00 UTC I will merge the lists. You don't have to do anything except rewriting your filter if you use one. > Wouldn't it be best to leave the arm mailing list as is until the arm port has been completed? > Thanks in advance for your consideration. > > Henne > > -- > Mailing List Admin > http://lists.opensuse.org > -- > To unsubscribe, e-mail: opensuse-ppc+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse-ppc+owner(a)opensuse.org > > Regards, Joop. -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-amd64+owner(a)opensuse.org

1 0

[opensuse-amd64] [ml-admin] Merging the architecture lists to opensuse-arch
by Henne Vogelsang 26 Oct '11

26 Oct '11

Hey, we are currently trying to reduce the amount of communication channels we provide. Because of this I would like to merge the 4 architecture lists into one list called opensuse-arch. If nobody objects until the 15th of November 12:00 UTC I will merge the lists. You don't have to do anything except rewriting your filter if you use one. Thanks in advance for your consideration. Henne -- Mailing List Admin http://lists.opensuse.org -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-amd64+owner(a)opensuse.org

2 1

[opensuse-amd64] Wrong Languages on openSuSE's Support Site!
by Constantine 'Gus' Fantanas 07 Dec '09

07 Dec '09

This is not strictly a 32-versus-64-bit issue, but I have to post it somewhere on some SuSE support list. I am trying to do an online upgrade to 11.2 from 11.1, as I explained in my previous email. I used google to search the openSuSE support site, but pages which are supposed to be in English come up in anything other than English! For example, < http://en.opensuse.org/Upgrade/11.2#Implementation > comes up in Spanish, and < http://en.opensuse.org/Upgrade > comes up in German. When I select "English" from the drop-down box named "Andere Sprachen" (Other Languages), nothing happens. This is very-very frustrating. Isn't the "en" in the beginning of the URL supposed to reference pages in English? I am not trying to insinuate that speaking a language other than English is wrong,I am only trying to say that support should be neatly categorized depending on language. -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

2 1

[opensuse-amd64] Ext4 and >16TB - how?
by Martin Jungowski 05 Dec '09

05 Dec '09

We're trying to create a 27TB partition on openSUSE 11.2 x86_64 and seem to be running into issues with e2fsprogs. Here's what happens: > root/bebd1$ mkfs.ext4 -v /dev/sdd1 > mke2fs 1.41.9 (22-Aug-2009) > mkfs.ext4: Size of device /dev/sdd1 too big to be expressed in 32 bits > using a blocksize of 4096. > root/bebd1$ uname -a > Linux bebd1 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 > +0100 x86_64 x86_64 x86_64 GNU/Linux All hitherto posts related to this problem seem to indicate that the underlying tools, such as mkfs itself, are still 32-bit even on a 64-bit system and that fixing this is top priority. That was as of April 2009 - is it possible that this issue has not been resolved yet? Or, to be more specific: what do I need to do in order to create a 27TB ext4 filesystem? Thanks, Martin -- Rieke Computersysteme GmbH Hellerholz 5 D-82061 Neuried Email: martin(a)rhm.de -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

6 10

[opensuse-amd64] Upgrading from 11.1 with encrypted partitions to 11.2
by Constantine 'Gus' Fantanas 05 Dec '09

05 Dec '09

I guess this is not strictly a 64-bit question, but I have been posting on this board since 2004. I am on openSuSE 11.1, 64-bits, and I want to upgrade to 11.2. My problem is that I have four partitions, /boot, /swap, /, and /home, of which the last three are encrypted. If I remember correctly, here is how I ended up with the current configuration: Initially, I had normal ext3 partitions, but I was running out of hard disk space. I got a bigger drive, which I connected to my computer (a laptop) via USB2.0, which I fdisked to four partitions, of which I encrypted the last three using luksFormat, created loopback devices with 'cyptsetup luksOpen', mounted them, created ext3 filesystems, and then copied the data from the original (unecrypted) partitions. In GRUB, I also issued kernel directives so, the kernel can at least find a root file system. (Somehow, I cannot get the crypttab straight, the kernel ignores it,and prompts me for the password for all three encrypted partitions, and then I get a message that the encrypted partitions are already assigned, but that's another story.) the system works reasonably well. When I tried to upgrade via an openSuSE 11.2 DVD, naturally, the DVD's kernel could see the partitions, but displayed them as "unknown." How can I get out of it? I am too hesitant to upgrade via 'zypper dup'. Thank you in advance for your time. CF -- Running 64-bit Linux on AMD64 -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0

[opensuse-amd64] Power Outage
by ml-admin＠opensuse.org 11 Sep '09

11 Sep '09

Broadcast message from ml-admin(a)opensuse.org (/dev/pts/0) at 07:30 GMT ... The system is going down for halt NOW! -- To unsubscribe, e-mail: opensuse-amd64+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-amd64+help(a)opensuse.org

1 0