From prarit at redhat.com Wed Nov 1 05:00:16 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Wed, 1 Nov 2006 00:00:16 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-1 Message-ID: <200611010500.kA150Gu0007620@devserv.devel.redhat.com> Bugs filed against fedora-ia64. If a you have filed a bug and it is not listed below, then it is likely you did not file it under the appropriate Product (Fedora Core) or Hardware Category (ia64). Total bugs in each state: NEEDINFO: 4 REOPENED: 1 MODIFIED: 1 ASSIGNED: 7 CLOSED : 166 NEW : 10 RECENT MOVERS (changed in past 7 days): 14 212929: [NEW] xen-sdlfb is defunct 212515: [ASSIGNED] vncfb does not run on IA64 212299: [NEW] The Domain-0 was hang after the VTI-Domain panic 212295: [NEW] domVTI cannot boot with a message ""Cannot allocate memory"". 212117: [ASSIGNED] Dom0 does not boot when audit packages are intalled. 211444: [NEW] DomU/DomVTI cannot boot on IA64 208895: [ASSIGNED] blktap does not build on ia64 208062: [NEW] [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko 204011: [NEW] Xen: kernel unaligned access 202973: [NEW] xen/ia64 fc6 blockers 200269: [MODIFIED] selinux causes kernel installation failure 178747: [NEEDINFO] rc.sysinit/bash denied execmod 171549: [NEEDINFO] Button release only works after cursor moves. Happens only on kernels 1526 and 1532. 1426 was ok. 137594: [CLOSED] gthumb crashes on startup on ia64 NEW state: 10 212929: xen-sdlfb is defunct 212299: The Domain-0 was hang after the VTI-Domain panic 212295: domVTI cannot boot with a message ""Cannot allocate memory"". 211961: Install hangs with blank screen 211444: DomU/DomVTI cannot boot on IA64 208062: [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko 207241: XenU domain can not be created successfully. 204011: Xen: kernel unaligned access 202973: xen/ia64 fc6 blockers 181501: unaligned accesses seen during mono execution From y_katase at soft.fujitsu.com Thu Nov 2 10:51:24 2006 From: y_katase at soft.fujitsu.com (Yoshinori Katase) Date: Thu, 2 Nov 2006 19:51:24 +0900 Subject: [Fedora-ia64-list] [ANNOUNCE]: One week delay in Fedora ia64 FC6 v2release References: <45420DF7.7060409@redhat.com> Message-ID: <02d701c6fe6c$d76d37a0$1a247c0a@ykatase> Hi Prarit, Please upload checksum file. Regards. Katase. ----- Original Message ----- From: "Prarit Bhargava" To: "ia64 Fedora Core Development" ; "Brian Stein" ; "Bob Johnson" Sent: Friday, October 27, 2006 10:47 PM Subject: [Fedora-ia64-list] [ANNOUNCE]: One week delay in Fedora ia64 FC6 v2release > Everyone, > > I'm announcing a one-week delay in the FC6 ia64 release. This will give me time to verify the CD, DVD, and net installations. > > Hopefully this doesn't cause any major headaches for anyone, > > P. > > -- > Fedora-ia64-list mailing list > Fedora-ia64-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-ia64-list > From prarit at redhat.com Thu Nov 2 14:46:24 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Thu, 02 Nov 2006 09:46:24 -0500 Subject: [Fedora-ia64-list] [ANNOUNCE]: FC6 GOLD ISOs available Message-ID: <454A04C0.8090505@redhat.com> I've built a set of FC6 ia64 ISOs (CD set and DVD) which are available for download from ftp://oss.sgi.com/projects/fedora/ 9aea82e31ace9ceb3e5aba210f4cda14 FC6GOLD-ia64-disc1.iso c3b3dd2e4cc0e4c60e4589532e79b4b4 FC6GOLD-ia64-disc2.iso 093b5aa79be4cd9ab8aff6f743df9fec FC6GOLD-ia64-disc3.iso f90baccedc2a1d5b1a0582649235691f FC6GOLD-ia64-disc4.iso afcfa7f9d6b47b2f78107dcbcce63eef FC6GOLD-ia64-disc5.iso 88ad15a45ca9dad378636cf572f4be03 FC6GOLD-ia64-DVD.iso (Click on Download on left-hand side, and then the FC6 directory) These are labelled as FC6GOLD to differentiate them from the broken sets that Yanmin attempted to release last week. md5sums are provided. We have verified CD, DVD, NFS, http, ftp installs on various HP & SGI boxes. Please remember that FC6 ia64 is _unsupported_ by Fedora. You can file bugs, but be sure to file them against the devel branch of Fedora Core. Also, add "fedora-ia64" to the "blocks" field of the BZ. Thanks to Doug for helping out with the install testing -- without his help the release probably would not have happened ... I _really_ appreciate the extra effort Doug. :) P. From prarit at redhat.com Mon Nov 6 05:00:04 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Mon, 6 Nov 2006 00:00:04 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-6 Message-ID: <200611060500.kA6504ox018239@devserv.devel.redhat.com> Bugs filed against fedora-ia64. If a you have filed a bug and it is not listed below, then it is likely you did not file it under the appropriate Product (Fedora Core) or Hardware Category (ia64). Total bugs in each state: NEEDINFO: 4 REOPENED: 1 MODIFIED: 1 ASSIGNED: 7 CLOSED : 166 NEW : 11 RECENT MOVERS (changed in past 7 days): 3 213386: [NEW] Installation by NFS failed if not decomposing the CD or DVD images 212117: [ASSIGNED] Dom0 does not boot when audit packages are intalled. 185100: [NEEDINFO] ia64: X fails to properly query PCI bus NEW state: 11 213386: Installation by NFS failed if not decomposing the CD or DVD images 212929: xen-sdlfb is defunct 212299: The Domain-0 was hang after the VTI-Domain panic 212295: domVTI cannot boot with a message ""Cannot allocate memory"". 211961: Install hangs with blank screen 211444: DomU/DomVTI cannot boot on IA64 208062: [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko 207241: XenU domain can not be created successfully. 204011: Xen: kernel unaligned access 202973: xen/ia64 fc6 blockers 181501: unaligned accesses seen during mono execution From prarit at redhat.com Mon Nov 13 05:00:03 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Mon, 13 Nov 2006 00:00:03 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 Message-ID: <200611130500.kAD503ld013432@devserv.devel.redhat.com> Bugs filed against fedora-ia64. If a you have filed a bug and it is not listed below, then it is likely you did not file it under the appropriate Product (Fedora Core) or Hardware Category (ia64). Total bugs in each state: NEEDINFO: 6 REOPENED: 1 MODIFIED: 1 ASSIGNED: 6 CLOSED : 167 NEW : 11 RECENT MOVERS (changed in past 7 days): 2 208895: [ASSIGNED] blktap does not build on ia64 163350: [ASSIGNED] Tracking bug for Fedora Core ia64/Itanium support NEW state: 11 214338: Must specify RAM size to get kernel to boot 212929: xen-sdlfb is defunct 212299: The Domain-0 was hang after the VTI-Domain panic 212295: domVTI cannot boot with a message ""Cannot allocate memory"". 211961: Install hangs with blank screen 211444: DomU/DomVTI cannot boot on IA64 208062: [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko 207241: XenU domain can not be created successfully. 204011: Xen: kernel unaligned access 202973: xen/ia64 fc6 blockers 181501: unaligned accesses seen during mono execution From luming.yu at intel.com Mon Nov 13 05:23:10 2006 From: luming.yu at intel.com (Yu, Luming) Date: Mon, 13 Nov 2006 13:23:10 +0800 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 Message-ID: <1C601A6A3344064EB423D0C1E83B717B75FC8E@pdsmsx411.ccr.corp.intel.com> where is the bug 202096: ia64: unaligned accesses during dmraid execution at startup ? >-----Original Message----- >From: fedora-ia64-list-bounces at redhat.com >[mailto:fedora-ia64-list-bounces at redhat.com] On Behalf Of >Prarit Bhargava >Sent: 2006?11?13? 13:00 >To: fedora-ia64-list at redhat.com >Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 > > >Bugs filed against fedora-ia64. If a you have filed a bug and >it is not listed below, then it is likely you did not file it under >the appropriate Product (Fedora Core) or Hardware Category (ia64). > >Total bugs in each state: >NEEDINFO: 6 >REOPENED: 1 >MODIFIED: 1 >ASSIGNED: 6 >CLOSED : 167 >NEW : 11 > >RECENT MOVERS (changed in past 7 days): 2 >208895: [ASSIGNED] blktap does not build on ia64 >163350: [ASSIGNED] Tracking bug for Fedora Core ia64/Itanium support > >NEW state: 11 >214338: Must specify RAM size to get kernel to boot >212929: xen-sdlfb is defunct >212299: The Domain-0 was hang after the VTI-Domain panic >212295: domVTI cannot boot with a message ""Cannot allocate memory"". >211961: Install hangs with blank screen >211444: DomU/DomVTI cannot boot on IA64 >208062: [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko >207241: XenU domain can not be created successfully. >204011: Xen: kernel unaligned access >202973: xen/ia64 fc6 blockers >181501: unaligned accesses seen during mono execution > >-- >Fedora-ia64-list mailing list >Fedora-ia64-list at redhat.com >https://www.redhat.com/mailman/listinfo/fedora-ia64-list > From prarit at redhat.com Mon Nov 13 12:13:14 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Mon, 13 Nov 2006 07:13:14 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 In-Reply-To: <1C601A6A3344064EB423D0C1E83B717B75FC8E@pdsmsx411.ccr.corp.intel.com> References: <1C601A6A3344064EB423D0C1E83B717B75FC8E@pdsmsx411.ccr.corp.intel.com> Message-ID: <4558615A.3010405@redhat.com> Yu, Luming wrote: > where is the bug 202096: ia64: unaligned accesses during > dmraid execution at startup ? > > 202096 was incorrectly filed under fc6test2 -- all Fedora ia64 bugs should be filed under "devel". P. > From jbass at dmsd.com Mon Nov 13 12:22:40 2006 From: jbass at dmsd.com (John L. Bass) Date: Mon, 13 Nov 2006 05:22:40 -0700 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 Message-ID: <200611131222.kADCMeoO005050@dmsd.com> On Mon, 13 Nov 2006 07:13:14 -0500 Prarit Bhargava writes: > 202096 was incorrectly filed under fc6test2 -- all Fedora ia64 bugs > should be filed under "devel". As I've noted before, most people understand selecting fedora, release, and platform. The "devel" requirement is highly counter productive for the project as valid bug reports are certain to be lost by helpful volunteer testers, slowing the maturity of this project. If this project is an actual RedHat/Fedora sponsored project, it would seem wise to have a friendly talk with the Bugzilla admin (or RedHat managment) to implement bug reports to any flavor of Fedora and ia64 being directed to this project. From prarit at redhat.com Mon Nov 13 14:00:20 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Mon, 13 Nov 2006 09:00:20 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 In-Reply-To: <200611131222.kADCMeoO005050@dmsd.com> References: <200611131222.kADCMeoO005050@dmsd.com> Message-ID: <45587A74.1000708@redhat.com> > > If this project is an actual RedHat/Fedora sponsored project, it would seem wise > It is not. And that has been made clear many times on this list ;) P. From jbass at dmsd.com Mon Nov 13 14:09:48 2006 From: jbass at dmsd.com (John L. Bass) Date: Mon, 13 Nov 2006 07:09:48 -0700 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 Message-ID: <200611131409.kADE9m6C005494@dmsd.com> > > If this project is an actual RedHat/Fedora sponsored project, it would seem wise > It is not. And that has been made clear many times on this list ;) P. Hmmm ... interesting. given the list name and host, and that you are using fedora logo's in release (which wouldn't be allowed for a 3rd party release) along with bug reporting to devel at redhat, I do say, it's something of a suprise given the fedora/redhat license. What's it take to get the Fedore team to officially sponsor the project? John From prarit at redhat.com Mon Nov 13 14:35:27 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Mon, 13 Nov 2006 09:35:27 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 In-Reply-To: <200611131409.kADE9m6C005494@dmsd.com> References: <200611131409.kADE9m6C005494@dmsd.com> Message-ID: <455882AF.5000705@redhat.com> John L. Bass wrote: > Hmmm ... interesting. given the list name and host, and that you are using > fedora logo's in release (which wouldn't be allowed for a 3rd party release) > along with bug reporting to devel at redhat, I do say, it's something of > a suprise given the fedora/redhat license. > > I have an "official" written and verbal okay from the Fedora Project to do "unofficial" ia64 releases as long as I stress that they are unsupported. I guess in some sense it comes down to what the word "unsupported" means... We are submitting bugs, and they are being fixed -- by myself, sometimes by other engineers. Does that mean the arch is "supported"? Not really because ia64 bugs are treated as second class bugs -- they won't be used as blocking issues for releases, etc.. Keep in mind a year ago it seemed to me that Fedora wasn't even interested in ia64 bugs (read below on how this has changed). > What's it take to get the Fedore team to officially sponsor the project? > We've made a lot of progress but there are still many obstacles before Fedora Project will officially support ia64. The bottom line is this: I (as in _me_, Prarit) need to show enough community involvement in the project and show that the community involvement can be sustained. IMO, we're not quite there yet. While this list has 100+ members I would say that there are at most 10 people who are actively involved in the project and maintaining the project. IMO, we do not yet have enough demand for ia64 -- and there's the problem with getting HW available for Fedora Project's testing, etc. Don't let this get you down though -- we've come A LONG WAY. IIRC, in February the kernel did not boot and anaconda did not work :). There was no FC4 release for ia64. Now when something breaks on ia64 the build managers know precisely who to come to for help fixing the issues (.... thinking about it, that's not such a good thing :) :) :) :) ) I've also succeeded in convincing individual package maintainers that replying with "Well, it's only ia64 so who cares?" is not a valid response to bugs. We have _CDs_ and a _DVD_ to install from -- that was unheard of last year. One of the things I've been pushing for is that the ia64 extras branch be publicly exported. That's the next big thing on my list. In conclusion, we've made a lot of progress but we have a long way to go ... P. From jbass at dmsd.com Mon Nov 13 15:20:20 2006 From: jbass at dmsd.com (John L. Bass) Date: Mon, 13 Nov 2006 08:20:20 -0700 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-13 Message-ID: <200611131520.kADFKKV3005918@dmsd.com> IMO, we do not yet have enough demand for ia64 -- and there's the problem with getting HW available for Fedora Project's testing, etc. Where is your QA/Test lab and who operates it? I've offered twice to provide testing for SR870BN4 and SR870BH2 machines from Intel and Dell, which hasn't yet been exploited. I assume from this that list members machines can't be part of your QA/Test cycle. That makes it pretty difficult to expand your HW available for the project. I have a fair sized cluster here that I can divert a machine or two for testing when needed. All you need to provide is the QA test scripts (both manual and automated). I can even provide remote access, including remote console access, if needed. From prarit at redhat.com Mon Nov 20 05:00:04 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Mon, 20 Nov 2006 00:00:04 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-20 Message-ID: <200611200500.kAK504ut010388@devserv.devel.redhat.com> Bugs filed against fedora-ia64. If a you have filed a bug and it is not listed below, then it is likely you did not file it under the appropriate Product (Fedora Core) or Hardware Category (ia64). Total bugs in each state: NEEDINFO: 5 REOPENED: 1 MODIFIED: 1 ASSIGNED: 7 CLOSED : 170 NEW : 10 RECENT MOVERS (changed in past 7 days): 9 215624: [CLOSED] Basic ""hello-world"" with systemtap doesn't work 213386: [ASSIGNED] Installation by NFS failed if not decomposing the CD or DVD images 212515: [ASSIGNED] vncfb does not run on IA64 212119: [CLOSED] vmm is not discribed in elilo.conf 208895: [ASSIGNED] blktap does not build on ia64 208062: [NEW] [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko 207241: [NEW] XenU domain can not be created successfully. 202096: [NEEDINFO] ia64: unaligned accesses during dmraid execution at startup 163350: [ASSIGNED] Tracking bug for Fedora Core ia64/Itanium support NEW state: 10 212929: xen-sdlfb is defunct 212299: The Domain-0 was hang after the VTI-Domain panic 212295: domVTI cannot boot with a message ""Cannot allocate memory"". 211961: Install hangs with blank screen 211444: DomU/DomVTI cannot boot on IA64 208062: [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko 207241: XenU domain can not be created successfully. 204011: Xen: kernel unaligned access 202973: xen/ia64 fc6 blockers 181501: unaligned accesses seen during mono execution From takebe_akio at jp.fujitsu.com Tue Nov 28 01:37:16 2006 From: takebe_akio at jp.fujitsu.com (Akio Takebe) Date: Tue, 28 Nov 2006 10:37:16 +0900 Subject: [Fedora-ia64-list] xen/ia64 kernel BUG while rebooting Message-ID: Hi, I'm debugging the following Bugzilla now. RH Bugzilla#203032: xen/ia64 kernel BUG while rebooting https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203032 RHEL5beta and FC6 still show the CallTrace while rebooting. I check why it is shown. I found thd CallTrace is not shown if we reboot after doing the below. # /etc/xen/scripts/network-bridge stop I think it should be happened also by using source of xen-ia64-unstable. (not RH source) But e1000_shutdown() is not called when I use source of xen-ia64-unstable. I don't know why yet. I'll continue to debug it. If you have comments, please tell me. Best Regards, Akio Takebe From prarit at redhat.com Wed Nov 29 18:11:55 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Wed, 29 Nov 2006 13:11:55 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-29 Message-ID: <200611291811.kATIBtxR032283@devserv.devel.redhat.com> Bugs filed against fedora-ia64. If a you have filed a bug and it is not listed below, then it is likely you did not file it under the appropriate Product (Fedora Core) or Hardware Category (ia64). Total bugs in each state: NEEDINFO: 4 REOPENED: 1 MODIFIED: 1 ASSIGNED: 9 CLOSED : 173 NEW : 10 RECENT MOVERS (changed in past 7 days): 9 217416: [ASSIGNED] /proc and /sys are not mounted during the system install 217392: [CLOSED] boot.iso + ""linux rescue"" drops into python debugger 217026: [CLOSED] gaim crash with this error: libnm_glib_nm_state_cb: dbus returned an error 216988: [CLOSED] problem with openmp - gettext-0.16 doesn't build on ia64 213386: [ASSIGNED] Installation by NFS failed if not decomposing the CD or DVD images 208895: [ASSIGNED] blktap does not build on ia64 204758: [ASSIGNED] ia64: anaconda dies on device-mapper errors 202096: [ASSIGNED] ia64: unaligned accesses during dmraid execution at startup 163350: [ASSIGNED] Tracking bug for Fedora Core ia64/Itanium support NEW state: 10 212929: xen-sdlfb is defunct 212299: The Domain-0 was hang after the VTI-Domain panic 212295: domVTI cannot boot with a message ""Cannot allocate memory"". 211961: Install hangs with blank screen 211444: DomU/DomVTI cannot boot on IA64 208062: [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko 207241: XenU domain can not be created successfully. 204011: Xen: kernel unaligned access 202973: xen/ia64 fc6 blockers 181501: unaligned accesses seen during mono execution From prarit at redhat.com Wed Nov 29 18:13:27 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Wed, 29 Nov 2006 13:13:27 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-29 In-Reply-To: <200611291811.kATIBtxR032283@devserv.devel.redhat.com> References: <200611291811.kATIBtxR032283@devserv.devel.redhat.com> Message-ID: <456DCDC7.7030109@redhat.com> Sorry about this everyone -- my system crashed and for some reason crond wasn't running when it rebooted :( P. Prarit Bhargava wrote: > Bugs filed against fedora-ia64. If a you have filed a bug and > it is not listed below, then it is likely you did not file it under > the appropriate Product (Fedora Core) or Hardware Category (ia64). > > Total bugs in each state: > NEEDINFO: 4 > REOPENED: 1 > MODIFIED: 1 > ASSIGNED: 9 > CLOSED : 173 > NEW : 10 > > RECENT MOVERS (changed in past 7 days): 9 > 217416: [ASSIGNED] /proc and /sys are not mounted during the system install > 217392: [CLOSED] boot.iso + ""linux rescue"" drops into python debugger > 217026: [CLOSED] gaim crash with this error: libnm_glib_nm_state_cb: dbus returned an error > 216988: [CLOSED] problem with openmp - gettext-0.16 doesn't build on ia64 > 213386: [ASSIGNED] Installation by NFS failed if not decomposing the CD or DVD images > 208895: [ASSIGNED] blktap does not build on ia64 > 204758: [ASSIGNED] ia64: anaconda dies on device-mapper errors > 202096: [ASSIGNED] ia64: unaligned accesses during dmraid execution at startup > 163350: [ASSIGNED] Tracking bug for Fedora Core ia64/Itanium support > > NEW state: 10 > 212929: xen-sdlfb is defunct > 212299: The Domain-0 was hang after the VTI-Domain panic > 212295: domVTI cannot boot with a message ""Cannot allocate memory"". > 211961: Install hangs with blank screen > 211444: DomU/DomVTI cannot boot on IA64 > 208062: [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko > 207241: XenU domain can not be created successfully. > 204011: Xen: kernel unaligned access > 202973: xen/ia64 fc6 blockers > 181501: unaligned accesses seen during mono execution > > -- > Fedora-ia64-list mailing list > Fedora-ia64-list at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-ia64-list > > From prarit at redhat.com Thu Nov 30 05:00:15 2006 From: prarit at redhat.com (Prarit Bhargava) Date: Thu, 30 Nov 2006 00:00:15 -0500 Subject: [Fedora-ia64-list] Fedora ia64 Buglist 2006-11-30 Message-ID: <200611300500.kAU50Fkq004031@devserv.devel.redhat.com> Bugs filed against fedora-ia64. If a you have filed a bug and it is not listed below, then it is likely you did not file it under the appropriate Product (Fedora Core) or Hardware Category (ia64). Total bugs in each state: NEEDINFO: 4 REOPENED: 1 MODIFIED: 1 ASSIGNED: 9 CLOSED : 173 NEW : 10 RECENT MOVERS (changed in past 7 days): 9 217416: [ASSIGNED] /proc and /sys are not mounted during the system install 217392: [CLOSED] boot.iso + ""linux rescue"" drops into python debugger 217026: [CLOSED] gaim crash with this error: libnm_glib_nm_state_cb: dbus returned an error 216988: [CLOSED] problem with openmp - gettext-0.16 doesn't build on ia64 208895: [ASSIGNED] blktap does not build on ia64 204758: [ASSIGNED] ia64: anaconda dies on device-mapper errors 202096: [ASSIGNED] ia64: unaligned accesses during dmraid execution at startup 191521: [CLOSED] loader received SIGSEGV during install 163350: [ASSIGNED] Tracking bug for Fedora Core ia64/Itanium support NEW state: 10 212929: xen-sdlfb is defunct 212299: The Domain-0 was hang after the VTI-Domain panic 212295: domVTI cannot boot with a message ""Cannot allocate memory"". 211961: Install hangs with blank screen 211444: DomU/DomVTI cannot boot on IA64 208062: [IA64-Xen] XenU would crash Xen0, if insmod xennet.ko 207241: XenU domain can not be created successfully. 204011: Xen: kernel unaligned access 202973: xen/ia64 fc6 blockers 181501: unaligned accesses seen during mono execution